Adding my two cents: If I have seen the following terminology being in a some places:
Mesos-master => director/orchestrator : the reasoning here is simple, there is always only one orchestrator and has the job of directing others to do as per the current requirements. The group of orchestrators is referred to as an ensemble in the zookeeper sense and hence we world be able to use the leader-follower understanding straight away. Mesos-slave => resource provider: the reasoning here is not host based because the slave process simply does the process of creating resource offers. It has no concept of the node if I was to squint at it a little. We tell it what resources are available and it provides them to the orchestrator for consumption. Again, nothing here is ground breaking and that is the point. There is a lot of knowledge that can be instantly used if we use common names that represent the underlying concepts and not done goofy names which mean nothing and make me relearn ( unless a case can be made that the concept being represented is actually novel ). -- Ankur On Jun 3, 2015 8:19 AM, "Tony Becker" <[email protected]> wrote: > I tweeted this suggestion to Brian Hicks and he asked me to send it to > the list for consideration: > > How about Director/Drone? > > "Robot" (in the Čapek sense) would be good to replace "slave" too. > Maybe Director/Robot? > > (This is just personal, but to me, leader/follower implies a certain > level of human agency where there is none.) > > -- > Tony Becker > Principal, Fort Pedro Informatics LLC > Web: http://fortpedro.com >
