From baf48657d05446eeaa5127d2f2dda3552172b695 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Petazzoni?= Date: Sun, 15 Oct 2017 23:13:06 +0200 Subject: [PATCH] Clean up a bunch of titles --- docs/extratips.md | 28 ---------------------------- docs/ipsec.md | 16 +--------------- docs/swarmtools.md | 20 -------------------- 3 files changed, 1 insertion(+), 63 deletions(-) diff --git a/docs/extratips.md b/docs/extratips.md index 92193f9b..76b1a3b1 100644 --- a/docs/extratips.md +++ b/docs/extratips.md @@ -1,5 +1,3 @@ -class: extra-details - # Controlling Docker from a container - In a local environment, just bind-mount the Docker control socket: @@ -22,8 +20,6 @@ More resources on this topic: --- -class: extra-details - ## Bind-mounting the Docker control socket - In Swarm mode, bind-mounting the control socket gives you access to the whole cluster @@ -37,8 +33,6 @@ class: extra-details --- -class: extra-details - ## Constraints and global services (New in Docker Engine 1.13) @@ -59,8 +53,6 @@ class: extra-details --- -class: extra-details - ## Constraints and dynamic scheduling (New in Docker Engine 1.13) @@ -79,8 +71,6 @@ class: extra-details --- -class: extra-details - ## Shortcomings of dynamic scheduling .warning[If a service becomes "unschedulable" (constraints can't be satisfied):] @@ -98,8 +88,6 @@ class: extra-details --- -class: extra-details - # Node management - SwarmKit allows to change (almost?) everything on-the-fly @@ -108,8 +96,6 @@ class: extra-details --- -class: extra-details - ## Node availability ```bash @@ -130,8 +116,6 @@ docker node update --availability --- -class: extra-details - ## Managers and workers - Nodes can be promoted to manager with `docker node promote` @@ -145,8 +129,6 @@ class: extra-details --- -class: extra-details - ## Removing nodes - You can leave Swarm mode with `docker swarm leave` @@ -161,8 +143,6 @@ class: extra-details --- -class: extra-details - ## Join tokens and automation - If you have used Docker 1.12-RC: join tokens are now mandatory! @@ -179,8 +159,6 @@ class: extra-details --- -class: extra-details - ## Disk space management: `docker system df` - Shows disk usage for images, containers, and volumes @@ -200,8 +178,6 @@ Note: `docker system` is new in Docker Engine 1.13. --- -class: extra-details - ## Reclaiming unused resources: `docker system prune` - Removes stopped containers @@ -225,8 +201,6 @@ Note: `docker system prune -a` will also remove *unused* images. --- -class: extra-details - ## Events - You can get a real-time stream of events with `docker events` @@ -248,8 +222,6 @@ class: extra-details --- -class: extra-details - ## Getting *all the events* - There is no built-in to get a stream of *all the events* on *all the nodes* diff --git a/docs/ipsec.md b/docs/ipsec.md index 7feb0010..d1dfbef2 100644 --- a/docs/ipsec.md +++ b/docs/ipsec.md @@ -1,5 +1,3 @@ -class: ipsec - # Securing overlay networks - By default, overlay networks are using plain VXLAN encapsulation @@ -16,8 +14,6 @@ class: ipsec --- -class: ipsec - ## Creating two networks: encrypted and not - Let's create two networks for testing purposes @@ -40,8 +36,6 @@ class: ipsec --- -class: ipsec - ## Deploying a web server sitting on both networks - Let's use good old NGINX @@ -64,8 +58,6 @@ class: ipsec --- -class: ipsec - ## Sniff HTTP traffic - We will use `ngrep`, which allows to grep for network traffic @@ -83,8 +75,6 @@ class: ipsec -- -class: ipsec - Seeing tons of HTTP request? Shutdown your DockerCoins workers: ```bash docker service update dockercoins_worker --replicas=0 @@ -92,8 +82,6 @@ docker service update dockercoins_worker --replicas=0 --- -class: ipsec - ## Check that we are, indeed, sniffing traffic - Let's see if we can intercept our traffic with Google! @@ -115,7 +103,7 @@ When you do the `curl`, you should see the HTTP request in clear text in the out --- -class: ipsec, extra-details +class: extra-details ## If you are using Play-With-Docker, Vagrant, etc. @@ -129,8 +117,6 @@ class: ipsec, extra-details --- -class: ipsec - ## Try to sniff traffic across overlay networks - We will run `curl web` through both secure and insecure networks diff --git a/docs/swarmtools.md b/docs/swarmtools.md index ed747710..32c63773 100644 --- a/docs/swarmtools.md +++ b/docs/swarmtools.md @@ -1,5 +1,3 @@ -class: swarmtools - # SwarmKit debugging tools - The SwarmKit repository comes with debugging tools @@ -14,8 +12,6 @@ class: swarmtools --- -class: swarmtools - ## Building the SwarmKit tools - We are going to install a Go compiler, then download SwarmKit source and build it @@ -39,8 +35,6 @@ the build might fail. In that case, just skip the Swarm tools section. --- -class: swarmtools - ## Getting cluster-wide task information - The Docker API doesn't expose this directly (yet) @@ -54,8 +48,6 @@ class: swarmtools --- -class: swarmtools - ## Using `swarmctl` - The Docker Engine places the SwarmKit control socket in a special path @@ -80,8 +72,6 @@ class: swarmtools --- -class: swarmtools - ## `swarmctl` in action - Let's review a few useful `swarmctl` commands @@ -102,8 +92,6 @@ class: swarmtools --- -class: swarmtools - ## `swarmctl` notes - SwarmKit is vendored into the Docker Engine @@ -121,8 +109,6 @@ class: swarmtools --- -class: swarmtools - ## `swarm-rafttool` - SwarmKit stores all its important data in a distributed log using the Raft protocol @@ -139,8 +125,6 @@ class: swarmtools --- -class: swarmtools - ## The powers of `swarm-rafttool` With `swarm-rafttool`, you can: @@ -157,8 +141,6 @@ It *cannot* work on live files, so you must stop Docker or make a copy first. --- -class: swarmtools - ## Using `swarm-rafttool` - First, let's make a copy of the current Swarm data @@ -179,8 +161,6 @@ class: swarmtools --- -class: swarmtools - ## Dumping the Raft log - We have to indicate the path holding the Swarm data