Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E860A200A5B for ; Wed, 25 May 2016 23:39:26 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E6E58160A34; Wed, 25 May 2016 21:39:26 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3A214160A0F for ; Wed, 25 May 2016 23:39:26 +0200 (CEST) Received: (qmail 33396 invoked by uid 500); 25 May 2016 20:56:13 -0000 Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list issues@activemq.apache.org Received: (qmail 33380 invoked by uid 99); 25 May 2016 20:56:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 May 2016 20:56:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CB4AE2C1F56 for ; Wed, 25 May 2016 20:56:12 +0000 (UTC) Date: Wed, 25 May 2016 20:56:12 +0000 (UTC) From: "Kaiming Yang (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ARTEMIS-540) Supporting openshift as source of service discovery MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 25 May 2016 21:39:27 -0000 [ https://issues.apache.org/jira/browse/ARTEMIS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaiming Yang updated ARTEMIS-540: --------------------------------- Description: 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. was: 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 mechansim that leverages OSE as the service to provide Artemis cluster information dynamically and are looking to provide those contributions back to the community. > 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)