| frickler | 5,15 kernel should be new cirros. that failure very much looks like memory corruption to me | 04:39 |
|---|---|---|
| opendevreview | Merged openstack/placement master: Bugtracker link update https://review.opendev.org/c/openstack/placement/+/876768 | 06:38 |
| gibi | dansmith: I agree that kernel crash points to cirros. Obviously if we see such crashes whathever happens after it (ie detach failure) is probably a consequence of the crash. | 07:50 |
| gibi | dansmith: in the original detach failure case there was no kernel crash, so this is definitely different | 07:50 |
| kashyap | gibi: On that device-detach patch from the QEMU upstream, do we have a way to test it upstream? -- https://www.mail-archive.com/qemu-devel@nongnu.org/msg952944.html | 08:01 |
| kashyap | gibi: I can create an RPM build of QEMU with that patch for Fedora ... if we there's a Fedora job that can test it | 08:02 |
| kashyap | But probably a Ubuntu package is preferred, I guess | 08:02 |
| gibi | I don't think we have a Fedora based job upstream :/ | 08:11 |
| gibi | kashyap: but if you can build the fix to Fedora then you can at least try my libvirt only reproduction to see if that is fixed | 08:12 |
| kashyap | gibi: Oh, right indeed. I'll give it a go this week and update you on the bug | 08:13 |
| gibi | cool,thanks | 08:13 |
| sean-k-mooney | gibi: bauzas i now want to add a new hw_vif_model specifically igb | 10:40 |
| sean-k-mooney | https://www.qemu.org/docs/master/system/devices/igb.html | 10:40 |
| sean-k-mooney | qemu added sriov virtualsiation support to it last year | 10:40 |
| gibi | wut? that feels super useful for testing if it does what I think it does | 10:41 |
| sean-k-mooney | unfortunetly it will take a while before our cloud providers have this | 10:41 |
| sean-k-mooney | gibi: yep thats why they added it | 10:41 |
| sean-k-mooney | it would allow us to take a neutron port and then create VFs from it | 10:41 |
| gibi | then I'm +100 | 10:41 |
| sean-k-mooney | support was added in libvirt 9.3.0 | 10:42 |
| sean-k-mooney | that may be qemu 9.3.0 libvirts docs kind of suck | 10:42 |
| sean-k-mooney | at makeing it cleare if they mean the qemu or libvirt version | 10:42 |
| sean-k-mooney | ill finish the filter stuff firts and you know actully try and do it locally before proposing anything but if it work ill bring this up in a team meeting | 10:44 |
| sean-k-mooney | just not today | 10:44 |
| sean-k-mooney | on a side note this is the alpine image i created https://fileshare.seanmooney.info/ | 10:45 |
| sean-k-mooney | im going to update the nova job patch to skip trying to build it and just pull that and see if it works after i finish the docs chagnes on teh schduler patch | 10:46 |
| zigo | How do I migrate away a VM with status SUSPENDED ?!? | 11:16 |
| sean-k-mooney | zigo: i suspended means suspended to disk. i think a cold migration might work but i would have to check the api | 11:26 |
| sean-k-mooney | live migration wont because its not actully running | 11:28 |
| sean-k-mooney | looking at the micate api it does not say but resize says You can only resize a server when its status is ACTIVE or SHUTOFF. | 11:29 |
| sean-k-mooney | zigo: so my guess is without resuming the instnace its not possible | 11:29 |
| sean-k-mooney | bauzas: you have reviewd this in the past can you take alook at this backprot again https://review.opendev.org/c/openstack/nova/+/790447 | 11:45 |
| zigo | sean-k-mooney: Thanks. | 11:59 |
| bauzas | sean-k-mooney: me clicks | 12:37 |
| dansmith | gibi: sean-k-mooney: yep, it could be totally different problems. However, we're at the point of suspecting the guest is not playing ball, and sometimes we just see no detach and other times a kernel crash | 13:32 |
| dansmith | sometimes I see only one trace in the klog when that happens, other times several like this | 13:32 |
| dansmith | so I'm just saying that I think expecting cirros to behave like a real guest is already suspect (in my mind) | 13:33 |
| gibi | yeah, I agree | 13:44 |
| sean-k-mooney | so i have the alpine image hosted at https://fileshare.seanmooney.info/alpine.qcow2 | 13:51 |
| sean-k-mooney | ill see if i can just sub that in later today into a job and see what breaks | 13:51 |
| dansmith | most of the guest crashes were in kmalloc things, | 13:54 |
| dansmith | which makes me wonder if there's more interaction with the host there | 13:55 |
| dansmith | actually they all go through load_module() in the kernel and are failing there | 13:58 |
| bauzas | dansmith: sorry I didn't had time to look at how many failures were having this kind of crash | 14:13 |
| bauzas | reminder : nova meeting in 15 mins | 15:45 |
| dansmith | bauzas: reminder, nova meeting 24 seconds ago | 16:00 |
| bauzas | #startmeeting nova | 16:00 |
| opendevmeet | Meeting started Tue Apr 18 16:00:33 2023 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
| opendevmeet | The meeting name has been set to 'nova' | 16:00 |
| bauzas | dansmith: you beated me on the clock | 16:00 |
| bauzas | walcome falks | 16:00 |
| elodilles | :D | 16:01 |
| elodilles | o/ | 16:01 |
| bauzas | #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting | 16:01 |
| auniyal | o/ | 16:01 |
| bauzas | let's try to do a quick one | 16:01 |
| bauzas | so let's start | 16:01 |
| bauzas | #topic Bugs (stuck/critical) | 16:02 |
| bauzas | #info No Critical bug | 16:02 |
| bauzas | (welp, somehow) | 16:02 |
| gibi | o/ | 16:02 |
| bauzas | #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 13 new untriaged bugs (-5 since the last meeting) | 16:02 |
| bauzas | kudos to gibi | 16:02 |
| bauzas | gibi: any bug you wanna raise today ? | 16:02 |
| gibi | triaged couple of one https://etherpad.opendev.org/p/nova-bug-triage-20230411 | 16:02 |
| bauzas | thanks | 16:02 |
| gibi | nothing to raise today | 16:03 |
| bauzas | very quickly looked at them, thanks for fishing them | 16:04 |
| bauzas | #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster | 16:04 |
| bauzas | so, next in the roster is melwitt | 16:04 |
| bauzas | not sure she's around | 16:04 |
| bauzas | I'll ask her later if she can help | 16:04 |
| bauzas | if not, I'll take the baton | 16:04 |
| bauzas | #info bug baton is being passed to melwitt/bauzas | 16:05 |
| bauzas | #topic Gate status | 16:05 |
| bauzas | #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs | 16:05 |
| bauzas | #link https://etherpad.opendev.org/p/nova-ci-failures | 16:05 |
| bauzas | do people want to discuss about the recent failures we got ? | 16:05 |
| bauzas | I didn't had time to look at logsearch yet | 16:05 |
| Uggla | o/ | 16:06 |
| bauzas | well, fair enough | 16:06 |
| bauzas | let's say I haven't seen yet a lot of failures in my internal gerrit email directory | 16:07 |
| bauzas | moving on so | 16:07 |
| bauzas | #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status | 16:08 |
| bauzas | as always, all greens | 16:09 |
| bauzas | #info Please look at the gate failures and file a bug report with the gate-failure tag. | 16:09 |
| bauzas | #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures | 16:09 |
| bauzas | #topic Release Planning | 16:09 |
| bauzas | so | 16:09 |
| bauzas | #link https://releases.openstack.org/bobcat/schedule.html | 16:09 |
| bauzas | #info Nova deadlines are set in the above schedule | 16:09 |
| bauzas | you'll see some nova details in the above schedule ^ | 16:09 |
| bauzas | basically, | 16:09 |
| bauzas | #info Bobcat-1 is in 3 weeks | 16:09 |
| bauzas | and ditto the stable branch review day | 16:10 |
| bauzas | anything to discuss about the schedule ? | 16:11 |
| bauzas | #topic Review priorities | 16:12 |
| bauzas | #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2) | 16:12 |
| bauzas | #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review | 16:12 |
| bauzas | #topic Stable Branches | 16:12 |
| bauzas | elodilles: your turn | 16:13 |
| elodilles | #info final Xena release (24.2.1) is out - ready to transition stable/xena to EM | 16:13 |
| bauzas | huzzah | 16:13 |
| elodilles | hopefully we haven't merged anything harmful :) | 16:13 |
| bauzas | and I +1d the EM patch | 16:13 |
| bauzas | so we're ready | 16:13 |
| elodilles | yepp, I will +2+W tomorrow morning | 16:13 |
| bauzas | one week in advance nah ? | 16:13 |
| bauzas | if so, \o/ | 16:14 |
| elodilles | almost 1 week, yes :] | 16:14 |
| elodilles | so we are good i think :) | 16:14 |
| bauzas | xena was a nice warrior but we should do yoga now | 16:14 |
| elodilles | yepp | 16:14 |
| elodilles | now the general things: | 16:14 |
| elodilles | #info stable gates are not blocked, but sometimes patches need many rechecks | 16:14 |
| elodilles | #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci | 16:14 |
| elodilles | that's all from me | 16:15 |
| bauzas | cool and thanks | 16:17 |
| elodilles | np | 16:17 |
| bauzas | auniyal: I guess you wanted to add the two other items ? | 16:17 |
| auniyal | #help Please review these backport patches for zed and yoga release | 16:17 |
| bauzas | as a weekly reminder | 16:17 |
| auniyal | will be releasing this week | 16:17 |
| auniyal | #link https://etherpad.opendev.org/p/release-liaison-PatchesToReview | 16:17 |
| bauzas | ack gtk, so I'll try to do homework then | 16:17 |
| auniyal | thats all bauzas, thanks | 16:17 |
| bauzas | auniyal: thanks | 16:17 |
| bauzas | #topic Open discussion | 16:18 |
| elodilles | thanks in advance auniyal :) | 16:18 |
| bauzas | (this time, I'm refreshing) | 16:18 |
| bauzas | aaaand nothing, even after Ctrl-R | 16:18 |
| bauzas | so, anything to say before we end this meeting ? | 16:18 |
| bauzas | I thought we wanted to discuss about some volume detach issues | 16:18 |
| bauzas | but not sure if the reporter is around, can't see jsanemet here | 16:19 |
| auniyal | bauzas, I have a feature spec on dangling volume its on review, is it same topic ? | 16:19 |
| auniyal | #link https://review.opendev.org/c/openstack/nova-specs/+/878757 | 16:20 |
| bauzas | auniyal: nope, jorge wanted to discuss about the volume detach issues we were having in CI | 16:20 |
| auniyal | ack | 16:20 |
| bauzas | but given he's not around, we'll defer it to next week (if so) | 16:20 |
| bauzas | auniyal: fwiw, your spec is part of my review backlog | 16:20 |
| auniyal | thanks bauzas | 16:21 |
| bauzas | okay, then, let's close early | 16:21 |
| bauzas | folks, have a nice day, be it pretty done or early for you :) | 16:22 |
| bauzas | thanks all | 16:22 |
| bauzas | #endmeeting | 16:22 |
| opendevmeet | Meeting ended Tue Apr 18 16:22:21 2023 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:22 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/nova/2023/nova.2023-04-18-16.00.html | 16:22 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/nova/2023/nova.2023-04-18-16.00.txt | 16:22 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/nova/2023/nova.2023-04-18-16.00.log.html | 16:22 |
| opendevreview | Dan Smith proposed openstack/nova master: Remove silent failure to find a node on rebuild https://review.opendev.org/c/openstack/nova/+/880632 | 16:22 |
| opendevreview | Dan Smith proposed openstack/nova master: Stop ignoring missing compute nodes in claims https://review.opendev.org/c/openstack/nova/+/880633 | 16:22 |
| bauzas | dansmith: looking at it then | 16:23 |
| bauzas | heh, first time I'm seeing such gerrit comment : "Code-Review-1 (copy condition: "changekind:TRIVIAL_REBASE OR is:MIN")" | 16:24 |
| dansmith | bauzas: I'm really not trying to nitpick, I just want to make sure we're sending what we should be | 16:27 |
| bauzas | that was me who nitpicked | 16:28 |
| bauzas | anyway; +2d | 16:28 |
| dansmith | bauzas: all the exit paths from that rebuild send a dedicated notification about the "phase" of the rebuild and I just didn't want to add a path that doesn't | 16:28 |
| bauzas | I see your point | 16:28 |
| opendevreview | ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (db) https://review.opendev.org/c/openstack/nova/+/831193 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (objects) https://review.opendev.org/c/openstack/nova/+/839401 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (manila abstraction) https://review.opendev.org/c/openstack/nova/+/831194 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (drivers and compute manager part) https://review.opendev.org/c/openstack/nova/+/833090 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Attach Manila shares via virtiofs (api) https://review.opendev.org/c/openstack/nova/+/836830 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Check shares support https://review.opendev.org/c/openstack/nova/+/850499 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Add metadata for shares https://review.opendev.org/c/openstack/nova/+/850500 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Add instance.share_attach notification https://review.opendev.org/c/openstack/nova/+/850501 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Add instance.share_detach notification https://review.opendev.org/c/openstack/nova/+/851028 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Add shares to InstancePayload https://review.opendev.org/c/openstack/nova/+/851029 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Add helper methods to attach/detach shares https://review.opendev.org/c/openstack/nova/+/852085 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Add libvirt test to ensure metadata are working. https://review.opendev.org/c/openstack/nova/+/852086 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Add virt/libvirt error test cases https://review.opendev.org/c/openstack/nova/+/852087 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Add share_info parameter to reboot method for each driver (driver part) https://review.opendev.org/c/openstack/nova/+/854823 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Support rebooting an instance with shares (compute and API part) https://review.opendev.org/c/openstack/nova/+/854824 | 16:32 |
| opendevreview | ribaudr proposed openstack/nova master: Add instance.share_attach_error notification https://review.opendev.org/c/openstack/nova/+/860282 | 16:33 |
| opendevreview | ribaudr proposed openstack/nova master: Add instance.share_detach_error notification https://review.opendev.org/c/openstack/nova/+/860283 | 16:33 |
| opendevreview | ribaudr proposed openstack/nova master: Add share_info parameter to resume method for each driver (driver part) https://review.opendev.org/c/openstack/nova/+/860284 | 16:33 |
| opendevreview | ribaudr proposed openstack/nova master: Support resuming an instance with shares (compute and API part) https://review.opendev.org/c/openstack/nova/+/860285 | 16:33 |
| opendevreview | ribaudr proposed openstack/nova master: Add helper methods to rescue/unrescue shares https://review.opendev.org/c/openstack/nova/+/860286 | 16:33 |
| opendevreview | ribaudr proposed openstack/nova master: Support rescuing an instance with shares (driver part) https://review.opendev.org/c/openstack/nova/+/860287 | 16:33 |
| opendevreview | ribaudr proposed openstack/nova master: Support rescuing an instance with shares (compute and API part) https://review.opendev.org/c/openstack/nova/+/860288 | 16:33 |
| opendevreview | ribaudr proposed openstack/nova master: Docs about Manila shares API usage https://review.opendev.org/c/openstack/nova/+/871642 | 16:33 |
| opendevreview | ribaudr proposed openstack/nova master: Mounting the shares as part of the initialization process https://review.opendev.org/c/openstack/nova/+/880075 | 16:33 |
| sean-k-mooney | bauzas: we missed talking about the release note for hyperv and vmawre experimental/deprecated status | 16:38 |
| sean-k-mooney | or more speicifclly backporting that to antelope | 16:38 |
| bauzas | shit | 16:39 |
| bauzas | my brain derailed | 16:39 |
| sean-k-mooney | so i would obviosly like to do both (merge on master and backport) | 16:39 |
| sean-k-mooney | so that the warning goes out early | 16:40 |
| sean-k-mooney | and then wait and see what happens with os-win before doing anythin else | 16:40 |
| sean-k-mooney | if the TC retrie os-win in bobcat then we can look at remvoing the supprot in 2024.1 | 16:41 |
| bauzas | sean-k-mooney: my only concern is that the relnotes for 27.0.0 won't see it | 16:42 |
| sean-k-mooney | as long as its not breaking any ci jobs and we have sent the warning i dont think thre is any pressure on us to do anything else | 16:42 |
| bauzas | show* | 16:42 |
| bauzas | so operators may miss it | 16:42 |
| sean-k-mooney | we can proably fix that | 16:42 |
| bauzas | well, they would need to upgrade to latest 2023.1 release before they would see the log, hence my point | 16:43 |
| sean-k-mooney | but they shoudl not just be looking at 27.0.0 before going to 29.0.0 | 16:43 |
| sean-k-mooney | yep but i dont think we will ahve peopel upgradign for 27.0.0 directly to 29.0.0 without any updates to 27.x.y | 16:44 |
| dansmith | I think backporting a reno to antelope is a good idea to increase our warning interval, but I do not think that buys us more time in terms of how soon we can do something | 16:44 |
| sean-k-mooney | its a concern but i think its a minor one | 16:44 |
| dansmith | because people may deploy a .0 and never update | 16:44 |
| sean-k-mooney | maybe | 16:44 |
| dansmith | meaning I don't think we can reasonably deprecate in 2023.2 and remove it in 2024.1 | 16:44 |
| sean-k-mooney | but i think CVEs ectra would force an update | 16:44 |
| dansmith | nobody is forced to update | 16:44 |
| sean-k-mooney | ya what sucks is we agree do deprecate in antelope and we just forgot to merge the patch | 16:45 |
| dansmith | IMHO, this is the extra work we take on by committing to the longer support envelope | 16:45 |
| sean-k-mooney | because it was not assocated with any bug or blueprint | 16:45 |
| bauzas | sean-k-mooney: we had quite the same situation in newton | 16:45 |
| dansmith | yeah, sucks, but.. we just can't rewrite history | 16:45 |
| bauzas | without that cadence | 16:45 |
| bauzas | but we forgot something that merged post-rc1 | 16:46 |
| bauzas | and I still remember the shitstorm that happened next | 16:46 |
| bauzas | it's still engraved in me | 16:46 |
| sean-k-mooney | so removal in 2024.2 it is i guess | 16:46 |
| sean-k-mooney | assuming nothign happens btween now and then | 16:46 |
| bauzas | I'd rather prefer to ask rosmaita again and the tc about the reno tooling things | 16:47 |
| bauzas | to see whether we could forward port the deletion notes to B | 16:47 |
| bauzas | brian's proposal was quite ok to me | 16:47 |
| bauzas | but the tooling has to be correctly documented | 16:47 |
| dansmith | that doesn't change anything about the decision, just the mechanics of the notice, to be clear | 16:48 |
| bauzas | yup, that's why I'm still afraid of removing anything in B | 16:48 |
| bauzas | the plan isn't sold yet | 16:48 |
| dansmith | deprecating? | 16:48 |
| dansmith | we can't remove these in B because we didn't warn about it | 16:48 |
| bauzas | removing anything, and by extension deprecating (in this case) | 16:48 |
| sean-k-mooney | ya like if we really wanted to we could just move the 2023.1 git tag so that 27.0.0 has the release note btu that has other problems so i dont really wnat to go there | 16:49 |
| dansmith | no. | 16:49 |
| sean-k-mooney | bauzas: ya not sure where removal is coming form in b | 16:49 |
| bauzas | sean-k-mooney: well, we can't do this or then the distros would hate us | 16:49 |
| sean-k-mooney | that is not what is beign proposed | 16:49 |
| bauzas | sorry, I meant the general case | 16:49 |
| sean-k-mooney | bauzas: hehe i know | 16:49 |
| sean-k-mooney | but if we really wanted to get it in the 27.0.0 release notes im sure that possibel | 16:50 |
| bauzas | I'm saying I'm still quite unhappy with any change proposing to deprecate or remove any thing in B, including in particular the hyperv driver that we speak | 16:50 |
| sean-k-mooney | anyway i think we can likely move forward with the patch and waith for it to go out in 2024.1 | 16:50 |
| sean-k-mooney | then see whtat the state is for 2024.2 and if its still functioanl at that point or not | 16:51 |
| bauzas | dansmith: I haven't read the tc agenda for today, but do you think they will discuss the slurp things we discussed before the PTG ? | 16:51 |
| sean-k-mooney | bauzas: i find it very unreasoonble to disallow deprecateion or removals in B | 16:51 |
| bauzas | sean-k-mooney: my PTG concern is still legit, we haven't still a solid plan on forward-porting the notes to C | 16:52 |
| sean-k-mooney | but i agree that we can only remove thing in B if they were deprecated in A or older | 16:52 |
| dansmith | bauzas: neither have I so I dunno | 16:52 |
| sean-k-mooney | sure but i dont think we should block the removal of deprecated fucntionalty on resolvign it | 16:53 |
| dansmith | tbh, I'm not getting the problem here | 16:54 |
| dansmith | we should backport a reno to 2023.1 about the deprecation, | 16:54 |
| dansmith | we should have another one in 2024.1 for such a large thing | 16:55 |
| dansmith | we should have a deprecation log message in 2023.1, 2023.2, 2024.1 | 16:55 |
| dansmith | I think bauzas' concern is about remembering to do the extra reno in 2024.1, right? | 16:55 |
| sean-k-mooney | yes bauzas and i swtiched topic slightly to talke about deprecation/removals in B in general | 16:55 |
| bauzas | dansmith: correct | 16:55 |
| sean-k-mooney | yes | 16:55 |
| bauzas | dansmith: your plan looks good then | 16:55 |
| bauzas | provided we don't forget to mention the deprecation in 2024.1 | 16:56 |
| dansmith | sean-k-mooney: well, you seemed to go back to the specific with the "block removing on resolving" | 16:56 |
| sean-k-mooney | well in 2024 we would be annouching that we intend to remvoe it effectivly | 16:56 |
| sean-k-mooney | if that what we decied at that point | 16:56 |
| sean-k-mooney | were as right now we are just saying its untested | 16:57 |
| bauzas | sean-k-mooney: dansmith: I apologize, I mixed two problems | 16:57 |
| dansmith | bauzas: to be honest, the removal of it is not that important, IMHO | 16:57 |
| sean-k-mooney | and deprecated but no plan to remove it in any partical release | 16:57 |
| bauzas | don't disagree | 16:57 |
| bauzas | dansmith: ^ | 16:57 |
| dansmith | bauzas: saying it's deprecated is a lot more important.. we can remove it when it becomes an _actual_ problem | 16:57 |
| bauzas | true | 16:57 |
| bauzas | ok, looks like we're settled then | 16:57 |
| dansmith | which, if it's been long enough, doesn't matter when we do it | 16:57 |
| bauzas | I can vote | 16:57 |
| sean-k-mooney | anyway i need to go to another meeting now | 16:59 |
| sean-k-mooney | bauzas: as an fyi i plan to submit the patch to remove the AZ filter next week when i have time to write it | 16:59 |
| bauzas | ack | 16:59 |
| sean-k-mooney | it was ment to be done like in xena or yoga. i have a version somewhere but im jsut going to do it from scratch | 17:00 |
| bauzas | sean-k-mooney: you know that by merging this without having a tooling in place, we basically leave myself to be responsible of the release note forward-porting, right? :) | 17:01 |
| bauzas | (just saying this here as well, as a side discussion occurs somewhere else) | 17:02 |
| bauzas | https://review.opendev.org/c/openstack/nova/+/863910 is sent to the gate | 17:09 |
| dansmith | so, | 17:12 |
| dansmith | marking it as experimental back then made more sense than I think it does now | 17:12 |
| dansmith | (I realize I'm +2 on that) | 17:12 |
| dansmith | I think we do need to mark it as actually deprecated to be clean here, because we know it has no maintenance horizon, the dependent library is abandoned and in danger, etc | 17:13 |
| sean-k-mooney | dansmith: we are technially doing both | 17:18 |
| sean-k-mooney | its deprecated in the relesae notes | 17:18 |
| dansmith | no it's not | 17:18 |
| sean-k-mooney | but we use experimantal in the logs becasue we did not want to call it deprecated for reasons | 17:18 |
| dansmith | https://review.opendev.org/c/openstack/nova/+/863910/1/releasenotes/notes/hyperv-experimental-antelope-372e18a05cafc295.yaml | 17:18 |
| dansmith | it says "may be removed" but no | 17:18 |
| dansmith | not "deprecated" | 17:19 |
| sean-k-mooney | deprecations: | 17:19 |
| sean-k-mooney | its in the deprecation section | 17:19 |
| dansmith | meh | 17:19 |
| dansmith | it's too vague at this point.. we should be saying it's deprecated and will be removed | 17:20 |
| dansmith | the log is probably even more important than the reno | 17:20 |
| dansmith | 2% of deployments are using hyperv...we really should not leave any room for misinterpreting what we know is going to happen | 17:21 |
| sean-k-mooney | ok im fine with refining it but i was ok with the fact it was in the deprecation section to track that it was deprecated. | 17:23 |
| opendevreview | Merged openstack/nova stable/yoga: Unify placement client singleton implementations https://review.opendev.org/c/openstack/nova/+/858997 | 17:55 |
| opendevreview | Merged openstack/nova stable/yoga: Avoid n-cond startup abort for keystone failures https://review.opendev.org/c/openstack/nova/+/858998 | 18:17 |
| opendevreview | sean mooney proposed openstack/nova master: add hypervisor version weigher https://review.opendev.org/c/openstack/nova/+/880231 | 19:23 |
| opendevreview | sean mooney proposed openstack/nova master: add hypervisor version weigher https://review.opendev.org/c/openstack/nova/+/880231 | 19:25 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!