We deploy our sling instances inside a Karaf [1] or ServiceMix [2] container, as opposed to the launchpad, so we can use features [3] to deploy sling and our applications. This allows us to deploy builds rather quickly, while also providing a central location for us to track the matrix of versions of our bundles and roll them all up into a single version of our feature. This also lets us pull bundles in from either a maven repo (Nexus) or and ORB repo (also Nexus for us).
[1] http://karaf.apache.org/ [2] http://servicemix.apache.org/home.html [3] http://karaf.apache.org/46-provisioning.html -- Mike -- mike moulton | meltmedia [email protected] w | 602.648.6810 c | 602.432.2568 @mmoulton On Jan 20, 2011, at 8:11 AM, Vidar Ramdal wrote: > I have been thinking about an easier way to upgrade our application, > which now consists of something like 100 bundles. We run on multiple > servers, and upgrading them bundle-by-bundle is really tedious. > > I know I can update bundles directly from an OSGi repository, via the > web console at http://localhost:8080/system/console/obr, but it still > requires to locate and deploy one bundle at a time. > > So how about a web console which allows me to upload an XML list, for > example on the same format used by the Maven Launchpad plugin. > The list of bundles will be compared to the set of currently deployed > bundles. Any bundle in the list which is not currently deployed, will > be downloaded, installed and started. Updated bundles, that is, the > bundle list contains a bundle in a newer version than a bundle > currently running, will be updated. And finally, bundles that are > currently deployed, but not in the list, will be uninstalled. > > Does this make sense as an extension to Sling? > > -- > Vidar S. Ramdal <[email protected]> - http://www.idium.no > Sommerrogata 13-15, N-0255 Oslo, Norway > + 47 22 00 84 00 > Quando omni flunkus moritatus!
