| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-09-17 | |||
| 12:23:03 | Roamer` | hi, possibly stupid question incoming :) If a company has two different physical datacenters, and an OpenStack setup in each of them, how would it be best to make it possible to (cold-)migrate instances (with attached volumes) between them? Is there a way to migrate an instance between two regions of the same cluster? The two options I've found so far is "openstack server image create" (which | |
| 12:23:09 | Roamer` | creates a zero-byte image for a volume-backed instance, though maybe I've configured something wrong) and cinder backup/restore; are there other options? | |
| 12:45:51 | bauzas | gibi: thanks for the updates | |
| 12:46:17 | gibi | bauzas: you are welcome | |
| 12:47:05 | gibi | bauzas: I think the series works as my bandwidth functional tests worked on top. But I wouldn't be surprised if migrate or evacuate would eventually be found broken | |
| 12:47:26 | bauzas | gibi: for migrate, we at least need to pass allocations | |
| 12:47:34 | bauzas | I have an uploaded change for it | |
| 12:47:42 | bauzas | to the drivers, I meant | |
| 12:47:54 | gibi | bauzas: for VGPU I guess | |
| 12:48:10 | bauzas | alas yes | |
| 12:49:00 | gibi | bauzas: yeah, that make sense. I also have to work on the bandwidth patch to see migrate works or not as-is. So fare I only have boot and delete tests there | |
| 12:50:15 | bauzas | yup, I just wanted to make sure you knew it | |
| 12:52:45 | gibi | VGPU and bandwidth differs in a sense that the physical use of the resource for VGPU happens in the virt driver (i.e. generating the proper xml) while for bandwidth it happens in neutron and os-vif. | |
| 12:53:24 | gibi | so at the moment I assumes that for bandwidth we don't need the allocations in the virt driver. But I very well be wrong in the SRIOV case due to the pci handling there | |
| 12:59:24 | bauzas | gibi: ah good point | |
| 13:29:54 | mriedem | got a clean run on the evacuate integration test https://review.openstack.org/#/c/602174/ | |
| 13:30:03 | mriedem | with no mdbooth around to celebrate | |
| 13:33:36 | mriedem | we have something in a runway for stein now https://review.openstack.org/#/c/599276/ | |
| 13:35:56 | gibi | mriedem: I've just added the consumer generation support to the runway queue | |
| 13:36:08 | mriedem | is that a blueprint? | |
| 13:36:33 | mriedem | https://blueprints.launchpad.net/nova/+spec/use-nested-allocation-candidates isn't approved | |
| 13:36:49 | gibi | it is part of bp/use-nested-allocation-candidates | |
| 13:37:00 | bauzas | do we started runways ? | |
| 13:37:51 | gibi | mriedem: true, then I remove the patches from the queue and bring up the bp on the Thursday meeting for approval | |
| 13:37:59 | bauzas | mriedem: FWIW https://review.openstack.org/#/c/527728/22/nova/tests/functional/test_servers.py should cover the boot case | |
| 13:42:52 | kashyap | Dear folks, I can't tell _why_ the 'neutron-grenade' job is failing here: https://review.openstack.org/#/c/602592/ | |
| 13:43:18 | kashyap | I'm looking at the "ara-report", but I can't find a log file. | |
| 13:45:32 | bauzas | kashyap: http://logs.openstack.org/92/602592/3/check/neutron-grenade/bfeb3e6/job-output.txt.gz | |
| 13:45:54 | kashyap | bauzas: Ah, let me look | |
| 13:46:10 | bauzas | mmm, actually | |
| 13:46:24 | mriedem | http://logs.openstack.org/92/602592/3/check/neutron-grenade/bfeb3e6/logs/devstack-gate-setup-workspace-old.txt | |
| 13:47:30 | mriedem | i've seen that in a couple of other jobs but don't know what's causing it | |
| 13:47:59 | kashyap | http://logs.openstack.org/92/602592/3/check/neutron-grenade/bfeb3e6/job-output.txt.gz#_2018-09-17_10_12_38_647361 | |
| 13:48:03 | bauzas | http://logs.openstack.org/92/602592/3/check/neutron-grenade/bfeb3e6/job-output.txt.gz#_2018-09-17_11_27_33_877513 | |
| 13:48:10 | kashyap | 2018-09-17 10:12:38.647361 | primary | smoke installed: ----------------------------------------,Error when trying to get requirement for VCS system Command "git config --get-regexp remote\..*\.url" failed with error code 1 in /opt/stack/new/tempest, falling back to uneditable format,Could not determine repository location of /opt/stack | |
| 13:48:26 | mriedem | that's common | |
| 13:48:32 | mriedem | the failure is in http://logs.openstack.org/92/602592/3/check/neutron-grenade/bfeb3e6/logs/devstack-gate-setup-workspace-old.txt | |
| 13:48:53 | mriedem | http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22error%3A%20The%20following%20untracked%20working%20tree%20files%20would%20be%20overwritten%20by%20checkout%3A%5C%22%20AND%20tags%3A%5C%22console%5C%22&from=7d | |
| 13:49:35 | kashyap | Ah, it's the untracked files | |
| 13:50:06 | bauzas | http://logs.openstack.org/92/602592/3/check/neutron-grenade/bfeb3e6/logs/devstack-gate-setup-workspace-old.txt | |
| 13:50:13 | bauzas | dammit, I'm burned | |
| 13:50:32 | kashyap | bauzas: Thought you'll be refreshed after the PTG? | |
| 13:50:41 | kashyap | Ah, _that_ kind of a burn | |
| 13:50:42 | bauzas | I am | |
| 13:50:53 | bauzas | nah, burned because I'm too slow | |
| 13:53:47 | mriedem | someone want to backport this to stable/rocky? https://review.openstack.org/#/c/546920/ | |
| 13:54:03 | mriedem | someone not on the stable core team... | |
| 13:59:32 | bauzas | stephenfin: ^ ? | |
| 14:00:10 | gibi | mriedem: elod is still in Denver but he is back on Wednesday so if nobody take this backport then I can encourage them to take it | |
| 14:00:30 | stephenfin | bauzas, mriedem: Sure | |
| 14:00:53 | bauzas | do we have a scheduler meeting ? | |
| 14:01:28 | mriedem | yes | |
| 14:02:33 | openstackgerrit | Stephen Finucane proposed openstack/nova stable/rocky: Fix soft deleting vm fails after "nova resize" vm https://review.openstack.org/603140 | |
| 14:02:48 | stephenfin | mriedem, bauzas: as requested ^ | |
| 14:03:22 | bauzas | ta | |
| 14:09:35 | mriedem | dansmith: if you're ok with what i've proposed for updates in https://review.openstack.org/#/c/579520/ (the volume type spec) then i'll just make those updates myself | |
| 14:09:51 | dansmith | looking | |
| 14:11:40 | dansmith | mriedem: the latest two small things? sure, but I should re-review the whole thing | |
| 14:11:55 | dansmith | if you do the update I'll do that once the caffeine starts hitting my bloodstream | |
| 14:12:23 | mriedem | ok, i might not get to that until after the placement meeting | |
| 14:26:57 | openstackgerrit | Vlad Gusev proposed openstack/nova stable/pike: [placement] Retry allocation writes server side https://review.openstack.org/590745 | |
| 14:35:12 | stephenfin | bauzas: Does this need a reno, actually? https://review.openstack.org/#/c/603140/ | |
| 14:42:50 | openstackgerrit | Matt Riedemann proposed openstack/nova-specs master: Add support specify volume type when boot instance https://review.openstack.org/579520 | |
| 14:43:03 | mriedem | dansmith: fleshed out the proposed change section and also the specific test scenarios i'd want to see at a minimum ^ | |
| 14:43:19 | dansmith | ack | |
| 14:48:31 | mriedem | bauzas: as far as i can tell, the only change i need to make in the libvirt vgpu reshaper patch is the naming convention we discussed at the ptg correct? https://review.openstack.org/#/c/599208/ | |
| 14:48:50 | mriedem | <HYPERVISOR_HOSTNAME>_VGPU_<TYPE_NAME> | |
| 14:50:19 | dansmith | mriedem: yauntmeta fix up my grammar nits, or just stack something on top? | |
| 14:51:19 | mriedem | i'll fix them quick | |
| 14:52:54 | dansmith | aight | |
| 14:58:07 | openstackgerrit | Matt Riedemann proposed openstack/nova-specs master: Add support specify volume type when boot instance https://review.openstack.org/579520 | |
| 14:58:10 | mriedem | dansmith: done | |
| 15:00:15 | dansmith | mriedem: also done | |
| 15:01:30 | dansmith | mriedem: heading to the twitters | |
| 15:02:21 | dansmith | https://twitter.com/get_offmylawn/status/1041703857460412419 | |
| 15:02:39 | mriedem | heh | |
| 15:02:41 | mriedem | oh chet | |
| 15:10:22 | bauzas | mriedem: sorry missed your ping | |
| 15:10:31 | bauzas | mriedem: yup, I guess, lemme check notes on this | |
| 15:11:07 | bauzas | mriedem: there was an upgrade concern, but I feel this should only be written for the multiple types support | |
| 15:11:15 | bauzas | I feel => I'm sure | |
| 15:11:56 | mriedem | yes multiple gpu types can't be supported until the reshape is done | |
| 15:12:10 | bauzas | mriedem: I reproposed the spec FWIW | |
| 15:12:28 | bauzas | mriedem: https://review.openstack.org/#/c/602474/ | |
| 15:13:06 | bauzas | jaypipes: I know you had concerns on https://review.openstack.org/#/c/602474/ but you eventually got a +2 | |
| 15:13:31 | bauzas | jaypipes: my take on this is that I'm fine if someone writes something using YAML | |
| 15:13:43 | bauzas | jaypipes: I'll then just use it for multiple VGPU types | |
| 15:13:56 | bauzas | (I mean, speaking of the inventory) | |
| 15:14:38 | bauzas | if by Stein, nobody proposes it, then I could consider proposing myself for Train | |
| 15:14:54 | mriedem | resource provider name looks like it's just a string in the api schema, | |
| 15:14:55 | bauzas | for the YAML inventory recording | |
| 15:15:02 | mriedem | wonder if we should replace whitespaces with underscores just to be safe | |
| 15:15:18 | mriedem | or remove whitespaces | |
| 15:15:23 | bauzas | mriedem: I think we agreed on underscores, nope ? | |
| 15:15:36 | mriedem | the etherpad says <HYPERVISOR_HOSTNAME>_VGPU_<TYPE_NAME> | |
| 15:15:43 | mriedem | the conf docs show: | |
| 15:15:44 | mriedem | <HYPERVISOR_HOSTNAME>_VGPU_<TYPE_NAME> | |
| 15:15:46 | mriedem | oops | |
| 15:15:50 | mriedem | enabled_vgpu_types = GRID K100,Intel GVT-g,MxGPU.2,nvidia-11 | |
| 15:16:02 | bauzas | hah, that | |