Stefan Seifert wrote > discussed at the Sling Committer Round Table @ adaptTo() 2016 > > currently we have Slind launchpad with a quite monolithic configuration [1] > one big list of all sling bundles), and we have a karaf feature repository > [2] with nicely cut features for different aspects of sling, allowing the > deployer to choose which sling features are wanted and which not, and which > are the dependencies. oliver did today a talk on karaf/sling [3]. > > the launchpad should be split up in separates features/provisioning fragments > to make it possible to easily build a "minimal launchpad" or "minimal > launchpad + X" by selection only some but not all features. > > both launchpad features and karaf features should share a common source to > avoid maintaining both in parallel. one could be generated from the other. >
Atm the provisioning model has a slightly larger function set as karaf features. We have support for framework properties and things like the repo init stuff. The text based format is also easier to diff than XML. The OSGi alliance defines a YAML format for configurations which I would like to directly support in the provisioning model (or whatever we use as the source). And we have tooling like crankstart that can take a provisioning model directly and launch the instance. This all leads me to the suggestion that we keep the provisioning model and generate the karaf features xml out of this. As the provisioning model supports features already we can directly create the features in the launchpad provisioning model as they are currently defined for karaf. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
