Tuesday, 2016-11-15

*** thorst has joined #openstack-powervm00:07
*** esberglu has quit IRC01:01
*** seroyer has joined #openstack-powervm01:13
*** svenkat has joined #openstack-powervm01:18
openstackgerritEric Berglund proposed openstack/nova-powervm: DNM: ci check  https://review.openstack.org/32831501:22
*** thorst has quit IRC01:40
*** thorst has joined #openstack-powervm01:41
*** thorst has quit IRC01:49
*** thorst has joined #openstack-powervm02:17
*** mdrabe has quit IRC02:21
*** thorst has quit IRC02:27
*** thorst has joined #openstack-powervm02:28
*** thorst has quit IRC02:36
*** thorst has joined #openstack-powervm02:58
*** thorst has quit IRC03:03
*** seroyer has quit IRC03:04
*** thorst has joined #openstack-powervm03:04
*** jwcroppe has quit IRC03:05
*** jwcroppe has joined #openstack-powervm03:05
*** seroyer has joined #openstack-powervm03:06
*** jwcroppe has quit IRC03:06
*** jwcroppe has joined #openstack-powervm03:08
*** apearson has joined #openstack-powervm03:11
*** thorst has quit IRC03:12
*** seroyer has quit IRC03:15
*** thorst has joined #openstack-powervm04:10
*** chas_ has joined #openstack-powervm04:13
*** chas_ has quit IRC04:17
*** thorst has quit IRC04:17
*** apearson has quit IRC04:52
*** thorst has joined #openstack-powervm05:17
*** thorst has quit IRC05:23
*** chas_ has joined #openstack-powervm05:36
*** chas_ has quit IRC05:40
*** thorst has joined #openstack-powervm06:21
*** thorst has quit IRC06:28
*** svenkat has quit IRC07:01
*** chas_ has joined #openstack-powervm07:07
*** YuYangWang has joined #openstack-powervm07:18
*** thorst has joined #openstack-powervm07:26
*** thorst has quit IRC07:33
*** k0da has joined #openstack-powervm07:38
*** thorst has joined #openstack-powervm08:32
*** thorst has quit IRC08:38
*** YuYangWang has quit IRC08:50
*** openstackgerrit has quit IRC09:18
*** openstackgerrit has joined #openstack-powervm09:18
*** thorst has joined #openstack-powervm09:35
*** thorst has quit IRC09:43
*** k0da has quit IRC10:01
*** thorst has joined #openstack-powervm10:41
*** thorst has quit IRC10:48
*** smatzek has joined #openstack-powervm11:47
*** thorst has joined #openstack-powervm11:47
*** smatzek has quit IRC11:49
*** thorst has quit IRC11:53
*** seroyer has joined #openstack-powervm12:26
*** thorst has joined #openstack-powervm12:56
*** k0da has joined #openstack-powervm13:17
*** edmondsw has joined #openstack-powervm13:18
*** svenkat has joined #openstack-powervm13:21
thorstadreznec: I'm going to be spotty for our CI meeting today.13:36
*** jwcroppe has quit IRC13:47
*** chas_ has quit IRC13:52
*** chas_ has joined #openstack-powervm13:52
*** chas__ has joined #openstack-powervm13:54
*** wangqwsh has joined #openstack-powervm13:56
*** chas_ has quit IRC13:56
*** esberglu has joined #openstack-powervm14:01
*** apearson has joined #openstack-powervm14:01
thorstFYI - we're going to start the CI meeting a little late14:02
thorstesberglu wangqwsh: ^^14:02
thorstefried1: ^^14:03
wangqwshyes14:03
esbergluOkay14:03
*** tblakes has joined #openstack-powervm14:03
efried1okay14:04
adreznecAll right14:05
adreznecIt looks like we're all in the room, so why don't we get things started14:05
adreznec#startmeeting PowerVM Driver Meeting14:06
openstackMeeting started Tue Nov 15 14:06:23 2016 UTC and is due to finish in 60 minutes.  The chair is adreznec. Information about MeetBot at http://wiki.debian.org/MeetBot.14:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:06
openstackThe meeting name has been set to 'powervm_driver_meeting'14:06
adreznecHelps if I use the right command14:06
adreznec#topic Current status14:06
adreznecAll right, so let's start with the upstream driver related topic14:07
adreznecNow that the blueprint is approved/spec merged, efried1 has taken the WIP off all of this change sets14:07
thorstwooo14:08
adreznecOur global requirements patch for pypowervm has a +1 from Jenkins, but needs responses to the requirements team questions14:08
thorstand our very sensible version number is going splendidly14:08
adreznecYes14:08
adreznecWe'll call it semver++14:08
adreznecOne + for each additional digit14:08
efried1For the record, I tried to produce the upper-constraints patch using the process outlined in the README.  Never got it to work.14:09
* adreznec grumbles off in the background14:09
efried1Hence typo14:09
efried1Didn't figure it was rocket science.  And it's not.  I'm just a doofus.14:09
efried1I'll take care of that questionnaire this morning.14:09
adreznecWas an easy fix anyway, and it means our very excellent versioning scheme can stay intact14:10
efried1#action efried to update requirements change set per comments.14:10
efried1#action efried1 to update requirements change set per comments.14:10
efried1(I guess I'm efried1 since the last time my laptop crashed)14:10
thorstI can't wait for efried214:10
efried1Me neither.14:10
efried1What's next.14:10
adreznecDo we need action on any of the other patches yet?14:10
thorstCI stability?14:11
efried1oh, hold on,14:11
efried1let's talk a little bit about Tony's comment.14:11
efried1Do we respond to it in the change set (and attempt to explain the IBM legal reasons we don't use semver)?14:11
adreznecI'm... not sure it matters either way?14:12
efried1Or maybe something flippant like, "yeah, we don't like it either, but there's a good (if boring) reason for it"14:12
efried1or just ignore it.14:12
adreznecI mean it's definitely awful14:12
adreznecBut I'm not sure it's actually a big deal to anyone at the end of the day14:12
adreznecBesides me14:12
efried1I'm just talking about for the sake of responding to Tony's comment.14:13
*** mdrabe has joined #openstack-powervm14:13
efried1<silence>14:13
adreznecI don't think it really matters as long as we can answer all the other questions14:13
efried1Roger that.14:13
adreznecFrom the questionnaire14:14
thorstyeah, I'm not sure its a big deal.  I'm OK saying 'we don't really like it either'...but I'm not sure we need to make it a big deal14:14
adreznecRight14:14
thorstI think its a bigger deal to us than them14:14
efried1The other thing on current patch sets: do we want to preserve the nova-powervm versioning history on the live migrate data object, or start it at 1.0 in nova proper?14:14
adreznecWe can just say Watson designated the version14:14
adreznecAnd leave it at that14:14
adreznec:P14:14
efried1(see comment: https://review.openstack.org/#/c/391284/3/nova/objects/migrate_data.py@30114:14
efried1)14:14
thorstefried1: I can respond there if you'd like14:15
thorstI'm sure they don't know the history of us being out of tree14:15
thorstbut that's why14:15
efried1So we do want to preserve our out-of-tree version history.14:16
thorstit simplifies the transition14:16
efried1Right, for people currently using the out-of-tree driver.14:16
thorstfor operators14:16
adreznecTo an extent, yeah14:16
adreznecI guess it depends on if we ever want to support anyone migrating from the out-of-tree driver to the in-tree driver14:17
efried1Heck, maybe we should even bump it up to 1.214:17
efried1or 1.1.0.0.914:17
adreznec+214:17
adreznecI guess we can respond with a comment saying we'd like to preserve it for ops14:18
adreznecAnd if they push back we can talk about the implications of that14:18
adreznecSeem reasonable thorst efried1?14:19
thorstyep14:19
efried1So14:19
efried1#action thorst to respond to https://review.openstack.org/#/c/391284/3/nova/objects/migrate_data.py@30114:19
efried1?14:19
adreznecSo it would seem14:20
adreznecAll right14:20
efried1Okay.  The last thing would be socializing the driver skeleton change set.14:20
efried1I'm still not clear how that's supposed to happen normally.14:20
efried1Guess we're not in a super hurry to get that merged until we have CI stable.  Next #topic?14:21
adreznecSo I think we need to talk with the Nova cores about whether we should be on that subteam priority reviews list now14:21
thorstsorry - afk for a bit.14:21
efried1adreznec, I don't know what that is.14:22
adreznecand list our 'top 5' reviews there like the other driver teams are14:22
adreznecLet me dig that up quick14:22
adreznecLike this: https://etherpad.openstack.org/p/ocata-nova-priorities-tracking14:23
efried1Oh, for sure.14:24
adreznecBasically whether or not we should have a PowerVM Subteam section on there where we start listing these reviews14:24
adreznecWe should bring this up in the next Nova meeting then14:24
*** chas__ has quit IRC14:24
efried1Sounds like a good plan.14:24
adreznec#action adreznec thorst and efried1 to bring up PowerVM subteam/reviews in the next Nova meeting14:25
*** chas_ has joined #openstack-powervm14:25
adreznecOkay14:25
adreznec#topic Priority reviews14:25
adreznecDo we have anything open that needs code review priority?14:25
efried1There's nothing on my radar in the community.14:26
adreznecFYI for the team - until https://review.openstack.org/#/c/396934/ merges, multi-architecture deploys are broken14:26
adreznecBut that already has +2/+1s this morning14:26
adreznecSo just awareness14:26
adreznecAll right14:26
adreznecSounds like nothing high priority14:26
adreznec#topic Priority bugs/defects14:27
adreznecSame thing here - any key issues people want to direct attention to?14:27
efried1Other than the CI, nothing I'm aware of.  thorst may have something.14:27
efried1Can we move on to CI?  That could be a substantial discussion.14:28
adreznecYep14:28
esbergluOk14:28
adreznec#topic CI discussion14:28
adreznecesberglu: efried1, it's all yours14:28
efried1esberglu, what's the latest?14:28
esbergluSo amartey thinks that upgrading novalink *may* fix the LUs hanging around after the runs14:29
esberglu#action esberglu update novalink in CI env14:29
esbergluAs far as the actual runs14:29
adreznecUpgrading it to what?14:29
adreznecLatest 1.0.0.4? Latest dev?14:29
*** esberglu has quit IRC14:30
*** esberglu has joined #openstack-powervm14:30
wangqwshhowever, i found 183 can not retrieve vm info14:30
*** chas_ has quit IRC14:30
esbergluSorry I got disconnected. Latest 1.0.0.414:30
adreznecOk14:30
adreznecWell I guess we can give it a shot14:31
esbergluI put the latest versions of the patches from efried on yesterday afternoon14:31
esbergluBut still not working14:31
esbergluI let one run through last night14:31
esbergluhere are the logs14:31
esbergluhttp://184.172.12.213/15/328315/19/check/nova-powervm-pvm-dsvm-tempest-full/9564270/14:31
esbergluStill not finding any valid hosts for many of the tests14:32
esbergluI haven't dug into the logs yet from that run14:32
efried1#action efried1 esberglu to analyze http://184.172.12.213/15/328315/19/check/nova-powervm-pvm-dsvm-tempest-full/9564270/14:33
efried1We may be at a point where we should put all hands on deck until the CI is stabilized.14:34
efried1Throwing more people at it doesn't help the runs themselves finish faster.  But having all eyes on the results right away...14:34
adreznecYeah, I know people are getting pulled in a number of directions right now14:35
adreznecMaybe even just a one day sprint14:35
adreznecFocused on CI improvements could help14:36
adreznecUnfortunately the holiday season is starting to creep up on us14:36
adreznecSo finding availability could be tricky14:36
esbergluYeah I'm out starting friday through all of thanksgiving week. No internet Friday to Wednesday14:37
adreznecAll right. I guess we'll have to table that discussion for now and discuss it outside the meeting14:38
adreznecSo what else do we have on CI?14:38
efried1Seems service nova-compute on host powervm-ci-powervm-devstacked-25844 is down. Last heartbeat was 2016-11-15 01:54:39. Elapsed time is 126.1495714:39
efried1Looks like the compute service died at some point in there.14:39
thorstbtw - I 100% agree that we need an all hands on deck for CI14:39
efried1Compute log has no interrupt or anything - it just stops.14:39
adreznecWell that would certainly explain issues finding a host14:39
thorstdoes it just stop because we hit 5 hours?14:40
thorstand zuul just shut it down14:40
esbergluNo the run went through in like 40 minutes14:40
esbergluIt went super fast because it couldn't find any hosts14:40
thorsto14:40
thorsthuh14:40
efried12016-11-14 19:54:43.560 is the last time stamp in the compute log.14:40
esbergluThe 5 hour runs happen when it times out waiting for hosts to become active (which we are past at this point I believe)14:41
esbergluSo should I let another run through? Maybe the host dying was just a one-off thing?14:42
thorstesberglu: the 5 hour thing happens when we wait for the marker LU14:42
thorstwhich we *may* be past, hopefully14:43
thorstjust needed an uber clean of the env14:43
esbergluYeah and efrieds latest patch14:43
thorstright.14:43
thorstwe also need the novalinks updated14:43
thorstdid you see that from apearson?14:43
esbergluYep14:44
esberglualready did an action for it14:44
thorstso are those the immediate next steps?14:44
adreznecYep14:44
adreznecAlready had the novalink upgrade as an action14:44
thorstthen all hands on deck for the next run to debug14:44
adreznec#action esberglu to try another CI run with latest patch and report results14:45
adreznecOk14:45
adreznecAnything else on the CI front?14:45
esbergluI think wangqwsh was hitting some OSA CI stuff?14:45
wangqwshyes,14:46
wangqwshthe memory is extended to 12g, galera can work.14:46
wangqwshbut it's failed to boot a vm.14:46
wangqwshi am trying to understand drew's mail14:46
wangqwshdo not know how to set the network on neo14...14:48
adreznecAh, this was the OVS network issues email14:48
wangqwshyes.14:49
thorstI kind of want to wait on the OVS bits until we have CI stabilized14:50
thorstwe need our core CI working first...14:50
adreznecthorst probably has a more detailed description than this, but basically where we're at now (IIRC) is that we need to create a PHYP vswitch for each tempest VM running OSA, then put the OVS trunk on that14:50
adreznecRight14:50
thorstadreznec is right.14:50
adreznecthorst: yeah, I agree with you14:51
wangqwshok14:51
adreznecwe should probably put the OSA CI work on temporary hold while we all debug the main CI issues14:51
adreznecthorst: I will note that on the patch Kyle put up to fix the OSA multi-arch stuff that got broken, Jesse did comment about investigating a multi-arch CI test14:52
adreznecNothing we need to do now14:52
adreznecBut something for the back burner14:52
adreznecSo, CI stability is going to take priority14:53
adreznecDo we have anything else to discuss here? Or are we just on deck for the next set of results?14:53
*** kriskend has joined #openstack-powervm14:54
adreznecOk, well if there's nothing else I'm going to call it14:54
adreznecThanks for joining everyone14:54
adreznec#endmeeting14:54
openstackMeeting ended Tue Nov 15 14:54:58 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2016/powervm_driver_meeting.2016-11-15-14.06.html14:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2016/powervm_driver_meeting.2016-11-15-14.06.txt14:55
openstackLog:            http://eavesdrop.openstack.org/meetings/powervm_driver_meeting/2016/powervm_driver_meeting.2016-11-15-14.06.log.html14:55
*** jwcroppe has joined #openstack-powervm14:56
*** seroyer has quit IRC15:03
*** wangqwsh has quit IRC15:05
*** chas_ has joined #openstack-powervm15:08
*** chas__ has joined #openstack-powervm15:10
*** chas_ has quit IRC15:13
*** chas__ has quit IRC15:15
*** seroyer has joined #openstack-powervm15:18
*** tjakobs has joined #openstack-powervm15:22
openstackgerritEric Berglund proposed openstack/nova-powervm: DNM: CI Check2  https://review.openstack.org/32831715:27
*** apearson has quit IRC15:39
efried1thorst adreznec https://bugs.launchpad.net/pypowervm/+bug/1627579 Is this a thing?15:39
openstackLaunchpad bug 1627579 in pypowervm "Novalink vscsi mappings removed from VIOS" [Undecided,New]15:39
thorstyeah15:42
thorstwe've had that on the backburner for a while15:42
adreznecYeah, we didn't have a scenario where that would happen in the field really15:43
adreznecSo it didn't get high priority15:43
*** openstackgerrit has quit IRC15:48
*** chas_ has joined #openstack-powervm15:48
*** openstackgerrit has joined #openstack-powervm15:48
*** chas_ has quit IRC15:53
*** mdrabe has quit IRC16:01
adreznechttps://github.com/openstack/nova-specs/blob/master/specs/ocata/approved/cold-migration-with-target-ocata.rst16:04
*** kotra03 has joined #openstack-powervm16:06
*** apearson has joined #openstack-powervm16:09
*** mdrabe has joined #openstack-powervm16:10
*** k0da has quit IRC16:15
*** chas_ has joined #openstack-powervm16:19
*** chas_ has quit IRC16:23
efried1esberglu, seeing CI runs failing too quickly to be real runs.  Just let me know when there's something ready to be triaged.16:37
esbergluefried1: There is some network issue where the runs are hanging trying to pull the openstack projects16:38
esbergluI got one to go through16:38
efried1okay.16:38
esbergluIt is finishing up the stack now16:38
*** chas_ has joined #openstack-powervm16:49
*** chas_ has quit IRC16:54
*** apearson has quit IRC17:05
*** apearson has joined #openstack-powervm17:13
*** chas_ has joined #openstack-powervm17:19
*** jwcroppe has quit IRC17:21
*** jwcroppe has joined #openstack-powervm17:22
*** chas_ has quit IRC17:25
*** jwcroppe has quit IRC17:26
*** jwcroppe has joined #openstack-powervm17:27
*** jwcroppe has quit IRC18:02
*** jwcroppe has joined #openstack-powervm18:03
*** jwcroppe has quit IRC18:07
*** thorst has quit IRC18:21
*** thorst has joined #openstack-powervm18:22
*** jwcroppe has joined #openstack-powervm18:24
openstackgerritSridhar Venkat proposed openstack/nova-powervm: ProvisionRequest does not distinguish event source  https://review.openstack.org/39673918:25
*** dwayne has quit IRC18:30
*** apearson has quit IRC18:32
*** dwayne has joined #openstack-powervm18:42
efried1thorst, <machine gun noises>18:51
efried1adreznec, public link to NovaLink overview?18:55
*** kriskend_ has joined #openstack-powervm18:59
*** kriskend has quit IRC19:01
adreznecefried1: blog post or presentation?19:02
efried1adreznec, the latter.19:02
efried1No big deal - was considering including it in the requirements questionnaire, but prolly don't need it.19:02
adreznecHmm I'm not sure we've actually published any presentations19:05
efried1adreznec, don't worry about it.19:08
efried1But...19:08
efried1https://pypi.python.org/pypi/pypowervm/LICENSE19:08
efried1Whyzat missing?19:08
adreznecGood question...19:09
adreznecMaybe something is wrong in our setup.cfg19:09
*** kotra03 has quit IRC19:09
adreznecThat points to the license19:09
adreznecI wonder if it was ever working19:10
adreznecCan't say I checked19:10
efried1actually, it's the README.rst, which is inlined in the pypi page; but pypi doesn't actually have the source sitting right there.19:10
*** k0da has joined #openstack-powervm19:13
efried1adreznec, how do I point to our deb and yum repos for pypowervm?19:14
adreznecWell... the yum stuff isn't published yet19:15
adreznecdeb repo is at http://public.dhe.ibm.com/systems/virtualization/Novalink/debian/19:15
efried1adreznec, what's the plan to publish RPMs?19:16
*** thorst has quit IRC19:16
adreznecThey'll go out with 1.0.0.4 next month19:16
*** apearson has joined #openstack-powervm19:16
efried1k19:16
adreznecThen they'll be at pretty much the same spot, just not in the debian directory19:16
*** kylek3h_away is now known as kylek3h19:24
efried1adreznec, thorst: See commit message updates on https://review.openstack.org/#/c/391286/19:24
*** thorst has joined #openstack-powervm19:25
adreznecWill do19:28
*** thorst has quit IRC19:31
*** thorst has joined #openstack-powervm19:33
*** thorst has quit IRC19:45
*** thorst has joined #openstack-powervm19:47
*** thorst has quit IRC19:50
*** seroyer has quit IRC19:52
*** thorst has joined #openstack-powervm19:56
*** kriskend_ has quit IRC19:59
*** seroyer has joined #openstack-powervm20:01
*** seroyer has quit IRC20:12
*** dwayne has quit IRC20:12
*** kriskend has joined #openstack-powervm20:14
*** thorst has quit IRC20:15
*** thorst has joined #openstack-powervm20:19
*** dwayne has joined #openstack-powervm20:26
*** chas_ has joined #openstack-powervm20:31
*** seroyer has joined #openstack-powervm20:42
thorstefried1: there/20:45
thorstesberglu: just saw a fail come through.  Was that a proper run?21:33
esbergluno21:33
thorstok - expected fail then?21:33
esbergluI must have forgot to turn off zuul before running the playbooks21:34
thorstso no worries?21:37
esbergluNo worries. The playbooks are just taking forever to clone projects. Still working through the compute node deployment21:42
thorstahh21:44
*** apearson has quit IRC21:59
*** jwcroppe has quit IRC22:00
*** jwcroppe has joined #openstack-powervm22:02
*** kriskend has quit IRC22:14
*** jwcroppe has quit IRC22:14
*** apearson has joined #openstack-powervm22:21
*** thorst has quit IRC22:34
*** svenkat has quit IRC22:34
*** edmondsw has quit IRC22:36
*** tblakes has quit IRC22:54
*** esberglu has quit IRC22:54
*** esberglu has joined #openstack-powervm22:55
*** esberglu_ has joined #openstack-powervm22:56
*** esberglu has quit IRC22:59
*** esberglu_ has quit IRC23:01
*** mdrabe has quit IRC23:02
*** seroyer has quit IRC23:06
*** dwayne has quit IRC23:07
*** esberglu has joined #openstack-powervm23:08
*** esberglu has quit IRC23:08
*** esberglu has joined #openstack-powervm23:08
*** jwcroppe has joined #openstack-powervm23:15
*** tjakobs has quit IRC23:23
*** apearson has quit IRC23:31
*** chas_ has quit IRC23:33
*** k0da has quit IRC23:33
*** dwayne has joined #openstack-powervm23:47
*** chas_ has joined #openstack-powervm23:58

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