Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
modul:m347:learningunits:lu07:lu07a [2025/03/07 15:22] – angelegt dgaravaldi | modul:m347:learningunits:lu07:lu07a [2025/06/17 21:44] (aktuell) – dgaravaldi | ||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
- | ====== LU07a - Einführung in Docker Swarm ====== | + | ====== LU07a - Projekt Taskmanager |
===== Ziele ===== | ===== Ziele ===== | ||
- | -Ich kann den Zweck von Docker Swarm beschreiben. | + | -Ich kann mit eine Anwendung sinnvoll in mehrere Container betreiben und testen. |
- | -Ich kann die grundlegenden Komponenten von Docker Swarm aufzählen. | + | -Ich kann bei Fehlern entsprechende Hinweismeldungen analysieren und interpretieren. |
+ | -Ich kann bei Fehlern erste Massnahmen benennen und umsetzen. | ||
\\ | \\ | ||
- | ===== Docker-Swarm ===== | ||
- | Cluster and scale containerized applications | ||
- | |||
- | ==== Introduction ==== | ||
- | Docker Swarm is similar Kubernetes — they both orchestrate containerized applications. Kubernetes has a lot more momentum and a more active community and ecosystem. However, Swarm is a lot easier to use and is a popular choice for many small-to-medium businesses and application deployments. Learning Swarm is a stepping-stone to learning Kubernetes. | ||
- | |||
- | Docker Swarm consists of two parts: | ||
- | |||
- | === A secure cluster of Docker hosts === | ||
- | On the clustering front, Swarm groups one or more '' | ||
- | |||
- | === An orchestrator of microservices apps === | ||
- | On the '' | ||
- | |||
- | |||
- | ==== Swarm primer ==== | ||
- | On the clustering front, a swarm consists of one or more '' | ||
- | |||
- | Nodes are configured as '' | ||
- | |||
- | {{: | ||
- | |||
- | The configuration and state of the swarm is held in a distributed database replicated on all managers. It’s kept in-memory and is extremely up-to-date. However, the best thing is that it requires zero configuration — it’s installed as part of the swarm and just takes care of itself. | ||
- | |||
- | TLS is so tightly integrated that it’s impossible to build a swarm without it. In today’s security conscious world, things like this deserve all the plaudits they get. Swarm uses TLS to encrypt communications, | ||
- | |||
- | On the orchestration front, the atomic unit of scheduling on a swarm is the service. This is a high-level construct that wraps some advanced features around containers. These features include scaling, rolling updates, and simple rollbacks. It’s useful to think of a service as an enhanced container. | ||
+ | ===== Übungen ===== | ||
+ | * Lösen Sie die Übung(en) im Repo-Verzeichnis '' | ||
+ | * Grundlage siehe [[..: |