Tuesday, 2023-03-28

opendevreviewNobuhiro MIKI proposed openstack/nova-specs master: Re-propose "Add maxphysaddr support for Libvirt" for 2023.2 Bobcat  https://review.opendev.org/c/openstack/nova-specs/+/87875309:54
opendevreviewKonrad Gube proposed openstack/nova master: Use Cinder's os-extend_volume_completion volume action.  https://review.opendev.org/c/openstack/nova/+/87356009:58
opendevreviewAmit Uniyal proposed openstack/nova-specs master: Add cleanup flag spec to remove dangling volumes  https://review.opendev.org/c/openstack/nova-specs/+/87875710:21
opendevreviewAmit Uniyal proposed openstack/nova-specs master: Add cleanup flag spec to remove dangling volumes  https://review.opendev.org/c/openstack/nova-specs/+/87875710:45
opendevreviewMoritz Wanzenböck proposed openstack/nova master: Implement extend_volume for local devices  https://review.opendev.org/c/openstack/nova/+/87876311:41
gibibauzas: I will be late from the start today due to an internal meeting. hopefully it will be a quick one (max 30min)12:14
gibithen I have another internal call from 15:00-15:30 UTC 12:15
bauzasack no worries12:16
kashyapbauzas: Is it still the "operator hour" now? - https://etherpad.opendev.org/p/oct2022-ptg-operator-hour-nova12:17
kashyaps/still//12:17
bauzaskashyap: at 15pm UTC https://ptg.opendev.org/ptg.html12:18
bauzas3pm whoops12:18
bauzasie. we will start the Nova vPTG session in ~47 mins,12:18
bauzasand then we will have the operator hour in ~2h47mins12:19
kashyapYep, nod.  Thx!12:20
* bauzas goes offline for 20 mins12:26
bauzasNova vPTG sessions start now :)13:03
artomWhat are we starting with? The retrospective? I'm visiting a daycare for baby in ~45 minutes, so I'll miss the first few topics13:14
opendevreviewJorge San Emeterio proposed openstack/nova master: libvirt: Check if VIF MTU matches network MTU  https://review.opendev.org/c/openstack/nova/+/85236713:15
bauzascourtesy ping list for antelope retro : gibi13:19
bauzasartom: https://ptg.opendev.org/ptg.html13:22
bauzasplacement patch https://review.opendev.org/c/openstack/placement/+/87676813:56
opendevreviewRajesh Tailor proposed openstack/nova master: Fix trivial doc issues  https://review.opendev.org/c/openstack/nova/+/87877914:27
opendevreviewMoritz Wanzenböck proposed openstack/nova master: Implement extend_volume for local devices  https://review.opendev.org/c/openstack/nova/+/87876314:29
opendevreviewJorge San Emeterio proposed openstack/nova master: Have host look for CPU controller of cgroupsv2 location.  https://review.opendev.org/c/openstack/nova/+/87312714:32
opendevreviewRajesh Tailor proposed openstack/nova master: Fix trivial doc issues  https://review.opendev.org/c/openstack/nova/+/87877914:35
bauzaswe're taking a break until 3pm UTC and then operator hour14:46
bauzasetherpad for operator hour is https://etherpad.opendev.org/p/march2023-ptg-operator-hour-nova14:46
auniyal__melwitt, ^^ unified limit topic in PTG15:05
opendevreviewMoritz Wanzenböck proposed openstack/nova master: Implement extend_volume for local devices  https://review.opendev.org/c/openstack/nova/+/87876315:25
dansmithwangrong: hi15:27
bauzaswangrong: I took notes on https://etherpad.opendev.org/p/generic-vdpa at the bottom of the page15:28
wangronghi15:28
dansmithwangrong: have you submitted a change to gerrit before?15:29
dansmithwangrong: the general procedure here would be to create a change in gerrit that adds a new file in nova-specs/specs/2023.2/approved something like "generic-vdpa-support.rst"15:31
dansmithwangrong: that file should start a a copy of the template, which is this: https://opendev.org/openstack/nova-specs/src/branch/master/specs/2023.2-template.rst15:31
dansmithwangrong: we are recommending that you copy the template to your spec file, and then fill out the "problem description" and "use cases" sections first, and get that submitted15:32
dansmithwangrong: here is an example of a spec that I have proposed, so you can see how it should look when you submit it: https://review.opendev.org/c/openstack/nova-specs/+/87729115:33
dansmithwangrong: I copied the template to my approved/compute-object-ids.rst file and then filled out the details15:33
dansmithdoes that make sense?15:33
wangrongdansmith: yes,  make sense, I will fill that template. For gerrit maybe will not be a problem.15:47
dansmithwangrong: okay cool, we can ask nova and neutron people to comment on the spec because it sounds like people from both projects will need to contribute15:48
bauzasauniyal__: ping about the Bobcat planning16:25
*** sfinucan is now known as stephenfin17:20
gibiDo you know Adri2000's IRC nick? I looked into the active instance during shelving issue he raised today and I might see what he saw in https://paste.opendev.org/show/bpd9AT9CA09O22eHHchd/17:25
gibinova reports the instance as active/running while the snapshot is uploaded to glance17:26
melwittbauzas: re: unified limits, I had hoped johnthetubaguy might be at the vPTG (I think he was at the last one) bc he's the one who was going to try out the initial exoerimental version of nova unified limits. I have been thinking about whether it's a good time now to implement the migration tools (forklift nova limits from nova db to keystone db) and write proper documentation, if there are no major issues that need to be fixed first that17:32
melwitt we know of17:32
bauzasgibi: that's his nick :)17:33
melwittI do have a bug open and patch proposed for a unified limits quota bug around unshelving an offloaded instance but other than that, I don't know of any problems17:33
bauzasI can ask him to join the channel if he isn't17:33
bauzasmelwitt: ack, sure17:33
bauzasmelwitt: fwiw, I haven't marked the unified limits topic as done, so we can discuss it later in the week if you want17:34
bauzasand folks, sorry about my chairing of the vPTG, I was pretty bad at that17:34
bauzasbad phrasing, bad timings17:34
bauzasI hope I'll be clearer tomorrow17:35
melwittbauzas: ok. I guess if we get everything else topics done, I don't think the unified limits topic (without any operator feedback) is requiring of "in person" discussion17:36
bauzasmelwitt: btw. given your tz, don't hesitate to add your nick on the topics you want to attend17:37
bauzasI know how 1pm UTC is damn early for you, so please help me making sure you can join the most important ones for you :)17:38
melwittI am thinking to create a specless blueprint (or something) to propose it and people can see what they think. it would be basically implementing the last bit of the spec and removing the "experimental do not use this driver" phrase on the config option help17:38
melwittbauzas: sure, thank you17:38
bauzasmelwitt: sounds good to me about the specless bp, and that's a good signal flag that I won't miss when writing the cycle highlights17:39
melwittack17:39
bauzasmelwitt: that said, hold on, considering the fact that Bobcat is non-SLURP17:40
melwittbauzas: ah right, good point. I wondered about that too17:40
bauzasif we flip the defaults now, we'll now to forward-port that in our C release notes17:40
bauzasbecause ops would miss the B relnotes if they jump straight17:40
bauzasmelwitt: I'm not opposed to flip the defaults in B17:41
bauzasmelwitt: I just wanna discuss with the team about how we ensure we don't miss anything in the C relnotes17:41
melwitt++17:42
bauzasdansmith: do you know btw. if the reno team worked on some reno magical flag for saying 'this is something you should also document for the next branch' ?17:43
melwittbauzas: to be clear, I'm not thinking of changing the defaults in B but to just add the "migrate nova quota limits to keystone" script and the docs. maybe it would be best to let that bake for B before flipping defaults in C? not sure17:43
bauzashah, my bad17:44
bauzasthen the problem remains, the migration would need to be performed in C if not done in B17:44
melwittthe migration isn't mandatory fwiw, operators can today just add their limits via the keystone API. the script would just be to make it extra easy if they want to use it17:46
bauzasyeah I remember17:46
melwittthey will either way have to add their own limits via keystone API to add other placement resources such as vGPU or whatever they want17:46
melwittkk17:46
melwitt(thinking out loud) maybe it would be good to hook the forklift script into online_data_migrations in C if we decide to flip the default in C ... bc unified limits default closed (limit of 0) so if they don't make their limits in keystone, all their quota would start being denied. it would be a major major problem to miss that upgrade step of adding limits in keystone if the default is changing. I'll write all of this up in the17:53
melwitt blueprint for discussion or maybe a small spec17:53
* bauzas needs to end his day now but finishes on a bitter taste due to https://review.opendev.org/c/openstack/nova/+/878693 constantly failing18:01
bauzaslooks like we have an ovn agent gone on grenade-multinode job18:02
dansmithbauzas: nope, I dunno18:13
*** efried1 is now known as efried18:22
opendevreviewsean mooney proposed openstack/nova master: Allow discard with virtio-blk  https://review.opendev.org/c/openstack/nova/+/87879518:53
opendevreviewCarl Morris proposed openstack/nova master: Fix a typo in this URL: https://docs.openstack.org/nova/latest/admin/availability-zones.html  https://review.opendev.org/c/openstack/nova/+/87879719:18

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!