21:00:04 #startmeeting nova 21:00:05 Meeting started Thu Aug 31 21:00:04 2017 UTC and is due to finish in 60 minutes. The chair is mriedem. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 21:00:08 The meeting name has been set to 'nova' 21:00:13 o/ 21:00:14 o/ 21:00:16 o/ 21:00:22 \o 21:00:51 \o 21:00:52 alright then 21:00:55 #link meeting agenda https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting 21:01:03 #topic release news 21:01:13 well we know pike is released 21:01:16 good riddance 21:01:21 I'll say 21:01:23 heh 21:01:25 #link Queens release schedule: https://wiki.openstack.org/wiki/Nova/Queens_Release_Schedule 21:01:29 i have to fill in ^ 21:01:36 #info Re-propose specs for Queens 21:01:37 resource tracking is going to haunt us 21:02:03 i love resource tracking but it doesn't love me 21:02:13 ok that's about it for release news 21:02:21 #topic bugs 21:02:30 nothing marked critical 21:02:34 #info 4 new untriaged bugs (up 1 from last week) 21:03:09 gate status is ok 21:03:15 3rd party ci status is, ok? 21:03:46 #topic reminders 21:03:52 #link Consider signing up for the Queens PTG which is the week of September 11 in Denver, CO, USA: https://www.openstack.org/ptg 21:04:06 #link Pike PTG topics etherpad: https://etherpad.openstack.org/p/nova-ptg-queens 21:04:20 i will hopefully get more serious about organizing that etherpad next week 21:04:31 right now it's PLACEMENT...CELLS...EVERYTHING ELSE 21:04:49 #info Be a star and consider the Pike project update interview at the PTG: http://lists.openstack.org/pipermail/openstack-dev/2017-August/121369.html 21:04:53 yeah. are we gonna have designated times for syncing with cinder and neutron teams? 21:05:01 thursday morning is nova/cinder love time 21:05:05 yeah, 9th green at 9 21:05:06 for both 21:05:11 don't know about neutron 21:05:16 kevinbenton hasn't been returning my calls 21:05:18 or texts 21:05:21 or letters 21:05:27 mriedem: you called? 21:05:27 haha 21:05:42 oh NOW you decide to respond 21:05:58 mriedem: you don't even hang out in the #openstack-neutron channel :) 21:06:03 sure as shit i do 21:06:19 anyway, kevinbenton if you want to talk PTG stuff later we can 21:06:34 mriedem: i haven't finished a schedule for neutron PTG so i'm flexible for a cross session 21:06:40 mriedem: ack, let's chat in channel 21:06:47 #topic stable branch status 21:06:54 well, we drop one, we add one 21:06:58 another thing to consider with PTG scheduling is, whether we should try to break stuff up into some time chunks to make it easier for people to move between rooms 21:06:58 #link stable/pike: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:stable/pike,n,z 21:07:17 melwitt: we did that last time right? 21:07:21 I assumed we would again 21:07:25 did we? 21:07:34 yeah, didn't we assign some times to things? 21:07:39 I don't think we did. some folks were disappointed with the lack of ability to move between rooms 21:07:41 yeah, morning/afternoon 21:07:47 but not granular like to the hour, like at the summit 21:07:54 some people == mel 21:08:06 There's that #openstack-ptg channel 21:08:06 haha, nooo 21:08:16 where we're sposed to announce when we're gonna move on to a topic. 21:08:22 yeah there is a bot thing now to notify when something is happening in a room 21:08:28 https://etherpad.openstack.org/p/nova-ptg-pike 21:08:34 we did for L287 and 288 21:08:55 yeah there are common rooms for cross-project things 21:08:55 there were meeting times for some of the cross-project ones, that's probably what I'm thinking about though 21:08:58 like the api wg one 21:09:00 that you can schedule a block of time 21:09:11 the horizontal topic things are also mostly monday/tuesday 21:09:16 leaving wed-friday for nova-specific stuff 21:09:17 efried: it has a "now" topic and a "next" topic 21:09:18 in our cave 21:09:21 I never move so it's not about me. I just heard some people felt stuck in the room so as not to miss the topic they wanted 21:09:40 yeah, i hope the bot helps with that, 21:09:53 we scheduled the neutron and keystone syncs 21:09:54 plus, if you're there, and you want to be pinged when we start talking about something, put your nick in the etherpad next to said topic 21:10:05 anyway 21:10:06 holy ship 21:10:09 +1 to slots 21:10:10 * bauzas waves super late 21:10:28 #action mriedem to appease melwitt and only melwitt with slotifying the ptg topics down to the nanosecond 21:10:37 lol 21:10:55 melwitt: i will totally be happy to trade doing that for you doing the project update 21:11:01 with the red hat marketing team 21:11:20 so as for stable stuff, 21:11:22 I'll take a look at that, maybe I could do it 21:11:25 stable/pike is active 21:11:42 and we have some known bugs coming out of pike FF/RC1/RC2 for edge cases with placement stuff 21:12:01 which will all get backported 21:12:16 we've had recent releases for ocata and newton, so those are pretty stable atm 21:12:26 no pun intended 21:12:34 #topic subteam highlights 21:12:38 dansmith: cells v2? 21:12:50 mriedem: planning a stable version soon-ish ? 21:13:07 given all the backports 21:13:08 not until several more bugs are fixed and backported 21:13:19 okay, fine by me 21:13:25 will prioritize that then 21:13:42 did we lose dansmith? 21:13:49 sorry 21:13:53 we talked about ptg topics 21:13:59 details are in the ptg etherpad 21:14:08 only one minorish bug since rc2 21:14:11 winning. 21:14:13 that's all 21:14:24 edleafe: scheduler? 21:14:28 Most of the meeting was spent discussing the options for returning data from the scheduler once we support alternates for each instance, along with the allocations for each choice. 21:14:32 We agreed not to use a cache for the allocations, and to use an object to manage the data returned from select_destinations() 21:14:35 There is already a much more limited Destination object in the RequestSpec, so that may be adapted to add this new information. 21:14:38 Lots of pre-requisite work, such as BP/specs for returning alternates and allocations still needs to be done first. 21:14:41 Fin. 21:15:09 ok 21:15:12 api meeting, i wasn't there 21:15:23 not sure anyone here was there either given timezone 21:15:52 notifications, 21:15:54 there was a meeting 21:16:00 The subteem meeting and weekly status mail has been restarted 21:16:09 * mriedem speaks for gibi 21:16:12 I started a ML thread and an etherpad to collect who is using nova notifications and I'm trying to get feedback and possible new contributors. #link http://lists.openstack.org/pipermail/openstack-dev/2017-August/121651.html 21:16:42 and finally cinder, 21:16:50 meeting was today. there was a new cinderclient release that has some stuff we need 21:17:00 patches in nova are going to be rebased 21:17:08 and ildikov is re-proposing the specs 21:17:20 #topic stuck reviews 21:17:23 nothing on the gaenda 21:17:24 *agenda 21:17:34 #topic open discussion 21:17:42 nothing on the agenda so i'll open it up 21:18:26 ok well i guess that's it 21:18:30 thanks everyone 21:18:33 #endmeeting