[feature] constraint distinct

[camerondavison]

I like the distinct_hosts constraint, but I would really like if it were more generic. This way it could be distinct racks or distinct aws availability zones. I was thinking that maybe there could be a distinct constraint that takes a string template and makes sure that the string is unique always. Then you could put in whatever template string you want and it would make sure that it was always distinct.

Such as "${attr.platform.aws.placement.availability-zone}"

[jpbetz]

@armon I have a similar need. I've plugged in a ${attr.platform.linkedin.rack} property via a custom env_*.go extension that I'd like to use both for rack diversity and affinity. I may add additional availability-zones in the future, but I need some way to constrain by them when scheduling for them to have any value.

[camerondavison]

What do you think the level of work for this is? Something I need to leave to the core team or something I could look into?

[dadgar]

Hey @jpbetz, make sense. I am curious is this long term ask or something you need in the immediate future?

[jpbetz]

We're currently comparing Nomad capabilities with other systems and testing the various capabilities out with a small cluster on Nomad managed machines. I can put this aside and prototype other aspects, but it's a must have before we can consider moving actual service deployables to Nomad. Our timeline is fairly tight for the whole prototyping effort. We've got maybe three months total. What's the level of effort here? Should I dig into the code or is this something the core team is interested in working on?

…

On Mon, Mar 6, 2017 at 3:52 PM Alex Dadgar ***@***.***> wrote: Hey @jpbetz <https://github.com/jpbetz>, make sense. I am curious is this long term ask or something you need in the immediate future? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1387 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAf9RnE5KTqp1urPp3jfxr4M6XR-Y49Oks5rjJw8gaJpZM4JFglT> .

[dadgar]

@jpbetz Going to sneak it into Nomad 0.5.5! It is a cool feature and would love to help you all out on your POC where possible 👍

[jpbetz]

Thanks @dadgar! For POC agility, we build and deploy Nomad from source. So it doesn't matter to me if this feature is in a point release or not, all I need is to know the commit hash and I'll pull from upstream to grab it.

[dadgar]

@jpbetz Let me know if you run into any hiccups!

[jpbetz]

@dadgar Go build fails on master using go 1.7.1 - 1.7.3 with:

src/github.com/hashicorp/nomad/helper/tlsutil/config.go:157: tlsConfig.Clone undefined (type *tls.Config has no field or method Clone, but does have tls.clone)

Having trouble finding a good go version to build with. What do you recommend?

[jpbetz]

Nevermind, was able to build with 1.8.

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.