Mailing-List: contact issues-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
Date: Sun, 28 Dec 2014 00:10:13 +0000 (UTC)
From: "Stephan Erb (JIRA)" <jira@apache.org>
To: issues@aurora.incubator.apache.org
Message-ID: <JIRA.12744500.1411840562000.105776.1419725413280@Atlassian.JIRA>
In-Reply-To: <JIRA.12744500.1411840562000@Atlassian.JIRA>
References: <JIRA.12744500.1411840562000@Atlassian.JIRA>
 <JIRA.12744500.1411840562601@arcas>
Subject: [jira] [Commented] (AURORA-761) Provide a proxy for generic service
 discovery
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Stephan Erb commented on AURORA-761:
------------------------------------

Great!

> Provide a proxy for generic service discovery
> ---------------------------------------------
>
>                 Key: AURORA-761
>                 URL: https://issues.apache.org/jira/browse/AURORA-761
>             Project: Aurora
>          Issue Type: Story
>          Components: Service Discovery, Usability
>            Reporter: Bill Farner
>            Priority: Minor
>
> While {{Announcer}} provides service registration, we lack a cross-cutting answer for service discovery.  There are well-known libraries that will do it (e.g. finagle), but we need an answer for others.  Marathon, for example, provides a script called {{haproxy_marathon_bridge}} that reloads configuration of HAProxy for this purpose.  We could do something similar with a mixin {{Process}} that dynamically routes an inbound port to a serverset path in ZooKeeper.


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