Add deployed-server backwards compatible template
authorJames Slagle <jslagle@redhat.com>
Mon, 9 Jan 2017 19:40:27 +0000 (14:40 -0500)
committerJames Slagle <jslagle@redhat.com>
Tue, 10 Jan 2017 18:04:52 +0000 (13:04 -0500)
commit6f20304c43bd010f656e9000f098d1d5d02cdc78
tree4a8562a048561fc283553e7ade5e8bcb7550daf6
parentc9596b72a1efd9733361081029f2dc0e194d0b6d
Add deployed-server backwards compatible template

In Newton, the ctlplane port on deployed-server was called
<hostname>-ctlplane-port. When this code was refactored in
I29fbc720c3d582cbb94385e65e4b64b101f7eac9, the -port suffix was dropped
in favor of <hostname>-<network> convention, and the port resource was
created directly in deployed-server.yaml instead of in a nested stack.

Both of those changes were backwards incompatible -- making it
impossible to upgrade to the new version of deployed-server.yaml without
the ctlplane port getting deleted/recreated, which causes a change in IP
address. The IP address change causes services to be misconfigured on
upgrade attempts.

Change-Id: I45991b60a151abf3c5e4d05a3aa7246b2d25ac5a
deployed-server/ctlplane-port.yaml [new file with mode: 0644]
deployed-server/deployed-server.yaml
environments/updates/README.md
environments/updates/update-from-deployed-server-newton.yaml [new file with mode: 0644]