[openstack-dev] [Mistral] Crack at a "Real life" workflow
harlowja at yahoo-inc.com
Thu Mar 6 15:26:39 UTC 2014
That sounds a little similar to what taskflow is trying to do (I am of course biased).
I agree with letting the native language implement the basics (expressions, assignment...) and then building the "domain" ontop of that. Just seems more natural IMHO, and is similar to what linq (in c#) has done.
My 3 cents.
Sent from my really tiny device...
> On Mar 6, 2014, at 5:33 AM, "Sandy Walsh" <sandy.walsh at RACKSPACE.COM> wrote:
> DSL's are tricky beasts. On one hand I like giving a tool to
> non-developers so they can do their jobs, but I always cringe when the
> DSL reinvents the wheel for basic stuff (compound assignment
> expressions, conditionals, etc).
> YAML isn't really a DSL per se, in the sense that it has no language
> constructs. As compared to a Ruby-based DSL (for example) where you
> still have Ruby under the hood for the basic stuff and extensions to the
> language for the domain-specific stuff.
> Honestly, I'd like to see a killer object model for defining these
> workflows as a first step. What would a python-based equivalent of that
> real-world workflow look like? Then we can ask ourselves, does the DSL
> make this better or worse? Would we need to expose things like email
> handlers, or leave that to the general python libraries?
>> On 03/05/2014 10:50 PM, Dmitri Zimine wrote:
>> I took a crack at using our DSL to build a real-world workflow.
>> Just to see how it feels to write it. And how it compares with
>> alternative tools.
>> This one automates a page from OpenStack operation
>> guide: http://docs.openstack.org/trunk/openstack-ops/content/maintenance.html#planned_maintenance_compute_node
>> Here it is https://gist.github.com/dzimine/9380941
>> or here http://paste.openstack.org/show/72741/
>> I have a bunch of comments, implicit assumptions, and questions which
>> came to mind while writing it. Want your and other people's opinions on it.
>> But gist and paste don't let annotate lines!!! :(
>> May be we can put it on the review board, even with no intention to
>> check in, to use for discussion?
>> Any interest?
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev