tripleo-heat-templates/puppet/services/neutron-plugin-ml2-cisco-vts.yaml
Tim Rozet df31016a9a Fixes certificate generation error for Neutron agents
TLS certificates were introduced for the Neutron Base service in order
for Neutron to securely communicate with OVS via SSL/TLS.  However, the
implementation only required Neutron DHCP agent (ODL deployment) to use
the certificates.  The other OVS agents are not used in ODL deployments
and SSL/TLS use there may be added in the future.  However, since other
services inherit NeutronBase config_settings, they will attempt to
generate certs.  This certificate generation will fail because these
services do not inherit metadata settings.

This patch fixes the above issue by adding the metadata settings
inheritance to every service derived from NeutronBase.

Closes-Bug: 1754363

Change-Id: I87afc3a11efeefc1cfd768dfe817fbb3b2422694
Signed-off-by: Tim Rozet <trozet@redhat.com>
2018-03-08 11:05:33 -05:00

90 lines
2.6 KiB
YAML

heat_template_version: queens
description: >
VTS Controller Settings for the Cisco VTS Neutron ML2 Plugin.
parameters:
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: ''
VTSPort:
description: Port of the VTS Server
type: number
default: 8888
VTSTimeout:
description: Timeout for VTS server
type: number
default: 120
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. This
mapping overrides those in ServiceNetMapDefaults.
type: json
DefaultPasswords:
default: {}
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
DefaultPasswords:
default: {}
type: json
resources:
NeutronMl2Base:
type: ./neutron-plugin-ml2.yaml
properties:
ServiceData: {get_param: ServiceData}
ServiceNetMap: {get_param: ServiceNetMap}
DefaultPasswords: {get_param: DefaultPasswords}
EndpointMap: {get_param: EndpointMap}
RoleName: {get_param: RoleName}
RoleParameters: {get_param: RoleParameters}
outputs:
role_data:
description: Role data for the VTS ML2 Plugin.
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}
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}
step_config: |
include ::tripleo::profile::base::neutron::plugins::ml2
metadata_settings:
get_attr: [NeutronMl2Base, role_data, metadata_settings]