activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arthur Naseef (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5471) Configuration server for Network of Brokers
Date Thu, 12 Feb 2015 22:28:11 GMT

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

Arthur Naseef commented on AMQ-5471:
------------------------------------

Tim's comments are interesting.  Reminds me of something I used to say - "they already invented
the tool that solves-all-problems; it's called a CPU".  So, we (software developers) really
are in the business of customizing and fitting solutions that are the right size to the problem.

As part of that - one thing to consider here - if we say, "ok, just use maven to serve up
the files" - then we've created a fair burden on a user and created a much more complex solution
for their use.  So, it makes sense here to define the interfaces from the "right-size" perspective,
implement to those interfaces, and then match to the technology underneath.  Using good modularity,
we can easily enable users to swap out underlying technologies where it makes sense.

With that said, I like the idea of a configuration server, again behind a "right-size" interface
(get config for broker <x>, etc).  Chatting with Hadrian earlier, I think an approach
that creates a simple configuration server and builds from there is a good way to go.  We
could build a lightweight server which is backed by files in a filesystem, making it quick
and easy to get started.  Management of those files can come later - if we need to implement
it ourselves.

Looking further ahead, it's preferable to provide end-users a complete solution that is as
simple to "drop in" as possible to make it easy to use and adopt.  Enabling others to come
along and implement alternatives, such as actually storing content in maven, is awesome too.

> 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.12.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