Remove mention of haproxy-endpoints role

Role was never migrated to usage of haproxy-endpoints role
and included task was used instead the whole time.
With that to reduce complexity and to have unified approach, all mention
of the role and handler are removed from the code.

Change-Id: Ia04bd0a729100ed3f0bade9185b0703ce903635f
This commit is contained in:
Dmitriy Rabotyagov 2022-06-14 20:01:24 +02:00 committed by Dmitriy Rabotyagov
parent 0db9f1f959
commit 0ea23558e7
3 changed files with 0 additions and 18 deletions

View File

@ -36,19 +36,6 @@ Example playbook
.. literalinclude:: ../../examples/playbook.yml
:language: yaml
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 <https://github.com/Logan2211/ansible-haproxy-endpoints>`_
used by the openstack-ansible project.
Tags
~~~~

View File

@ -42,7 +42,3 @@
listen:
- "Restart manila services"
- "venv changed"
- meta: noop
listen: Manage LB
when: false

View File

@ -34,7 +34,6 @@
when: item.condition | default(True)
with_items: "{{ manila_core_files + manila_rootwrap_files }}"
notify:
- Manage LB
- Restart manila services
- Restart uwsgi services