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

This article mainly introduces how to use Nginx to achieve grayscale release, the article is very detailed, has a certain reference value, interested friends must read it!

Grayscale publishing refers to a release way that can make a smooth transition between black and white. AB test is a grayscale publishing method that allows some users to continue to use An and some users to start using B. if users have no objection to B, then gradually expand the scope and migrate all users to B.

The grayscale release can ensure the stability of the whole system, and the problem can be found and adjusted at the initial gray level to ensure its influence.

There are three common ways to publish grayscale:

Nginx+LUA mode

Realize grayscale publishing according to Cookie

Realize grayscale publishing according to source IP

This article will mainly explain how to achieve simple grayscale publishing based on Cookie and source IP. Nginx+LUA involves too much content and will not be carried out in this article.

Amob B test process

Nginx implements grayscale publishing according to Cookie

Query the value of the cookie key as version according to Cookie, and forward it to hilinux_01 if the cookie value is V1 and to hilinux_02 if V2. If the Cookie values do not match, the default is to go to the server corresponding to hilinux_01.

The two servers are defined as:

Hilinux_01 192.168.1.100:8080

Hilinux_02 192.168.1.200:8080

Using if instruction to implement

Upstream hilinux_01 {server 192.168.1.100 listen 8080 max_fails=1 fail_timeout=60;} upstream hilinux_02 {server 192.168.1.200 max_fails=1 fail_timeout=60; 8080 max_fails=1 fail_timeout=60;} upstream default {server 192.168.1.100 max_fails=1 fail_timeout=60; 8080 max_fails=1 fail_timeout=60;} server {listen 80; server_name www.hi-linux.com; access_log logs/www.hi-linux.com.log main; # match cookie set $group "default" If ($http_cookie * "version=V1") {set $group hilinux_01;} if ($http_cookie ~ * "version=V2") {set $group hilinux_02;} location / {proxy_pass http://$group; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; index index.html index.htm;}}

Using map instruction to implement

Configure a mapping in Nginx, and $COOKIE_version can parse the version field in Cookie. $group is a variable, and {} contains mapping rules.

If a user whose version is V1 comes to access, $group equals hilinux_01. If you use it in server, you will proxy it to http://hilinux_01. If the version is a V2 user, $group equals hilinux_02. If you use it in server, you will proxy it to http://hilinux_02. If the Cookie values do not match, the default is to go to the server corresponding to hilinux_01.

Upstream hilinux_01 {server 192.168.1.100 COOKIE_version 8080 max_fails=1 fail_timeout=60;} upstream hilinux_02 {server 192.168.1.200 max_fails=1 fail_timeout=60; 8080 max_fails=1 fail_timeout=60;} upstream default {server 192.168.1.100 upstream hilinux_01 8080 max_fails=1 fail_timeout=60;} map $COOKIE_version $group {~ * V1 $hilinux_01;~*V2 $hilinux_02;default default;} server {listen 80; server_name www.hi-linux.com; access_log logs/www.hi-linux.com.log main Location / {proxy_pass http://$group; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; index index.html index.htm;}}

Nginx publishes grayscale according to source IP.

If it is an internal IP, reverse proxy to hilinux_02 (pre-release environment); if not, reverse proxy to hilinux_01 (production environment).

Upstream hilinux_01 {server 192.168.1.100 upstream hilinux_02 8080 max_fails=1 fail_timeout=60;} upstream hilinux_02 {server 192.168.1.200 max_fails=1 fail_timeout=60; 8080 max_fails=1 fail_timeout=60;} upstream default {server 192.168.1.100 max_fails=1 fail_timeout=60;} server {listen 80; server_name www.hi-linux.com; access_log logs/www.hi-linux.com.log main; set $group default; if ($remote_addr ~ "211.118.119.11") {set $group hilinux_02 } location / {proxy_pass http://$group; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; index index.html index.htm;}}

If you only have a single server, you can set up different website root directories according to different IP to achieve the same goal.

Server {listen 80; server_name www.hi-linux.com; access_log logs/www.hi-linux.com.log main; set $rootdir "/ var/www/html"; if ($remote_addr ~ "211.118.119.11") {set $rootdir "/ var/www/test";} location / {root $rootdir;}} these are all the contents of the article "how to use Nginx to achieve grayscale publishing". Thank you for reading! Hope to share the content to help you, more related 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.