| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2018-04-23 | |||
| 16:52:51 | mriedem | if not, the next one is https://blueprints.launchpad.net/nova/+spec/list-show-all-server-migration-types and i have reservations about even supporting that now (i think i always did but got tired of pushing against it) | |
| 16:53:01 | mriedem | so i left some notes in the etherpad | |
| 16:57:04 | openstackgerrit | Surya Seetharaman proposed openstack/nova stable/queens: Cleanup RP and HM records while deleting a compute service. https://review.openstack.org/563698 | |
| 17:01:41 | jaypipes | lbragstad: some comments inline on your set scope_types for admin password policies patch. | |
| 17:01:49 | jaypipes | lbragstad: comments and questions that is... | |
| 17:05:52 | openstackgerrit | Matt Riedemann proposed openstack/nova stable/pike: Add policy rule to block image-backed servers with 0 root disk flavor https://review.openstack.org/563700 | |
| 17:08:42 | lbragstad | jaypipes: awesome - checking | |
| 17:16:54 | openstackgerrit | Zack Cornelius proposed openstack/nova-specs master: Libvirt file backed memory https://review.openstack.org/563704 | |
| 17:22:47 | openstackgerrit | Merged openstack/nova master: libvirt: fix wrong driver name for vhostuser interface https://review.openstack.org/561562 | |
| 17:31:00 | jaypipes | lbragstad: thx for the answers. so what does the 'all' in system={'all': True} refer to? | |
| 17:38:18 | artom | dansmith, https://review.openstack.org/#/c/563704/ you're some sort of ninja dude | |
| 17:38:48 | dansmith | artom: um, what? | |
| 17:39:18 | artom | 20 minutes since patch posted, 13 comments, that's close to 1 comment per minute :) | |
| 17:39:59 | dansmith | artom: only 14 between post and comment.. don't sell me short | |
| 17:40:40 | artom | Gomen, senpai | |
| 17:40:51 | artom | (Sincere apologies to all Japanese speakers here) | |
| 17:41:10 | dansmith | heh | |
| 17:42:30 | openstackgerrit | Julia Kreger proposed openstack/nova master: DNM: Test: Ironic: Lock the instance if plug vifs https://review.openstack.org/563714 | |
| 17:44:46 | dansmith | artom: when you're right you're right | |
| 17:45:09 | artom | I shall speak of this moment to my grandchildren | |
| 17:47:59 | melwitt | mriedem: ack | |
| 17:49:07 | openstackgerrit | Matt Riedemann proposed openstack/nova stable/ocata: Add policy rule to block image-backed servers with 0 root disk flavor https://review.openstack.org/563719 | |
| 17:52:38 | openstackgerrit | Chris Dent proposed openstack/nova master: Use nova.db.api directly https://review.openstack.org/543262 | |
| 17:54:11 | openstackgerrit | Jim Rollenhagen proposed openstack/nova master: WIP: ironic: add instance_uuid before any other spawn activity https://review.openstack.org/563722 | |
| 17:58:26 | lbragstad | jaypipes: it's supposed to refer to the entire deployment system | |
| 17:59:30 | lbragstad | jaypipes: following the documentation here - http://specs.openstack.org/openstack/keystone-specs/specs/keystone/queens/system-scope.html#authenticating-for-a-system-scoped-token | |
| 17:59:32 | jaypipes | lbragstad: ok. so the string 'all' is special? | |
| 17:59:38 | lbragstad | yeah | |
| 17:59:42 | jaypipes | gotcha | |
| 17:59:47 | openstackgerrit | Matt Riedemann proposed openstack/nova master: doc: add note about xenapi aggregate upcall being resolved https://review.openstack.org/563724 | |
| 18:00:23 | lbragstad | our intention was to build it so that eventually we could do something like system: {$service: $id} | |
| 18:00:43 | lbragstad | but that would be relayed in the token | |
| 18:06:59 | openstackgerrit | Matt Riedemann proposed openstack/nova master: api-ref: mark block_device_mapping_v2.boot_index as required https://review.openstack.org/563728 | |
| 18:07:52 | mriedem | alex_xu: see ^ i don't know if we should revert https://review.openstack.org/#/c/524208/ or not | |
| 18:08:04 | mriedem | i tend to think we should | |
| 18:35:49 | openstackgerrit | Matt Riedemann proposed openstack/nova master: Fix dropped check for boot_index 0 in _validate_bdm https://review.openstack.org/563732 | |
| 18:41:43 | openstackgerrit | Eric Fried proposed openstack/nova master: WIP: placement: Granular GET /allocation_candidates https://review.openstack.org/517757 | |
| 18:48:33 | openstackgerrit | Eric Fried proposed openstack/nova master: WIP: placement: Granular GET /allocation_candidates https://review.openstack.org/517757 | |
| 18:49:44 | openstackgerrit | Matt Riedemann proposed openstack/nova master: docs: link to volume multi-attach demo recording https://review.openstack.org/563734 | |
| 18:51:56 | openstackgerrit | Lance Bragstad proposed openstack/nova master: Set scope_types for admin password policies https://review.openstack.org/553613 | |
| 18:53:27 | mriedem | jackie-truong: can you post a spec amendment per L68 https://etherpad.openstack.org/p/nova-runways-rocky ? | |
| 18:54:50 | jackie-truong | mriedem: Yep, Peter Hamilton from our team is working on it | |
| 18:55:07 | mriedem | ok, thanks | |
| 18:55:16 | jackie-truong | In the mean time, Brianna has started a WIP patch for notifications: https://review.openstack.org/#/c/563269/ | |
| 19:11:12 | mriedem | arvindn05: i kind of think we should remove https://blueprints.launchpad.net/nova/+spec/glance-image-traits from the runways queue until there is agreement on the direction in https://review.openstack.org/#/c/560718/ | |
| 19:12:09 | mriedem | melwitt: do you want me to send something to the ML re https://blueprints.launchpad.net/nova/+spec/list-show-all-server-migration-types and if we should still do it? | |
| 19:13:06 | mriedem | of the 5 things next in line, i think https://review.openstack.org/#/q/topic:bp/add-host-to-instance-action-events+status:open is the only one that's really ready to go | |
| 19:18:15 | mriedem | esberglu: are you updating https://review.openstack.org/#/c/526094/ / | |
| 19:18:16 | mriedem | ? | |
| 19:19:44 | esberglu | mriedem: Yep working on it right now | |
| 19:25:18 | arvindn0_ | mriedem: does the runway queue allow for closure on the specs? | |
| 19:26:27 | arvindn0_ | mriedem: i was thinking we can discuss the spec in the runway if thats the case. Also, we are trying to make progress on other patches which hopefully can also be reviewed in the runway | |
| 19:28:32 | mriedem | arvindn0_: my understanding is that runways are for things that are ready to go | |
| 19:28:37 | mriedem | and i wouldn't consider this ready to go | |
| 19:28:59 | mriedem | btw, i'm trying to summarize alternatives for this in the ML to get some visibility | |
| 19:30:53 | openstackgerrit | Merged openstack/nova master: Add root and parent provider uuid to group by clause https://review.openstack.org/562379 | |
| 19:32:32 | arvindn0_ | mriedem: thanks. should be fine to move to end of runway...i guess the runway maintainer is going to make this change | |
| 19:38:39 | jaypipes | artom: if you have a minute, would you mind giving your thoughts on https://review.openstack.org/#/c/546713/1/os_traits/compute/net.py please? | |
| 19:39:09 | artom | jaypipes, looking | |
| 19:40:01 | jaypipes | artom: cheers | |
| 19:40:09 | artom | jaypipes, I'd go with gibi | |
| 19:40:35 | artom | Maybe a "real" example would make more sense: | |
| 19:40:55 | artom | 1. Just interface attachment: nova interface-attach port-id=blah | |
| 19:41:09 | artom | 2. Tagged attachment: nova interface-attach port-id=blah,tag=foo | |
| 19:44:39 | openstackgerrit | Arvind Nadendla proposed openstack/nova-specs master: Handle rebuild of instance with new image https://review.openstack.org/560718 | |
| 19:47:18 | arvindn0_ | jaypipes: can you add your thoughts on the above BP? if we can get direction from you whether modifyiny `GET /allocation_candidates` by adding an in_tree parameter AND make resources optional is something we can agree to, i can start thiking in that direction | |
| 19:52:15 | openstackgerrit | Merged openstack/nova master: Leave a hint when populate_schema fails https://review.openstack.org/562757 | |
| 19:54:43 | jaypipes | arvindn0_: I don't have any thoughts on the above BP. I don't know much about rebuild at all and trust everything mriedem says. | |
| 19:56:05 | artom | Oh hey are we reopening the rebuild with new image can of worms | |
| 19:56:56 | jaypipes | artom: sorry, coming back to you... so I don't understand why that is a particular capability of the virt driver... is there a reason adding metadata about devices is specific to a virt driver? | |
| 19:57:24 | arvindn0_ | jaypipes: are you OK with modifying allocation_candiadates API to not take resources as a required parameter? | |
| 19:57:26 | artom | jaypipes, because the driver is what knows about the actual hardware metadata, like PCI and MAC address for NICs | |
| 19:57:40 | jaypipes | arvindn0_: no, I am not. | |
| 19:57:57 | jaypipes | arvindn0_: if there is nothing to allocate, there's no reason to call GET /allocation_candidates. | |
| 19:58:35 | arvindn0_ | jaypipes: if there are strong opinions against it, then we need to drop that proposal... | |
| 19:59:01 | jaypipes | arvindn0_: ok, gimme a bit. | |
| 19:59:18 | jaypipes | arvindn0_: I see mriedem just posted to the ML. I will respond there. | |
| 19:59:41 | arvindn0_ | no problem...i know rebuild is a can of worms like artom mentioned :) | |
| 20:00:34 | jaypipes | artom: but why is the capability to associated a tag of "foo" with a PCI address something that is virt-driver dependent? | |
| 20:01:00 | dansmith | jaypipes: because the virt driver is what knows the address of the thing | |
| 20:01:10 | dansmith | jaypipes: if you ask for two nics, one tagged as foo and one as bar, | |
| 20:01:18 | artom | jaypipes, because some virt drivers don't have the code for it :) | |
| 20:01:19 | dansmith | only the virt driver knows how and where those are attached | |
| 20:02:01 | artom | (Wasn't trying to be condescending, I swear!) | |
| 20:02:03 | jaypipes | *sigh* | |
| 20:05:42 | jaypipes | dansmith, artom: so you're saying that nova interface-attach port-id=blah,tag=foo only works if specific virt drivers (libvirt only I guess?) are in use for the instance? | |
| 20:06:01 | artom | jaypipes, yes | |
| 20:06:10 | jaypipes | that's lovely. | |
| 20:06:36 | jaypipes | implementation-defined interfaces. | |
| 20:07:04 | dansmith | jaypipes: you know that some virt drivers don't even provide network interface attachments at all right? | |
| 20:07:06 | dansmith | *gasp* | |
| 20:07:13 | artom | I don't disagree, but hasn't that been the case for a while? It's sort of why we have the support matrix in the first place... | |
| 20:07:13 | jaypipes | artom: why doesn't something above the virt layer save the tag information for the interface? | |
| 20:07:44 | dansmith | jaypipes: it does happen above the virt driver level, but it doesn't have sufficient information to be useful | |
| 20:07:45 | artom | jaypipes, it does, and we could conceivably just put "device: {tag: foo}" in the metadata | |
| 20:07:53 | artom | But that's useless for the guest OS | |
| 20:08:07 | jaypipes | why is that useless for the guest OS | |
| 20:08:09 | jaypipes | ? | |
| 20:08:10 | dansmith | jaypipes: if we're attaching a pci nic at pci addres 1.2.3, or a virtio nic in slot 7, or a xenback device at /xenstore/foo/bar -- | |
| 20:08:24 | dansmith | those are the things the guest needs to know which tag applies to which | |