d0702e82b5
With parameter tags, it is possible to categorize the parameters. In this patch, all role-specific parameters of the services are categorized as role_specific, which will help in adding validation during the deployment (to ensure the provided role-specific parameter is actually implemented as role-specific). This patch adds only the tags, and the validation will done via workflows. Change-Id: Ic053111298e7872a3a3cd11e6249dbd85707cc29
53 lines
1.4 KiB
YAML
53 lines
1.4 KiB
YAML
heat_template_version: queens
|
|
|
|
description: >
|
|
Configure tuned
|
|
|
|
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. This
|
|
mapping overrides those in ServiceNetMapDefaults.
|
|
type: json
|
|
DefaultPasswords:
|
|
default: {}
|
|
type: json
|
|
EndpointMap:
|
|
default: {}
|
|
description: Mapping of service endpoint -> protocol. Typically set
|
|
via parameter_defaults in the resource registry.
|
|
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
|
|
TunedProfileName:
|
|
default: ''
|
|
description: Tuned Profile to apply to the host
|
|
type: string
|
|
tags:
|
|
- role_specific
|
|
|
|
outputs:
|
|
role_data:
|
|
description: Role data for tuned
|
|
value:
|
|
service_name: tuned
|
|
config_settings:
|
|
map_replace:
|
|
- map_replace:
|
|
- tripleo::profile::base::tuned::profile: TunedProfileName
|
|
- values: {get_param: RoleParameters}
|
|
- values: {'TunedProfileName': {get_param: TunedProfileName}}
|
|
step_config: |
|
|
include ::tripleo::profile::base::tuned
|