Commit Graph

6 Commits

Author SHA1 Message Date
Dave McCowan 6d9cf739ca Add documentation for two-VIP and TLS blueprints
Relates-to: blueprint kolla-ssl

Change-Id: Id82d22c2195be5d897c781f28087a1ea422b8bea
2016-03-08 09:27:26 -05:00
Dave McCowan 25f99ad930 Add two more examples of openrc for use with public endpoints
Relates-to: blueprint kolla-ssl

Change-Id: I6d9531ce4513ed06f1d13081418b167ad264aaff
2016-03-05 20:45:10 -05:00
SamYaple d3cfb2052a Change kolla_internal_address variable
Due to poor planning on our variable names we have a situation where
we have "internal_address" which must be a VIP, but "external_address"
which should be a DNS name. Now with two vips "external_vip_address"
is a new variable.

This corrects that issue by deprecating kolla_internal_address and
replacing it with 4 nicely named variables.

kolla_internal_vip_address
kolla_internal_fqdn
kolla_external_vip_address
kolla_external_fqdn

The default behaviour will remain the same, and the way the variable
inheritance is setup the kolla_internal_address variable can still be
set in globals.yml and propogate out to these 4 new variables like it
normally would, but all reference to kolla_internal_address has been
completely removed.

Change-Id: I4556dcdbf4d91a8d2751981ef9c64bad44a719e5
Partially-Implements: blueprint ssl-kolla
2016-02-26 20:00:09 +00:00
Hui Kang bcce4502ed Use kolla_internal_address in the example rc file
Change-Id: I4ec1b5208a347a45ff729e1d8bff6fe6e37b925e
Closes-Bug: #1509865
2015-10-28 12:50:02 -04:00
Steven Dake c950212079 Use external address in openrc-example
This is mostly a docs change.  The external address should be used
rather than the internal address when sourcing openrc-example.
The internal address may not be accessible from outside the VIP
interface.

Change-Id: I10ac0c116227af9c4409a050203e2a28e3a116a2
2015-08-28 15:06:41 +00:00
Sam Yaple 7a25b6bea3 Adds an example openrc file
Change-Id: Ie056a8347f6b72ffb647bfb79ee4449ca45f3fef
Closes-Bug: #1476294
2015-07-31 23:58:36 +00:00