path: root/releasenotes
diff options
authorJenkins <jenkins@review.openstack.org>2017-04-21 06:01:09 +0000
committerGerrit Code Review <review@openstack.org>2017-04-21 06:01:09 +0000
commit42ed08b6c016e85c3b3026571200e3f81866354b (patch)
tree0499ed2ef49083b82f1b1796c1de49dad2dd6c35 /releasenotes
parent073e43de7d907ec1b3f52c82aa9621d5af196897 (diff)
parentd381054c8e92c8341e243179e2de447cf11242b3 (diff)
Merge "Replace references to the 192.0.2 network" into stable/ocata
Diffstat (limited to 'releasenotes')
1 files changed, 20 insertions, 0 deletions
diff --git a/releasenotes/notes/replace-references-to-old-ctlplane-0df7f2ae8910559c.yaml b/releasenotes/notes/replace-references-to-old-ctlplane-0df7f2ae8910559c.yaml
new file mode 100644
index 0000000..09d3be0
--- /dev/null
+++ b/releasenotes/notes/replace-references-to-old-ctlplane-0df7f2ae8910559c.yaml
@@ -0,0 +1,20 @@
+ - |
+ The default network for the ctlplane changed from to
+ All references to the ctlplane network in the templates
+ have been updated to reflect this change. When upgrading from a previous
+ release, if the default network was used for the ctlplane (,
+ then it is necessary to provide as input, via environment file, the correct
+ setting for all the parameters that previously defaulted to 192.0.2.x and
+ now default to 192.168.24.x; there is an environment file which could be
+ used on upgrade `environments/updates/update-from-192_0_2-subnet.yaml` to
+ cover a simple scenario but it won't be enough for scenarios using an
+ external load balancer, Contrail or Cisto N1KV. Follows a list of params to
+ be provided on upgrade.
+ From contrail-net.yaml: EC2MetadataIp, ControlPlaneDefaultRoute
+ From external-loadbalancer-vip-v6.yaml: ControlFixedIPs
+ From external-loadbalancer-vip.yaml: ControlFixedIPs
+ From network-environment.yaml: EC2MetadataIp, ControlPlaneDefaultRoute
+ From neutron-ml2-cisco-n1kv.yaml: N1000vVSMIP, N1000vMgmtGatewayIP
+ From contrail-vrouter.yaml: ContrailVrouterGateway