aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Erb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-761) Provide a proxy for generic service discovery
Date Wed, 15 Oct 2014 22:25:34 GMT

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

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

Your analysis and plan of action sounds good to me.

In regard to prior art, looks like marathon folks like to reinvent the wheel  :-)

* the original HAProxy script shiped by Marathon itself
* https://github.com/QubitProducts/bamboo 
* https://github.com/opentable/mesoshub 
* https://github.com/opencredo/mesos_service_discovery 
* https://github.com/Wizcorp/frontrunner 




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

Mime
View raw message