[openstack-dev] [OpenStack][Mistral]A simple tool to discover and manage custom actions

Renat Akhmerov renat.akhmerov at gmail.com
Wed May 3 03:21:20 UTC 2017


Hi,

I’m joining Lingxian to say thank you for addressing this.

In addition I’d like to say that we have huge plans to rework the entire actions subsystem till the end of this year so that implementing and managing actions become really easy and enjoying. We’ll definitely look closer at your code.

We’d be happy if you joined us at #openstack-mistral IRC channel to discuss this and other things.

Thanks

Renat

On 2 May 2017, 19:35 +0700, Lingxian Kong <anlin.kong at gmail.com>, wrote:
> Hi, int32bit,
>
> First, thanks very much for your work and share with us for what you did.
>
> You are right about the lack of flexibility of current mistral action registration process, in addition to your work, here are some of my suggestions:
>
> - I recommend you work with mistral team to figure out a way to improve current tools/sync_db.py script, add the capability to manipulate actions without reinstall mistral. I believe there are other people who are also very interested in the enhancement.
> - We (mistral team) are working on mistral-lib, a new library that will define a base action class that all 3-rd party customized actions could inherit, which aims to make action developer's life easier.
>
> Thanks again for the email, feel free to jump in #openstack-mistral irc channel for any further discussion.
>
>
> Cheers,
> Lingxian Kong (Larry)
>
> > On Tue, May 2, 2017 at 8:54 PM, int32bit <krystism at gmail.com> wrote:
> > > Hi, All,
> > >
> > > As we know, Mistral allow developer  write a new custom action, but must reinstall Mistral service if it was installed in our system[1]. I think it's hardly acceptable for production environment.
> > >
> > > So I write a CLI tool used for automatically discovering & registering custom actions and no need modify any configuration and reinstall any service. In fact, it's completely independent with Mistral project.
> > >
> > > In addition, this project provide a CLI to manage custom actions, we can list all registered actions, and unregister any action if it doesn't need any more.
> > >
> > > For more detail, please see mistral-actions.
> > >
> > > It work well on our environment but not sure if there is any potential risk. Thanks for any suggest and comment.
> > >
> > >
> > > [1] https://docs.openstack.org/developer/mistral/developer/creating_custom_action.html
> > >
> > > __________________________________________________________________________
> > > 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/20170503/767299b3/attachment.html>


More information about the OpenStack-dev mailing list