Tuesday, 2017-01-17

*** seroyer has quit IRC00:01
*** thorst has joined #openstack-powervm00:19
*** tjakobs has quit IRC00:19
*** thorst has quit IRC00:21
*** efried has quit IRC00:35
*** efried has joined #openstack-powervm00:47
*** svenkat has joined #openstack-powervm01:11
*** YuYangWang has quit IRC01:14
*** thorst has joined #openstack-powervm01:22
*** thorst has quit IRC01:27
openstackgerritSridhar Venkat proposed openstack/nova-powervm: WIP: Migration scenario, SR-IOV vif contains source physical ports  https://review.openstack.org/41247401:42
*** thorst has joined #openstack-powervm01:42
*** thorst has quit IRC01:43
*** svenkat has quit IRC02:00
*** thorst has joined #openstack-powervm02:44
*** thorst has quit IRC02:48
*** tjakobs has joined #openstack-powervm03:19
*** edmondsw has joined #openstack-powervm03:31
*** edmondsw has quit IRC03:36
*** thorst has joined #openstack-powervm04:45
*** thorst has quit IRC04:50
*** tlian has quit IRC04:50
*** nbante has joined #openstack-powervm04:56
*** kylek3h has quit IRC05:46
*** kylek3h has joined #openstack-powervm05:46
*** kylek3h has quit IRC05:51
*** Sujeet_ has joined #openstack-powervm06:27
*** tjakobs has quit IRC06:29
*** thorst has joined #openstack-powervm06:46
*** kylek3h has joined #openstack-powervm06:47
*** thorst has quit IRC06:50
*** kylek3h has quit IRC06:51
*** thorst has joined #openstack-powervm08:47
*** thorst has quit IRC08:52
*** thorst has joined #openstack-powervm10:48
*** thorst has quit IRC10:52
*** XiaYan has joined #openstack-powervm10:56
*** xia has joined #openstack-powervm10:56
*** nbante has quit IRC11:49
*** Cartoon has joined #openstack-powervm12:02
*** Sujeet_ has quit IRC12:03
*** seroyer has joined #openstack-powervm12:35
*** smatzek has joined #openstack-powervm12:36
seroyerBorD__ I got an answer.  They weren't real happy with the idea and strongly recommend you figure out the depenecy issue instead.  But here you go: http://pastebin.com/VDXVEPXL12:41
*** thorst has joined #openstack-powervm12:46
*** esberglu has quit IRC12:49
*** jwcroppe has joined #openstack-powervm12:59
*** chmod666org has quit IRC13:02
*** chmod666org has joined #openstack-powervm13:03
*** edmondsw has joined #openstack-powervm13:03
*** tblakes has joined #openstack-powervm13:07
*** svenkat has joined #openstack-powervm13:14
*** sujeet_ has joined #openstack-powervm13:20
*** esberglu has joined #openstack-powervm13:40
*** apearson has joined #openstack-powervm13:49
*** nbante has joined #openstack-powervm13:50
*** wangqwsh has joined #openstack-powervm13:52
*** kylek3h has joined #openstack-powervm13:59
esberglu#startmeeting powervm_driver_meeting14:00
openstackMeeting started Tue Jan 17 14:00:03 2017 UTC and is due to finish in 60 minutes.  The chair is esberglu. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
openstackThe meeting name has been set to 'powervm_driver_meeting'14:00
efriedadreznec thorst14:01
esberglu#topic Status14:02
xiaHi all, it's my first time to join this meeting, I'm Yan Xia,wangqw's team member14:02
thorsthey xia!14:03
xiaThanks!Glad to meet you all!14:03
esbergluAnyone have status? I'm still a bit out of the loop for where we are on this14:03
efriedI'll do a quick summary of the in-tree driver work.14:04
efriedWe have four change sets out there.14:04
efriedhttps://review.openstack.org/391288  https://review.openstack.org/409401  https://review.openstack.org/409402  https://review.openstack.org/40940414:04
efried...in that order.14:04
thorstefried: we still need a vif one to be seeded?14:05
efriedThe first one is _almost_ ready to go.  I'm working on a few tweaks suggested by thorst.14:05
efriedYes, I think we could start a vif change set and an SSP change set in parallel.14:05
nbanteHi, I am Nilesh Bante..I am joining this meeting first time14:05
efriedWelcome nbante14:05
thorstnbante will be helping with testing OSA for PowerVM  :-)14:06
efriedThe vif and SSP change sets could be a good thing for wangqwsh and xia to get started on.14:06
thorstefried: the vif one needs a little bit of research14:06
efriedwangqwsh and xia, do you have systems to test on?14:06
thorstbecause we need to understand where 'os-vif' is in core nova.14:06
wangqwshi have neo414:06
efriedthorst: start with OVS?14:06
thorstwell, yeah, but more importantly, do we do OVS as we have out of tree14:07
thorstor has ocata changed the 'vif' model a bit14:07
thorstI guess initially, lets move in what we have, and I'll do some os-vif research14:07
efried#action thorst to research the status of os-vif in core nova14:08
efriedwangqwsh, xia - y'all good with starting on OVS and SSP change sets?14:08
thorstto clarify, two separate change sets.  To copy/paste in the code for the vif/ssp logic from the out of tree into the in-tree driver.  But only port over the stuff we need specific to those14:09
thorstwe're trying to create very small change sets for the nova team to review14:09
thorstbut at the same time keep it in sync with our out-of-tree driver14:10
efried#action wangqwsh and xia to seed next two change sets: 1) PlugVifs and supporting code for OVS only; 2) SSP disk driver and supporting code.14:10
*** mdrabe has joined #openstack-powervm14:10
efriedLet me know if you need help/guidance there.14:10
thorstefried: I'm assuming we hold off on the in-tree CI discussion till later part of meeting?14:10
efriedI wrote the SSP driver, so I'm pretty familiar with it; thorst did the OVS work, so he's the SME.14:10
efriedthorst: sure, fine with me.14:11
efriedOne more note on status:14:11
wangqwshi will try to read the code first. any issue i will let you know.14:11
efriedAs we get code reviews on the ported code, some changes/fixes/improvements need to be flushed back to nova-powervm.  That's what I've been working on while fixing up the first in-tree change set.14:12
efriedOne of the things we're trying to avoid in the in-tree driver is unit tests that dig too deeply into pypowervm.14:12
efriedAmong other things, this means that wherever we're using pypowervm's test data files, we need to convert over to using plain ol' mocks instead.14:13
BorD__seroyer thanks a ton!  things got wonky after upgrading rpm to the version that works with yum..14:13
efriedAlso be on the lookout for places where we're validating pypowervm lib functions - those should be replaced with mock.patches of the pypowervtm lib methods instead.14:14
efriedSometimes we can let the pypowervm methods run, but only if we don't have to do a bunch of extra mocking and coercion in the UT to make them "work".14:14
efriedAny questions for now?14:15
thorstagree with that.  No Questions14:15
efriedesberglu: next topic?14:15
esbergluWhat else do you guys want to talk about?14:16
efriedIf you don't have anything else queued up, we can get into the dual-CI business.14:16
efried#topic CI for in-tree driver14:17
efriedSo the challenge here is that the in-tree driver has a tiny subset of the functionality we're testing in our existing CI.14:17
efriedWe can't stop testing the out-of-tree driver14:17
esbergluSo we want a second set of tests whitelisted for the in tree14:18
efriedbut we need to be able to show a passing CI for the in-tree driver before we can expect to merge it  (per nova core direction, and common sense)14:18
efriedYes, we'll need a separate environment to test in-tree.  It'll involve both a whitelist for the tests around the functionality we have, and a separate conf setup to load up and configure the in-tree driver properly.14:19
efriedThat env will have to proceed in lock-step with the change sets as they merge.14:19
thorstI want to be clear14:19
thorstIt won't be a separate environment14:19
efriedSo right now, it needs to be set up to target just the first (spawn/delete) change set (https://review.openstack.org/391288)14:19
thorstit'll be a different VM in the existing CI environment14:19
thorstwhich runs a different setup/test job14:20
thorstso if nova has a patch, we kick off two jobs.  One out of tree, one in tree.14:20
efriedOnce that change set merges, we'll need to modify the conf & whitelist to support the second.  And so on.14:20
thorstefried: that whitelist needs to be flexible14:21
efriedthorst: what do you mean?14:21
thorstbecause you'll be working on change set 3, then need to make a rev on change set 1.14:21
esbergluAre you saying we want 2 types of ready nodes? Or just one type of ready node with diff. config and setup after14:21
thorstesberglu: one ready node...two different jobs14:21
esbergluOkay good14:21
thorstone "type" of ready node14:21
efriedSure, the whitelist will need to keep up with change set 1 - but I don't see us trying to maintain whitelists for multiple in-flight change sets at once.14:22
thorstefried: fair enough...we'll see how that goes14:22
efriedI mean, we _could_ try to do that - but the CI infra would have to keep a mapping of change sets to conf/whitelists.  That would be complicated, and probably not worth the trouble.14:23
*** tlian has joined #openstack-powervm14:23
thorstlets start with easy14:23
thorstmove up from there14:23
efriedAt any given point, the setup should still pass for all in-flight change sets.  But we can't add new tests until a change set merges.14:24
thorstesberglu: priority wise, this second CI is probably right after getting our main CI up and running again14:24
efriedThat and core reviews are the last inhibitor to getting the first change set merged (once I've put up the last patch set with thorst's suggested changes).14:25
esbergluMain CI pretty much is up and running, just was failing on those 2 tests added to the skip list14:25
efriedNow, is it going to be easier to fix the CI as-is, and then do the split, or do both at once?14:25
esbergluSo I can start looking into the 2nd CI today14:25
efriedokay, I guess you answered that.14:25
efried#action esberglu to start work on the split-CI14:26
efriedAnything else on CI for now?14:26
thorstI'd like a status update with the main CI14:26
efried#topic Main CI status14:27
esbergluIt seems to be working pretty well. I upgraded to zuul 2.5.1 yesterday, 2.5.0 was missing a change and was causing issues14:27
efriedare we passing?14:28
esbergluThere were 2 tests that were failing and got added to the skip list. Pretty much every failure I saw yesterday was just those 214:28
esbergluA run hasn't finished since the skip list change merged14:28
efriedAre the two tests appropriate to skip, or do they need to be investigated for possible code fixes?14:28
esbergluNot supported14:28
thorstappropriate to skip14:29
thorstare we working in parallel getting the staging environment up and running?14:29
efriedDo we have some way of knowing when new tests are added so we can maybe be proactive about skipping unsupported stuff?14:29
esbergluthorst: I was going to deploy staging this morning. I really want to get us back on the latest devstack master, the longer we wait on that the more difficult its going to be14:30
esbergluSo I was going to hit staging with that while I start working on the code for the 2nd CI14:30
thorstesberglu: before you chase that, could you try out that DNS server that adreznec set up?14:31
thorstI'd love to just knock that out.14:31
esbergluadreznec: Is that change set ready? I still need to look through it14:31
adreznecesberglu: Yeah, like I said the client-side changes to actually set clients to use the DNS mirror/apt cache aren't tested14:32
thorstadreznec in/14:32
adreznecBut it's ready for review/testing anyway14:33
thorstso ready for staging14:33
adreznecThere might be some wonkiness in the variables we need to handle14:33
esbergluOkay. I will deploy with that as well then14:33
adreznecIf we're going to share one between staging and prod14:33
thorstesberglu: we're thinking that can dramatically speed up CI runs14:33
thorstmaybe another 10-20 min14:33
esberglu#action esberglu: Test dns / apt on staging environment14:33
esbergluThat would be sweet14:33
adreznecThough I suppose we could have it such that in staging it just installs those things onto the management nodes14:34
thorstyeah, and make it more stable...14:34
adreznecSince the management node isn't getting a lot of volume there14:34
esbergluLet's see what happens when I deploy and go from there?14:36
esbergluAnything else for CI?14:37
thorstnot from my end.14:37
adreznecSure. Was just a heads up that it might not work right out of the box14:37
esbergluOther topics?14:38
esbergluBtw, the first run with the new skip list just went through and passed14:38
efriedDo we have some way of knowing when new tests are added so we can maybe be proactive about skipping unsupported stuff?14:38
esbergluI can look into it14:39
efriedCool.  Low priority, below other stuff above.14:39
esberglu#action: esberglu: Find a way to get notified of new tempest tests14:39
esbergluefried: thorst: I think you guys wanted further discussion on the in-tree driver?14:41
efriedI think that was the split-CI discussion14:41
esbergluOh okay14:41
esbergluAnything final topics before I end the meeting?14:42
thorstjust one future facing thing14:42
thorstwe're going to need to start looking at supporting that fileio disk/volume connector14:42
thorstI'm trying to figure out who/how we do that...but I don't think it'll be too tough TBH14:42
thorstprobably start with cinder.14:42
thorsttarget will be pike14:43
efriedneed a bp?14:44
thorstout of tree bp though14:45
esbergluAlright looks like that covers it. Thanks for joining14:48
thorstthat's all I had14:48
openstackMeeting ended Tue Jan 17 14:49:03 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2017/powervm_driver_meeting.2017-01-17-14.00.html14:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2017/powervm_driver_meeting.2017-01-17-14.00.txt14:49
openstackLog:            http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2017/powervm_driver_meeting.2017-01-17-14.00.log.html14:49
*** wangqwsh has quit IRC15:02
*** burgerk has joined #openstack-powervm15:19
*** tjakobs has joined #openstack-powervm15:33
*** mdrabe has quit IRC15:49
*** burgerk has quit IRC15:54
*** mdrabe has joined #openstack-powervm16:00
*** sujeet_ has quit IRC16:07
*** xia has quit IRC16:22
*** burgerk has joined #openstack-powervm16:26
*** XiaYan has quit IRC16:27
openstackgerritSridhar Venkat proposed openstack/nova-powervm: WIP: Migration scenario, SR-IOV vif contains source physical ports  https://review.openstack.org/41247416:45
*** smatzek has quit IRC16:48
*** smatzek has joined #openstack-powervm16:50
openstackgerritTaylor Jakobson proposed openstack/nova-powervm: First pass at imagecache  https://review.openstack.org/40875817:02
openstackgerritTaylor Jakobson proposed openstack/nova-powervm: First pass at imagecache  https://review.openstack.org/40875817:10
*** seroyer has quit IRC17:39
*** seroyer has joined #openstack-powervm17:54
openstackgerritSridhar Venkat proposed openstack/nova-powervm: Migration scenario, SR-IOV vif contains source physical ports  https://review.openstack.org/41247418:16
*** smatzek has quit IRC18:16
*** nbante has quit IRC18:54
openstackgerritEric Fried proposed openstack/nova-powervm: Mock data cleanup 1  https://review.openstack.org/42144819:01
efriedthorst: We now have pypowervm on pypi.19:10
efriedI would like to update the global requirements, but we'll have to justify it: http://git.openstack.org/cgit/openstack/requirements/tree/README.rst#n32719:10
efriedCan we point to any show-stopping differences from .3.9?19:10
thorstefried: I can't19:18
thorstso lets stick with for now...19:18
efriedk, I guess we wait til the in-tree driver breaks on somethnig.19:18
thorstfair enough19:19
adreznecefried: Hmm... well I guess it depends where we want to go. If we want to say things like SR-IOV support, etc19:19
adreznecOh wait19:19
adreznecI think iSCSI is broken in
adreznecand there are the upload bits as well thorst19:20
adreznecThat aren't in there19:20
thorstwe don't use iSCSI yet.19:20
thorstbut true.19:20
adreznecwas just thinking of major items19:20
efriedibmi console...19:21
thorstthat was in
adreznecCan we just update it on the grounds that the version number is evil?19:22
adreznecI think this is the diff https://github.com/powervm/pypowervm/compare/cba2106c107f23165bdc3ab02064a35d9f1152ee...release/
efriedPCI device ID (whatever that is)19:24
efriedI don't see SR-IOV differences.19:25
efriedadreznec: you and your fancy URLs.  I downloaded the tarballs and diff'd 'em.19:25
efriedthorst: in response to your comment about exceptions: There's 20 in the oot driver, including a couple of abstracts (we can probably get rid of one of those).19:29
efriedNo other driver seems to have its own exception classes, so I guess we should probably look toward adding them to the main one.19:30
*** Cartoon has quit IRC19:31
thorstefried: agree.19:32
efriedThat said, I only find one nova exception that mentions a specific driver.19:32
*** apearson has quit IRC20:01
*** apearson has joined #openstack-powervm20:03
thorstefried: something up with ut's?20:16
thorstall these change sets I'm seeing proposed are failing ut....20:16
efriedwhich ones?20:16
thorstbut I think its just people not running tox on their code20:16
thorstand not real problems20:16
thorstyeah, verified...your stuff is clean and prestine20:16
efriedIt does look like core nova moved some stuff around recently, which could be causing issues.  At least I believe that's the problem with svenkat's20:17
svenkatefried: I figured the problem… upadting UT code. I was mocking wrong API class.20:18
openstackgerritMerged openstack/ceilometer-powervm: Update to match latest global-requirements  https://review.openstack.org/41861820:27
*** tjakobs has quit IRC20:29
*** tjakobs has joined #openstack-powervm20:33
*** apearson has quit IRC20:37
*** apearson has joined #openstack-powervm20:39
openstackgerritSridhar Venkat proposed openstack/nova-powervm: Migration scenario, SR-IOV vif contains source physical ports  https://review.openstack.org/41247420:44
efriedthorst: https://review.openstack.org/#/c/421515/20:49
efried(global requirements update)20:49
openstackgerritEric Fried proposed openstack/nova-powervm: Mock data cleanup 1  https://review.openstack.org/42144820:56
thorstadreznec: did we ever merge the bp for the image cache?21:35
thorstI don't think we did...21:35
adreznecI don't think so21:35
adreznecKind of forgot about it21:35
thorstyeah...I ask because I'm starting on this bp21:37
adreznecWell we should clean it up and merge it then I guess21:50
adreznecand probably be more diligent in the future21:50
*** thorst has quit IRC21:59
openstackgerritTaylor Jakobson proposed openstack/nova-powervm: BP: Add image cache to nova-powervm  https://review.openstack.org/37194622:01
*** svenkat has quit IRC22:04
*** burgerk has quit IRC22:09
*** thorst has joined #openstack-powervm22:24
*** thorst has quit IRC22:24
*** seroyer has quit IRC22:24
*** seroyer has joined #openstack-powervm22:24
*** tblakes has quit IRC22:30
openstackgerritEric Fried proposed openstack/nova-powervm: BP: Add image cache to nova-powervm  https://review.openstack.org/37194622:32
*** tlian has quit IRC22:34
*** edmondsw has quit IRC22:42
*** thorst has joined #openstack-powervm22:46
*** thorst has quit IRC22:53
*** dwayne__ has quit IRC22:58
*** tlian has joined #openstack-powervm22:58
*** mdrabe has quit IRC23:00
*** seroyer has quit IRC23:25
*** edmondsw has joined #openstack-powervm23:25
*** edmondsw has quit IRC23:30
*** apearson has quit IRC23:31
openstackgerritTaylor Jakobson proposed openstack/nova-powervm: First pass at imagecache  https://review.openstack.org/40875823:37
*** tjakobs has quit IRC23:42
*** esberglu has quit IRC23:44
*** esberglu has joined #openstack-powervm23:45
*** esberglu has quit IRC23:49

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!