Hi Adam,
1. Mesos Agent
2. Mesos Agent
3. No but is master-agent a logical coupling?
4. +1 Dave, documentation, then API, then rest of the code base. We should
also make sure that we only have to change once and that we cover all the
connotations that might offend.
On Tue, Jun 2, 2015 at 11:50
Hi Adam,
1. Mesos Worker
2. Mesos Worker
3. No
4. Carefully. Should take care the compatible when upgrade.
On Wed, Jun 3, 2015 at 2:50 AM, Dave Lester d...@davelester.org wrote:
Hi Adam,
I've been using Master/Worker in presentations for the past 9 months and
it hasn't led to any
My $0.02...
The use of the word Worker is confusing. This entity has several
responsibilities, including, maintaining connectivity to master, managing
and monitoring the executors, sending status updates, and other future
endeavors such as autonomously determining actions for resource
-1 for the name change.
The master/slave terms in Mesos accurately describe the relationship
between the components using common engineering terms that predate modern
computing.
Human slavery is an abomination, but then so is murder. Would you have us
eliminate all references to kill in the
1.Mesos Resource-Agent
2.mesos resource-Agent
3.Mesos Resource-Scheduler
4.Eventually
Thanks Regards,
Pradeep
On 2 June 2015 at 15:39, Scott Rankin sran...@motus.com wrote:
+1
1. Mesos Worker
2. mesos-worker
3. No
4. Change the docs as soon as the new command is
+1
1. Mesos Worker
2. mesos-worker
3. No
4. Change the docs as soon as the new command is available, perhaps provide
a symlink for a while.
From: Adam Bordelon
Reply-To: user@mesos.apache.orgmailto:user@mesos.apache.org
Date: Monday, June 1, 2015 at 5:18 PM
To: dev,
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
On 06/01/2015 04:18 PM, Adam Bordelon wrote:
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 find political correctness rather nausiating. Folks should stop
trying
On 06/02/2015 11:30 AM, Alexander Gallego wrote:
1. mesos-worker
2. mesos-worker
Currently, my (limited) understanding of the codebase for mesos, is that
slave does not have any autonomy, is 100% controlled by the Master,
hence the clear nomenclature of Master-Slave. If we are to migrate to
9 matches
Mail list logo
