Thursday, 2017-03-09

*** catintheroof has quit IRC00:46
*** zhurong has joined #openstack-mistral00:46
*** jkilpatr has joined #openstack-mistral02:05
*** jkilpatr has quit IRC02:10
*** Kevin_Zheng has joined #openstack-mistral02:17
*** thrash is now known as thrash|g0ne02:18
*** gongysh has joined #openstack-mistral02:28
*** sharatss has quit IRC03:21
*** sharatss has joined #openstack-mistral03:22
*** sharatss has quit IRC03:27
*** sharatss has joined #openstack-mistral03:28
*** jamielennox is now known as jamielennox|away04:13
*** jamielennox|away is now known as jamielennox04:47
openstackgerritRyan Brady proposed openstack/mistral-lib master: Adds minimum common shared code for custom actions API  https://review.openstack.org/41141204:53
*** gongysh has quit IRC05:16
*** gongysh has joined #openstack-mistral06:01
d0ugaljoanna: Are you looking to use Mistral from another OpenStack project?06:47
*** jamielennox is now known as jamielennox|away07:09
*** jamielennox|away is now known as jamielennox07:27
*** shardy has joined #openstack-mistral08:10
openstackgerritDougal Matthews proposed openstack/mistral-specs master: Add AUTHORS to the .gitignore  https://review.openstack.org/44346708:13
openstackgerritDougal Matthews proposed openstack/mistral-specs master: Force the docs to be built with Python 2  https://review.openstack.org/44346808:14
openstackgerritDougal Matthews proposed openstack/mistral-specs master: Add the Pike section headers and links  https://review.openstack.org/44347708:20
*** jaosorior has joined #openstack-mistral08:28
openstackgerritJuan Antonio Osorio Robles proposed openstack/python-mistralclient master: Use generic keystone client instead of versioned  https://review.openstack.org/44311808:42
*** jpich has joined #openstack-mistral08:53
openstackgerritJuan Antonio Osorio Robles proposed openstack/mistral master: Use generic keystone client instead of versioned  https://review.openstack.org/44311708:56
jaosoriord0ugal: found the issue! could you check it out https://review.openstack.org/#/c/443118/ ?09:34
jaosoriorrakhmerov: if you have a chance https://review.openstack.org/#/c/443118/09:36
d0ugaljaosorior: yup, looking in a min09:42
bretoncan i schedule instance shutdown with second-precision?10:18
bretoni know that mistal has cron triggers, but are there "at" triggers?10:27
openstackgerritMerged openstack/mistral-dashboard master: Add test for mistral-dashboard action_executions  https://review.openstack.org/43828010:36
*** gongysh has quit IRC10:44
bretonnow i am thinking of doing something stupid with wait-before10:55
bretonbut it seems to be not HA10:55
d0ugalbreton: so you want to schedule a one off workflow?10:57
d0ugalbreton: You can use a combination of --pattern --first-time and --count to run something once at a specific time/date11:01
d0ugalmistral cron-trigger-create --pattern "* * * * *" --first-time "2017-03-10 00:00" --count 111:02
d0ugal^ that should run it once only at the start of tomorrow11:02
d0ugal(note: I have never actually used this feature)11:02
*** thrash|g0ne is now known as thrash11:19
*** vishwanathj has quit IRC11:29
*** vishwanathj has joined #openstack-mistral11:29
bretond0ugal: nice. Can i do it at a specific second?11:43
d0ugalbreton: good question, I'm not sure.11:44
d0ugalbreton: it is stored as a standard datetime, so that suggests that you can11:45
d0ugalbut I am not sure where the code is that parses it from a string, I guess that is the place to check11:45
d0ugalor you could just try :)11:45
d0ugalbreton: it seems not. https://github.com/openstack/mistral/blob/e6a1ac2b5371d1887122571b209d4154218b9c05/mistral/services/triggers.py#L70-L7311:46
bretonwhat i want to do high-level is billing that would disable instances at specific time, based on $ left on account. Since the price per second is known, i can calculate the time. And i need something to trigger at that time.11:50
*** zhurong has quit IRC12:08
*** shardy is now known as shardy_lunch12:32
*** gongysh has joined #openstack-mistral12:43
*** shardy_lunch has quit IRC12:45
*** shardy_lunch has joined #openstack-mistral12:45
*** jkilpatr has joined #openstack-mistral12:56
*** sharatss has quit IRC12:59
*** sharatss has joined #openstack-mistral12:59
*** jaosorior is now known as jaosorior_brb13:03
*** jkilpatr has quit IRC13:04
*** jkilpatr has joined #openstack-mistral13:06
*** sharatss has quit IRC13:10
*** sharatss has joined #openstack-mistral13:11
*** jkilpatr has quit IRC13:12
*** rbrady-afk is now known as rbrady13:13
openstackgerritMerged openstack/mistral master: Updated from global requirements  https://review.openstack.org/44335513:13
d0ugalbreton: makes sense - I'm not sure Mistral can guarantee second precision13:15
*** jkilpatr has joined #openstack-mistral13:16
*** jkilpatr has quit IRC13:22
*** sharatss has quit IRC13:22
*** sharatss has joined #openstack-mistral13:23
*** sharatss has quit IRC13:25
*** fultonj has joined #openstack-mistral13:26
*** sharatss has joined #openstack-mistral13:26
*** shardy_lunch is now known as shardy13:27
*** chlong_ has joined #openstack-mistral13:33
*** gongysh has quit IRC14:08
ddejad0ugal: It can't14:08
d0ugal:)14:08
ddejadue to how the trigger scheduler is build14:08
d0ugalbreton: ^ so maybe Mistral isn't a good choice if you need billing precision14:09
ddejaif we have a wf that we want to start at, for example 5:30:00, mistral only guarantes that it would start no sooner than 5:30:0014:09
d0ugalright14:10
ddejabut it may start a few second later, especially if there would be a lot of triggers specified for given time14:10
d0ugalor lots of other workflows already running I guess14:10
ddejayes14:10
ddejahm, that's interesting case to be honest14:11
ddejaI will be able to prepare a scenario where trigger is not start at all for a day, as an example14:12
d0ugalheh14:12
d0ugalbecause there is a large queue already?14:12
ddejaof course, it would be a prepared scenario, I don't belive such case would ever be observed naturally14:12
ddejad0ugal: basically, yes, schedule a ton of workflow with std.sleep action in it14:13
d0ugallol14:13
d0ugalbasically DOS mistral :)14:13
ddejayeah14:13
ddejawell no, that will probably not work14:15
bretonwell, i think this scenario can be prepared for any non- real-time system ;)14:15
ddejabut running milion of times mitral run-action std.sleep seconds=55 should break it ;)14:15
ddejabreton: I guess so14:15
ddejawell, no, the second scenario will also not work due to 1 minute timeouts14:16
ddejaok, no, I think it's not that easy to postpone a trigger execution for longer than 1 minute14:16
ddejadespite having a lot of triggeres scheduled for same hour14:17
ddejawe are iterating over them one-by-one, so it can take time14:17
ddejait's only a few miliseconds per trigger, but still14:18
* ddeja should not be thinking this much about breaking mistral14:18
d0ugalddeja: 1 minute timeout?14:18
bretonwell, in my environment i can kindly ask folks not to do what you are describing :)14:19
ddejad0ugal: that14:19
ddejad0ugal: that's the default timeout for rpc calls14:19
d0ugalddeja: aha, but an action can run for more than 1 minute14:19
ddejad0ugal: yes, sure14:20
ddejabut engine will be accepting next calls14:20
d0ugalbreton: life is easier when you can trust your users :)14:20
d0ugalddeja: right14:20
ddejaso it can send requests to another executor14:20
ddejait is safe to have executor in threading mode14:20
ddejasince it is not touching the db14:20
*** jaosorior_brb is now known as jaosorior14:43
*** amoralej has joined #openstack-mistral14:51
amoralejhi mistral, i've reported in https://bugs.launchpad.net/mistral/+bug/1671505 an issue we are facing while running mistral tempest jobs in rdo-ci14:52
openstackLaunchpad bug 1671505 in Mistral "Tempest errors running mistral-api as wsgi in apache" [Undecided,New]14:52
amoralejlet me know if you need any help to access logs or i can help in any way14:52
*** chlong_ has quit IRC15:17
*** sharatss has quit IRC15:22
*** jaosorior has quit IRC15:59
*** jaosorior has joined #openstack-mistral16:19
*** fultonj has quit IRC16:30
*** shardy has quit IRC17:21
*** jpich has quit IRC17:26
*** jaosorior has quit IRC17:29
*** rbrady is now known as rbrady-afk17:51
*** amoralej is now known as amoralej|off18:31
*** rbrady-afk has quit IRC18:32
*** rbrady has joined #openstack-mistral18:46
*** chlong_ has joined #openstack-mistral20:47
*** toure is now known as toure|gone21:01
*** gyee has joined #openstack-mistral21:11
*** jaosorior has joined #openstack-mistral21:25
*** jaosorior has quit IRC21:33
*** gyee has quit IRC21:51
*** gyee has joined #openstack-mistral22:24
*** catintheroof has joined #openstack-mistral22:39
*** jamielennox is now known as jamielennox|away22:42
*** jtomasek has quit IRC22:44
*** jamielennox|away is now known as jamielennox22:45
*** jtomasek has joined #openstack-mistral22:47
*** gyee has quit IRC22:48
*** gyee has joined #openstack-mistral23:00
*** gyee has quit IRC23:04
*** gyee has joined #openstack-mistral23:07
*** chlong_ has quit IRC23:21
*** gyee has quit IRC23:33

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