Hi,
2014-09-22 7:40 GMT+02:00 Bertrand Delacretaz <[email protected]>: > 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. > > Right, and I also think the same goes for the describing language :) > 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. > Right, if we have a model which also exactly describes how to merge we have a solid foundation we can built on. > 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? > > Sure, just realized I forgot to commit those :) Here you go, it's the launchpad from last week, split up in three files: http://svn.apache.org/repos/asf/sling/trunk/launchpad/slingstart/src/main/systems/ The slingstart maven launchpad plugin reads them on startup in alphabetical order. Carsten > 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 [email protected]
