Shulou(Shulou.com)06/01 Report--

Editor to share with you how to deploy Docker container consul, I believe that most people do not know much about it, so share this article for your reference, I hope you can learn a lot after reading this article, let's learn about it!

Introduction to Consul

Consul is a service software that supports multi-data center distributed and highly available service discovery and configuration sharing. It is developed by HashiCorp in Go language and is open source based on Mozilla Public License 2.0 protocol. Consul supports health check and allows HTTP, GRPC, and DNS protocols to call API to store key-value pairs.

The virtual machine management software vgrant, which is super easy to use on the command line, is also a product developed by HashiCorp.

The consistency protocol uses Raft algorithm to ensure the high availability of services. Use GOSSIP protocol to manage members and broadcast messages, and support ACL access control.

Consul usage scenario

Registration and configuration sharing of Docker instances

Registration and configuration sharing of Coreos instances

Configuration sharing, service discovery and health check for SaaS applications.

Vitess cluster

Integrate with confd services to dynamically generate nginx and haproxy configuration files

-consul deployment-

Server: 192.168.37.100 Docker-ce, Consul, Consul-template

Server: 192.168.37.107 Docker-ce, registrator

Template template (update profile)

Registrator (auto-discovery + registration to the consul-server side)

Every time the backend updates a container, it registers with registrator to control the consul to complete the update operation, and consul triggers the consultemplate template for hot update (reload).

Core mechanism: consul: automatic discovery, automatic update, provide services for containers (add, delete, life cycle)-- consul server

Create a consul directory

[root@localhost ~] # hostnamectl set-hostname consul [root@localhost ~] # su [root@consul ~] # mkdir / root/consul

Compress the consul package and put it under / use/bin

[root@consul ~] # cd consul/ [root@consul ~ / consul] # lsconsul_0.9.2_linux_ amd64.zip [root @ consul ~ / consul] # unzip consul_0.9.2_linux_amd64.zipArchive: consul_0.9.2_linux_amd64.zip inflating: consul [root@consul ~ / consul] # lsconsul consul_0.9.2_linux_ amd64.zip [root @ consul ~ / consul] # mv consul/ usr/bin/

Configure the mode of consul

Onsul agent\

-server\ server mode

-bootstrap front-end framework

-ui\ accessible web interface

-data-dir=/var/lib/consul-data\

-bind=192.168.37.100\

-client=0.0.0.0\ registrator (Application Server-docker-tomcat/apache)

-node=consul-server01 & > / var/ log / consul.log &

[root@consul ~ / consul] # consul agent\ >-server\ >-bootstrap\ >-ui\ >-data-dir=/var/lib/consul-data\ >-bind=192.168.37.100\ >-client=0.0.0.0\ >-node=consul-server01 & > / var/log/consul.log & [1] 24144 [root@consul ~ / consul] # consul membersNode Address Status Type Build Protocol DCconsul-server01 192.168.37.100ve8301 alive Server 0.9.2 2 dc1

At this point, we look at the cluster information.

[root@consul ~ / consul] # consul membersNode Address Status Type Build Protocol DCconsul-server01 192.168.37.100 alive server 8301 0.9.2 2 dc1

View details and filter out leader

[root@consul ~ / consul] # consul info | grep leader leader = true leader_addr = 192.168.37.100v8300

View the consul interface. Use port 8500, 8300 is a communication port

The container service automatically joins the consul cluster to install Gliderlabs/Registrator Gliderlabs/Registrator

