[
https://issues.apache.org/jira/browse/MESOS-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14541141#comment-14541141
]
Marco Massenzio edited comment on MESOS-2709 at 5/13/15 1:07 AM:
-----------------------------------------------------------------
Created proof of concept in Python:
[zk-mesos|https://github.com/massenz/zk-mesos]
(this is one, the simplest to implement, of several possible - but also, by its
very nature, the least "pure").
Adapting this to work with Java (and, by consequence, Scala) is trivial - other
languages (eg Go) complexity depends on the difficulty of binding to Google
Protobufs.
Starting to write the design doc, outlining the various alternatives.
was (Author: marco-mesos):
Created proof of concept in Python:
(zk-mesos)[https://github.com/massenz/zk-mesos]
(this is one, the simplest to implement, of several possible - but also, by its
very nature, the least "pure").
Adapting this to work with Java (and, by consequence, Scala) is trivial - other
languages (eg Go) complexity depends on the difficulty of binding to Google
Protobufs.
Starting to write the design doc, outlining the various alternatives.
> Design Master discovery functionality for HTTP-only clients
> -----------------------------------------------------------
>
> Key: MESOS-2709
> URL: https://issues.apache.org/jira/browse/MESOS-2709
> Project: Mesos
> Issue Type: Improvement
> Components: java api
> Reporter: Marco Massenzio
> Assignee: Marco Massenzio
>
> When building clients that do not bind to {{libmesos}} and only use the HTTP
> API (via "pure" language bindings - eg, Java-only) there is no simple way to
> discover the Master's IP address to connect to.
> Rather than relying on 'out-of-band' configuration mechanisms, we would like
> to enable the ability of interrogating the ZooKeeper ensemble to discover the
> Master's IP address (and, possibly, other information) to which the HTTP API
> requests can be addressed to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
