admin_address cannot be configured independently of internal_address

[Paul Bourke]

Some administrators want to configure the management endpoint to be on a separate interface to the internal address.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/282513

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/282513
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=34c2cb8e64c4758ec9e834dc3fabc9f5835fe9ac
Submitter: Jenkins
Branch: master

commit 34c2cb8e64c4758ec9e834dc3fabc9f5835fe9ac
Author: Dave McCowan <email address hidden>
Date: Thu Feb 18 13:50:39 2016 -0500

    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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Paul Bourke (<email address hidden>) on branch: master
Review: https://review.openstack.org/269114