You can check the running status of the container to register automatically, and you can also register the service information of the docker container to the service configuration center (consul 8300-"8500 display). Consul, Etcd, and skyDNS2 are currently supported.

Do the following at 192.168.37.107

[root@server] # docker run-d\ >-- name=registrator\ >-- net=host\ >-v / var/run/docker.sock:/tmp/docker.sock\ >-- restart=always\ > gliderlabs/registrator:latest\ >-ip=192.168.37.107\ > consul://192.168.37.100:8500 # below is loading Unable to find image 'gliderlabs/registrator:latest' locallylatest: Pulling from gliderlabs/registratorImage docker.io/gliderlabs/registrator:latest uses outdated schema1 manifest format. Please upgrade to a sc hema2 image for better future compatibility. More information at https://docs.docker.com/registry/spec/depr ecated-schema-v1/c87f684ee1c2: Pull completea0559c0b3676: Pull completea28552c49839: Pull completeDigest: sha256:6e708681dd52e28f4f39d048ac75376c9a762c44b3d75b2824173f8364e52c10Status: Downloaded newer image for gliderlabs/registrator:latest2536df1b1fbb77dcbf5d2e09295f222496ecc63f00a49020ce6976decd52a439

View the container

[root@server] # docker ps-aCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES2536df1b1fbb gliderlabs/registrator:latest "/ bin/registrator-I …" 51 seconds ago Up 50 seconds registrator Test Service Discovery function is normal

Install two nginx and two apache

Docker run-itd-p itd 83test01 nginxdocker run 80-- name test-01-h test01 nginxdocker run-itd-p Vera 84RV 80-- name test-02-h testo2 nginxdocker run-itd-p RV 88ler80-- name test-03-h test03 httpddocker run-itd-p RV 8980-- name test-04-h test04 httpd

Go to the web page to check at this time.

Install consul-template

Consul-Template is a daemon that queries consul cluster information in real time and updates any number of specified templates on the file system to generate configuration files. After the update is complete, you can choose to run the shell command to perform the update operation and reload the Nginx. Consul-Template can query the service catalog, Key, Key-values and so on in consul.

This powerful abstraction and query language templates make Consul-Template particularly suitable for dynamically creating configuration files. For example: create Apache/Nginx (nginx upstream) Proxy Balancers, Haproxy Backends

Prepare the template nginx template file

-operate on consul-

[root@consul ~ / consul] # vim nginx.ctmp1upstream http_backend {{range service "nginx"}} server {{.Port}; {{end} server {listen 83; server_name localhost 192.168.37.100; access_log / var/log/nginx/xiao.cn-access.log; index index.html index.php; location / {proxy_set_header HOST $host Proxy_set_header x-Real-IP $remote_addr; proxy_set_header client-IP $remote_addr; proxy_set_header x-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://http_backend; } install nginx#### required package [root@server] # yum install gcc pcre-devel zlib-devel-yearly packages # decompress nginx package [root@server] # tar zxf nginx-1.12.0.tar.gz### execute [root@server / opt/nginx-1.12.0] #. / configure-- prefix=/usr/local/nginx## compile [root@server / opt/nginx-1.12.0] # make & & make install

Modify the configuration file to identify the file at the end of the .conf file

Create a vhost directory

[root@server / usr/local/nginx/conf] # mkdir vhost

Create a nginx log directory

[root@server / usr/local/nginx/conf/vhost] # mkdir / var/log/nginx.log

Start nginx

[root@server / usr/local/sbin] # ln-s / usr/local/nginx/sbin/nginx / usr/local/sbin/ [root@server / usr/local/sbin] # nginx

Check to see if it starts

[root@server / usr/local/sbin] # netstat-natp | grep nginxtcp 0 0 0.0. 0. 0. 0. 0. 0. 0. 0. 0. 0 of the consul-template * LISTEN 54739/nginx: master configuration and launch template[ root @ consul ~ / consul] # unzip consul-template_0.19.3_linux_amd64.zipArchive: consul-template_0.19.3_linux_amd64.zip inflating: consul-template [root@consul ~ / consul] # lsconsul_0.9.2_linux_amd64.zip consul-template consul-template_0.19.3_linux_amd64.zip nginx.ctmp1 [root@consul ~ / consul] # mv consul-template / usr/bin

# # Operation of Associated Sub-configuration Files in nginx Virtual Directory

[root@consul ~ / consul] # consul-template-consul-addr 192.168.37.100 consul-template 8500\ >-template "/ root/consul/nginx.ctmp1:/usr/local/nginx/conf/vhost/xiao.conf:/usr/local/nginx/sbin/nginx-s reload"\ >-- log-level=info

View build profile

It's all accessible.

These are all the contents of the article "how Docker containers deploy consul". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.