Thursday, 2020-04-02

*** gyee has quit IRC00:08
*** rs91 has joined #openstack-nova00:11
openstackgerritGhanshyam Mann proposed openstack/nova master: Add new default roles in security group policies  https://review.opendev.org/71679700:13
*** rs91 has quit IRC00:15
*** ociuhandu has joined #openstack-nova00:34
*** mlavalle has quit IRC00:36
openstackgerritGhanshyam Mann proposed openstack/nova master: Add test coverage of existing server diagnostics policies  https://review.opendev.org/71680000:37
*** ociuhandu has quit IRC00:38
brinzhang_gmann:I think you mean I should merged https://review.opendev.org/#/c/716679 to https://review.opendev.org/#/c/716679, right?00:39
gmannbrinzhang_: that is just example patch i showed instead of comment which was little hard to explain. i will abandon this once you do those changes in your patch.00:40
brinzhang_gmann: I think I know what you want to say, if the user want to swap, need to check the v2.85 and swap policy,00:42
brinzhang_gmann: if the user want to swap + update, they should check update policy for d-o-t, because of other parameters we doesnot allow to update (update only)00:43
gmannbrinzhang_: swap policy check for swap only or update+swap both. swap only can be with any microversion00:43
brinzhang_yes00:43
gmannbrinzhang_: correct. because that is place where we know request is for update00:44
brinzhang_and I can say, swap policy can do anything in update api, contains update policy00:45
brinzhang_gmann: I will update and add the these test said by gibi00:47
gmannbrinzhang_: yeah, tests covering all those cases will be good00:48
openstackgerritGhanshyam Mann proposed openstack/nova master: Introduce scope_types in server diagnostics  https://review.opendev.org/71680300:57
openstackgerritGhanshyam Mann proposed openstack/nova master: Add new default roles in security group policies  https://review.opendev.org/71679301:05
*** Liang__ has joined #openstack-nova01:08
openstackgerritGhanshyam Mann proposed openstack/nova master: Add new default roles in server diagnostics policies  https://review.opendev.org/71680501:08
*** N3l1x has quit IRC01:09
brinzhang_gmann: context.can(va_policies.POLICY_ROOT % 'swap') this policy check, does we need to add target={} in it?01:30
openstackgerritGhanshyam Mann proposed openstack/nova master: Pass the actual target in server diagnostics policy  https://review.opendev.org/71681001:31
openstackgerritmelanie witt proposed openstack/nova master: Move nova-manage placement heal_allocations to nova-audit  https://review.opendev.org/70878801:36
*** zhanglong has joined #openstack-nova01:40
melwittgmann: hey, just to clarify, if I understand correctly we're going to address the warning log issue in a later patch before FF with the plan being to remove the warning log and use Upgrade reno instead? and we'll have a nova doc page explaining the detail of the change in defaults with instructions for users on how to review the new defaults and use them? (enforce_scope = True and how to generate new defaults for review)?01:51
*** links has joined #openstack-nova02:17
*** tetsuro has quit IRC02:50
*** mkrai has joined #openstack-nova02:54
*** links has quit IRC03:00
*** ccamacho has quit IRC03:03
*** sapd1_x has joined #openstack-nova03:10
*** Liang__ is now known as LiangFang03:22
*** tetsuro has joined #openstack-nova03:30
*** igordc has quit IRC03:42
openstackgerritBrin Zhang proposed openstack/nova master: Separate update and swap volume policies  https://review.opendev.org/71119403:45
openstackgerritGuo Jingyu proposed openstack/nova master: WIP: nova supports password encrypted VNC  https://review.opendev.org/62233603:46
*** mkrai has quit IRC03:48
*** mkrai_ has joined #openstack-nova03:48
brinzhang_gibi, gmann: I addressed your comments in https://review.opendev.org/#/c/711194/11, but when I want to add the "policy check fails for swap + update due to update policy failure" case, that cannot get what I want, see http://paste.openstack.org/show/791501/03:48
brinzhang_gibi, gmann: Anything I missed?03:48
*** evrardjp has quit IRC04:36
*** evrardjp has joined #openstack-nova04:37
*** amodi has quit IRC04:47
*** udesale has joined #openstack-nova04:56
*** sapd1_x has quit IRC05:02
*** yaawang has quit IRC05:05
*** yaawang has joined #openstack-nova05:05
*** threestrands has joined #openstack-nova05:06
*** fnordahl has joined #openstack-nova05:10
*** ratailor has joined #openstack-nova05:13
*** sapd1_x has joined #openstack-nova05:14
*** links has joined #openstack-nova05:25
*** ociuhandu has joined #openstack-nova05:58
*** ociuhandu has quit IRC06:02
*** spatel has joined #openstack-nova06:20
*** mnasiadka has quit IRC06:21
*** mnasiadka has joined #openstack-nova06:21
*** ociuhandu has joined #openstack-nova06:23
*** spatel has quit IRC06:25
*** sapd1_x has quit IRC06:29
*** vishalmanchanda has joined #openstack-nova06:30
*** nightmare_unreal has joined #openstack-nova06:31
*** zhanglong has quit IRC06:39
*** zhanglong has joined #openstack-nova06:40
*** sapd1_x has joined #openstack-nova06:41
*** mkrai_ has quit IRC06:52
*** mkrai has joined #openstack-nova06:52
*** dklyle has quit IRC06:53
*** david-lyle has joined #openstack-nova06:53
*** gary_perkins has quit IRC06:55
*** ccamacho has joined #openstack-nova06:56
*** tesseract has joined #openstack-nova06:57
*** gary_perkins has joined #openstack-nova06:58
*** ociuhandu has quit IRC07:03
*** ociuhandu has joined #openstack-nova07:04
*** maciejjozefczyk has quit IRC07:04
*** frickler_ is now known as frickler07:05
gibigood morning nova07:08
gibibrinzhang_: will get to it soon07:08
*** maciejjozefczyk has joined #openstack-nova07:08
brinzhang_good morning gibi07:08
gibi_erlon_: it is up as usual. I update the agenda as soon07:08
brinzhang_gibi: thanks, wait for your check07:08
*** slaweq has joined #openstack-nova07:08
*** ociuhandu has quit IRC07:09
*** tetsuro_ has joined #openstack-nova07:10
brinzhang_gibi: the noVnc feature, my colleague pushed the PoC code, maybe we can done of that feature, I will give him help as soon as possiable https://review.opendev.org/#/c/622336/07:11
brinzhang_gibi: you dont too review now, when it's ready, I will respin07:12
*** tetsuro has quit IRC07:13
gibibrinzhang_: ack, I saw the patch getting up07:14
*** tetsuro_ has quit IRC07:14
*** avolkov has joined #openstack-nova07:16
*** rpittau|afk is now known as rpittau07:17
*** masterpe has quit IRC07:29
*** yaawang has quit IRC07:34
*** yaawang has joined #openstack-nova07:34
*** ociuhandu has joined #openstack-nova07:37
*** sapd1_x has quit IRC07:39
*** tetsuro has joined #openstack-nova07:40
*** dtantsur|afk is now known as dtantsur07:44
gibibrinzhang_: regarding http://paste.openstack.org/show/791501/ the test fails as the calls https://review.opendev.org/#/c/711194/11/nova/api/openstack/compute/volumes.py@488 raises instead of returns False07:49
gibiso somehow you setting @ for swap policy does not pass07:51
brinzhang_but I overwrite to self.policy_root % "swap": "@",07:51
gibiyeah07:51
brinzhang_why?07:51
gibiI have no clue yet07:51
gibithere are 3 test classes all inheriting the unit test 2 of the fails 1 passes07:53
gibiso something is different in those classes07:54
gibithis passes VolumeAttachPolicyTest07:55
gibiVolumeAttachNoLegacyPolicyTest and .VolumeAttachScopeTypePolicyTest fails07:55
brinzhang_yes, it's ok in VolumeAttachPolicyTest class, and not ok in VolumeAttachScopeTypePolicyTest and VolumeAttachNoLegacyPolicyTest class07:55
brinzhang_I tried move it to VolumeAttachScopeTypePolicyTest class, but I think I cannot do that, I should keep them in the base class, I think07:56
brinzhang_of course, in VolumeAttachScopeTypePolicyTest it's also failed07:56
*** masterpe has joined #openstack-nova07:59
*** threestrands has quit IRC08:01
*** tosky has joined #openstack-nova08:02
*** yaawang has quit IRC08:03
*** yaawang has joined #openstack-nova08:04
*** ralonsoh has joined #openstack-nova08:12
gibiI gave up, we need gmann to look at these tests08:13
*** sapd1_x has joined #openstack-nova08:13
*** sapd1 has quit IRC08:16
brinzhang_gibi: yeah, thanks also ^^08:17
*** xek has joined #openstack-nova08:25
gibistephenfin: just to double check is this bp done now? https://blueprints.launchpad.net/nova/+spec/remove-nova-network-ussuri08:32
*** yaawang has quit IRC08:32
gibiI don't see any open patches08:32
gibistephenfin: nvm, I see that the bp is in Implemented state08:32
*** yaawang has joined #openstack-nova08:34
*** ociuhandu has quit IRC08:36
*** rambo_li has joined #openstack-nova08:38
*** ociuhandu has joined #openstack-nova08:38
*** martinkennelly has joined #openstack-nova08:39
*** ociuhandu has quit IRC08:43
*** rambo_li has quit IRC08:47
stephenfinYeah, I updated that last week08:52
gibistephenfin: thanks08:53
gibiI'm going through the BPs targeted to ussuri just by eye skipped a line an thought nova-net bp is not closed08:54
gibis/by/my08:54
gibistephenfin: how familiar you are with the oslo policy stuff?08:54
stephenfinI've been learning it slowly08:55
gibistephenfin: brinzhang_ has a test that fails on policy problem and I didn't find the solution08:55
*** luyao has joined #openstack-nova08:55
gibistephenfin: this is the problematic test (in the comment in the paste) https://review.opendev.org/#/c/711194/11/nova/tests/unit/policies/test_volumes.py@176 if you have time. If not then no worries we will ping gmann later08:56
brinzhang_gibi, thanks mention these, if stephenfin can give some help, I will be appreciate08:59
stephenfinwill do09:03
luyaostephenfin: Hi, I hope you could continue looking at vpmem live migration support https://review.opendev.org/#/c/687856/ if you have time. :)09:03
*** rambo_li has joined #openstack-nova09:06
*** ociuhandu has joined #openstack-nova09:10
*** rambo_li has quit IRC09:11
*** rambo_li has joined #openstack-nova09:12
*** tetsuro has quit IRC09:14
brinzhang_gibi, dansmith: I will modify the SPEC in 2020/4/4 or 2020/4/5, to show the new PUT api changes, I think it's not later09:17
gibibrinzhang_: sure. doc changes can go in after FF. and the spec repo is not even released so that is OK to update even later09:17
*** tframbo has joined #openstack-nova09:20
brinzhang_gibi: thank, if so, I will update that while I have more free time ^^09:20
gibibrinzhang_: thanks09:21
brinzhang_gibi: np09:21
*** LiangFang has quit IRC09:22
*** tframbo has quit IRC09:22
openstackgerritStephen Finucane proposed openstack/nova master: Remove future imports  https://review.opendev.org/71467509:39
openstackgerritStephen Finucane proposed openstack/nova master: Use unittest.mock instead of third party mock  https://review.opendev.org/71467609:39
openstackgerritStephen Finucane proposed openstack/nova master: hacking: force explicit import of python's mock  https://review.opendev.org/70876809:39
*** tkajinam has quit IRC09:47
*** ygk_12345 has joined #openstack-nova09:52
*** ygk_12345 has left #openstack-nova09:55
*** zhanglong has quit IRC10:08
*** spatel has joined #openstack-nova10:09
*** sapd1_x has quit IRC10:09
*** spatel has quit IRC10:14
*** rpittau is now known as rpittau|bbl10:14
*** brinzhang_ has quit IRC10:24
*** brinzhang_ has joined #openstack-nova10:24
stephenfingibi, brinzhang_: RE: https://review.opendev.org/#/c/711194/11/nova/tests/unit/policies/test_volumes.py@176 - you're using the wrong HTTPRequest object10:28
stephenfinyou're modifying 'nova.context' on 'self.req' and then calling things with a local 'req' that doesn't have 'nova.context' configured10:29
brinzhang_stephenfin: I should add v2.85 support, what I do to change req = fakes.HTTPRequest.blank('', version='2.85')?10:30
gibistephenfin: good eyes! thanks!10:30
stephenfinbrinzhang_: I'm guessing but I think think self.req.version = '2.85' should do the trick??10:31
stephenfinIf not, you need to do req = fakes.HTTPRequest.blank('', version='2.85')10:31
brinzhang_stephenfin: let me try10:31
stephenfinand the do e.g. req.environ['nova.context'] = self.system_foo_context10:31
stephenfin^ that's what I did locally10:32
stephenfinbrinzhang_: Actually, in the setUp, is there any reason not to configure 'self.req' with a version argument?10:33
stephenfinYou're testing policy, not microversion support, so you'll always want to use a known working version, right?10:33
brinzhang_yes10:33
brinzhang_stephenfin: you mean I should change self.req to req in setup()?10:35
stephenfinno10:35
stephenfininstead of self.req = fakes.HTTPRequest.blank('')10:36
stephenfindo self.req = fakes.HTTPRequest.blank('', version='2.85')10:36
stephenfinhere https://review.opendev.org/#/c/711194/12/nova/tests/unit/policies/test_volumes.py@7810:36
brinzhang_no, it dosenot only for v2.8510:37
brinzhang_so I just used req in v2.85 policy tests10:37
stephenfinah, I see now, this is only for the 'update_volume' case10:37
brinzhang_yes10:37
stephenfingotcha10:37
brinzhang_req.environ['nova.context'] = self.system_foo_context10:37
stephenfinyup, that'll do so ^10:38
brinzhang_I added this, it run ok now, will update10:38
brinzhang_thansk stephenfin, gibi10:38
*** sapd1 has joined #openstack-nova10:41
*** rambo_li has quit IRC10:42
*** derekh has joined #openstack-nova10:44
openstackgerritBrin Zhang proposed openstack/nova master: Separate update and swap volume policies  https://review.opendev.org/71119410:47
brinzhang_gibi, stephenfin: done thanks10:47
brinzhang_stephenfin: can you +A for this patch https://review.opendev.org/#/c/693828/25? it's ready for everything, that comment inline, I will fixed by FUP10:48
stephenfinbrinzhang_: I haven't looked at that in a while so I'll need a while10:50
openstackgerritStephen Finucane proposed openstack/nova master: api: Add framework for extra spec validation  https://review.opendev.org/70464310:50
openstackgerritStephen Finucane proposed openstack/nova master: api: Add support for new cyborg extra specs  https://review.opendev.org/71622210:50
openstackgerritStephen Finucane proposed openstack/nova master: api: Add microversion 2.85, extra spec validation  https://review.opendev.org/70843610:50
openstackgerritStephen Finucane proposed openstack/nova master: docs: Add documentation for flavor extra specs  https://review.opendev.org/71003710:50
stephenfingibi: addressed the comments from Sundar and removed those errant prints from the last doc patch ^10:51
brinzhang_stephenfin, gibi, gmann: thanks, hope you have a greate day ^^10:51
openstackgerritSylvain Bauza proposed openstack/nova master: Provide the parent pGPU when creating a new vGPU  https://review.opendev.org/71548910:52
openstackgerritSylvain Bauza proposed openstack/nova master: WIP: Support different vGPU types per pGPU  https://review.opendev.org/71549010:52
bauzassean-k-mooney: ^10:52
*** brinzhang has joined #openstack-nova10:58
*** brinzhang_ has quit IRC11:01
openstackgerritMerged openstack/nova master: Add new default roles in remote console policies  https://review.opendev.org/71648411:03
*** ratailor_ has joined #openstack-nova11:08
*** mkrai has quit IRC11:09
*** ratailor has quit IRC11:10
*** tkajinam has joined #openstack-nova11:12
*** brinzhang_ has joined #openstack-nova11:21
*** ratailor_ has quit IRC11:23
*** ratailor_ has joined #openstack-nova11:23
*** brinzhang has quit IRC11:24
*** ratailor__ has joined #openstack-nova11:30
*** ratailor_ has quit IRC11:33
*** ratailor__ has quit IRC11:33
gibistephenfin: ack, will look shortly11:38
*** udesale_ has joined #openstack-nova11:40
gibistephenfin: I'm all the way +2 on that series. Do you have a novaclient change as well?11:41
*** udesale has quit IRC11:43
*** rcernin has quit IRC11:54
*** ratailor has joined #openstack-nova11:56
*** rpittau|bbl is now known as rpittau12:12
stephenfinbauzas: You think you could review https://review.opendev.org/#/c/710037/8/doc/ext/extra_specs.py ? It's not the least bit complicated, if that helps :)12:25
bauzasoh yeah12:25
stephenfinHappy to trade reviews12:25
sean-k-mooneybauzas: at the moment i assume you are not allowing multiple vGPU types on a single pGPU12:34
sean-k-mooneybauzas: there is noting in princiapl that prevents that form working even if nvida does not support that12:34
*** mkrai has joined #openstack-nova12:34
sean-k-mooneythe vfio mediated device framework fully support using multiple mdev_types on the same devcie concurrnetly12:35
alex_xuanyone know why we can swap the same volume before https://review.opendev.org/#/c/693828/25/nova/api/openstack/compute/volumes.py@495...12:35
sean-k-mooneyalex_xu: lyarwood is on pto i think but i think we can may do that for a volume retype on the cinder side12:36
alex_xuoh, I guess we can't, that will fail at later voluem status check12:36
alex_xusean-k-mooney: ah, thanks12:36
sean-k-mooneyalex_xu: im not sure if my guess above was correct by the way. we could very well just fail later as you said12:37
alex_xuyea12:37
sean-k-mooneybut i think cinder allows use to retype a voule while its attached to an instance and this is the only way i can think if for it to tell nova that it has updated12:38
alex_xusean-k-mooney: ok, thanks12:39
sean-k-mooneyalex_xu: i didnt review the rest of that patch but just -1'd it since its aliasing the id builtin fucntion and using id as a varible which is wrong12:41
sean-k-mooneyin this context it wont break anything but we should never do that12:41
alex_xusean-k-mooney: I'm not sure we can check that, I need to check the api code. we use 'id' in many API. but I agree that seems wrong12:51
sean-k-mooneyim not sure we call id directly in nova since we normally dont care about the objects address in memory12:53
sean-k-mooneybut its just not good practic to alias builtins in general12:53
sean-k-mooneyit would only really be an issue if you did "id=dir" or something at module scope12:54
sean-k-mooneyinside a function it will jsut make id unavialbel in that function body12:54
*** nweinber has joined #openstack-nova12:55
*** mriedem has joined #openstack-nova12:55
sean-k-mooneybut if you do  python3 -c "id=dir; help(id)" it will show the help for dir so if you do that at module scope anything that uses id after will get dir instead12:57
alex_xuyea, agree with that12:58
alex_xusean-k-mooney: this is where id coming from https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/routes.py#L82012:58
sean-k-mooneyah i see ya we proably shoucl change that to <resouce>_id for all of the usages and add a hacking check.13:00
sean-k-mooneythat is a seperate change however so ill remove my -113:00
sean-k-mooneythis is an existing bug13:00
*** mkrai has quit IRC13:02
*** ociuhandu has quit IRC13:02
openstackgerritHuaqiang Wang proposed openstack/nova master: Introduce the 'CPUAllocationPolicy.MIXED' enum  https://review.opendev.org/71626713:02
openstackgerritHuaqiang Wang proposed openstack/nova master: hardware: Add support for 'hw:cpu_dedicated_mask' extra spec  https://review.opendev.org/71470613:02
openstackgerritHuaqiang Wang proposed openstack/nova master: Introduce 'pcpuset' field for InstanceNUMACell  https://review.opendev.org/71698413:02
*** francoisp has joined #openstack-nova13:03
*** mkrai has joined #openstack-nova13:04
*** derekh has quit IRC13:10
*** mkrai has quit IRC13:10
*** tesseract has quit IRC13:11
*** ratailor has quit IRC13:12
*** tesseract-RH has joined #openstack-nova13:16
artomstephenfin, could you take a look at the bottom patch in the NUMA LM series? Dan Smith is +2, if you agree, we can at least get the first 2 patches in that series in the gate13:19
stephenfinsure13:19
artomThe rest can wait until after FF I guess, since there are probably more important series to review13:20
artomstephenfin, err, link: https://review.opendev.org/#/c/714228/213:20
bauzassean-k-mooney: that's a correct assumption, I prevent such thing (supporting multiple types concurrently for *each* pGPU)13:21
sean-k-mooneybauzas: ok. well that is not limitation of mdevs just of the nova/nvida usage13:22
sean-k-mooneybauzas: that is fine for now in anycase13:22
bauzassean-k-mooney: like I also doesn't want to support yet asking for multiple allocations using groups13:22
bauzasi limit to only one allocation for the VGPU resource class13:23
bauzasI mean, people can ask VGPU>113:23
bauzas(of course)13:23
bauzasbut not with numbered request groups13:23
sean-k-mooneyya that is fine13:23
sean-k-mooneyi dont think we shoudl use numbered request groups in teh flavor anyway so im fine with that13:24
bauzasI don't return an exception for this13:24
bauzasI just take the first one13:24
sean-k-mooneythat could be an improvement to add as a followup13:25
sean-k-mooneybauzas: its documented which is the important thing13:25
bauzasyup13:25
*** markmcclain has joined #openstack-nova13:26
bauzassean-k-mooney: yeah I know the mdev framework does that13:28
bauzas(I mean having multiple vGPU types per pGPU=13:28
bauzasbut then if you create one mdev with the nvidia driver, then automatically and magically the available instances of vGPU for the other types turn to 0 :D13:29
bauzas(at least GRID10 AFAIK)13:29
bauzasanyway, rushing to finish my change so that I can decently review stephenfin's extra spec validation thingies https://review.opendev.org/#/c/704643/2013:30
*** mkrai has joined #openstack-nova13:31
*** amodi has joined #openstack-nova13:42
openstackgerritjayaditya gupta proposed openstack/nova master: Support for nova-manage placement heal_allocations --cell  https://review.opendev.org/71445913:53
nightmare_unrealmriedem:  if you get some time can you see this : https://review.opendev.org/#/c/714459/ . I can't seem to figure out the issue with the unit test case I wrote. Thank you :) . I have fixed rest of the points you mentioned13:54
*** vishalmanchanda has quit IRC13:58
*** dtantsur is now known as dtantsur|brb14:10
*** mkrai has quit IRC14:14
mriedemnightmare_unreal: this? "Exception: This test uses methods that set internal oslo_db state, but it does not claim to use the database. This will conflict with the setup of tests that do use the database and cause failures later."14:15
mriedemthat means the unit test class is using NoDBTestCase or whatever it's called, which means something in the test is trying to make a database connection and isn't allowed,14:15
*** asettle has quit IRC14:15
mriedemso either move that test to the functional test class where there is a DB connection, or you have to mock out the DB call to raise the NotFound error or whatever for the test14:16
mriedemyour test can mock objects.CellMapping.get_by_uuid to raise CellMappingNotFound14:16
*** mkrai has joined #openstack-nova14:16
*** ociuhandu has joined #openstack-nova14:17
mriedem@mock.patch('nova.objects.CellMapping.get_by_uuid', side_effect=exception.CellMappingNotFound('uuid')14:17
mriedemsomething like that as a decorator to the test case method14:18
openstackgerritMerged openstack/nova master: Combine the limits policies in single place  https://review.opendev.org/71567814:20
*** N3l1x has joined #openstack-nova14:26
nightmare_unrealThanks !!14:28
*** mkrai has quit IRC14:29
*** ociuhandu has quit IRC14:34
openstackgerritjayaditya gupta proposed openstack/nova master: Support for nova-manage placement heal_allocations --cell  https://review.opendev.org/71445914:35
dansmithbrinzhang_: are you working on feedback on the PUT patch?14:35
francoispstephenfin, just to draw your attention, I answered your last question on https://review.opendev.org/#/c/669674/10 - thanks!14:41
stephenfinack14:42
openstackgerritAlexandre arents proposed openstack/nova master: Calculate over_committed_disk_size for raw instances  https://review.opendev.org/71703714:48
*** ttsiouts has quit IRC14:49
*** macz_ has joined #openstack-nova14:55
*** mkrai has joined #openstack-nova15:00
*** links has quit IRC15:03
*** david-lyle has quit IRC15:08
*** dklyle has joined #openstack-nova15:08
*** ttsiouts has joined #openstack-nova15:08
*** gyee has joined #openstack-nova15:11
*** mlavalle has joined #openstack-nova15:16
*** ociuhandu has joined #openstack-nova15:18
*** mkrai has quit IRC15:22
*** ociuhandu has quit IRC15:23
*** mkrai has joined #openstack-nova15:31
*** ociuhandu has joined #openstack-nova15:34
*** avolkov has quit IRC15:36
gmannmelwitt: that is correct. I need to propose some ideas on warning disable on oslo side what discussed with lbragstad. But yes all these are planed before FF. I am hoping to finish the policy things first by this Sat or Sunday.15:38
*** ttsiouts has quit IRC15:46
*** ttsiouts has joined #openstack-nova15:48
gibinova meeting starts in 10 minutes on #openstack-meeting-315:50
bauzasmelwitt: sorry I didn't had time yet to review your nova-manage patches, is it still worth it given the -W ?15:50
dansmithgibi: fyi, I'm running final tests on a change to that PUT patch to address just the critical bits of alex_xu's review15:50
bauzasbut of course I'll do it if you want15:50
*** mkrai has quit IRC15:50
dansmithdidn't get a response from brinzhang_ so I assume he's not working on it right now15:51
gibidansmith: ack. thanks15:52
*** tesseract-RH has quit IRC15:55
*** rpittau is now known as rpittau|afk15:56
gmanndansmith: gibi also we need to add schema tests coverage for None to verify those things.15:58
dansmithgmann: I'm changing how those checks work, which might mean not15:59
dansmithdevice_name appears to be nullable at least, in the schema and in the db15:59
dansmiththe others are all separate definitions I think16:00
gmannyeah, other does not allow None from schema only device do.16:01
*** dtantsur|brb is now known as dtantsur16:01
openstackgerritHuaqiang Wang proposed openstack/nova master: Introduce 'pcpuset' field for InstanceNUMACell  https://review.opendev.org/71698416:01
openstackgerritBalazs Gibizer proposed openstack/nova master: Fix assertEqual param order in Accelerator tests  https://review.opendev.org/71706916:02
openstackgerritBalazs Gibizer proposed openstack/nova master: Stabilize functional tests  https://review.opendev.org/71707016:02
*** ttsiouts has quit IRC16:04
openstackgerritDan Smith proposed openstack/nova master: Allow PUT volume attachments API to modify delete_on_termination  https://review.opendev.org/69382816:04
dansmithgmann: ^16:04
gmannthanks checking16:05
toskyfor stable maintainers: this last review should remove any reference to legacy-tempest-dsvm-full-devstack-plugin-nfs (then we are doing the same in Cinder): https://review.opendev.org/#/c/714958/16:08
gmanndansmith: do not we nee do check dot with old value vefore change - https://review.opendev.org/#/c/693828/25..26/nova/api/openstack/compute/volumes.py@46016:08
gmannbefore16:08
dansmithgmann: why? we sad that if you PUT with no changes it's not an error right?16:08
dansmithtechnically BDM should not be doing a db save if there are no changes, but not all objects do that properly.. but either way, no reason to just add more to the conditional really16:09
gmanndansmith: yeah but when we add policy in next patch that become difficult to handle on "update request" vs "no change means not update request"16:10
dansmithgmann: I don't follow16:10
gmannin case of "swap + update" - we consider request is for update only when value is changed right. if value is same then we need to consider no update request and it is onyl swap16:11
gmannin that case, how we can check the update policy so that that policy is being checked only when request is update (means value change)16:11
dansmithin 2.85 we should only consider it a swap if volumeId is changed16:12
gmannbut we support swap + update together also16:12
dansmithi.e. only check the stricter policy if volumeId is changed, otherwise we check the regular PUT policy16:12
gmann>2.8516:12
dansmiththe swap policy should imply you can also change the other values right?16:12
gmannyeah and checking regular PUT policy when value is same is wrong.16:12
dansmithI disagre16:13
gmannwe want to allow update for non-admin16:13
dansmithif volumeId is changed, we check the swap policy, else check PUT policy16:13
gmannlet me rephrase16:13
dansmithin this patch it's all one policy, and the next patch splits them into two16:14
gmannok, we can discuss in next patch but there question was - we should not check the PUT policy if request is swap only not update.16:16
openstackgerritHuaqiang Wang proposed openstack/nova master: Introduce 'pcpuset' field for InstanceNUMACell  https://review.opendev.org/71465816:16
gmannknowing it is 'not update' is only done by if value is changed16:17
dansmithgmann: and like I said, I think >=2.85, we should only ever consider something a swap if the volumeId changed, otherwise it's a put, even if *nothing* changed16:17
gmanndansmith: that is question actually. if nothing changes should we consider that as update request ? especially when we allow people to replicate the PUT and change only volumeId fir swap16:18
gmannif do so then we endup checking two (PUT and SWAP) policy for swap16:18
dansmithI strongly feel that going forward this should behave like a regular PUT, where you can PUT with no changes all the time,16:19
dansmithand only check the swap policy if you're actually changing the volume16:19
dansmithI don't see how anything else makes sense16:19
gmanndansmith: yeah +1 on 'only check the swap policy if you're actually changing the volume'. but this became hard to implement with no value check of dot.16:21
gmanni think if you rebase the policy patch then it will be clear.16:22
dansmithokay I don't see what the value of dot has to do with which policy gets checked16:22
gmannpolicy stuff is a challenge here16:22
bauzasgibi: if you don' mind, I would appreciate https://blueprints.launchpad.net/nova/+spec/vgpu-multiple-types to be targeted for ussuri-316:22
dansmithgmann: do you not agree that if you have swap permissions, you should also be able to change dot?16:23
bauzasthe patches in question are small16:23
gmanndansmith: that is fine but vice versa should not16:23
gmanndansmith: here - https://review.opendev.org/#/c/711194/11..13/nova/api/openstack/compute/volumes.py@46816:23
gibibauzas: noted, I will update lauchpad after the meeting16:23
gmannotherwise we end up doing PUT policy check always16:23
bauzasgibi: thanks16:24
dansmithgmann: right but as stephen (and now I) say there, that's the wrong place to check policy16:24
dansmithgmann: we should check at the beginning of update(), either the PUT or PUT-with-swap policy based on whether or not volumeId is changed.. it should be very simple if..else16:24
dansmithgmann: anyway, once the base patch looks like it's +2 I will rebase the policy patch (or help brinzhang_ ) and we can discuss/argue the policy bit on that16:25
*** udesale_ has quit IRC16:26
gmanndansmith: ok. after rebase it will be more clear. But i think i got your point of swap policy supersede the PUT policy16:27
openstackgerritDan Smith proposed openstack/nova master: Allow PUT volume attachments API to modify delete_on_termination  https://review.opendev.org/69382816:27
dansmithgmann: ack16:27
dansmithgmann: ^ that removes one more thing alex asked about that I forgot16:27
gmannok16:27
dansmithgmann: sorry if it got lost in the policy discussion, but... is there still a need to change the schema for null-ness?16:28
gmannwith 'x in attr' check, it is not needed16:29
dansmithgmann: okay cool16:29
stephenfindansmith: off the top of your head, obj_from_primitive is called whenever we pull an o.vo from the DB, yeah?16:31
dansmithstephenfin: for serialized objects16:31
bauzasartom: FWIW, I left the bare minimum in the etherpad for your OSC concerns, the floor is yours :p16:36
bauzasartom: https://etherpad.openstack.org/p/nova-victoria-ptg16:36
artombauzas, OK16:36
*** evrardjp has quit IRC16:36
artombauzas, I'll proll'y just be lazy and harass mordred16:36
*** evrardjp has joined #openstack-nova16:36
bauzasI think the problem isn't the design as I said16:37
artomAbout where any new microversion-enabling client code should go16:37
bauzaswe discussed it so many times16:37
bauzasI think we just need hands16:37
artombauzas, well that's the point, right? We already say "if you're adding a new microversion, you must provide the novaclient patch"16:37
artomNot we'll be saying "and you also need to provide the osdk patch"16:37
bauzasartom: it's more complicated than that16:37
artomIf osdk is indeed the correct place16:37
bauzasartom: if you're about to propose, say 2.8116:37
* mordred waves16:38
bauzasartom: then you also need to make sure that <2.81 works too16:38
bauzasand then you signed-off for doing all the stuff, yay16:38
artombauzas, oh, because of the gap16:38
artom*sigh*16:38
artomYeah ok, I get it16:38
mordredwell - once we reach steady-state making sure <2.81 works too should be pretty easy16:38
artommordred, what does steady-state mean in this context?16:39
mordredthat said - if we can just start getting folks to submit an osdk patch wehn new microversions are made so we can start tracking new things, we can use those as opportunities to fill in old stuff - and I'm happy to help do that16:39
*** ttsiouts has joined #openstack-nova16:39
artommordred, I think I'd like that - we have to start somewhere16:39
mordredartom: I mean havig filled in the support for the existing old microversions16:39
artommordred, ah, that was the thing that mriedem started16:40
mordredmost of the time when someone says "I want to support microversion vX" - it turns out ot be quite easy16:40
artomWell, started driving16:40
mordredyeah16:40
mordredbut - there's a bunch we need to walk through and make sure we understand :)16:40
artommordred, in terms of how the Nova API works?16:40
mordredyeah- many of them wind up being no-ops from sdk point of view16:40
mordredbut it's good to go look at the MV and say "yup, nothing to do16:41
artommordred, ah, for example for things like new fields in responses? sdk just shows them with no added logic16:41
artom(Right?)16:41
gmannyeah, like adding the field in response is same list16:41
mordredyeah, well, we need to add new fields when they're added16:42
mordredbut - we already are up to date with most fields as of like the mid-2.4x or 2.5x - just not labeled that way16:42
mordredso for many of them we're already caught up :)16:42
mordredand for new ones adding support is _usually_ very trivial - one or two lines16:42
mordredthe behavior breaks - like changing live migration - those take some real thought16:43
mordredbut - those require real thought to do the feature too16:43
artomYeah, the live migration thing was ugly16:44
artomBut let's not revisit that :)16:44
gmannis it not we need to bump the python-novaclint version on OSC because we maintain the MAX_VERSION there and increase when no change needed16:44
mordredyeah. but - that's one of the ones where I'm quite happy with our support16:44
mriedemin my experience adding feature parity for compute API microversions to OSC, for example, is not always so trivial, especially when the people reviewing the changes aren't from the nova team or aren't familiar with how the API works16:45
gmann+116:46
mordredI agree - although I'd like to make progress on changing that :)16:46
artommordred, alright, we'll probably talk this over at the PTG again, but the initial "action item" of "require sdk patch, use as opportunity to catch up a bit" makes sense to me16:46
mriedemso random person throws up a change and the OSC team just basically trusts that it's correct from an API POV and then their review is based on UX standards for OSC16:46
mriedemmordred: there was progress while i was pushing it from the nova team, but ...16:46
mriedemsomeone needs to fill those shoes16:46
artomYeah, having someone from the project reviewing the change should be a must16:46
mordredmriedem: we just need to clone you16:46
artomDoesn't have to be core16:47
gmannI can volunteer for that16:47
artomLike, I feel I have a good enough handle on it to give +1s16:47
artom(Or -1s)16:47
mriedemno it doesn't have to be a core, but it's good to be familiar with the actual API change and spec and all that16:47
artom... which I never did, so mea culpa, I guess16:47
mriedemand the people that review API changes and specs are ... usually cores16:47
artomWell, assuming the api-ref is correct and complete, that's good enough doc, no?16:48
mriedemanyway, if the api side core review enforces good docs / api ref then anyone should be able to review the client side changes16:48
mriedemjinx16:48
artomAnd if you review the sdk change, look at the api-ref, and can't grok if it makes sense or not, it means we've failed at api-ref16:48
mriedemlots of ifs16:48
artomAnd butts16:49
artom(Sorry)16:49
mriedemcandy and nuts16:49
gmannmriedem: how you do, monitoring yourself or osc team add as reviewer etc ?16:49
gmannyou did16:49
mriedemi'd have to find my old etherpad that was tracking the compute API microversion gaps in OSC16:49
mriedembut that's usually how i'd track things, then once there was a review up i'd add myself as reviewer yeah16:50
mriedemi also just started making the changes myself16:50
artomhttps://etherpad.openstack.org/p/DEN-osc-compute-api-gaps ?16:50
gmannohk, i know that etherpad.16:50
mriedemthen was made OSC core about a month before i left :)16:50
mriedemartom: close: https://etherpad.openstack.org/p/compute-api-microversion-gap-in-osc16:50
*** rambo_li has joined #openstack-nova16:51
mriedemnote the gap continues to widen,16:51
mriedemand we're not tracking the last few new microversions in there16:52
*** ociuhandu has quit IRC16:52
artomYeah, that's what prompted by question16:52
artomWe're adding new mvs, but not requiring changes to sdk16:52
artomIt's a battle we can't win16:52
mriedemjust takes someone that cares and discipline16:52
artomSo better just give up then, right?16:53
mriedemsure16:53
*** ttsiouts has quit IRC16:54
*** dtantsur is now known as dtantsur|afk16:59
artomsean-k-mooney, tbh I wasn't really planning on attending those - ML is fine with me17:00
artomI can share the info, but don't feel like taking on planning tasks17:00
artomThat's TC's job, and I have no TC ambitions17:01
artom(Or whatever other committee handles that)17:02
bauzasartom: well, the problem is that lots of operators (including the ones that are getting a certain product from a big red company) are told to use OSC by the documentation17:03
bauzaswhich is fine if you wanna have a stable and interoperable experience17:03
bauzas(eg. with public clouds)17:03
sean-k-mooneyartom: well the indivugal teams normlaly work out the detailed timetable17:04
mriedemosc isn't only good for that,17:04
mriedema unified CLI is important for new users to openstack, even if it's just your private cloud17:04
sean-k-mooneyso i dont expect the tc to do that just beasue it now virutal17:04
mriedemneeding to install and learn 10 different python-*client project CLIs sucks17:04
sean-k-mooneyyep i agreee with ^17:04
mriedemall with their own options and command structure17:04
bauzasI'm just saying that a company that provides top-notch features to their customers and provide internal docs about using OSC should also care about making sure OSC is workable for those top-notch featureds17:05
artombauzas, yeah, that's an argument for centralizing on osc/sdk and eventually getting rid of novaclient altogether :)17:05
dansmithmriedem: I agree with that in principle of course, but I don't know that I agree that osc is currently better17:05
artomWhich is what we're doing :)17:05
sean-k-mooneywhich compay might that be ? :P and yes17:05
mriedemdansmith: not until someone works to make it better17:05
mriedeme.g. the bfv gaps17:05
mriedemlive migration sucking ass17:05
dansmithyep, as long as that's in the mix17:05
bauzasI personnally gave up with this.17:06
dansmithmriedem: and all the version override hacks you have to do to do anything17:06
mriedemyup the version discovery is way better in nova cli17:06
mriedems/way better/exists/17:06
sean-k-mooneymriedem: i do think that if you use an option that requries a min cli you should not have to specify it with osc like you do today17:07
dansmithtbh I've seen less confusion from the different project clients than I have from people wondering how they're supposed to know when to use a given version to do something in nova17:07
mriedemsean-k-mooney: that's shade or oaktree or whatever mordred had before17:07
sean-k-mooneybut im not sure the bevhior of nova cli always using latest is actully good17:07
mriedem"the nova cli is not a bash sdk"17:07
dansmithyou can run fooclient --help and bumble the way through a thing, but you can't do that with osc help because you don't have the magic version decoder ring17:08
mriedemthe osc help should tell you what version is needed to do things,17:08
*** martinkennelly has quit IRC17:08
mriedembut that's been a gap in people reviewing and enforcing those osc changes17:08
sean-k-mooneydansmith: ya its both better and worse that it show you the help for the microversion you specify17:08
sean-k-mooneyif you dont know the microverion exits your screwed17:08
*** martinkennelly has joined #openstack-nova17:09
dansmithmriedem: okay I've literally never seen that on a help, but maybe because the things I needed didn't have it17:09
mriedeme.g. https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/server-event.html#server-event-show17:09
mriedempart of the gaps closure in that etherpad is just adding stuff like that to the help17:09
dansmithmriedem: oh that's in the docs not in the --help?17:09
mriedemsame17:09
mriedemdocs are generated from the help17:10
mriedemlike osc-placement17:10
dansmithokay well, I've never seen it in the help for things I was looking at, but okay17:10
mriedemanother example for 2.73 that tssurya added https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/server.html#server-lock17:10
mriedemyeah it's a constant fight to make sure people remember to add those,17:11
mriedemand get people to backfill them17:11
mriedemhence the etherpad17:11
dansmithin that one page, one says "use version X" and another says "use version X by passing --this-complicated-arg-thing"17:11
dansmithbut yeah, it would definitely be better if that was all consistent enough to rely on17:11
rambo_liExcuse me, sean-k-mooney ralonsoh Please Let’s talk about the bug here:17:12
rambo_lihttps://bugs.launchpad.net/neutron/+bug/1815989 And what is our plan to solve this bug?17:12
openstackLaunchpad bug 1815989 in OpenStack Compute (nova) "OVS drops RARP packets by QEMU upon live-migration causes up to 40s ping pause in Rocky" [Medium,In progress] - Assigned to sean mooney (sean-k-mooney)17:12
dansmithI'm not helping so I know I can't complain too much, but in the current state of the world, I don't see osc as better17:12
mordredmriedem: fwiw - I want to completely change what the version story is in osc - and I agree with sean-k-mooney - I do not think you should have to specify a min version on the cli17:13
sean-k-mooneyrambo_li: at the moment im not working on it, the patch i submited shoudl fix it but they dont work anymore due to rebases and refacoting17:13
mordredit is that way for hysterical raisins and I think those raisins are no longer useful to us17:13
sean-k-mooneymordred: if we default to oldest that support feature ex it keeps the stablity and if you want the new behavior you ask for it17:14
mordredI am planning on writing something up so we can discuss it around PTG time to make sure it meets what people are wanting17:14
*** ttsiouts has joined #openstack-nova17:14
sean-k-mooneybut we dont do that today in many cases we say to use option x you need to pass version y17:14
sean-k-mooneyi have noticed that lately with osc-placment when trying ot use some operation but im sure we have the same behviaor in the nova supprot in osc17:15
mordredright - I think there's actually a third option which can be more aggressive about new things while not breaking people - but I need to write it up17:15
mordredfrom my end-user pov - if I *ever* have to give osc a version for a reason other than "I am a developer debugging the rest api" something has completely failed17:16
*** artom has quit IRC17:16
dansmithmordred: ++17:16
mordredwhich is not to say that this failure isn't happening consistently today :)17:16
*** artom has joined #openstack-nova17:16
mordredbut - it's a failure from an UX perspective and I want to fix it17:16
mordreds/want/am going to/17:16
mordredI will know I'm successful when everyone here thinks it's behaving properly ;)17:17
dansmith"if you've ever had to pass a version to OSC in the last six months, you get an ATC pass to the summit"17:17
mordreddansmith: ++17:17
sean-k-mooneymordred: you will have to get the ironic folks on board too17:18
sean-k-mooneymordred: sicne they went ahead and impleemnted the same version negoction logic in there plugin they had in the legacy client17:18
mordredsean-k-mooney: yeah - I've already got good ironic support done by the ironic team in sdk though - so I think I'm closer with them17:19
sean-k-mooneymordred: i think one thing to condiser is moveing everything after nova v2.0 out of osc and into a nova plugin17:19
mordredI want to get rid of all plugins17:19
sean-k-mooneymordred: well part of the issue currently is geting things landed in osc17:20
mordredright. that's based on the past - we're making some massive changes17:20
sean-k-mooneyso project wich plugisn could make progress but "core" project had an issue17:20
mordredso - gimme a little bit to let those changes percolate17:20
sean-k-mooneysure im glad the sdk and ocs team are combined/combinging17:20
*** martinkennelly has quit IRC17:24
*** rambo_li has quit IRC17:24
*** nightmare_unreal has quit IRC17:27
*** KeithMnemonic has joined #openstack-nova17:28
*** martinkennelly has joined #openstack-nova17:28
sean-k-mooneymordred: honestly if we could deprecate the nova clinet and  deliver changes as easily as we can today to osc for V that would be awsome but there are still a long list of gaps to close before that is realistic17:31
*** ociuhandu has joined #openstack-nova17:32
artomsean-k-mooney, I don't think anyone disagrees - but to paraphrase mriedem, and directly quote Nike, "just do it" :)17:33
*** ociuhandu has quit IRC17:36
mordredsean-k-mooney: I agree ... but I'm going to make a concerted push to see how many of those gaps I can close and how much I can ease the situation17:37
mordredmight not work, obviously- but otoh - getting novaclient parity and being able to deprecate it would be a _huge_ step forward in terms of gravity, so I think it's worth extra attention17:38
*** sapd1 has quit IRC17:38
openstackgerritMerged openstack/nova master: Add test coverage of existing server diagnostics policies  https://review.opendev.org/71680017:39
sean-k-mooneywell i almost never need to use nova client for day to day things but it does happen.17:40
sean-k-mooneyi should really just chagne https://review.opendev.org/#/c/643578/ back to evacuate too17:40
sean-k-mooneymordred: should i just abandon ^ by the way or if i rebase it and change the command back to evacuate will it get reviews17:44
sean-k-mooneyi kindof gave up on this since i was hoping it would be a non contoversionl quick gap to close and it ended up being the opisite17:44
mordredsean-k-mooney: I will totally review it17:51
mordredactually. lemme read the scrollback on it real quick17:51
sean-k-mooneymordred: context was at the fourm sesseion we express frustration that evacuate did not match with peopel expcations of keeping data at least not unless you are on shared storage17:53
sean-k-mooneyso it was suggested to change the name to resurect or recreate17:53
sean-k-mooneyso i did but there is also the consernt that using a different name17:53
sean-k-mooneywould confuse people that think its somehting new or different17:54
mordredsean-k-mooney: hrm. well - I like the idea of the term ressurrect17:54
mordred(for all the reasons you mention in the patch)17:54
sean-k-mooneyi kind of feel like we should really change how the api works17:55
sean-k-mooneyand then have two seperate commands17:55
mordredsean-k-mooney: I kinda want it to be resurrect and then just have evacuate work as an alias for it - so that people with muscle memory will get what they're expecting, but new people will learn something new17:55
mordredor maybe that17:55
sean-k-mooneyone that will always preserve your data and refuse to work if not on shared stroate17:55
sean-k-mooneyand one that always recretes the vm17:56
sean-k-mooneybasicaly just rebuild on a differnet host17:56
mordredyeah - but with the same volumes and ports17:56
sean-k-mooneyya so litrally rebuild on different host reimabing the root disk17:56
sean-k-mooney*reimageing17:56
sean-k-mooneysee its tricky and once its in a cli we cant really remove it17:58
*** ccamacho has quit IRC18:13
*** maciejjozefczyk has quit IRC18:20
*** ralonsoh has quit IRC18:28
openstackgerritMerged openstack/nova master: Introduce scope_types in server diagnostics  https://review.opendev.org/71680318:30
openstackgerritMerged openstack/nova master: Add new default roles in server diagnostics policies  https://review.opendev.org/71680518:39
openstackgerritMerged openstack/nova master: func tests: move _run_periodics() into base class  https://review.opendev.org/71422818:39
openstackgerritMerged openstack/nova master: tests: work around malformed serial XML  https://review.opendev.org/70554618:39
*** tbachman has quit IRC19:14
*** tbachman has joined #openstack-nova19:16
*** ociuhandu has joined #openstack-nova19:52
_erlon_bauzas: ping19:55
_erlon_bauzas: so, you mentioned that there is a way to add a custom filter without having to change the egg files?19:56
*** ttsiouts has quit IRC19:56
*** ociuhandu has quit IRC20:02
*** ociuhandu has joined #openstack-nova20:02
openstackgerritMatt Riedemann proposed openstack/nova master: Support for nova-manage placement heal_allocations --cell  https://review.opendev.org/71445920:07
*** ociuhandu has quit IRC20:07
mriedemhello nova cores, ^ is pretty simple and would be nice to get in before that stuff is all refactored to nova-audit20:07
artom_erlon_, since bauzas is in France is done for the day, maybe https://docs.openstack.org/nova/latest/user/filter-scheduler.html#writing-your-own-filter can help you?20:36
*** iurygregory has quit IRC20:38
*** iurygregory has joined #openstack-nova20:39
_erlon_artom: hey, thanks for helping, my question was more about the import error that I was getting the last time I tried to add a class that was not in the built in filters20:39
_erlon_artom: let's say I create a new file my_filter.py, with TheFilter, inside. If I put my_filter,py inside the nova/scheduler/filters, and change enabled_filters=+TheFilter, it use to give me an import error20:42
_erlon_artom: so, we needed to add an entry_point in the nova-egg20:42
*** nweinber has quit IRC20:44
*** ttsiouts has joined #openstack-nova20:45
*** ttsiouts_ has joined #openstack-nova20:46
*** ttsiouts has quit IRC20:49
mordred_erlon_: don't put it in nova/scheduler/filters - check that link21:01
*** ociuhandu has joined #openstack-nova21:02
*** igordc has joined #openstack-nova21:05
*** xek has quit IRC21:05
*** ociuhandu has quit IRC21:06
_erlon_mordred: got it! As he puts in the config file, isnt that overwriting the default available filters?21:07
_erlon_see that thereis 2 instances under the same stanza:21:07
_erlon_[filter_scheduler]21:07
_erlon_available_filters = nova.scheduler.filters.all_filters21:07
_erlon_available_filters = myfilter.MyFilter21:07
*** slaweq has quit IRC21:07
mriedemno, it's multi-valued https://docs.openstack.org/nova/latest/configuration/config.html#filter_scheduler.available_filters21:09
*** iurygregory has quit IRC21:12
*** dpawlik has quit IRC21:12
*** slaweq has joined #openstack-nova21:14
*** slaweq has quit IRC21:26
*** lbragstad has quit IRC21:27
*** brinzhang has joined #openstack-nova21:34
*** lbragstad has joined #openstack-nova21:35
*** brinzhang_ has quit IRC21:37
*** mriedem has left #openstack-nova21:38
*** rcernin has joined #openstack-nova22:22
openstackgerritGhanshyam Mann proposed openstack/nova master: Add test coverage of existing limits policies  https://review.opendev.org/71567422:23
openstackgerritGhanshyam Mann proposed openstack/nova master: Correct security groups policy check_str  https://review.opendev.org/71678222:29
openstackgerritmelanie witt proposed openstack/nova master: Move nova-manage db purge to nova-audit  https://review.opendev.org/70878322:29
openstackgerritmelanie witt proposed openstack/nova master: Move nova-manage db archive_deleted_rows to nova-audit  https://review.opendev.org/70878422:29
openstackgerritmelanie witt proposed openstack/nova master: Move nova-manage cell_v2 discover_hosts to nova-manage  https://review.opendev.org/70878522:29
openstackgerritmelanie witt proposed openstack/nova master: Move nova-manage cell_v2 map_instances to nova-audit  https://review.opendev.org/70878622:29
openstackgerritmelanie witt proposed openstack/nova master: Move nova-manage placement sync_aggregates to nova-audit  https://review.opendev.org/70878722:29
openstackgerritmelanie witt proposed openstack/nova master: Move nova-manage placement heal_allocations to nova-audit  https://review.opendev.org/70878822:29
openstackgerritGhanshyam Mann proposed openstack/nova master: Introduce scope_types in limits policy  https://review.opendev.org/71568022:37
*** ttsiouts_ has quit IRC22:38
openstackgerritGhanshyam Mann proposed openstack/nova master: Add new default roles in limits policies  https://review.opendev.org/71576022:43
openstackgerritGhanshyam Mann proposed openstack/nova master: Pass the actual target in limits policy  https://review.opendev.org/71576122:48
*** openstackstatus has quit IRC22:56
*** openstack has joined #openstack-nova22:58
*** ChanServ sets mode: +o openstack22:58
*** macz_ has quit IRC22:59
*** tosky has quit IRC23:00
openstackgerritMerged openstack/nova master: FUP for Add a placement audit command  https://review.opendev.org/71579723:08
openstackgerritMerged openstack/nova master: Introduce scope_types in list migrations  https://review.opendev.org/71614123:08
openstackgerritMerged openstack/nova master: Add new default roles in migrations policies  https://review.opendev.org/71614523:08
openstackgerritMerged openstack/nova master: Fix assertEqual param order in Accelerator tests  https://review.opendev.org/71706923:08
*** brinzhang_ has joined #openstack-nova23:15
*** ttsiouts has joined #openstack-nova23:16
*** brinzhang has quit IRC23:18
*** ttsiouts has quit IRC23:21
*** martinkennelly has quit IRC23:21
*** gyee has quit IRC23:38

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!