felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet" <gno...@gmail.com>
Subject Re: Provisoning system
Date Fri, 28 Sep 2007 14:33:17 GMT
Thanks a lot for these detailed explanations.
After a very brief overview of pax runner, it also seems to me that
this is not a runtime / dynamic provisioning mechanism which is what
we are looking for.  But i'll try to have a deeper look nonetheless.

On 9/28/07, Alin Dreghiciu <adreghiciu@gmail.com> wrote:
> I looked at the jira issue and pax runner does not metach what you are
> trying to archive. But pax runner could be a good adition to ServiceMix as:
> 1. By using pax runner as the starter to ServiceMix (bundles) you will be
> able to target different platforms, so you will be able, with very small
> effort to start ServiceMix in equinox, felix or knopflerfish with no change
> to Service Mix (if ServiceMix does not depend on felix internals). What you
> have to do is just to use one of the provisioning schemes, mos easily being
> that you have all service mix bundles in a directory and pointing pax runner
> to that directory.
> Basically you will give the user the option on what platform to start
> Service Mix.
> 2. You could provide different profiles targeting difereent aspects of
> ServiceMix (I'm not knowledgeable to ServiceMix so I cannot give examples of
> what such profiles could be).. But bottom lines you could give the user the
> option to start service mix with a subset of service mix bundles or some
> functional combination. For example right now you can use pax runner to
> start your bundles with a web profiles meaning that beside your bundles you
> will get a http service (Pax Web) and loging (Pax Logging) - do not
> understand from here that only pax stuff profiles is supported. And to o
> that you use a simple command line command like pax-run --profiles=web. To
> add in top a config admin (Felix) you do -ax-run --profiles=web,config.
> Simple, isn't it :)?
> 3. You could use the implemented handlers as pax runner mvn handler for easy
> referencing the source of the bundles. E.g. pax-run
> mvn:org.ops4j.pax.web/pax-web-service
> will start a felix platform with pax web installed. There is also a wrap:
> protocol handler that allows you to wrap jars as bundles on the fly.
> 4. You culd use the scanners (knows how to find out what bundles to
> install). So, once you get the configuration / update on a configuration,
> the configuration could contain a url of the bundles to be provisioned for
> example, and you could just use one of teh scanners to automatically instart
> and optionally start those bundles. There are diferent scanners as scan-file
> that instals bunsles referenced in a text file (including properties),
> scan-dir that handles bundles in a direcotry or a jar, scan-pom that you
> could point to a pom file.
> Also if you have some specific needs just let us know and we are willing to
> help / support.
> Cheers,
> Alin Dreghiciu
> On 9/28/07, Guillaume Nodet <gnodet@gmail.com> wrote:
> >
> > For ServiceMix 4.0, we are thinking about implementing  a provisioning
> > system (see https://issues.apache.org/activemq/browse/SM-1071).  As
> > ServiceMix will be based on OSGi, OBR sounds like a good tool to use
> > for that.
> > I'm wondering if anyone has already implemented that / thought about that
> > ?
> >
> > Basically, I'm thinking about an OSGi service that would use a simple
> > API to detect changes and load a new configuration (through ldap,
> > http, jcr, or whatever).  This configuration would include the list of
> > bundles to install, and OBR would be used to download / install all
> > the dependencies.  Does it make sense ?
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> > ------------------------
> > Blog: http://gnodet.blogspot.com/
> >

Guillaume Nodet
Blog: http://gnodet.blogspot.com/

View raw message