Ansible role to deploy qpid dispatch router
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Zuul 9202684117 Merge "Prepare reno for stable/rocky" 1 month ago
defaults Create sasl user in func test 6 months ago
doc docs: drop sphinxmark 2 months ago
handlers Initial commit 1 year ago
meta Create sasl user in func test 6 months ago
releasenotes/source Prepare reno for stable/rocky 9 months ago
tasks Create sasl user in func test 6 months ago
templates Create sasl user in func test 6 months ago
tests Merge "Trivial: Fix the pep8 warning" 1 month ago
vars Create sasl user in func test 6 months ago
zuul.d Create sasl user in func test 6 months ago
.gitignore Role requirements and tests 1 year ago
.gitreview OpenDev Migration Patch 2 months ago
LICENSE Initial commit 1 year ago
README.rst Role requirements and tests 1 year ago
Vagrantfile Role requirements and tests 1 year ago
bindep.txt Role requirements and tests 1 year ago
run_tests.sh Role requirements and tests 1 year ago
setup.cfg Introduce base Zuul jobs 11 months ago
setup.py Role requirements and tests 1 year ago
tox.ini fix tox python3 overrides 8 months ago

README.rst

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

BSD

Author Information

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