Monday, 2016-11-21

*** Mudpuppy has quit IRC01:41
*** valw has joined #craton01:48
*** Mudpuppy has joined #craton02:05
*** harlowja has quit IRC02:57
*** valw has quit IRC04:25
*** valw has joined #craton04:26
*** valw has quit IRC04:31
*** Mudpuppy has quit IRC04:58
*** tojuvone has joined #craton06:13
*** valw has joined #craton06:27
*** valw has quit IRC06:32
*** tojuvone_ has joined #craton06:51
*** tojuvone__ has joined #craton06:51
*** tojuvone__ has quit IRC06:52
*** tojuvone has quit IRC06:52
*** tojuvone_ has quit IRC06:52
*** tojuvone has joined #craton07:01
suloo/08:49
*** valw has joined #craton10:29
*** valw has quit IRC10:33
*** tojuvone has quit IRC11:42
*** tojuvone has joined #craton11:46
-openstackstatus- NOTICE: We are currently having capacity issues with our ubuntu-xenial nodes. We have addressed the issue but will be another few hours before new images have been uploaded to all cloud providers.12:17
sulois http://paste.openstack.org/show/589870/ something on client side13:24
sulo?13:24
*** VW has joined #craton13:33
sigmavirussulo: looks to be13:41
sulosigmavirus: yeah it looks to be missing a few things13:43
sigmavirusI wouldn't phrase it that way14:00
sigmavirusbut I'll take a clook at it14:00
suloprocess_header is missing too ... i know you are wokring on redoing a few things there .. so i am wondering14:03
suloif i should wait untill that to do the functional test thing14:04
suloor maybe just do with requests for now ? and change to use client later14:04
sigmavirusOh I didn't realize you were doing functional testing with the client. yeah, I would not suggest that ever14:05
suloever ?14:05
sigmavirusProjects tend to use requests directly. It more closely resembles what a regular user might do who isn't tied to python14:05
suloright14:05
sigmavirus(because requests is rather generic in how it works014:05
sulook, sounds good to me .. thats what i was doing to begin with .. i thought you jimbaker wanted client used there14:06
sulomy misunderstanding14:06
*** valw has joined #craton14:30
*** valw has quit IRC14:35
jimbakersulo, sigmavirus, others - meeting in 2 min14:59
jimbakergit-harry, ^^^14:59
jimbakerpalendae, ^^^15:02
jimbakerin #openstack-meeting-4 of course15:02
palendaeHere, vidyo? Have another video meeting at this time15:02
jimbakerpalendae, no, just our usual scheduled irc meeting15:03
palendaeRoger15:03
jimbakerpalendae, but totally optional for you :)15:03
palendaeWill at least lurk. Also pop it on my calendar15:03
jimbakerpalendae, sounds good15:03
jimbakeri can send you the invite15:03
*** Mudpuppy has joined #craton15:11
*** valw has joined #craton15:20
*** VW has quit IRC15:26
*** valw has quit IRC15:31
*** valw has joined #craton15:32
*** valw has quit IRC15:33
*** valw has joined #craton15:33
*** valw has quit IRC15:35
tojuvoneHi guys15:35
*** valw has joined #craton15:36
sigmavirusHo tojuvone!15:36
sigmavirus*Hi15:36
sigmavirusI see you found your way from the mailing list :)15:36
tojuvoneyeah :) Otherwise not that far..15:36
tojuvoneI'm strugling my devstack env after which can continue to setup craton on it15:37
sulojimbaker: git-harry: sigmavirus: oops i totally lost track of time here .. missed the meeting ... reading log now15:39
jimbakersulo, no worries15:40
jimbakersulo, do you want to just describe your forthcoming week?15:40
jimbakeralso, https://review.openstack.org/#/c/399305/ needs to be reviewd15:41
jimbakervirtualized variables should just be a matter of being to dynamically update the resolution order with a plugin; plus some additional scaffolding15:42
sulook looks like a short meeting there ...15:42
suloyeah, so i have a few pending tasks that i need to cleanup15:42
sulotesting : https://review.openstack.org/#/c/397872/15:43
suloready for some review15:43
suloi have one more patch that i need to cleanup15:43
suloafter that i am going to start poking at workflows again15:43
jimbakersulo, cool re workflows15:43
jimbakeri suggest we start from that partial patch i started15:44
jimbakermaybe i can clean that up so you have something to build upon?15:44
jimbakeri think the db modeling is good for it15:44
sulosure15:44
sulois it in gerrit ?15:44
suloactually no i dont see anything open for that from you15:45
jimbakerhttps://gist.github.com/jimbaker/0b7b8fcebce65bbe176116d1c0b1165315:45
jimbakersulo, ^^15:45
suloah cool, thx15:45
suloi can start from that15:45
jimbakerit was too early for gerrit, at least for me :)15:45
jimbakersulo, here's some code to exercise - https://gist.github.com/jimbaker/9cfc95a1a683bb22562b2c0d87811cd015:46
jimbakerbasically i had done a partial rework of the original test code15:46
sulocool. i might team up with git-harry on that go get more eyes on it .. he is in UK so its easy to peer-program on things15:47
suloif he is up for it that is15:47
jimbakeralso the other thing to note is the complete duhh i experienced here, after talking with harlowja - https://gist.github.com/jimbaker/9cfc95a1a683bb22562b2c0d87811cd0#file-cab_workflow-py-L20215:48
git-harrysulo: sure, we can talk about it tomorrow.15:48
jimbakerif we look at the flow listener api - _task_receiver(self, state, details) means we get the new state in the arg passed; the old state is in the details15:49
sulogit-harry: ok15:49
jimbakerit's possibly questionable we are using _flow_receiver, _task_receiver - but despite the naming of those methods, they are used elsewhere in the taskflow codebase, not just in the module where they are defined15:50
jimbakersulo, anyway that first gist (the diff on models.py) should be a good start. the second gist just shows one way of how to use15:51
jimbakerafter this we need to work on the worker stuff, and nailing that down15:51
sulojimbaker: cool. i will have to refresh mysefl on all of taskflow again so ill go though all of this15:52
jimbakersulo, sounds good15:52
jimbakercertainly reach out as you see anything15:52
jimbakerbut i'm pretty happy with the db modeling i did15:52
jimbakerit seemed to capture exactly what we wanted - we could readily query a workflow for its tasks, and find out those states. with some indexing, we could have good queries on that too15:54
jimbakermeanwhile the definitions (workflow_def, task_def) are kept separate15:54
*** syed__ has joined #craton15:55
jimbakerit's possible that the description of the work performed in workflow_def, task_def captures enough. my assumption was that if we had packaged with the Dockerfile, then simply running commands sequentially against the worker would suffice15:56
jimbakerbut not described here is how the worker gets its environment variables15:57
jimbakerwhich i assume come out of variables somehow15:57
jimbakeranyway... a number of decision points we can settle on15:57
jimbakersyed__, hi15:58
syed__Hi jim15:58
jimbakersyed__, http://eavesdrop.openstack.org/meetings/craton/2016/craton.2016-11-21-15.00.html15:58
jimbakersyed__, could you give a brief standup for what you plan to work on this week?15:59
syed__I will be working over fixing the schemas for client along with tests, and some more client work. Also was looking into the raised bug called need testing for network15:59
syed__so will be try doing as much as possible in all that per this week16:00
syed__i have some sample api calls along with responses noted, so maybe i can add that to docs for regions hosts cells individually, will make it look more cooler16:00
syed__jimbaker: did we put in all the points for rbac in blueprint16:02
jimbakersyed__, no, that's what i'm working on :)16:02
syed__jimbaker: i see some interesting discussion this meeting for rbac :)16:02
syed__looking into it more16:02
jimbakersyed__, yes, that's a rough high level outline of what will be in the bp16:03
jimbakersome interesting discussion of whether to be polymorphic or not, but given that's a general approach we have taken, i don't see why a little more wouldn't hurt16:04
jimbakerimho, it has been a great modeling decision for us16:05
*** VW has joined #craton16:05
jimbakerwhy a little more *would* hurt... get my negatives straight!16:05
*** VW has quit IRC16:10
sigmavirusjimbaker: left a stream-of-consciousness style review for git-harry, sulo, and you Ib459b9824815d6cac0eaa9e544e13b90fb61ecc116:15
sigmavirusgah, copied the change-id https://review.openstack.org/40019816:15
*** VW has joined #craton16:17
jimbakersigmavirus, git-harry - nice, and i appreciate anything that simplifies our logic and use16:17
*** valw has quit IRC16:26
*** valw has joined #craton16:35
*** tojuvone has quit IRC16:50
*** jovon has joined #craton16:58
*** VW has quit IRC17:06
*** VW has joined #craton17:19
*** VW has quit IRC17:24
sigmavirusjimbaker: so, the conversation on that review is more of what I want your attention on17:33
sigmavirusI think that "simplification" is pointing out rather blatantly that the shape and semantics of our API design presently is bad17:33
*** VW has joined #craton17:34
sulosigmavirus: we talked abou change that at one point but never did17:36
sulosigmavirus: this seems to be a good time to do it, since its back in attention17:36
suloits a smallish change too .. so not too bad17:37
sigmavirusyeah17:37
*** VW has quit IRC17:38
sigmavirusbtw, sulo would you mind dumping info into a bug on https://bugs.launchpad.net/python-cratonclient about the problems you ran into with debug logging?17:38
sigmavirusJust want to link my review to a bug17:38
sulosigmavirus: will do17:38
sigmavirusThanks sulo17:38
sigmavirusYou can also just assign me out of the gate17:38
*** VW has joined #craton17:40
sigmavirusthis is going to wreak havoc on the client (when we make those URLs more logical)17:44
sigmavirusremoving the Inventory object is already going to be a huge change :/17:44
sulohttps://bugs.launchpad.net/craton/+bug/164365017:47
openstackLaunchpad bug 1643650 in craton "python-cratonclient: session object seems to be missing some properties" [Undecided,New] - Assigned to Ian Cordasco (icordasc)17:47
sigmavirusThanks sulo !17:47
suloyeah region stuff is broken too .. i didnt bother creating issues for it cuz i thought you are changing it altogether17:47
sulofor example its doing this: https://github.com/openstack/python-cratonclient/blob/master/cratonclient/v1/regions.py#L3017:48
jimbakersigmavirus, sulo - sounds good about further refactoring17:59
jimbakerof the api17:59
jimbakerthe point of filtered_context was to remove boilerplate. removing even more, or changing the api, sounds good to me18:00
*** harlowja has joined #craton18:14
sigmavirussulo: just make bugs18:36
sigmavirusbugs bugs bugs18:36
sigmavirussyed__: and jovon can pick up those bugs too if you make them18:36
sigmavirusgives them discrete work items18:36
syed__Sounds good sigmavirus18:37
jovonagreed18:37
*** valw has quit IRC18:47
*** valw has joined #craton18:49
*** valw has quit IRC19:05
*** valw has joined #craton19:07
*** valw has quit IRC19:22
*** valw has joined #craton19:23
*** valw has quit IRC19:29
*** valw has joined #craton19:34
*** VW has quit IRC20:01
*** VW has joined #craton20:01
*** VW has quit IRC20:06
*** VW has joined #craton20:10
*** valw has quit IRC20:23
*** valw has joined #craton20:23
*** valw has quit IRC20:28
*** valw has joined #craton20:29
*** valw has quit IRC20:29
*** valw has joined #craton20:30
*** valw has quit IRC20:31
*** valw has joined #craton20:31
*** VW has quit IRC21:06
*** VW has joined #craton21:06
*** VW has quit IRC21:09
*** VW has joined #craton21:10
*** Mudpuppy_ has joined #craton22:01
*** valw has quit IRC22:01
*** Mudpuppy has quit IRC22:04
*** Mudpuppy_ has quit IRC22:05
jimbaker+122:19
*** rainya has joined #craton22:28
*** rainya has quit IRC22:32
*** rainya has joined #craton22:33
*** rainya has quit IRC22:41
*** rainya has joined #craton22:44
*** VW has quit IRC22:49
*** rainya has quit IRC22:54
*** VW has joined #craton22:54
*** rainya has joined #craton22:55
*** rainya has quit IRC23:00
*** VW_ has joined #craton23:10
*** VW has quit IRC23:12
*** VW_ has quit IRC23:14
*** rainya has joined #craton23:19
*** rainya_ has joined #craton23:19
*** rainya has quit IRC23:23
*** VW has joined #craton23:39
*** openstack has joined #craton23:44
*** rainya_ has quit IRC23:54

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