Open Stack

Renat:

Perfect. A combination of 1 and 2a would fit our needs.

One reason we are venturing toward an async workflow is to address the
scale limitation in tacker. Now, do you've some pointers how well mistral
scales (so that we don't just move our scale problem down to the mistral
dependency). Looking at the mistral architecture [*], is it safe to assume
the individual mistral components like api, engine, scheduler, executor can
be linearly scaled across different hosts ?

- Sridhar

[*] https://docs.openstack.org/developer/mistral/architecture.html

On Wed, Mar 22, 2017 at 11:22 PM, Renat Akhmerov <renat.akhmerov at gmail.com>
wrote:

> Another option:
>
> 1. Run a workflow with a loop (i.e. task calls itself), in order to have a
> delay between task executions you can use either wait-before/wait-after
> task policies
> 2.a The workflow can be stopped via Mistral API by a 3rd party, if needed.
> 2.b The workflow can have a special task that checks if it still needs to
> be running (i.e. making a request to a 3rd party), it can be done using
> conditional transitions
>
>
> Renat Akhmerov
> @Nokia
>
> On 23 Mar 2017, at 09:40, Lingxian Kong <anlin.kong at gmail.com> wrote:
>
> Yeah, as Bob said, cron-trigger is what you are looking for.
>
> As our discussion on IRC, currently, Mistral doesn't support to execute
> shell command directly, my suggestion is, you could consider using http
> action (which is supproted by Mistral out of the box) or providing a host
> (physical or virtual) to run 'ping' command and use ssh action in Mistral.
>
>
> Cheers,
> Lingxian Kong (Larry)
>
> On Thu, Mar 23, 2017 at 1:16 PM, gongys2017 <gongys2017 at aliyun.com> wrote:
>
>> Hi mistral stackers,
>>
>> Tacker is using the mistral as its part of system. Now we have a
>> requirement:
>>
>> tacker server registers an openstack as its NFVI, and needs to ping<or
>> http-ping) the openstack's management IP,
>> for example the keystone URL until tacker updates or delete the openstack
>> NFVI.
>>
>> Can the mistral be asked to start a workflow which  contains  just such a
>> kind of task:
>> for ever running until extenal tells him to stop.
>>
>>
>> Thanks
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
>> e <http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170324/5fa5d7d9/attachment.html>