aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Weingartner (JIRA)" <>
Subject [jira] [Commented] (AURORA-285) Provide some method to reserve hosts/resources to explicit requests
Date Thu, 20 Mar 2014 23:21:49 GMT


Tobias Weingartner commented on AURORA-285:

By using an explicit constraint to force the task to be on these resources.


Assume you have a host "A", and the local performance gurus wish to have a couple of different
tasks co-located on this host to study their interdependence and inability to play nicely
in a shared "sandbox".

At the current time, AFAICT, we would need to create a slave with a dedicated attribute, part
of this attribute checks and enforces that the role matches the dedication.  Instead, I see
a use case for not enforcing this constraint quite so rigorously, instead allowing any job
owner to specify a constraint in their jobs/tasks such that their tasks/jobs would be forced
to be scheduled onto the specified slaves.

Not sure if that clarifies?

> Provide some method to reserve hosts/resources to explicit requests
> -------------------------------------------------------------------
>                 Key: AURORA-285
>                 URL:
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Tobias Weingartner
> in order to support testing and other host specific uses, it would be nice to be able
to reserve a set of hosts (possibly through a slave attribute) from being considered for scheduling,
unless a set of constraints forces tasks onto these specific hosts.
> The "dedicated" attribute is too much, as it restricts the tasks to be of a certain role.
 In this case, we'd like to allow any task in any role to be able to request to these reserved

This message was sent by Atlassian JIRA

View raw message