swarm

Ajout de node dans swarm

Pour gérer un swarm, il faut, avant tout, obtenir le token… La syntax est :

pi@pi4node001:~ $ docker swarm join-token
"docker swarm join-token" requires exactly 1 argument.
See 'docker swarm join-token --help'.

Usage:  docker swarm join-token [OPTIONS] (worker|manager)

Manage join tokens
pi@pi4node001:~ $

pi@pi4node001:~ $ docker swarm join-token

"docker swarm join-token" requires exactly 1 argument.

See 'docker swarm join-token --help'.

Usage: docker swarm join-token [OPTIONS] (worker|manager)

Manage join tokens

pi@pi4node001:~ $

Donc quand on veut ajouter un node de type MANAGER :

pi@pi4node001:~ $ docker swarm join-token manager
To add a manager to this swarm, run the following command:

docker swarm join --token SWMTKN-1-2kr5jo0trm2o9bvnypqlzizx1exxivfeitqzi9smnhv6gxsd0f-95rzv0a1mbp0f8k1xkg55176n 192.168.0.201:2377

pi@pi4node001:~ $

pi@pi4node001:~ $ docker swarm join-token manager

To add a manager to this swarm, run the following command:

docker swarm join --token SWMTKN-1-2kr5jo0trm2o9bvnypqlzizx1exxivfeitqzi9smnhv6gxsd0f-95rzv0a1mbp0f8k1xkg55176n 192.168.0.201:2377

pi@pi4node001:~ $

et pour un de type WORKER :

pi@pi4node001:~ $ docker swarm join-token worker 
To add a worker to this swarm, run the following command:

    docker swarm join --token SWMTKN-1-2kr5jo0trm2o9bvnypqlzizx1exxivfeitqzi9smnhv6gxsd0f-8agpq7585s28ppp6gu1ldkf2x 192.168.0.201:2377

pi@pi4node001:~ $

pi@pi4node001:~ $ docker swarm join-token worker

To add a worker to this swarm, run the following command:

docker swarm join --token SWMTKN-1-2kr5jo0trm2o9bvnypqlzizx1exxivfeitqzi9smnhv6gxsd0f-8agpq7585s28ppp6gu1ldkf2x 192.168.0.201:2377

pi@pi4node001:~ $

maintenant, il faut se connecter sur le node voulu et exécuter la commande ci-dessusplus

dockerswarm

Visualisation du swarm

Quand docker swarm est installé, j’ai défini une application bien pratique de visualisation de l’état du swarm : La procédure d’installation est :

pi@pi4node001:~ $ <strong>docker node ls</strong>
ID                            HOSTNAME     STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
ppyfmhdq6p4xpflqj17eay2cm *   pi4node001   Ready     Active         Leader           20.10.5
pwsktgnu30hvtx5zkgsz4ay2v     pi4node002   Ready     Active                          20.10.5
zmt3lly41a9ultipey0p42oor     pi4node003   Ready     Active                          20.10.5
ushbeebwkt20orsg29uhy8420     pi4node004   Ready     Active                          20.10.5
pi@pi4node001:~ $ <strong>docker service create \
        --name viz \
        --publish 8080:8080/tcp \
        --constraint node.role==manager \
        --mount type=bind,src=/var/run/docker.sock,dst=/var/run/docker.sock \
        alexellis2/visualizer-arm:latest</strong>
ki6uzmz4myuuyuwpb74mtabqh
overall progress: 1 out of 1 tasks
1/1: running   [==================================================>]
verify: Service converged
pi@pi4node001:~ $ <strong>docker service ls</strong>
ID             NAME      MODE         REPLICAS   IMAGE                              PORTS
ki6uzmz4myuu   viz       replicated   1/1        alexellis2/visualizer-arm:latest   *:8080->8080/tcp
pi@pi4node001:~ $

pi@pi4node001:~ $ docker node ls

ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS ENGINE VERSION

ppyfmhdq6p4xpflqj17eay2cm * pi4node001 Ready Active Leader 20.10.5

pwsktgnu30hvtx5zkgsz4ay2v pi4node002 Ready Active 20.10.5

zmt3lly41a9ultipey0p42oor pi4node003 Ready Active 20.10.5

ushbeebwkt20orsg29uhy8420 pi4node004 Ready Active 20.10.5

pi@pi4node001:~ $ docker service create \

--name viz \

--publish 8080:8080/tcp \

--constraint node.role==manager \

--mount type=bind,src=/var/run/docker.sock,dst=/var/run/docker.sock \

alexellis2/visualizer-arm:latest

ki6uzmz4myuuyuwpb74mtabqh

overall progress: 1 out of 1 tasks

1/1: running [==================================================>]

verify: Service converged

pi@pi4node001:~ $ docker service ls

ID NAME MODE REPLICAS IMAGE PORTS

ki6uzmz4myuu viz replicated 1/1 alexellis2/visualizer-arm:latest *:8080->8080/tcp

pi@pi4node001:~ $

Swarm est apparement beaucoup moins gourmand que k3s….plus

ClusterdockerswarmBASHRaspberry