History

Michele Baldessari 00ea9d5623 Fix TLS resource_registry key error Via I1bfdb6d064f3b10b269dedafd36ca367139fe1df we moved to using environments/ssl/enable-tls.yaml. The problem is that the code in roles/overcloud-ssl/library/tls_tht.py assumes that the parsed yaml file already has the 'resource_registry' key in the dictionary. That was true with environments/enable-tls.yaml but is not true any longer for environments/ssl/enable-tls.yaml. Since Iaf7386207e5bd8b336759f51e4405fe15114123a in rocky NodeTLSData is not used anymore, so let's just skip the whole assignment starting with rocky. Closes-Bug: #1796626 Depends-On: Ibee6ba188585f80f0f7d136c81146096cb4432c2 Change-Id: I53851edbb8bb562dc4194fb99d6ade259227d2f9		2018-10-11 16:25:09 +00:00
..
defaults	derive overcloud_public_ip	2017-03-03 23:56:04 -05:00
library	Fix TLS resource_registry key error	2018-10-11 16:25:09 +00:00
meta	Integrate undercloud_user var into oooq-extras	2017-01-18 09:32:16 -05:00
tasks	Make overcloud trust undercloud CA if undercloud has TLS	2017-11-13 08:33:42 +00:00
templates	Fix used paths to match custom working dir	2018-09-20 07:50:33 +00:00
tests	Cleanup and move files for overcloud-ssl	2016-11-21 11:50:16 +01:00
README.md	Cleanup and move files for overcloud-ssl	2016-11-21 11:50:16 +01:00

README.md

Role Name

A brief description of the role goes here.

Requirements

Any pre-requisites that may not be covered by Ansible itself or the role should be mentioned here. For instance, if the role uses the EC2 module, it may be a good idea to mention in this section that the boto package is required.

Role Variables

A description of the settable variables for this role should go here, including any variables that are in defaults/main.yml, vars/main.yml, and any variables that can/should be set via parameters to the role. Any variables that are read from other roles and/or the global scope (ie. hostvars, group vars, etc.) should be mentioned here as well.

Dependencies

A list of other roles hosted on Galaxy should go here, plus any details in regards to parameters that may need to be set for other roles, or variables that are used from other roles.

Example Playbook

Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:

- hosts: servers
  roles:
     - { role: username.rolename, x: 42 }

License

Apache 2.0

Author Information

An optional section for the role authors to include contact information, or a website (HTML is not allowed).