tripleo-heat-templates/puppet/services/veritas-hyperscale-controller.yaml
Carlos Camacho 44ef2a3ec1 Change template names to rocky
The new master branch should point now to rocky.

So, HOT templates should specify that they might contain features
for rocky release [1]

Also, this submission updates the yaml validation to use only latest
heat_version alias. There are cases in which we will need to set
the version for specific templates i.e. mixed versions, so there
is added a variable to assign specific templates to specific heat_version
aliases, avoiding the introductions of error by bulk replacing the
the old version in new releases.

[1]: https://docs.openstack.org/heat/latest/template_guide/hot_spec.html#rocky
Change-Id: Ib17526d9cc453516d99d4659ee5fa51a5aa7fb4b
2018-05-09 08:28:42 +02:00

107 lines
3.6 KiB
YAML

# Copyright (c) 2017 Veritas Technologies LLC.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
heat_template_version: rocky
description: >
Openstack Veritas HyperScale backend
parameters:
VrtsRabbitPassword:
type: string
description: The Rabbitmq password of the hyperscale user. Mandatory.
VrtsKeystonePassword:
type: string
description: The Keystone password of the hyperscale service. Mandatory.
VrtsMysqlPassword:
type: string
description: The MySQL password of the hyperscale user. Mandatory.
VrtsCtrlMgmtIP:
type: string
default: ''
description: The management IP of HyperScale. The value will be inferred
from the rest of the deployment settings if left blank.
VrtsDashboardIP:
type: string
default: ''
description: The dashboard IP of HyperScale. The value will be inferred
from the rest of the deployment settings if left blank.
VrtsZookeeperIP:
type: string
description: The IP of a node where Zookeeper is configured. Mandatory.
VrtsSSHPassword:
type: string
description: The SSH password of the hyperscale user. Mandatory.
VrtsConfigParam1:
type: string
default: ''
description: Additional config parameter. Optional.
VrtsConfigParam2:
type: string
default: ''
description: Additional config parameter. Optional.
VrtsConfigParam3:
type: string
default: ''
description: Additional config parameter. Optional.
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: {}
type: json
description: Mapping of service endpoint -> protocol. Typically set
via parameter_defaults in the resource registry.
outputs:
role_data:
description: Install Veritas HyperScale packages for controller.
value:
service_name: veritas_hyperscale_controller
config_settings:
global_config_settings:
vrts_ctrl_mgmt_ip: {get_param: VrtsCtrlMgmtIP}
vrts_dashboard_ip: {get_param: VrtsDashboardIP}
vrts_zookeeper_ip: {get_param: VrtsZookeeperIP}
vrts_ssh_passwd: {get_param: VrtsSSHPassword}
vrts_config_param1: {get_param: VrtsConfigParam1}
vrts_config_param2: {get_param: VrtsConfigParam2}
vrts_config_param3: {get_param: VrtsConfigParam3}
step_config: |
include ::veritas_hyperscale::controller_pkg_inst
service_config_settings:
rabbitmq:
vrts_rabbitmq_passwd: {get_param: VrtsRabbitPassword}
keystone:
vrts_keystone_passwd: {get_param: VrtsKeystonePassword}
mysql:
vrts_mysql_passwd: {get_param: VrtsMysqlPassword}