You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2016/06/07 19:57:20 UTC

[jira] [Commented] (ARTEMIS-540) Supporting openshift as source of service discovery

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

clebert suconic commented on ARTEMIS-540:
-----------------------------------------

We can use JGroups as a discovery mechanism. and I bet JGroups should already have such thing. on which case this JIRA wouldn't be needed and you could just reuse JGroups for this purpose.

If that doesn't make sense on JGroups, it's easy to extend/implement BroadcastEndpoint.



> Supporting openshift as source of service discovery
> ---------------------------------------------------
>
>                 Key: ARTEMIS-540
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-540
>             Project: ActiveMQ Artemis
>          Issue Type: Wish
>          Components: Broker
>    Affects Versions: 1.2.0
>            Reporter: Kaiming Yang
>
> Artemis Apache MQ currently only support broadcast for service discovery. 
> At our company that is not allowed, hence we are looking to provide a plugin that can use a different service discovery mechanism.
> At our company we are using OpenShift 3.x, which provides service discovery/lookup itself. We are looking to provide a mechanism that leverages OSE as the service to provide Artemis cluster information dynamically and are looking to provide those contributions back to the community.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)