[
https://issues.apache.org/jira/browse/AURORA-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14194588#comment-14194588
]
Jing Dong commented on AURORA-761:
----------------------------------
Hello, I'm the source maintainer for Bamboo. We were initially thinking using
Consul as storage, but we didn't want to introduce additional requirement for
Marathon deployment. So we decided to use the Mesos/Marathon's Zookeeper
option. We specifically put the configuration in separate JSON key for future
migration or optional storage support.
I'm happy to bring Bamboo to support Aurora if implementation requirements are
discussed here, and of course if it can be implemented generically enough
without 'hacking' or 'fighting' to fit both Marathon/Aurora.
> 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)
