14:00:23 #startmeeting nova 14:00:26 Meeting started Thu Feb 8 14:00:23 2018 UTC and is due to finish in 60 minutes. The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:30 The meeting name has been set to 'nova' 14:00:34 @/ 14:00:40 hi! I will be your host today 14:00:41 o/ 14:00:45 _o 14:00:50 \o (even) 14:01:19 \o 14:01:26 \o 14:01:37 mriedem update the agend on the wiki and I will try to walk through it 14:01:42 *updated 14:02:01 o/ 14:02:04 o/ 14:02:33 #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting 14:02:39 let's get started 14:02:42 #topic release news 14:02:53 #link Queens release schedule: https://wiki.openstack.org/wiki/Nova/Queens_Release_Schedule 14:03:00 #info Feb 8: Queens release candidate 1 14:03:04 which is today 14:03:55 If I understand correclty we have two weeks to test the RC1 and release additional RCs if needed 14:04:20 partially correct https://releases.openstack.org/queens/schedule.html 14:04:34 we are R-3 14:04:54 2/22 is the final day for RCs 14:04:56 so yes gibi is right 14:05:09 I agree, hence partially 14:05:10 o/ 14:05:15 because R+0 is the GA 14:05:27 anyway 14:05:42 #info Blueprints: 41 completed out of 53 approved (77% completion rate); the rest have been deferred to Rocky; mriedem will send the burndown chart details to the ML. 14:06:11 This feels like a nice progress 14:06:28 #link Queens RC1 TODOs: https://etherpad.openstack.org/p/nova-queens-release-candidate-todo 14:06:52 there are couple of open patches in the etherpad to look at 14:07:20 my goal for rc1 today, 14:07:24 is the prelude release note, 14:07:31 and dansmith's compute rpc versoin bump patch 14:07:35 https://review.openstack.org/#/c/541005/ 14:07:48 then i think i'm going to cut it 14:08:08 sounds doable :) 14:08:19 mriedem: I was reviewing dansmith's compute RPC patch 14:08:20 any questions comments on the RC1 ? 14:09:10 then moving to bugs 14:09:12 #topic Bugs (stuck/critical) 14:09:18 #link queens-rc-potential bugs: https://bugs.launchpad.net/nova/+bugs?field.tag=queens-rc-potential 14:09:46 there are two bugs on the list 14:09:56 i'm cleaning up my patch for the 2nd one, 14:10:07 I haven't seen any other crucial bug when triaging 14:10:11 the first, the non-ascii one, i wonder if that's a regression or not, because if it's not a regression, it's not an rc1 blocker 14:10:17 #link https://review.openstack.org/#/c/541008/ 14:10:33 just updated ^ 14:11:40 It seems we don't have any critical bugs 14:11:44 I didn't open a bug for this, but https://review.openstack.org/#/c/540534/ has a bunch of support matrix fixes we might want to get in 14:12:13 yikes, i'm not reviewing that today 14:12:29 people generally read docs from the latest published version, so that's fine to just get on master later 14:12:34 yeah, it was pretty comprehensive... thought about splitting it up, but part of the point was consistency... 14:12:38 edmondsw: okay, will look for today if possible 14:13:11 #info 51 new untriaged bugs (up 3 since the last meeting) 14:13:14 no 14:13:25 36 new untriaged bugs 14:13:38 bauzas: then thanks for your triaging effort 14:13:52 #info 36 new untriaged bugs 14:14:03 I'd love to see that down to less than 10 before we cut the release 14:15:30 bauzas: totally make sense. I will try to look at some as well 14:15:38 #link check queue gate status http://status.openstack.org/elastic-recheck/index.html 14:16:06 I don't see issue with the gate today 14:16:32 #link 3rd party CI status http://ci-watch.tintri.com/project?project=nova&time=7+days 14:16:47 the nova-next job seems to be failing consistently 14:16:56 the glanceclient workaround rc1 patch fixes nova-next 14:17:00 https://review.openstack.org/#/c/541008/ 14:17:13 ++ 14:17:23 That's ready for some cores IMO 14:17:36 I will look at it after the meeting 14:17:45 seems small and easy 14:18:08 any other questions / comments about bugs or CI ? 14:19:07 then moving to reminders 14:19:12 #topic Reminders 14:19:19 #link Today is the last day for Rocky summit talk proposals: https://www.openstack.org/summit/vancouver-2018/call-for-presentations/ 14:19:50 isn't that closed already ? 14:20:00 I thought it was 12am ET 14:20:19 when i updated the agenda last night, it was 'today' :) 14:20:19 there is a green Add New Presentation button on the page 14:20:27 so it is not closed yet 14:20:38 snap, nevermind 14:20:49 bauzas: 23:59 PST 14:21:14 after 15 years working with international people, I can't still handle timezones 14:21:44 we should ban timezones 14:21:48 #link Rocky PTG topics: https://etherpad.openstack.org/p/nova-ptg-rocky 14:22:07 I think mriedem mentioned that he will structure the etherpad a bit after RC1 14:22:42 Should melwitt be doing that instead? :P 14:23:34 I don't know what is the cut off date for the PTL change :) 14:23:53 Maybe melwitt delegated the task to mriedem :D 14:24:02 14:24:40 okay, okay, our esteemed leadership is not rising to the bait; they must be busy with actual work. 14:24:49 anything else we need to remember? 14:25:14 then, stable branches 14:25:17 #topic Stable branch status 14:25:26 #link stable/pike: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/pike,n,z 14:26:03 #link stable/ocata: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/ocata,n,z 14:26:07 i will likely go through some of those and then cut a stable release 14:26:24 several are backports from me and have a +2 so i can't approve them 14:26:30 or shouldn't 14:26:45 next week for me 14:27:32 anything else for the stable status? 14:27:57 then subteam highlights 14:28:01 #topic Subteam Highlights 14:28:09 Cells v2 14:28:22 there wasn't much, 14:28:26 just some bug fixes for latent issues 14:28:40 they are linked into the rc1 etherpad but since they are latent we can backport them later too 14:28:41 there are couple patches linked to the Queens TODO etherpad 14:28:44 i won't hold rc1 for them 14:29:04 mriedem: thanks 14:29:33 Scheduler 14:29:37 Spent most of our time discussing some latent bugs due to inconsistent handling of generations for resource providers. Agreed that generation handling will be an excellent PTG topic. 14:29:41 We also discussed cdent's experiments on extracting placement from Nova. 14:29:44 efried and I are submitting a "State of Placement" talk for Vancouver. Now if we can only figure out how to get travel approval... 14:29:47 EOF 14:30:23 edleafe: thanks 14:30:31 Notification 14:30:39 that is me 14:30:40 edleafe: TSP is open till end of March IIRC 14:31:06 only a short meeting 14:31:10 I mean, one or two weeks after the final talks choice 14:31:23 we discussed two specless bp 14:31:38 I will bring them up in the Open discussion topic 14:31:45 EOF 14:32:00 hm, what happened with the other subteams? they are not on the agenda 14:32:13 i removed cinder 14:32:23 nothing to report there, no meetings before the ptg 14:32:32 working through docs and bugs 14:32:49 and no one is ever here to report on the api meeting 14:32:51 if it still happens 14:33:06 OK 14:33:18 then moving forward 14:33:29 #topic Stuck Reviews 14:33:35 nothing on the agenda 14:34:11 do we have anything to talk about here? 14:34:17 nope 14:34:23 then 14:34:25 #topic Open discussion 14:34:38 [02.07.][gibi]: Let's quickly agree on the specless bluperint: trigger notifications when lock or unlock instances #link https://blueprints.launchpad.net/nova/+spec/trigger-notifications-when-lock-unlock-instances 14:34:57 There is lock and unlock instance actions in nova 14:35:06 but we don't emit notifications for them 14:35:16 s/excepted/expected/ and I'm +1 14:35:19 +1 14:35:27 it's an instance action, all other actions have notifications 14:35:27 fine with me 14:36:03 I can help with the implementation and the review 14:36:52 seems the we agree to approve this 14:37:10 then moving forward to next on the agenda 14:37:18 [02.07.][gibi]: Let's quickly agree on another specless blueprint: Add the user id and project id of the user initiated the instance action to the notification #link https://blueprints.launchpad.net/nova/+spec/add-action-initiator-to-instance-action-notifications 14:37:45 today the notifications contain the user_id and the project_id of the _owner_ of the instance 14:38:10 but the instance action we are notifying about might be initiated by another user 14:38:22 i think this one is OK 14:38:24 +1, pending excruciating naming bikeshed 14:38:44 efried: bikeshed can happen in the review 14:39:15 I can be the driver for this bp as well 14:40:32 seem like no objections :) 14:40:49 this was the last item on the agenda 14:41:01 any other thing to bring up? 14:41:31 seem no 14:41:40 let's get back to shaping the RC1 14:41:58 #endmeeting