Remove mention of haproxy-endpoints role

Code Issues Proposed changes

Keystone 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: I3693ee3a9a756161324e3a79464f9650fb7a9f1a

This commit is contained in:

Dmitriy Rabotyagov

2022年06月14日 19:41:53 +02:00

parent cf66cd365c

commit 604085ffe6

6 changed files with 0 additions and 23 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

13
doc/source/index.rst

View File

@@ -35,19 +35,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

~~~~

Remove mention of haproxy-endpoints role

13 doc/source/index.rst Unescape Escape View File

13
doc/source/index.rst

View File