Open Stack

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?

$0.02

-S



On 03/05/2014 10:50 PM, Dmitri Zimine wrote:
> Folks, 
> 
> 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?
> 
> DZ> 
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>