WIP: Implement 'pool': An attribute & constraint that lets you split a cluster #187
Conversation
…ster into multiple parts, without having to use Mesos's roles.
EvanKrall
changed the title
|
I've marked this as WIP because I want to be very careful about merging and rolling this out. As is, this will cause a large bounce. |
| @@ -218,6 +218,18 @@ def get_extra_volumes(self): | |||
| <https://mesosphere.github.io/marathon/docs/native-docker.html>`_""" | |||
| return self.config_dict.get('extra_volumes', []) | |||
|
|
|||
| def get_pool(self): | |||
| """Which pool of nodes this job should run on. This can be used to mitigate noisy neighbors, by putting | |||
There was a problem hiding this comment.
Can you move these docs, or some of them to the actual docs location?
|
Are you sure you don't want to do the thing where if pool is not None, add the constraint? Also of course we'll need to add the attributes to our slaves now |
|
I'm not sure what you mean in your first sentence. My default behavior is pretty clearly specified: a constraint of I've got an internal review for adding the attribute to our slaves. |
mjksmith
force-pushed
the
master
branch
2 times, most recently
from
8bbb271 to
42ae5c2
Compare
|
Gotcha, it sound like you are going to deploy the new attribute first, and then optionally add this constraint to a bunch of apps, then push this code? |
|
Yeah, that's the plan. |
...into multiple parts, without having to use Mesos's roles.