auto switch of glance-api containers to other controllers
Hello All, I understand that glance-api container run only one controller always. I have tried to check if the glance-api container to switch over to the next available controller by means of rebooting and stopping the containers, but nothing happened. Is there a way to make sure that glance-api container switches to other controllers if controller 1 is not available. Thanks for you help Regards Pradeep
Hi, I'm not sure if you used any deployment tool for your environment, but usually for such failover there's a load balancer in conjunction with VRRP or Anycast, that able to detect when controller1 is down and forward traffic to another controller. As example, OpenStack-Ansible as default option installs haproxy to each controller and keepalived to implement VRRP and Virtual IPs. So when glance is down on controller1, haproxy will detect that and forward traffic to other controllers. If controller1 is down as a whole, keepalived will detect that and raise VIP on controller2, so all client traffic will go there. Since controller2 also have haproxy, it will pass traffic to available backends based on the source IP. пт, 9 дек. 2022 г., 09:06 pradeep <pradeep8985@gmail.com>:
Hello All,
I understand that glance-api container run only one controller always. I have tried to check if the glance-api container to switch over to the next available controller by means of rebooting and stopping the containers, but nothing happened. Is there a way to make sure that glance-api container switches to other controllers if controller 1 is not available.
Thanks for you help
Regards Pradeep
Hi Dmitriy, Thanks for the response. Sorry, I forgot to mention that i used kolla ansible for deployment. As per kolla docs, glance-api container runs only in one controller. So i am looking from kolla perspective if it can automatically switch it over other available controllers. Regards Pradeep On Fri, 9 Dec 2022 at 14:51, Dmitriy Rabotyagov <noonedeadpunk@gmail.com> wrote:
Hi,
I'm not sure if you used any deployment tool for your environment, but usually for such failover there's a load balancer in conjunction with VRRP or Anycast, that able to detect when controller1 is down and forward traffic to another controller.
As example, OpenStack-Ansible as default option installs haproxy to each controller and keepalived to implement VRRP and Virtual IPs. So when glance is down on controller1, haproxy will detect that and forward traffic to other controllers. If controller1 is down as a whole, keepalived will detect that and raise VIP on controller2, so all client traffic will go there. Since controller2 also have haproxy, it will pass traffic to available backends based on the source IP.
пт, 9 дек. 2022 г., 09:06 pradeep <pradeep8985@gmail.com>:
Hello All,
I understand that glance-api container run only one controller always. I have tried to check if the glance-api container to switch over to the next available controller by means of rebooting and stopping the containers, but nothing happened. Is there a way to make sure that glance-api container switches to other controllers if controller 1 is not available.
Thanks for you help
Regards Pradeep
-- ----------------------- Regards Pradeep Kumar
Any help is highly appreciated. Thank you! On Fri, 9 Dec 2022 at 21:46, pradeep <pradeep8985@gmail.com> wrote:
Hi Dmitriy, Thanks for the response. Sorry, I forgot to mention that i used kolla ansible for deployment. As per kolla docs, glance-api container runs only in one controller. So i am looking from kolla perspective if it can automatically switch it over other available controllers.
Regards Pradeep
On Fri, 9 Dec 2022 at 14:51, Dmitriy Rabotyagov <noonedeadpunk@gmail.com> wrote:
Hi,
I'm not sure if you used any deployment tool for your environment, but usually for such failover there's a load balancer in conjunction with VRRP or Anycast, that able to detect when controller1 is down and forward traffic to another controller.
As example, OpenStack-Ansible as default option installs haproxy to each controller and keepalived to implement VRRP and Virtual IPs. So when glance is down on controller1, haproxy will detect that and forward traffic to other controllers. If controller1 is down as a whole, keepalived will detect that and raise VIP on controller2, so all client traffic will go there. Since controller2 also have haproxy, it will pass traffic to available backends based on the source IP.
пт, 9 дек. 2022 г., 09:06 pradeep <pradeep8985@gmail.com>:
Hello All,
I understand that glance-api container run only one controller always. I have tried to check if the glance-api container to switch over to the next available controller by means of rebooting and stopping the containers, but nothing happened. Is there a way to make sure that glance-api container switches to other controllers if controller 1 is not available.
Thanks for you help
Regards Pradeep
-- ----------------------- Regards Pradeep Kumar
-- ----------------------- Regards Pradeep Kumar
Kolla only uses a single controller if you use file based backend by default. If you want to continue using the file backend, you can use something like an NFS share to share images between controllers and then change the glance_file_datadir_volume parameter which will result in the api being deployed on all controllers ________________________________ From: pradeep <pradeep8985@gmail.com> Sent: 12 December 2022 04:53 To: Dmitriy Rabotyagov <noonedeadpunk@gmail.com> Cc: openstack-discuss <openstack-discuss@lists.openstack.org> Subject: Re: auto switch of glance-api containers to other controllers CAUTION: This email originates from outside THG ________________________________ Any help is highly appreciated. Thank you! On Fri, 9 Dec 2022 at 21:46, pradeep <pradeep8985@gmail.com<mailto:pradeep8985@gmail.com>> wrote: Hi Dmitriy, Thanks for the response. Sorry, I forgot to mention that i used kolla ansible for deployment. As per kolla docs, glance-api container runs only in one controller. So i am looking from kolla perspective if it can automatically switch it over other available controllers. Regards Pradeep On Fri, 9 Dec 2022 at 14:51, Dmitriy Rabotyagov <noonedeadpunk@gmail.com<mailto:noonedeadpunk@gmail.com>> wrote: Hi, I'm not sure if you used any deployment tool for your environment, but usually for such failover there's a load balancer in conjunction with VRRP or Anycast, that able to detect when controller1 is down and forward traffic to another controller. As example, OpenStack-Ansible as default option installs haproxy to each controller and keepalived to implement VRRP and Virtual IPs. So when glance is down on controller1, haproxy will detect that and forward traffic to other controllers. If controller1 is down as a whole, keepalived will detect that and raise VIP on controller2, so all client traffic will go there. Since controller2 also have haproxy, it will pass traffic to available backends based on the source IP. пт, 9 дек. 2022 г., 09:06 pradeep <pradeep8985@gmail.com<mailto:pradeep8985@gmail.com>>: Hello All, I understand that glance-api container run only one controller always. I have tried to check if the glance-api container to switch over to the next available controller by means of rebooting and stopping the containers, but nothing happened. Is there a way to make sure that glance-api container switches to other controllers if controller 1 is not available. Thanks for you help Regards Pradeep -- ----------------------- Regards Pradeep Kumar -- ----------------------- Regards Pradeep Kumar Danny Webb Principal OpenStack Engineer Danny.Webb@thehutgroup.com [THG Ingenuity Logo] www.thg.com<https://www.thg.com> [https://i.imgur.com/wbpVRW6.png]<https://www.linkedin.com/company/thg-ingenuity/?originalSubdomain=uk> [https://i.imgur.com/c3040tr.png] <https://twitter.com/thgingenuity?lang=en> Danny Webb Principal OpenStack Engineer The Hut Group<http://www.thehutgroup.com/> Tel: Email: Danny.Webb@thehutgroup.com<mailto:Danny.Webb@thehutgroup.com> For the purposes of this email, the "company" means The Hut Group Limited, a company registered in England and Wales (company number 6539496) whose registered office is at Fifth Floor, Voyager House, Chicago Avenue, Manchester Airport, M90 3DQ and/or any of its respective subsidiaries. Confidentiality Notice This e-mail is confidential and intended for the use of the named recipient only. If you are not the intended recipient please notify us by telephone immediately on +44(0)1606 811888 or return it to us by e-mail. Please then delete it from your system and note that any use, dissemination, forwarding, printing or copying is strictly prohibited. Any views or opinions are solely those of the author and do not necessarily represent those of the company. Encryptions and Viruses Please note that this e-mail and any attachments have not been encrypted. They may therefore be liable to be compromised. Please also note that it is your responsibility to scan this e-mail and any attachments for viruses. We do not, to the extent permitted by law, accept any liability (whether in contract, negligence or otherwise) for any virus infection and/or external compromise of security and/or confidentiality in relation to transmissions sent by e-mail. Monitoring Activity and use of the company's systems is monitored to secure its effective use and operation and for other lawful business purposes. Communications using these systems will also be monitored and may be recorded to secure effective use and operation and for other lawful business purposes. hgvyjuv
participants (3)
-
Danny Webb
-
Dmitriy Rabotyagov
-
pradeep