Mesos#

Table of Contents

Questions to be answered#

Assign only part of node resources to a slave ?#

Can I run a mesos-slave on a node, but not dedicate all resources of that node to the cluster ?
For example if I want to run multiple clusters and run multiple slaves from different clusters on the same node.

This can be done with the --resources switch. Create the file /etc/mesos-slave/resources with the following content : 

cpus(*):0.3; mem(*):512; disk(*):6543; ports(*):[31000-32000]
Then you might have to remove rm -vf /tmp/mesos/meta/slaves/latest and do a systemctl restart mesos-slave

How to setup security, at least slave authentication ?#

See the Mesos configuration documentation at :

I got it, create the following files (and restarting master and slave), as the doc says you can create files for flags :

A file named the same name as the flag may be placed in the /etc/mesos-master directory. So a /etc/mesos-master/hostname file containing the value of 10.141.141.10 is like running the master with the option --hostname=10.141.141.10 : 

/etc/mesos/mesos-master/authenticate  ==> true
/etc/mesos/mesos-master/authenticate_slaves  ==> true
/etc/mesos/mesos-master/credentials  ==> /etc/mesos/mesos-config/mesos-master.passwd
/etc/mesos/mesos-slave/credential ==> /etc/mesos/mesos-config/mesos-slave.passwd
/etc/mesos/mesos-config/mesos-master.passwd  ==> user password
/etc/mesos/mesos-config/mesos-slave.passwd  ==> user password

Use the mesos state command to verify: 

[root@node1 conf]# mesos state
{
    "lost_tasks": 0, 
    "build_user": "root", 
    "pid": "master@192.168.33.10:5050", 
    "build_time": 1427387871, 
    "finished_tasks": 0, 
    "unregistered_frameworks": [], 
    "id": "20150421-050455-169978048-5050-945", 
    "git_sha": "e890e2414903bb69cab730d5204f10b10d2e91bb", 
    "build_date": "2015-03-26 16:37:51", 
    "hostname": "node1", 
    "version": "0.22.0", 
    "log_dir": "/var/log/mesos", 
    "killed_tasks": 0, 
    "leader": "master@192.168.33.10:5050", 
    "deactivated_slaves": 0, 
    "failed_tasks": 0, 
    "start_time": 1429592695.33795, 
    "git_tag": "0.22.0", 
    "staged_tasks": 0, 
    "completed_frameworks": [], 
    "elected_time": 1429592710.071, 
    "orphan_tasks": [], 
    "activated_slaves": 0, 
    "frameworks": [], 
    "flags": {
        "help": "false", 
        "zk": "zk://localhost:2181/mesos", 
        "recovery_slave_removal_limit": "100%", 
        "port": "5050", 
        "logbufsecs": "0", 
        "authenticate": "true", 
        "work_dir": "/var/lib/mesos", 
        "slave_reregister_timeout": "10mins", 
        "authenticators": "crammd5", 
        "authenticate_slaves": "true", 
        "framework_sorter": "drf", 
        "version": "false", 
        "log_dir": "/var/log/mesos", 
        "logging_level": "INFO", 
        "log_auto_initialize": "true", 
        "registry_strict": "false", 
        "registry_fetch_timeout": "1mins", 
        "root_submissions": "true", 
        "webui_dir": "/usr/share/mesos/webui", 
        "registry": "replicated_log", 
        "credentials": "/etc/mesos-config/mesos-master.passwd", 
        "allocation_interval": "1secs", 
        "zk_session_timeout": "10secs", 
        "quorum": "1", 
        "user_sorter": "drf", 
        "quiet": "false", 
        "registry_store_timeout": "5secs", 
        "initialize_driver_logging": "true"
    }, 
    "started_tasks": 0, 
    "slaves": []
}

But it all fails : 

Apr 21 06:11:48 node1 mesos-master[945]: W0421 06:11:48.951118  1175 master.cpp:3866] Failed to authenticate slave(1)@192.168.33.10:5051: Failed to get list of mechanisms: SASL(-4): no mechanism available: Internal Error -4 in server.c near line 1757
Apr 21 06:11:48 node1 mesos-master[945]: I0421 06:11:48.954591  1175 master.cpp:3813] Authenticating slave(1)@192.168.33.10:5051
Apr 21 06:11:48 node1 mesos-master[945]: I0421 06:11:48.954753  1175 master.cpp:3824] Using default CRAM-MD5 authenticator
Apr 21 06:11:48 node1 mesos-master[945]: I0421 06:11:48.955693  1175 authenticator.hpp:170] Creating new server SASL connection
Apr 21 06:11:48 node1 mesos-master[945]: W0421 06:11:48.957067  1175 authenticator.hpp:213] Failed to get list of mechanisms: no mechanism available
I reverted back to no security

Can I run without root ?#

By default everything (master and slave) run with root. Can you run without root, and if so, what are the consequences ?

Install summary#

A short summary of playing around with mesos , marathon and chronos .
Mostly provided by the Mesosphere intro course.

add this option to your Vagrantfile: 

      config.vm.box_download_insecure = true

Login with vagrant@localhost:2222 pw=vagrant , or "vagrant ssh"

Install mesos: 

    sudo rpm -Uvh http://repos.mesosphere.io/el/7/noarch/RPMS/mesosphere-el-repo-7-1.noarch.rpm
    sudo yum -y install mesos marathon

Install zookeeper, the distributed configuration service used by mesos: 

    sudo rpm -Uvh http://archive.cloudera.com/cdh4/one-click-install/redhat/6/x86_64/cloudera-cdh-4-0.x86_64.rpm
    sudo yum -y install zookeeper zookeeper-server

