Wednesday, 2017-02-08

*** thorst_ has joined #openstack-powervm00:08
*** k0da has quit IRC00:38
*** thorst_ has quit IRC00:45
*** thorst_ has joined #openstack-powervm01:19
*** thorst_ has quit IRC01:19
*** Jay2 has joined #openstack-powervm01:50
*** thorst_ has joined #openstack-powervm02:19
*** thorst_ has quit IRC02:24
*** kjw3 has quit IRC02:37
*** Jay2 has quit IRC02:39
*** seroyer has quit IRC02:41
*** thorst_ has joined #openstack-powervm02:55
*** thorst_ has quit IRC02:55
*** svenkat has joined #openstack-powervm02:59
*** Jay2 has joined #openstack-powervm03:13
*** apearson has joined #openstack-powervm03:22
*** tlian has quit IRC03:23
*** svenkat has quit IRC03:29
*** thorst_ has joined #openstack-powervm03:56
*** thorst_ has quit IRC04:01
*** Jay21 has joined #openstack-powervm04:01
*** Jay2 has quit IRC04:03
*** thorst_ has joined #openstack-powervm04:57
*** thorst_ has quit IRC05:02
*** Jay21 has quit IRC05:03
*** Jay2 has joined #openstack-powervm05:03
*** Jay2 has quit IRC05:07
*** Jay2 has joined #openstack-powervm05:21
*** Jay2 has quit IRC05:26
*** thorst_ has joined #openstack-powervm05:58
*** thorst_ has quit IRC06:03
*** apearson has quit IRC06:13
*** edmondsw has joined #openstack-powervm06:17
*** Jay2 has joined #openstack-powervm06:19
*** edmondsw has quit IRC06:21
*** openstackgerrit has joined #openstack-powervm07:54
openstackgerritgengchc2 proposed openstack/ceilometer-powervm master: Remove support for py34  https://review.openstack.org/43061907:54
*** thorst_ has joined #openstack-powervm07:59
*** thorst_ has quit IRC08:04
*** k0da has joined #openstack-powervm08:37
*** openstackgerrit has quit IRC09:34
*** k0da has quit IRC09:34
*** k0da has joined #openstack-powervm09:35
*** thorst_ has joined #openstack-powervm10:00
*** thorst_ has quit IRC10:04
*** smatzek_ has joined #openstack-powervm11:55
*** smatzek__ has joined #openstack-powervm11:57
*** thorst_ has joined #openstack-powervm12:00
*** smatzek_ has quit IRC12:01
*** thorst_ has quit IRC12:05
*** tblakes has joined #openstack-powervm12:07
*** edmondsw has joined #openstack-powervm12:13
*** tblakes has quit IRC12:28
*** Jay2 has quit IRC12:30
*** seroyer has joined #openstack-powervm12:33
*** thorst_ has joined #openstack-powervm12:41
*** jpasqualetto has joined #openstack-powervm12:45
*** svenkat has joined #openstack-powervm12:55
*** efried has quit IRC13:03
*** efried has joined #openstack-powervm13:13
*** nbante has joined #openstack-powervm13:31
*** AlexeyAbashkin has joined #openstack-powervm13:42
*** AlexeyAbashkin has quit IRC13:42
efriedthorst_ Got a few to talk about 4776?13:53
thorst_that power ops?13:53
efriedyes13:53
efriedSee response just posted.13:53
thorst_morpheus is slowly loading13:54
efriedSomeone ought to move that guy to FC disks.13:54
thorst_so basically, I don't like that we're passing in unbounded dictionaries with tribal knowledge keys to issue certain commands13:54
efriedOkay, we're in agreement on not liking it.13:55
thorst_and if we had a PowerOpts object or something you could pass in that enumerated it, fine13:55
thorst_but just an unbounded dict13:55
efriedOkay, so we have enums for BootMode, KeylockPos, and RemoveOptical.13:55
thorst_I always argued against this...clearly lost in this case.13:55
thorst_yeah, but something to take that in, in a way that is bounded.13:55
thorst_the argument against it was 'well the REST API could add something before we update the API to support it', but that's always the case.13:56
efriedOkay, so I think the main point of contention here is the bounding.13:56
efriedWe clearly can't get away with that for legacy.13:56
thorst_right.13:56
efriedBut I can see doing it for the new APIs.13:56
thorst_but for legacy, we can convert unbounded dictionary to the new bounding 'thing'13:56
efriedWell, not if the new bounding 'thing' is bounded.13:57
thorst_'immediate: True' --> power_opt.immediate = True13:57
efriedCause we potentially lose options that we haven't supported.13:57
efried...supported explicitly13:57
thorst_there are none that we know of (even at the API) that we don't know about13:57
thorst_are there?13:57
thorst_I mean, we own REST too...we should be able to figure that out13:58
efriedI would literally have to go into the REST code to glean the exact set of possible keys & values, and clone those logically in a python class.13:58
efriedYes.13:58
thorst_the client certainly doesn't know about an opt that we/REST team don't know about13:58
efriedYeah, the Job itself definitely has an explicit and bounded set of params it accepts.13:58
efriedI wrote that framework.13:58
thorst_k.  So we just use that  :-)13:59
efriedWe've generally stayed away from exhaustively copying the REST semantics.13:59
efriedBut I guess we've trapped ourselves into doing that in some form in this case.13:59
efriedIt does get sticky, though, when we get to 'operation' and 'immediate'.14:01
thorst_right.14:01
efriedThose are JobParameters just like the others, but they're kinda special.14:01
thorst_we took the easy answer earlier.14:01
efriedIs the hard answer better?14:02
efriedAnd... what IS the hard answer?14:02
*** mdrabe has joined #openstack-powervm14:03
*** mdrabe_ has joined #openstack-powervm14:04
*** esberglu has joined #openstack-powervm14:06
*** mdrabe has quit IRC14:08
thorst_the easy answer was an unbounded dictionary14:08
thorst_the hard answer is what I'm arguing we need to do - bound the parameters into the op14:08
efriedthorst_ Ugh, there's a ton of them.14:09
efriedFor IBMi, you can specify netboot params - IP, netmask, gateway, etc.14:09
thorst_well, we know no one is using those14:09
thorst_so I suggest we only do the ones we really know about14:10
thorst_do you really believe anyone would be impacted?14:10
efriedThat's dangerous talk.14:10
thorst_well, I guess if you're really worried we can still take in an unbounded dict...but I don't want the new thing using it.14:10
thorst_maybe it uses it under the covers14:11
thorst_but the new thing shouldn't extend an old, terrible pattern14:11
thorst_for an API we have likely been the only ones that have read it.  :-)14:11
efriedWell, yeah, under the covers we still have to create the job parameters the same way.14:11
efriedI can take a whack at this, but I suspect it's going to feel like we're boiling the ocean.14:12
thorst_there's no one else I'd rather send in to boil the ocean than you14:13
thorst_:-p14:13
*** AlexeyAbashkin has joined #openstack-powervm14:13
thorst_if it gets ridiculous, and I'm being silly, you have the right to tell me to just shove off14:13
efriedRoger that.14:14
thorst_I did +1 afterall14:14
esbergluthorst_: mdrabe_: Moved the staging neo to 1.0.0.5. Ran 2 tests on14:18
esbergluhttps://review.openstack.org/#/c/425780/14:18
esbergluAnd they both passed14:18
esbergluSo we should be good transitioning the prod. CI as well14:18
mdrabe_sweet thanks14:19
*** mdrabe_ is now known as mdrabe14:19
thorst_agree...lets get more throughput on it14:19
*** smatzek__ has quit IRC14:27
efriedthorst_ I assume you do NOT want the pypowervm side to validate business logic too.14:27
thorst_psht, no14:28
efriedLet the REST side handle that as usual.14:28
efriedk14:28
efriede.g. "if you specify X, you must also specify Y and Z" or "the value for X must be between A and B" - that kind of thing.14:28
thorst_push off to rest14:29
*** tlian has joined #openstack-powervm14:35
*** smatzek has joined #openstack-powervm14:57
*** esberglu_ has joined #openstack-powervm15:00
*** esberglu has quit IRC15:04
*** AlexeyAbashkin has quit IRC15:05
*** kriskend has joined #openstack-powervm15:07
*** apearson has joined #openstack-powervm15:10
*** Jay2 has joined #openstack-powervm15:16
*** nbante has quit IRC15:21
*** nbante has joined #openstack-powervm15:22
*** dwayne has joined #openstack-powervm15:24
*** Jay21 has joined #openstack-powervm15:36
*** Jay2 has quit IRC15:36
*** burgerk has joined #openstack-powervm15:36
*** Jay21 has quit IRC15:36
thorst_esberglu_: can we start shutting down the CI environments?15:44
thorst_so I can move the disks around15:44
esberglu_Yep15:48
esberglu_What do you need me to do15:49
thorst_esberglu_: shutdown the servers15:52
thorst_cause I'm just going to force off them15:52
thorst_so you should do something a little nicer than that before I come in with an ax15:52
esberglu_Ok one sec15:53
esberglu_thorst_: all right15:58
*** seroyer has quit IRC16:01
thorst_esberglu_: shut off?16:11
*** seroyer has joined #openstack-powervm16:18
*** k0da has quit IRC16:40
*** jpasqualetto has quit IRC17:08
*** jpasqualetto has joined #openstack-powervm17:19
*** smatzek has quit IRC17:29
*** tblakes has joined #openstack-powervm17:31
thorst_esberglu_: The production VMwas are coming back online.  This is the zuul and openstack VMs17:34
thorst_staging is next...the files are still moving over to the san17:35
*** smatzek has joined #openstack-powervm17:46
*** tblakes has quit IRC17:48
thorst_esberglu_: Staging is coming up now17:48
thorst_so now its up to you to get the envs running again  :-)17:49
esberglu_Are the production ones both up? I can get to the management but not the controller17:50
thorst_should be...let me look at the controller17:52
thorst_remember, you lost your devstack17:52
thorst_so you need to redeploy17:52
esberglu_Yeah. I can't even ping it17:52
thorst_OK - I'll take a peak in 5.17:54
*** smatzek has quit IRC17:54
thorst_well, it got stuck in grub17:56
thorst_yeah, totally hosed.  I'll recopy it17:57
thorst_how about the staging ones?  Everything OK there?18:00
*** tblakes has joined #openstack-powervm18:06
*** smatzek has joined #openstack-powervm18:28
*** nbante has quit IRC18:29
*** adi_____ has quit IRC18:35
*** AndyWojo has quit IRC18:37
thorst_esberglu_: everything should be back now18:41
*** mdrabe has quit IRC19:04
*** mdrabe has joined #openstack-powervm19:04
*** nbante has joined #openstack-powervm19:05
*** nbante has quit IRC19:08
*** mdrabe has quit IRC19:10
*** mdrabe has joined #openstack-powervm19:20
*** apearson has quit IRC19:32
*** adi_____ has joined #openstack-powervm19:47
*** apearson has joined #openstack-powervm19:50
mdrabeesberglu_ So are all the CI nodes on 1.0.0.5 now?19:50
esberglu_mdrabe: Currently redeploying. But yes when they are back up they will be 1.0.0.519:50
mdrabeah ok, thanks for the update19:51
*** AndyWojo has joined #openstack-powervm20:13
*** k0da has joined #openstack-powervm20:19
*** smatzek has quit IRC21:32
*** thorst_ has quit IRC21:53
*** thorst_ has joined #openstack-powervm21:53
*** thorst_ has quit IRC21:58
*** svenkat has quit IRC22:01
*** burgerk has quit IRC22:31
*** edmondsw has quit IRC22:41
*** esberglu_ has quit IRC22:56
*** esberglu has joined #openstack-powervm22:57
*** tblakes has quit IRC22:59
*** mdrabe has quit IRC23:01
*** esberglu has quit IRC23:01
*** seroyer has quit IRC23:10
*** esberglu has joined #openstack-powervm23:10
*** esberglu_ has joined #openstack-powervm23:11
*** esberglu has quit IRC23:11
*** esberglu_ has quit IRC23:13
*** kriskend has quit IRC23:14
*** jpasqualetto has quit IRC23:27
*** apearson has quit IRC23:29
*** k0da has quit IRC23:40

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