Allow for usage of pre-allocated IPs for the controller nodes
authorGiulio Fidente <gfidente@redhat.com>
Wed, 9 Dec 2015 12:07:32 +0000 (13:07 +0100)
committerGiulio Fidente <gfidente@redhat.com>
Tue, 15 Dec 2015 11:44:19 +0000 (12:44 +0100)
commit22b4acf454d74302f1cca03f7fe22f63619b1f70
tree7f57b0c197d64543606de5b5b9cb0b3673db9fde
parent3e8010dc8506755f193d6e0f84006452b4eaeee5
Allow for usage of pre-allocated IPs for the controller nodes

This change adds a new *_from_pool.yaml meant to return an IP from
a list instead of allocating a Neutron port, useful to pick an IP
from a pre-defined list and making it possible to configure, for
example an external balancer in advance (or dns), with the future
IPs of the controller nodes.

The list of IPs is provided via parameter_defaults (in the
ControllerIPs struct) using ControllerIPs param.

Also some additional VipPort types are created for the *VirtualIP
resources. The VIPs were previously created using the same port
resource used by the nodes, but when deploying with an external
balancer we want the VIP resource to be nooped instead.

Change-Id: Id3d4f12235501ae77200430a2dc022f378dce336
20 files changed:
environments/external-loadbalancer-vip.yaml
environments/network-isolation.yaml
network/ports/ctlplane_vip.yaml
network/ports/external.yaml
network/ports/external_from_pool.yaml [new file with mode: 0644]
network/ports/from_service.yaml [new file with mode: 0644]
network/ports/internal_api.yaml
network/ports/internal_api_from_pool.yaml [new file with mode: 0644]
network/ports/net_vip_map_external.yaml
network/ports/noop.yaml
network/ports/storage.yaml
network/ports/storage_from_pool.yaml [new file with mode: 0644]
network/ports/storage_mgmt.yaml
network/ports/storage_mgmt_from_pool.yaml [new file with mode: 0644]
network/ports/tenant.yaml
network/ports/tenant_from_pool.yaml [new file with mode: 0644]
network/ports/vip.yaml
overcloud-resource-registry-puppet.yaml
overcloud.yaml
puppet/controller.yaml