From cab38c8515800d4a6fab7203d13184314f4d1238 Mon Sep 17 00:00:00 2001 From: Viktor Sadovnikov Date: Mon, 16 May 2016 18:58:19 +0200 Subject: [PATCH 1/4] weaveworks/scope#1507. Adding Marathon JSON for launching on minimesos cluster --- examples/mesos/README.md | 14 ++++++++++ examples/mesos/minimesos.json | 51 +++++++++++++++++++++++++++++++++++ 2 files changed, 65 insertions(+) create mode 100644 examples/mesos/README.md create mode 100644 examples/mesos/minimesos.json diff --git a/examples/mesos/README.md b/examples/mesos/README.md new file mode 100644 index 000000000..63e74f275 --- /dev/null +++ b/examples/mesos/README.md @@ -0,0 +1,14 @@ +# Launching Weave Scope on Apache Mesos Cluster + +## Launching on minimesos Cluster + +`minimesos` project enables running Apache Mesos cluster on a single machine for prototyping and unit testing of Mesos +frameworks. All running components of `minimesos` cluster are represented by docker containers. To enable reuse of local +docker images, docker in Mesos Agent containers reuses `docker.sock` file of the host. Therefore all started in Agents +containers are also seen on the host. This setup gives single Weave Scope container access to all containers running in +`minimesos` cluster. + +Launching of Weave Scope by providing content `minimesos.json` file to Marathon is a part of default `minimesos` cluster. If +removed from configuration, Weave Scope can be added to the running cluster by `minimesos install --marathonFile ` + +UI of Weave Scope can be accessed on http://172.17.0.1:4040/ diff --git a/examples/mesos/minimesos.json b/examples/mesos/minimesos.json new file mode 100644 index 000000000..3135f1846 --- /dev/null +++ b/examples/mesos/minimesos.json @@ -0,0 +1,51 @@ +{ + "id": "weave-scope", + "cpus": 1, + "mem": 128, + "instances": 1, + "constraints": [ + [ + "hostname", + "UNIQUE" + ] + ], + "container": { + "type": "DOCKER", + "docker": { + "image": "weaveworks/scope:0.15.0", + "network": "HOST", + "privileged": true, + "parameters": [ + { + "key": "pid", + "value": "host" + }, + { + "key": "name", + "value": "weavescope" + } + ] + }, + "volumes": [ + { + "containerPath": "/var/run/docker.sock", + "hostPath": "/var/run/docker.sock", + "mode": "RW" + } + ] + }, + "args": [ + "--probe.docker", + "true" + ], + "env": { + "CHECKPOINT_DISABLE": "" + }, + "portDefinitions": [ + { + "port": 4040, + "protocol": "tcp", + "name": "http" + } + ] +} \ No newline at end of file From 58f80920b3a576939721f620dec6a4f6a8009a04 Mon Sep 17 00:00:00 2001 From: Viktor Sadovnikov Date: Tue, 24 May 2016 09:38:20 +0200 Subject: [PATCH 2/4] weaveworks/scope#1507. disabling new version updates --- examples/mesos/minimesos.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/mesos/minimesos.json b/examples/mesos/minimesos.json index 3135f1846..30452589c 100644 --- a/examples/mesos/minimesos.json +++ b/examples/mesos/minimesos.json @@ -39,7 +39,7 @@ "true" ], "env": { - "CHECKPOINT_DISABLE": "" + "CHECKPOINT_DISABLE": "true" }, "portDefinitions": [ { From b63d3374cbbcf8786136cf6ba88835a0f4b48c21 Mon Sep 17 00:00:00 2001 From: Viktor Sadovnikov Date: Thu, 26 May 2016 10:22:23 +0200 Subject: [PATCH 3/4] weaveworks/scope#1507. README.md: adding example for using latest minimesos.json --- examples/mesos/README.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/examples/mesos/README.md b/examples/mesos/README.md index 63e74f275..3a26da104 100644 --- a/examples/mesos/README.md +++ b/examples/mesos/README.md @@ -8,7 +8,13 @@ docker images, docker in Mesos Agent containers reuses `docker.sock` file of the containers are also seen on the host. This setup gives single Weave Scope container access to all containers running in `minimesos` cluster. -Launching of Weave Scope by providing content `minimesos.json` file to Marathon is a part of default `minimesos` cluster. If -removed from configuration, Weave Scope can be added to the running cluster by `minimesos install --marathonFile ` +Launching of Weave Scope by providing content `minimesos.json` file to Marathon is a part of default `minimesos` cluster. +If removed from configuration, Weave Scope can be added to the running cluster by +`minimesos install --marathonFile `. Example for using the latest, not released yet, version +of Marathon task file + +``` +minimesos install --marathonFile https://raw.githubusercontent.com/weaveworks/scope/master/examples/mesos/minimesos.json +``` UI of Weave Scope can be accessed on http://172.17.0.1:4040/ From edb27e0935564b7b0ba94e3b625f6d896181490d Mon Sep 17 00:00:00 2001 From: Viktor Sadovnikov Date: Fri, 27 May 2016 00:25:13 +0200 Subject: [PATCH 4/4] weaveworks/scope#1507. moving minimesos installation instructions to site/installing.md file --- examples/mesos/README.md | 20 -------------------- site/installing.md | 20 ++++++++++++++++++++ 2 files changed, 20 insertions(+), 20 deletions(-) delete mode 100644 examples/mesos/README.md diff --git a/examples/mesos/README.md b/examples/mesos/README.md deleted file mode 100644 index 3a26da104..000000000 --- a/examples/mesos/README.md +++ /dev/null @@ -1,20 +0,0 @@ -# Launching Weave Scope on Apache Mesos Cluster - -## Launching on minimesos Cluster - -`minimesos` project enables running Apache Mesos cluster on a single machine for prototyping and unit testing of Mesos -frameworks. All running components of `minimesos` cluster are represented by docker containers. To enable reuse of local -docker images, docker in Mesos Agent containers reuses `docker.sock` file of the host. Therefore all started in Agents -containers are also seen on the host. This setup gives single Weave Scope container access to all containers running in -`minimesos` cluster. - -Launching of Weave Scope by providing content `minimesos.json` file to Marathon is a part of default `minimesos` cluster. -If removed from configuration, Weave Scope can be added to the running cluster by -`minimesos install --marathonFile `. Example for using the latest, not released yet, version -of Marathon task file - -``` -minimesos install --marathonFile https://raw.githubusercontent.com/weaveworks/scope/master/examples/mesos/minimesos.json -``` - -UI of Weave Scope can be accessed on http://172.17.0.1:4040/ diff --git a/site/installing.md b/site/installing.md index 225407c01..6e2cc4b10 100644 --- a/site/installing.md +++ b/site/installing.md @@ -15,6 +15,7 @@ The following topics are discussed: * [Using Docker Compose in Service Mode](#docker-compose-sercice) * [Installing Scope on Kubernetes](#k8s) * [Installing Scope on Amazon ECS](#ecs) + * [Installing Scope on minimesos](#minimesos) * [Installing Scope on Mesosphere DC/OS](#dcos) ##Installing Scope on Docker @@ -222,6 +223,25 @@ The link below will launch a sample app using a Cloudformation template, but you For step by step instructions on how to configure the stack, see: [Install Weave to AWS with One-Click](https://www.weave.works/deploy-weave-aws-cloudformation-template/) +##Installing Scope on minimesos + +[minimesos](https://github.com/ContainerSolutions/minimesos) project enables running Apache Mesos cluster on a single machine for prototyping and unit testing of Mesos +frameworks. All running components of `minimesos` cluster are represented by docker containers. To enable reuse of local +docker images, docker in Mesos Agent containers reuses `docker.sock` file of the host. Therefore all started in Agents +containers are also seen on the host. This setup gives single Weave Scope container access to all containers running in +`minimesos` cluster. + +Launching of Weave Scope by providing content `minimesos.json` file to Marathon is a part of default `minimesos` cluster. +If removed from its configuration file, Weave Scope can be added to the running cluster by +`minimesos install --marathonFile `. Example for using the latest, not released yet, version +of Marathon task file + +``` +minimesos install --marathonFile https://raw.githubusercontent.com/weaveworks/scope/master/examples/mesos/minimesos.json +``` + +UI of Weave Scope becomes accessible on http://172.17.0.1:4040/ + ##Installing Scope as a DC/OS Package Scope can be installed as a DC/OS Package through the open Universe.