Monday, 2019-06-10

openstackgerritTakashi NATSUME proposed openstack/python-novaclient master: Enable omission of the value of '--config-drive'  https://review.opendev.org/65368300:22
*** takashin has quit IRC00:39
*** dave-mccowan has quit IRC00:41
*** frank_wang has quit IRC00:44
*** dave-mccowan has joined #openstack-nova00:53
*** frankwang has joined #openstack-nova00:57
*** bhagyashris has joined #openstack-nova01:16
*** Dinesh_Bhor has quit IRC01:24
*** takashin has joined #openstack-nova01:24
*** boxiang_ has quit IRC01:27
*** boxiang_ has joined #openstack-nova01:27
*** rcernin has quit IRC01:30
*** tbachman has quit IRC01:31
*** j99 has joined #openstack-nova01:38
*** markvoelker has joined #openstack-nova01:42
*** rcernin has joined #openstack-nova01:46
*** brinzhang has joined #openstack-nova01:53
*** sapd1 has quit IRC01:58
*** markvoelker has quit IRC02:15
*** edleafe has quit IRC02:17
*** irclogbot_3 has quit IRC02:17
*** altlogbot_2 has quit IRC02:19
*** irclogbot_3 has joined #openstack-nova02:20
*** altlogbot_0 has joined #openstack-nova02:21
openstackgerritTakashi NATSUME proposed openstack/nova master: Fix no propagation of nova context request_id  https://review.opendev.org/66271502:23
*** _hemna has joined #openstack-nova02:24
*** sapd1 has joined #openstack-nova02:25
*** whoami-rajat has joined #openstack-nova03:08
*** dklyle has joined #openstack-nova03:22
*** ricolin has joined #openstack-nova03:22
*** psachin has joined #openstack-nova03:33
*** dklyle has quit IRC03:37
*** dklyle has joined #openstack-nova03:37
*** dave-mccowan has quit IRC03:38
*** Dinesh_Bhor has joined #openstack-nova03:45
*** factor has joined #openstack-nova03:45
*** BjoernT has joined #openstack-nova03:47
*** BjoernT has quit IRC03:47
*** udesale has joined #openstack-nova03:54
*** BjoernT has joined #openstack-nova03:58
*** BjoernT has quit IRC04:02
*** BjoernT has joined #openstack-nova04:03
*** BjoernT_ has joined #openstack-nova04:06
*** BjoernT has quit IRC04:07
*** BjoernT_ has quit IRC04:10
*** _hemna has quit IRC04:12
*** markvoelker has joined #openstack-nova04:12
*** janki has joined #openstack-nova04:34
*** _hemna has joined #openstack-nova04:42
*** markvoelker has quit IRC04:46
*** abhishekk has joined #openstack-nova04:47
openstackgerritTakashi NATSUME proposed openstack/nova master: Replace joinedload_all with joinedload  https://review.opendev.org/66419304:59
*** swamireddy has quit IRC05:01
*** pcaruana has joined #openstack-nova05:03
*** markvoelker has joined #openstack-nova05:09
*** _hemna has quit IRC05:15
*** ratailor has joined #openstack-nova05:29
*** ricolin has quit IRC05:29
*** slaweq has joined #openstack-nova05:31
*** slaweq has quit IRC05:35
*** udesale has quit IRC05:40
*** udesale has joined #openstack-nova05:41
*** udesale has quit IRC05:41
*** udesale has joined #openstack-nova05:42
*** ivve has quit IRC05:44
*** tkajinam has quit IRC05:51
*** tkajinam has joined #openstack-nova05:53
*** xek_ has joined #openstack-nova05:56
*** tkajinam_ has joined #openstack-nova05:56
*** guozijn has joined #openstack-nova05:56
*** tkajinam has quit IRC05:58
*** _hemna has joined #openstack-nova06:01
openstackgerritMerged openstack/nova-specs master: Specifying az when restore shelved server  https://review.opendev.org/62468906:01
*** ratailor_ has joined #openstack-nova06:21
*** ratailor has quit IRC06:24
openstackgerritBrin Zhang proposed openstack/nova-specs master: Clarify the error response in proposed change  https://review.opendev.org/66419806:29
*** slaweq has joined #openstack-nova06:30
openstackgerritBoxiang Zhu proposed openstack/nova master: Validate requested host/node during servers create  https://review.opendev.org/66123706:31
*** _hemna has quit IRC06:35
*** yikun has joined #openstack-nova06:41
*** ratailor_ has quit IRC06:47
*** ratailor_ has joined #openstack-nova06:47
*** ratailor__ has joined #openstack-nova06:50
*** ratailor__ has quit IRC06:50
*** udesale has quit IRC06:50
*** ratailor has joined #openstack-nova06:51
*** udesale has joined #openstack-nova06:51
*** ratailor_ has quit IRC06:51
*** ratailor_ has joined #openstack-nova06:55
*** ratailor has quit IRC06:58
*** ricolin has joined #openstack-nova06:58
*** ivve has joined #openstack-nova07:01
*** luksky has joined #openstack-nova07:05
*** guozijn has quit IRC07:06
*** rcernin has quit IRC07:09
*** _hemna has joined #openstack-nova07:10
*** dpawlik has joined #openstack-nova07:22
*** jangutter has joined #openstack-nova07:29
*** helenafm has joined #openstack-nova07:40
*** _hemna has quit IRC07:44
*** ralonsoh has joined #openstack-nova07:53
*** zbr has joined #openstack-nova07:55
*** zbr is now known as zbr|ruck07:55
*** guozijn has joined #openstack-nova07:58
*** ricolin has quit IRC08:02
sapd1Hi everyone, In this line, https://github.com/openstack/nova/blob/master/nova/api/metadata/base.py#L362  I think I can get devices which are being attached to the instance, But When I tried, It returns None.08:05
sapd1Can any one tell me why?08:07
*** markvoelker has quit IRC08:10
*** markvoelker has joined #openstack-nova08:10
openstackgerritTakashi NATSUME proposed openstack/nova master: Replace 'is comprised of' with 'comprises'  https://review.opendev.org/66317508:14
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove unnecessary setUp methods  https://review.opendev.org/66317908:14
*** markvoelker has quit IRC08:15
*** _hemna has joined #openstack-nova08:22
*** imacdonn has quit IRC08:38
*** ociuhandu has joined #openstack-nova08:38
*** imacdonn has joined #openstack-nova08:38
*** xek_ has quit IRC08:40
*** tkajinam_ has quit IRC08:52
*** _hemna has quit IRC08:57
*** markvoelker has joined #openstack-nova09:11
*** owalsh has quit IRC09:26
*** owalsh has joined #openstack-nova09:27
*** jaosorior has joined #openstack-nova09:30
*** takashin has left #openstack-nova09:33
*** markvoelker has quit IRC09:44
openstackgerritEdward Hope-Morley proposed openstack/nova master: Fix python3 compatibility of rbd get_fsid  https://review.opendev.org/66360709:45
*** _hemna has joined #openstack-nova09:46
openstackgerritBrin Zhang proposed openstack/nova master: Specify availability_zone to unshelve  https://review.opendev.org/66385109:52
*** luksky has quit IRC09:55
*** slaweq has quit IRC09:57
*** cdent has joined #openstack-nova10:02
*** guozijn has quit IRC10:09
*** priteau has joined #openstack-nova10:10
*** _hemna has quit IRC10:21
*** frankwang has quit IRC10:24
*** bhagyashris has quit IRC10:36
*** davidsha has joined #openstack-nova10:37
*** udesale has quit IRC10:37
*** luksky has joined #openstack-nova10:41
*** guozijn has joined #openstack-nova10:46
openstackgerritsean mooney proposed openstack/nova master: libvirt: delegate ovs plug to os-vif  https://review.opendev.org/60243210:50
*** brinzhang has quit IRC10:57
*** jaypipes has joined #openstack-nova11:02
openstackgerritStephen Finucane proposed openstack/nova master: Recalculate 'RequestSpec.numa_topology' on resize  https://review.opendev.org/66252211:04
openstackgerritStephen Finucane proposed openstack/nova master: tests: Cleanup of '_test_resize' helper test  https://review.opendev.org/66424511:04
*** _hemna has joined #openstack-nova11:10
*** slaweq has joined #openstack-nova11:18
*** nicolasbock has joined #openstack-nova11:24
*** abhishekk has quit IRC11:25
*** rcernin has joined #openstack-nova11:32
*** ttsiouts has joined #openstack-nova11:35
*** ttsiouts has quit IRC11:37
*** ttsiouts has joined #openstack-nova11:37
*** guozijn has quit IRC11:40
*** markvoelker has joined #openstack-nova11:41
*** ttsiouts has quit IRC11:42
*** rcernin has quit IRC11:43
*** _hemna has quit IRC11:45
*** BjoernT has joined #openstack-nova11:46
*** BjoernT has quit IRC11:51
*** jroll has quit IRC11:54
*** guozijn has joined #openstack-nova11:54
*** jroll has joined #openstack-nova11:54
*** keerthidg has joined #openstack-nova11:55
*** guozijn has quit IRC11:57
*** slaweq has quit IRC12:03
*** tbachman has joined #openstack-nova12:05
*** lbragstad has joined #openstack-nova12:08
*** edleafe has joined #openstack-nova12:13
*** ratailor_ has quit IRC12:14
*** markvoelker has quit IRC12:15
*** janki has quit IRC12:18
*** slaweq has joined #openstack-nova12:24
*** udesale has joined #openstack-nova12:25
*** _hemna has joined #openstack-nova12:34
*** lpetrut has joined #openstack-nova12:37
*** _hemna has quit IRC13:09
*** markvoelker has joined #openstack-nova13:12
*** _hemna has joined #openstack-nova13:16
*** artom has quit IRC13:16
*** jdillaman has joined #openstack-nova13:27
stephenfinefried: I'd like a python-novaclient release with https://review.opendev.org/#/c/650363/ in it. Have proposed https://review.opendev.org/#/c/664259/, assuming that's okay?13:28
openstackgerritStephen Finucane proposed openstack/nova master: tests: Add '_setup_compute_services' helper  https://review.opendev.org/66310213:32
*** eharney has joined #openstack-nova13:32
*** tbachman has quit IRC13:33
*** yikun has quit IRC13:41
*** _hemna has quit IRC13:43
*** markvoelker has quit IRC13:45
*** dave-mccowan has joined #openstack-nova13:46
efriedstephenfin: looking13:47
*** slaweq has quit IRC13:47
*** ricolin has joined #openstack-nova13:50
efriedstephenfin: gross. Are you going to blacklist all 8 versions the original got included in, for py27?13:51
efriedI guess if this only affects the CLI, no need for that.13:51
stephenfinI don't think so13:51
stephenfinIt's a lot of effort and I figure distros will pick this up pretty quickly13:51
dansmithis gibi out?13:51
efriedstephenfin: +113:53
*** mriedem has joined #openstack-nova13:54
*** dave-mccowan has quit IRC13:56
*** jistr is now known as jistr|call14:00
*** _alastor_ has joined #openstack-nova14:08
*** jistr|call is now known as jistr14:16
stephenfinefried: Want to take a look at this too and unblock the rest of the series https://review.opendev.org/#/c/651311/14:20
efriedstephenfin: Will do. I was just looking at the "all call super" patch in that series...14:21
stephenfinAlso got https://review.opendev.org/#/c/660950/ working, though that's lower priority (turns out it's 'foo(x=None, *args, **kwargs)' and not 'foo(*args, x=None, **kwargs)', but flake8 doesn't catch that)14:21
stephenfinHeh, jinx14:21
*** dpawlik has quit IRC14:24
efriedstephenfin: bottom one is +A.14:29
efriedimo the super one shouldn't be adding *args or **kwargs anywhere they weren't already.14:29
*** slaweq has joined #openstack-nova14:29
*** lpetrut has quit IRC14:31
*** mlavalle has joined #openstack-nova14:32
*** maciejjozefczyk has joined #openstack-nova14:36
openstackgerritMatt Riedemann proposed openstack/nova master: Make get_provider_by_name public and remove safe_connect  https://review.opendev.org/66406214:36
*** keerthidg has quit IRC14:37
openstackgerritStephen Finucane proposed openstack/nova master: Ensure controllers all call super  https://review.opendev.org/66095014:38
stephenfinefried: Cool. Fixed the super one by removing all the *args and **kwargs (none of them were necessary, fwict) ^14:38
*** maciejjozefczyk has quit IRC14:42
*** markvoelker has joined #openstack-nova14:42
*** itlinux_ has quit IRC14:48
efriedstephenfin: Cool man, +2.14:53
stephenfinmriedem, sean-k-mooney: What am I missing here? I see only one callers to the revert_resize function and that's from the API https://review.opendev.org/#/c/662522/3/nova/compute/api.py@342014:53
stephenfinWe wouldn't call "openstack resize --revert" on a failed migration, would we?14:53
*** slaweq has quit IRC14:54
sean-k-mooneystephenfin: im pretty sure we use teh revert_resize api endpoint to revert a cold-migration14:54
mriedemstephenfin: cold migrate == resize except same flavor14:55
mriedemit's the same code flow14:55
stephenfinI realize that14:55
stephenfin100%14:55
mriedemyour comment says, "This is the 'revert_resize' function. There's no way we could get here  for anything unless we were doing a revert of the resize operation (i.e.  no cold migration flow through here), right?"14:55
stephenfinbut would a user revert a cold migration14:55
mriedemyes14:55
mriedemsure14:55
sean-k-mooneystephenfin: yes they can14:55
mriedemjust because it's called "resize" doesn't mean it's not also used by the cold migrate flow14:55
mriedemsame as rebuild is used for evacuate14:55
stephenfinSeriously? Why can't I find any documentation on the internet about this?14:56
sean-k-mooneybecause its an internal detail of nova implemeation14:56
sean-k-mooneyit should be in a dev ref14:56
stephenfinThe ability of a user to revert their failed cold migration is a internal detail?14:56
stephenfinHow it's implemented, sure, but not the raw ability to do the thing14:57
sean-k-mooneyits in the api ref14:57
mriedemfor one, users don't cold migrate, admins do14:57
mriedemhttps://developer.openstack.org/api-ref/compute/?expanded=migrate-server-migrate-action-detail#migrate-server-migrate-action14:57
mriedem"after a successful cold migration and then must be confirmed or reverted."14:57
stephenfinthe more you know14:58
sean-k-mooneyi think revert does not require admin  https://developer.openstack.org/api-ref/compute/?expanded=migrate-server-migrate-action-detail,revert-resized-server-revertresize-action-detail#migrate-server-migrate-action14:58
sean-k-mooneyexcept as indicated in teh precondions14:58
mriedem"Policy defaults enable only users with the administrative role to perform this operation. "14:58
*** BlackDex has quit IRC14:58
mriedemcold migrate is admin_api by default14:59
stephenfinHmm, why don't we have an 'openstack server migrate --revert' thing for this?14:59
mriedemwe do14:59
mriedemhttps://docs.openstack.org/python-openstackclient/latest/cli/command-objects/server.html#server-resize14:59
mriedemresize --revert14:59
stephenfinthat's 'resize --revert', not 'migrate --revert'15:00
mriedemthey hit the same api15:00
stephenfinThen why have an 'openstack migrate' command15:00
mriedemfor cold and live migration15:00
mriedemwhich are not resizes15:00
stephenfinlive migration, sure, but not cold migration15:01
stephenfinthat's the same thing but with the same image?15:01
stephenfin*flavor15:01
*** artom has joined #openstack-nova15:01
sean-k-mooneystephenfin: we could delete migrate and jsut use resize for the cold migration case but most user dont think a resize and migration are the same thing15:02
mriedemcold migrate == resize but with no flavor change15:02
stephenfinsean-k-mooney: Yeah, that's my point. Why would a user think "oh, my migration failed. Best revert this resize"15:02
sean-k-mooneymigrate is just syntactic sugar over resize really.15:03
stephenfinyeah15:03
mriedemnote that a revert isn't to recover a failed move15:03
mriedemyou can only revert if the resize/cold migration *didn't* fali15:03
mriedem*fail15:03
stephenfinActually, yeah, I've done this in tests now that I think about15:03
stephenfin*it15:03
stephenfin(Or rather avoided doing it because confirming a resize/migration requires a lot of mocking out of libvirt stuff in functional tests that's not worth the effort)15:04
stephenfinmriedem: I think a '--revert' flag for the 'openstack server migrate' command would be helpful syntactic sugar. Any reason not to?15:05
mriedemif you're concerned about docs, you could update the description on https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/server.html#server-migrate to talk about how after a successful cold migration you need to revert or confirm the migration and which commad does that15:05
stephenfinI can do that too, sure15:05
mriedemidk, ask dean. one reason could be someone thinking they could revert a live migration since that's built into the same command.15:05
Nick_Asorry if this is not the right place - we have a kvm compute with qcow2, but snapshots are being stored as raw. is there a setting we're overlooking to take snapshots as qcow2?15:05
mriedembut that's likely solved with a good description of the parameter and validation in the command.15:05
stephenfinI'm annoyed that I work on this stuff and _I_ wasn't able to find information about this easily. That seems...silly :)15:05
stephenfinYeah, we already have that issue for other flags so this is just one more15:06
mriedemNick_A: probably this https://docs.openstack.org/nova/latest/configuration/config.html#DEFAULT.force_raw_images15:06
Nick_Athank you, looking15:07
mriedemNick_A: I think glance also has an option to convert everything to raw15:07
stephenfinOkay, I'll start on that. Thanks for the clarification, mriedem, sean-k-mooney15:07
sean-k-mooneystephenfin: there are some docs here too https://github.com/openstack/nova/blob/master/doc/source/admin/migration.rst15:08
mriedemNick_A: I think this https://docs.openstack.org/glance/latest/configuration/glance_api.html#taskflow_executor.conversion_format15:09
sean-k-mooneystephenfin: we show we use "openstack server resize --confrim" to confrim the migration but not how to revert15:09
Nick_Athank you15:09
stephenfinsean-k-mooney: Sweet, I'll fix that too and add some some 'migrate --confirm' syntactic sugar for good measure15:10
*** hongbin has joined #openstack-nova15:13
openstackgerritMatt Riedemann proposed openstack/nova stable/stein: Avoid unnecessary joins in InstanceGroup.get_hosts  https://review.opendev.org/66427115:15
*** _alastor_ has quit IRC15:16
*** markvoelker has quit IRC15:16
*** ivve has quit IRC15:26
*** luksky has quit IRC15:34
dansmithmriedem: are you going to update the pre-filter disabled computes spec?15:40
dansmithI assume gibi is on vacay or something and hasn't circled back,15:40
dansmithbut I figure he's probably fine with it as long as we have a plan for that (which we do)15:40
mriedemdansmith: i was waiting for gibi15:41
dansmithokay15:42
mriedemwhat was the plan again? :) on disable, check if down and if down, return 200 (like if it was an old compute) and let upt sync the trait on restart of the service15:43
*** helenafm has quit IRC15:43
mriedemif that's the plan i can write that edge case into the spec15:44
dansmithyeah, always set compute.disabled=True, not make the rpc call if it's down, return 20015:44
mriedemok i can wordsmith that after tearing up artom's patch here15:44
dansmithby all means, prioritize tearing up anything of artom's15:44
artom;_:15:44
artom(That's from both emotional and physical pain)15:45
*** ericyoung has quit IRC15:48
aspiersstephenfin: ok to add you to reviewers for a couple of SEV patches which need more core attention? they're not particularly big or complex15:48
stephenfinsure15:48
aspiersthanks!15:48
*** ericyoung has joined #openstack-nova15:49
*** BlackDex has joined #openstack-nova15:52
*** wwriverrat has quit IRC15:53
*** itlinux has joined #openstack-nova15:54
*** itlinux has quit IRC15:56
*** _alastor_ has joined #openstack-nova15:58
*** itlinux has joined #openstack-nova16:00
mriedemartom: sean-k-mooney: mdbooth: dansmith: comments in https://review.opendev.org/#/c/644881/16:00
artomWhoa, you weren't kidding about tearing up16:01
mdboothWhoa!16:01
mdboothmriedem: Thanks, btw16:01
artomsean-k-mooney, correct me if I'm wrong, but I don't believe "The bigger issue I have is the concern that we could have a server with both ovs hybrid plugged ports and ports without that" is possible16:02
sean-k-mooneyit is only posible if you have ovs +sriov ports16:03
sean-k-mooneye.g. if they are all ovs ports then it would all be hybrid_plug true or false16:03
artomsean-k-mooney, ah, so ports on which the firewall driver that causes hybrid plug to be used doens't apply16:03
sean-k-mooneybut if you have some vswitch prot for say managmenet and some sriov ports for the data plane then you could have a mixx16:04
artom(https://review.opendev.org/#/c/660782/6/playbooks/legacy/nova-multinode/run.yaml@55)16:04
sean-k-mooney right so if you are using sriov there is no firewall16:06
artomSo... do we need to handle that? Ie, wait for hybrid plugged ports in the compute manager, and for the sriov ones in the virt driver?16:06
artomOr is there no vif to plug for the latter case, so it's irrelevant?16:06
mriedemor will you get an event regardless b/c of the port binding change, in which case you don't need to filter on ovs hybrid plug in the compute manager16:07
sean-k-mooneythat is a good question there should be a vif plugged in that case16:07
sean-k-mooneyso i guess we would16:07
mriedemwhich would take this change back to when artom, dansmith and i talked about it on hangouts 2 months ago16:07
sean-k-mooneywe would get an event for the sriov port16:09
artom*sigh*16:09
artomI suppose we better test it16:10
sean-k-mooneybut im trying to remeber when16:10
sean-k-mooneyplug is a noop for sriov. it is handeled by libvirt.16:10
artomActually, wait16:11
artomIs resizing an instance with SRIOV supported?16:11
sean-k-mooneyyes16:11
sean-k-mooneyits kind of buggy but yes16:11
*** igordc has joined #openstack-nova16:12
sean-k-mooneyalthogh https://review.opendev.org/#/q/topic:bug/1809095+(status:open+OR+status:merged) will fix the most recent one16:12
*** markvoelker has joined #openstack-nova16:13
sean-k-mooneythis is concerning https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/mech_sriov/mech_driver/mech_driver.py#L131-L14316:16
artomI suppose I could hax _get_neutron_events_for_migration() to be smart about what vifs it returns...16:16
artomThat seems fragile as hell, event more than the patch in its current form16:16
sean-k-mooneyif the the prot is a PF https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/mech_sriov/mech_driver/mech_driver.py#L163-L16816:16
sean-k-mooneywe will send the event when we update the binding16:17
sean-k-mooneyif the port if a vf we will send the event when the agent wires it up16:17
artomAt point do we just say screw it and start queuing reveived events?16:18
artom*At what16:18
artomOr unload all those problems on Neutron and tell them to send the events consistently?16:18
sean-k-mooneywell https://review.opendev.org/#/c/645173/ is ment to help with this16:19
artomBecause assuming what sean-k-mooney is saying is True (and I have no reason to doubt it, but it def needs testing), we now have 3 different port "types" that we need to be aware of16:19
sean-k-mooneybut i have not been working on it because of other stuff like RDT/CAT16:19
artomsean-k-mooney, yeah, but depending on that spec would make the Nova patch unbackportable, which I'm trying to avoid16:20
artom(Never mind that it would take forever16:21
artom)16:21
sean-k-mooneyright also i have not had time to work on it for a month and likely wont in the short term as i have nto figured out how to expresss when the event will be sent yet in an abstct way16:21
artomI guess "do what we did before (wait in libvirt), except for known cases where it doesn't work and we have to do new thing (wait in compute manager)" would be a valid guiding principle16:22
artomI'm gonna go get lunch, then try and see if I can code that in a palatable way16:23
sean-k-mooneyyou would have to wait if hybrid_plug=true or vnic_type=direct-physical16:23
sean-k-mooneyin the manager16:23
sean-k-mooneyelse waith in the driver16:23
artomsean-k-mooney, so, that latter part hasn't actually come up (yet?), so I don't think I want to include it16:23
artomBut I'm going to try to genericize my _uses_hybrid_plug() method a bit to make it extensible16:24
sean-k-mooneywe could fix sriov in a sperate patch?16:24
sean-k-mooneyartom: mriedem  thoughts ^16:24
artom... and also do as yet unclear things to allow the compute manager to communicate to the virt driver *which VIFs* it needs to listen to events for16:25
artomOr some other way of achieving the same effect16:25
sean-k-mooneyartom: we would need to be able to express on a per vf bassis if we should wait which is what i want to do with that sepec anyway16:25
artomsean-k-mooney, yeah, it's basically the same, just without the Neutron part16:25
sean-k-mooneywe would have to embed logcici into the vif object to encode "wait in dirver" or what ever instead of using a flag for all vifs yes16:26
artomsean-k-mooney, that's not going to be backportable either, is it?16:27
sean-k-mooneythe vif "objects" we store in the networkin info cache are dicts so its not versioned16:28
efriedstephenfin: I've got a permalink in nova docs16:28
efriedhttps://opendev.org/openstack/nova/blame/commit/1316c1c2850d2f966f335b628f7f5fe88cef611c/doc/source/user/flavors.rst#L77616:28
efriedthat I want to use from a reno. How do I do that?16:28
sean-k-mooneybut i would have to check the code to determin that16:29
efriedstephenfin: I don't think I can just use extra-specs-numbered-resource-groupings_ - because the renos and the docs are in separate repositories?16:29
mriedemefried: https://docs.openstack.org/nova/latest/user/flavors.html#extra-specs-numbered-resource-groupings16:29
mriedemunless nova-doc works in reno builds16:29
stephenfinefried: https://docs.openstack.org/nova/latest/user/flavors.html#extra-specs-numbered-resource-groupings16:30
stephenfinyeah16:30
stephenfinit doesn't because release note builds aren't versioned16:30
efriedstephenfin: mriedem: Right, so I have to use the whole URL, okay. Thanks.16:30
artomsean-k-mooney, oh, those VIFs. Well, we have what we need already, no? ovs_hybrid_plug and type16:30
sean-k-mooneyartom: ya the vif you are using in that code is an instance of nova.network.model.Vif https://github.com/openstack/nova/blob/master/nova/network/model.py#L38016:30
sean-k-mooneyyes we do16:30
*** davidsha has quit IRC16:31
sean-k-mooneybut if you wanted to add a flag so you did not check bot of those you could add a property to that class that return a vlaue base on if ether of the dict values were set16:31
sean-k-mooneye.g. put the logic to wait into the Vif class and have a property "wait_location" that return "driver" or "manager" based on the vnic_type or hybrid_plug16:32
sean-k-mooneyartom: like https://github.com/openstack/nova/blob/master/nova/network/model.py#L46116:32
sean-k-mooneyi guess it could be just a fuction too16:33
aspiersefried: according to the SEV spec, our current plan is to add hw:mem_encryption to flavor extra specs and image properties, but I've just noticed that while existing extra specs params use the "hw:" prefix, image properties all use the "hw_" prefix. Presumably I should remain consistent with those conventions?16:33
artomsean-k-mooney, not sure about putting logic in the model itself, but yeah, it's an idea16:33
mriedemsean-k-mooney: so as it stands, artom's patch will do:16:34
sean-k-mooneyartom: well we have is_hybrid_plug_enabled in the Vif object16:34
mriedem1. if all ports are ovs_hybrid_plug=True, wait for all in the manager and you're fine,16:34
artom0. drive artom to even moar excessive alcoholism16:34
mriedem2. if all ports are ovs_hybrid_plug=false, wait in the driver and you're fine (tested in the gate),16:34
artomsean-k-mooney, yeah, but that's basically just a getter16:34
mriedem3. if some ports are ovs_hybrid_plug=True but not all, we'll wait for all events for all ports in the manager and some might not come (at least direct-physical)16:35
*** ricolin has quit IRC16:35
*** udesale has quit IRC16:35
sean-k-mooneymriedem: correctr16:35
mriedemok so based on #3,16:35
mriedemwhat if we only wait for the known ones in the manager (ovs_hyrbid_plug=True),16:36
*** gyee has joined #openstack-nova16:36
sean-k-mooneydirect-pysical will be the same as ovs_hyrbid_plug=True16:36
mriedemand if there are others, we pass vifs_already_plugged=False to the driver? that would fail in the ovs_hybrid_plug=true ports b/c we already processed that event yeah?16:36
*** takamatsu has quit IRC16:36
sean-k-mooneyvnic_type=direct and macvatap are teh same as ovs_hyrbid_plug=False and will arrive at the dirver16:36
sean-k-mooneymriedem: yes it would fail for ovs_hyrbid_plug=True because we already processed it16:37
mriedemi'm trying to get at some best effort kind of logic if we don't have good enough details from neutron and when we get the events from neutron is inconsistent per backend (which we know it is)16:37
mriedemthinking like, compute manager waits for all that are ovs_hybrid_plug=True and if there are others (a mix), we pass vifs_already_plugged=True so the driver doesn't wait16:38
sean-k-mooneyif we get a mix we could just not wait at all or wait wait for the ones we expect in the manager and not wait in the driver16:38
mriedemyup i just said the same16:38
sean-k-mooneyya that would work16:39
sean-k-mooneyits technically racy but its better then what we have today16:39
sean-k-mooneybut i also think it would be simple to have the driver check if it should wait per vif16:39
mriedemin the #2 case where none of the ports are ovs_hybrid_plug=True, we'd pass vifs_already_plugged=false to the driver and assume the driver will wait and get all of the events after it plugs16:39
sean-k-mooneyinstead of needing to set teh flag16:39
sean-k-mooneyyep16:39
sean-k-mooney1 and 2 are easy16:40
openstackgerritEric Fried proposed openstack/nova master: Defaults missing group_policy to 'none'  https://review.opendev.org/65779616:40
sean-k-mooneybut we really shoudl be checking "ovs_hyrbid_plug=True or vnic_type=direct-physical"16:41
mriedemhow many different types of vifs are in the wild?16:41
sean-k-mooneytechnically its a finite set defiend in neutron lib16:41
sean-k-mooneybut not all backend will treat them all the same16:41
mriedemi just kind of vomit in my mouth a bit when we try encoding this in nova16:41
efriedaspiers: Yes16:41
sean-k-mooneymriedem: ya i know it sucks16:42
artommriedem, we really shouldn't have to in theory16:42
artomBut reality and all that16:42
efriedaspiers: And if you're collecting a spec tweak fup patch, clarify in there.16:42
sean-k-mooneyfor what its worth however i think we can encode it here in a new 3 line function https://github.com/openstack/nova/blob/master/nova/network/model.py#L46116:42
artomsean-k-mooney, yeah, that part's not hard16:43
artomIt's how we use it that I'm fuzzier on16:43
artomIe, split events to be waited for between compute and libvirt16:43
artomI'm making an executing decision: ph00d, then hax. A patch, even broken WIP, is better than endless discussion16:44
mriedemi'm not terribly comfortable in backporting something that gets this complicated especially since we don't test any of these vif types in the gate16:44
sean-k-mooneye.g. def wait_in_manager(self):16:44
sean-k-mooney retrun self.is_hybrid_plug_enabled or self.get("vnic_type") == "direct-physical"16:44
mriedemartom: hacking something up that you do'nt have agreement on from the people reviewing it isn't going to speed this up16:45
sean-k-mooneythen in the manager an driver we just do if vif.wait_in_manager():16:45
artommriedem, I thought we kinda did?16:45
mriedemhow about, 1. artom gets food, 2. sean comments on the change16:45
mriedem3. artom digests both16:45
artommriedem, for backporting, if we split the patch and only backport the hybrid stuff?16:45
artomLeaving the SRIOV stuff for master only16:45
*** markvoelker has quit IRC16:46
*** takamatsu has joined #openstack-nova16:46
sean-k-mooneyartom: or we can backport this downstream only if we really have to16:46
sean-k-mooneybut ill comment on the review i think we can make this simpler16:46
*** whoami-rajat has quit IRC16:46
artomsean-k-mooney, it's always an option, but not my first one, obviously16:46
sean-k-mooneyi think if we only fix it for ovs we will get a bug report form a different custoemr for sriov16:47
openstackgerritStephen Finucane proposed openstack/nova master: docs: Document how to revert, confirm a cold migration  https://review.opendev.org/66439616:47
sean-k-mooneyso we will have to fix both eventually16:47
artomsean-k-mooney, yeah, and that's fine, and we can address it later16:47
artomEspecially since it'd be as simple as adding a check to that 3-line method of yours :)16:47
artomWe could even do it now in a fup patch, and backport if/when some testing happens16:48
sean-k-mooneyits actully 2 lines :P untill we have pep8 it16:48
artom*fup patch now16:48
artom(Though realistically it shouldn't merge until if/when some testing happens :)16:49
*** cfriesen has joined #openstack-nova16:52
openstackgerritMatt Riedemann proposed openstack/nova master: Deprecate RetryFilter  https://review.opendev.org/66395317:02
*** ociuhandu has quit IRC17:05
openstackgerritAdam Spiers proposed openstack/nova-specs master: Change new image property to hw_mem_encryption  https://review.opendev.org/66439717:06
*** lpetrut has joined #openstack-nova17:09
*** mvkr has quit IRC17:12
*** takamatsu has quit IRC17:15
*** lpetrut has quit IRC17:18
*** luksky has joined #openstack-nova17:20
*** itlinux has quit IRC17:25
aspiersefried: should I hold off including doc change fragments covering SEV support until the whole series lands?17:26
efriedaspiers: "doc change fragments" in the spec or in the codebase?17:27
aspierscodebase17:27
aspiersotherwise there's a risk of documenting stuff which doesn't work yet17:27
aspiersespecially if it didn't all land before Train17:27
efriedRight, those go in in the patch that flips the switch that makes it work.17:27
aspiersOK thanks17:27
efrieddocs & reno etc.17:27
aspiersYup17:27
*** itlinux has joined #openstack-nova17:29
*** itlinux has quit IRC17:31
*** ralonsoh has quit IRC17:33
*** itlinux has joined #openstack-nova17:35
*** takamatsu has joined #openstack-nova17:36
*** amodi has quit IRC17:40
*** markvoelker has joined #openstack-nova17:43
*** takamatsu has quit IRC17:43
*** spatel has joined #openstack-nova17:45
spatelsean-k-mooney: is there anyway to stop migration instance? I have initiate block migration and i want to cancel it17:45
sean-k-mooneyspatel: as in cancel a livemigration17:46
sean-k-mooneyi think we have a way too17:46
sean-k-mooneylet me check17:46
sean-k-mooneyi know people have asked for it before17:46
spateli didn't find any command line option or GUI option17:46
sean-k-mooneywell what you can do with crul directly to the api is > then the clis enable17:47
sean-k-mooneyi dont know if we ever landed the force complete and force abourt apis however17:47
spatel?17:47
sean-k-mooneywe dont always get around to adding everyting that the api support to the command line clients17:48
sean-k-mooneyor somethimes it takes a while17:48
spatelwhat if i kill TCP connection which is transferring disk17:49
sean-k-mooneyspatel: you can abort it via libvirt using virsh17:49
sean-k-mooneyspatel: so ya it looke like you can use the old nova cli17:50
sean-k-mooneynova live-migration-abort INSTANCE_ID MIGRATION_ID or nova live-migration-force-complete INSTANCE_ID MIGRATION_ID17:51
sean-k-mooneyspatel: https://docs.openstack.org/nova/pike/admin/live-migration-usage.html#addressing-migration-timeouts17:51
sean-k-mooneyspatel: nova live-migration-abort is what you are looking for.17:52
spatellet me see17:52
sean-k-mooneyyou need the instance id + the migration_id for the currently running migration17:52
sean-k-mooneyyou get the migration id by doing "nova server-migration-list <server/instance uuid>"17:53
spatelhow do i find MIGRATION_ID?17:54
sean-k-mooneyspatel: ^ :)17:54
sean-k-mooneyspatel: its covered in the monitoring migration part of that doc https://docs.openstack.org/nova/pike/admin/live-migration-usage.html#monitoring-the-migration17:54
spatelreading it..17:55
sean-k-mooneydoes that make sense you do "nova server-migration-list <server id>"17:57
sean-k-mooneythen that give you the list of migrations.17:57
sean-k-mooneythen if you have more then one you use nova server-migration-show <server uuid > <migration id>17:58
sean-k-mooneyto see which one was the most recent17:58
sean-k-mooneyand then that one is the migration you want to canchel with17:58
sean-k-mooneynova live-migration-abort INSTANCE_ID MIGRATION_ID17:58
spatelnova server-migration-list <server id>  this is showing nothing about migration except saying | OS-EXT-STS:task_state               | resize_migrating18:00
-spatel- [root@ostack-osa ~(keystone_admin)]# openstack server show 580e624f-d1c9-496c-a591-a36c2de92e62 | grep mig18:00
-spatel- | OS-EXT-STS:task_state | resize_migrating18:00
spateli am not seeing any ID...18:00
*** psachin has quit IRC18:02
*** itlinux has quit IRC18:03
sean-k-mooneyspatel: am can you past the output to paste.openstack.org. feel free to remove anything sensitive18:04
*** mgariepy has quit IRC18:04
sean-k-mooneynova server-migration list shoudl vice you an output that start with Id | Source Node | Dest Node ....18:04
sean-k-mooneythe Id colum is the migration id18:05
spatelhmm18:06
*** mgariepy has joined #openstack-nova18:07
spatelhttp://paste.openstack.org/show/752693/18:09
spatelsean-k-mooney: ^^18:09
sean-k-mooneyspatel: openstack server show  not migration list18:09
*** itlinux has joined #openstack-nova18:09
sean-k-mooneydo "nova migration-list --instance-uuid 580e624f-d1c9-496c-a591-a36c2de92e6218:10
sean-k-mooney"18:10
spatelI can see lots of info npw18:11
spatelnow18:11
*** itlinux has quit IRC18:11
sean-k-mooneyok do you have more then 1 row18:11
sean-k-mooneyif not you just need the value of the ID colum18:11
*** itlinux has joined #openstack-nova18:12
sean-k-mooneythen you can do "nova live-migration-abort 580e624f-d1c9-496c-a591-a36c2de92e62 <id>18:12
sean-k-mooney"18:12
spatelhttp://paste.openstack.org/show/752695/18:12
spatelsean-k-mooney: ^618:12
sean-k-mooneyya so it would be18:13
spatelis that UUID is migration ID?18:13
sean-k-mooney"nova live-migration-abort 580e624f-d1c9-496c-a591-a36c2de92e62 384"18:13
sean-k-mooneymp Id18:13
sean-k-mooney*no18:13
sean-k-mooneyit the first column18:13
sean-k-mooneythe UUID column is the instance uuid18:13
*** itlinux has quit IRC18:13
spatelto abort it i need migration ID right ( that i not able to find :( )18:14
*** itlinux has joined #openstack-nova18:14
sean-k-mooneyspatel: so as i said its call Id in the output18:14
sean-k-mooneyso in this case it 384 and the command would be "nova live-migration-abort 580e624f-d1c9-496c-a591-a36c2de92e62 384"18:14
spatel38418:15
sean-k-mooneyyep does that make sense18:15
*** markvoelker has quit IRC18:17
*** mriedem has quit IRC18:17
sean-k-mooneythe migration has a UUID also but which is the firt UUID column i miss typed earlirer but the id colume "384" is what you were looking for. let me kno if that works for you :)18:18
spatelhttp://paste.openstack.org/show/752698/18:19
*** mriedem has joined #openstack-nova18:19
spatelsean-k-mooney: ^^18:19
sean-k-mooneyok so it looks like we dont allow you to abort if its already copying the guest memory... that seams weird18:20
*** _alastor_ has quit IRC18:21
sean-k-mooneyspatel: are you doing a live migration or a cold migration18:21
spatelMy compute nodes attached to shared storage.18:22
spatelso live migration isn't possible it has to be block migration18:22
*** takamatsu has joined #openstack-nova18:22
sean-k-mooneylive migration is unrealted to shared storage18:22
spatelmy compute nodes **NOT** attached to shared storage18:22
sean-k-mooneyand if you are on shared storage you do not use block migration18:22
sean-k-mooneyah18:22
sean-k-mooneywhat command did you use to start the migration18:23
spatelOh! wait.. i though live migration only possible when you are using shared storage like ceph18:23
sean-k-mooneyno you can do live migration with block storage too18:23
sean-k-mooneywe just rsync the disk image to the destaion18:23
spatelI didn't do anything, someone else just drop down in horizon and said "live migrate"18:23
sean-k-mooneyor rather libvirt does18:23
sean-k-mooneyah ok just making sure its a live migration18:24
spatelI meant "Migrate instance" option in GUI18:24
sean-k-mooneyok so that is different18:24
spatelwhat is the difference between18:24
*** whoami-rajat has joined #openstack-nova18:24
sean-k-mooneythe instance is shutdown http://paste.openstack.org/show/752693/18:24
sean-k-mooneyso its doing a cold or offline migration18:24
spatel"Migrate instance" vs "Live migration" in GUI drop down?18:24
sean-k-mooneymigrate instance in horizon i think is a cold migration18:25
sean-k-mooneyi would have to double check.18:25
spatelWe powered down machine before migration (its safe)18:25
*** takamatsu has quit IRC18:25
sean-k-mooneywell live migration are only done if the vm is running18:25
*** takamatsu has joined #openstack-nova18:25
sean-k-mooneythat what makes the a live migration18:26
sean-k-mooneyso the api i asked you to try is only used for live migration but you are doing a cold migration18:26
spatelI talled to you couple month back NOVA has bug which doesn't copy full disk and that cause instance never get full migrate...18:26
spatelI am worried about that bug... (someone did migration without checking with me) now i want to stop this :(18:26
sean-k-mooneyi vaguly rememeber that yes18:26
sean-k-mooneymriedem: is there any way to stop a cold migration that is in flight?18:27
*** priteau has quit IRC18:27
sean-k-mooneymriedem: can we revert it18:27
mriedemnope18:27
spatelnova start block migration and then kill it source disk without verifying full disk migration.. that was the bug18:27
sean-k-mooneywhen the instance is in task_sate resize_migrating18:27
sean-k-mooneymriedem: what about reseting the state on the vm?18:28
*** nicolasbock has quit IRC18:29
*** nicolasbock has joined #openstack-nova18:29
mriedemsean-k-mooney: that would reset the task_state to None so you'd maybe fail somewhere along the way in compute if it tries to update the task_state and is using instance.save(expected_task_state=...)18:29
mriedembut clearly that's not any kind of supported way to interrupt a cold migration18:30
*** priteau has joined #openstack-nova18:30
sean-k-mooneymriedem: yes i know18:30
*** _alastor_ has joined #openstack-nova18:30
spatelcold migration = when machine is shutdown it does cold migration ?18:30
spatelis that true?18:31
sean-k-mooneyspatel: by machine you mean the vm?18:31
mriedemNTT (i think it was NTT) had a spec up for several releases to add support to abort a cold migration, with the main reason being "we shove logs into a 100GB+ local disk and migrating those VMs takes a long time so we'd maybe like to abort the cold migration"18:31
spatelyes machine = VM18:31
sean-k-mooneymriedem: ya i vaguly rememebr that18:31
sean-k-mooneyspatel: do you have nova configured to auto confim migrations/resize18:32
sean-k-mooneyspatel: if not then nova will not delete the souce disk unless you confim the resize.18:32
spatelNO i don't have auto confim18:33
sean-k-mooneyat which point you can either boot up the vm and check its ok or you can do "nova resize-revert <server uuid>"18:33
spateloh! can i boot instance without confirm ?18:33
sean-k-mooneyi think so. i have not tried this in quite a while.18:34
*** _alastor_ has quit IRC18:35
sean-k-mooneymaybe we cant but i know that has also been asked for in the past18:35
sean-k-mooneyspatel: in anycase when the migration eventually complete you can revert it which will be quick as teh data will not have been delete on the souce node.18:36
openstackgerritAdam Spiers proposed openstack/nova master: Add extra spec parameter and image property for memory encryption  https://review.opendev.org/66442018:36
aspiersefried: is this roughly along the right lines? ^^^18:37
spateli will revert it without confirm it18:38
efriedaspiers: I'm going to have to look a bit later, I'm afraid.18:38
*** amodi has joined #openstack-nova18:38
aspiersefried: np. Don't need a full review yet, just confirmation I'm barking up the right tree18:38
*** ivve has joined #openstack-nova18:39
*** tbachman has joined #openstack-nova18:43
*** cdent has quit IRC18:52
*** francoisp has quit IRC18:54
spatelsean-k-mooney: revert works!18:55
spatelwhat a pain :)18:55
spatelsean-k-mooney: thank you again for saving my a... :)18:56
*** bbowen has joined #openstack-nova19:03
openstackgerritMatt Riedemann proposed openstack/nova-specs master: Spec to pre-filter disabled computes with placement  https://review.opendev.org/65788419:14
*** markvoelker has joined #openstack-nova19:14
*** amodi has quit IRC19:21
*** ociuhandu has joined #openstack-nova19:43
*** markvoelker has quit IRC19:47
*** dave-mccowan has joined #openstack-nova19:48
*** eharney has quit IRC19:51
openstackgerritArtom Lifshitz proposed openstack/nova master: WIP: Revert resize: wait for events according to hybrid plug  https://review.opendev.org/64488119:53
openstackgerritArtom Lifshitz proposed openstack/nova master: Remove finish_revert_migration TypeError try/except  https://review.opendev.org/66401319:53
*** tbachman has quit IRC19:53
openstackgerritArtom Lifshitz proposed openstack/nova master: WIP: Include direct-physical in compute manager events check  https://review.opendev.org/66443119:53
artomsean-k-mooney, mriedem, ^^ did a thing. Still lots of cleanup to do, but maybe check the compute manager/libvirt driver parts to see if the general approach is palatable?19:53
*** tbachman has joined #openstack-nova19:54
sean-k-mooneythat likely wont be backportable. due to the chagne in the signiture of finish_revert_migration or at least its more invasive then it needs to be19:59
sean-k-mooneystill reading it19:59
artomfinish_revert_migration was changed with the previous approach as well (was adding vifs_already_plugged)20:00
sean-k-mooneyyes but we can actully make this work without adding any new parmater to finish_revert_migration20:01
sean-k-mooneyif we take the approch i was suggesting. we actully did not need to pass vif_already_plugged20:01
artomWhy is adding a parameter bad though? That's not RPC, don't think it'll affect backportability...20:02
artomIt's compute manager talking to its virt driver, both are updated at the same time20:02
sean-k-mooneyits chaning the virt dirver api right20:02
artomYeah20:02
sean-k-mooneyso it would break out of tree drivers without the try catch20:02
artomWell, yeah20:03
sean-k-mooney* try excpet20:03
artomI don't see a way around passing the virt driver *something*20:04
sean-k-mooneywe have all the info we need in the network_info object since that is a list of vifs20:05
sean-k-mooneyso we can calualte if we need to wait in the driver or manager form that without passing anything20:05
sean-k-mooneywhich is part of the reason i suggested adding the function in the vif model class20:05
*** jaypipes has quit IRC20:06
*** jaypipes has joined #openstack-nova20:06
artomThe problem is that finish_revert_migration isn't always called for revert resize...20:07
artomSo even if network_info has all it needs in terms of event "types"20:07
artomWe still need a way to tell the virt driver when to actually use that information20:07
sean-k-mooneyim not following20:08
artomAll of this stuff, it's only applicable in the revert resize case, right?20:09
sean-k-mooneyand revert migration yes20:09
sean-k-mooney*cold migration20:09
artomIs it? Does the instance remain shutoff on the source with the VIFs still wired while it's cold migrating?20:10
sean-k-mooneyyes20:10
sean-k-mooneyto both questions20:11
artomSo, the only other instance of driver.finish_revert_migration that I've found is https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L100120:11
artomSo maybe you're right, driver.finish_revert_migration is called if and only iff we need to do the compute manager/virt driver events checking thing20:11
sean-k-mooneyyes cold migration uses the resize_migrating task state20:11
sean-k-mooneyright it only used in two case20:12
sean-k-mooneyif we are migrating/resizing instance.task_state == task_states.RESIZE_MIGRATING20:13
artomSo in that case yeah, we can stuff the logic inside the VIF model20:13
sean-k-mooneywhich is that auto rollback if things go wrong20:13
artomKinda weird for something so specific to go in the model, but I guess it makes sense20:13
sean-k-mooneyor if the user revert the migraion/resize form the api after we succeed in the migratio/resize instead of  confiming20:13
sean-k-mooneyartom: well i had planned to stuff the event info form neutron in that data stcutrue if we implement the spec in anycase20:14
sean-k-mooneyartom: we can always add a untility module or make it a free fucntion if you like but i think the encapsulation makes sense20:16
* artom just tried it - yeah, 'nova migrate' will leave the instance shutoff on the source20:16
artomUntil confirmed (or reverted)20:17
sean-k-mooneyyep20:17
sean-k-mooneyand we default to auto confirm disabled20:17
sean-k-mooneyi more or less had this conversation with stephenfin and mriedem a few hours ago :)20:18
artom(Which is weird UX, btw - because you 'nova migrate', but then you 'nova resize-revert')20:18
sean-k-mooneyyep we know :)20:18
artomYeah, didn't think I was teaching anyone anything20:18
*** francoisp has joined #openstack-nova20:19
sean-k-mooneyhehe its just funny to me because you are reiterating what stephenfin said more or less like 6 hours ago20:19
artomBetter late than never, I suppose20:20
sean-k-mooneyartom: http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2019-06-10.log.html#t2019-06-10T14:53:27 :)20:20
artom*snerk* Yeah20:21
sean-k-mooneyso are you open to trying to remove the api change to the driver api and filtering the events as i was suggesting ? it shoudl reduce the size of the patch a resonable amount20:24
artomsean-k-mooney, yeah20:24
artomStill opposed to passing 'revert' to _create_domain_and_network though :)20:25
*** tbachman has quit IRC20:25
artomBut less oot driver pain is indeed better20:25
*** amodi has joined #openstack-nova20:25
* artom h4x20:25
sean-k-mooneywell you might be able to tell form somthing else but why dont you like passing revert to  _create_domain_and_network20:26
sean-k-mooneyi dont think you replied to the commets did you?20:26
* sean-k-mooney goes to look20:26
artomIt's higher up logic that should live higher up20:27
artomI kinda replied20:27
artomSo what I came up with is passing a list of events to wait for20:27
artomI say higher up20:28
sean-k-mooneyoh ok. am i guess you could generate that in the driver20:28
sean-k-mooneyrather then pass it from teh compute manager20:28
sean-k-mooneythat an internal api so it more ok to modify the the driver api as you wont break anything at that point20:29
artomYeah, so really "higher up" means "more specific"20:29
artomIe, finish_revert_migration knows we're doing a revert, _cdan has no idea, nor should it20:30
sean-k-mooneyartom: dansmith raised a vaild point we need to make sure not to change livemigration behavior20:30
sean-k-mooneyartom: oh and i just saw your top level comment regarding revert20:30
*** pcaruana has quit IRC20:31
artomsean-k-mooney, yeah, which is why I straight up added https://review.opendev.org/#/c/644881/24/nova/compute/manager.py@649920:31
artomI can probably just call it revert20:31
artomBecause it also applied for reverting cold migrations20:32
sean-k-mooney ya you could rename the other one and add live20:32
sean-k-mooneyactully no20:32
sean-k-mooneythat is more work20:32
sean-k-mooneyand its unrelated20:32
artomsean-k-mooney, where are you in Ireland again, btw?20:35
sean-k-mooneyShannon20:35
sean-k-mooneyon the west coast more or less20:35
artomhttps://i.imgur.com/lqfeJZk.jpg West Coast!20:37
* artom kinda wants to put the get_revert_events part into the compute manager virtapi20:39
sean-k-mooneyi was debating if it could go into the compute untils module20:39
* artom is still bothered by putting it into the VIF model20:40
sean-k-mooneyso in here somewhere https://github.com/openstack/nova/blob/master/nova/compute/utils.py20:40
sean-k-mooneythen you can use it for the driver or the compute manger20:40
sean-k-mooneyand not put it in the vif if you dont like that20:40
artomIt just feels so alien there20:40
artomIt's business logic, after all, right?20:41
artomReally specific one at that20:41
sean-k-mooneyi was not suggsting puting the event generation in teh VIF by the way20:41
sean-k-mooneyjsut the function that says if it should wait in the manager or driver20:41
artomWell.... "is_manager_vif" or w/e you called it is basically the same logic :)20:41
artomIt's not the generation part that I have issues with, it's that the VIF model suddenly understand the difference between compute manager and virt driver20:42
sean-k-mooneyyes but if we get teh info form neutron in the future i can simply change the impliation of that method20:42
artomAnyways, we're ratholing :)20:42
sean-k-mooneyand only for the revert resize case too20:43
sean-k-mooneyso nova.compute.utils20:43
sean-k-mooneyi think it qualifies as a """Compute-related Utilities and helpers."""20:43
*** eharney has joined #openstack-nova20:43
sean-k-mooneythat has things like is_volume_backed_instance20:44
artomFair enough20:44
*** spatel has quit IRC20:45
sean-k-mooneyyou could put it in the virtapi i guess too20:45
sean-k-mooneyif you did that then the manager would call the driver to get teh events20:46
artomEh?20:46
artomHow so?20:46
sean-k-mooneywell were you thinking of making it a module level function or adding it to the driver interface20:46
*** ociuhandu has quit IRC20:47
sean-k-mooneyvirtapi is actuly just event stuff...20:47
sean-k-mooneyhttps://github.com/openstack/nova/blob/master/nova/virt/virtapi.py20:47
sean-k-mooneyi guess that would be fine too.20:48
artomThis *is* event stuff :)20:49
sean-k-mooneyya i would be fine with adding it there20:49
sean-k-mooneyi assummed wrongly that the base compute driver api would be defiended there but that is in driver.py20:50
efriedaspiers: Reviewed.20:51
aspiersthanks!20:51
sean-k-mooneydamn no wonder the libvirt virt driver is 5000 lines lon the base class is almost 200020:51
*** tbachman has joined #openstack-nova20:55
*** mvkr has joined #openstack-nova20:57
*** tbachman has quit IRC20:57
*** tbachman has joined #openstack-nova21:07
openstackgerritArtom Lifshitz proposed openstack/nova master: WIP: Revert resize: wait for events according to hybrid plug  https://review.opendev.org/64488121:12
openstackgerritArtom Lifshitz proposed openstack/nova master: WIP: Include direct-physical in compute manager events check  https://review.opendev.org/66443121:12
artomsean-k-mooney, mriedem, ^^21:13
artomAnd I think I need to head home at this point.21:13
artomOr potentially to daycare, if wife doesn't make it there in time :/21:13
sean-k-mooneyack21:14
sean-k-mooneyat first glance it certenly shorter21:14
sean-k-mooneyif it fixes the issue even better ill take a look21:14
artomWell tests are missing21:14
sean-k-mooneydetails :)21:15
mriedemprobably want to revive sean-k-mooney's dnm test patch to recreate the issue on top of this again if you changed the fix21:17
sean-k-mooneysure i can restroe it and rebase21:17
sean-k-mooneymriedem: did your change to tempest merge or shoudl i add a depense on to remvoe teh skip21:18
*** artom has quit IRC21:19
mriedemit's approved21:20
mriedemsorry, +221:20
mriedembut i'm not sure that matters for what you were testing,21:20
mriedemyou could merge artom's patch to run the revert resize tests in the nova-live-migration job and add your ovs_hybrid_plug config21:20
sean-k-mooneywell artom abandoned his chagne that ran the revert tests21:20
mriedemand you abandoned yours - just copy his stuff into your DNM change right?21:21
sean-k-mooneyya i could do that21:21
*** priteau has quit IRC21:22
*** itlinux has quit IRC21:23
*** whoami-rajat has quit IRC21:24
openstackgerritsean mooney proposed openstack/nova master: [DNM] testing bug/1813789 revert resize events  https://review.opendev.org/66444221:29
sean-k-mooneyinteresting... gerrit auto added artom to the comitt i jsut pushed and also aprently he is the author of ^21:32
sean-k-mooneyi didnt think i was ment to be allowed to that but whatever21:33
*** tbachman_ has joined #openstack-nova21:35
*** tbachman has quit IRC21:35
*** tbachman_ is now known as tbachman21:35
openstackgerritMatt Riedemann proposed openstack/nova master: Add Migration.cross_cell_move and get_by_uuid  https://review.opendev.org/61401221:43
openstackgerritMatt Riedemann proposed openstack/nova master: Add InstanceAction/Event create() method  https://review.opendev.org/61403621:43
openstackgerritMatt Riedemann proposed openstack/nova master: Add Instance.hidden field  https://review.opendev.org/63112321:43
openstackgerritMatt Riedemann proposed openstack/nova master: Add TargetDBSetupTask  https://review.opendev.org/62789221:44
openstackgerritMatt Riedemann proposed openstack/nova master: Add CrossCellMigrationTask  https://review.opendev.org/63158121:44
openstackgerritMatt Riedemann proposed openstack/nova master: Execute TargetDBSetupTask  https://review.opendev.org/63385321:44
openstackgerritMatt Riedemann proposed openstack/nova master: Add prep_snapshot_based_resize_at_dest compute method  https://review.opendev.org/63329321:44
openstackgerritMatt Riedemann proposed openstack/nova master: Add PrepResizeAtDestTask  https://review.opendev.org/62789021:44
openstackgerritMatt Riedemann proposed openstack/nova master: Add prep_snapshot_based_resize_at_source compute method  https://review.opendev.org/63483221:44
openstackgerritMatt Riedemann proposed openstack/nova master: Add nova.compute.utils.delete_image  https://review.opendev.org/63760521:44
openstackgerritMatt Riedemann proposed openstack/nova master: Add PrepResizeAtSourceTask  https://review.opendev.org/62789121:44
openstackgerritMatt Riedemann proposed openstack/nova master: Refactor ComputeManager.remove_volume_connection  https://review.opendev.org/64218321:44
openstackgerritMatt Riedemann proposed openstack/nova master: Add power_on kwarg to ComputeDriver.spawn() method  https://review.opendev.org/64259021:44
openstackgerritMatt Riedemann proposed openstack/nova master: Add finish_snapshot_based_resize_at_dest compute method  https://review.opendev.org/63508021:44
openstackgerritMatt Riedemann proposed openstack/nova master: Add FinishResizeAtDestTask  https://review.opendev.org/63564621:44
openstackgerritMatt Riedemann proposed openstack/nova master: Add Destination.allow_cross_cell_move field  https://review.opendev.org/61403521:44
openstackgerritMatt Riedemann proposed openstack/nova master: Execute CrossCellMigrationTask from MigrationTask  https://review.opendev.org/63566821:44
openstackgerritMatt Riedemann proposed openstack/nova master: Plumb allow_cross_cell_resize into compute API resize()  https://review.opendev.org/63568421:44
openstackgerritMatt Riedemann proposed openstack/nova master: Support cross-cell moves in external_instance_event  https://review.opendev.org/65847821:44
openstackgerritMatt Riedemann proposed openstack/nova master: Add cross-cell resize policy rule and enable in API  https://review.opendev.org/63826921:44
openstackgerritMatt Riedemann proposed openstack/nova master: WIP: Enable cross-cell resize in the nova-multi-cell job  https://review.opendev.org/65665621:44
*** panda has quit IRC21:58
*** panda has joined #openstack-nova22:01
openstackgerritEric Fried proposed openstack/nova master: fup: Remove unused mock in libvirt functional base  https://review.opendev.org/66444922:01
*** mriedem has quit IRC22:08
*** mlavalle has quit IRC22:12
*** spatel has joined #openstack-nova22:12
*** spatel has quit IRC22:17
*** artom has joined #openstack-nova22:33
*** efried has quit IRC22:39
*** hongbin has quit IRC22:40
*** efried has joined #openstack-nova22:41
*** markvoelker has joined #openstack-nova22:44
redkriegI'm trying to get my nova instances to not use a backing file so I can remove images from _base.  for some reason even when I set use_cow_images=False I still have _base backed instances.  Is there some new config for this feature?  I'm using info from here: https://www.pixelbeat.org/docs/openstack_libvirt_images/22:47
*** tkajinam has joined #openstack-nova22:53
*** tkajinam has quit IRC22:53
*** tkajinam has joined #openstack-nova22:55
redkriegnevermind, I had images_type under [libvirt] set to qcow2 instead of default22:56
*** rcernin has joined #openstack-nova23:04
*** rcernin_ has joined #openstack-nova23:05
*** rcernin has quit IRC23:09
*** slaweq has joined #openstack-nova23:10
*** luksky has quit IRC23:13
*** markvoelker has quit IRC23:18
*** slaweq has quit IRC23:19
*** sorrison has quit IRC23:34
*** takashin has joined #openstack-nova23:37
*** factor has quit IRC23:42
*** icarusfactor has joined #openstack-nova23:42
*** threestrands has joined #openstack-nova23:44
*** factor__ has joined #openstack-nova23:49
*** factor__ has quit IRC23:51
*** icarusfactor has quit IRC23:52
*** factor has joined #openstack-nova23:53

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