Earlier  
Posted Nick Remark
#openstack-nova - 2017-04-06
15:27:45 dansmith here? https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L4400-L4400
15:27:57 mriedem actually yeah
15:27:58 mriedem not RT
15:28:02 mriedem i was thinking of ALLOW_RESOURCE_REMOVAL in rt
15:28:10 dansmith took me like eight whole seconds :)
15:28:23 mriedem https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L4396 is what i was thinking of
15:28:34 mriedem which uses https://github.com/openstack/nova/blob/master/nova/compute/resource_tracker.py#L939
15:28:43 mriedem and https://github.com/openstack/nova/blob/master/nova/compute/vm_states.py#L78
15:28:49 mriedem alaski had to draw that picture for me once
15:28:54 mriedem i'll always be indebted
15:31:29 bauzas mriedem: I was surprised when you said that hence my "orly"
15:31:47 bauzas mriedem: because I don't remember where in RT we do set instance.host
15:32:01 bauzas we play with compute tracking
15:32:17 bauzas so it would defend the purpose of the RT if we would play with the instance fields in there
15:32:28 bauzas dansmith: thanks, missed that - so I'm blind
15:32:39 dansmith :)
15:33:39 mriedem i would not be surprised at all of RT or Claims messed with instance fields
15:33:44 mriedem s/of/if/
15:34:31 bauzas mriedem: they look them up
15:34:39 bauzas mriedem: but they don't touch them
15:34:53 bauzas or I would seriously -2 any change for that
15:35:04 bauzas resource *tracking*
15:35:12 bauzas not resource *setting* :p
15:36:30 mriedem you might -2 that but that doesn't mean someone else won't +W before you see it
15:38:54 cdent fa
15:38:59 cdent ww
15:41:43 bauzas mriedem: question about https://review.openstack.org/#/c/453859/1/nova/compute/api.py
15:41:55 mriedem shoot
15:42:09 bauzas mriedem: if we nullify instance.host when shelve_offload, why do we need to verify the instance state too ?
15:42:30 mriedem bauzas: read the commit message?
15:43:19 bauzas mriedem: ok, this time, you can *really* blame me in public
15:43:19 mriedem basically that whole block is about cases where the instance isn't scheduled to a cell
15:43:23 mriedem or that was the original assumption
15:43:34 mriedem that assumption breaks down when instance.host is None and vm_state is shelved offloaded
15:43:39 mriedem b/c that means the instance did get scheduled to a cell
15:43:45 mriedem and we need to do the old style local delete flow below
15:43:58 mriedem all explained in the commit message in exquisite detail
15:45:14 bauzas mriedem: I see L1974 so I understand now
15:45:43 mriedem fwiw i'm going to be trying to unwind this mess once this fix is in
15:46:37 mriedem dansmith: i eagerly await your updates to https://review.openstack.org/#/c/442162/
15:46:58 mriedem b/c then we can get the bottom 5 changes in
15:47:15 dansmith mriedem: yep in my queue
15:47:50 mriedem i drank one too many cups of coffee to counteract my nyquil hangover and now i'm all amped up
16:39:44 mriedem ildikov: just an issue with the wording in the reno https://review.openstack.org/#/c/444253/
16:40:24 openstackgerrit Dan Smith proposed openstack/nova master: Teach HostAPI about cells https://review.openstack.org/442162
16:40:24 openstackgerrit Dan Smith proposed openstack/nova master: Sort CellMappingList.get_all() for safety https://review.openstack.org/443174
16:40:25 openstackgerrit Dan Smith proposed openstack/nova master: Add get_by_instance_uuids() to InstanceMappingList https://review.openstack.org/443292
16:40:26 openstackgerrit Dan Smith proposed openstack/nova master: Clean up ClientRouter debt https://review.openstack.org/444487
16:40:26 mriedem dansmith: are you still using this? https://review.openstack.org/#/c/421399/
16:40:27 openstackgerrit Dan Smith proposed openstack/nova master: Make server_groups determine deleted-ness from InstanceMappingList https://review.openstack.org/443293
16:40:28 dansmith mriedem: have you reviewed that yet?
16:40:28 openstackgerrit Dan Smith proposed openstack/nova master: Remove Mitaka-era service version check https://review.openstack.org/442861
16:40:30 openstackgerrit Dan Smith proposed openstack/nova master: Add workaround to disable group policy check upcall https://review.openstack.org/442736
16:40:39 mriedem dansmith: reviewed what yet?
16:40:44 dansmith mriedem: the thing I just pushed up
16:40:47 dansmith mriedem: what about now?
16:40:48 dansmith mriedem: now?
16:40:51 mriedem oh
16:40:51 mriedem i see
16:41:05 mriedem let me get out my red pen
16:41:13 dansmith mriedem: I haven't gotten to the actual subnode part of my devstack patch to know if I need that again or not
16:41:16 dansmith mriedem: I think I will
16:41:35 dansmith mriedem: if it's bothering you I can resubmit it under my name so you can abandon
16:41:36 dansmith I've long since given up trying to keep my dashboard clean
16:41:39 ildikov mriedem: cool, I'll fix it now, tnx
16:44:27 mriedem dansmith: it's fine, i just clean up every few weeks
16:45:35 mdnadeem ildikov, dansmith , mriedem , Hello guys, i have a query
16:45:42 mdnadeem https://github.com/openstack/nova/blob/stable/newton/nova/scheduler/filters/aggregate_image_properties_isolation.py#L42
16:46:07 mdnadeem ^^ It returns only core image property
16:46:16 mriedem yes
16:46:21 mriedem your out of tree image properties won't work
16:46:40 mdnadeem I have set some custom property to my image , however i cant get it there
16:46:46 mriedem because of https://github.com/openstack/nova/blob/stable/newton/nova/objects/image_meta.py#L213
16:47:13 mdnadeem mriedem, any way to use custom image property ?
16:47:14 mriedem https://github.com/openstack/nova/blob/stable/newton/nova/objects/image_meta.py#L478
16:47:20 mriedem mdnadeem: upstream it
16:47:27 mriedem or hack that object and live with the version changes
16:48:52 mdnadeem mriedem, is this a bug ?
16:49:01 mriedem mdnadeem: no, it's by design
16:49:22 mriedem a wild west of custom image properties is a barrier to interoperability
16:49:32 mriedem flavor extra specs is still a wild west if that helps
16:49:57 mdnadeem mriedem, I have a requirement to use custom image property, should i propose a fix upstream for the same?
16:50:16 mriedem mdnadeem: if you have an image property that makes sense to upstream then i encourage you to do so
16:50:29 mriedem because chances are someone else has a similar use case
16:50:42 mdnadeem mriedem, ok, Thanks a lot :)
16:50:45 mriedem yw
16:50:57 mdnadeem mriedem++
16:52:39 mriedem dansmith: i'm brain isn't working on why api/scheduler/conductor show up in cell0 https://review.openstack.org/#/c/442162/19/nova/compute/api.py@4433 - i thought those would only show up if we start the services?
16:52:47 mriedem s/i'm/my
16:54:49 mriedem https://github.com/openstack/nova/blob/8d9bf947a4c8654a30e016a5d95d9bec55447506/nova/service.py#L154
16:56:26 openstackgerrit Ildiko Vancsa proposed openstack/nova master: Deprecate the Cinder API v2 support https://review.openstack.org/444253
17:00:47 dansmith mriedem: they're going to show up in whatever db is configured in their config file
17:01:06 dansmith mriedem: which in my devstack patch, and in real deploys after we're past this hump, will be cell0 I expect
17:01:07 mriedem right, which means you f'ed up and started services with a nova.conf pointing at cell0 right?
17:01:33 mriedem hmm
17:01:35 dansmith I mean, you could just choose a random cell to have them show up in, but I dunno why you would
17:01:50 mriedem yeah i guess that's a good point
17:01:52 mriedem they aren't in the api db
17:01:58 mriedem they wouldn't be in a random cell db
17:02:00 dansmith right

Earlier   Later