09:03:24 <jamespage> #startmeeting upgrades_sig
09:03:25 <openstack> Meeting started Mon Apr 15 09:03:24 2019 UTC and is due to finish in 60 minutes.  The chair is jamespage. Information about MeetBot at http://wiki.debian.org/MeetBot.
09:03:26 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
09:03:29 <openstack> The meeting name has been set to 'upgrades_sig'
09:03:50 <jamespage> morning all - I see a few openstack-charmers here for the upgrades-sig meeting - any others?
09:04:35 <jamespage> nope ok this might be a quick one then!
09:04:42 <jamespage> #topic Ops Feedback
09:05:02 <jamespage> objective for this topic is for operators to discuss current pain points
09:05:10 <jamespage> but as we don't have any here..
09:05:18 <jamespage> #topic Deployment Project Updates
09:05:35 <jamespage> fnordahl: want to say anything on behalf of the openstack-charms project here?
09:05:40 <jamespage> anything new?
09:05:57 <fnordahl> We are on the verge of releasing the OpenStack Charms 19.04
09:06:45 <fnordahl> There will be new features one of them being support for deploying OpenStack Stein on Bionic.
09:06:45 <jamespage> \o/
09:07:09 <fnordahl> More details to be announced as part of our documentation in the charm-guide and deployment-guide
09:07:36 <jamespage> thanks - upgrades from rocky of course!
09:07:44 <jamespage> #topic Knowledge Sharing
09:08:21 <jamespage> not sure we'll have anything here today; I have been looking at optimising the restart logic for openvswitch in Ubuntu to minimise downtime during package upgrades
09:08:37 <jamespage> however that is WIP and probably won't be mature until 20.04
09:08:59 <jamespage> anything else for the knowledge sharing section
09:09:01 <jamespage> ?
09:09:34 <fnordahl> We have hit some challenges with the migration to Python 3.7 on Ubuntu Disco
09:10:05 <fnordahl> I'm brewing up some changes to the charm layer ``layer-basic`` to help tackle them
09:10:33 <gnuoy> There may not be anyone in the meeting right now who can answer this but I'd be interested if anyone has experience of running clouds for a long period with mixed OpenStack releases > I've upgraded half my compute nodes to N+1 but left the other half at N sort of thing.
09:10:44 <jamespage> ack - thanks that's a good headsup for +12 months when that's the default python3 version - I know coreycb and others have been enabling and fixing issues across projects
09:10:59 <jamespage> gnuoy: I think that's a good question
09:11:44 <icey> I did a bit mixed, not compute, but network/compute for a while
09:12:05 <icey> it was xenial-queens for neutron-gateway and bionic-rocky for the rest of the cloud
09:12:16 <icey> sample size of one but it did basically just work
09:12:24 <gnuoy> ack, thanks
09:13:47 <fnordahl> There is upcoming support in juju for something called generations, basically version control for your juju models
09:14:05 <fnordahl> That will probably lead to more people running mixed versions as part of upgrades etc
09:14:54 <jamespage> I would expect that to be somewhat transitory
09:15:09 <jamespage> anyway - I'll document in the meeting notes as a question - might get a response on the ML
09:15:22 <jamespage> ok next
09:15:23 <jamespage> #topic Docs Updates
09:15:30 <jamespage> I don't think we have any of those right now
09:15:36 <jamespage> SIG is a bit stale recently
09:15:40 <jamespage> #topic Open Discussion
09:15:47 <jamespage> anyone for anything else?
09:15:55 <fnordahl> not from me
09:16:06 <gnuoy> nor me
09:16:06 <icey> Nope
09:16:34 <jamespage> ok lets wrap then
09:16:36 <jamespage> #endmeeting