Consul and docker swarm cluster
0 likes683 views
The document discusses setting up a Docker Swarm cluster with 3 Raspberry Pi nodes and integrating Consul for service discovery. It begins with an introduction to Consul and its key features like service discovery, health checking, and key-value storage. It then describes deploying Consul and a Swarm master on one node, registering a sample web service, and verifying the cluster. Finally, it explores the Consul UI and adds a Docker UI for visualizing the cluster.
Consul and docker swarm cluster
- 1. Container Cluster Consul & Swarm Eueung Mulyana http://eueung.github.io/docker-stuff/consul CodeLabs | Attribution-ShareAlike CC BY-SA 1 / 26
- 2. Outline Consul - Introduction RPI Swarm Cluster + Consul 2 / 26
- 4. 4 / 26 Consul Consul is s a tool for discovering and con guring services in our infrastructure. Key Features Service Discovery | Health Checking | Key/Value Store | Multi Datacenter
- 5. Service Discovery Clients of Consul can provide a service, such as api or mysql, and other clients can use Consul to discover providers of a given service. Using either DNS or HTTP, applications can easily nd the services they depend upon. Health Checking Consul clients can provide any number of health checks, either associated with a given service ("is the webserver returning 200 OK"), or with the local node ("is memory utilization below 90%"). This information can be used by an operator to monitor cluster health, and it is used by the service discovery components to route tra c away from unhealthy hosts. 5 / 26 Key/Value Store Applications can make use of Consul's hierarchical key/value store for any number of purposes, including dynamic con guration, feature agging, coordination, leader election, and more. The simple HTTP API makes it easy to use. Multi Datacenter Consul supports multiple datacenters out of the box. This means users of Consul do not have to worry about building additional layers of abstraction to grow to multiple regions. Ref: Introduction - Consul by HashiCorp
- 6. Architecture Consul is a distributed, highly available system. Every node that provides services to Consul runs a Consul agent. Running an agent is not required for discovering other services or getting/setting key/value data. The agent is responsible for health checking the services on the node as well as the node itself. 6 / 26 The agents talk to one or more Consul servers. The Consul servers are where data is stored and replicated. The servers themselves elect a leader. While Consul can function with one server, 3 to 5 is recommended to avoid failure scenarios leading to data loss. A cluster of Consul servers is recommended for each datacenter. Components of your infrastructure that need to discover other services or nodes can query any of the Consul servers or any of the Consul agents. The agents forward queries to the servers automatically. Each datacenter runs a cluster of Consul servers. When a cross- datacenter service discovery or con guration request is made, the local Consul servers forward the request to the remote datacenter and return the result. Ref: Introduction - Consul by HashiCorp
- 7. 7 / 26
- 8. RPI Swarm Cluster + Consul 8 / 26
- 9. Let's rebuild our previous container cluster with Consul.. Check it again if necessary: Docker Swarm Cluster 9 / 26
- 10. 10 / 26 A 3-Node RPI Cluster node1 192.168.1.102 node2 192.168.1.101 node3 192.168.1.100
- 12. #etc/default/docker DOCKER_OPTS="--storage-driver=overlay-D-Htcp://0.0.0.0:2375--cluster-st #ifnecessary $systemctlrestartdocker $dockerinfo $psaux|grepdocker 12 / 26 Engine Config DOCKER_OPTS
- 14. $exportDOCKER_HOST=tcp://192.168.1.102:10000 $dockerrun-d-p8080:80hypriot/rpi-nano-httpd 571d31928b3db90fc6baffa088c25c645f8d55d5e144dc03816ef5f6af62ae21 $dockerps CONTAINERID IMAGE COMMAND CRE 571d31928b3d hypriot/rpi-nano-httpd "/httpd80" 8 d897b5aeab29 hypriot/rpi-swarm:1.2.1 "/swarmmanage-H0.0" dc1bb0bd5188 hypriot/rpi-consul:0.6.4 "/consulagent-serve" 14 / 26 Check & Test
- 16. Consul UI 16 / 26
- 17. Consul UI 17 / 26
- 18. Consul UI 18 / 26
- 19. $dockerrun-d-p9000:9000hypriot/rpi-dockerui:v0.9.0-ehttp://192.168 a08588d3e7888952875e9f14496ccf5e943af954a8e70a4c51439025ff31a943 $dockerps CONTAINERID IMAGE COMMAND CRE a08588d3e788 hypriot/rpi-dockerui "/dockerui-ehttp://" 6 571d31928b3d hypriot/rpi-nano-httpd "/httpd80" Abo d897b5aeab29 hypriot/rpi-swarm:1.2.1 "/swarmmanage-H0.0" Abo dc1bb0bd5188 hypriot/rpi-consul:0.6.4 "/consulagent-serve" Abo 19 / 26 Now: UI for Docker Try DockerUI
- 20. DockerUI 20 / 26
- 21. DockerUI 21 / 26
- 22. DockerUI 22 / 26
- 23. DockerUI 23 / 26
- 24. Refs 24 / 26
- 25. Refs 1. Introduction - Consul by HashiCorp 2. Consul Architecture - Consul by HashiCorp 3. kevana/ui-for-docker: An uno cial web interface for Docker, formerly known as DockerUI 4. consul @ docker hub 5. progrium/consul @ docker hub 6. gliderlabs/consul @ docker hub | consul-agent | consul-server 25 / 26
- 26. END Eueung Mulyana http://eueung.github.io/docker-stuff/consul CodeLabs | Attribution-ShareAlike CC BY-SA 26 / 26