Make RoleParameters and key_name descriptions consistent
authorBen Nemec <bnemec@redhat.com>
Tue, 27 Jun 2017 16:07:52 +0000 (11:07 -0500)
committerBen Nemec <bnemec@redhat.com>
Wed, 2 Aug 2017 21:18:25 +0000 (16:18 -0500)
commit4502b7cba6b86cfb041459dbcebe77219236ecaf
tree40ebdf51c2e82b8368920f60c00a6efa7d10003f
parent303a5be4916ece351e4eaeeb5b4dae44a5e6f490
Make RoleParameters and key_name descriptions consistent

The key_name default is ignored because the parameter is used in
some mutually exclusive environments where the default doesn't
need to be the same.

Change-Id: I77c1a1159fae38d03b0e59b80ae6bee491d734d7
Partial-Bug: 1700664
12 files changed:
common/services.yaml
deployed-server/deployed-server.yaml
extraconfig/pre_network/contrail/compute_pre_network.yaml
extraconfig/pre_network/contrail/contrail_dpdk_pre_network.yaml
extraconfig/pre_network/host_config_and_reboot.yaml
puppet/blockstorage-role.yaml
puppet/cephstorage-role.yaml
puppet/compute-role.yaml
puppet/controller-role.yaml
puppet/objectstorage-role.yaml
puppet/role.role.j2.yaml
tools/yaml-validate.py