| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-03-21 | |||
| 15:31:52 | bauzas | jroll: not sure it could be a bug, but I would appreciate some brainstorm | |
| 15:35:03 | openstackgerrit | Sujitha proposed openstack/nova master: Add description to policies in admin_actions. https://review.openstack.org/440829 | |
| 15:37:50 | openstackgerrit | Sujitha proposed openstack/nova master: Add description to policies in admin_password.py https://review.openstack.org/443957 | |
| 15:38:28 | openstackgerrit | Sujitha proposed openstack/nova master: Add description to policies in agents.py https://review.openstack.org/445208 | |
| 15:40:21 | openstackgerrit | Sandeep Pawar proposed openstack/nova master: Libvirt volume driver for Veritas HyperScale https://review.openstack.org/443951 | |
| 15:40:23 | jroll | bauzas: resize depends on migrate being available, right? | |
| 15:40:38 | jroll | (which ironic can't do) | |
| 15:40:39 | bauzas | jroll: nova resize ? | |
| 15:40:42 | jroll | yes | |
| 15:40:58 | bauzas | I dunno, but good point, lemme verify | |
| 15:41:07 | openstackgerrit | Sujitha proposed openstack/nova master: Add description to policies in aggregates.py https://review.openstack.org/445230 | |
| 15:41:10 | jroll | I'm looking, I see lots of migration code in it | |
| 15:41:16 | bauzas | jroll: either way, this spec doesn't only target a specific virt driver | |
| 15:41:34 | bauzas | so I'm supposing it can be possible | |
| 15:41:42 | bauzas | eg. FPGA devices with libvirt | |
| 15:41:51 | jroll | bauzas: your resize concerns are around the upgrade thing we do in the ironic driver, though | |
| 15:41:54 | bauzas | although it would require libvirt to expose it | |
| 15:42:07 | jroll | (afaict) | |
| 15:42:23 | bauzas | jroll: well, basically I thought about resize because it's all about an existing instance taking an API flavor | |
| 15:42:43 | bauzas | here, that spec is focusing on changing the instance nested flavors, not the API-faced flavors AFAICS | |
| 15:43:06 | bauzas | so we could end up mixing both old and new world, which could be a problem | |
| 15:43:18 | bauzas | jroll: tbc, my -1 is for signaling a potential problem | |
| 15:43:22 | jroll | I still don't get it, sorry :/ | |
| 15:43:26 | jroll | yeah I understand that much :) | |
| 15:43:39 | jroll | just trying to understand the concern | |
| 15:43:46 | bauzas | jroll: first, lemme verify if resize is available for ironic | |
| 15:44:01 | jroll | sure | |
| 15:44:27 | bauzas | mmm, it is not | |
| 15:44:28 | bauzas | https://docs.openstack.org/developer/nova/support-matrix.html#operation_resize | |
| 15:44:57 | bauzas | so perhaps it can be a nobrainer | |
| 15:45:04 | mriedem | cfriesen: comments in https://review.openstack.org/#/c/265282/ | |
| 15:45:15 | mriedem | cfriesen: i'm +2 otherwise | |
| 15:47:42 | jroll | bauzas: replied in gerrit | |
| 15:53:40 | bauzas | jroll: I'm still struggling to evaluate the impacty | |
| 15:53:46 | bauzas | impact* | |
| 15:55:11 | jroll | bauzas: that instance.flavor migration thing only impacts allocations, afaict | |
| 15:55:44 | mriedem | cfriesen: nvm i'll just address the issues quick and approve | |
| 15:59:04 | bauzas | jroll: just to make sure I understand correctly | |
| 15:59:35 | bauzas | jroll: we migrate the existing instances in order to self-heal the allocations that would claim custom resource classes, right? | |
| 16:01:02 | jroll | bauzas: yep. we don't want a flavor to appear that suddenly can claim a node with an instance already on it | |
| 16:01:08 | jroll | though, thinking back to this morning | |
| 16:01:39 | jroll | if we make a change that makes nova claim all resources for ironic nodes with an instance... we don't need this extra migration | |
| 16:03:11 | bauzas | jroll: graaah, just entering a team meeting, need to defer my thinkins for that :( | |
| 16:03:17 | bauzas | thinkings* | |
| 16:03:22 | jroll | bauzas: it's fine, no worries | |
| 16:05:40 | jamespage | mriedem: hello | |
| 16:05:48 | jamespage | mriedem: would you have time to chat about https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1665698 | |
| 16:05:48 | openstack | Launchpad bug 1665698 in libvirt (Ubuntu Yakkety) "/etc/qemu-ifup not allowed by apparmor" [Medium,Triaged] | |
| 16:06:36 | mriedem | jamespage: ok, but i have no context on that. | |
| 16:06:48 | jamespage | mriedem: let me give you some :-) | |
| 16:06:53 | jamespage | mriedem: ok so... | |
| 16:06:56 | jamespage | mriedem: some history | |
| 16:07:04 | mriedem | this is the empty script path element thing? | |
| 16:07:11 | mriedem | i saw there was a revert proposed for that | |
| 16:07:18 | mriedem | sgordon: ^ | |
| 16:07:25 | jamespage | mriedem: that's the one | |
| 16:07:32 | jamespage | mriedem: the fix for bug 1649527 | |
| 16:07:32 | openstack | bug 1649527 in OpenStack Compute (nova) newton "nova creates an invalid ethernet/bridge interface definition in virsh xml" [Medium,Fix committed] https://launchpad.net/bugs/1649527 - Assigned to Roman Podoliaka (rpodolyaka) | |
| 16:08:17 | jamespage | appears to have broken baseline compatibility for libvirt so for certain vif types, xenial libvirt + newton stable is broken. | |
| 16:08:23 | bauzas | jroll: one other thinking while attending my meeting, if we rebuild an instance having a modified nested flavor, we could just put it to a Pike node then, right? | |
| 16:08:54 | openstackgerrit | Matt Riedemann proposed openstack/nova-specs master: add spec for instance flavor API https://review.openstack.org/265282 | |
| 16:08:57 | bauzas | jroll: to make it clear, I'm not trying to punt your spec, just trying to think about all the possible move operations | |
| 16:09:44 | jroll | bauzas: yeah, I know what you're doing, I'm not upset about it | |
| 16:09:57 | bauzas | :) | |
| 16:10:18 | bauzas | I'm just an overthinking person :( | |
| 16:10:18 | jroll | bauzas: I would need to read rebuild code to answer that question, but I assume we use instance.flavor for that, which means the scheduling decision would be different. interesting. | |
| 16:10:35 | jroll | bauzas: "pike node" means a node with a resource class set, yes? | |
| 16:10:46 | mriedem | jamespage: ok it's confusing because of comments like this in the original bug report https://bugs.launchpad.net/nova/+bug/1649527/comments/19 | |
| 16:10:46 | openstack | Launchpad bug 1649527 in OpenStack Compute (nova) newton "nova creates an invalid ethernet/bridge interface definition in virsh xml" [Medium,Fix committed] - Assigned to Roman Podoliaka (rpodolyaka) | |
| 16:11:00 | bauzas | jroll: a node that supports that custom RC | |
| 16:11:08 | mriedem | jamespage: also though libvirt 2.5.0 isn't base xenial | |
| 16:11:13 | mriedem | base xenial libvirt is 1.3.1 right? | |
| 16:11:14 | jroll | bauzas: right, yeah, it would be scheduled that way | |
| 16:11:19 | jamespage | mriedem: nope - its 1.3.1 | |
| 16:11:28 | jamespage | mriedem: that was a somewhat unhelpful comment | |
| 16:11:37 | jroll | bauzas: I'm thinking if we can do the "allocate all resources" thing outside of instance.flavor, we don't need to do this instance.flavor migration | |
| 16:11:55 | jamespage | mriedem: I found the bug history quite confusing as well | |
| 16:12:24 | bauzas | jroll: yeah I tend to agree with you although there could be some corner cases | |
| 16:13:12 | mriedem | jamespage: yeah they later clarified they were running in a container with debian so different versions :/ | |
| 16:13:36 | bauzas | jroll: I'm just afraid of us possibly needing to do like we made for Ocata and just having the scheduler calling placement about custom RCs only if all the nodes are pike | |
| 16:13:37 | mriedem | jamespage: so i guess this didn't affect rhel 7.3 or centos because they are running with a newer libvirt which doesn't cause issues that 1.3.1 does | |
| 16:14:06 | mriedem | jamespage: this isn't just newton right? i mean it would also be broken in ocata wouldn't it? | |
| 16:14:15 | mriedem | i see the backport was merged to newton though https://review.openstack.org/#/c/425637/ | |
| 16:14:28 | mriedem | and we didn't raise the minimum required libvirt in nova in ocata | |
| 16:15:28 | jroll | bauzas: yeah, I see now, because we upgrade scheduler before compute, right? | |
| 16:15:40 | bauzas | jroll: yup | |
| 16:16:05 | jroll | bauzas: which means operators must wait until after the pike deploy to change their flavors. which isn't ideal but I think it's fine? | |
| 16:16:26 | bauzas | jroll: hum no | |
| 16:16:38 | bauzas | jroll: operators can modify their flavors in Ocata | |
| 16:16:52 | bauzas | given it's extra specs, it's just meaningless until Pike, that's it | |
| 16:17:07 | jroll | bauzas: pike scheduler + ocata compute means scheduling on new style flavors would be broken | |
| 16:17:22 | jroll | because we won't be reading resource class | |
| 16:18:03 | bauzas | jroll: yeah the worst case scenario would be all but computes upgraded to Pike, and n-cpus still on Ocata | |
| 16:18:14 | bauzas | jroll: then, if flavors are upgraded, kaboom | |
| 16:18:20 | bauzas | NoValidHosts | |
| 16:18:24 | mriedem | jamespage: so if i'm understanding this correctly, between https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1665698/comments/50 and https://review.openstack.org/#/c/425637/1/releasenotes/notes/libvirt-script-with-empty-path-2b49caa68b05278d.yaml | |
| 16:18:24 | openstack | Launchpad bug 1665698 in libvirt (Ubuntu Yakkety) "/etc/qemu-ifup not allowed by apparmor" [Medium,Triaged] | |
| 16:18:44 | mriedem | jamespage: we want script path to be '' if libvirt < 1.3.3, and None if libvirt >= 1.3.3 yes? | |
| 16:18:51 | jroll | bauzas: right, which I guess is why I need reviews on this, too :) https://etherpad.openstack.org/p/nova-ironic-flavor-transition-plan | |
| 16:19:04 | bauzas | oh, never heard of that yet ^ | |