For more info on the recent Service DiscoveryInfo, see https://issues.apache.org/jira/browse/MESOS-2150 (and the design doc linked from there). For Mesos labels, see https://issues.apache.org/jira/browse/MESOS-2120
On Sun, Apr 12, 2015 at 2:49 AM, Tom Arnfeld <[email protected]> wrote: > Hi Yaron, > > I'm not sure about Marathon but I know recently some new protobufs landed > for rich service discovery information to be provided to tasks/executors by > framework schedulers. The structure can be found here > https://github.com/apache/mesos/blob/master/include/mesos/mesos.proto#L1089-L1116 > . > > On 12 April 2015 at 10:09, Yaron Rosenbaum <[email protected]> > wrote: > >> Hi >> >> The Marathon 0.8.0 release notes has briefly mentioned a new feature >> called Labels. >> I am trying to find more documentation about this, especially around the >> REST interface. >> >> Also, the release notes mentions something about Mesos using Labels as >> well - I would like to hear more information about how exactly mesos could >> / would use the information in the Labels. >> >> Specifically, I am looking for a way to pass information for a ‘service >> discovery’ component that I have built. I currently use environment >> variables for that, I was hoping Labels would be a cleaner way to do the >> same. Example: >> >> "env": { >> "DISCOVERY_DOMAIN": "test.multicloud.me", >> "DISCOVERY_FRONTEND": "http" >> } >> >> This information is used to automatically re-configure an HAProxy >> instance. >> >> Thanks. >> >> (Y) >> >> >
