15:01:42 #startmeeting kolla 15:01:42 Meeting started Wed Nov 6 15:01:42 2019 UTC and is due to finish in 60 minutes. The chair is mgoddard. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:46 The meeting name has been set to 'kolla' 15:01:47 #topic rollcall 15:01:50 \o 15:02:02 o/ 15:02:04 o/ 15:03:45 #topic agenda 15:03:52 * Roll-call 15:03:54 * Announcements 15:03:56 ** Kolla vPTG on Thu & Fri this week: https://etherpad.openstack.org/p/kolla-ussuri-ptg 15:03:58 * Review action items from last meeting 15:04:00 * CI status 15:04:02 * Train release planning 15:04:04 * Review priorities 15:04:06 * Kolla vPTG plannign 15:04:08 Let's keep it short today as we're meeting tomorrow & friday 15:04:13 #topic announcements 15:04:26 #info Kolla vPTG on Thu & Fri this week 15:04:32 #link https://etherpad.openstack.org/p/kolla-ussuri-ptg 15:05:14 #info Kolla RC1 and stable/train created. Waiting on kolla-ansible release 15:05:30 Any others? 15:05:44 We can remove feature freeze once kolla-ansible RC1 has been released 15:05:57 * yoctozepto been to orthodontist today and is trying to regain ability to speak 15:06:25 ouch 15:06:38 yeah, considering tomorrow's action 15:06:43 Hopefully you will recover by tomorrow... 15:06:58 #topic Review action items from last meeting 15:07:03 I will write in the chat window if it doesn't get better 15:07:06 announce kolla virtual ptg on mailing list 15:07:07 :-) 15:07:08 Split images into UNBUILDABLE/CI_TESTED/rest so we can have odl as buildable but not do it on CI 15:07:20 yoctozepto did ML annoncement 15:07:24 I did 15:07:46 not sure who was supposed to do the other 15:08:02 normally action items need an owner 15:08:13 sorry :-( 15:08:18 I think we'll disucss it tomorrow anyway 15:08:28 np 15:08:36 thanks again for running the meeting last week yoctozepto 15:08:41 #topic CI status 15:08:42 yw 15:08:58 I think we're relatively healthy right now 15:09:04 anyone want to refute that? 15:09:17 na-ah 15:09:45 cool 15:09:46 o/ (me late as always) 15:09:55 oh yes, he is late 15:09:58 #topic Train release planning 15:10:11 getting closer, we have an RC1 15:10:29 still need kolla-ansible RC1 patch to merge, then we can unfreeze master 15:10:47 are we planning for rc2 and retagging bugs to rc2 milestone? 15:11:08 we'll have an RC2 yes - several bug fixes since RC1 15:11:24 I think kolla itself is pretty well-shaped in RC1 15:11:26 I don't bother with RC milestones, just release 15:11:28 yeah 15:11:31 k-a might need RC2 indeed 15:11:51 but launchpad milestones are fine with release only 15:11:57 I proposed a couple of patches to stable/train for kolla which I think Tripleo will want 15:12:02 will the RC (and first stable release) have an upgrade path from stein? for k-a 15:12:05 or does that ocme later 15:12:21 kplant: it has it already 15:12:31 look at me paying attention. ty :-) 15:12:36 kplant: we test upgrades in CI throughout the cycle 15:12:44 mgoddard: ah, yeah, forgot about those non-merged 15:13:31 so let's keep focusing on bug fixes and stability until train release 15:14:08 mgoddard: it doesn't mean we test upgrades of all services - but the core works ;-) 15:14:23 early adopters with time to test the RC will be rewarded with community tokens 15:14:32 i have a question on that but ill raise it after the meeting 15:14:44 mgoddard: how do community tokens work? 15:15:14 yoctozepto: they are worth respect 15:15:28 mgoddard: ah, respect in the hood 15:15:32 anyway, keeping it short :) 15:15:34 mgoddard: i might be able to bump the lab here to train rc1 15:16:02 kplant: that would be great. backup if it's at all important to you (as always) :P) 15:16:26 you might hit an issue with the " Running Nova API bootstrap container" task 15:16:50 sean-k-mooney: what issue is that? 15:16:59 is there a bug report? 15:17:10 "Database schema file with version 72 doesn't exist." 15:17:17 lol 15:17:18 i was going to ask ye about it after the meeting 15:17:30 we had no idea 15:17:37 yeah, haven't seen that one 15:17:37 the api db sync is failing 15:17:41 it passes CI :-) 15:17:49 its might be a nova issue 15:18:05 ok, let's pick it up after the meeting. Thanks for raising sean-k-mooney 15:18:10 #topic Review priorities 15:18:39 Same as before really - RP+1 for bug fixes we want in Train 15:18:51 and any release-related patches 15:18:58 features still RP-1 for now 15:19:10 Any other priorites we need? 15:19:45 speech recovery 15:21:16 #topic Kolla vPTG planning 15:21:27 It's almost upon us 15:21:36 #link https://etherpad.openstack.org/p/kolla-ussuri-ptg 15:22:06 I did a little work on the etherpad yesterday - moved some things out of the 'general' section which became a bit bloated 15:22:17 added incomplete train priorities at the bottom 15:22:43 some new sections: "How to Get Involved", "Agenda", "Train cycle retrospective" 15:24:02 Please go through it again and see if we have missed anything. We can always add things during the PTG 15:24:20 How does this look for an agenda? 15:24:22 Welcome, troubleshoot video conferencing 15:24:24 Introductions 15:24:26 Train cycle retrospective 15:24:28 Ussuri design discussions 15:24:30 Ussuri priority voting 15:24:32 Housekeeping 15:25:01 Welcome, troubleshoot video conferencing 15:25:04 45 mins 15:25:08 lol 15:25:20 :D 15:25:47 I was trying to avoid making it a timed schedule - just an agenda to work through 15:25:48 yeah, I like it 15:26:43 cool. Anything else we need to do before tomorrow? 15:27:10 *cough* learn to speak again *cough* 15:27:13 sleep well :) 15:27:35 I seriously thought it would be less impactful 15:28:01 what did they do to you? 15:28:41 placed some elastic metal bar on the palate 15:28:52 among other drastic things 15:29:06 but this contributes to VERY bad articulation 15:29:07 let's hope you recover in time 15:29:24 #topic Open discussion 15:29:41 sean-k-mooney: where were we? 15:30:07 migration 72 15:30:41 i was evluating my poor life choice of deploying a random commit off master for about month ago and trying to update :) 15:31:12 ya so the nova-manage api_db sync command is failing in the nova-api bootstrap container 15:31:12 ah, so probably not a problem that most people will hit? 15:31:18 propably not 15:31:32 im debating if this is a nova issue which it may be 15:31:33 still it sounds weird 15:31:50 ya the migration is just a placeholder https://github.com/openstack/nova/tree/master/nova/db/sqlalchemy/api_migrations/migrate_repo/versions 15:32:10 but its as if the master contianer does not have it 15:32:19 its a unbuntu source deployment 15:32:25 using the docker hub images 15:32:57 looks like it was made for ussuri though 15:33:13 could be you got the images for ussuri back then 15:33:20 yes its the placeholder incase we need to backport something 15:33:30 ah 15:33:31 ok 15:33:37 i could have got it before that was merged ya 15:33:49 https://github.com/openstack/nova/tree/stable/train/nova/db/sqlalchemy/api_migrations/migrate_repo/versions 15:33:50 i basicaly deploy nova rc1 15:33:54 still, it's not in train 15:34:10 so you are essentially trying a downgrade now 15:34:24 ah that makes sense 15:34:36 hmm, sounds like you got caught between train GA and kolla switching to train packages on master 15:34:36 we did builds of master 15:34:40 ok this is jsut a dev cluster at home 15:34:45 so i can always redeploy it 15:34:52 destroy :D 15:35:00 if you crack open the container you can check the nova commit 15:35:07 glad we solved the mystery 15:35:19 mgoddard: ya that has happended to me before 15:35:41 i got impatent wanting to have my home openstack running again 15:36:19 ok well that all makes sense. i might redepoy with rc1 at the weekend 15:36:59 mgoddard: are the "master" images currently built off train? 15:37:10 sean-k-mooney: ussuri 15:37:14 stable/train is train 15:37:26 sean-k-mooney: yes, for a short time 15:37:36 but soon will go back to master 15:37:39 ah right 15:37:44 mgoddard: the docker hub ones are stable train right 15:37:44 the revert is pending, my bad 15:37:49 but use stable/train 15:37:51 after kolla-ansible RC1 we can go back to master 15:37:57 indeed 15:38:02 sean-k-mooney: today, yes 15:38:08 yoctozepto: it explains what im seeing 15:38:31 ok all is good 15:39:48 Any other topics for today? 15:40:35 low activity today 15:40:42 everyone prepping for vptg 15:40:43 i have a quick one 15:40:57 is there any apetite to bump to rabbitmq 3.8 in U? 15:41:11 reason i ask is the official prometheus plugin is shipped with 3.8 15:41:12 kplant: to deprecate and move to amqp 15:41:22 :D 15:41:37 yoctozepto: not official party line :p 15:41:37 just kidding, rabbitmq needs some love indeed 15:41:47 we are blocked by erlang vm being old 15:42:01 do we know what centos 8 gives us? 15:42:05 rmq 3.8 solves a bunch of issues with ipv6 as well 15:42:19 mgoddard: not checked 15:43:02 I think it's worth a discussion. But let's also see what, if anything, centos 8 does for us 15:43:19 no rabbitmq 15:43:29 in the default repos 15:43:53 no erlang either hmm 15:44:21 probably will be shipped by rdo 15:44:43 we need upstream for ubuntu anyways 15:44:53 kplant: maybe you could investigate and report back? 15:44:54 it was too late for train 15:44:57 to coordinate 15:45:35 added to PTG agenda 15:48:05 ok, any more? 15:48:13 mgoddard: yeah i was actually poking through the el8 mirrors until i got a call 15:49:21 none from me 15:49:26 let's wrap it up I think 15:49:29 Thanks all 15:49:32 #endmeeting