gistfile1.txt

SANs: Subject Alternate Names

Service Discovery: A mapping between the logical ID of the container to a concrete (routable) IP:PORT pair must be established and maintained.

Zookeeper: ZooKeeper acts as the master election service in the Mesosphere architecture and stores state for the Mesos nodes.
To find if a node is a Leader or Follower (or Standalone), use the command below:
echo srvr | nc localhost 2181 | grep Mode

docker run -d -p 8888:2375 --name docker-swarm -e SWARM_MESOS_USER=root swarm manage -c mesos-experimental --cluster-opt mesos.address=0.0.0.0 --cluster-opt mesos.port=5050 zk://172.31.0.11:2181/mesos

docker run -d --net host --name swarm -e SWARM_MESOS_USER=root swarm:1.0.0-rc2 --debug manage -c mesos-experimental -H 0.0.0.0:8888 --cluster-opt mesos.address=0.0.0.0 zk://172.31.0.11:2181/mesos

export DOCKER_HOST=tcp://0.0.0.0:8888
for i in {0..9} ; do docker -D run -d -p 3101$i:80 --name ww$i -m 16m nginx ; done

If you get the following error:
FATA[0005] Error response from daemon: no resources available to schedule container

restart swarm:

DOCKER_HOST= docker stop docker-swarm ; DOCKER_HOST= docker start docker-swarm


To restart Mesos Slaves:

sudo rm -rf /tmp/mesos/meta/slaves
sudo service mesos-slave start

Look at log files:
tail /var/log/mesos/mesos-slave.INFO


The centerpiece of Mesosphere is Apache Mesos. Mesos installs with two different components, the master and the slave. The master is a process which runs on a node in the cluster and orchestrates the running of tasks on slaves by receiving resource offers from slaves and offering those resources to registered frameworks, such as Mesosphere Marathon or Docker Swarm.