Excerpts from Clark Boylan's message of 2018-09-12 10:44:55 -0700: > On Wed, Sep 12, 2018, at 10:23 AM, Jim Rollenhagen wrote: > > The process of operators upgrading Python versions across their fleet came > > up this morning. It's fairly obvious that operators will want to do this in > > a rolling fashion. > > > > Has anyone considered doing this in CI? For example, running multinode > > grenade with python 2 on one node and python 3 on the other node. > > > > Should we (openstack) test this situation, or even care? > > > > This came up in a Vancouver summit session (the python3 one I think). General > consensus there seemed to be that we should have grenade jobs that run > python2 on the old side and python3 on the new side and test the update from > one to another through a release that way. Additionally there was thought > that the nova partial job (and similar grenade jobs) could hold the non > upgraded node on python2 and that would talk to a python3 control plane. > > I haven't seen or heard of anyone working on this yet though. > > Clark >
IIRC, we also talked about not supporting multiple versions of python on a given node, so all of the services on a node would need to be upgraded together. Doug __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
