Use static environment for deployed-server neutron mappings
authorJames Slagle <jslagle@redhat.com>
Wed, 19 Jul 2017 00:01:06 +0000 (20:01 -0400)
committerJames Slagle <jslagle@redhat.com>
Wed, 19 Jul 2017 00:01:06 +0000 (20:01 -0400)
commitd90d57a8c35e066a68a433cac108675dfab1d9e0
tree6a02e81c8cc1b420c7b49c22f1e6857fb3a088d1
parent7e4f7dd2b0324247bba8fd8da5f3becd20e8299f
Use static environment for deployed-server neutron mappings

We can't include these mappings for the deployed-server neutron ports
when using split-stack in the generated environment file because the
path to the actual templates directory is not known from with the
templates themselves.

This patch removes the mappings from the generated environment from the
stack output and adds a static environment file with relative paths that
will have to be included on the deploy command cli instead.

Change-Id: Id4b8c939fa7b26205609819b66e76bf73c9890d0
Closes-Bug: #1705144
deployed-server/deployed-server-environment-output.yaml
environments/deployed-server-deployed-neutron-ports.yaml [new file with mode: 0644]