Oooh, ok! Yeah, additional tests for that would help us clearly see that solved.

Thanks!

Renat Akhmerov
@ Mirantis Inc.



> On 03 Mar 2015, at 18:03, Peter Razumovsky <prazumov...@mirantis.com> wrote:
> 
> Hi Renat,
> 
> We solved problem with referencing. I'll add more tests for understanding, 
> how Mistral Workflow resource look like in Heat template. 
> 
> 
> 2015-03-03 14:35 GMT+03:00 Renat Akhmerov <rakhme...@mirantis.com 
> <mailto:rakhme...@mirantis.com>>:
> Hi Peter,
> 
> Thanks for sharing this.. Overall it looks good to me, I just left a couple 
> of comments/questions in 
> https://review.openstack.org/#/c/147645/17/contrib/heat_mistral/heat_mistral/tests/test_workflow.py
>  
> <https://review.openstack.org/#/c/147645/17/contrib/heat_mistral/heat_mistral/tests/test_workflow.py>
>  Could you please take a look?
> 
> We keep in mind that one thing is still not implemented: workflow references 
> get broken if we upload a workflow which calls another workflow. We need to 
> discuss the best way to deal with that. Either we need to do in Heat itself 
> to restore those references accounting for stack name etc.. Or we need to 
> provide some facility in Mistral itself.
> 
> Other than that it looks to be ready to start gathering Heat folks’ feedback.
> 
> Renat Akhmerov
> @ Mirantis Inc.
> 
> 
> 
>> On 26 Feb 2015, at 17:49, Peter Razumovsky <prazumov...@mirantis.com 
>> <mailto:prazumov...@mirantis.com>> wrote:
>> 
>> In anticipation of Mistral supporting in Heat, let's introduce using Mistral 
>> in Heat.
>> 1. For using Mistral resources workflow and cron-trigger in Heat, Mistral 
>> must be installed to DevStack. Installation guide for DevStack on 
>> https://github.com/stackforge/mistral/tree/master/contrib/devstack 
>> <https://github.com/stackforge/mistral/tree/master/contrib/devstack> 
>> Detailed information about Workflow and CronTrigger you can find on 
>> https://wiki.openstack.org/wiki/Mistral 
>> <https://wiki.openstack.org/wiki/Mistral> Note, that currently Mistral use 
>> DSLv2 (https://wiki.openstack.org/wiki/Mistral/DSLv2 
>> <https://wiki.openstack.org/wiki/Mistral/DSLv2>) and Rest API v2 
>> (https://wiki.openstack.org/wiki/Mistral/RestAPIv2 
>> <https://wiki.openstack.org/wiki/Mistral/RestAPIv2>).
>> 2. When Mistral will be installed, check it accessibility - in screen or 
>> using command 'mistral --help' (list of commands). You can test Mistral 
>> resources creating workflow resources with DSLv2-formatted definitions, 
>> cron-triggers and executions.
>> For example, command 'mistral workflow-list' gives the table:
>> Starting new HTTP connection (1): 192.168.122.104
>> Starting new HTTP connection (1): localhost
>> +---------------------+--------+------------------------------+---------------------+------------+
>> | Name                | Tags   | Input                        | Created at   
>>        | Updated at |
>> +---------------------+--------+------------------------------+---------------------+------------+
>> | std.create_instance | <none> | name, image_id, flavor_id... | 2015-01-27 
>> 14:16:21 | None       |
>> | std.delete_instance | <none> | instance_id                  | 2015-01-27 
>> 14:16:21 | None       |
>> +---------------------+--------+------------------------------+---------------------+------------+
>> 
>> 3. Mistral resources for Heat you can find there: 
>> https://review.openstack.org/#/q/status:open+project:openstack/heat+branch:master+topic:bp/mistral-resources-for-heat,n,z
>>  
>> <https://review.openstack.org/#/q/status:open+project:openstack/heat+branch:master+topic:bp/mistral-resources-for-heat,n,z>
>> 4. Simple templates using Mistral resources in Heat templates you can find 
>> there:
>> https://wiki.openstack.org/wiki/Heat_Mistral_resources_usage_examples 
>> <https://wiki.openstack.org/wiki/Heat_Mistral_resources_usage_examples>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org 
>> <mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
>> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe 
> <http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev 
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to