Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/binocarlos/powerstrip-swarm-demo
Demo a combo of powerstrip-flocker and powerstrip-weave working with swarm
https://github.com/binocarlos/powerstrip-swarm-demo
Last synced: 10 days ago
JSON representation
Demo a combo of powerstrip-flocker and powerstrip-weave working with swarm
- Host: GitHub
- URL: https://github.com/binocarlos/powerstrip-swarm-demo
- Owner: binocarlos
- Created: 2015-03-13T15:09:30.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2015-09-09T10:35:37.000Z (about 9 years ago)
- Last Synced: 2024-04-14T14:36:46.173Z (7 months ago)
- Language: Shell
- Size: 159 KB
- Stars: 5
- Watchers: 3
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# powerstrip-swarm-demo
A demo of [powerstrip-flocker](https://github.com/clusterhq/powerstrip-flocker) and [powerstrip-weave](https://github.com/binocarlos/powerstrip-weave) working with [swarm](https://github.com/docker/swarm)
[](https://asciinema.org/a/19305)
## install
First you need to install:
* [virtualbox](https://www.virtualbox.org/wiki/Downloads)
* [vagrant](http://www.vagrantup.com/downloads.html)
## start vms
To run the demo:
```bash
$ git clone https://github.com/binocarlos/powerstrip-swarm-demo
$ cd powerstrip-swarm-demo
$ vagrant up
```
## automated example
We have included a script that will run through each of the commands shown above. To run the script, run the following commnads:
```bash
$ vagrant ssh master
master$ sudo bash /vagrant/run.sh demo
```
## info
You can see the state of the swarm by doing this on the master:
```bash
$ vagrant ssh master
master$ DOCKER_HOST=localhost:2375 docker ps -a
```
This displays the containers used for powerstrip, flocker and weave
You can see the state of the weave network by doing this on node1 or node2:
```bash
$ vagrant ssh node1
node1$ sudo bash /vagrant/install.sh weave status
```
## about
This demo consists of 3 servers - a master and 2 nodes.
The master runs the swarm deamon and the flocker control server - the 2 nodes each run powerstrip and the 2 powerstrip adapters (for flocker and weave).
```
docker client
|
swarm deamon
flocker-control
/ \
node1 node2
disk SSD
| |
powerstrip powerstrip
flocker flocker
weave weave
| |
docker docker
```
We run a database and a HTTP server on node1. We then decide to upgrade our database container to run on a server that has an SSD.
The IP address to connect to the database is hardcoded - when we move the database container we are migrating the IP address AND the data!
#### Initial Layout:
* NODE1 (disk)
* HTTP server
* Database server (10.255.0.10 + /flocker/data)
* NODE2 (SSD)
#### Final Layout:
* NODE1 (disk)
* HTTP server
* NODE2 (SSD)
* Database server (10.255.0.10 + /flocker/data)
## conclusion
We have moved both an IP address and a data volume across hosts using nothing more than the docker client!
## Manual example
If we run each step of the example manually, we can see clearly what is happening on each step.
#### Step 1
First we SSH onto the master and export `DOCKER_HOST`:
```bash
$ vagrant ssh master
master$ export DOCKER_HOST=localhost:2375
```
#### Step 2
Then we start the HTTP server on node1:
```bash
master$ docker run -d \
--name demo-server \
-e constraint:storage==disk \
-e WEAVE_CIDR=10.255.0.11/24 \
-e API_IP=10.255.0.10 \
-p 8080:80 \
binocarlos/multi-http-demo-server:latest
```
#### Step 3
Then we start the DB server on node1:
```bash
master$ docker run -d \
--hostname disk \
--name demo-api \
-e constraint:storage==disk \
-e WEAVE_CIDR=10.255.0.10/24 \
-v /flocker/data1:/tmp \
binocarlos/multi-http-demo-api:latest
```
#### Step 4
Then we hit the web service a few times to increase the number:
```bash
master$ curl -L http://172.16.255.251:8080
master$ curl -L http://172.16.255.251:8080
master$ curl -L http://172.16.255.251:8080
master$ curl -L http://172.16.255.251:8080
master$ curl -L http://172.16.255.251:8080
```
#### Step 5
Then we kill the database container:
```bash
master$ docker rm -f demo-api
```
#### Step 6
Now we start the DB server on node2:
```bash
master$ docker run -d \
--hostname ssd \
--name demo-api \
-e constraint:storage==ssd \
-e WEAVE_CIDR=10.255.0.10/24 \
-v /flocker/data1:/tmp \
binocarlos/multi-http-demo-api:latest
```
#### Step 7
Then we hit the web service a few times to ensure that it:
* has kept the state after having migrated
* can still communicate with the DB server
```bash
master$ curl -L http://172.16.255.251:8080
master$ curl -L http://172.16.255.251:8080
master$ curl -L http://172.16.255.251:8080
master$ curl -L http://172.16.255.251:8080
master$ curl -L http://172.16.255.251:8080
```
#### Step 8
Now we close the 2 containers
```bash
master$ docker rm -f demo-api
master$ docker rm -f demo-server
```
## run tests
To run the acceptance tests:
```bash
$ make test
```
This will `vagrant up` and then `bash test.sh`.
`test.sh` will use `vagrant ssh -c ""` style commands to run through the following tests:
* a basic data migration using powerstrip-flocker
* launch the web and api servers and hit with curl checking output
* kill the api server
* migrate the api server
* hit the web server checking the output contains the tag: ssd meaning the migration happened