Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2017-02-16
16:32:43 mriedem sdague: johnthetubaguy: can one of you put this through? https://review.openstack.org/#/c/434552/
16:32:46 mriedem needed for rc2
16:33:13 mriedem dansmith: did you want to get this into docs for rc2 or don't care? https://review.openstack.org/#/c/432482/
16:33:44 frickler BobBall: will do, thanks for checking
16:34:13 dansmith mriedem: I was a little worried with that one that it might be implying that you could upgrade from cellsv1 to cellsv2, but I never articulated that
16:34:26 dansmith mriedem: but yeah, I'm fine with it going into ocata if you want
16:34:56 sdague mriedem: bam!
16:35:12 mriedem sweet
16:35:28 sdague mriedem: so I need to tweak that spec for keystone validation of projects, as the 403 case wasn't really specified well enough
16:35:37 mriedem so anyone else want to help sway me either way on whether or not we should quickly change the default on the xen vif_driver config option to be the ovs driver since neutron is the default now in ocata?
16:35:51 mriedem otherwise the xen vif driver is not correct by default out of the box in a fresh ocata install for xen
16:35:59 mriedem sdague: ok
16:36:35 BobBall I'm perfectly happy for the default to change - I wasn't sure if we could deprecate it (not sure if rax are using for quark)
16:37:04 mriedem BobBall: johnthetubaguy: i'm +2 on https://review.openstack.org/#/c/424428/
16:37:12 mriedem any changes to the default vif_driver config can be a separate change
16:37:22 mriedem BobBall: do you know if rax is even using an in-tree vif driver for xen?
16:37:24 dansmith mriedem: I thought the logo was going to have some hands on it
16:37:40 mriedem i noticed the vif_driver option is a classloading option so you can load out of tree vif drivers for xen
16:37:43 mriedem dansmith: as in the gaping butthole?
16:37:47 mriedem that's only on twitter
16:37:55 dansmith mriedem: yeah, I must have missed where that was downvoted
16:37:57 dansmith ah, maybe so
16:38:29 BobBall mriedem: I know RAX use an out-of-tree VIF driver but I'm not certain if they use vif_driver or have custom patches
16:38:49 mriedem ok, because i'd like to close the out of tree vif driver support in here via the vif_driver option
16:38:56 mriedem and just make the vif driver decision based on use_neutron
16:39:11 mriedem we've been closing that window on lots of other configs
16:39:21 mriedem that would actually allow us to kill the vif_driver option and not use it
16:39:37 mriedem BobBall: you're sure that bridge driver won't work with neutron?
16:40:29 mriedem i won't hold rc2 up for it, anyone using xen i'm sure should already know about this
16:40:29 BobBall mriedem: No. But I'm sure we don't test it with Neutron and I would be quite shocked (or should I say pleasantly surprised?) if it does work. I always considered it to be nova-net only.
16:40:55 mriedem well we know it won't work with live migration and xenserver 7.0 i guess?
16:41:32 BobBall Right.
16:41:58 mriedem i'd kind of like to start the deprecation timer on that option in ocata if possible
16:42:01 mriedem so we don't lose 6 months
16:42:32 mriedem BobBall: who from rax might know what they use?
16:42:37 BobBall Totally agreed - what should we do? Log message if anyone uses the function? Update help on the vif_driver option?
16:42:49 BobBall johnthetubaguy: will know I'm sure - he's just been AWOL for a few hours ;)
16:42:52 mriedem let me post my idea
16:43:16 johnthetubaguy he is here
16:43:38 johnthetubaguy rackspace is neutron, with the quark plugin
16:43:48 BobBall Does you set vif_driver to the quark plugin?
16:43:50 johnthetubaguy uses ovs
16:43:54 BobBall or can we deprecate the vif_driver option in nova?
16:44:13 openstackgerrit Sujitha proposed openstack/nova master: Adding tags field to InstancePayload https://review.openstack.org/407228
16:44:58 johnthetubaguy BobBall: seems fine to me
16:45:07 mriedem heh the config option says this:
16:45:14 mriedem "NOTE: The XenAPIBridgeDriver should be used for running OVS or Bridge in XenServer."
16:45:22 mriedem i guess that's totally wrong?
16:45:47 BobBall heh... Indeed.
16:47:01 BobBall frickler: There was a new tempest test added which made use of floating IPs. I've excluded it now. Please re-check.
16:50:09 BobBall mriedem: sorry for the sadness in the XenServer CI - as mentioned to frickler above, we have identified the probable cause for the ssh timeouts (we had two neutron agents with the same hostname - which meant sometimes the wrong agent was picked for something or other...). A fix was made today, but further investigation is being done to prove it doesn't break secure groups (there was some suggestion yesterday it might, but today we believe it won't).
16:50:35 mriedem BobBall: that's fine, i know it's not failing on this patch
16:51:56 BobBall Indeed. There are many false negatives today - but rechecks should fix them now. Hopefully we'll have the proper fix in the CI early next week and we will re-enable these tests.
16:53:44 openstackgerrit Sean Dague proposed openstack/nova master: WIP: verify project_id when quotas are checked https://review.openstack.org/435010
16:54:05 sdague mriedem: that kind of works, no tests, I'll update the spec with the differences
16:57:50 mriedem BobBall: changing the default vif driver causes all sorts of unit test failure of course
16:59:03 BobBall mriedem: would it be enough to add help text in the vif driver, a release note and a log message when loading the deprecated one stating that it is deprecated? Then I can change the default, fix the UT and remove the old one in Pike?
16:59:42 mriedem yeah i think i'm going to leave the default and mark the option deprecated for pike - we could also just hack the tests to use the bridge driver to pass for now
16:59:49 mriedem i'm trying to find a spot to do that
16:59:59 openstackgerrit Sean Dague proposed openstack/nova-specs master: Updates for validation spec based on implementation https://review.openstack.org/435016
17:00:04 sdague mriedem: ^^^
17:03:27 cfriesen for nova microversion 2.42 is there going to be any work required in novaclient?
17:04:38 mriedem cfriesen: it's a bug fix, andreykurilin had a patch
17:04:56 mriedem https://review.openstack.org/#/c/424745/
17:06:06 andreykurilin mriedem: also there is a patch for 2.42 - https://review.openstack.org/#/c/429512/ . I suppose we need to merge 424745 change with 429512
17:06:08 mdbooth bauzas: https://github.com/openstack/nova/blob/master/nova/compute/resource_tracker.py#L1049-L1053
17:06:33 mdbooth bauzas: That's the info that eventually ends up in the scheduler, right?
17:06:44 mriedem BobBall: got a workaround for the tests, pushing the change up shortly
17:07:01 BobBall Ah awesome - I was just looking into that.
17:07:12 mdbooth If so, I think the bug is that it should be looking at bdms, otherwise it doesn't know the actual sizes (or existence) of the root and ephemeral disks
17:07:18 mdbooth Also, it takes no account of swap
17:07:27 mdbooth Or kernel/ramdisk
17:07:44 mdbooth bauzas: Can you sanity check^^^?
17:09:09 cfriesen mriedem: andreykurilin: thanks, was hoping someone had done it since I'm proposing a change for 2.43. :)
17:10:21 andreykurilin cfriesen: unfortunately, I'll not have an ability to finish my change till March :(
17:11:45 cfriesen andreykurilin: okay. I see your change handles the fact that tags don't work for certain versions...what about handling the fact that they should work again as of 2.42?
17:12:12 andreykurilin cfriesen: it should be handled here - https://review.openstack.org/#/c/429512/
17:15:20 cfriesen andreykurilin: right, so now you accept 2.42. but doesn't the change at https://review.openstack.org/#/c/424745 mean that we won't use it?
17:15:36 cfriesen won't use tags, I mean, even though they're supported on the server side
17:16:39 andreykurilin cfriesen: change 424745 should clarify situation for microversions <2.42 . The change 429512 should return support of tags with 2.42
17:18:08 cfriesen 429512 would work standalone because it's assuming "there are no version-wrapped shell method changes for this". However, change 424745 introduces a version-wrapped change.
17:18:53 cfriesen so if one goes in first the other one has to be reworked to account for it otherwise tags won't work for version 2.42. (I think, anyway. I could be wrong.)
17:24:12 openstackgerrit Matt Riedemann proposed openstack/nova master: Deprecate xenserver.vif_driver config option and change default https://review.openstack.org/435037
17:24:19 mriedem BobBall: johnthetubaguy: ^
17:24:29 mriedem dansmith: sdague: ^ let me know if you think that's wacky
17:24:35 mriedem but i kind of want to get that into ocata to set the timer
17:27:09 sdague mriedem: I'd be fine with it. I think that given the lower level of xenserver usage, things like that can move a bit more nimbly
17:27:20 dansmith mriedem: why is it whacky?
17:27:22 cfriesen andreykurilin: mriedem: would it make sense to push https://review.openstack.org/#/c/429512 for Ocata so that the client/server match up on their max version support? Then we can go back and fix up the intermediate versions where tags were broken.
17:27:26 dansmith er, wacky.. heh
17:27:33 mriedem dansmith: just b/c i want to get it into ocata
17:27:37 mriedem not really wacky
17:28:01 mriedem cfriesen: huh?
17:28:04 dansmith seems decidedly unwacky to me
17:28:12 mriedem cfriesen: novaclient is frozen for ocata
17:28:16 mriedem except for backporting fixes
17:28:47 sdague BobBall: mriedem: why is this failing xenserver ci? - https://review.openstack.org/#/c/424428/12
17:29:11 cfriesen mriedem: so we have nova with max version 2.42 but novaclient with 2.41?
17:29:38 mriedem sdague: everything is
17:29:39 cfriesen mriedem: and no way to make use of the fact that 2.42 fixes tags?

Earlier   Later