Initialize and start Zookeeper: 

    sudo -u zookeeper zookeeper-server-initialize --myid=1
    sudo service zookeeper-server start

Install java: yum -y install java-1.8.0-openjdk

Run the interactive zookeeper shell : /usr/lib/zookeeper/bin/zkCli.sh and issue some tests :

Start mesos master and slave : 

    systemctl start mesos-master
    systemctl start mesos-slave
Install mesos: 
    sudo rpm -Uvh http://repos.mesosphere.io/el/7/noarch/RPMS/mesosphere-el-repo-7-1.noarch.rpm
    sudo yum -y install mesos marathon

Install zookeeper, the distributed configuration service used by mesos: 

    sudo rpm -Uvh http://archive.cloudera.com/cdh4/one-click-install/redhat/6/x86_64/cloudera-cdh-4-0.x86_64.rpm
    sudo yum -y install zookeeper zookeeper-server

Initialize and start Zookeeper: 

    sudo -u zookeeper zookeeper-server-initialize --myid=1
    sudo service zookeeper-server start

Install java: yum -y install java-1.8.0-openjdk

Run the interactive zookeeper shell : /usr/lib/zookeeper/bin/zkCli.sh and issue some tests :

Start mesos master and slave : 

    systemctl start mesos-master
    systemctl start mesos-slave

Mesos webui available at http://192.168.33.10:5050

Play around a bit with mesos : 

    export MASTER=$(mesos-resolve `cat /etc/mesos/zk` 2>/dev/null)
    mesos help

Bring up a second node, node2 at 192.168.33.12 :

Install mesos: 

    sudo rpm -Uvh http://repos.mesosphere.io/el/7/noarch/RPMS/mesosphere-el-repo-7-1.noarch.rpm
    sudo yum -y install mesos marathon

Install zookeeper, the distributed configuration service used by mesos: 

    sudo rpm -Uvh http://archive.cloudera.com/cdh4/one-click-install/redhat/6/x86_64/cloudera-cdh-4-0.x86_64.rpm
    sudo yum -y install zookeeper zookeeper-server

Initialize and start Zookeeper: 

    sudo -u zookeeper zookeeper-server-initialize --myid=1
    sudo service zookeeper-server start

Run the interactive zookeeper shell : /usr/lib/zookeeper/bin/zkCli.sh and issue some tests :

Edit zookeeper config at /etc/mesos/zk, change the IP address to the address of the master.

Start mesos slave : 

    sudo systemctl start mesos-slave

Make sure the nodes are DNS accessible (update /etc/hosts) . Logging of marathon, be default, goes to syslog (/var/log/messages)

Running Tasks always have a port, and this port is webaccessible giving you access to stdout and stderr.

Messing with the marathon REST api (see Marathon REST api

Delete an app: curl -X DELETE http://192.168.33.10:8080/v2/apps/test | python -m json.tool

Create an app by posting the following data in (file app1.json) : 

    {
  "id": "/app1",
  "cmd": "python -m SimpleHTTPServer $PORT",
  "args": null,
  "user": null,
  "env": {},
  "instances": 3,
  "cpus": 0.9,
  "mem": 16.0,
  "disk": 10.0,
  "executor": "",
  "constraints": [],
  "uris": ["/testapp"],
  "storeUrls": [],
  "ports": [10000],
  "requirePorts": false,
  "backoffSeconds": 1,
  "backoffFactor": 1.15,
  "maxLaunchDelaySeconds": 3600,
  "container": null,
  "healthChecks": [],
  "dependencies": [],
  "upgradeStrategy": {
    "minimumHealthCapacity": 1.0,
    "maximumOverCapacity": 1.0
  }
}

curl -v -H "Content-Type: application/json" -X POST --data @app1.json http://192.168.33.10:8080/v2/apps

Now install chronos (the cron for mesos) : 

    sudo yum -y install chronos
    sudo service chronos start

Chronos installs as a mesos framework, like marathon does. (marathon is a sort of init.d for mesos) Chronos is available at http://192.168.33.10:4400/

Install the mesos command line utility : 

    curl "https://bootstrap.pypa.io/get-pip.py" -o "get-pip.py"
    sudo python get-pip.py
    sudo pip install virtualenv
    sudo pip install mesos.cli

Run mesos-slave in a docker container

First create a slightly modified container from redjack/mesos-slave (just installing python to it) .

Use the following cmd to start the container : 

docker run -d -e MESOS_LOG_DIR=/var/log -e MESOS_RESOURCES='cpus(*):0.3; mem(*):512; disk(*):6543; ports(*):[31000-32000]' -e MESOS_MASTER=zk://192.168.33.10:2181/mesos -e MESOS_HOSTNAME=slave3 -p 5051:5051 -p 8000:8000 --name slave3 --hostname slave3 harry:mesos-slave

Also make sure to edit the /etc/hosts and add an entry for this node (use the IP address of the docker container, not the host).

Logging#

Create /etc/rsyslog.d/mesos.conf with following content : 

if $programname == 'marathon' then {
   action(type="omfile" file="/var/log/mesos/marathon.log")
}

if $programname == 'chronos' then {
   action(type="omfile" file="/var/log/mesos/chronos.log")
}

if $programname == 'mesos-master' then {
   action(type="omfile" file="/var/log/mesos/mesos-master.log")
}

if $programname == 'mesos-slave' then {
   action(type="omfile" file="/var/log/mesos/mesos-slave.log")
}

And look at /var/log/mesos/ for the resulting files.

This particular version was published on 23-Apr-2022 17:05 by Harry Metske.Top