[kolla] Updating libvirt container images without VM downtime

Danny Webb Danny.Webb at thehutgroup.com
Wed Jan 5 09:30:06 UTC 2022

If working properly the restart of the libvirtd container is a non-impacting action for running VMs.  The only containers on the hypervisors that have an actual impact on the VMs in the standard setups are the restart of the ovs-vswitchd / ovn-controller / ovsdb containers which result in a small blip of the VM neworks that we've noticed.
From: J-P Methot <jp.methot at planethoster.info>
Sent: 04 January 2022 19:17
To: openstack-discuss <openstack-discuss at lists.openstack.org>
Subject: [kolla] Updating libvirt container images without VM downtime

CAUTION: This email originates from outside THG


I'm looking for validation regarding the way Kolla and containers work
in regard to upgrading the libvirt containers. Essentially, when you
upgrade the libvirt container to a new container image, the container
needs to be restarted, thus creating downtime for the VMs. There is no
way to avoid this downtime, unless you migrate the VMs to another node
and then move them back once the container has restarted, right?

Jean-Philippe Méthot
Senior Openstack system administrator
Administrateur système Openstack sénior
PlanetHoster inc.

Danny Webb
Senior Linux Systems Administrator
The Hut Group<http://www.thehutgroup.com/>

Email: Danny.Webb at thehutgroup.com<mailto:Danny.Webb at 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.

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20220105/8a8dd400/attachment.htm>

More information about the openstack-discuss mailing list