
Based on conversation on an ansible issue[1], I implemented a LB orchestration role[2] similar to the POC here[3]. This will allow external loadbalancer management roles to hook into a universal notify listener "Manage LB" to perform before/ after endpoint management actions when the service is being restarted. [1]: https://github.com/ansible/ansible/issues/27813 [2]: https://github.com/Logan2211/ansible-haproxy-endpoints [3]: https://github.com/Logan2211/tmp-ansible-27813 Change-Id: I7d2f47e94826526e9a5a99d32575f691fb6b30fd
1.6 KiB
OpenStack-Ansible glance role
configure-glance.rst
This role installs the following Systemd services:
- glance-api
- glance-registry
To clone or view the source code for this repository, visit the role repository for os_glance.
Default variables
../../defaults/main.yml
Required variables
None
Example playbook
../../examples/playbook.yml
External Restart Hooks
When the role performs a restart of the service, it will notify an
Ansible handler named Manage LB
, which is a noop within
this role. In the playbook, other roles may be loaded before and after
this role which will implement Ansible handler listeners for
Manage LB
, allowing external roles to manage the load
balancer endpoints responsible for sending traffic to the servers being
restarted by marking them in maintenance or active mode, draining
sessions, etc. For an example implementation, please reference the ansible-haproxy-endpoints
role used by the openstack-ansible project.
Tags
This role supports two tags: glance-install
and
glance-config
. The glance-install
tag can be
used to install and upgrade. The glance-config
tag can be
used to manage configuration.