[
https://issues.apache.org/jira/browse/AMQ-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232206#comment-14232206
]
Hadrian Zbarcea commented on AMQ-5471:
--------------------------------------
If you just want to server static content, httpd, nginx are fine. If the
content is more dynamic it starts to get more complicated. Sure you can map the
http resource to a directory that is a git repository and then have hooks or
some other external mechanism that deals with the fs content. I thought about
maven repos, but I think they'd be overkill for this. If you want to use this
service to provide not just configuration but also status of the brokers in the
nob, in which case no cots product would help you.
I don't see this as innovation in the wheel industry. Is there a simpler
solution I miss?
> Configuration server for Network of Brokers
> -------------------------------------------
>
> Key: AMQ-5471
> URL: https://issues.apache.org/jira/browse/AMQ-5471
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 5.11.0
>
>
> Brokers use the xbean configuration to start which is usually found in ./conf
> other other places on the local disk. In a NOB topology however it is hard to
> distribute the configuration files and maintain them across brokers
> especially with a growing or elasticly changing number of brokers.
> ActiveMQ already supports reading the xbean configuration from an http;//
> URL, so it would be very helpful to have a rest service that manages the
> configuration for all the brokers.
> I started such a service on [github|https://github.com/hzbarcea/activemq-nob]
> but plan to contribute it to ASF once it's in a decent shape, in a couple of
> weeks or so.
> The service uses the local file system and appropriate conventions to store
> all the relevant broker configuration resources (e.g. could be generated with
> ./bin/activemq create <instance> minus certificates probably). I plan to
> enhance it later to support a git repository for the configuration, so that
> it's versioned, so that an operator could roll out a new NOB topology, or
> roll back to the previous configuration.
> Feedback appreciated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
