Generate masterN.mesos record for current leader

[jdef]

Fixes #165

[tsenart]

What do you think of making this a nested map?

if _, ok := rg.records[rtype]; !ok {
    rg.records[rtype] = map[string][]string{}
}
rg.records[rtype][name] = append(rg.records[rtype][name], host)

[tsenart]

Or even better:

if _, ok := rg.records[rtype]; !ok {
    rg.records[rtype] = map[string]map[string]struct{}{}
}

if _, ok := rg.records[rtype][name]; !ok {
    rg.records[rtype][name] = map[string]struct{}{}
    rg.records[rtype][host] = map[string]struct{}{}
}

rg.records[rtype][name][host] = struct{}{}
rg.records[rtype][host][name] = struct{}{}

[jdef]

good suggestions. if the system wasn't about to undergo major re-implementation to support new features, i'd agree to an approach like this.

[kozyraki]

@jdef @tsenart Gentlemen, is this good to go from your point of view? Cannot tell for sure.

[jdef]

Not ready for merge, needs additional work.

On Thu, Jun 11, 2015 at 1:38 PM, Christos Kozyrakis <
notifications@github.com> wrote:

@jdef https://github.com/jdef @tsenart https://github.com/tsenart
Gentlemen, is this good to go from your point of view? Cannot tell for
sure.

—
Reply to this email directly or view it on GitHub
#169 (comment).

[tsenart]

LGTM in regards to the scope of the PR. Let's review the other suggestions after we have this through.