...@gmail.com]
*发送时间:* 2015年6月5日 10:40
*收件人:* u...@mesos.apache.org
*主题:* Re: [DISCUSS] Renaming Mesos Slave
+1 master/slave, no change needed.
2015-06-05 0:10 GMT+08:00 Ankur Chauhan an...@malloc64.com:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
+1 master/slave
James made some very good
-1 master/worker
-1 master/agent
-1 leader/follower
+1 master/slave; no change needed
There's no technical benefit **at all** to a terminology change at this
point. If people want to change the names in their client presentations
that's fine. Master/slave conveys specific meaning that is lost
1. Mesos Worker [node/host/machine]
2. Mesos Worker [process]
3. No, master/worker seems to address the issue with less changes.
4. Begin using the new name ASAP, add a disambiguation to the docs, and
change old references over time. Fixing the official name, even before
changes are in
: dev
Subject: Re: [DISCUSS] Renaming Mesos Slave
Strong -1 for changing the name (either master or slave).
From a community stand point, if dev resources are diverted to renaming
efforts, then the community and the user base both lose meaningful
functionality that isn't being worked on.
From
+1
I’d like to voice my support for removing the master/slave nomenclature. It’s
our policy at aster.is that we don’t use that terminology in our projects or
presentations.
Currently we use ‘leader/follower’, but we are open to using whatever terms the
community comes up with. We’re also
+1
I’d like to voice my support for removing the master/slave nomenclature. It’s
our policy at aster.is http://aster.is/ that we don’t use that terminology in
our projects or presentations.
Currently we use ‘leader/follower’, but we are open to using whatever terms the
community comes up
+1 for Brian Hicks' leader/follower name and a huge +1 for the explanation
he gave
On Wed, Jun 3, 2015 at 10:27 AM, Brian Hicks br...@brianthicks.com wrote:
1. We’ve been aliasing everything to “leader/follower” in the projects I’m
a part of. I think it gets rid of the problematic language
1. Mesos worker
2. Mesos worker
3. No
4. Documentation should first be changed
Thanks,
Elizabeth
On Monday, June 1, 2015, Adam Bordelon a...@mesosphere.io wrote:
There has been much discussion about finding a less offensive name than
Slave, and many of these thoughts have been captured in
Hi Jie,
I understand your concern here, but within Apache projects,
organizations do not have a voice/vote -- people do.
I think should take into strong consideration the overhead any change
may have on any adopter/organization and discuss those risks and
problems openly, but ideally this
Adam,
If a vote is called out, how do we decide if it passes or not. Will that be
the same of voting for a release (i.e., PMC member can veto it)?
I would imagine that some PMC members might want to express some negative
feedbacks on this, but certainly do not want to veto it. How do we deal
Dave,
I am not saying that we should make the decision solely based on
organization votes. This is just an extra input we can use while making the
decision.
By looking at the threads, looks like we don't have a community consensus
here. Then the question is: how do we make a *better* decision
1. Mesos Worker (or just Mesos node)
2. Mesos Worker
3. No, but if we do then Leader or Director or Controller
4. Deprecation cycle, documentation, etc. Provide aliases for a release or
two.
Thanks for raising this topic; it's been on my mind for a while.
As for why I think this matters:
Strong -1 for changing the name (either master or slave).
From a community stand point, if dev resources are diverted to renaming
efforts, then the community and the user base both lose meaningful
functionality that isn't being worked on.
From a using organization stand point, as well as
1) Mesos Agent maybe? Agent (in law e.g.) is someone acting on behalf of
other person. That is right what we have, mesos-slave isn't a worker and
shouldn't be - it should let others work.
2) mesos-agent
Although I personally like Google terminology - Borg master and borglet,
Omega master and
1) Mesos Worker
2) Mesos Worker
3) no, I'm OK with Mesos Master
4) announce the change as part of a new release and deprecate the old names
publicly; this may also be a good time to consider crafting an official
deprecation policy for the project so we're transparent with how
deprecation will work
+1
1. Mesos Worker [node/host/machine]
2. Mesos Worker [process]
3. No, master/worker seems to address the issue with less changes.
4. Begin using the new name ASAP, add a disambiguation to the docs, and change
old references over time. Fixing the official name, even before changes are
in
My (very personal) thought here is that we should ensure a vocal minority
is not changing things for the sake of changing it. What is the industry
standard here? Are potential users actually refusing to use mesos due to
the terminology which is unfortunately very prevalent in the client/server
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
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
18 matches
Mail list logo
