The purpose of this spec is to add support for the OpenStack Zaqar program to OpenStack-Ansible. This would allow the deployment of Zaqar along with the core OpenStack components using OpenStack-Ansible.
Blueprint - Zaqar deployment on OpenStack-Ansible:
Presently, while deploying OpenStack using OpenStack-Ansible only the core OpenStack components get deployed. The deployment of other components (eg: Zaqar) on playbooks is not supported yet and to use other component’s services, they need to be deployed manually.
The Zaqar program encompasses a number of projects, but this spec and this proposed series of changes covers the initial implementation of support for Zaqar. This will involve adding support for the Zaqar server and Zaqar client.
The proposed changes include:
Test playbooks will be placed in the openstack-ansible-zaqar repository for functional testing purposes, with no initially proposed changes to OpenStack-Ansible playbooks.
In the future, once the Zaqar role is found to be useful and acceptable, a future spec will address the integration of the Zaqar role with the main OpenStack-Ansible repository.
Deployers will be able to deploy Zaqar and use messaging service through OpenStack-Ansible.
When support for the new Zaqar role is added to the parent repository, new Zaqar specific configuration options will be made available. This will provide an optional role for use in the OpenStack-Ansible toolbox for the deployers.
As this change is self-contained initially, no impact on other developers is expected.
The usual gate checks can be used for these changes. Also, each individual commit can be functionally tested individually.
Adding support to the user guide on how to enable Zaqar support will be required.