activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Bain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5471) Configuration server for Network of Brokers
Date Tue, 02 Dec 2014 20:56:14 GMT

    [ https://issues.apache.org/jira/browse/AMQ-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14232117#comment-14232117
] 

Tim Bain commented on AMQ-5471:
-------------------------------

If this is just a service for hosting and serving XML files, why can't you just use an existing
COTS product?  Apache, for example, or one of the various products that allow you to host
Maven repos?  What justifies re-inventing the wheel here?

> 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)

Mime
View raw message