Thursday, 2014-08-28

openstackgerritChelsea Winfree proposed a change to openstack/barbican: Adding initial update logic for orders  https://review.openstack.org/11738600:07
*** rm_work|away is now known as rm_work00:08
rm_workalright, took forever but finally in the air <_<00:08
rm_workchellygel: agh, is there going to be Order PUT functionality before I even get my client changes through? :P00:08
chellygelrm_work, tread lightly -- i almost punched my computer through the wall to get that commit up there00:09
chellygellol00:09
rm_workheh00:09
rm_workI feel ya00:09
rm_workI am stuck on an airplane with nothing to do, so I guess I'll take a peek :P00:11
rm_workBTW what exactly is order meta? I may not be loading / treating it correctly in the client right now because i didn't see much about what it is for00:12
rm_workchellygel: ^^00:12
chellygelin my case, it is going to hold data for certificate requests rm_work00:12
rm_workok, so it's kind of... general purpose00:13
rm_workfigured as much... not sure whether it is important to display when someone does "barbican order get" using the CLI00:13
rm_workor how to parse it, I assume it's just random json?00:14
chellygelim not familiar enough to answer that question00:14
chellygeluhh, its going to be validated in the future -- but for now we arent concerned with whats in it00:14
rm_workok00:14
chellygeljust cause its initial crs and stuff00:14
rm_workthen I am probably fine not displaying it00:15
rm_work(for now)00:15
rm_workso all that can be updated with a PUT is that meta?00:15
chellygelfor certificates its going to have like... csr, email addy, order related info?00:15
chellygelmaybe an id?00:15
chellygelyep.00:15
rm_workok00:16
chellygelwhere you off to rm_work ?00:16
rm_workSeattle00:16
rm_workheading up to visit friends, and go to PAX Prime :P00:16
chellygelugh i love it00:16
chellygelim going to PAX south00:16
rm_workheh00:17
rm_workuhh, if you can book a flight within the next day or so, I have an extra set of Prime passes, lol00:17
rm_worksomeone I bought passes for bailed :P00:17
chellygeli would, but i have so much shit at work at this point00:17
chellygelmy dad lives up there though00:17
chellygelvery tempting00:17
rm_workheh00:17
rm_worknotice I'm working from the plane >_>00:18
rm_workprobably will be working in any spare moment too, lol00:18
rm_worktrying to get these reviews through00:18
rm_workbut yeah, also doing PAX South00:18
rm_workand hosting a bunch of out-of-towners on my extra floorspace :P00:19
openstackgerritSheena Gregson proposed a change to openstack/barbican: Updated Create Secret request and response  https://review.openstack.org/11737900:21
rm_workuh-oh00:21
rm_workturbulence warning00:21
rm_workI have not had enough alcohol for this to be ok >_>00:21
* rm_work is fine with flying as long as it's smooth00:21
rm_workchellygel: looks good to me so far, granted that there's a couple of pretty decent TODOs in there :P00:23
chellygelpax south should be fun. and you are nice to help them00:23
chellygelalso, there are going to be like 012934810293 CRs from this one00:24
rm_workheh00:24
chellygelthose todos wont even be done when this CR gets put through, is my guess00:24
rm_workI always shoot for < 3000:24
chellygelCertificates is going to be quite fun to implement00:24
rm_workso far so good on the two I have in flight currently...00:24
chellygeli need to go write those unit tests but im pretty burnt out for the night00:26
rm_workheh yeah00:26
rm_workthough usually test-writing is pretty brainless00:26
rm_workreally it's "which tests do i need to add" that's the tough part00:27
rm_workfilling them in is pretty rote <_<00:27
*** akoneru has quit IRC00:28
woodster_rm_work: the new order format has type/meta, and that is visible to clients. There is also plugin meta associated with orders that is private to plugins, not visible to clients00:32
rm_workwoodster_: ok, but I don't have to worry about that for my current CR right?00:33
woodster_I don't think so, let a follow on cr(s) deal with that00:34
rm_workkk :)00:35
rm_workhuge fan of "BUT, not an issue for *this* CR" :P00:35
woodster_rm_work: the longer these CRs linger out there the harder it is to resist trying to keep up with changes00:37
woodster_rm_work: but then they'd just get fatter and fatter00:37
rm_workyeah, then we'd have to start making "your CR is so fat..." jokes00:39
rm_workwoodster_: you should review 115080 again -- just check out what changed since patch 9 (when you reviewed last), shouldn't be much00:44
*** nkinder has joined #openstack-barbican00:46
rm_workgeneral plug for reviews for https://review.openstack.org/#/c/115080/ (anyone who happens to be around)00:48
rm_workI guess it is getting late00:49
*** bdpayne has quit IRC00:51
rm_workwish Juan would get on so I could discuss some of his comments T_T00:54
chellygelhe usually gets on i wanna say like 11 CDT00:54
rm_workyeah I think I see that he is in Finland?00:57
rm_workso, bit of a time differential00:57
rm_workchellygel: ack, are you still at work? I looked up flights for you but they have gotten quite expensive T_T00:58
chellygelyou talking about seattle??>?00:58
chellygellol00:58
rm_workyes :P00:58
chellygelhahaha, im still at work... sadly00:59
rm_work$700-800 roundtrip now :(00:59
chellygelbut its a personal choice00:59
chellygelNBD, couldnt take the time off anyway00:59
rm_workyeah I am usually at work until 7:30-8 recently too <_<00:59
rm_workbut I feel like I may get in later than you do00:59
chellygelhahha01:00
rm_worktried to explain to someone why I was planning to stay at work until 8pm last friday, and they were like "make some excuse and go home", and i couldn't seem to get them to understand that I COULD leave any time, but I didn't want to :)01:00
chellygelthis week ive been getting in around 8;30 or 901:00
rm_workyeah, much earlier >_<01:00
rm_workturns out working on Barbican stuff is actually interesting :P01:00
chellygelhahaha01:01
chellygelgood!01:01
chellygelokay, i am leaving now -- 8 is good enough01:01
rm_workhave a good ... night then :P01:01
rm_workbit late to still be evening <_<01:01
chellygelv_v01:01
* chellygel cries01:01
*** igueths has joined #openstack-barbican01:03
iguethsHey woodster_, you wouldn't happen to be hanging around by any chance?01:04
rm_workigueths: if he is, I want him too :)01:05
iguethsrm_work: Ha ha01:05
jvrbanacrm_work, I +2'ed your CR01:05
woodster_No I'm mobile :(01:05
rm_workjvrbanac: cool, thanks :)01:05
rm_workjvrbanac: any chance of some love for the dependent one too? :P01:06
rm_workalso, wtf is up with Jenkins/Zuul recently01:06
rm_workI'm in a THREE HOUR queue01:06
jvrbanacrm_work, 987 lines?!?!01:06
jvrbanacgeez!01:06
rm_workjvrbanac: a lot of that is tests! :P01:07
iguethswoodster_: Ah01:07
rm_workjvrbanac: but yes, I've been busy <_<01:07
jvrbanacrm_work, we really need to work on splitting up our work into smaller chunks.01:09
rm_workjvrbanac: this is one pretty basic chunk01:09
rm_worknot sure how it could be split01:09
rm_workI already DID split it into two01:09
rm_workthis COULD have been part of the last one01:09
rm_workjvrbanac: going from "no containers.py" to "have containers.py" and "have tests for containers.py"01:10
rm_workeverything else is a few lines here and there, but all directly related <_<01:11
*** lisaclark1 has joined #openstack-barbican01:11
jvrbanacrm_work, yeah01:11
rm_workI mean, I could have cut out almost 400 lines of that if i didn't do the tests in this CR :)01:11
rm_workjvrbanac: would love to actually be working on something that's simple enough to do in 100 lines or less for once :)01:13
*** lisaclark1 has left #openstack-barbican01:14
jvrbanacrm_work, well, there are always hacking violations ;)01:14
rm_workI mean, I am totally down for fixing those!01:14
jvrbanacrm_work, I'm slowly trying to bring our code into compliance with hacking 0.9.201:14
jvrbanacas can be seen here: https://review.openstack.org/#/c/11733401:15
rm_workbut like... even my last 5 line change had ~200 lines of tests tacked on <_<01:15
jvrbanaclo!01:15
jvrbanaclol!01:15
aleewoodster_, ?01:16
jvrbanacalee, woodster_ is out/mobile at the moment01:16
rm_workjvrbanac: well, I could like... tack onto that, I guess?01:16
rm_workif you want some assistance01:17
aleejvrbanac, thanks -- just checking on the off chance he was around01:17
rm_workand don't mind someone pushing patchsets onto your CR01:17
aleerm_work, thanks01:17
* rm_work is sitting on a plane trying to find code to edit01:17
jvrbanacrm_work, you can create a dependent CR ;)01:17
rm_workjvrbanac: well sure, but then if I fix stuff it'll still show up as broken when you run pep8 against your CR01:18
aleeabout to put up a new version of my cr for review.  Feel free to take a look when you get a chance.01:18
rm_workbecause it'll be fixed in the next CR, not in yours :/ and then it'd just be confusing01:18
jvrbanacrm_work, it's not broken at the moment because we pin to an earlier version of hacking. To do the changes I just pop in the global req version of hacking and then remove it before submitting.01:19
jvrbanacalee, k01:19
rm_workright01:20
rm_workjvrbanac: actually, wouldn't it make sense just to update the hacking version *in that CR*?01:20
rm_workand by broken, I meant that I'm assuming you decide what to fix based on running the pep8 checks :P01:20
rm_workso stuff would come up in the report that was actually already fixed in the dependent CR01:20
rm_workwhich would make deciding what to work on a bit confusing01:21
jvrbanacrm_work, the reason I didn't change the requirements is because there are hundreds more of the violations, so the gates would never pass01:21
rm_workalso rebasing constantly would be a PITA since it's random files all over the place we'd be changing, so good chances of accidentally overlapping01:21
rm_workjvrbanac: right, but... don't you want to get them ALL? :P01:22
jvrbanacrm_work, eventually yes, but small chunks remember? ;)01:22
rm_workheh01:22
rm_workok, so are you DONE with that CR then?01:22
jvrbanacyeah01:22
rm_workif that's the case, then yeah, I could just do a dependent CR01:22
rm_workI thought you were still going to be updating it01:22
jvrbanacrm_work, no I'll just make dependent CR's for future work as well.01:23
rm_workkk01:23
rm_workit's funny, I noticed a lot of these issues just LOOKING01:23
jvrbanacI don't want to make these go more than 200 lines a pop01:23
rm_workand was like "hey, isn't that a hacking violation?"01:23
rm_workbut didn't question it since they passed gate :P01:23
rm_workalright, I'll see if I can knock out ~200 lines before I land01:24
jvrbanacrm_work, nice! Thanks!01:24
rm_workmight be optimistic :P01:24
rm_workhacking==0.9.2 ??01:26
iguethsAfk.01:27
*** igueths has left #openstack-barbican01:27
rm_workI feel like I should expense this $13 in-flight wifi :P01:28
rm_workwell, at this rate tox won't have finished installing hacking/pep8 before I land >_>01:31
*** gyee has quit IRC01:32
jvrbanacrm_work, lol yeah01:33
rm_workit's a race, which will happen first -- I land, tox finishes setting up its environment, or Zuul actually finishes running the tests on my CR patchsets from 3.5 hours ago01:34
rm_workI think probably 2,1,301:34
jvrbanacrm_work, the official global req is: hacking>=0.9.2,<0.10 however, the latest is 0.9.2 at the moment01:35
rm_workk01:35
rm_workthere we go01:38
openstackgerritAde Lee proposed a change to openstack/barbican: Additional work on certificate processing  https://review.openstack.org/11695601:45
aleejvrbanac, its up ..01:45
aleejvrbanac, depends on woodster_ cr which we both +2'd01:46
jvrbanacalee, awesome k01:46
rm_workman, this multi-line-comment-blank-line thing is super annoying01:46
jvrbanacrm_work, I know right!01:46
rm_worksomeone should give a good smack to whoever decided on that one01:47
rm_workcouldn't we just like.... IGNORE H405 in our tox.ini? :P01:47
rm_workwe already ignore some others01:47
rm_workthis one is dumb >_<01:47
jvrbanacrm_work, I get the idea behind the rule, but yeah. Unfortunately, ignoring rules should only be seldom used. :/01:51
rm_workyes, but I *already* HATE this one01:51
rm_workah well, fixed a few of them already01:51
jvrbanacrm_work, it does kind of point out that we need better docstrings in places lol01:52
rm_workI guess <_<01:52
rm_workfixing these requires some creativity (lots of rewording)01:55
jvrbanac:D01:55
*** openstackgerrit has quit IRC02:02
*** openstackgerrit has joined #openstack-barbican02:03
rm_workjvrbanac: any easy way to check how many lines I've changed?02:04
jvrbanacgit diff --stat02:04
rm_workah, right02:04
rm_workonly + counts, right? :P02:04
jvrbanaclol just try to keep it sensible.02:05
jvrbanacLarge CR's tend to go to the bottom of my review pile02:06
rm_workLOLWUT does this even mean02:06
rm_workIterator that prints the contents of a wrapper string iterator when iterated.02:06
jvrbanacwhat number?02:07
rm_workI think I am just going to remove the "when iterated."02:07
rm_workoh, that's the comment02:07
rm_workit's a multi-line docstrint02:07
jvrbanacoh lol!02:07
rm_work*docstring02:07
rm_workI am going to assume SOMEONE knows what that means02:07
rm_workis ./barbican/model/migration/alembic_migrations/env.py generated / exempt from hacking?02:10
jvrbanacFor now yeah02:10
rm_workwow, some of these line continuation fixes are tough02:37
rm_workwow, some of these line continuation fixes are tough02:38
rm_workerr02:38
rm_workoops02:38
jvrbanacrm_work, I'm glad they are forcing people to not use backslashes anymore they are a plague.02:39
rm_workyeah02:39
rm_workagree, but like02:39
rm_workrunning into a lot of "visual indentation cannot be distinguished from the following line" when trying to fix multi-clause `if` statements02:40
rm_workthey can be really tricky to do (and honestly probably MORE ugly once "fixed")02:40
jvrbanacrm_work, depends. I end up reworking the layout a bit, perhaps handling some processing outside.02:42
rm_workheh02:42
rm_workso you actually were doing more than just rearranging in those cases02:42
jvrbanacrm_work, it really depends on the case. If you need a suggestion, send me the file and line number you're looking at02:43
jvrbanacphew! 2 hours later I finally finished that review rm_work02:46
rm_workheh02:47
rm_workwell, I am about to submit a thing02:47
rm_workhopefully this is what you had in mind02:47
rm_worklanding soon, so submitting this :(02:50
rm_workerr, :)02:50
jvrbanaclol02:50
rm_workwent through pretty literally just fixing the issues02:51
openstackgerritAdam Harwell proposed a change to openstack/barbican: Making a few MORE modules hacking 0.9.2 compliant  https://review.openstack.org/11740402:51
rm_workdidn't do much real refactoring, like I guess maybe you did in some cases02:51
jvrbanacrm_work, sweet02:52
rm_worksame EXACT number of lines as yours, rofl02:52
jvrbanachaha!02:52
rm_workdidn't even realize till i just looked02:52
rm_workono, I got a -102:53
jvrbanac:(02:53
rm_workso, on the __str__ method crazy02:56
rm_workI agree, it's a little nuts02:56
rm_workI guess I could do something like that02:57
jvrbanacrm_work, lol I had to reread that 4 times to make sure I understood what was going on there02:57
rm_workheh03:00
rm_workI mean, the thing that's happening is not un-complicated03:00
rm_workI think jaosorior (spelling?) is correct in saying the entirety of all of the __str__ for the client classes need work03:01
jvrbanacthey do03:01
rm_workmaybe by letting cliff handle it03:01
rm_workthe format functions for cliff would work great I think, assuming those can just be easily plugged in03:01
rm_workand that we'd be ok with using the cliff style formatting03:02
jvrbanacIf cliff has them, that would be awesome03:02
jvrbanacI don't know what the formatting style is03:02
jvrbanacI haven't seen it03:02
rm_workah03:02
rm_workit's like pretty-table kinda03:02
jvrbanacewww03:02
rm_worklots of __ ||||03:02
rm_workboxes and shit03:02
rm_workdesigned for CLI output03:02
rm_workbut so is __str__, really03:03
jvrbanacsomething about variable length secrets tends to not fit in tables very well ;)03:04
rm_workusing *args in that wrapper simplifies the ones in the other classes too actually :P03:04
rm_workalright, think i got all of your comments addressed except the __str__ one03:06
rm_workoh, and the thing about RSAContainer could return CertificateContainer :P03:07
rm_workTechnically yes, but I don't think that's necessarily a bad "feature". I could MAYBE see some confusion from a user who tries this and ends up with a different object type (I would definitely WTF myself), but the alternative is passing the type through and raising a TypeException or something in Container() if the fetched data isn't of the passed type. Do you think that's a better approach?03:08
rm_workjvrbanac: ^^ was my response03:08
jvrbanacrm_work, ahh... Personally, I'm really not a fan of multiple return types especially when you're asking for a specific object type. There's probably a couple of different ways to deal with this.03:10
jvrbanacPart of it is around making sure the factory gives you what you are asking for03:11
rm_workwell, I have the way I mentioned already "done"03:11
rm_workif we want to do that03:11
rm_workit'll raise a TypeError if the response type and expected type don't match03:11
rm_workis that something you agree with?03:12
jvrbanacrm_work, I think that would work for now. I would like to get a couple other opinions on this. I would hate to start a pattern that then turns into an ugly beast 6 months down the road.03:13
rm_workyeah03:13
rm_workalright landing03:15
jvrbanacgeez it's 10pm. I'm gonna head out. catch you later rm_work. btw I +2'ed your other CR03:15
rm_workwill submit that fix in a bit03:15
rm_workcool03:15
rm_workwell03:15
jvrbanacthe one you just put up03:15
rm_workah cool03:15
rm_workI have to do another patchset on the first one you +2'd03:15
rm_workto do the wrapper fix with *args03:15
rm_worksince both of those classes use that too03:15
jvrbanacahh ok03:16
*** juantwo has quit IRC03:16
jvrbanacwell, just let me know when they're up and I'll take a look again03:16
openstackgerritAdam Harwell proposed a change to openstack/python-barbicanclient: Add Containers to python-barbicanclient  https://review.openstack.org/11339303:16
rm_workthis one is now03:16
rm_worklol03:16
jvrbanaclol ok, well I will look at it first thing in the morning03:17
rm_workand the other will be in about 10s :P03:17
rm_workyeah03:17
rm_workthat is fine03:17
rm_workah shoulda done this one first03:17
rm_worknow I have to rebase the other one immediately >_>03:17
rm_workanywho, night!03:17
*** juantwo has joined #openstack-barbican03:18
jvrbanaclol night03:18
openstackgerritAdam Harwell proposed a change to openstack/python-barbicanclient: Refactor client models in python-barbicanclient  https://review.openstack.org/11508003:18
openstackgerritAdam Harwell proposed a change to openstack/python-barbicanclient: Add Containers to python-barbicanclient  https://review.openstack.org/11339303:19
*** rm_work is now known as rm_work|away03:20
*** juantwo_ has joined #openstack-barbican04:04
*** juantwo has quit IRC04:08
*** juantwo_ has quit IRC04:11
*** rm_mobile has joined #openstack-barbican04:15
*** rm_mobile has quit IRC04:37
*** rm_mobile has joined #openstack-barbican04:37
*** rm_mobile has quit IRC04:49
*** rm_mobile has joined #openstack-barbican04:52
openstackgerritA change was merged to openstack/barbican-specs: Remove docutils pin  https://review.openstack.org/11717604:57
*** rm_mobile has quit IRC04:59
*** woodster_ has quit IRC06:05
*** tkelsey has joined #openstack-barbican06:38
*** jaosorior has joined #openstack-barbican07:11
jaosoriorI know it's late for you guys, but rm_work, are you around?07:14
redrobotjaosorior it's actually only midnight for rm_work right now... but I think he may be done for the night.07:19
jaosorioryeah, just had to give it a shot, you never know07:19
jaosoriorso what's up, redrobot, how's it going dude?07:22
redrobotjaosorior not too shabby... up way past my bed time.07:22
redrobotjaosorior got engaged a couple of weeks ago, so there's that07:23
redrobotsoon there'll be a mrs. redrobot07:23
jaosorioraaaah crap! congrats dude! :D07:24
redrobotthanks!07:26
*** jamielennox is now known as jamielennox|away08:36
*** tkelsey has quit IRC11:06
*** juantwo has joined #openstack-barbican12:14
*** juantwo has quit IRC12:17
*** juantwo has joined #openstack-barbican12:18
*** alee has quit IRC12:22
*** nkinder has quit IRC13:09
*** alee has joined #openstack-barbican13:32
*** woodster_ has joined #openstack-barbican13:44
*** paul_glass has joined #openstack-barbican13:45
*** SheenaG11 has quit IRC13:45
*** nkinder has joined #openstack-barbican14:04
*** samuelbercovici has joined #openstack-barbican14:14
chellygelGood Morning everyone!14:16
*** SheenaG1 has joined #openstack-barbican14:20
jaosoriorhey, chellygel, good morning :)14:22
chellygelhey jaosorior! good afternoon14:22
jaosoriorhow's it going?14:23
chellygelits thursday before a 3 day weekend. Soooooo14:23
chellygelhahah14:24
chellygelbut, i can't complain -- its pretty good14:24
chellygelyou?14:24
jaosorior3 day weekend? niiiice14:24
jaosoriorhow come?14:24
chellygelwe have labor day on monday14:25
chellygeli dont know much of the history behind it14:25
chellygelbut basically, national free day off14:25
jaosoriorhahaha hey, fair enough14:25
chellygeli take what i can get man14:26
jaosoriorhahaha I feel you :P14:26
jaosoriorany plans?14:26
chellygelnothing solid yet. still debating. May go visit friends, may just take a lazy weekend!14:27
chellygellabor day is known for terrible traffic -- and i think i'm allergic to it ;)14:27
jaosoriorgo the evening before it?14:28
chellygelits true, i could!14:28
chellygelyou have any plans for the weekend?14:29
chellygelboulders to conquer?14:29
jaosoriorsome friends are gonna visit me from another city, and we'll party hard :P14:30
chellygelhaha, yeah??14:31
jaosoriorhaha yup14:32
jaosoriorlets see how it goes14:32
*** atiwari has joined #openstack-barbican14:45
aleejaosorior, thanks for review.  responded to your comments14:53
aleewoodster_, ping - had a chance to take a look yet?14:54
woodster_alee: I'm looking at it now14:54
aleewoodster_, great14:59
jvrbanacwoodster_, tossed a quick question for you on https://review.openstack.org/#/c/115301/15:10
jaosorioralee: certificate_manager instead of cm or cert_mgr would be better IMO15:10
woodster_jvrbanac: I'll take a look shortly....15:10
chellygeljaosorior, for the sake of being explicit?15:12
chellygelcertificate_manager, that 20 characters of my 80! not including the 4 for tabs! lol15:12
jaosoriorI don't see that as an argument :P15:13
chellygelim just curious as to why that is your preference15:13
jaosoriorbut if there REALLY is a need to keep it short, the shortest I would think would be acceptable would be cert_mgr15:13
woodster_alee: Just added comments now....the retry stuff we really need to flesh out. I'll start a etherpad for it....15:13
jaosoriorfor the sake of being explicit and completely unambiguous15:14
jaosoriorI think it's generally a good practice to have variable names that are actually pronounceable. if the code needs more than those 80 characters, then might as well revise the algorithm. Simplicity FTW ;)15:15
openstackgerritA change was merged to openstack/barbican: Updated Get Secrets request and response  https://review.openstack.org/11735215:15
chellygelso, would cert_manager work?15:15
jraim__reaperhulk: you there?15:16
jraim__redrobot: you there?15:16
jaosoriorI would be OK with cert_manager, though I would still prefer the full word :P15:16
openstackgerritA change was merged to openstack/barbican: Updated Create Secret request and response  https://review.openstack.org/11737915:16
chellygeli'll add the comment! thanks -- still learning the whole python thing :)15:17
jraim__woodster_: you there?15:17
woodster_jaim: yes15:17
jraim__question about the 'Add support to order new and modify existing SSL certs.'15:18
jraim__spec15:18
jraim__launchpad says started15:18
jraim__is that code going to land for j3?15:18
jaosoriorchellygel: what comment?15:18
chellygeli added the "cert_manager" comment to alee's change, so others can weigh in15:19
jaosorioruok15:19
*** paul_glass has quit IRC15:19
jraim__woodster_: ^^15:20
woodster_jraim: let me take a look at the specs CR for it...I think that was merge in, and if so, yes landing for Juno M315:21
jraim__okay, we need to clean up the BP listing for J3 so I'm trying to figure out what's done and what is going to be pushed15:21
woodster_jraim: oh got you. I think Douglas has been trying to clean things up out there as well, I'll give him a heads up when I see him15:22
woodster_jraim: when do you need this Juno-cut info by? Can we flesh that out this afternoon?15:23
jraim__that's fine. I have a meeting with ttx in a few minutes and I want to make sure we have an idea.15:24
jraim__of where we are15:24
woodster_jraim: regarding SSL plans specifically, this blueprint covers the SSL certificate work we planned on doing (see the Work Items section): https://github.com/openstack/barbican-specs/blob/master/specs/juno/add-ssl-ca-support.rst15:24
woodster_jraim: got it15:25
jraim__BPs / specs are fine. We just need ot make sure that everything that got landed that had a spec, the BP that corresponds to that spec is linked to the J release it was in15:25
jraim__before we cut j3 next week15:25
woodster_jraim: yes, we have been having regular conversations about that, but the blueprints in LP probably need to be polished to reflect that. The big changes are for: 1) the new orders resource format (backwards compatible to the old one though), 2) to allow for PUTs to the orders resource, 3) removing the tenant-id from the URI, 4) adding an optional consumers15:31
woodster_registration for containers, 5) adding transport-key wrapping support.15:31
jraim__cool. We'll also have to talk about what we do with approved specs that didn't make it into Juno. Nova is actually requiring that the submitter resubmit the spec for Kilo rather than port them over15:32
jraim__I kind of like that idae15:32
*** samuelbercovici has quit IRC15:33
*** paul_glass has joined #openstack-barbican15:33
redrobotjraim__ there's a couple of BPs in j-3 with a ton of CRs, so it'll take  me a min to sort those out15:33
woodster_alee: Please weigh in on this CR when you can: https://review.openstack.org/#/c/116387/15:34
jaosoriorwoodster_: I actually made a comment about that CR15:35
jraim__redrobot: no hurry, just wanted to be able to tell ttx that we are on it15:35
redrobotjraim__ the only one I'm not sure about status is reaperhulk's refactor of PKCS1115:35
redrobotI think it's in-progress now?15:36
woodster_jaosorior: I just noticed that now...I'll take a look at those,  thanks15:36
woodster_redrobot: yes, he is looking at that now15:36
openstackgerritKaitlin Farr proposed a change to openstack/barbican: Add PyKMIP to requirements  https://review.openstack.org/11753915:37
woodster_redrobot: might require data model mods, which wouldn't be affected by J3 deadline I'd think as long as have migration scripts. Might also require tweaks to the HSM plugin interface though...I still need to talk to Paul about that.15:37
redrobotIs Kaitlin around?15:38
jraim__redrobot: I pinged him this morning, but it's still early for him :)15:39
reaperhulkit is totally early15:39
reaperhulkand i am fighting swig.15:39
reaperhulkso...who knows.15:39
jraim__you haz a sad15:39
woodster_reaperhulk: See my last comments to redrobot above ^^^^15:39
redrobotso maybe "slow progress" instead of "good progress" would be a better status :)15:39
reaperhulkwoodster_ cool15:39
jraim__it's not biggie if it doesn't land for j3, we just need to retarget it for k1 and land it in a branch until Juno stable is out15:39
woodster_well, it would be good to using the revised HSM approach sooner than Kilo I think :)15:41
redrobotdoes that mean Juno won't support PKCS11 HSMs?15:42
woodster_well, this is the MEK approach vs the current per-tenant approach I believe15:42
aleewoodster_,  lets leave the fleshing out of exactly what needs to happen to schedule a retry task to a subsequent CR.15:43
jraim__woodster_: then it needs to be in for j3. After that, we shouldn;t be landing big features.15:43
jraim__We can land the work, it'll just wont be in the Juno release15:43
jraim__It'll be in a K1 branch that we can merge to master once we cut the j-stable15:43
aleewoodster_, we can keep what I have so far, but realize that its subject to change later.  and if we change it, everything we need will be there.15:44
aleewoodster_, agreed?15:45
woodster_alee: I think so, but I still would prefer the private functions to be pushed lower than the public ones in certificate_manager.py15:46
aleewoodster_, ok agreed -- I'm making all those changes now15:46
woodster_alee: nice, thanks15:46
*** gyee has joined #openstack-barbican15:47
aleewoodster_, are we ready to push https://review.openstack.org/#/c/115715/6 ?15:47
woodster_alee: I've been ready. :)15:49
aleewoodster_, :)  maybe we can recruit some of the troops ?15:50
woodster_alee: ha! for sure15:51
aleereaperhulk, can we get a woop woop -- https://review.openstack.org/#/c/115715 ?15:51
aleewoodster_, I'm thinking that perhaps we get my CR in after yours -- and then you rebase and get your events one and 11638715:52
alee(116287 will need to be adjusted most likely)15:53
woodster_alee: yeah, that's been my hope, getting all the puzzle pieces in there.15:53
aleewoodster_, we should also get a cr in adding order substatus and message15:53
aleewoodster_, you could probably whip that up in a heartbeat ..15:54
reaperhulkapproved15:54
woodster_alee: ha! Yes, that *should* be a simple one15:56
aleereaperhulk, fantastic -- I'll be pinging you for mine shortly (I hope)!15:57
*** jraim__ has quit IRC16:06
*** jraim_ has joined #openstack-barbican16:06
*** rm_mobile has joined #openstack-barbican16:06
openstackgerritA change was merged to openstack/barbican: Add a py3pep8 tox job. This will verify py3 compliant syntax  https://review.openstack.org/11672516:08
openstackgerritA change was merged to openstack/barbican: Initial connect orders resource to certificate processing  https://review.openstack.org/11571516:15
rm_mobileHey  jaosorior , I'm awake now :)16:17
rm_mobileWent -2 timezones, it's early16:17
*** arunkant_work has joined #openstack-barbican16:18
arunkant_workjuantwo, Can you look into my reply of https://review.openstack.org/#/c/110817/13/barbican/model/repositories.py,cm and let me know if you still want me to add TODO and submit new patch16:19
*** rm_work|away is now known as rm_work16:19
redrobotarunkant_work Juan Antonio Osorio Robles is jaosorior16:20
juantwo^16:21
jaosoriorouh, sorry rm_mobile, leaving actually :/16:21
jaosorioror rm_work16:22
rm_worklol k16:22
rm_workI need to check for reviews16:22
rm_workit's early here and i'm in ETO, but whatev :P16:22
rm_workgotta get my CRs in :P16:22
jaosoriorarunkant_work: I'll leave a 0 score to see if woodster_ or someone else weighs in, if by tomorrow nobody has, then I'll +1 it16:23
arunkant_workredrobot, thanks.16:25
*** akoneru has joined #openstack-barbican16:27
woodster_jvrbanac: John, can you take a look at the comments at the top of this CR: https://review.openstack.org/#/c/110817/13/barbican/queue/keystone_listener.py,cm16:38
akonerureaperhulk, ping16:39
woodster_dos Juans16:39
aleewoodster_, did we decide retry_time could be zero?16:46
aleewoodster_,  and if so - what does that mean?16:46
woodster_alee: I think a retry of <= 0 could mean no retry at all16:47
aleeok16:47
rm_workjaosorior: i guess you are probably gone/16:48
akoneruping. Hi. I am trying to run the unit tests for barbican. I followed the Quick start guide and setup a virtual environment. I also setup the oslo-incubator project.16:50
redrobothi akoneru16:50
* rm_work waves at akoneru 16:50
redrobotakoneru unit tests are run via tox16:50
akoneruWhen i run bin/barbican.sh, i see this in the log - http://fpaste.org/129376/40924392/16:50
redrobotugh... yeah... barbican.sh sucks...16:50
* akoneru Namasthe!16:51
redrobotwe really need to either fix barbican.sh or get rid of it16:51
akonerubut the test runs fine when run in PyCharm16:51
redrobotakoneru to run unit tests, first pip install tox16:51
*** gyee has quit IRC16:51
redrobotakoneru then run "tox" for the full suite16:51
akoneruredrobot, hmm. ok. will try that.16:52
redrobotakoneru or tox -e py27 for python 2.7 only, tox -e pep8 for pep8 only, etc16:52
redrobotakoneru tox is what the Gerrit gates use, not barbican.sh16:52
akoneruredrobot, hmm. ok. so the output i shared is from the nosetests call? Any idea as to why i get it when i am able to run the test fine in PyCharm?16:53
akoneruredrobot, just wanted to confirm that there is nothing wrong with my setup16:54
redrobotakoneru not familiar with PyCharm.  But yes, that is a bug with barbican.sh16:54
redrobotakoneru barbican.sh uses nose, which was removed from the project in favor of testtools16:55
akoneruredrobot, oh. ok. thanks! i will try tox.16:56
redrobotakoneru filed a bug for the barbican.sh error https://bugs.launchpad.net/barbican/+bug/136271416:58
*** rellerreller has joined #openstack-barbican16:58
akoneruredrobot, thanks!17:00
reaperhulkakoneru did redrobot cover everything? :)17:00
akonerureaperhulk, yes17:00
reaperhulkgreat17:00
openstackgerritAdam Harwell proposed a change to openstack/barbican: Making a few MORE modules hacking 0.9.2 compliant  https://review.openstack.org/11740417:02
rm_workjvrbanac: you need to rebase https://review.openstack.org/#/c/117334/117:03
rm_worki was able to submit my changes with "git review -R" but you have rebase issues in your commit that gerrit was complaining about :P17:03
*** paul_glass has quit IRC17:07
openstackgerritAde Lee proposed a change to openstack/barbican: Additional work on certificate processing  https://review.openstack.org/11695617:09
rm_workgah wtf, I'm on ETO, what am I doing working all morning >_<17:10
aleewoodster_, jvrbanac , hockeynut, jaosorior  - new CR uploaded17:11
aleereaperhulk, ^^17:11
aleechellygel, ^^17:12
*** kebray has joined #openstack-barbican17:14
*** juantwo has quit IRC17:19
*** alee is now known as alee_lunch17:21
*** rellerreller has quit IRC17:30
chellygelthanks alee_lunch17:32
*** bdpayne has joined #openstack-barbican17:34
*** paul_glass has joined #openstack-barbican17:39
woodster_akoneru: barbican.sh was intended to be a quick and dirty local installer tool...that test step should definitely be removed18:08
*** paul_glass has quit IRC18:14
*** gyee has joined #openstack-barbican18:21
woodster_speakers for openstack: https://openstacksummitnovember2014paris.sched.org/directory/speakers/4#attendee-list18:24
*** paul_glass has joined #openstack-barbican18:26
rm_workwoodster_: turns out I am going, so maybe I'll be able to do the thing i wanted to do as a brown-bag talk, since the talk I was a part of didn't make it18:26
*** rm_work is now known as rm_work|away18:37
*** rm_mobile has quit IRC18:40
woodster_alee: Checkout https://openstacksummitnovember2014paris.sched.org/event/b33df98d88388ec57ce958d0a0c47c66#.U_9334BdUjA18:42
*** jaosorior has quit IRC18:42
*** juantwo has joined #openstack-barbican18:46
woodster_alee: have to figure out how to add rellerreller to that talk as well18:51
woodster_alee_lunch: See above comments please ^^^^18:51
openstackgerritJohn Vrbanac proposed a change to openstack/barbican: Making a few modules hacking 0.9.2 compliant  https://review.openstack.org/11733418:56
*** alee_lunch is now known as alee18:56
aleewoodster_, hey looks good - and yes , we should18:57
alee(figure out a way to add rellerreller18:58
aleeassuming he's going ..18:58
aleewoodster_, had a chance to review CR?18:58
*** SheenaG1 has quit IRC19:02
*** ametts has joined #openstack-barbican19:04
reaperhulkSo, I see rellerreller is trying to get pykmip into global reqs...anybody know why? Seems like it has no need to be present in global requirements just like pykcs11 and the dogtag pki lib don't need to be there19:11
openstackgerritKaitlin Farr proposed a change to openstack/barbican: Add PyKMIP to requirements  https://review.openstack.org/11753919:13
*** rm_mobile has joined #openstack-barbican19:23
*** openstackgerrit has quit IRC19:31
*** openstackgerrit has joined #openstack-barbican19:33
*** kebray has joined #openstack-barbican19:38
*** kebray has quit IRC19:39
jraim_ha, perfect timimg19:44
aleewoodster_, ping19:47
woodster_alee: hello19:47
aleewoodster_, when do we plan to normalize all secrets to base 64 before storing?19:47
woodster_alee: I thought that was already going on?19:48
aleeI still see a TODO in there ..19:48
aleeplugin/resources.py line 10119:49
woodster_ah yes, good find19:51
aleewoodster_, looks to me like we're passing in a byte array and the content type to the plugins ..19:52
aleeam i reading that correctly?19:52
woodster_alee: yep, per tr.normalize_before_encryption() logic19:53
aleewoodster_, so is this going to change in juno?19:53
woodster_alee: so I think tr.normalize_before_encryption() should do the base64 conversion and return that as unencrypted19:54
aleesure -- just wanted to know when we wanted to land that change19:54
aleeso I can adjust the dogtag plugin accordingly19:54
woodster_alee: I think it needs to, if I recall rellerreller right...I think he was expecting this for their KMIP work.19:54
aleeok - another one on the list then :/19:55
*** SheenaG1 has joined #openstack-barbican19:59
aleewoodster_, so had a chance to look at my cr?20:05
*** rm_mobile has quit IRC20:19
*** rm_mobile has joined #openstack-barbican20:19
woodster_alee: just +2ed it...zuul is still pending it looks like20:22
aleewoodster_, cool - yeah zuul on its coffee break20:22
woodster_Regarding Juan's comment in my remove config parameter CR: https://review.openstack.org/#/c/116387/3/barbican/model/repositories.py,cm20:27
*** paul_glass has quit IRC20:27
woodster_....does anyone have a preference of his dict of repositories approach vs the CR's separate getter functions approach?20:27
woodster_alee: ^^^^20:28
aleejvrbanac, reaperhulk , chellygel , hockeynut  -- my CR needs some love please :)20:29
aleewoodster_, let me look .. give me a few mins -- in the middle of some dogtag reviews ..20:29
woodster_jvrbanac: I added a response to your comment in the cert event CR here: https://review.openstack.org/#/c/115301/7/barbican/plugin/interface/certificate_manager.py,cm20:30
woodster_alee: no problem, thanks20:30
chellygelalee, sure, reading now20:30
aleethanks20:31
*** woodster_ is now known as woodster20:32
chellygelhey alee,20:40
chellygelon your plugin/dogtag.py -- you have cm as the import still instead of cert_manager, i know its existing code -- would it be better to keep that consistent ?20:41
chellygelit can be a separate CR, just curious.20:41
aleechellygel, yeah - I'll do that in a separate CR20:42
aleechellygel, doing it in this one would just obscure the changes20:43
chellygelyeah, makes sense to me!20:43
chellygeli'll add the comment on my vote20:43
chellygelw/ "separate cr" of course :)20:43
aleethanks20:43
*** AndChat|40521 has joined #openstack-barbican20:50
*** rm_mobile has quit IRC20:50
aleereaperhulk, https://review.openstack.org/#/c/116956/ needs a woop woop please :)20:52
*** rm_work|away is now known as rm_work20:52
*** AndChat|40521 has quit IRC20:53
reaperhulkalee: curious about the CA_PLUGIN_TYPE_DOGTAG and CA_PLUGIN_TYPE_SYMANTEC constants. Are those used anywhere/will they be used in an upcoming CR?20:53
openstackgerritAdam Harwell proposed a change to openstack/barbican: Making a few MORE modules hacking 0.9.2 compliant  https://review.openstack.org/11740420:57
rm_workalright, rebased now20:58
rm_workthanks jvrbanac20:58
aleereaperhulk, I think they are used -- or at least the dogtag one is used in this CR21:08
reaperhulkah yeah I see it21:09
aleereaperhulk, but yes - the idea is that a client could send in the preferred vendor21:09
aleeand the plugin supports method will need to say it supports that type21:09
reaperhulkI'm less familiar with the certificate implementation than I probably should be but this lgtm21:10
aleereaperhulk, awesome -- woop woop?21:10
reaperhulkapproved21:10
aleecool beans21:10
aleewoodster, we're on a roll ..21:11
rm_workI forget, is thursday a merge/sprint meeting for you guys usually?21:11
woodsterrm_work: you mean us? Ours is on alternate Tuesdays21:12
rm_workah Tuesday21:12
rm_workwoodster: but while I have you responding... https://review.openstack.org/#/c/113393/ :P21:13
*** kebray has joined #openstack-barbican21:14
aleewoodster, I have to think about whether I prefer Juan's approach or the get_xxx_repository() one.21:18
aleewoodster,  overall I'm more inclined to the get_xxx_repository()21:19
aleewoodster,  makes things more explicit21:19
woodsteralee: yeah, I like not having multiple get functions, but not liking having to provide a string to the one finder function21:19
woodsteralee: yeah, explicit seems better to me as well21:19
woodsteralee: you want to add a comment along those lines?21:20
*** SheenaG1 has quit IRC21:20
aleewoodster, overall , I think the approach in the cr is good.  I'm not too keen about having StoreCryptoPlugin not inherit from SecretStoreBase though21:20
aleewhy can't you define a helper function _get_context() that gets the context you need in the functions in StoreCryptoPlugin ?21:22
aleewoodster, need to think on this some more, but there must be a way to do it ..21:24
woodsteralee: yeah, but I don't think it really could without attaching the information out of band to the call, which would make this a stateful operation...no bueno! Also, this is a one-off plugin...a barbican core adapter to a different set of plugins. I think it's fair to treat it in a one-off way.21:24
aleeok - If I can't think of anything else thats clever - I'll approve it.21:26
woodsteralee: ha! that's cool, thanks21:26
aleewoodster, I thought though that we were going to try to get rid of all the repos being passed around ..21:26
woodsteralee: I wanted this CR to get landed first (which converts some of the repos to module singletons), then follow up with a CR that removes them all using that same pattern (whichever pattern gets accepted in this CR).21:27
aleeok21:28
*** nkinder has quit IRC21:39
*** akoneru has quit IRC21:59
*** alee has quit IRC22:04
atiwariwoodster, yt?22:39
*** akoneru has joined #openstack-barbican22:49
openstackgerritA change was merged to openstack/barbican: Additional work on certificate processing  https://review.openstack.org/11695623:02
*** nkinder has joined #openstack-barbican23:05
*** alee has joined #openstack-barbican23:08
*** atiwari has quit IRC23:09
*** arunkant_work has quit IRC23:18
*** akoneru has quit IRC23:26
rm_workanyone around? jvrbanac ?23:30
rm_workwoodster?23:30
*** SheenaG1 has joined #openstack-barbican23:40
*** SheenaG11 has joined #openstack-barbican23:43
*** SheenaG1 has quit IRC23:45
*** openstackgerrit has quit IRC23:46
*** jamielennox|away is now known as jamielennox23:47
*** openstackgerrit has joined #openstack-barbican23:47
rm_workso, I have a draft of an alternate __str__ format for the client objects, going to submit it as a possible thing, could always roll it back.23:54
rm_workor, maybe I'll wait for Juan to be on at the same time as me so we can talk about it :P23:55

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