I've added a first simple parser for the crankstart format, it supports
classpath, bundles and configuration for now.

Now, the major difference between crankstart and all other models is that
crankstart describes actions - most of them (like the above, start level
changes, osgi properties) can be translated into the model. Others like,
logging, stopping the instance etc. can't.
I'm not sure if we need this flexibility and/or how to handle it.

Carsten

2014-09-22 7:40 GMT+02:00 Bertrand Delacretaz <bdelacre...@apache.org>:

> Hi Carsten,
>
> On Sunday, September 21, 2014, Carsten Ziegeler <cziege...@apache.org>
> wrote:
> > I think we need a new approach to describe a deliverable or
> installation...
> > ...It would be great to have all the
> > information in a single place to make it more understandable but also to
> > allow for new ways of operations...
>
> I agree, and the Crankstart launcher [1] is exactly about this. But you're
> right that agreeing on the *model* that describes the Sling instances is
> much more important than whatever code interprets this model.
>
> I much prefer structured text formats (either plain text or yaml) over XML
> for such things, as they're more friendly to hack and especially more
> diff-friendly which is very important in a devops view. But that's a detail
> in terms of defining the model.
>
> How about creating some commented example definition files in svn (even if
> we have no code to run them so far), so we can look at each other's ideas
> and come up with a merged model of the good ideas on those files?
>
> For crankstart I can provide these files as examples that demonstrate the
> model features:
>
>
> http://svn.apache.org/repos/asf/sling/trunk/contrib/crankstart/launcher/src/test/resources/launcher-test.crank.txt
>
>
> https://github.com/ArtyomStetsenko/sling-devops-experiments/blob/master/crankstart/sling-minion.crank.txt
>
> -Bertrand
>
> >
> [1] http://svn.apache.org/repos/asf/sling/trunk/contrib/crankstart/
>



-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Reply via email to