Return-Path: 
 <dev-return-44008-apmail-mesos-dev-archive=mesos.apache.org@mesos.apache.org>
X-Original-To: apmail-mesos-dev-archive@www.apache.org
Delivered-To: apmail-mesos-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 5F07618EBF
	for <apmail-mesos-dev-archive@www.apache.org>;
 Wed,  3 Jun 2015 20:10:27 +0000 (UTC)
Received: (qmail 27120 invoked by uid 500); 3 Jun 2015 20:10:27 -0000
Delivered-To: apmail-mesos-dev-archive@mesos.apache.org
Received: (qmail 27063 invoked by uid 500); 3 Jun 2015 20:10:27 -0000
Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@mesos.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@mesos.apache.org>
List-Post: <mailto:dev@mesos.apache.org>
List-Id: <dev.mesos.apache.org>
Reply-To: dev@mesos.apache.org
Delivered-To: mailing list dev@mesos.apache.org
Delivered-To: moderator for dev@mesos.apache.org
Received: (qmail 31425 invoked by uid 99); 2 Jun 2015 20:00:50 -0000
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 3
X-Spam-Level: ***
X-Spam-Status: No, score=3 tagged_above=-999 required=6.31
	tests=[HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
	autolearn=disabled
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:from:content-type:mime-version:subject
         :in-reply-to:date:cc:message-id:references:to;
        bh=ZSVyr3BjImRjklCmYGmdX9JJE3OS9lYkb5tNSBGhebg=;
        b=RSBtDi5/pLSnwb/g4dvIqY95aq3YABC2Xovf00b/TyqIrdchU9WZW/9cojfQ9jsr2p
         BQ/+k/NxAZvH/JHsUncXspNjEPUv+RnyVBKLlV5nJY33TpPxLwvSnrdCCw27PzeVP7oH
         tCvuoBW226/DND5S0FJrD8D1vQr+ehh4kC7wlxBDnrXikpm2T10Gf6RKlcJ4VdItjdnm
         R04zNEctiDV8uXh/M86iYNOZB+ba5HML7V3eekCofzjaBXdMjjk+gapjLL0YHTMAXCnn
         rdfZYgWLaiFQowkhd2JqJermOika7Uz2d9vlZPpc6zgX4/TsMBYHTUiSR11YOU68XyQE
         zIOw==
X-Gm-Message-State: 
 ALoCoQkt07ieoTsypiWok6JdmFVRrvR/T9f334T54tVXx8iQhqRgBuE/Yvc1CJ4QOADuMaAff76M
X-Received: by 10.70.30.193 with SMTP id u1mr52048339pdh.59.1433275195250;
        Tue, 02 Jun 2015 12:59:55 -0700 (PDT)
From: Steven Borrelli <steve@aster.is>
X-Google-Original-From: Steven Borrelli <steve@borrelli.org>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_EA02753E-2FF1-4A21-9B57-53CF20F68B2B"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Subject: Re: [DISCUSS] Renaming Mesos Slave
In-Reply-To: 
 <CAK8jAgPxfY2gueyyVxE1Nr0ihDW1jjguz-8o9PwEE9j1Szz5ZQ@mail.gmail.com>
Date: Tue, 2 Jun 2015 14:59:59 -0500
Cc: dev <dev@mesos.apache.org>
Message-Id: <4A18A648-5061-4AFC-9A47-9A5E9E11E37B@borrelli.org>
References: 
 <CAK8jAgPxfY2gueyyVxE1Nr0ihDW1jjguz-8o9PwEE9j1Szz5ZQ@mail.gmail.com>
To: user@mesos.apache.org
X-Mailer: Apple Mail (2.2098)

--Apple-Mail=_EA02753E-2FF1-4A21-9B57-53CF20F68B2B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

+1

I=E2=80=99d like to voice my support for removing the master/slave =
nomenclature. It=E2=80=99s our policy at aster.is <http://aster.is/> =
that we don=E2=80=99t use that terminology in our projects or =
presentations.=20

Currently we use =E2=80=98leader/follower=E2=80=99, but we are open to =
using whatever terms the community comes up with. We=E2=80=99re also =
willing to contribute resources to help get this accomplished.

We also like queen/drone.=20

1. Mesos follower. I=E2=80=99m fine with worker or compute. Not a fan of =
minion.
2. mesos-<term>
3. We use the term =E2=80=98leader=E2=80=99 right now.
4. - Update internal code references & UI (have duplicate API endpoints)
    - update packages & launch scripts, systemd service files, docker =
containers. Luckily, the mesos binary doesn=E2=80=99t need to be =
changed, just the start scripts and locations in /etc. For N versions we =
can update launch scripts to look for things like /etc/mesos-master =
config, environment files, and docker containers for backwards =
compatibility.=20
    - make changes final by Mesoscon in August, add deprecation warnings=20=

    - N + x version of Mesos, remove old UI endpoints and usage of =
master/slave config files

Cheers,

Steven Borrelli

> On Jun 1, 2015, at 4:18 PM, Adam Bordelon <adam@mesosphere.io> wrote:
>=20
> There has been much discussion about finding a less offensive name =
than "Slave", and many of these thoughts have been captured in =
https://issues.apache.org/jira/browse/MESOS-1478 =
<https://issues.apache.org/jira/browse/MESOS-1478>
>=20
> I would like to open up the discussion on this topic for one week, and =
if we cannot arrive at a lazy consensus, I will draft a proposal from =
the discussion and call for a VOTE.
> Here are the questions I would like us to answer:
> 1. What should we call the "Mesos Slave" node/host/machine?
> 2. What should we call the "mesos-slave" process (could be the same)?
> 3. Do we need to rename Mesos Master too?
>=20
> Another topic worth discussing is the deprecation process, but we =
don't necessarily need to decide on that at the same time as deciding =
the new name(s).
> 4. How will we phase in the new name and phase out the old name?
>=20
> Please voice your thoughts and opinions below.
>=20
> Thanks!
> -Adam-
>=20
> P.S. My personal thoughts:
> 1. Mesos Worker [Node]
> 2. Mesos Worker or Agent
> 3. No
> 4. Carefully


--Apple-Mail=_EA02753E-2FF1-4A21-9B57-53CF20F68B2B--