| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-04-06 | |||
| 13:57:25 | mriedem | johnthetubaguy: added what for hyperv? | |
| 13:57:26 | mriedem | fake_scheduler? | |
| 13:57:33 | johnthetubaguy | x.509 cert generation | |
| 13:57:39 | johnthetubaguy | to replace the ssh keypair type | |
| 13:57:41 | bauzas | dansmith: anyway, I tried to think about reschedules | |
| 13:57:48 | bauzas | dansmith: I still think we need them | |
| 13:57:57 | bauzas | because of X or Y | |
| 13:58:37 | dansmith | X or Y? | |
| 13:58:52 | mriedem | nova meeting in 2 minutes | |
| 14:00:23 | openstackgerrit | Roman Podoliaka proposed openstack/osc-placement master: WIP: implement API version 1.0 https://review.openstack.org/451877 | |
| 14:02:14 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Remove a fallacy in scheduler.driver config option help text https://review.openstack.org/454196 | |
| 14:04:17 | claudiub | mriedem: johnthetubaguy you mean the x509 certificates? | |
| 14:04:29 | johnthetubaguy | yeah, for windows auth | |
| 14:04:30 | claudiub | those would the windows equivalent of ssh keys | |
| 14:04:43 | claudiub | so, not hyper-v specific, windows guests specific | |
| 14:05:19 | dane-fichter | johnthetubaguy: So what I'm hearing is that generate_winrm_x509_cert() is still needed? | |
| 14:05:30 | johnthetubaguy | dane-fichter: I think so, yeah | |
| 14:05:38 | johnthetubaguy | dane-fichter: even after we kill nova-cert | |
| 14:05:51 | openstackgerrit | Dan Smith proposed openstack/nova master: Add functional test for two-cell scheduler behaviors https://review.openstack.org/452006 | |
| 14:05:54 | dane-fichter | johnthetubaguy: ok. good to know. | |
| 14:06:29 | johnthetubaguy | dane-fichter: although I am willing to believe its something we should deprecate in the API, us generating certs is probably the wrong thing to do for winRM, but I am not sure | |
| 14:06:47 | johnthetubaguy | dane-fichter: needs a look, I guess | |
| 14:08:04 | dane-fichter | johnthetubaguy: I'll take a look at it. | |
| 14:16:11 | ildikov | johnthetubaguy: mriedem: lyarwood: hi, a quick reminder that we plan to switch to 1600 UTC with the Cinder-Nova meeting today | |
| 14:17:03 | johnthetubaguy | ah, I forgot about tht | |
| 14:17:44 | ildikov | johnthetubaguy: sorry, I should've sent out a reminder mail earlier, I only got to propose a patch to change the slot officially, it's not merged yet | |
| 14:17:53 | ildikov | johnthetubaguy: can you make it to the earlier slot? | |
| 14:18:04 | johnthetubaguy | ildikov: that should be OK | |
| 14:18:13 | ildikov | johnthetubaguy: cool, tnx | |
| 14:18:48 | openstackgerrit | Scott Moser proposed openstack/nova master: Limit exposure of network device types to the guest. https://review.openstack.org/400883 | |
| 14:27:45 | openstackgerrit | Scott Moser proposed openstack/nova master: Limit exposure of network device types to the guest. https://review.openstack.org/400883 | |
| 14:38:13 | mriedem | sfinucan: artom: https://github.com/openstack/nova/blob/master/nova/tests/functional/test_metadata.py is what i was thinking of | |
| 14:38:46 | mriedem | we'd have to fix mikal's sins here for network data https://github.com/openstack/nova/blob/master/nova/tests/functional/test_metadata.py#L64 | |
| 14:39:02 | mriedem | since ^ is all using nova-network right now | |
| 14:44:07 | bauzas | mriedem: wait, we unset instance.host when we offload the instance from the compute ? | |
| 14:44:18 | bauzas | (after shelving) | |
| 14:45:01 | bauzas | I know it requires a reschedule, but I was thinking we were keeping the reference before the unshelve and that were just overriding the host value | |
| 14:45:13 | dansmith | bauzas: no, once offloaded, it loses host, AFAIK | |
| 14:45:23 | bauzas | dansmith: so in the compute? | |
| 14:45:28 | bauzas | because AFAIK, you shelve | |
| 14:45:40 | bauzas | and then, a couple of mins after (config) then it's offloaded | |
| 14:46:02 | bauzas | AFAIK, it's a periodic task running on the compute which offloads the instance off | |
| 14:46:06 | dansmith | right | |
| 14:47:03 | bauzas | dansmith: okay, for my knowledge, reading again the code | |
| 14:51:18 | mriedem | we immediately offload by default | |
| 14:51:20 | mriedem | bauzas: ^ | |
| 14:51:29 | mriedem | it's based on config | |
| 14:51:36 | johnthetubaguy | mriedem: +1 | |
| 14:51:37 | mriedem | the time defaults to 0 | |
| 14:51:55 | mriedem | and then yes the instance does not have a host or node set on it | |
| 14:52:50 | bauzas | mriedem: right, because the opt value is 0 | |
| 14:53:00 | bauzas | mriedem: that's what I meant sorry | |
| 14:53:02 | bauzas | it's time-based | |
| 14:53:06 | bauzas | if 0, do that now | |
| 14:58:29 | mriedem | heads up, apparently pypi mirror issues | |
| 14:58:32 | mriedem | so jobs are failing | |
| 15:01:34 | dansmith | yeah | |
| 15:01:35 | dansmith | was just seeing that | |
| 15:02:00 | openstackgerrit | Vladik Romanovsky proposed openstack/nova master: Support HTTP CONNECT in websocket proxy https://review.openstack.org/454226 | |
| 15:26:30 | bauzas | mriedem: dansmith: I'm puzzled, can't find where instance.host is unset in the compute manager method for shelve offloading | |
| 15:27:11 | mriedem | bauzas: in the RT | |
| 15:27:18 | mriedem | super tight coupling | |
| 15:27:22 | mriedem | equals super fun | |
| 15:27:34 | bauzas | mriedem: orly? man | |
| 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 | |