Earlier  
Posted Nick Remark
#openstack-nova - 2023-01-10
16:20:38 gibi gmann: I don't know the reason either
16:20:38 gmann so we need to test latest placement in master gate only
16:21:17 gmann sean-k-mooney: right but that we do not need on stable osc-placement version right?
16:21:41 sean-k-mooney gmann: correct it can and should use the stable version
16:21:52 gmann I was hesitating to pin placement there as I do not know the original reason ot use latest placement there
16:21:54 sean-k-mooney they do need to be kept in sync however
16:22:06 sean-k-mooney its caputed in teh comme messange here https://github.com/openstack/osc-placement/commit/da8cd4d68b06399c607776db2a704b4578146996
16:22:18 gmann ack
16:22:48 gmann thanks
16:24:33 sean-k-mooney ok i think we have covered those topics and can move on
16:24:42 bauzas I was about to ask
16:24:49 bauzas ok, let's move on then
16:24:54 gmann yeah
16:25:00 bauzas #topic Release Planning
16:25:04 bauzas #link https://releases.openstack.org/antelope/schedule.html
16:25:07 bauzas #info Antelope-3 is in 5 weeks
16:25:16 bauzas (and featurefreeze... :) )
16:25:21 bauzas #info As a reminder, Nova SpecFreeze deadline is this Thursday https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031636.html
16:26:08 bauzas I'll modify launchpad's https://blueprints.launchpad.net/nova/antelope once we're done with reviewing specs
16:26:58 bauzas I have then a question
16:27:07 bauzas #link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031645.html I guess we'll want to have a virtual PTG again ?
16:27:07 bauzas #link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031645.html I guess we'll want to have a virtual PTG again ?
16:27:39 bauzas for the Bobcat planning :)
16:27:55 bauzas (man, haven't but should have voted this time...)
16:28:02 sean-k-mooney can we create teh 2023.2 specs repo after spec freeze
16:28:19 sean-k-mooney i dont recall seeing a vote email go out
16:28:24 bauzas there was one
16:28:28 sean-k-mooney i tought this was selected by the foundation
16:28:51 bauzas nope, sent during your holidaus
16:28:56 sean-k-mooney ok well the foundation has never consicidently sent me vote urls anyway
16:28:58 bauzas hence why you haven't probably seen it
16:29:01 gmann format will be 1 virtual PTG + 1 in-person PTG per year. in-person PTG will be aligned to summit+release
16:29:36 bauzas gmann: any chance to have those physical attendances (I don't like the PTG naming) to be at the start of the release time ?
16:29:46 bauzas for Vancouver, ship is sailed
16:30:25 dansmith sean-k-mooney: I didn't get one either
16:30:50 gmann bauzas: yeah, that is what foundation staff updated that they will try to aligned it with summit and openstack relaese but let's see as it can be challenging too
16:30:52 bauzas dansmith: sean-k-mooney: https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031551.html
16:31:10 dansmith oh, to the list
16:31:19 bauzas 70% of the list was probably on PTO
16:31:24 sean-k-mooney but that vote url is a personal one
16:31:28 sean-k-mooney not one everyone can use right
16:31:33 gmann for vancouver, yes as event is in between of cycle it needs to be that time
16:31:44 sean-k-mooney you are ment to get one to your personal email for all votes
16:31:56 bauzas sean-k-mooney: good point, again, I haven't voted so I haven't tested it
16:32:31 gmann sean-k-mooney: I think it is public vote so anyone can vote with that url but one per IP or so
16:32:37 bauzas anyway, this is done anyway
16:32:42 gmann if I am remembering public vote things correctly
16:32:46 bauzas gmann: fun fact is, voting isn't closed AFAICS
16:33:02 sean-k-mooney perhaps in the tool but the name has been released
16:33:14 bauzas yup, another ship sailed
16:33:18 sean-k-mooney in anycase i can create a 2023.2 folder in the spec repo
16:33:20 gmann ohk :) honestly saying I have not given mush attention to release naming :)
16:33:28 gmann sean-k-mooney: +1
16:33:33 bauzas sean-k-mooney: wait for the spec freeze
16:33:41 opendevreview Merged openstack/nova stable/wallaby: Adapt websocketproxy tests for SimpleHTTPServer fix https://review.opendev.org/c/openstack/nova/+/866194
16:33:41 sean-k-mooney but bauzas if you want to do that after spec freeze we can wait till after thrsday
16:33:42 bauzas sean-k-mooney: or it would perhaps confuse people
16:33:53 bauzas sean-k-mooney: well, I'm not opposed to delegate
16:34:07 sean-k-mooney cool well i ahve done it in the past but lest do it next week
16:34:44 bauzas anyway, I guess we vote for a virtual PTG on end of March ? (that was the original question)
16:35:20 bauzas and we don't say "meh, no, just let's do a physical one at right the middle of the release, and go f*** our deadlines !"
16:35:22 bauzas :D
16:36:16 bauzas I hear crickets, so I decide so
16:36:19 elodilles well, that is the usual PTG time, so i think it is not something to vote for :)
16:36:23 gmann not sure physical one can be utilized same as our normal PTG but can plan for some operaotr oriented discussions
16:36:41 bauzas #info we'll have a virtual Nova PTG on March 27-31
16:36:45 gmann virtual one in March will be the normal vPTG we have for cycle
16:36:48 bauzas I'll register our name :)
16:37:08 bauzas gmann: honestly, I don't expect much more from what we currently have at the Forum
16:37:13 bauzas gmann: but let's be creative
16:37:17 gmann bauzas: yeah.
16:37:42 bauzas if we really need to s/Forum/PTG to have more people coming, I'm not opposed to a rebranding
16:37:53 elodilles some teams do mid-cycle PTG-s, so the in-person one can be considered such, i guess
16:37:56 gmann we asked same PTG fomat questions on vancouver PTG but that is not answer yet
16:38:23 bauzas elodilles: given the Summit will be around Spec Freeze, that's gonna be fun
16:38:27 gmann I think in openstack-discuss ML but anyways let's see
16:38:50 bauzas elodilles: but we could do 'review sprints' or 'implementation sessions'
16:39:03 bauzas if that helps people wanting to come :)
16:39:10 gmann +1. good idea
16:39:16 bauzas I guess we're done on that topic
16:39:31 bauzas moving on
16:39:36 bauzas #topic Review priorities
16:39:44 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:39:50 bauzas #info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review
16:40:13 bauzas I'll slowly but progressively use this label for knowing what to review
16:40:17 bauzas so you know about it
16:40:25 bauzas next topic (we only have 20 mins)
16:40:29 bauzas #topic Stable Branches
16:40:34 bauzas elodilles: happy to see you back
16:40:41 elodilles :)
16:40:49 elodilles we mostly discussed, but
16:41:10 elodilles #info stable branches seem to be unblocked / OK -- except placement, osc-placement, ...
16:41:33 elodilles thanks gmann for fixing the tox4 issues on stable branches!
16:41:45 elodilles #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:41:54 elodilles and maybe one more thing:
16:41:55 gmann for pin not fix :)
16:42:13 elodilles gmann: yepp, a good workaround for now ;)
16:42:53 elodilles so maybe we should do nova stable releases as there are already some merged content on zed, yoga and xena
16:43:29 elodilles and a small side track: i would want some stable core opinions about my comment here: https://review.opendev.org/c/openstack/nova/+/867912
16:43:46 elodilles as the zed release might depend on that

Earlier   Later