Return-Path: X-Original-To: apmail-aurora-dev-archive@minotaur.apache.org Delivered-To: apmail-aurora-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C5D2C188A4 for ; Wed, 27 Jan 2016 00:09:39 +0000 (UTC) Received: (qmail 73403 invoked by uid 500); 27 Jan 2016 00:09:39 -0000 Delivered-To: apmail-aurora-dev-archive@aurora.apache.org Received: (qmail 73350 invoked by uid 500); 27 Jan 2016 00:09:39 -0000 Mailing-List: contact dev-help@aurora.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.apache.org Delivered-To: mailing list dev@aurora.apache.org Received: (qmail 73339 invoked by uid 99); 27 Jan 2016 00:09:39 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jan 2016 00:09:39 +0000 Received: from mail-oi0-f42.google.com (mail-oi0-f42.google.com [209.85.218.42]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 5914B1A003F for ; Wed, 27 Jan 2016 00:09:39 +0000 (UTC) Received: by mail-oi0-f42.google.com with SMTP id o124so115202692oia.3 for ; Tue, 26 Jan 2016 16:09:39 -0800 (PST) X-Gm-Message-State: AG10YORslB0HlKJy3A+WjJfLUzgSslmaq+BOkgDJJsHg2+8NS4t15Bx7CJ5TX74/n7MpY5Q7JioLjNiFwR6RGg== MIME-Version: 1.0 X-Received: by 10.202.189.195 with SMTP id n186mr2466696oif.109.1453853378628; Tue, 26 Jan 2016 16:09:38 -0800 (PST) Received: by 10.202.193.213 with HTTP; Tue, 26 Jan 2016 16:09:38 -0800 (PST) In-Reply-To: <1453853117056.6903@blue-yonder.com> References: <0599327bfbff44a7b82b656c7aa268c5@ex2013-1.phi-tps.local> <1453853117056.6903@blue-yonder.com> Date: Tue, 26 Jan 2016 16:09:38 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Job-Aggregation From: Bill Farner To: dev@aurora.apache.org Content-Type: multipart/alternative; boundary=001a113ddb76305636052a459e7c --001a113ddb76305636052a459e7c Content-Type: text/plain; charset=UTF-8 That's about what i figured. I've observed several behavioral features in this area like dependencies and group-wise scaling. However, i have a hard time believing those tend to be that useful in practice. On Tue, Jan 26, 2016 at 4:05 PM, Erb, Stephan wrote: > I guess most of the time it is just the viewing, and then knowing that > everything that is supposed to be there is healthy in the Aurora-sense. > That's a pretty loose notion of working, but tends to be quite helpful. > ________________________________________ > From: Bill Farner > Sent: Wednesday, January 27, 2016 12:53 AM > To: dev@aurora.apache.org > Subject: Re: Job-Aggregation > > Are there any specific things you be looking to do with these groups, or > just view them as a logical collection? > > On Tue, Jan 26, 2016 at 3:01 PM, Erb, Stephan > > wrote: > > > Hi, > > > > I've noticed that a couple of people [1, 2] have independently talked > > about aggregating multiple Aurora jobs to 'logical services'. > Internally, > > we also do something similar. I am wondering if there is a broader > concept > > waiting to be discovered as an Aurora feature. As a kind of related > > concept, Marathon does have its application groups [3] and Kubernetes its > > pods [4]. > > > > Does anyone have thoughts on this? That's a pretty open ended question > > here, but would be unfortunate if many Aurora users end up building a > > similar thing independently. > > > > Regards, > > Stephan > > > > > > [1] > > > https://mail-archives.apache.org/mod_mbox/aurora-user/201512.mbox/%3CCABwOPbetX_pA%3Dq8fUCWHB%2B9R1JdD8V4m_S6T2AVDvmwn36t4Cg%40mail.gmail.com%3E > > [2] > > > https://issues.apache.org/jira/browse/AURORA-1052?focusedCommentId=15108936&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15108936 > > [3] https://mesosphere.github.io/marathon/docs/application-groups.html > > [4] http://kubernetes.io/v1.0/docs/user-guide/pods.html > --001a113ddb76305636052a459e7c--