Skip to content
This repository has been archived by the owner on Feb 1, 2021. It is now read-only.

Proposal: Swarm use unreserved/reserved resources from Mesos #1618

Closed
ghost opened this issue Jan 12, 2016 · 3 comments
Closed

Proposal: Swarm use unreserved/reserved resources from Mesos #1618

ghost opened this issue Jan 12, 2016 · 3 comments

Comments

@ghost
Copy link

ghost commented Jan 12, 2016

When launch tasks, Swarm only use unreserved resource; and if Mesos offer reserved resources, the role info are also ignored which is rejected by Mesos master.

This proposal is to let Swarm use both un-reserved/reserved resources Mesos.

@ghost
Copy link
Author

ghost commented Jan 14, 2016

@jimenez any comments on this requirement?

@gradywang
Copy link
Contributor

Append the PR #1890 , In that PR, Swarm is enabled to use both reserved and unreserved resources to create container.

The design proposal is : swarm will use reserved resources firstly, if reserved resources are not enough for the creating container, then the unreserved resources will be used for the gap. This behaviour could eventually be configurable by end user (use unreserved resources or reserved resources firstly), although we may want to avoid providing that option until we see a valid use case.

@jimenez , cloud you help to review this proposal and that patch? Thanks!

@nishanttotla
Copy link
Contributor

Closing due to #2853

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants