16:00:25 #startmeeting nova 16:00:26 Meeting started Thu Aug 6 16:00:25 2020 UTC and is due to finish in 60 minutes. The chair is gibi. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:29 The meeting name has been set to 'nova' 16:00:45 o/ 16:00:48 hi 16:00:52 o/ (Right on time, noon church bells are going off and everything) 16:00:53 greo/ 16:01:04 o/ 16:02:19 let's get started 16:02:32 thank you dansmith for chairing the last week meeting in my absence 16:02:38 np 16:02:40 #topic Bugs (stuck/critical) 16:02:45 No Critical bugs 16:02:50 #link 39 new untriaged bugs (+3 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 16:02:56 please look at the untriaged bug list and try to push some bugs forward 16:03:15 is there any high profile bug we need to discuss today? 16:04:09 #topic Runways 16:04:17 etherpad #link https://etherpad.opendev.org/p/nova-runways-victoria 16:04:26 the slot for #link https://review.opendev.org/#/q/topic:bp/add-emulated-virtual-tpm will expire today 16:04:37 I don't see too much review progress lately there 16:04:50 the #link https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh-deprecated-apis still has more than a week in the slot and has already a +2 so we only need a second core to push it 16:05:30 the third slot is empty 16:05:41 he next in the queue is #link https://blueprints.launchpad.net/nova/+spec/cyborg-shelve-and-unshelve but it has negative feedback and in merge conflict so I'll drop it from the queue 16:05:51 the next is #link https://review.opendev.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/provider-config-file (tony_su) which also has negative feedback 16:06:10 this might be worth to put in a slot as tony_su is actively working on it as far as I see 16:06:29 or we can put the next one from the queue #link https://review.opendev.org/#/q/topic:bp/cyborg-rebuild-and-evacuate+(status:open+OR+status:merged) 16:06:36 what do you think? 16:08:45 I guess the silence means that we don't feel motivate to have anyithing in the third slot so I keep it empty for now 16:08:53 it is summertime anyhow 16:09:15 anything else about the stuff in runway slots? 16:10:11 * sean-k-mooney checks 16:10:13 * lyarwood joins late 16:10:41 provider.yaml would be nice to complete 16:10:49 if its ready for a slot 16:11:03 other then that i think 2 items is fine 16:11:24 the vtpm stuff is failly invovled 16:11:42 so there is a lot with that and the policy work as it is 16:12:16 OK then keeping the slots as is. I would really want the policy work to move forward 16:12:33 #topic Release Planning 16:12:40 last week we hit spec freeze. We will discuss freeze exceptions in the Open discussion section at the end. 16:12:56 anything else about the upcoming release? 16:13:55 #topic Stable Branches 16:14:34 lyarwood, elod : do you have some news for us? 16:14:42 gibi: nothing from me, elod? 16:14:54 nothing from me either :) 16:14:59 ack 16:15:00 thanks 16:15:06 #topic Sub/related team Highlights 16:15:38 API (gmann) 16:15:49 only one things about review on policy patches having stephenfin +2 already 16:15:52 #link https://review.opendev.org/#/q/topic:bp/policy-defaults-refresh-deprecated-apis+(status:open+OR+status:merged) 16:16:05 its in runway also as you mentioned early 16:16:10 yepp 16:16:15 thanks 16:16:21 Libvirt (bauzas) 16:16:46 he's out on PTO for 3 weeks and there's nothing on the pad AFAIK 16:16:52 OK, thanks 16:16:58 #topic Stuck Reviews 16:17:14 nothing on the agenda. Is there anything to discuss here? 16:18:22 #topic Open discussion 16:18:34 lets start with spec freeze exceptions 16:18:48 (Rambo ): Spec freeze exception for https://review.opendev.org/#/c/739349/ 16:19:00 add volume backed server rebuild spec 16:19:51 As far as I see there is a change compared to the originally planned cinder-nova interaction 16:19:58 I communicated with the Cinder team, there are some questions to determine, so they will discuss this more at the midcycle next week. 16:19:58 http://eavesdrop.openstack.org/irclogs/%23openstack-meeting-alt/%23openstack-meeting-alt.2020-08-05.log.html#t2020-08-05T14:25:16 16:20:37 rambo_li: do I undesrstand from the cinder meeting logs that the change from polling to os-server-externa-notification is not discussed yet? 16:20:59 yes, not discussed 16:21:02 i did not see that mentioned in the log but i could have missed it 16:21:13 I'm affraid we are running out of time for this spec on the nova side. I would only be confortable granting exception if everything would be set before end of this week 16:21:50 but I encurage to continue discussing it with cinder and nova teams 16:23:06 so can we approved this in nova firstly? 16:24:12 cinder seam to not have added a microveriosn when then added the new api 16:24:23 the question is how confident we are that cinder is OK with the external event. This is a new piece of logic that cinder needs to do 16:24:32 so we still have an open question of how we dedect if reimage is supported at all 16:24:42 even if we went back to polling 16:25:01 so i think we need an api chane in any case 16:25:15 sean-k-mooney: but reimage is an api change, isn't it? 16:25:23 yes 16:25:27 and when they added it 16:25:33 they did not add a microverion 16:25:41 so stien and train use the same one 16:25:46 but it was added in train 16:25:53 yes, the reimage api should add a microversion 16:26:16 https://docs.openstack.org/cinder/latest/contributor/api_microversion_history.html#maximum-in-stein-and-train 16:26:29 rambo_li: wasnt reimage added in trian 16:26:43 not merge 16:26:52 oh ok 16:27:10 https://review.opendev.org/#/c/606346/ 16:27:29 this review is add microversion 16:27:38 added 16:27:38 then ya we just need to know if cinder are ok with the change in poling to event 16:27:50 yea 16:27:52 yes 16:27:58 then we can check for 2.61 16:28:18 can you ask the cinder team to comment on that 16:28:27 you can link to the irc logs or this 16:28:32 to summarize. I'm willing to grant exception if cinder confirms that they are OK with the event approach. But the deadline to approve the spec is end of this week 16:29:13 I will leave my tentative +2 vote there after the meeting 16:29:20 sean-k-mooney: ok, I understand 16:29:33 gibi: thank you 16:29:38 cool 16:29:40 moving forward 16:29:52 (mlycka): Spec freeze exception for https://review.opendev.org/#/c/702810/ 16:30:05 Enable REST quiescing 16:30:18 there are multiple -1 on this one 16:30:51 I see that there is discussion about using os-server-external-events for quiescing the attached volume 16:30:58 or using a separate server action 16:31:12 for me this depends on the actual use case 16:31:34 so on irc it was mentioned that they wanted to use this without cidner 16:31:47 using a third party backup solution 16:31:48 until now I thought that the end user would ask Cinder to snapshot a volume, and then Cinder would call Nova to quesing 16:32:06 yes that is wht the spec implies 16:32:18 is it supported to backup a Cinder volume without Cinder knowing about it? 16:32:44 well i think they are going to run somehting in the vm to do the backup 16:32:50 which would be 16:33:01 but if they are going to the cinder backend i would say no 16:33:24 the same way we dont support peopel doing backup and restore of the qcow files on the compute host 16:33:53 if they go into the VM then they can also quiesce the VM from inside 16:34:14 yes that is true which confusted me why this was needed 16:34:35 if this is only for cinder then im fine with the external event 16:35:20 I think there was other things open in that spec too 16:35:31 last line of problem descrition "No other actor, such as an external backup tool, is able to quiesce a VM." 16:36:00 yes johnthetubaguy 16:36:17 you had some open quetion regarding the change from the previouly appoved spec 16:36:52 I don't feel like we can answer all these during tomorrow 16:37:07 #link https://specs.openstack.org/openstack/nova-specs/specs/mitaka/approved/expose-quiesce-unquiesce-api.html 16:37:25 i dont thnk so either althoguh im not really invested in this spec 16:38:20 oh so the previous spec give a much better usecase 16:38:28 takeing a snapshot fo a group of vms 16:38:42 and it uses an instance action 16:39:11 OK, we have to go back to the use case 16:39:23 which means more discussion 16:39:36 which means I don't think we should grant an freeze exception for this 16:40:08 let's continue discussing the use case in V and have an agreed spec for early W feels better 16:40:11 sorry 16:40:32 moving on 16:40:34 (gibi): Spec freeze exception for https://review.opendev.org/#/c/733703 16:40:41 Routed network scheduling spec 16:40:48 it basically has 2 +2s 16:41:06 I was away last week so I could not approve it in time 16:41:32 just to be clear this will not fix everything related to routed netwroks 16:41:32 is there any objection to approve it now? 16:41:45 sean-k-mooney: yes, it is a next step forward with route net 16:41:54 but the issue it does fix make the situation defetly better then todya 16:42:05 so i think it makes sense for incremetal improvement 16:42:26 yep so no object from me 16:42:36 *objection 16:43:03 going once 16:43:35 going twice 16:44:22 approved 16:44:27 moving forward 16:44:44 so these were the spec freeze exception 16:44:45 s 16:44:52 (gibi): I will be on vacation during the next two weeks. I need volunteer(s) to run the next two nova meetings. 16:45:28 * sean-k-mooney admires the silence 16:45:40 I will be a bit less gone than last week so I might pop in for a quick check during both weeks but not be able to run meetings 16:45:56 as an alternative I can cancel the next two meetings 16:46:03 * lyarwood can help run the next two meetings 16:46:12 \o/ thanks lyarwood ! 16:46:32 then moving forward 16:46:38 (lyarwood): https://launchpad.net/~nova-coresec - Do we need to reseed this team with active core team members? 16:47:22 Yeah I noticed that johnthetubaguy and dansmith are the only semi active Nova cores in that team at the moment 16:47:38 and wonderd if we wanted to get more people listed there? 16:47:50 gibi: I'd assume you would like to be as PTL at least? 16:48:08 fwiw, I don't think the ptl is generally added to that list in the past, 16:48:09 for some reason I already see the private secu bugs in launchpad 16:48:19 oh well there we go then 16:48:26 gibi: if you have been added to cc you can 16:48:28 but it's common to copy them which makes them visible 16:48:35 right TIL 16:48:37 gibi: often the security team will add the ptl 16:48:37 then I know the reason 16:49:28 you can corner me to help in with this work 16:49:46 ack thanks 16:49:49 but I would like to get a specific trigger to know where to help 16:50:47 do we have any good candidate to be added to that team? 16:50:59 lyarwood: are you volunteering? ;) 16:51:09 haha no I've only just been made a core 16:51:22 I just wanted to raise it with the group and see if anyone was interested 16:51:35 we don't need to dwell on it, we can move on 16:51:57 OK, so if somebody interested to joint to the security team then let dansmith or johnthetubaguy know 16:52:23 lyarwood: thanks for noticing and bringing this up 16:52:44 this was the last item on the agenda 16:52:53 is there any other topic for today? 16:53:01 just quickly for os-vif 16:53:12 the non client lib freeze is septemebr 3rd 16:53:23 but i would like to try an finalise it august 27th 16:53:41 to give us a week if anything is found after teh relese 16:53:50 although we are not changing much this cycle 16:54:00 so i dont epect to need it 16:54:29 sean-k-mooney: thanks. Is there anyithing outstanding that we really want to lend in os-vif before the freeze? 16:54:34 land 16:54:47 i want to change one default 16:54:57 and then just the ubuntu 20.04 change 16:55:03 but not really 16:55:13 thre are currently 4 patches 16:55:17 i think we can land them all 16:55:29 no rush yet 16:55:59 cool 16:56:02 thanks for the headsup 16:56:03 the default change is using the python binding instead of cli for ovs db 16:56:16 i will rebase the ubuntu 20.04 one, seems merge conflict https://review.opendev.org/#/c/738130/ 16:56:43 cool 16:57:28 i think we are done so 16:57:58 OK 16:58:06 if nothing else then thanks for joining today 16:58:16 o/ 16:58:33 #endmeeting