[Openstack-operators] [openstack-dev] [skip-level-upgrades][fast-forward-upgrades] PTG summary
Arkady.Kanevsky at dell.com
Arkady.Kanevsky at dell.com
Fri Sep 29 20:01:12 UTC 2017
There are some loose ends that Saverio correctly bringing up.
These perfect points to discuss at Forum.
Suggest we start etherpad to collect agenda for it.
From: Lee Yarwood [mailto:lyarwood at redhat.com]
Sent: Friday, September 29, 2017 7:04 AM
To: Saverio Proto <saverio.proto at switch.ch>
Cc: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>; openstack-operators at lists.openstack.org
Subject: Re: [openstack-dev] [Openstack-operators] [skip-level-upgrades][fast-forward-upgrades] PTG summary
On 29-09-17 11:40:21, Saverio Proto wrote:
> sorry I could not make it to the PTG.
> I have an idea that I want to share with the community. I hope this is
> a good place to start the discussion.
> After years of Openstack operations, upgrading releases from Icehouse
> to Newton, the feeling is that the control plane upgrade is doable.
> But it is also a lot of pain to upgrade all the compute nodes. This
> really causes downtime to the VMs that are running.
> I can't always make live migrations, sometimes the VMs are just too
> big or too busy.
> It would be nice to guarantee the ability to run an updated control
> plane with compute nodes up to N-3 Release.
> This way even if we have to upgrade the control plane every 6 months,
> we can keep a longer lifetime for compute nodes. Basically we can
> never upgrade them until we decommission the hardware.
> If there are new features that require updated compute nodes, we can
> always organize our datacenter in availability zones, not scheduling
> new VMs to those compute nodes.
> To my understanding this means having compatibility at least for the
> nova-compute agent and the neutron-agents running on the compute node.
> Is it a very bad idea ?
> Do other people feel like me that upgrading all the compute nodes is
> also a big part of the burden regarding the upgrade ?
Yeah, I don't think the Nova community would ever be able or willing to verify and maintain that level of backward compatibility. Ultimately there's nothing stopping you from upgrading Nova on the computes while also keeping instance running.
You only run into issues with kernel, OVS and QEMU (for n-cpu with
libvirt) etc upgrades that require reboots or instances to be restarted (either hard or via live-migration). If you're unable or just unwilling to take downtime for instances that can't be moved when these components require an update then you have bigger problems IMHO.
Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76
More information about the OpenStack-operators