| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-04-13 | |||
| 20:31:49 | sean-k-mooney | well it has no "code" so i kindof makes sense that it would not be needed | |
| 20:32:43 | melwitt | mriedem: for adding "upgrade impact" to the spec template, should I do it only for the queens template or for pike and queens? | |
| 20:32:53 | mriedem | melwitt: quenes | |
| 20:32:55 | mriedem | *queens | |
| 20:32:57 | melwitt | thanks | |
| 20:33:28 | clarkb | yasfb made a release today | |
| 20:34:16 | clarkb | checking if a downgrade fixes | |
| 20:34:26 | jangutter | There is definitely a lot of non-ascii characters in the specs. | |
| 20:34:27 | mriedem | me too | |
| 20:36:04 | mriedem | clarkb: yeah that works | |
| 20:37:27 | openstackgerrit | Matt Riedemann proposed openstack/nova-specs master: Cap yasfb at 0.6.0 https://review.openstack.org/456754 | |
| 20:38:12 | openstackgerrit | Matt Riedemann proposed openstack/nova-specs master: Cap yasfb at 0.6.0 https://review.openstack.org/456754 | |
| 20:38:24 | sean-k-mooney | mriedem: do we need to cap that in upper constraits too | |
| 20:38:34 | mriedem | sean-k-mooney: we don't use it from u-c | |
| 20:38:49 | mriedem | yasfb isn't in u-c | |
| 20:39:02 | mriedem | you know, i think the last time i figured out that nova-specs doesn't use u-c, it was because of yasfb | |
| 20:39:05 | sean-k-mooney | mriedem: yes but i assume this will hit others out side of nova? | |
| 20:39:17 | sean-k-mooney | haha | |
| 20:39:24 | mriedem | https://github.com/openstack/nova-specs/commit/8c0a70ec54c3e4c764fdf34cd0db59fa9c6cd095 | |
| 20:39:28 | mriedem | i don't think we even need to use it | |
| 20:39:42 | sean-k-mooney | is there any reason that we cant make the specs utf-8 out of interest | |
| 20:40:05 | clarkb | sounds like because yasfb | |
| 20:40:11 | mriedem | i'm bugging doug | |
| 20:40:12 | openstackgerrit | melanie witt proposed openstack/nova-specs master: Add a new section: "Upgrade impact" to the template https://review.openstack.org/456756 | |
| 20:40:18 | mriedem | dougbug | |
| 20:40:42 | sean-k-mooney | didnt stephen just disable building all sphinx target except html | |
| 20:41:02 | mriedem | yeah | |
| 20:41:06 | sean-k-mooney | are we still building the rss xml output? | |
| 20:41:16 | mriedem | i guess? https://review.openstack.org/#/c/456754/ | |
| 20:41:18 | mriedem | oops | |
| 20:41:23 | mriedem | http://specs.openstack.org | |
| 20:41:56 | itlinux | hello all, has anyone adopted a way to automatically register a name of the VM to a DNS server without using Deseginete? | |
| 20:42:20 | sean-k-mooney | but presumable that is done as a post merge job. it could just be installed in the job. | |
| 20:43:15 | itlinux | should we have cloud-init do this.. | |
| 20:43:29 | mriedem | ok fast approved https://review.openstack.org/#/c/456754/ | |
| 20:47:03 | mriedem | +2 on handling volume extend events from cinder https://review.openstack.org/#/c/453272/ spec if someone else can +W | |
| 20:50:15 | openstackgerrit | Matt Riedemann proposed openstack/nova-specs master: Spec to enable Netronome SmartNIC support https://review.openstack.org/456386 | |
| 20:50:24 | mriedem | jangutter: you should be fixed now | |
| 20:50:28 | mriedem | just need to address sean-k-mooney's comments | |
| 20:50:40 | jangutter | Thanks. | |
| 20:50:49 | openstackgerrit | Matt Riedemann proposed openstack/nova-specs master: Add a new section: "Upgrade impact" to the template https://review.openstack.org/456756 | |
| 20:51:58 | sean-k-mooney | mriedem: jangutter my only real feedback is on the logation fo the os-vif code. if its not upstream in the main ovs repo the pluging changes need to be in an external plugin | |
| 20:52:05 | jangutter | sean-k-mooney: I understand that the VIF types would likely need to be forked because we're not upstream (yet). | |
| 20:52:42 | sean-k-mooney | jangutter: well the vif object definition should go in os-vif even for external plugins | |
| 20:52:48 | openstackgerrit | melanie witt proposed openstack/nova-specs master: Amend spec for placement project/user association https://review.openstack.org/454352 | |
| 20:53:02 | sean-k-mooney | jangutter: that is to ensure we all have a common set of datamodels | |
| 20:53:19 | jangutter | sean-k-mooney: yep, agreed, but it would still be acceptable? | |
| 20:53:40 | sean-k-mooney | createing the port profiles in os-vif yes | |
| 20:54:46 | jangutter | forgive me if I'm operating a bit on the wonky side, I claim a severe lack of sleep and the wrong timezone... | |
| 20:54:46 | sean-k-mooney | jangutter: the changes to vif_plug_ovs in https://review.openstack.org/#/c/456483/ should be done in an external os-vif plugin | |
| 20:56:10 | sean-k-mooney | the changes to the os_vif objects should got to os-vif | |
| 20:56:38 | jangutter | OK, so an extra task would be: create a new external plugin (replicating what the OVS plugin does). | |
| 20:56:56 | sean-k-mooney | jangutter: yes but only replicating the part you need | |
| 20:57:30 | sean-k-mooney | os-vif was structured so that you can clone it and the cp one of the plugin sub directos and use that as the base for a new plugin. | |
| 20:58:04 | jangutter | Yep, I noticed that too, it's pretty awesome. | |
| 20:58:26 | sean-k-mooney | jangutter: of example i dont think you need to support iptables/hybrid plug in you case correct | |
| 20:58:46 | jangutter | Correct: that part of the kernel is short-circuited. | |
| 20:59:03 | jangutter | We do support the ovs conntrac rules on the chip though. | |
| 20:59:10 | sean-k-mooney | so the plugin itself should be failly small | |
| 20:59:13 | sean-k-mooney | cool | |
| 20:59:37 | jangutter | Thanks, amending spec. | |
| 21:00:05 | sean-k-mooney | contrack should not effect the plug dirver code though. if you want me to review the plugin or help you with it let me know | |
| 21:00:20 | mriedem | nova meeting itme | |
| 21:00:21 | mriedem | *time | |
| 21:00:24 | mriedem | in #openstack-meeting | |
| 21:15:01 | openstackgerrit | Jan Gutter proposed openstack/nova-specs master: Spec to enable Netronome SmartNIC support https://review.openstack.org/456386 | |
| 21:23:42 | sean-k-mooney | mriedem: that was a short and sweet meeting | |
| 21:23:43 | jangutter | sean-k-mooney: yep, nova is blithely oblivious to conntrack. | |
| 21:28:19 | bauzas | mriedem: I guess https://review.openstack.org/#/c/448253/ is very latent for Ubuntu given they still provide an old libvirt ? | |
| 21:29:46 | openstackgerrit | Rick Bartra proposed openstack/nova master: Add policy granularity to the Flavor API https://review.openstack.org/449288 | |
| 21:30:27 | openstackgerrit | Rick Bartra proposed openstack/nova master: Add policy granularity to the Flavor API https://review.openstack.org/449288 | |
| 21:31:59 | sean-k-mooney | jangutter: minor nit in latest version of https://review.openstack.org/#/c/456386/9 but otherwise this looks good to me | |
| 21:32:19 | jangutter | The main reason I left that in there was to coordinate with the Mellanox guys. | |
| 21:32:30 | bauzas | mriedem: yeah confirmed, xenial LTS is having libvirt-1.3.1 http://packages.ubuntu.com/xenial/libvirt-bin | |
| 21:32:32 | mriedem | bauzas: yes, outside of UCA | |
| 21:32:44 | mriedem | bauzas: we regressed ubuntu with a fix for centos 7.3 | |
| 21:32:47 | mriedem | that assumed a newer libvirt | |
| 21:32:54 | bauzas | okay | |
| 21:32:54 | mriedem | which was ok for centos, but broke xenial | |
| 21:32:59 | mriedem | so we straddle the versions now | |
| 21:33:00 | jangutter | sean-k-mooney: If we can come up with a common standard, it might get us that much closer to upstream by default into OVS. | |
| 21:33:34 | sean-k-mooney | jangutter: ya the melonox work seams to be getting traction upstream in ovs | |
| 21:34:03 | bauzas | mriedem: so, if you deploy Nova on Xenial without using the UCA packages, then kaboom, correct? | |
| 21:34:19 | sean-k-mooney | if you are able to make that work for ye then all of these changes could go into the openvswitch plugin in os-vif | |
| 21:35:31 | jangutter | sean-k-mooney: yep, but the TC stuff is kernel hackery, and the bar for merging that is VERY high. | |
| 21:36:27 | sean-k-mooney | ya i know we have looked at doing something similar with dpdk in the past | |
| 21:36:51 | sean-k-mooney | we canceled those nics though so that got pushed back | |
| 21:37:36 | jangutter | sean-k-mooney: As have we. The funny thing is that there doesn't seem to be something at this stage that does everything well. | |
| 21:37:50 | jangutter | *looked at DPDK. | |
| 21:38:10 | sean-k-mooney | i know of at least 3 vendors who have done something in this space now so it would be nice to have a singel api in ovs for this. | |
| 21:38:31 | mriedem | bauzas: and you have one of these vif types | |
| 21:38:34 | mriedem | that set that config | |
| 21:38:56 | mriedem | bauzas: but yeah, they were picking up the latest newton patch release which regressed them | |
| 21:38:56 | jangutter | sean-k-mooney, I definitely owe you your libation of choice. | |
| 21:39:11 | bauzas | okay, anyway, +2d | |
| 21:39:25 | mriedem | cool thanks | |
| 21:39:42 | sean-k-mooney | jangutter: ah no worries im happy to help. | |
| 21:39:48 | dtp | can i get a ruling on https://blueprints.launchpad.net/nova/+spec/conf-network-metadata-always-static-ip, please? | |
| 21:40:05 | dtp | unsure what to do next w/ it | |
| 21:40:16 | mriedem | clarkb: mordred: are you interested in https://review.openstack.org/#/c/336293/ ? | |