Skip to content
This repository has been archived by the owner on Apr 24, 2023. It is now read-only.

Add support for host constraints #42

Closed
dgrnbrg opened this issue Sep 22, 2015 · 5 comments
Closed

Add support for host constraints #42

dgrnbrg opened this issue Sep 22, 2015 · 5 comments

Comments

@dgrnbrg
Copy link
Contributor

dgrnbrg commented Sep 22, 2015

This should be for things like "only on hosts w/ a specific attribute". This will enable things like GPU or machine class aware scheduling.

This will need to be added to the client-facing API, as well as to the scheduler & db.

@dgrnbrg dgrnbrg added this to the Fenzo Integration milestone Sep 22, 2015
@dgrnbrg
Copy link
Contributor Author

dgrnbrg commented Oct 21, 2015

@shamsmahmood Can you comment on what you did at the Mesoscon Europe hackathon on this?

@shamsimam
Copy link
Contributor

I added support in the Cook json api to accept host constraints as key value pairs. The database schema has also been updated so that these constraints are stored in the database. The unit tests in api.clj should also help explain what has been done (https://github.com/shamsmahmood/Cook).

@dgrnbrg
Copy link
Contributor Author

dgrnbrg commented Dec 7, 2015

#69 has the API side of this implemented. Once #84 is merged, it should be easy to complete the integration, as #84 includes an API for adding constraints.

@DaoWen
Copy link
Contributor

DaoWen commented Mar 31, 2018

@shamsimam - I think this is done now, right? Please close this if you agree.

@shamsimam
Copy link
Contributor

Was implemented in #284

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

No branches or pull requests

3 participants