[jira] Commented: (SM-1071) Provisioning system
[ https://issues.apache.org/activemq/browse/SM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40241 ] Guillaume Nodet commented on SM-1071: - I've had a look at the Deployment Admin. I think it could be used instead of OBR for installing packages, but it does not offer the feature of detecting changes and accessing the whole configuration, so we will still need a simple interface / implementations for that (http, jcr, jndi)... I really see one downside to this Deployment Admin which is the fact that a single bundle can not be shared, so I suppose that you need to install several times the same bundle and rename it :-( > Provisioning system > --- > > Key: SM-1071 > URL: https://issues.apache.org/activemq/browse/SM-1071 > Project: ServiceMix > Issue Type: New Feature >Reporter: Guillaume Nodet >Assignee: Bruce Snyder > Fix For: 4.0 > > > Maybe using OBR > (http://felix.apache.org/site/apache-felix-osgi-bundle-repository-obr.html) or > Equinox (http://wiki.eclipse.org/index.php/Equinox_Provisioning). > Basically, i'm thinking about two things: > * leverage OBR to install features easily (activemq, ode, cxf, etc...) > * dynamic / automatic provisioning of applications > For the second one, a service could pull an HTTP url from time to time to > check is a new configuration for itself is available. if yes, download it > and uninstall stop / uninstall unneeded bundes, install new ones, etc... > The configuration would be a simple xml defining which bundles / version > should be started -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Scheduling 3.2 release
I posted a development enhancement in the ActiveMQ forums as it directly relates to the next release and indirectly relates to ServiceMix at some point. The link is provided below. http://www.nabble.com/Proposed-Additional-BrokerViewMBean-Methods-tf4545757s2354.html One question is what does the time frame look like for syncing ServiceMix with ActiveMQ releases? Seems like it can be done fairly quickly with new releases of ActiveMQ as it is just a maven build change. Also does the above feature make sense for providing dynamic network connectors (i.e. for remote managed ServiceMix clustering and JMS distributed queues/topics). I know for a fact that the feature would be useful in many enterprise environments where a central server manages many ActiveMQ/ServiceMix brokers through JMX instead of some other custom protocol and in hub/spoke architectures. I'm still in the process of developing a patch for the above mentioned link...hopefully I can get that out tomorrow at some point as part of a jira enhancement task. There hasn't been any comments on the issue as of yet...but hopefully soon once I get the patch online. Thanks, Trevor gnodet wrote: > > I'm going through the remaining JIRA assigned for 3.2. > If anybody has any important issues to schedule there (or patches to > apply), please yell ! > I'd like to put 3.2 in release mode asap. > > -- > Cheers, > Guillaume Nodet > > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/Scheduling-3.2-release-tf4528728s12049.html#a12992809 Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
