13:31:16 #startmeeting powervm_ci_meeting 13:31:17 Meeting started Thu Dec 15 13:31:16 2016 UTC and is due to finish in 60 minutes. The chair is esberglu. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:31:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:31:20 The meeting name has been set to 'powervm_ci_meeting' 13:31:24 o/ 13:31:36 \o 13:32:36 ymadhavi@in.ibm.com proposed openstack/nova-powervm: Set MTU for the tap device https://review.openstack.org/411317 13:32:53 #topic openstack ci 13:32:56 so I guess - note that we have a hard stop in 28 minutes for the nova meeting 13:33:04 :-) 13:33:58 Yep. And you want the reviews done by then 13:34:20 if possible. I'd like the WIP removed ASAP on the first patch, but I think its held back by reviews 13:34:37 I also asked wangqsh to run it through a devstack on neo-4 or 50 13:34:44 which I know is currently earmarked for CI. 13:35:10 Okay 13:35:18 Tell him neo 4 I still need to reinstall 50 13:35:28 k 13:35:39 Did anyone look at why the first patch failed our CI? 13:35:48 nope. 13:35:56 probably because of namespace overlap 13:36:22 The earlier patches were failing because the driver failed to initialize 13:36:30 I haven't looked at the newer ones yet 13:36:38 k 13:37:39 it actually raises an interesting problem... 13:38:01 the nova proper namespace is not being overridden by the out of tree driver 13:38:11 so it is using the in tree driver. 13:38:26 and of course, we're missing 99% of the function there. 13:38:42 so the patch still needs to be WIP...maybe we need to change the namespace or something. 13:39:35 Link to the logs from the CI run 13:39:37 http://184.172.12.213/88/391288/12/check/nova-pvm-dsvm-tempest-full/f8be969 13:39:37 anyway, besides that...ci looks like it is going well? This other topic needs more discussion. 13:39:53 Yeah CI is great 13:40:24 #topic nova driver 13:41:04 ahh, well if we're talking nova driver... 13:41:12 so any ideas on what we do there? 13:42:53 Yeah, that's a hard one... 13:43:07 we could change the name space in tree to pvm. 13:43:20 I think it leads to a bigger question - how do we decide when a patch should be tested against nova-powervm vs in-tree powervm 13:43:37 it should be tested with both. 13:43:43 Right 13:43:48 Just doubles our CI load 13:43:54 and the series of tests we run against each changes 13:43:59 Mhm 13:44:08 Two lists of tempest tests 13:44:30 yeah...that doesn't worry me too much. One test should be very quick to start... 13:45:43 Right 13:46:23 I kind of don't like the solution of changing the in-tree namespace to pvm from a technical standpoint... but we can't break all our current consumers either 13:46:31 We should look at what the hyper-v guys are doing 13:46:56 adreznec: agree...and I bet their out of tree has a different name. 13:47:03 we could do something silly and make it power_vm 13:47:53 adreznec: mind doing some research on that and see what you think is best? 13:47:54 Right 13:47:56 Sure 13:48:34 cool. 13:49:15 wangqwsh: did you see the note about testing with devstack? 13:49:25 yes, I read it 13:49:47 does it make sense? esberglu was recommending we use neo-dev-4 for that instead of 50 13:49:55 install AIO or AIT? 13:50:08 ok 13:50:26 AIT is easier probably 13:50:31 because the novalinks have small disks 13:50:47 and devstack can consume more than all of it if it is also running the controller 13:50:47 I do not have VMs 13:50:53 lets get you one on jupiter 13:51:08 we can send you link in private message 13:51:34 ok 13:52:57 the idea here is that we just test the function in the WIP patch set 13:54:28 alright. 13:54:32 any other topics? 13:54:35 t-minus 5 min 13:55:05 i am fine. 13:55:13 I don't have anything 13:56:05 I have to drop here to transition to the nova meeting 13:56:07 Back online then 13:56:26 k 13:56:30 end meeting time? 13:57:28 #endmeeting