-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 code? -- Paul On Tue, Jun 2, 2015 at 12:53 PM, haosdent <haosd...@gmail.com> wrote: > 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 confusion. >> >> 1. Mesos worker >> 2. Mesos worker >> 3. No >> 4. Documentation, then API with a full deprecation cycle >> >> Dave >> >> On Mon, Jun 1, 2015, at 02: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 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 >> >> >> > > > > -- > Best Regards, > Haosdent Huang > -- -- Paul Brett
