diff options
| author | Dave McCowan <dmccowan@cisco.com> | 2016-02-18 13:50:39 -0500 |
|---|---|---|
| committer | Dave McCowan <dmccowan@cisco.com> | 2016-02-24 09:18:06 -0500 |
| commit | 34c2cb8e64c4758ec9e834dc3fabc9f5835fe9ac (patch) | |
| tree | fb5fea1f267fb85abf994bdfd5de015fe1d6b2dc /doc | |
| parent | 3f8bc072706dc7dfb064ea37813dc2ccc3d87e31 (diff) | |
| download | kolla-34c2cb8e64c4758ec9e834dc3fabc9f5835fe9ac.tar.gz kolla-34c2cb8e64c4758ec9e834dc3fabc9f5835fe9ac.zip | |
Implement Option for Two VIPs to separate API traffic
To improve security, operators have asked for two VIPs for
their cloud.
VIP 1 is the internal VIP that can reach internal and admin endpoints.
In addition, the internal VIP can also reach other internal services,
such as the database and message services.
VIP 2 is the external VIP that can only reach public endpoints.
With one VIP only, all services are reached at the same address.
To add a second VIP, this patch adds two new configuration parameters.
kolla_external_vip_address: is an IPv4 address to use for created VIP
kolla_external_vip_interface: is the network interface to use for VIP
In this scenario, the first VIP (the internal VIP), is defined by
the original parameters (kolla_internal address and network_interface).
When using two VIPs, the existing kolla_external_address parameter
should be/point to/resolve to the kolla_external_vip_address.
Closes-bug: 1535333
Change-Id: I5bfcefaf7899298455cdade8209c34324aebfecb
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions