tripleo-heat-templates/deployed-server/deployed-server-environment-output.yaml
James Slagle d90d57a8c3 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
2017-07-18 20:01:06 -04:00

56 lines
1.4 KiB
YAML

heat_template_version: pike
parameters:
RoleCounts:
type: json
default: {}
VipMap:
type: json
default: {}
DeployedServerPortMap:
type: json
default: {}
DeployedServerDeploymentSwiftDataMap:
type: json
default: {}
DefaultRouteIp:
type: string
default: 192.168.24.1
resources:
DeployedServerPortMapParameter:
type: OS::Heat::Value
properties:
type: json
value:
DeployedServerPortMap:
map_merge:
- {get_param: DeployedServerPortMap}
- control_virtual_ip:
fixed_ips:
- ip_address: {get_param: [VipMap, ctlplane]}
- redis_virtual_ip:
fixed_ips:
- ip_address: {get_param: [VipMap, redis]}
DeployedServerEnvironment:
type: OS::Heat::Value
properties:
type: json
value:
parameter_defaults:
map_merge:
- {get_attr: [DeployedServerPortMapParameter, value]}
- DeploymentSwiftDataMap: {get_param: DeployedServerDeploymentSwiftDataMap}
- EC2MetadataIp: {get_param: DefaultRouteIp}
- ControlPlaneDefaultRoute: {get_param: DefaultRouteIp}
- {get_param: RoleCounts}
outputs:
deployed_server_environment:
description:
Environment data that can be used as input into the services stack when
using split-stack.
value: {get_attr: [DeployedServerEnvironment, value]}