I feel like calling the slave a worker is confusing, since many applications call their executors workers. I think that minion is suitably exotic as to avoid confusion. On Tue, Jun 2, 2015 at 9:56 AM Pradeep Kiruvale <pradeepkiruv...@gmail.com> wrote:
> > > 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 available, perhaps >> provide a symlink for a while. >> >> >> From: Adam Bordelon >> Reply-To: "user@mesos.apache.org" >> Date: Monday, June 1, 2015 at 5:18 PM >> To: dev, "user@mesos.apache.org" >> Subject: [DISCUSS] Renaming Mesos Slave >> >> 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 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? >> >> 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? >> >> Please voice your thoughts and opinions below. >> >> Thanks! >> -Adam- >> >> P.S. My personal thoughts: >> 1. Mesos Worker [Node] >> 2. Mesos Worker or Agent >> 3. No >> 4. Carefully >> >> This email message contains information that Motus, LLC considers >> confidential and/or proprietary, or may later designate as confidential and >> proprietary. It is intended only for use of the individual or entity named >> above and should not be forwarded to any other persons or entities without >> the express consent of Motus, LLC, nor should it be used for any purpose >> other than in the course of any potential or actual business relationship >> with Motus, LLC. If the reader of this message is not the intended >> recipient, or the employee or agent responsible to deliver it to the >> intended recipient, you are hereby notified that any dissemination, >> distribution, or copying of this communication is strictly prohibited. If >> you have received this communication in error, please notify sender >> immediately and destroy the original message. >> >> Internal Revenue Service regulations require that certain types of >> written advice include a disclaimer. To the extent the preceding message >> contains advice relating to a Federal tax issue, unless expressly stated >> otherwise the advice is not intended or written to be used, and it cannot >> be used by the recipient or any other taxpayer, for the purpose of avoiding >> Federal tax penalties, and was not written to support the promotion or >> marketing of any transaction or matter discussed herein. >> > >
