| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2017-04-13 | |||
| 20:11:39 | jangutter | sean-k-mooney: I've updated it to https://review.openstack.org/#/c/456386/7/specs/pike/approved/netronome-smartnic-enablement.rst | |
| 20:12:01 | jangutter | sean-k-mooney: would you mind checking? tox completes fine on my side... | |
| 20:12:11 | peter-hamilton | jaypipes: do you think you'll be able to get to the cert validation spec today? | |
| 20:12:33 | peter-hamilton | jaypipes: don't want to be pest, obv | |
| 20:12:38 | mriedem | i think he's under the weather | |
| 20:12:45 | peter-hamilton | mriedem: ah, ok | |
| 20:13:17 | peter-hamilton | mriedem: do you mind giving it a look over then? he's been a +2 for the past couple versions | |
| 20:13:35 | mriedem | i've got some other things queued up first | |
| 20:15:15 | peter-hamilton | mriedem: gotcha | |
| 20:16:04 | sean-k-mooney | jangutter: sure im just pulling it down now | |
| 20:17:44 | mriedem | me too | |
| 20:20:29 | sean-k-mooney | jangutter: ya i get the same error as the gate | |
| 20:21:01 | mriedem | me too | |
| 20:21:03 | mriedem | after i rebased | |
| 20:21:07 | mriedem | and did a tox -r -e docs | |
| 20:22:15 | mriedem | i'm wondering if it has something to do with this https://github.com/openstack/nova-specs/commit/0a4c1bcaeb600229103cc61d574d57cac320ba84 | |
| 20:22:19 | openstackgerrit | Dan Smith proposed openstack/nova master: Fix hypervisors api missing HostMappingNotFound handlers https://review.openstack.org/456227 | |
| 20:22:25 | clarkb | oh chardet updated | |
| 20:22:38 | clarkb | and I know openstack-manuals ran into a similar problem | |
| 20:22:54 | mriedem | ah yeah | |
| 20:22:56 | mriedem | 3.0.2 | |
| 20:23:09 | jangutter | Are those the dashes we are looking for? | |
| 20:23:25 | mriedem | *2.3.0 | |
| 20:23:37 | sean-k-mooney | so we have to cap chardet or is there a way to fix it? | |
| 20:24:08 | mriedem | oh wait no 3.0.2 is new, but u-c is using 2.3.0 | |
| 20:24:48 | mriedem | clarkb: i don't see chardet used in this job | |
| 20:24:51 | mriedem | http://logs.openstack.org/86/456386/7/check/gate-nova-specs-docs-ubuntu-xenial/9c8b9dd/tox/venv-3.log | |
| 20:25:07 | jangutter | I've had _fun_ with pbr and tox before. | |
| 20:27:02 | mriedem | someone remind me next time i mark my entire nova folder as read in thunderbird, that i need to not set view > threads > threads with unread | |
| 20:27:07 | mriedem | because i got scared | |
| 20:27:32 | sdague | heh | |
| 20:28:35 | sean-k-mooney | mriedem: clarkb downgradeing chardet to 2.3.0 has no effect | |
| 20:29:05 | mriedem | yeah we have chardet 2.3.0 in u-c already | |
| 20:29:08 | mriedem | that's not new | |
| 20:29:52 | mriedem | reverting https://github.com/openstack/nova-specs/commit/0a4c1bcaeb600229103cc61d574d57cac320ba84 makes no difference either | |
| 20:30:14 | mriedem | nova meeting in 30 minutes | |
| 20:31:01 | sean-k-mooney | mriedem: looking at https://github.com/openstack/nova-specs/blob/master/tox.ini i dont think we are using the upper constraints in nova-specs | |
| 20:31:17 | mriedem | oh that's right | |
| 20:31:25 | mriedem | and i can't remember why | |
| 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 | 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: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: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. | |