Remove the barbican "Grant access" from cookbook
We missed a line when removing the requirement to grant Octavia access to the secret in barbican. This patch corrects that oversight. Change-Id: I3c6459becc415d6dc0792c44ca75e717b239cd92
This commit is contained in:
parent
0c1cb417e9
commit
cb55a8cf78
|
@ -421,12 +421,11 @@ balancer features, like Layer 7 features and header manipulation.
|
|||
1. Combine the individual cert/key/intermediates to a single PKCS12 file.
|
||||
2. Create a barbican *secret* resource for the PKCS12 file. We will call
|
||||
this *tls_secret1*.
|
||||
3. Grant the *admin* user access to the *tls_secret1* barbican resource.
|
||||
4. Create load balancer *lb1* on subnet *public-subnet*.
|
||||
5. Create listener *listener1* as a TERMINATED_HTTPS listener referencing
|
||||
3. Create load balancer *lb1* on subnet *public-subnet*.
|
||||
4. Create listener *listener1* as a TERMINATED_HTTPS listener referencing
|
||||
*tls_secret1* as its default TLS container.
|
||||
6. Create pool *pool1* as *listener1*'s default pool.
|
||||
7. Add members 192.0.2.10 and 192.0.2.11 on *private-subnet* to *pool1*.
|
||||
5. Create pool *pool1* as *listener1*'s default pool.
|
||||
6. Add members 192.0.2.10 and 192.0.2.11 on *private-subnet* to *pool1*.
|
||||
|
||||
**CLI commands**:
|
||||
|
||||
|
@ -474,13 +473,12 @@ listener using Server Name Indication (SNI) technology.
|
|||
1. Combine the individual cert/key/intermediates to single PKCS12 files.
|
||||
2. Create barbican *secret* resources for the PKCS12 files. We will call them
|
||||
*tls_secret1* and *tls_secret2*.
|
||||
3. Grant the *admin* user access to both *tls_secret* barbican resources.
|
||||
4. Create load balancer *lb1* on subnet *public-subnet*.
|
||||
5. Create listener *listener1* as a TERMINATED_HTTPS listener referencing
|
||||
3. Create load balancer *lb1* on subnet *public-subnet*.
|
||||
4. Create listener *listener1* as a TERMINATED_HTTPS listener referencing
|
||||
*tls_secret1* as its default TLS container, and referencing both
|
||||
*tls_secret1* and *tls_secret2* using SNI.
|
||||
6. Create pool *pool1* as *listener1*'s default pool.
|
||||
7. Add members 192.0.2.10 and 192.0.2.11 on *private-subnet* to *pool1*.
|
||||
5. Create pool *pool1* as *listener1*'s default pool.
|
||||
6. Add members 192.0.2.10 and 192.0.2.11 on *private-subnet* to *pool1*.
|
||||
|
||||
**CLI commands**:
|
||||
|
||||
|
@ -537,13 +535,12 @@ HTTP just get redirected to the HTTPS listener), then please see `the example
|
|||
1. Combine the individual cert/key/intermediates to a single PKCS12 file.
|
||||
2. Create a barbican *secret* resource for the PKCS12 file. We will call
|
||||
this *tls_secret1*.
|
||||
3. Grant the *admin* user access to the *tls_secret1* barbican resource.
|
||||
4. Create load balancer *lb1* on subnet *public-subnet*.
|
||||
5. Create listener *listener1* as a TERMINATED_HTTPS listener referencing
|
||||
3. Create load balancer *lb1* on subnet *public-subnet*.
|
||||
4. Create listener *listener1* as a TERMINATED_HTTPS listener referencing
|
||||
*tls_secret1* as its default TLS container.
|
||||
6. Create pool *pool1* as *listener1*'s default pool.
|
||||
7. Add members 192.0.2.10 and 192.0.2.11 on *private-subnet* to *pool1*.
|
||||
8. Create listener *listener2* as an HTTP listener with *pool1* as its
|
||||
5. Create pool *pool1* as *listener1*'s default pool.
|
||||
6. Add members 192.0.2.10 and 192.0.2.11 on *private-subnet* to *pool1*.
|
||||
7. Create listener *listener2* as an HTTP listener with *pool1* as its
|
||||
default pool.
|
||||
|
||||
**CLI commands**:
|
||||
|
|
Loading…
Reference in New Issue