[
https://issues.apache.org/activemq/browse/SM-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40158
]
Guillaume Nodet commented on SM-1071:
-------------------------------------
<quote>I have been thinking about something like this for the Apache Directory
Server as well. When we restructure around OSGi I want to be able to leverage
OBR and add some group/cluster configuration concepts so that we can bring up a
new server and point it to a config server url and a group name and have it
provision bundles and configure itself. Of course I want to build this
centralized management facility on top of ApacheDS LDAP to store configuration
information by group, node name, etc., but this is a generic idea that could
apply to a lot of OSGi applications, particularly server side apps like
ServiceMix.</quote>
Yeah, I was thinking about that too. If you use virtualization at the same
time (like VMWare) it can be very powerful. Using http for accesing the
config has some pros too, because you could use svn for example. (or other CMS
/ rest api). Anyway, a simple facade api should be able to abstract the
backend.
<quote>I am also thinking about some change management features for versioned
configuration packages (for audit history, rollback to snapshot, etc.) and the
ability to move change packages through development, QA, and production
environments. I know a lot of this is beyond the scope of this issue, but it
would be interesting to see if we can work together to satisfy the common
requirements we have.</quote>
Yeah, a bit beyond the scope ... but still very interesting. If we use svn or
a CMS, wouldn't this feature be available at a cheap price ? at least for
versioning of configurations. I don't know much about ldap. What kind of
features would it bring ?
> Provisioning system
> -------------------
>
> Key: SM-1071
> URL: https://issues.apache.org/activemq/browse/SM-1071
> Project: ServiceMix
> Issue Type: New Feature
> Reporter: Guillaume Nodet
> 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.
