Earlier  
Posted Nick Remark
#openstack-nova - 2021-07-27
16:17:40 melwitt the only thing you get with PUT is if you issue a delete of your instance, if someone else updates it while it's deleting, you have a chance to reconsider your decision to delete it. afaik that might be the reasoning
16:18:06 bauzas melwitt: yeah, that's what I think too
16:18:12 bauzas for a race
16:18:16 bauzas anyway
16:18:26 melwitt yeah sorry, can move on
16:18:28 bauzas about the placement periodic job, well, we merged stuff
16:18:31 sean-k-mooney ya that is what i assuem too but i dont think that is the right design choice if we delete it we shoudl just delete it
16:18:31 bauzas last week
16:18:40 bauzas now the job looks to work
16:18:51 bauzas (we merged a now o-r-c)
16:18:59 bauzas *version
16:19:02 sean-k-mooney o-r-c
16:19:06 sean-k-mooney ??
16:19:20 sean-k-mooney oh os-resouce-classes
16:19:26 sean-k-mooney yes
16:20:14 sean-k-mooney placment was updated to account for the new os-resource-class release
16:20:26 bauzas yeah, sorry was triying to find the patch
16:20:37 bauzas https://review.opendev.org/c/openstack/placement/+/796595
16:20:52 bauzas anyway, nothing to tell more
16:21:13 sean-k-mooney one thing we might want to consider it preparing the patch when we are preparing the release
16:21:35 bauzas except maybe https://zuul.openstack.org/build/0e135bb912b240c8bc2aa96049727a1a
16:21:56 sean-k-mooney we know we have to do this every time we release it so we can prementivly submit the placment patch with a depens on the releases repo patch
16:21:56 bauzas oh nevermind, was fixed by the above
16:22:14 bauzas sean-k-mooney: you mean the placement release patch ?
16:22:19 sean-k-mooney yep
16:22:28 bauzas for m-3 ?
16:22:34 sean-k-mooney yes
16:22:40 sean-k-mooney well
16:22:48 sean-k-mooney when we go to release o-r-c again
16:23:00 sean-k-mooney we can prepare a patch to placment for it
16:23:23 sean-k-mooney to update the canary test and have it ready to go by depending on the pathch to the release repo
16:23:32 bauzas well, generally this is made by the release mgmt team but we can surely prepare it
16:23:36 sean-k-mooney im not sure if we will have anothger o-r-c release at m3
16:24:00 sean-k-mooney they will open the patch if we dont but they ask the ptl to approve
16:24:32 sean-k-mooney so at that point we can just do the house keeping patch for placnement and preappove ti so it will merge wehen the release patch does
16:24:45 bauzas they ask either the release folk or the PTL, yup :)
16:24:58 sean-k-mooney anyway we can move on just a tought
16:25:20 bauzas sean-k-mooney: keep your thought for next week when we get our ptl back
16:25:32 bauzas moving on
16:25:34 bauzas time is flying
16:25:49 bauzas Please look at the gate failures, file a bug, and add an elastic-recheck signature in the opendev/elastic-recheck repo (example: #link https://review.opendev.org/#/c/759967)
16:25:56 bauzas #topic Release Planning
16:26:02 bauzas We past M2 and spec freeze. M3 is in 5 weeks.
16:26:10 bauzas We have 21 approved an open blueprints and we have 5 weeks to finish them. Please focus review effort on bps in Needs Code Review state.
16:26:29 bauzas that reminds me, people have to make sure their blueprint is on Needs Code Review
16:26:51 bauzas #link https://launchpad.net/nova/+milestone/xena-3
16:27:35 bauzas the delivery status doesn't really mean anything but that can help reviewers to know which series to look at
16:27:49 bauzas so, if you love reviews, you know what to do
16:28:19 bauzas Next deadline is non-client library freeze at 16th of August
16:28:43 bauzas think about it for os-resource-class ;)
16:28:58 bauzas moving on
16:29:06 bauzas #topic PTG Planning
16:29:14 bauzas PTG timeslots booked by gibi, see #link http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023787.html
16:29:24 bauzas The PTG etherpad is ready to be filled with topics: #link https://etherpad.opendev.org/p/nova-yoga-ptg
16:29:37 bauzas If you see a need for a specific cross project section then please let gibi know
16:30:22 bauzas I'm pretty sure this etherpad will be filled before we have the PTG :)
16:30:47 bauzas #topic Stable Branches
16:30:56 bauzas elodilles: flood is yours
16:31:01 bauzas floor*
16:31:06 bauzas (oh man)
16:31:09 elodilles stable gates are not blocked
16:31:10 elodilles :)
16:31:18 elodilles at least as far as I can tell
16:31:19 bauzas excellent, excellent :D
16:31:46 bauzas tbh, this is not really time of the cycle when I look at stable changes
16:31:47 elodilles not so much activity around stable branches (M2, M3, vacations, etc...)
16:32:16 bauzas yup, most of the team efforts are focused on feature delivery as we speak, I guess
16:32:18 elodilles bauzas: true :)
16:32:21 bauzas moving on
16:32:30 bauzas #topic Sub/related team Highlights
16:32:36 bauzas Libvirt (bauzas)
16:32:45 bauzas bauzas: floor is your
16:32:52 bauzas bauzas: thanks
16:32:57 bauzas bauzas: nothing to report, sir.
16:33:01 bauzas bauzas: thanks.
16:33:05 bauzas moving on.
16:33:25 bauzas #topic Open discussion
16:33:40 bauzas I refreshed and nothing popped in the wikipage while we were speaking
16:34:01 bauzas so, nothing to say on this today, unless someone wanna raise something now
16:34:35 stephenfin nope
16:34:41 bauzas (I guess my fake dialog frightened a lof of people who disappeared)
16:34:55 bauzas oh wow, at least someone stayed \o/
16:35:08 bauzas I'm not that bad actor
16:35:10 sean-k-mooney can we ever really leave
16:35:39 bauzas I could just pretend I'll keep the stick for the whole hour and prevent you to use this channel for the last 25 mins
16:35:41 sean-k-mooney i dont have anything more for today
16:35:51 bauzas privilege of the power, whahahah
16:36:39 bauzas but, heh,
16:36:42 bauzas #stopmeeting
16:36:53 bauzas #endmeeting
16:36:53 opendevmeet Meeting ended Tue Jul 27 16:36:53 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
16:36:53 opendevmeet Minutes: https://meetings.opendev.org/meetings/nova/2021/nova.2021-07-27-16.00.html
16:36:53 opendevmeet Minutes (text): https://meetings.opendev.org/meetings/nova/2021/nova.2021-07-27-16.00.txt
16:36:53 opendevmeet Log: https://meetings.opendev.org/meetings/nova/2021/nova.2021-07-27-16.00.log.html
16:36:54 bauzas even
16:37:22 sean-k-mooney melwitt: bauzas do you want to chat about the allocation delete issue
16:37:38 bauzas sean-k-mooney: I guess I need to look at the original change
16:38:12 sean-k-mooney it didnt really contain much more motivation then we surmised already
16:38:33 sean-k-mooney https://review.opendev.org/c/openstack/nova/+/591597
16:39:31 sean-k-mooney it looks like the current intent was to put the instance in error if there was a conflict

Earlier   Later