| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-09-30 | |||
| 18:21:28 | mriedem | gmann_afk: ok. there are samples for 2.69 which use a down cell fixture so maybe something is just missing from that, idk. | |
| 18:56:41 | mriedem | dansmith: maybe we should finally fix this :) https://bugs.launchpad.net/nova/+bug/1781286 | |
| 18:56:41 | openstack | Launchpad bug 1781286 in OpenStack Compute (nova) "CantStartEngineError in cell conductor during reschedule - get_host_availability_zone up-call" [Medium,Triaged] | |
| 18:57:03 | mriedem | i think it's just a matter of shoving the AZ into the Selection object that we pass around in conductor | |
| 18:58:05 | mriedem | tricky thing is functional testing since we don't have a great way to poison conductor on a reschedule to not hit the API DB | |
| 18:58:39 | dansmith | ack | |
| 18:59:01 | dansmith | mriedem: in your reply you said cern is running without a superconductor.. you just mean their cell conductors have api creds right? | |
| 18:59:13 | mriedem | yeah | |
| 18:59:16 | mriedem | but, | |
| 18:59:28 | mriedem | i don't think they make a distinction between a top and cell level conductor | |
| 18:59:30 | dansmith | because unless I'm missing something, you can't not have superconductors, as you need something listening on the conductor topic that isn't going to be confused for cell traffic | |
| 19:00:18 | dansmith | I guess you could have your apis set to penalize one cell's conductors to do the super work, if that made sense in your topology (i.e. one big cell and a bunch of smaller ones or something) | |
| 19:00:19 | mriedem | hmm, i just assumed they were doing whatever devstack does for singleconductor | |
| 19:00:25 | mriedem | which still has cell0 and cell1 | |
| 19:00:35 | mriedem | right, that's what i'm assuming cern does | |
| 19:00:43 | dansmith | well, if you do, then cell1 ends up doing all the work for cell2 for example | |
| 19:00:45 | mriedem | or just a handful of big conductor | |
| 19:00:57 | mriedem | we could ask them but no one in channel | |
| 19:01:21 | dansmith | for a deployment tool, they'd have to have some way of letting you pick which cell should be burdened with the extra work | |
| 19:01:25 | dansmith | which seems less than ideal to me | |
| 19:03:15 | mriedem | as for the console proxy auth stuff, | |
| 19:03:15 | mriedem | https://specs.openstack.org/openstack/nova-specs/specs/rocky/implemented/convert-consoles-to-objects.html | |
| 19:03:25 | mriedem | "instead we will resolve the cell database issue by running console proxies per cell instead of global to a deployment, such that the cell database is local to the console proxy" | |
| 19:03:30 | mriedem | i couldn't find that in our docs | |
| 19:03:35 | mriedem | which seems...bad | |
| 19:03:46 | mriedem | like it should be in https://docs.openstack.org/nova/latest/user/cellsv2-layout.html | |
| 19:03:47 | mriedem | melwitt: ^? | |
| 19:03:55 | mriedem | did the console proxy per cell thing get into the docs? | |
| 19:04:19 | dansmith | yeah, I couldn't either, which is why I punted to her | |
| 19:04:39 | mriedem | nothing here either https://docs.openstack.org/nova/latest/admin/remote-console-access.html | |
| 19:11:25 | mriedem | mgoddard: when you say kolla-ansible is adding support for cells v2, you mean multiple cells specifically right? because cells v2 (cell0, cell1, mappings, etc) has been required since ocata | |
| 19:12:16 | dansmith | mriedem: I think he said specifically adding a cell to an existing deployment | |
| 19:13:26 | mriedem | ah yeah at the end, "I'm trying to design it such that it's possible to deploy a new cell in an existing environment" | |
| 19:13:37 | dansmith | aye | |
| 19:18:38 | mriedem | here is a docs bug for the console proxy per cell thing anyway https://bugs.launchpad.net/nova/+bug/1846045 | |
| 19:18:38 | openstack | Launchpad bug 1846045 in OpenStack Compute (nova) "Docs don't mention running console proxies per cell" [Undecided,New] | |
| 19:38:09 | openstackgerrit | Eric Fried proposed openstack/nova master: Allow versioned discovery unauthenticated https://review.opendev.org/685181 | |
| 20:14:25 | openstackgerrit | Eric Fried proposed openstack/nova master: DNM: Alt: Extract some helper functions from DriverVolumeBlockDevice https://review.opendev.org/685782 | |
| 21:03:55 | openstackgerrit | Merged openstack/nova master: make virtual pmem feature compatible with python3 https://review.opendev.org/685593 | |
| 21:04:28 | efried | dansmith: ^ | |
| 21:39:29 | markguz_ | Hi, Anyone know of way to group pci passthrough cards together based on a label or tagging? | |
| 21:40:08 | markguz_ | for example. I have a compute node with 4 Identical Fiber Channel cards. 2 are connected to SAN 1 and 2 are connected to SAN 2. | |
| 21:40:44 | markguz_ | i wanted to be able to group the cards based on what they were connected to, but so far I have not found a way of doing that | |
| 21:40:50 | markguz_ | am i out of luck? | |
| 21:52:45 | efried | markguz_: I defer to sean-k-mooney for all things pci alias, but yeah, I don't think you can e.g. have each of two aliases grouping together the cards on the same SAN. | |
| 21:55:10 | markguz_ | efried: Yeah I thought maybe I could make an alias for a pci slot, but alias doesn't support it | |
| 21:55:37 | efried | nope, only whitelist has wildcarding I think | |
| 21:56:01 | efried | once we have placement tracking of devices, your SAN is a trait... | |
| 21:56:46 | markguz_ | efried: and I suppose there's anyway to reference the whitelist directly in a flavor? | |
| 21:57:08 | efried | no, the alias is the level of abstraction available to flavors. | |
| 21:59:06 | openstackgerrit | Matt Riedemann proposed openstack/nova master: WIP: Add Selection.availability_zone field https://review.opendev.org/685807 | |
| 21:59:43 | markguz_ | efried: bummer. thanks though. | |
| 22:06:30 | openstackgerrit | Eric Fried proposed openstack/nova master: Allow versioned discovery unauthenticated https://review.opendev.org/685181 | |
| 22:39:52 | efried | mriedem: we used to have something in nova-specs that enforced conformance to the template, no?? | |
| 22:41:55 | efried | ah, it's hidden in pep8 | |
| 22:59:12 | openstackgerrit | Eric Fried proposed openstack/nova-specs master: Add 'Core Liaison' section to spec template https://review.opendev.org/685857 | |
| #openstack-nova - 2019-10-01 | |||
| 01:33:39 | openstackgerrit | Eric Fried proposed openstack/nova master: Allow versioned discovery unauthenticated https://review.opendev.org/685181 | |
| 02:47:08 | SonPham | hi | |
| 02:47:19 | SonPham | had any project to create live-snapshot for openstack? | |
| 02:47:48 | SonPham | snapshot with save ram state | |
| 03:01:28 | brinzhang_ | Now, nova not support to do for that | |
| 03:04:55 | openstackgerrit | Seyeong Kim proposed openstack/nova master: block_device: Optionally recreate attachments when refreshing connection_info https://review.opendev.org/579004 | |
| 03:07:43 | brinzhang_ | SonPham: sorry for above said, current, cannot do a live-snapshot for hte paused server of libvirt/qemu driver. | |
| 03:08:13 | brinzhang_ | paused and shutdown status server. | |
| 03:10:13 | melwitt | dansmith, mriedem: the doc reference got removed here https://github.com/openstack/nova/commit/009fd0f35bcb88acc80f12e69d5fb72c0ee5391f | |
| 03:26:16 | SonPham | brinzhang_ Can we save VM state (save Ram) in the snapshot? | |
| 03:31:27 | brinzhang_ | SonPham: I think you can, bug I am not sure, you can review that and try, with "disable_libvirt_livesnapshot" configuration in you env. | |
| 03:31:43 | brinzhang_ | SonPham: https://docs.openstack.org/nova/stein/configuration/config.html#workarounds.disable_libvirt_livesnapshot | |
| 03:54:41 | SonPham | brinzhang_ I'm using libvirt to create snapshot for instance | |
| 08:33:17 | mgoddard | mriedem: yeah, I meant multiple cells. We would be quite behind to not have any support for cells v2... | |
| 09:57:58 | bauzas | gibi: can I ask you something about how to create a new allocation ? | |
| 10:01:01 | gibi | bauzas: sure hit me | |
| 10:03:09 | bauzas | gibi: to explain it : http://paste.openstack.org/show/780546/ | |
| 10:03:30 | bauzas | gibi: I want to recreate the migration allocation that was deleted when confirming the resize | |
| 10:03:47 | bauzas | gibi: so after that, after running my audit command, it would find it | |
| 10:04:24 | bauzas | but then, I need a consumer_generation, right? | |
| 10:04:42 | bauzas | or should I just update the allocations ? | |
| 10:05:07 | bauzas | ie. https://docs.openstack.org/api-ref/placement/?expanded=update-allocations-detail#id72 | |
| 10:05:54 | gibi | bauzas: you want to recreate the migration allocation so I assume that there is no allocation with that consumer. In that case the consumer generation when you create the allocation should be 0 | |
| 10:06:09 | bauzas | gibi: that's correct | |
| 10:06:22 | bauzas | I no longer have allocations for the migration UUID | |
| 10:06:51 | bauzas | if so, we don't need to provide a generation version | |
| 10:07:11 | bauzas | gibi: do we have any helper for putting a new allocation in the functional tests ? | |
| 10:07:25 | gibi | I mean: "The generation of the consumer. Should be set to null when indicating that the caller expects the consumer does not yet exist." | |
| 10:07:54 | gibi | bauzas: I think I never needed to manually create allocation in the functional test | |
| 10:08:23 | bauzas | ok | |
| 10:10:22 | stephenfin | gmann: Still about? I'm stuck with https://review.opendev.org/#/c/684335/5/doc/api_samples/servers/v2.69/servers-details-resp.json | |
| 10:11:25 | stephenfin | gibi: You might be able to advise on ^ too | |
| 10:20:09 | openstackgerrit | Stephen Finucane proposed openstack/nova master: nova-net: Migrate 'test_server_tags' functional tests https://review.opendev.org/684335 | |
| 10:20:10 | openstackgerrit | Stephen Finucane proposed openstack/nova master: nova-net: Migrate 'test_servers' functional tests https://review.opendev.org/684336 | |
| 10:20:10 | openstackgerrit | Stephen Finucane proposed openstack/nova master: nova-net: Migrate 'test_hosts' functional tests https://review.opendev.org/684337 | |
| 10:20:11 | openstackgerrit | Stephen Finucane proposed openstack/nova master: nova-net: Migrate 'test_hypervisors' functional tests https://review.opendev.org/684340 | |
| 10:20:11 | openstackgerrit | Stephen Finucane proposed openstack/nova master: nova-net: Migrate 'test_attach_interfaces' functional tests https://review.opendev.org/684341 | |
| 10:20:12 | openstackgerrit | Stephen Finucane proposed openstack/nova master: nova-net: Migrate 'test_simple_tenant_usage' functional tests https://review.opendev.org/684342 | |
| 10:20:13 | openstackgerrit | Stephen Finucane proposed openstack/nova master: trivial: Neutron fixture cleanup https://review.opendev.org/684343 | |
| 10:20:13 | openstackgerrit | Stephen Finucane proposed openstack/nova master: nova-net: Migrate 'test_floating_ips' functional tests https://review.opendev.org/684344 | |
| 10:20:14 | openstackgerrit | Stephen Finucane proposed openstack/nova master: nova-net: Add TODOs for remaining nova-network functional tests https://review.opendev.org/684345 | |
| 10:20:14 | openstackgerrit | Stephen Finucane proposed openstack/nova master: tests: Correctly mock out security groups in NeutronFixture https://review.opendev.org/685927 | |
| 10:21:51 | openstackgerrit | Matthew Booth proposed openstack/nova master: libvirt: Ignore DiskNotFound during update_available_resource https://review.opendev.org/685391 | |
| 10:25:22 | gibi | stephenfin: do I understand the situation that the nova net base sample tests was not covered the sec group case and now that you add neutron based sample tests which has sec group you discovered a bug in the api behavior? | |