Thursday, 2017-07-13

*** bobh has quit IRC00:52
*** bobh has joined #openstack-mistral01:37
*** weshay is now known as weshay_pto02:01
*** bobh_ has joined #openstack-mistral02:18
*** bobh has quit IRC02:19
*** bobh_ has quit IRC03:10
*** bobh has joined #openstack-mistral03:21
*** bobh has quit IRC03:35
*** gkadam has joined #openstack-mistral03:59
openstackgerritMerged openstack/mistral master: Updated from global requirements  https://review.openstack.org/48305704:08
*** sharatss has joined #openstack-mistral04:56
sharatssapetrich, hi05:00
sharatssi submitted patch on https://review.openstack.org/#/c/480368/ it passes gate now05:00
*** jtomasek_ has joined #openstack-mistral05:07
*** jtomasek has quit IRC05:23
*** jtomasek_ has quit IRC05:31
apetrichsharatss, morning05:43
apetrichlooking05:43
sharatssapetrich, ok :)05:44
apetrichsharatss, ok need more coffee I was looking at version 5 not 6 :)05:44
sharatssapetrich, hahaha... pls have some05:46
sharatssapetrich, if u find any time i need some guidance with this https://review.openstack.org/#/c/458515/05:59
*** d0ugal has quit IRC06:33
*** FL1SK has quit IRC06:53
*** d0ugal has joined #openstack-mistral07:10
*** d0ugal has quit IRC07:18
openstackgerritjunbo.li proposed openstack/mistral master: Tests: Use recommended assertion  https://review.openstack.org/48323707:24
*** jpich has joined #openstack-mistral07:38
*** mgershen has joined #openstack-mistral07:43
*** shardy has joined #openstack-mistral07:52
openstackgerritGergely Csatari proposed openstack/mistral master: Adding warning-is-error to doc building  https://review.openstack.org/48325408:13
openstackgerritjunbo.li proposed openstack/mistral master: Update reference link to Ocata  https://review.openstack.org/48325508:13
openstackgerritjunbo.li proposed openstack/mistral master: Update reference link to Ocata  https://review.openstack.org/48325508:14
*** jtomasek_ has joined #openstack-mistral08:34
*** mgershen has quit IRC08:38
*** d0ugal has joined #openstack-mistral08:42
*** dtantsur|afk is now known as dtantsur08:52
*** FL1SK has joined #openstack-mistral08:53
*** d0ugal has quit IRC09:15
*** sharatss has quit IRC09:44
*** jpich has quit IRC10:35
*** jpich has joined #openstack-mistral10:38
*** jkilpatr has quit IRC11:01
*** khandhedia has joined #openstack-mistral11:09
khandhediaIs there any way to perform run-action through ReST API. I don't see such details here https://docs.openstack.org/mistral/latest/api/v2.html#actions Is it that I must create a workflow to test the action through ReST?11:09
thrashkhandhedia: you need to create an action execution.11:26
thrashhttps://docs.openstack.org/mistral/latest/api/v2.html#action-executions11:27
*** dprince has joined #openstack-mistral11:27
khandhediathrash: Thanks. I see these are get APIs. As in, I can get all executions (../executions) or get a specific execution (../execution/<execution-id>). But, I am not able to create an execution for an existing action.11:35
thrashkhandhedia: interesting... the docs look incomplete.11:36
*** dprince_ has joined #openstack-mistral11:37
*** dprince_ has quit IRC11:37
thrashkhandhedia: I will look into that... In the meantime, a POST to /executions or /action-executions should do the trick.11:38
thrashPOST to /executions will create a workflow execution, and /action-execution runs an action11:39
thrashbut yeah... that's a problem with the docs11:39
*** jkilpatr has joined #openstack-mistral11:39
rbradythrash: if you can, file a quick doc bug with a link to the part that's incomplete11:40
khandhediathrash: let me try with that. I will try to check out some sample for json request body.11:40
thrashrbrady: already in process11:40
rbradythrash: woot!11:40
thrashrbrady: https://bugs.launchpad.net/mistral/+bug/170411311:42
openstackLaunchpad bug 1704113 in Mistral "The API docs appear incomplete" [Undecided,New]11:42
rbradythrash: thanks!11:42
*** d0ugal has joined #openstack-mistral11:42
*** d0ugal has quit IRC11:47
khandhediahttps://bugs.launchpad.net/mistral/+bug/1704113/comments/111:51
openstackLaunchpad bug 1704113 in Mistral "The API docs appear incomplete" [Undecided,New]11:51
thrashkhandhedia: rbrady simple fix coming up!12:04
thrash:D12:04
khandhediathrash: Thank you! BTW, do we have sample request for /executions? May be some paste?12:05
thrashhttp://paste.openstack.org/show/615251/12:06
openstackgerritBrad P. Crochet proposed openstack/mistral master: Make the API docs fully generate  https://review.openstack.org/48332012:10
*** mgershen has joined #openstack-mistral12:13
thrashrbrady: ^^^12:26
*** khandhedia has quit IRC12:39
openstackgerritOpenStack Proposal Bot proposed openstack/mistral master: Updated from global requirements  https://review.openstack.org/48333312:40
*** d0ugal has joined #openstack-mistral12:56
*** catintheroof has joined #openstack-mistral12:56
*** d0ugal has quit IRC13:07
*** gkadam has quit IRC13:08
*** deep-book-gk_ has joined #openstack-mistral13:09
*** deep-book-gk_ has left #openstack-mistral13:10
*** d0ugal has joined #openstack-mistral13:18
*** d0ugal has quit IRC13:18
*** d0ugal has joined #openstack-mistral13:18
*** d0ugal has quit IRC13:20
*** d0ugal has joined #openstack-mistral13:20
*** bobh has joined #openstack-mistral13:28
*** d0ugal has quit IRC13:29
*** jkilpatr has quit IRC13:42
openstackgerritRyan Brady proposed openstack/mistral-extra master: [WIP] Port keystone utils to mistral-extra  https://review.openstack.org/48339713:45
*** jkilpatr has joined #openstack-mistral13:47
openstackgerritOpenStack Proposal Bot proposed openstack/mistral master: Updated from global requirements  https://review.openstack.org/48333314:16
openstackgerritOpenStack Proposal Bot proposed openstack/python-mistralclient master: Updated from global requirements  https://review.openstack.org/48342014:24
*** jtomasek_ is now known as jtomasek14:53
*** bobh has quit IRC15:01
*** toure is now known as toure|afk15:18
*** jkilpatr has quit IRC15:23
*** bobh has joined #openstack-mistral15:44
*** dtantsur is now known as dtantsur|afk16:02
apetrichthrash, O16:05
apetrichthrash, I've -1ed it because https://review.openstack.org/#/c/483254/ is doing the same. Do you feel that we should do that in two different patches I'll remove the -116:06
thrashapetrich: wfm. I'll abandon mine.16:09
thrashmgershen: can you +2 ^^^ instead?16:09
*** jpich has quit IRC16:09
*** jtomasek has quit IRC16:10
mgershensure :)16:14
mgershenthrash: done16:16
thrashmgershen: thanks!16:16
*** jamielennox has quit IRC16:19
*** dprince has quit IRC16:21
*** chlong has joined #openstack-mistral16:30
*** chlong has quit IRC16:32
*** chlong has joined #openstack-mistral16:33
*** dprince has joined #openstack-mistral16:49
*** shardy has quit IRC16:58
*** jkilpatr has joined #openstack-mistral17:18
*** jkilpatr has quit IRC17:26
*** harlowja has quit IRC17:27
*** FL1SK has quit IRC18:04
*** mgershen has quit IRC18:05
*** jkilpatr has joined #openstack-mistral18:16
*** thrash is now known as thrash|brb18:17
*** thrash|brb is now known as thrash18:31
*** mnaser has joined #openstack-mistral18:33
mnaseri'm thinking of using mistral to do things like build images with dib on demand18:35
mnaseris that a good idea.. or?18:35
*** jamielennox has joined #openstack-mistral18:37
mnaseralso anywhere i can find some sample workflows?18:39
*** harlowja has joined #openstack-mistral18:54
apetrichmnaser, I think the ansible workflow and tripleo-quickstart18:59
mnaserapetrich i found this too https://github.com/openstack/mistral-extra18:59
rbradymnaser: not a bad idea.  you might need to build a custom action to wrap dib, but there should be existing swift/glance/glare actions for storage needs19:01
mnaserrbrady im thinking that id have to spin up a vm and do the work inside it, but the one interesting thing is how i can get permissions for openstack inside the vm19:01
mnaserex: uploading to glance from the VM that build it19:01
rbradymsaser: ssh19:02
mnaserrbrady: yeah i figured i can use the std.ssh but how can i get access to the "trust" or token which i can then use to upload to glance19:14
mnaseris that somehow shipped as an env variable.. am i missing something obvious?19:14
rbradymnaser: push it to the vm via metadata service?19:18
mnaserrbrady that's a pretty good idea19:18
openstackgerritBrad P. Crochet proposed openstack/mistral master: Cleanup docs to include params  https://review.openstack.org/48351719:19
thrashrbrady: ^^^ doc rabbit hole19:19
thrashrbrady: hopefully not too crazy. :D19:20
thrashhmmm... Could you create a custom action whose output is an image??19:21
thrashWould that be stupid?19:22
thrashlol19:22
rbradythrash: aren't action results stored in the db?  if so, I think you might run into an issue19:23
rbradythrash: I was thinking you could create an action that created the image and pushed to storage, but mnaser wanted to do it in a VM19:24
rbradythrash: hmm...what about starting a container to build the image and passing the token in as an arg?19:25
mnaserrbrady the reason behind not doing it that way is that i dont want the mistral-executor process to possibly create a giant file and cause issues on the controller19:25
mnaserso putting it in a VM will cause a good amount of isolation19:25
thrashmnaser: yeah... that makes sense.19:25
thrashmnaser: you'd really be better off doing most of it via std.ssh I think...19:26
thrashlike rbrady said.19:26
mnaseryeah i think i'll maybe do something like install all the packages required first and then another one which builds the actual image19:26
mnaserand then figure out a way to get access to the token (is there an action for that?) to pass via metadata19:26
thrashthis is some inception-level stuff. lol19:28
thrashrbrady: TODO: mistral-extra README is crap19:29
rbradythrash: ack19:30
thrashrbrady: still basically just mentions examples...19:30
thrashmnaser: RE: token... not that I'm aware of..19:30
thrashmnaser: unless it can be done via keystone actions19:31
thrashmnaser: which is you most likely vector19:31
thrash*your19:31
thrashrbrady: thoughts? ^^^19:33
rbradyyou can get the token from the context within the action19:35
rbradythe vm instance would need to retrieve via metadata service19:36
thrashw00t!19:36
thrashhehe19:36
rbradyyou just need to see if there is a client for the metadata service already in the openstack actions19:36
*** rbrady is now known as rbrady-biab19:36
*** thrash is now known as thrash|brb19:55
mnaserhttps://docs.openstack.org/mistral/latest/admin/dsl_v2.html20:03
mnaserword-for-word the create_vm is failing?20:03
mnaserYaqlEvaluationException: Can not evaluate YAQL expression:  $.vm_id , data = {}; error: u'vm_id'20:03
*** FL1SK has joined #openstack-mistral20:03
*** thrash|brb is now known as thrash20:08
mnasermore specifically i am running to the exact issue here - https://bugs.launchpad.net/mistral/+bug/159912220:08
openstackLaunchpad bug 1599122 in Mistral "execution-create of standard workflow fails with yaql error" [High,Fix released] - Assigned to Shaik Apsar (sa709c)20:08
*** harlowja has quit IRC20:19
*** harlowja has joined #openstack-mistral20:22
*** rbrady-biab is now known as rbrady20:45
*** dprince has quit IRC20:50
*** chlong has quit IRC20:52
openstackgerritMerged openstack/mistral master: Adding warning-is-error to doc building  https://review.openstack.org/48325421:30
*** rbrady is now known as rbrady-afk21:31
*** bobh has quit IRC22:19
*** catintheroof has quit IRC23:03
*** vishwanathj has quit IRC23:53
*** vishwanathj has joined #openstack-mistral23:54

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