[
https://issues.apache.org/jira/browse/AMQ-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232234#comment-14232234
]
Tim Bain commented on AMQ-5471:
-------------------------------
Maybe you need to rewrite the description, then.
Your current text focuses on how distributed clients can access a central
server to retrieve content. Apache, Git, Maven repos, etc., all already meet
that need (and, frankly, should be how you implement distribution of config
files, so you don't have to worry about security features, etc.). For that
part of it, yes, I think this is innovation in the wheel industry. Keep in
mind too that "simpler" often turns out to mean "half-implemented solution that
only meets my particular needs"; reusing an existing COTS product is in fact
probably simpler than maintaining your own custom implementation of a web
server, and it'll hit all the use cases instead of just the ones you feel like
spending time on.
If your real innovation here is an easy way to dynamically generate the config
files for a given broker based on input you collect, or a visual editor for
config files, or any of a number of improvements to the process of actually
generating the config files, then go for it. But since there's no mention
whatsoever of any of that in your initial description, you probably should
refocus the description to focus on those aspects. And I still think that
however you generate the config files, you should serve them up via a COTS
product such as Apache.
> 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)
