tripleo-heat-templates/deployment/neutron/neutron-plugin-ml2-cisco-vts-container-puppet.yaml
Alex Schultz ebab335f38 Role specific container support
We may want to be able to specific different containers at a role level.
This requires switching the container image parameters to be role
specific too allow for role based overrides.

Change-Id: I4090e889a32abd51e7c11139737a7a18e27d18e7
2022-01-21 14:18:02 -07:00

111 lines
3.4 KiB
YAML

heat_template_version: wallaby
description: >
VTS Controller Settings for Neutron ML2 Plugin (Docker)
parameters:
EndpointMap:
default: {}
description: Mapping of service endpoint -> protocol. Typically set
via parameter_defaults in the resource registry.
type: json
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
ContainerNeutronConfigImage:
description: The container image to use for the neutron config_volume
type: string
tags:
- role_specific
RoleName:
default: ''
description: Role name on which the service is applied
type: string
RoleParameters:
default: {}
description: Parameters specific to the role
type: json
VTSUsername:
description: The username for the VTS server.
type: string
VTSPassword:
type: string
description: The password for the VTS server.
hidden: true
VTSServer:
description: VTS Server IP address
type: string
VTSVMMID:
description: VMM ID used on VTS
type: string
default: ''
VTSSiteId:
description: VTS Site Id of the controller
type: string
default: ''
VTSPort:
description: Port of the VTS Server
type: number
default: 8888
VTSTimeout:
description: Timeout for VTS server
type: number
default: 120
resources:
NeutronMl2Base:
type: ./neutron-plugin-ml2.yaml
properties:
EndpointMap: {get_param: EndpointMap}
ServiceData: {get_param: ServiceData}
ServiceNetMap: {get_param: ServiceNetMap}
RoleName: {get_param: RoleName}
RoleParameters: {get_param: RoleParameters}
RoleParametersValue:
type: OS::Heat::Value
properties:
type: json
value:
map_replace:
- map_replace:
- ContainerNeutronConfigImage: ContainerNeutronConfigImage
- values: {get_param: [RoleParameters]}
- values:
ContainerNeutronConfigImage: {get_param: ContainerNeutronConfigImage}
outputs:
role_data:
description: Role data for the Neutron ML2 Cisco VTS Plugin role.
value:
service_name: neutron_plugin_ml2_cisco_vts
config_settings:
map_merge:
- get_attr: [NeutronMl2Base, role_data, config_settings]
- vts::vts_ip: {get_param: VTSServer}
vts::vts_port: {get_param: VTSPort}
vts::vts_siteid: {get_param: VTSSiteId}
neutron::plugins::ml2::cisco::vts::vts_username: {get_param: VTSUsername}
neutron::plugins::ml2::cisco::vts::vts_password: {get_param: VTSPassword}
neutron::plugins::ml2::cisco::vts::vts_vmmid: {get_param: VTSVMMID}
neutron::plugins::ml2::cisco::vts::vts_timeout: {get_param: VTSTimeout}
service_config_settings: {}
metadata_settings:
get_attr: [NeutronMl2Base, role_data, metadata_settings]
# BEGIN DOCKER SETTINGS
puppet_config:
config_volume: 'neutron'
puppet_tags: neutron_plugin_ml2
step_config: |
include tripleo::profile::base::neutron::plugins::ml2
config_image: {get_attr: [RoleParametersValue, value, ContainerNeutronConfigImage]}
kolla_config: {}
docker_config: {}