You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2015/04/13 21:36:13 UTC

[jira] [Commented] (AURORA-1278) Allow inverted constraints

    [ https://issues.apache.org/jira/browse/AURORA-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14492939#comment-14492939 ] 

Bill Farner commented on AURORA-1278:
-------------------------------------

Is negation of a value constraint what you're after?

https://github.com/apache/aurora/blob/master/docs/configuration-reference.md#specifying-scheduling-constraints

e.g.

{noformat}
constraints = {
  'rack': '!knownBadRack',  # Temporarily avoiding this bad rack.
  'arch': '!arm',           # App will not run on ARM CPUs.
}
{noformat}

> Allow inverted constraints
> --------------------------
>
>                 Key: AURORA-1278
>                 URL: https://issues.apache.org/jira/browse/AURORA-1278
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Silas Snider
>
> Currently, I can list a set of hosts upon which my job should schedule. However, there are some common-ish situations where I want to specify a list of hosts on which my job should never schedule. For instance, if I, as an application developer without administrative access to the aurora scheduler wish to avoid scheduling on a piece of hardware while I get the admins to drain it, or even if I know I trigger some specific kernel bug on a certain class of hardware.
> I can see scenarios for racks as well (issues with the TOR), so it would make sense there as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)