tripleo-heat-templates/deployment/neutron/neutron-bgpvpn-api-container-puppet.yaml
ramishra b253d564f7 Use server side env merging for ServiceNetMap/VipSubnetMap
This simplifies the ServiceNetMap/VipSubnetMap interfaces
to use parameter merge strategy and removes the *Defaults
interfaces.

Change-Id: Ic73628a596e9051b5c02435b712643f9ef7425e3
2021-05-19 10:16:58 +05:30

58 lines
1.8 KiB
YAML

heat_template_version: wallaby
description: >
BGPVPN API service configured with Puppet
parameters:
ServiceData:
default: {}
description: Dictionary packing service data
type: json
ServiceNetMap:
default: {}
description: Mapping of service_name -> network name. Typically set
via parameter_defaults in the resource registry. Use
parameter_merge_strategies to merge it with the defaults.
type: json
RoleName:
default: ''
description: Role name on which the service is applied
type: string
RoleParameters:
default: {}
description: Parameters specific to the role
type: json
EndpointMap:
default: {}
description: Mapping of service endpoint -> protocol. Typically set
via parameter_defaults in the resource registry.
type: json
ContainerNeutronConfigImage:
description: The container image to use for the neutron config_volume
type: string
BgpvpnServiceProvider:
default: 'BGPVPN:Dummy:networking_bgpvpn.neutron.services.service_drivers.driver_api.BGPVPNDriver:default'
description: Backend to use as a service provider for BGPVPN
type: string
resources:
ContainersCommon:
type: ../containers-common.yaml
outputs:
role_data:
description: Role data for the BGPVPN role.
value:
service_name: neutron_bgpvpn_api
config_settings:
neutron::services::bgpvpn::service_providers: {get_param: BgpvpnServiceProvider}
# BEGIN DOCKER SETTING
puppet_config:
config_volume: 'neutron'
puppet_tags: neutron_bgpvpn_service_config
step_config: |
include tripleo::profile::base::neutron::bgpvpn
config_image: {get_param: ContainerNeutronConfigImage}
kolla_config: {}
docker_config: {}