Return-Path: X-Original-To: apmail-aurora-issues-archive@minotaur.apache.org Delivered-To: apmail-aurora-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D82B6102EF for ; Thu, 20 Mar 2014 23:22:14 +0000 (UTC) Received: (qmail 13417 invoked by uid 500); 20 Mar 2014 23:22:14 -0000 Delivered-To: apmail-aurora-issues-archive@aurora.apache.org Received: (qmail 13389 invoked by uid 500); 20 Mar 2014 23:22:14 -0000 Mailing-List: contact issues-help@aurora.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.incubator.apache.org Delivered-To: mailing list issues@aurora.incubator.apache.org Received: (qmail 13381 invoked by uid 99); 20 Mar 2014 23:22:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Mar 2014 23:22:14 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 20 Mar 2014 23:22:12 +0000 Received: (qmail 11800 invoked by uid 99); 20 Mar 2014 23:21:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Mar 2014 23:21:49 +0000 Date: Thu, 20 Mar 2014 23:21:49 +0000 (UTC) From: "Tobias Weingartner (JIRA)" To: issues@aurora.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AURORA-285) Provide some method to reserve hosts/resources to explicit requests MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/AURORA-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942503#comment-13942503 ] Tobias Weingartner commented on AURORA-285: ------------------------------------------- By using an explicit constraint to force the task to be on these resources. TL;DR 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: https://issues.apache.org/jira/browse/AURORA-285 > 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 resources. -- This message was sent by Atlassian JIRA (v6.2#6252)