github/container.training

Fork 0

mirror of https://github.com/jpetazzo/container.training.git synced 2026-05-06 08:56:35 +00:00

Files

Jerome Petazzoni 5bc4e95515 Clarify service discovery

2018-02-27 14:45:08 -06:00

6.8 KiB

Raw Blame History

Our sample application

Visit the GitHub repository with all the materials of this workshop:
https://github.com/jpetazzo/container.training
The application is in the dockercoins subdirectory
Let's look at the general layout of the source code:

there is a Compose file docker-compose.yml ...

... and 4 other services, each in its own directory:
- rng = web service generating random bytes
- hasher = web service computing hash of POSTed data
- worker = background process using rng and hasher
- webui = web interface to watch progress

Compose file format version

Particularly relevant if you have used Compose before...

Compose 1.6 introduced support for a new Compose file format (aka "v2")
Services are no longer at the top level, but under a services section
There has to be a version key at the top level, with value "2" (as a string, not an integer)
Containers are placed on a dedicated network, making links unnecessary
There are other minor differences, but upgrade is easy and straightforward

Service discovery in container-land

We do not hard-code IP addresses in the code
We do not hard-code FQDN in the code, either
We just connect to a service name, and container-magic does the rest

(And by container-magic, we mean "a crafty, dynamic, embedded DNS server")

Example in `worker/worker.py`

redis = Redis("`redis`")


def get_random_bytes():
    r = requests.get("http://`rng`/32")
    return r.content


def hash_bytes(data):
    r = requests.post("http://`hasher`/",
                      data=data,
                      headers={"Content-Type": "application/octet-stream"})

(Full source code available here)

Links, naming, and service discovery

Containers can have network aliases (resolvable through DNS)
Compose file version 2+ makes each container reachable through its service name
Compose file version 1 did require "links" sections
Network aliases are automatically namespaced
- you can have multiple apps declaring and using a service named database
- containers in the blue app will resolve database to the IP of the blue database
- containers in the green app will resolve database to the IP of the green database

What's this application?

It is a DockerCoin miner! .emoji[💰🐳📦🚢]

No, you can't buy coffee with DockerCoins

How DockerCoins works:
- worker asks to rng to generate a few random bytes
- worker feeds these bytes into hasher
- and repeat forever!
- every second, worker updates redis to indicate how many loops were done
- webui queries redis, and computes and exposes "hashing speed" in your browser

Getting the application source code

We will clone the GitHub repository
The repository also contains scripts and tools that we will use through the workshop

Clone the repository on node1:

git clone git://github.com/jpetazzo/container.training

]

(You can also fork the repository on GitHub and clone your fork if you prefer that.)

Running the application

Without further ado, let's start our application.

Go to the dockercoins directory, in the cloned repo:
```
cd ~/container.training/dockercoins
```
Use Compose to build and run all containers:
```
docker-compose up
```

]

Compose tells Docker to build all container images (pulling the corresponding base images), then starts all containers, and displays aggregated logs.

Our application at work

On the left-hand side, the "rainbow strip" shows the container names
On the right-hand side, we see the output of our containers
We can see the worker service making requests to rng and hasher
For rng and hasher, we see HTTP access logs

Connecting to the web UI

"Logs are exciting and fun!" (No-one, ever)
The webui container exposes a web dashboard; let's view it

With a web browser, connect to node1 on port 8000
Remember: the nodeX aliases are valid only on the nodes themselves
In your browser, you need to enter the IP address of your node

]

A drawing area should show up, and after a few seconds, a blue graph will appear.

If the graph doesn't load

If you just see a Page not found error, it might be because your Docker Engine is running on a different machine. This can be the case if:

you are using the Docker Toolbox
you are using a VM (local or remote) created with Docker Machine
you are controlling a remote Docker Engine

When you run DockerCoins in development mode, the web UI static files are mapped to the container using a volume. Alas, volumes can only work on a local environment, or when using Docker4Mac or Docker4Windows.

How to fix this?

Stop the app with ^C, edit dockercoins.yml, comment out the volumes section, and try again.

Why does the speed seem irregular?

It looks like the speed is approximately 4 hashes/second
Or more precisely: 4 hashes/second, with regular dips down to zero
Why?

The app actually has a constant, steady speed: 3.33 hashes/second
(which corresponds to 1 hash every 0.3 seconds, for reasons)
Yes, and?

The reason why this graph is not awesome

The worker doesn't update the counter after every loop, but up to once per second
The speed is computed by the browser, checking the counter about once per second
Between two consecutive updates, the counter will increase either by 4, or by 0
The perceived speed will therefore be 4 - 4 - 4 - 0 - 4 - 4 - 0 etc.
What can we conclude from this?

"I'm clearly incapable of writing good frontend code!" 😀 — Jérôme

Stopping the application

If we interrupt Compose (with ^C), it will politely ask the Docker Engine to stop the app
The Docker Engine will send a TERM signal to the containers
If the containers do not exit in a timely manner, the Engine sends a KILL signal

Stop the application by hitting ^C

]

Some containers exit immediately, others take longer.

The containers that do not handle SIGTERM end up being killed after a 10s timeout.

6.8 KiB Raw Blame History