| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2019-05-02 | |||
| 15:08:26 | mriedem | i just need to run a play after devstack is done but before tempest runs so i can modify policy on the controller | |
| 15:08:52 | mriedem | everything else in my role works fine but that orchestrate-devstack thing seems to screw things up with starting glance-api | |
| 15:09:57 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Enable cross-cell resize in the nova-multi-cell job https://review.opendev.org/656656 | |
| 15:10:40 | mriedem | lyarwood: can you poke these backports now? https://review.opendev.org/#/q/status:open+project:openstack/nova+branch:stable/stein+topic:bug/1825020 | |
| 15:11:03 | lyarwood | mriedem: yarp | |
| 15:14:26 | efried | gryf: https://etherpad.openstack.org/p/nova-ptg-train | |
| 15:15:31 | gryf | efried, thanks. | |
| 15:20:59 | openstackgerrit | Merged openstack/nova-specs master: Abandon flavor-classes backlog spec https://review.opendev.org/649095 | |
| 15:36:14 | openstackgerrit | Dan Smith proposed openstack/nova master: Add image type request filter https://review.opendev.org/656413 | |
| 15:36:23 | gmann | mriedem: which patch you did the pre- run-tempest in devstack playbook ? i did not find in https://review.opendev.org/#/c/655222/9 | |
| 15:41:06 | mriedem | gmann: https://review.opendev.org/#/c/656656/ | |
| 15:41:22 | mriedem | gmann: note https://review.opendev.org/#/c/656656/2..3/playbooks/nova-multi-cell/pre.yaml | |
| 16:20:49 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Add a live migration regression test https://review.opendev.org/641200 | |
| 16:29:03 | openstackgerrit | Maxim Nestratov proposed openstack/nova-specs master: Reduce CPU and RAM quota when VM is shelved https://review.opendev.org/656806 | |
| 16:30:48 | openstackgerrit | Maxim Nestratov proposed openstack/nova-specs master: Reduce CPU and RAM quota when VM is shelved https://review.opendev.org/656806 | |
| 16:34:39 | openstackgerrit | Takashi NATSUME proposed openstack/nova master: Add TODO note for mox removal https://review.opendev.org/576758 | |
| 16:53:16 | openstackgerrit | Maxim Nestratov proposed openstack/nova-specs master: Reduce CPU and RAM quota when VM is shelved https://review.opendev.org/656806 | |
| 17:16:23 | artom | mdbooth, as in, in the same cloud you could have computes too old to support a thing (tags, multiattach) | |
| 17:16:34 | artom | Not the case anymore, but was a thing in the cycle when those were introduced | |
| 17:17:04 | openstackgerrit | Rodolfo Alonso Hernandez proposed openstack/os-vif master: Remove unused vif_plug_ovs.i18n module https://review.opendev.org/656815 | |
| 17:29:04 | openstackgerrit | Maxim Nestratov proposed openstack/nova-specs master: Reduce CPU and RAM quota usage when server is shelved https://review.opendev.org/656806 | |
| 17:37:45 | stephenfin | cdent: Wanna blindly approve some patches for me? https://review.opendev.org/#/q/project:x/wsme+topic:trivial+status:open | |
| 17:37:56 | stephenfin | cdent: Should probably kick off a 1.0 release then | |
| 17:44:30 | cdent | stephenfin: I removed myself from wsme, or at least meant to. Talk to dtantsur | |
| 17:45:00 | dtantsur | stephenfin: will approve when they pass the CI | |
| 17:45:17 | stephenfin | ta | |
| 17:45:45 | dtantsur | I'm not sure why I don't see them in my gerrty.. I wonder if something broke during the transition for me. | |
| 17:45:52 | dtantsur | ah, no, here they are | |
| 17:48:58 | openstackgerrit | Maxim Nestratov proposed openstack/nova-specs master: Reduce CPU and RAM quota usage for servers in SHELVED_OFFLOADED state https://review.opendev.org/656806 | |
| 18:12:50 | cdent | I want mriedem's face right now to be my new social media avatar | |
| 18:17:16 | openstackgerrit | Merged openstack/nova stable/stein: Add functional regression recreate test for bug 1825020 https://review.opendev.org/656511 | |
| 18:17:17 | openstack | bug 1825020 in OpenStack Compute (nova) stein "resize of instance, that was booted from volume, trigger image size check then fails resize" [High,In progress] https://launchpad.net/bugs/1825020 - Assigned to Matt Riedemann (mriedem) | |
| 18:21:46 | mriedem | cdent: hands over face? | |
| 18:27:14 | openstackgerrit | Balazs Gibizer proposed openstack/nova master: Reset the stored logs at each notification test steps https://review.opendev.org/656844 | |
| 19:00:17 | openstackgerrit | Chris Friesen proposed openstack/nova master: Preserve UEFI NVRAM variable store https://review.opendev.org/621646 | |
| 19:47:19 | openstackgerrit | Adrian Chiris proposed openstack/nova master: Move get_pci_mapping_for_migration to MigrationContext https://review.opendev.org/643023 | |
| 19:47:19 | openstackgerrit | Adrian Chiris proposed openstack/nova master: Allow driver to properly unplug VIFs on destination on confirm resize https://review.opendev.org/643024 | |
| 19:48:31 | openstackgerrit | Merged openstack/nova stable/stein: Fix volume-backed resize with a smaller disk flavor https://review.opendev.org/656666 | |
| 19:53:40 | dansmith | mriedem: I think I performed cranial extraction on https://review.opendev.org/#/c/656413 | |
| 19:56:34 | jroll | did we ever finish the network aware scheduling thing? or is there some way to tie a network to an aggregate that I'm not seeing? | |
| 19:56:56 | jroll | I know that neutron's routed networks creates placement aggregates for each segment, do I just drop hosts into that aggregate? | |
| 19:57:12 | mriedem | mlavalle: ^ | |
| 19:58:06 | mlavalle | jroll: in principle yes, but there is work pending in Nova | |
| 19:59:16 | jroll | mlavalle: ok, so right now if I connect the hosts to the aggregate, it won't stop nova from putting the 'wrong' network on the host? | |
| 19:59:30 | mlavalle | jroll: correct | |
| 19:59:37 | jroll | mlavalle: ok, thanks | |
| 19:59:48 | jroll | totally thought that was done already, sigh | |
| 20:00:11 | mriedem | jroll: no, osic laying everyone off working on it kind of ... stalled things out | |
| 20:00:34 | jroll | hasn't osic ruined my life enough already? | |
| 20:00:42 | mriedem | obviously not | |
| 20:00:56 | jroll | :| | |
| 20:00:59 | mriedem | if it makes you feel better, there are plenty of new intel specs to discuss at the ptg today | |
| 20:01:11 | jroll | that does make me feel better about not being there | |
| 20:02:10 | mriedem | i forget what we even need for linking the routed network aggregates | |
| 20:02:54 | mriedem | neutron creates a placement aggregate around the nova compute node resource providers in a given network segment, right? | |
| 20:02:59 | jroll | this is the most recent I could find: https://review.opendev.org/#/q/topic:bp/prep-for-network-aware-scheduling-pike | |
| 20:03:01 | jroll | correct | |
| 20:03:40 | mriedem | and when creating a server with a given network or port, we want to create the server on a host in the aggregate associated with that network | |
| 20:04:10 | jroll | correct | |
| 20:04:24 | mriedem | and placement aggregates don't have ids, so we can't just rely on some aggregate id being in the network meta for nova to use during scheduling | |
| 20:04:42 | mriedem | but the nova host aggregate has a uuid, | |
| 20:04:57 | mriedem | and if we could link the network to that aggregate uuid, then we could .... | |
| 20:04:58 | mriedem | idk | |
| 20:05:02 | jroll | seems like it would also fit in the get-me-a-network stuff - choose a network that can be used on the selected host | |
| 20:05:02 | mriedem | i'm confusing myself | |
| 20:05:12 | jroll | you're confusing me more I suspect | |
| 20:05:38 | mriedem | we have placement request pre-filters in the scheduler now that leverage placement aggregates, | |
| 20:05:47 | mriedem | i'm just trying to think through how we could do something like that for this | |
| 20:06:21 | jroll | I appreciate that :) | |
| 20:06:33 | jroll | I'm happy to talk post-ptg sometime to not distract you | |
| 20:07:51 | mriedem | oh ok, | |
| 20:08:12 | mriedem | so yeah, aggregates in placement are just a grouping concept of resource providers (compute nodes here), and the aggregate in placement is just an id, | |
| 20:08:53 | mriedem | if we had that aggregate id stored on the network resource in neutron, we could just translate that in nova during scheduling to say 'give me all allocation candidates (compute nodes) in that provider aggregate for this network' | |
| 20:09:11 | mriedem | mlavalle: is the provider aggregate in placement stored in the network resource or anywhere related to it? | |
| 20:09:25 | mriedem | *aggregate id | |
| 20:09:53 | jroll | ctrl-f "Verify that inventories were created for each segment " https://docs.openstack.org/neutron/rocky/admin/config-routed-networks.html | |
| 20:10:01 | jroll | looks like the resource provider ID is the network segment | |
| 20:10:29 | jroll | the segment has the network ID but dunno about vice versa | |
| 20:10:49 | jroll | can query segments by network ID, so that could work | |
| 20:13:08 | mriedem | the network resource has a list of segments | |
| 20:14:14 | jroll | hmm, it does, but not with UUIDs :/ | |
| 20:14:48 | mriedem | https://developer.openstack.org/api-ref/network/v2/index.html?expanded=show-network-details-detail#response-example-admin-user-multiple-segment-mappings | |
| 20:15:11 | mriedem | right so how to translate that to https://developer.openstack.org/api-ref/network/v2/index.html?expanded=show-network-details-detail#segments | |
| 20:15:49 | mriedem | GET /v2.0/segments?segmentation_id=1,segmentation_id=2,etc | |
| 20:15:52 | mriedem | i think? | |
| 20:16:01 | mriedem | and then from those, you use the uuid id to get the providers | |
| 20:16:55 | mriedem | and then from those, you what? get the provider aggregates that those segments are in? | |
| 20:17:28 | mriedem | and those aggregates are mirrored as nova host aggregates that you, the admin, have to put hosts into...right? | |
| 20:18:07 | mriedem | would need to sit down with mlavalle probably to make sure i'm understanding properly, but it sounds like the pieces are there | |
| 20:18:50 | mriedem | would be much easier to play with if i had a devstack with routed networks setup, but i'm not sure how easy that is | |
| 20:19:38 | jroll | well if we're going to do another API call, we could just do GET /v2.0/segments?network_id=foo | |
| 20:19:55 | jroll | the segment UUID is the UUID for the resource provider aggregate | |
| 20:20:09 | jroll | and yeah, I assume the admin would have to put the hosts in there | |
| 20:23:08 | mriedem | i thought the segment id (uuid) was the provider id, | |
| 20:23:09 | mriedem | not the aggregate id | |
| 20:23:21 | mriedem | but yeah GET /v2.0/segments?network_id=foo is simpler | |
| 20:27:27 | mriedem | a couple of issues with this in nova scheduler right now: 1. we don't have the requested networks in the RequestSpec 2. we don't yet have the ability to put a RequestGroup in the spec that is not filtering on some kind of resource (e.g. filtering on just traits or aggregates), but the good news is i think both of those are in progress | |
| 20:28:30 | mriedem | 1: https://review.opendev.org/#/c/570201/ | |
| 20:29:45 | mriedem | gibi_cape: don't you have a patch for supporting an unnumbered request group that doesn't require resources? | |
| 20:30:44 | mriedem | https://review.opendev.org/#/c/647396 | |