Skip to content

Latest commit

 

History

History
100 lines (87 loc) · 4.43 KB

UsingCalicoMesos.md

File metadata and controls

100 lines (87 loc) · 4.43 KB
Raw

warning This document applies to the HEAD of the calico-mesos-deployments source tree.

View the calico-mesos-deployments documentation for the latest release here.

Using Calico Mesos

The following information includes application json and information on launching tasks in a Mesos Cluster with Calico.

Test Cluster Health

Before you start launching tasks with Marathon, we suggest running the Calico-Mesos Test Framework. This Framework will register with mesos directly and launch ping and sleep tasks across your mesos cluster, verifiying netgroup enforcement and network connectivity between tasks.

To launch the framework, run the following docker command from any host that can communicate with your master (we recommend simply running it directly on the master itself):

docker run --net=host calico/calico-mesos-framework <master-ip>:5050
  • Some tests require multiple hosts to ensure cross-host communication, and may fail unless you are running 2+ agents.
  • Additionally, if running your cluster in the public cloud, cross-host tests will fail unless you Enable IP over IP

Be sure to contact us on Slack if your tests are still not passing!

Launching Tasks with Marathon

Calico is compatible with all frameworks which use the new NetworkInfo protobuf when launching tasks. Marathon has introduced limited support for this in v0.14.0.

Launching Marathon

If you haven't followed one of our guides which includes Marathon, quickly launch it with the following command:

docker run \
-e MARATHON_MASTER=zk://<ZOOKEEPER-IP>:2181/mesos \
-e MARATHON_ZK=zk://<ZOOKEEPER-IP>:2181/marathon \
-p 8080:8080 \
mesosphere/marathon:v0.14.0

Launching Tasks

Marathon-v0.14.0 supports two new fields in an application's JSON file:

  • ipAddress: Specifiying this field grants the application an IP Address networked by Calico.
  • group: Groups are roughly equivalent to Calico Profiles. The default implementation isolates applications so they can only communicate with other applications in the same group. Assign a task the static public group to allow it to communicate with any other application.

See Marathon's IP-Per-Task documentation for more information.

The Marathon UI does not yet include a field for specifiying NetworkInfo, so we'll use the command line to launch an app with Marathon's REST API. Below is a sample app.json file that is configured to receive an address from Calico:

{
    "id":"/calico-apps",
    "apps": [
        {
            "id": "hello-world-1",
            "cmd": "ip addr && sleep 30",
            "cpus": 0.1,
            "mem": 64.0,
            "ipAddress": {
                "groups": ["my-group-1"]
            }
        }
    ]
}

Send the app.json to marathon to launch it:

curl -X PUT -H "Content-Type: application/json" http://localhost:8080/v2/groups/calico-apps  -d @app.json

Launching Docker Images

The release of Mesos 0.27.0 includes changes to the Mesos Containerizer which enable it to launch docker images. Using an experimental build of Marathon (djosborne/marathon:docker), we can launch docker images networked with calico with the following json blob:

{
    "id":"/calico-apps",
    "apps": [
        {
            "id": "unified-1",
            "cmd": "ip addr && sleep 30",
            "cpus": 0.1,
            "mem": 64.0,
            "ipAddress": {
                "groups": ["my-group-1"]
            },
            "container": {
                "type": "MESOS",
                "mesos": {
                    "image": {
                        "type": "DOCKER",
                        "docker": {
                            "name": "ubuntu:14.04"
                        }
                    }
                }
            }
        }
    ]
}

Analytics