wrong paths in deployed-server-environment-output.yaml

[James Slagle]

deployed-server/deployed-server-environment-output.yaml contained two paths to environment files in the generated resource_registry that were incorrect relative paths:

  OS::TripleO::DeployedServer::ControlPlanePort: tripleo-heat-templates/deployed-server/deployed-neutron-port.yaml
  OS::TripleO::Network::Ports::ControlPlaneVipPort: tripleo-heat-templates/deployed-server/deployed-neutron-port.yaml

Those values won't work unless "tripleo-heat-templates" exists in the current dir, which we can't rely on. We don't have access to the templates paths within the templates themselves.

We will need to just use a static environment for these mappings.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/484985

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/484985
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=d90d57a8c35e066a68a433cac108675dfab1d9e0
Submitter: Jenkins
Branch: master

commit d90d57a8c35e066a68a433cac108675dfab1d9e0
Author: James Slagle <email address hidden>
Date: Tue Jul 18 20:01:06 2017 -0400

    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

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 7.0.0.0b3 development milestone.