[openstack-dev] [Mistral] Query on creating multiple resources

Renat Akhmerov rakhmerov at mirantis.com
Tue Dec 9 08:49:32 UTC 2014


No problem, let us know if you have any other questions.

Renat Akhmerov
@ Mirantis Inc.



> On 09 Dec 2014, at 11:57, Sushma Korati <sushma_korati at persistent.com> wrote:
> 
> 
> Hi,
> 
> Thank you guys.
> 
> Yes I am able to do this with heat, but I faced issues while trying the same with mistral.
> As suggested will try with the latest mistral branch. Thank you once again. 
> 
> Regards,
> Sushma
> 
> 
> 
>  
> From: Georgy Okrokvertskhov [mailto:gokrokvertskhov at mirantis.com <mailto:gokrokvertskhov at mirantis.com>] 
> Sent: Tuesday, December 09, 2014 6:07 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Mistral] Query on creating multiple resources
>  
> Hi Sushma,
>  
> Did you explore Heat templates? As Zane mentioned you can do this via Heat template without writing any workflows. 
> Do you have any specific use cases which you can't solve with Heat template?
>  
> Create VM workflow was a demo example. Mistral potentially can be used by Heat or other orchestration tools to do actual interaction with API, but for user it might be easier to use Heat functionality.
>  
> Thanks,
> Georgy
>  
> On Mon, Dec 8, 2014 at 7:54 AM, Nikolay Makhotkin <nmakhotkin at mirantis.com <mailto:nmakhotkin at mirantis.com>> wrote:
> Hi, Sushma! 
> 
> Can we create multiple resources using a single task, like multiple keypairs or security-groups or networks etc?
>  
> Yes, we can. This feature is in the development now and it is considered as experimental -https://blueprints.launchpad.net/mistral/+spec/mistral-dataflow-collections <https://blueprints.launchpad.net/mistral/+spec/mistral-dataflow-collections>
>  
> Just clone the last master branch from mistral.
> 
> You can specify "for-each" task property and provide the array of data to your workflow: 
> 
>  --------------------
> version: '2.0'
> 
> name: secgroup_actions
> 
> workflows:
>   create_security_group:
>     type: direct
>     input:
>       - array_with_names_and_descriptions
> 
>     tasks:
>       create_secgroups:
>         for-each: 
>           data: $.array_with_names_and_descriptions
>         action: nova.security_groups_create name={$.data.name <http://data.name/>} description={$.data.description}
> ------------
>  
> On Mon, Dec 8, 2014 at 6:36 PM, Zane Bitter <zbitter at redhat.com <mailto:zbitter at redhat.com>> wrote:
> On 08/12/14 09:41, Sushma Korati wrote:
> Can we create multiple resources using a single task, like multiple
> keypairs or security-groups or networks etc?
> 
> Define them in a Heat template and create the Heat stack as a single task.
> 
> - ZB
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org <mailto:OpenStack-dev at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> 
>  
> -- 
> Best Regards,
> Nikolay
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org <mailto:OpenStack-dev at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> 
>  
> -- 
> Georgy Okrokvertskhov
> Architect,
> OpenStack Platform Products,
> Mirantis
> http://www.mirantis.com <http://www.mirantis.com/>
> Tel. +1 650 963 9828
> Mob. +1 650 996 3284
> DISCLAIMER ========== This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails.
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org <mailto:OpenStack-dev at lists.openstack.org>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <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/20141209/b16a3f9f/attachment.html>


More information about the OpenStack-dev mailing list