aboutsummaryrefslogtreecommitdiffstats
path: root/overcloud-vlan-port.yaml
AgeCommit message (Collapse)AuthorFilesLines
2014-10-28Don't replace OS::Neutron::Port on updateSteve Hardy1-0/+1
Due to an ununsual interface to OS::Neutron::Port resources, it's necessary to specify replacement_policy: AUTO, or the resource is unconditionally replaced on every stack update. I've started discussion re possibly changing the default in Heat, but right now, we need this or we have the bad outcome of replacing all (!) compute and controller nodes on every stack-update, even if the templates are unmodified. Passing the AUTO value should be safe regardless of any potential change of default value in Heat. Change-Id: I6dd02ae17407f8f4c81ae418e5027f4f38ae4e9b Closes-Bug: #1383709
2014-09-04Fix spelling of controller0_VLANPortJames Polley1-1/+1
Prior to this change, using these templates fails as controller0_VLANPort is defined, but we attempt to use controller0VLANPort instead. Change-Id: Ieb2eece4e7d48177acae0bef916192d8e6a4a4a3
2014-08-28Expose public_interface_tag support.Robert Collins1-0/+38
Proper VLAN support requires adding the IP address to a new device, rather than br-ex/br-ctlplane. This is added in the tripleo-image-elements change https://review.openstack.org/103449 (I3f77f72ac623792e844dbb4d501b6ab269141f8e) and here we just expose it with appropriate glue to get the IP address from Neutron. With this we can now describe a VLAN public interface scenario to the undercloud and overcloud control planes. Change-Id: I4d2194fc813aebb0708d6fddf4f05bae5f091fd8