Wednesday, 2017-05-24

*** rbrady has quit IRC01:35
*** rbrady has joined #openstack-mistral01:46
*** rbrady has quit IRC01:46
*** rbrady has joined #openstack-mistral01:46
*** zhurong has joined #openstack-mistral02:11
*** bobh has quit IRC02:26
*** bobh has joined #openstack-mistral02:27
*** rbrady has quit IRC02:42
*** bobh has quit IRC03:15
*** bobh has joined #openstack-mistral03:16
*** bobh has quit IRC03:19
*** rbrady has joined #openstack-mistral03:52
*** rbrady has quit IRC03:52
*** rbrady has joined #openstack-mistral03:52
*** zhurong has quit IRC04:11
*** zhurong has joined #openstack-mistral04:15
*** mattybre_ has quit IRC04:39
*** jaosorior_away is now known as jaosorior04:55
*** sharatss has joined #openstack-mistral05:18
*** bobh has joined #openstack-mistral05:20
*** bobh has quit IRC05:25
openstackgerritMerged openstack/python-mistralclient master: Updated from global requirements  https://review.openstack.org/46719905:39
openstackgerritMerged openstack/mistral master: Updated from global requirements  https://review.openstack.org/46715806:19
*** shardy has joined #openstack-mistral07:14
*** sharat has joined #openstack-mistral07:32
*** sharatss has quit IRC07:35
*** warface has joined #openstack-mistral07:39
*** jpich has joined #openstack-mistral07:48
openstackgerritMerged openstack/mistral master: Fix doc generation for python 3  https://review.openstack.org/45720408:02
openstackgerritSharat Sharma proposed openstack/python-mistralclient master: Switch from keystoneclient to keystoneauth  https://review.openstack.org/45765609:12
*** sharatss_ has joined #openstack-mistral09:19
*** sharat has quit IRC09:22
openstackgerritSharat Sharma proposed openstack/python-mistralclient master: Switch from keystoneclient to keystoneauth  https://review.openstack.org/45765609:39
warfacehey guys, is it possible to re-run the complete workflow from a specified task ?09:48
warfaceeg. https://hardbin.com/ipfs/QmdxMwy3Kbhfr9skR8Fyr5Jf2EGnKiBs4F9H9RCdn73S2k/#DjzHTNpGXEbgXpZSHQz455r2Z57FECMDdZ3kTprmHjKb09:48
warfacewhen we first run the workflow, flow is workflow1->on-error->miniworkflow209:50
warfaceafter that we have specified the task_execution_id to re-run workflow1, but neither on-success nor on-error is executed ?09:51
warfaceis it even possible ? thanks :)09:51
*** ttpl has joined #openstack-mistral09:55
*** zhurong has quit IRC10:04
d0ugalwarface: I believe so, but I have not actually attempted it.10:17
d0ugalrakhmerov: ^10:17
rakhmerovwarface: how did you try to rerun it?10:23
rakhmerovMistral supports reruning from a task10:23
rakhmerovyes10:23
d0ugalkong: have you seen this? http://lists.openstack.org/pipermail/openstack-dev/2017-May/117197.html10:25
d0ugalI don't fully understand, but it seems we are blocking releases.10:25
d0ugalprometheanfire: I don't think we are capping: https://github.com/openstack/mistral/blob/master/requirements.txt#L5610:26
d0ugalso does that just mean we need a new release proposed?10:26
prometheanfired0ugal: but we need a release with that, that's all10:26
d0ugalprometheanfire: okay, I'll propose one to get the ball rolling. thanks10:27
prometheanfirethanks10:27
rakhmerovd0ugal, prometheanfire: release from master10:28
rakhmerov?10:28
d0ugalrakhmerov: yeah10:28
rakhmerovunder what tag?10:28
prometheanfirea beta I imagine10:28
rakhmerovok10:28
prometheanfireas long as it's accessable from pypi (so requirements gets the update)10:28
d0ugalI guess we want 5.0.0.0b2 - https://github.com/openstack/releases/blob/master/deliverables/pike/mistral.yaml#L910:29
prometheanfireb1 wasn't in pypi10:29
d0ugaloh, weird.10:29
rakhmerovtags with letter don't go to pypi, afaik10:29
d0ugalso it can't be a beta?10:29
rakhmerovit's not weird, it's how pypi jobs are configured in CI10:29
prometheanfireI don't see why it can't, I'd talk to the releases team about it10:29
rakhmerovd0ugal: yep10:30
prometheanfirepypi can accept it, but the releases time probably has a policy of not publishing betas10:30
prometheanfireI was hoping one of them would be at the meeting, but I'll ask them about it today10:30
d0ugalrakhmerov, prometheanfire: https://pypi.python.org/pypi/mistral/5.0.0.0b110:30
d0ugalit is on PyPI10:31
rakhmerovlast time I was looking at it I saw a regex to filter out all releases with letters10:31
prometheanfirehmm, I'll try submitting that as a UC update to reqs then10:31
prometheanfirethat's 5.0.0.0 as well10:31
rakhmerovooh, then seems like they changed it10:31
prometheanfireodd10:31
d0ugalso it would indeed hav been weird if it wasn't :)10:31
prometheanfireanyway, nn10:32
d0ugalo/10:32
d0ugalrakhmerov: it seems like they have always been on PyPI10:32
d0ugalI see 2.0.0.0b1 for example still there10:32
d0ugaleven 1.0.0.0b1 :)10:33
rakhmerovno, not always, I bet )10:33
d0ugalhah, we even have a version 010:33
rakhmerovI assume they could publish them later10:33
d0ugalhttps://pypi.python.org/pypi/mistral/010:33
d0ugalI didn't know that was allowed10:33
rakhmerovok, so now what do we need to do?10:34
d0ugal1.0.0.0b1 was uploaded on Jun 26, 201510:34
d0ugalrakhmerov: I think nothing for now, we need to wait and see if prometheanfire can update the reqs10:34
rakhmerovrelease with 5.0.0.0b2? But it's kind of reserved for Pike-210:34
rakhmerovok10:35
d0ugalbtw, it is easier to see the package history here: https://pypi.org/project/mistral/#history10:35
d0ugalThat is the new version of PyPI - considered beta but it uses the same database10:35
d0ugalI really wish we could delete the 2015* versions.10:36
rakhmerovd0ugal: yeah, we talked to release team about it already but they said it was nearly impossible10:38
*** jkilpatr has quit IRC10:38
d0ugalhmm, maybe I'll try asking some friends that know pypi well10:39
rakhmerovwell, PyPi is not the main reason. It was mainly because they didn't want to change git history, which is kind of crazy10:40
rakhmerovbecause it's not easy to propagate deletion of certain git tags across all git repo clones10:41
rakhmerovand thus if we delete from PyPi versions would go out of sync with git history10:41
rakhmerov=> inconsistency10:41
rakhmerovbut we can try to discuss that again, the situation might have changed10:42
rakhmerovwe tried to solve it a couple of years ago10:42
d0ugalrakhmerov: I don't have a problem with slight inconsistency10:52
d0ugalbut I'm sure it must confuse some of our users that just run "pip install mistral" and get a really old version10:52
*** jkilpatr has joined #openstack-mistral10:56
rakhmerovd0ugal: I got a very strong pushback from infra and release teams when I proposed it last time10:58
rakhmerovbut I'm ok with bringing it up again10:59
rakhmerovwe can try10:59
d0ugalokay, thanks10:59
openstackgerritSharat Sharma proposed openstack/python-mistralclient master: Switch from keystoneclient to keystoneauth  https://review.openstack.org/45765611:07
*** bobh has joined #openstack-mistral11:23
*** bobh has quit IRC11:27
*** bobh has joined #openstack-mistral11:34
*** thrash|g0ne is now known as thrash11:40
openstackgerritSharat Sharma proposed openstack/python-mistralclient master: Switch from keystoneclient to keystoneauth  https://review.openstack.org/45765611:47
*** ttpl has quit IRC11:50
*** ttpl has joined #openstack-mistral11:51
*** dprince has joined #openstack-mistral12:18
*** bobh has quit IRC12:25
*** FL1SK has quit IRC12:28
*** zhurong has joined #openstack-mistral12:35
*** zhurong has quit IRC12:36
*** sharatss_ has quit IRC12:46
*** warface has quit IRC12:51
*** warface has joined #openstack-mistral12:52
*** warface has quit IRC12:57
*** rbrady has quit IRC13:13
*** rbrady has joined #openstack-mistral13:27
*** warface has joined #openstack-mistral13:36
warfacerakhmerov, d0ugal: ah, sorry, went in for a meeting that took some time13:37
warfacerunning it like:13:37
warfaceexecution-create workflow_id input.yaml '{"task_execution_id": "id of the _test_ workflow execution"}'13:39
warfaceexecution-create workflow_id input.json '{"task_execution_id": "id of the _test_ workflow execution"}'13:39
warfacethe task is running fine, but on-success is not getting executed13:40
warfaceso, just curious, is the desired behavior by deafult or am I missing something13:40
*** warface has quit IRC14:04
*** warface has joined #openstack-mistral14:06
*** mattybrennan has joined #openstack-mistral14:08
*** FL1SK has joined #openstack-mistral14:26
*** warface has quit IRC14:32
*** chlong has joined #openstack-mistral14:38
*** dprince has quit IRC14:51
*** bobh has joined #openstack-mistral15:01
*** dprince has joined #openstack-mistral15:05
*** shardy has quit IRC15:23
prometheanfired0ugal: rakhmerov https://review.openstack.org/46767716:47
prometheanfirewe'll see16:47
prometheanfire:D16:47
*** jpich has quit IRC16:51
*** fultonj has quit IRC16:59
*** fultonj has joined #openstack-mistral17:01
*** jaosorior has quit IRC17:24
*** bobh has quit IRC18:21
*** bobh has joined #openstack-mistral18:26
*** openstackgerrit has quit IRC19:48
*** openstackgerrit has joined #openstack-mistral20:06
openstackgerritToure Dunnon proposed openstack/python-mistralclient master: [WIP] Workflow Error Analysis Client updates.  https://review.openstack.org/45290120:06
*** toure is now known as toure|gone20:06
*** bobh has quit IRC20:10
*** thrash is now known as thrash|g0ne20:25
*** dprince has quit IRC20:39
*** bobh has joined #openstack-mistral20:52
*** bobh has quit IRC20:57
*** bobh has joined #openstack-mistral21:27
*** rbrady is now known as rbrady-afk21:43
*** bobh has quit IRC21:47
*** jkilpatr has quit IRC22:05
*** jkilpatr has joined #openstack-mistral22:26
*** bobh has joined #openstack-mistral22:33
*** bobh has quit IRC23:11
openstackgerritWinson Chan proposed openstack/mistral master: Implement notification of execution events  https://review.openstack.org/46779923:24

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