Wednesday, 2024-11-20

opendevreviewTakashi Kajinami proposed openstack/nova master: Replace deprecated FormatChecker.cls_checks  https://review.opendev.org/c/openstack/nova/+/93573301:37
opendevreviewTakashi Kajinami proposed openstack/placement master: Replace deprecated FormatChecker.cls_checks  https://review.opendev.org/c/openstack/placement/+/93573401:40
opendevreviewTakashi Kajinami proposed openstack/nova master: Migrate MEM_ENCRYPTION_CONTEXT from root provider  https://review.opendev.org/c/openstack/nova/+/92181402:45
opendevreviewTakashi Kajinami proposed openstack/nova master: Detect AMD SEV-ES support  https://review.opendev.org/c/openstack/nova/+/92568502:45
opendevreviewTakashi Kajinami proposed openstack/nova master: Add hw_mem_encryption_model image property  https://review.opendev.org/c/openstack/nova/+/92770602:45
opendevreviewTakashi Kajinami proposed openstack/nova master: libvirt: Launch instances with SEV-ES memory encryption  https://review.opendev.org/c/openstack/nova/+/92610602:47
opendevreviewTakashi Kajinami proposed openstack/placement master: Replace deprecated FormatChecker.cls_checks  https://review.opendev.org/c/openstack/placement/+/93573403:17
opendevreviewmelanie witt proposed openstack/nova master: Add [quota]unified_limits_resource_(strategy|list)  https://review.opendev.org/c/openstack/nova/+/92402503:29
melwittdansmith, sean-k-mooney: I also updated the config options patch to reflect the latest PS of the spec ^03:31
opendevreviewTakashi Kajinami proposed openstack/nova master: Replace deprecated FormatChecker.cls_checks  https://review.opendev.org/c/openstack/nova/+/93573304:10
*** __ministry is now known as Guest24304:26
opendevreviewmelanie witt proposed openstack/nova master: Add [quota]unified_limits_resource_(strategy|list)  https://review.opendev.org/c/openstack/nova/+/92402504:33
opendevreviewRajesh Tailor proposed openstack/nova master: Add support for showing finish_time  https://review.opendev.org/c/openstack/nova/+/92893305:46
opendevreviewMerged openstack/nova master: Remove workaround for eventlet < 0.27.0  https://review.opendev.org/c/openstack/nova/+/93072606:01
*** __ministry is now known as Guest25306:54
fricklerbauzas: (or other cores) seems we still do need sean-k-mooney's fix for os-vif https://review.opendev.org/c/openstack/os-vif/+/935653 in order to be able to get https://review.opendev.org/c/openstack/os-vif/+/932436 in in order to unblock oslo.utils in reqs, please have a look09:54
opendevreviewTakashi Kajinami proposed openstack/os-vif master: DNM: Testing 932436  https://review.opendev.org/c/openstack/os-vif/+/93575510:08
opendevreviewMerged openstack/nova-specs master: Re-propose config option for behavior of unset unified limits  https://review.opendev.org/c/openstack/nova-specs/+/93439110:24
gibielodilles: Hi! Can I get review on the next set of patches in the backort series of https://review.opendev.org/q/topic:%22bug/2085975%2212:12
gibifrickler: I fast approved the os-vif change to get things unblocked12:15
elodillesgibi: looking12:23
elodilles+2'd them12:29
gibielodilles: thanks a lot12:50
elodillesnp12:55
tkajinamsean-k-mooney, hi o/ Could you check my reply in https://review.opendev.org/c/openstack/nova/+/931582 when you have time ?14:20
sean-k-mooneydo you plan to add that funcitonaltiy in oslo in the future?14:21
sean-k-mooneyim ok with having it in nova in the interim but i think it woudl be better to have it in oslo eventurally14:22
tkajinamyeah I can move it to oslo.utils14:22
sean-k-mooneyok i wont block on that then we can just do that when it makes sense to do so14:23
tkajinamI also replaced netifaces used in oslo.utils by psutil so the proposed implementation is consistent with the ones we maintain in oslo.utils14:23
tkajinamso there is not strict blocker for future migration14:24
sean-k-mooneyim not sure if nova is already usign psutils but i was hoping to aovid a direct dep if we were not14:24
tkajinamit does.14:24
tkajinamhttps://github.com/openstack/nova/blob/master/requirements.txt#L5114:24
sean-k-mooneyhttps://github.com/openstack/nova/blob/e8a544f0e1134a4b260720cc634ad1997f936d6d/nova/virt/libvirt/volume/quobyte.py#L2214:25
sean-k-mooneyfor that14:25
sean-k-mooneyhttps://github.com/openstack/nova/blob/e8a544f0e1134a4b260720cc634ad1997f936d6d/nova/virt/libvirt/volume/quobyte.py#L55-L6214:25
tkajinamit's for quobyte, yeah14:25
sean-k-mooneythat code looks suspect as we really shoudl not be trying to look at systemd and if its running14:25
sean-k-mooneybut ok14:25
sean-k-mooneysince its already a dep it does not impact packaging14:26
tkajinamwe deprecated quobyte support so that code may go away next cycle14:26
sean-k-mooneywell it moving form optional to requried but its also requried because fo oslo so i guess its fine14:26
tkajinamyes14:26
sean-k-mooneyok so i have only one other comment, there is no new testcoverage for get_machine_ips14:27
sean-k-mooneyyou removed https://review.opendev.org/c/openstack/nova/+/931582/6/nova/tests/unit/compute/test_utils.py14:28
sean-k-mooneythe error case but didnt provide any repalcement coverage. and with the poison that impoiles this is not called in other tests or is mocked14:28
sean-k-mooneyso i dont think we have any coverage of that code.14:28
sean-k-mooneycan you add a small testcase that mocks psutil.net_if_addrs() and jsut cover the body of the for 14:30
sean-k-mooneyi.e. i.e. the removal of the ipv6 adresses? im not sure how hard that would be 14:30
sean-k-mooneysory its not remivng the ipv6 adresses14:31
sean-k-mooneybtu it is stripign the content after %14:31
tkajinamthat removes scope from ipv6 address14:32
sean-k-mooneyi guess we didnt have coverate for that before...14:32
tkajinamlet me update the change to include unit tests. That's a very good point14:32
sean-k-mooneyso its technially not a regression14:32
sean-k-mooneyim kind of +1.514:32
sean-k-mooneyi dont have a sense of how worried i shoudl be about a regression in that code 14:33
sean-k-mooneyyou didnt actully chagne andy of the logic that is processing the adresses14:33
sean-k-mooneyyou just removed the try excpet14:34
sean-k-mooneypresumably because  `psutil.net_if_addrs().items()` alwasy returns a dict even if its an empty one14:35
sean-k-mooneyor well an iterator over a mapping/dict view 14:35
tkajinamyeah14:36
sean-k-mooneytkajinam: im kind of feelign that the missing unit test is a prexisiting bug and i should not ask you to fix it while your are fixing the netifaces issue14:36
tkajinamsean-k-mooney, that's also ok. I can add some test coverage in an independent follow-up14:37
tkajinamyeah it reminds me that I only removed the test case because the exception may no be raised in a new implementation and there are no actual test coverage for normal cases14:38
sean-k-mooneyi left a coment to that effect and a +214:40
sean-k-mooneyif you have time to add coverage in a followup then that great if not its ok14:40
sean-k-mooneyill leave it to others to disagree on the reivew if they feel differently14:41
tkajinamsean-k-mooney, thank you !14:42
sean-k-mooneyfrickler: looks liek even with the exteneed timeout it can still sometiems fail14:44
sean-k-mooneyi think for now it would be best to skip that test when using the native driver14:45
sean-k-mooneyit always passes for the ovs-vsctl one and we can revisti this once the current set of release are done14:45
sean-k-mooney*requirements bumps14:45
sean-k-mooneyunfortunetly we do not capture the ovs logs in this job but i suspect there might be an error of some kidn that we can see14:49
sean-k-mooneys/can see/can't see/14:49
ildikovbauzas: sean-k-mooney: Hi, I'm pinging you about the Bridging the Gap effort that we last discussed at the recent PTG.15:10
ildikovWe talked about some simple improvements for Nova, like documenting your process to set priorities for the work that's happening during release cycles.15:10
ildikovI was looking into the Nova docs a little bit, and was doing a Google search on this topic as well to see what a newcomer might find when looking for information about how to work with the Nova team.15:11
ildikovI found a page in the Nova docs that talks about specs, blueprints, etc: https://docs.openstack.org/nova/latest/contributor/blueprints.html15:12
ildikovIt looks like a good place to add some additional information about processes that the team is using throughout release cycles to organize your work.15:12
ildikovWhat do you think?15:12
sean-k-mooneythat is one place but not the only one we have15:13
sean-k-mooneythis is the starting point https://docs.openstack.org/nova/latest/contributor/contributing.html15:14
sean-k-mooneythe doc you linked to is fpr mew featire [;ammomg15:14
sean-k-mooneyhere you will see the more detailed docs https://docs.openstack.org/nova/latest/contributor/index.html15:15
sean-k-mooneyildikov: we maintian an entire subseciton of our docs "the contibutor guide/docs" 15:16
sean-k-mooneyso we can add more contet to this as required15:16
sean-k-mooneya high level overview of our process is here https://docs.openstack.org/nova/latest/contributor/process.html15:17
sean-k-mooneyildikov: https://docs.openstack.org/nova/latest/contributor/process.html#why-do-we-have-priorities is where we discuss priorities but we have nto enforced them for some time15:17
sean-k-mooneythis was the section we added most recently https://docs.openstack.org/nova/latest/contributor/process.html#what-the-review-priority-label-in-gerrit-are-use-for 15:18
sean-k-mooneyto document how to sue review priority label but bauzas proposed a diffent way to do it via etherpads last cycle which has more or less replaced it15:19
sean-k-mooneywe also have old documetion of the runwasy system we used before that https://docs.openstack.org/nova/latest/contributor/process.html#runways15:19
sean-k-mooneyildikov: so i can see why it might be confusitn since we still have to docs for the previous ways of working15:19
sean-k-mooneyildikov: this is somthing that is continuiously evloving as we try thigns for a release or two and then try somethign new 15:20
sean-k-mooneyso nova has a lot of docs on this topic already but most have not been updated for  a few releases15:21
sean-k-mooneyildikov: that partly why i tough the fedback toward nova was rather unfare in the ptg discussions15:22
sean-k-mooneyildikov: it seamed to ignroe all of the existing doc we had and the efforts we had made to make it transparent15:23
dansmithmelwitt: okay I see, it's being echoed once because of the manage_output=$() and once for the [[ $manage_output =~ SUCCESS ]]16:06
dansmithmelwitt: so it might be better to do this:16:08
dansmithnova_manage blah | tee /tmp/output16:08
dansmithif grep SUCCESS /tmp/output;16:08
dansmithso we get one copy16:09
melwittthe job output is so hard to parse for me :( ok, I'll try that16:10
dansmithalso I just realized you're not checking the return code and just looking for the SUCCESS, but a script will be using the former, so we should probably as well yeah?16:10
dansmithyeah I want the job output to be easier to read for sure and not stuffing large multi-line outputs into vars will help I think16:10
melwittyeah that would work, originally I didn't have it returning non zero for the warning case and I didn't think to change it16:12
melwittI'll do that also16:12
ildikovsean-k-mooney: thank you for sharing all the links, and some details on how the documentation has been evolving18:52
ildikovsean-k-mooney: I'm sorry the feedback towards the documentation felt unfair. It seems like there might be a challenge for newcomers and casual contributors to find their ways around the currently existing docs, where the disconnect might be.18:57
ildikovsean-k-mooney: You mentioned that some of the docs haven't been updated in a while now. Which parts of the docs should be updated or removed, if any, to accurately reflect how the Nova team works today?18:59
opendevreviewmelanie witt proposed openstack/nova master: nova-manage: Add flavor scanning to migrate_to_unified_limits  https://review.opendev.org/c/openstack/nova/+/92411019:13
melwittsean-k-mooney: you are fast :)19:23
sean-k-mooneyi happend ot be doing my "finsih the day be going through my emails" routine when the notificaoin came in19:25
melwittwoohoo19:26
sean-k-mooneyill try and review the second patch again tomorrow19:28
melwittcool, thank you19:29
sean-k-mooneyi have an older veriosn checked out in one... of my devstack vms19:30
sean-k-mooneyi might see if i can try enabeling it and test the basics19:30
melwittthe more testing the better :)19:30
melwittI realized it wouldn't be the right thing to validate resource classes (for quotas) in init_host() bc that's a nova-compute thing and the quota checking happens in nova-api and nova-conductor. so I'm looking for a similar spot I can add the validation for startup19:33
melwittoh derp, init_host() can be added for any service I see now19:39
melwittnova-api needs to be different though bc it won't go through nova.service I don't think19:41
melwittok the wsgi app does use a nova Service but calls only Service.create()19:44
sean-k-mooneyit does not enven need to be init_host19:45
sean-k-mooneywe just need a early point to hook after the config is parsrced19:45
sean-k-mooneyso the post start hook woudl work too19:45
sean-k-mooneyactully pre_start_hook would work too19:47
sean-k-mooneybut ya init_host is my go too 19:47
sean-k-mooneymelwitt: if your feellign laze it technially could go in __init__ https://github.com/openstack/nova/blob/e8a544f0e1134a4b260720cc634ad1997f936d6d/nova/manager.py#L92 but ya init_host or pre_start_hook are proably better19:50
melwittsean-k-mooney: I think the nova-api wsgi app doesn't go through init_host or pre_start_hook bc it doesn't call Service.start(). so that has to either be done differently or go into __init__ or Service.create19:52
sean-k-mooneyis that true... it might be i tough it was common but you might be right19:53
sean-k-mooneyi didnt think the manager part changed between the too19:53
dansmithI'm quite sure melwitt is right here19:54
dansmiththere's really no service lifecycle for it under wsgi19:54
sean-k-mooneysure but this is not part of the service 19:54
sean-k-mooneyits part of the manager19:54
melwittsean-k-mooney: I was looking at this https://github.com/openstack/nova/blob/master/nova/api/openstack/wsgi_app.py#L5219:54
sean-k-mooneythe service calls it but init_host is a methond on the manager19:54
dansmithcalled by the service stuff though I think19:55
melwittnova-api has no manager, no?19:55
sean-k-mooneysshhh with you logic and correctness19:56
sean-k-mooneyyour right it does not19:56
melwitt😂 19:56
melwittI'm wrong most of the time, so there's that19:56
sean-k-mooneythat has not been my expnce  but if you say so19:57
melwittheh19:57
sean-k-mooneytaking a step back19:58
sean-k-mooneywe are just talking about validating the config right19:58
melwittright19:58
sean-k-mooneydoes oslo allow ues to register a callback for that on the config opt19:58
melwitthm, dunno but I'll look19:58
melwittnot seeing something like that in https://github.com/openstack/oslo.config/blob/master/oslo_config/cfg.py20:01
sean-k-mooneyso i know we can define our own otp types20:01
sean-k-mooneyand for string we have the ablity to provide enum vlaues20:01
melwittwe need dynamic enum (from os-resource-classes standard classes) and a regex for CUSTOM_stuff I think20:02
sean-k-mooneywell i was thinking of inheriting form listOpt20:03
sean-k-mooneyand just adding the validation 20:04
sean-k-mooneybasically providing a limitListOPT class20:04
melwittah ok20:05
melwittthat sounds interesting. I'll check it out20:05
sean-k-mooneylooking at how its implemted fro string20:06
sean-k-mooneyhttps://github.com/openstack/oslo.config/blob/68cefad313bd03522e99b3de95f1786ebea45d4b/oslo_config/types.py#L6820:06
sean-k-mooneywhen you create and isntance of the opt you can provide choices (for a enum) or a regex20:07
sean-k-mooneyand then the __call__ method actully does the validation20:07
melwittthat's cool20:07
sean-k-mooneyand raise a valueError if it invalid20:07
sean-k-mooneyhttps://github.com/openstack/oslo.config/blob/68cefad313bd03522e99b3de95f1786ebea45d4b/oslo_config/types.py#L141-L17020:07
sean-k-mooneyso if you inherited form List your call could call super which would provide a list and you could just loop over all the values and check if they were valid20:09
sean-k-mooneyif yes just return the result form the call to super else rais20:09
sean-k-mooneymelwitt: im not sure if that is overkill but its doable20:09
sean-k-mooneyand it keeps the valdiation in teh config code so thats nice cause it will work for the api the same as everything else20:10
sean-k-mooneyanyway o/20:11
melwittwe could show off pro level oslo.config usage20:11
melwittthanks for the ideas. seeya tomorrow o/20:11
fricklersean-k-mooney: sorry if I missed that in scrollback, but https://review.opendev.org/c/openstack/os-vif/+/935653 failed in gate with the error it is supposed to fix, iiuc you wanted to skip that check completely, then?20:56
sean-k-mooney[m]ya i didnt get around to pushing a patch but i was going to make that test skip if the native driver was used20:57
sean-k-mooney[m]i just finished dinner but i can update the patch to do that in a little bit20:58
sean-k-mooney[m]we have 2 drivers ovs-vsctl and the nantive python on. its only the native one that sometimes times out20:59
opendevreviewsean mooney proposed openstack/os-vif master: address test stablity under load  https://review.opendev.org/c/openstack/os-vif/+/93565321:22
sean-k-mooneyfrickler: ^ updated to skip21:22
sean-k-mooneythe rest of the change is technially not needed but it does not hurt so i kept it21:22
opendevreviewTakashi Kajinami proposed openstack/os-vif master: Clean up Windows support  https://review.opendev.org/c/openstack/os-vif/+/93243621:23
sean-k-mooneyi rebsased and reappoved ^ on top so hopefuly that will pass and we can merge both soon21:24
fricklerthx, will check for results tomorrow21:27
opendevreviewCyril Roelandt proposed openstack/python-novaclient master: Replace glanceclient with openstacksdk  https://review.opendev.org/c/openstack/python-novaclient/+/93127621:44
opendevreviewmelanie witt proposed openstack/nova master: nova-manage: Add flavor scanning to migrate_to_unified_limits  https://review.opendev.org/c/openstack/nova/+/92411021:54
dansmithmelwitt: why the most recent change?21:56
dansmithdid checking the rc not work?21:56
dansmithbecause if not, that needs fixing I think21:56
dansmithoh I see, you kept the output check without the ... output21:56
melwittdansmith: yeah :( dumb22:11
sean-k-mooneydansmith: melwitt: https://review.opendev.org/c/openstack/os-vif/+/935653 passed with the test skip woudl one of ye mind reappoving that to unblock the follow up patch which is holding up the oslo requirement bump23:54

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