summaryrefslogtreecommitdiffstats
path: root/environments/external-loadbalancer-vip.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-04-10Replace references to the 192.0.2 networkGiulio Fidente1-1/+1
Following change I1393d65ffb20b1396ff068def237418958ed3289 the ctlplane network will be 192.168.24 by default and not 192.0.2 anymore. This change removes old references left to 192.0.2 network from the overcloud templates. Change-Id: I1986721d339887741038b6cd050a46171a4d8022
2016-11-21Modify external loadbalancer environments to use new FixedIPsDan Sneddon1-13/+6
This change modifes the environment files external_loadbalancer_vip.yaml and external_loadbalancer_vip_v6.yaml to take advantage of the new mechanism for setting FixedIPs for each VIP. The previous mechanism was used to set the VIP addresses directly, but each VIP now contains a FixedIPs parameter which sets the IP for the VIP when it is created. The advantage of the new mechanism is that we no longer have to set each VIP to noop.yaml in the resource registry, since vip.yaml can now handle both automatic and fixed IP selection. Change-Id: I6e66ea6041fe7357c01b8f79f04e2533579206dc
2016-03-18Comment out the ManagementPort in external-loadbalancer-vip.yamlMarius Cornea1-3/+4
The Management network is optional and disabled by default. This change preserves backward compatibility and fixes https://bugzilla.redhat.com/show_bug.cgi?id=1317594 Change-Id: I73cf51154c9ee7c05938e2cadf0c5ac107840bad
2016-03-04Allow for usage of pre-allocated IPs for the management networkSteven Hardy1-0/+3
Id3d4f12235501ae77200430a2dc022f378dce336 added support for pre-allocated IPs on the other overlay networks, but because the patch adding the managment network (I0813a13f60a4f797be04b34258a2cffa9ea7e84f) was under review around the same time, we missed adding the from_pool capability to the ManagementNetwork. Change-Id: If99f37634d5da7e7fb7cfc31232e926bd5ff074a
2015-12-15Allow for usage of pre-allocated IPs for the controller nodesGiulio Fidente1-6/+29
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
2015-11-24Make load balancer deployment optional via template paramGiulio Fidente1-0/+1
Adds control over the load balancer deployment via template param. Change-Id: I5625083ff323a87712a5fd3f9a64dd66d2838468
2015-11-24Add net_vip_map_external to be used for an external balancerDan Prince1-0/+13
Changes VipMap into a new NetVipMap resource which defaults to being the same as the 'old' VipMap. An environment file can be used to map NetVipMap instead to the net_vip_map_external.yaml which allows for passing in explicit Virtual IP addresses. It also ensures that references to the Virtual IPs are gathered from the VipMap resource and allows for an empty ControlPlaneIP parameter in the neutron port templates where it can be. Co-Authored-By: Giulio Fidente <gfidente@redhat.com> Change-Id: Ifad32e18f12b9997e3f89e4afe3ebc4c30e14a86