Re: [Openstack] [Nova-orchestration] Thoughts on Orchestration (was Re: Documentation on Caching)

2012-04-03 Thread Ziad Sawalha
Just confirming what Sandy said; I am playing around with SpiffWorkflow. I'll post my findings when I'm done on the wiki under the Nova Orchestration page. So far I've found some of the documentation lacking and concepts confusing, which has resulted in a steep learning curve and made it

Re: [Openstack] [Nova-orchestration] Thoughts on Orchestration (was Re: Documentation on Caching)

2012-04-03 Thread Sandy Walsh
: [Openstack] [Nova-orchestration] Thoughts on Orchestration (was Re: Documentation on Caching) Just confirming what Sandy said; I am playing around with SpiffWorkflow. I'll post my findings when I'm done on the wiki under the Nova Orchestration page. So far I've found some of the documentation lacking

Re: [Openstack] [Nova-orchestration] Thoughts on Orchestration (was Re: Documentation on Caching)

2012-04-03 Thread Yun Mao
Hi Ziad, Thanks for taking the effort. Do you know which ones out of the 43 workflows patterns are relavant to us? I'm slightly concerned that SpiffWorkflow might be an overkill and bring unnecessary complexity into the game. There was a discussion a while ago suggesting that relatively simple

Re: [Openstack] [Nova-orchestration] Thoughts on Orchestration (was Re: Documentation on Caching)

2012-03-29 Thread Sriram Subramanian
Guys, Sorry for missing the meeting today. Thanks for the detailed summary/ logs. I am cool with the action item : #action sriram to update the Orchestration session proposal. This is my understanding the logs of things to be updated in the blueprint: 1) orchestration service provides state

Re: [Openstack] [Nova-orchestration] Thoughts on Orchestration (was Re: Documentation on Caching)

2012-03-29 Thread Dugger, Donald D
Sriram- Great, this matches my understanding of what we agreed to today. Tnx for agreeing to update the BP. -- Don Dugger Censeo Toto nos in Kansa esse decisse. - D. Gale Ph: 303/443-3786 -Original Message- From: Sriram Subramanian [mailto:sri...@computenext.com] Sent: Thursday,