<div dir="ltr"><div dir="ltr">Thank you for the clarification. <br><div>So I should let the handling of redundancy to keepalive and haproxy instead of using external tools.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 19 Jul 2022 at 15:21, Sean Mooney <<a href="mailto:smooney@redhat.com">smooney@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, 2022-07-19 at 13:51 +0100, A Monster wrote:<br>
> I've deployed openstack xena using *kolla-ansible* on *centos 8 stream*,<br>
> I've used multiple controller nodes, a bunch of compute nodes and a storage<br>
> cluster.<br>
> Controller nodes include network services.<br>
> <br>
> I want to know how can I successfully set up redundancy between these<br>
> controller nodes, in a way that some nodes are active while others are on<br>
> standby state, and would only become active in case when the active nodes<br>
> are to fail.<br>
in generall that is not needed with openstack.<br>
<br>
most service are partly or mostly stateless using the db to store any relevent persitent state.<br>
<br>
that generally menas that for example you can have n nova api process active at any time and<br>
you do not need to use external managment fo the serivce to have some be active and other be passive.<br>
<br>
in general such active/standby configurtation is an antipatter and should not need to be done with openstack.<br>
<br>
in kolla keepalived and haproxe shoudl migrate the contol plane vips and include/exclude donw services automaiticaly.<br>
<br>
if you want to manually take over that function its likely possibel but not how HA is intended to work in general.<br>
<br>
i dont work on kolla anymore so perhapse there perspectiive has change but in generaly i would advocat for active active<br>
ha in preference ot active standby.<br>
> <br>
> Thank you. Regards<br>
<br>
</blockquote></div></div>