Thursday, 2019-01-10

*** bobh has joined #openstack-mistral02:39
*** bobh has quit IRC02:43
*** d0ugal has quit IRC03:19
*** d0ugal has joined #openstack-mistral03:33
rakhmerovjenner, hi. Ad-hoc actions (accessible via an endpoint) are stored in DB so you don't need to restart anything. When it comes to executors, it's a little tricky internally, but effectively yes, they know about the changes immediately04:34
*** hardikjasani has joined #openstack-mistral04:43
*** jrist has quit IRC04:54
*** jrist has joined #openstack-mistral05:07
*** pgaxatte has joined #openstack-mistral06:57
*** gkadam has joined #openstack-mistral07:43
jennerrakhmerov: thanks09:10
*** shardy has joined #openstack-mistral09:10
jennerwe're just trying to figure out th best deployment strategy for docker (openshift), seems like it's sufficient to just update the actions + WFs via REST09:12
*** shardy has quit IRC09:13
*** shardy has joined #openstack-mistral09:13
*** bobh has joined #openstack-mistral09:19
openstackgerritlijunjie proposed openstack/mistral master: Fix the misspelling of "default"  https://review.openstack.org/62980309:22
*** apetrich has quit IRC09:42
*** apetrich has joined #openstack-mistral09:43
*** mmethot has quit IRC09:55
*** mmethot has joined #openstack-mistral09:56
*** jaosorior has quit IRC10:00
rakhmerovjenner: yes, but keep in mind that we're talking only about ad-hoc actions. It's the kind of actions declared with YAQL and they are based on regular actions10:11
rakhmerovso essentially they are wrappers around usual actions that can transform an input and an output of a base action10:12
rakhmerovwell, actually an ad-hoc action can be also declared around another ad-hoc action, that also works10:13
rakhmerovrecursive stuff10:13
*** bobh has quit IRC10:19
pgaxatterakhmerov: are the executors aware of the adhoc definition or is it translated before sending it in the queue?10:26
pgaxatteand hi by the way :D10:26
rakhmerovpgaxatte: Hi! They are actually translated into base actions, yes :)10:27
rakhmerovthat's why I said that it's a little tricky internally10:27
rakhmerovexecutors never access DB, it's was done on purpose10:28
rakhmerovit was..10:28
pgaxatterakhmerov: yeah I imagine it's complicated10:28
pgaxatteand yeah the separataion with the DB is a nice feature10:28
rakhmerovso that executors could be installed in an environment where we don't have access to DB, for example10:28
pgaxatteexactly and this is very useful to us10:29
rakhmerovso they are very lightweight10:29
rakhmerovok10:29
pgaxattewe can executors in restricted networks for specific tasks10:29
rakhmerovyep10:29
rakhmerovmakes sense10:29
pgaxattealthough the rabbit port is usually not part of the default filtering rules :D10:30
openstackgerritMerged openstack/python-mistralclient master: Replace tripleo-scenario003-multinode with scenario003-standalone  https://review.openstack.org/62827710:33
openstackgerritDougal Matthews proposed openstack/mistral master: Replace tripleo-scenario003-multinode with scenario003-standalone  https://review.openstack.org/62827410:34
*** jaosorior has joined #openstack-mistral11:01
*** openstackgerrit has quit IRC11:05
*** shardy has quit IRC11:14
*** shardy has joined #openstack-mistral11:46
*** openstackgerrit has joined #openstack-mistral11:51
openstackgerritMerged openstack/mistral master: Fix the misspelling of "default"  https://review.openstack.org/62980311:51
*** hardikjasani has quit IRC14:21
*** shardy_ has joined #openstack-mistral14:57
*** shardy has quit IRC15:00
*** pgaxatte has quit IRC15:38
*** gkadam has quit IRC17:21
*** shardy_ has quit IRC17:53
*** jrist is now known as jrist__18:16
*** jrist has joined #openstack-mistral18:17
*** jrist__ has quit IRC18:18
*** openstackgerrit has quit IRC20:50
*** bobh has joined #openstack-mistral21:25
*** bobh has quit IRC21:33
*** bobh has joined #openstack-mistral22:09
*** bobh has quit IRC22:15

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