public class RedisKey {
    /**
     * 正则表达式.
     */
    public static final String REGEX = "\\{[a-zA-Z0-9]*\\}";
    /**
     * 全局独自执行任务.
     */
    public static final String EXEC_LOCK = "exec:lock";
    /**
     * 和锁配合使用,每个客户端一个标志.
     */
    private static final String OWNER_ID = UUID.randomUUID().toString();
    /**
     * 获取执行指定任务权限key.
     *
     * @return
     */
    public static String getExecLock(Object... objs) {
        return replaceKey(EXEC_LOCK, objs);
    }
    private static String replaceKey(String key, Object... objs) {
        for (Object obj : objs) {
            key = key.replaceFirst(REGEX, String.valueOf(obj));
        }
        return key;
    }
    public static String getOwnerId() {
        return OWNER_ID;
    }
}

@Slf4j
public class RedisService {  
    /**
     * Only set the key if it does not already exist.
     */
    private static final String SET_IF_NOT_EXIST = "NX";
    /**
     * Set the specified expire time, in milliseconds.
     */
    private static final String SET_WITH_EXPIRE_MILL_TIME = "PX";
    /**
     * Set the specified expire time, in seconds.
     */
    private static final String SET_WITH_EXPIRE_SECOND_TIME = "EX";
    private static final String LOCK_SUCCESS = "OK";
    private static final Long RELEASE_SUCCESS = 1L;
    
    /**
     * 设置分布式锁.(过期时间毫秒)
     * @param lockKey    锁的名称.
     * @param requestId  持锁人ID.
     * @param expireTime 锁的超时时间.
     * @return 是否获取锁.
     */
    public synchronized boolean tryGetDistributeLock(String lockKey, String requestId, int expireTime) {
        log.debug("lock key: {}, ownerId: {}, expire time: {}", lockKey, requestId, expireTime);
        String result = jedis.set(lockKey, requestId, SET_IF_NOT_EXIST, SET_WITH_EXPIRE_MILL_TIME, expireTime);
        if (LOCK_SUCCESS.equals(result)) {
            return true;
        }
        return false;
    }

    /**
     * 释放分布式锁.
     *
     * @param lockKey   锁
     * @param requestId 请求标识
     * @return 是否释放成功.
     */
    public synchronized boolean releaseDistributedLock(String lockKey, String requestId) {
        log.debug("release lock key: {}, ownerId: {}, expire time: {}", lockKey, requestId);
        String script = "if redis.call('get', KEYS[1]) == ARGV[1] then return redis.call('del', KEYS[1]) else return 0 end";
        Object result = jedis.eval(script, Collections.singletonList(lockKey), Collections.singletonList(requestId));
        if (RELEASE_SUCCESS.equals(result)) {
            return true;
        }
        return false;
    }
}

# 生成一个RSA私钥,1024是加密强度，一般是1024或2048 
$ openssl genrsa -out private.key 2048
 
# 生成一个证书请求
$ openssl req -new -key private.key -out cert_req.csr

# 自己签发证书，如果要权威CA签发的话，要把cert_req.csr发给CA
$ openssl x509 -req -days 3650 -in cert_req.csr -signkey private.key -out server_cert.crt
只需要两处填写就行,其他都不填.
...
Common Name (eg, fully qualified host name) []:这里填域名
...
A challenge password []:密码

$ ./gencrt.sh 
输入域名和密码即可,这里输入域名gitlab.example.com,则生成以下4个文件
gitlab.example.com.crt：自签名的证书
gitlab.example.com.csr：证书的请求
gitlab.example.com.key：不带口令的Key
gitlab.example.com.origin.key：带口令的Key
只要使用.crt和com.key即可.

# 启动nginx
$ docker run --name mynginx -p 8080:80 -d nginx
# 拷贝nginx的配置文件到本地,并重命名文件夹为conf
$ docker cp mynginx:/etc/nginx /opt/nginx
$ mv /opt/nginx/nginx /opt/nginx/conf/certs下
# 删除容器
$ docker rm -f mynginx
# 拷贝密钥到/opt/nginx/conf/certs下
$ cp gitlab.example.com.crt gitlab.example.com.key /opt/nginx/conf/certs
# 设置证书.在配置文件最后添加内容.
$ vim /opt/nginx/conf/conf.d/default.conf
server {
    listen 443 ssl;
    server_name  localhost;

    ssl                      on;
    ssl_certificate          /etc/nginx/certs/gitlab.example.com.crt;
    ssl_certificate_key      /etc/nginx/certs/gitlab.example.com.key;

    ssl_session_timeout  5m;

    ssl_ciphers HIGH:!aNULL:!MD5;
    ssl_protocols SSLv3 TLSv1 TLSv1.1 TLSv1.2;
    ssl_prefer_server_ciphers   on;

    location / {
        root   /usr/share/nginx/html;
        index  index.html index.htm;
    }
}
# 启动
$ docker run --name mynginx -v /opt/nginx/conf:/etc/nginx -p 8080:80 -p 8081:443 -d nginx
# 浏览器验证即可.

$ vim gencrt.sh
#!/bin/sh
# create self-signed server certificate:
read -p "Enter your domain [www.example.com]: " DOMAIN

echo "Create server key..."

openssl genrsa -des3 -out $DOMAIN.key 2048

echo "Create server certificate signing request..."

SUBJECT="/C=US/ST=Mars/L=iTranswarp/O=iTranswarp/OU=iTranswarp/CN=$DOMAIN"

openssl req -new -subj $SUBJECT -key $DOMAIN.key -out $DOMAIN.csr

echo "Remove password..."

mv $DOMAIN.key $DOMAIN.origin.key
openssl rsa -in $DOMAIN.origin.key -out $DOMAIN.key

echo "Sign SSL certificate..."

openssl x509 -req -days 3650 -in $DOMAIN.csr -signkey $DOMAIN.key -out $DOMAIN.crt

echo "TODO:"
echo "Copy $DOMAIN.crt to /etc/nginx/ssl/$DOMAIN.crt"
echo "Copy $DOMAIN.key to /etc/nginx/ssl/$DOMAIN.key"
echo "Add configuration in nginx:"
echo "server {"
echo "    ..."
echo "    listen 443 ssl;"
echo "    ssl_certificate     /etc/nginx/ssl/$DOMAIN.crt;"
echo "    ssl_certificate_key /etc/nginx/ssl/$DOMAIN.key;"
echo "}"

$ docker run -ti --name [容器名] -d [镜像名] /bin/bash

FROM centos:7
RUN yum install -y squid
# ip高匿与端口
RUN echo 'request_header_access Via deny all' >> /etc/squid/squid.conf \
 && echo 'request_header_access X-Forwarded-For deny all' >> /etc/squid/squid.conf \
 && echo 'request_header_access From deny all' >> /etc/squid/squid.conf \
 && sed -i 's/http_access deny all/http_access allow all/g' /etc/squid/squid.conf \
 && sed -i 's/http_port 3128/http_port 57112/g' /etc/squid/squid.conf
ENTRYPOINT /usr/sbin/squid start && /bin/bash # 这个是重点
EXPOSE 57112

FROM centos:7
RUN yum install -y squid python-setuptools
RUN easy_install supervisor
COPY supervisord.conf /etc/supervisor/conf.d/supervisord.conf
# ip高匿与端口
RUN echo 'request_header_access Via deny all' >> /etc/squid/squid.conf \
 && echo 'request_header_access X-Forwarded-For deny all' >> /etc/squid/squid.conf \
 && echo 'request_header_access From deny all' >> /etc/squid/squid.conf \
 && sed -i 's/http_access deny all/http_access allow all/g' /etc/squid/squid.conf \
 && sed -i 's/http_port 3128/http_port 57112/g' /etc/squid/squid.conf
EXPOSE 57112

[supervisord]
nodaemon=true
[program:squid]
command=/usr/sbin/squid start

# 本地运行Docker官方文档网站
$ docker run -d -p 80:4000 docs/docker.github.io

# 卸载旧版本
$ yum remove docker \
                  docker-ce \
                  docker-client \
                  docker-client-latest \
                  docker-common \
                  docker-latest \
                  docker-latest-logrotate \
                  docker-logrotate \
                  docker-selinux \
                  docker-engine-selinux \
                  docker-engine
# 为了防止之前已经安装的遗留问题,删除镜像储存目录
$ rm -rf /var/lib/docker
# 安装依赖工具
$ yum install -y yum-utils \
  device-mapper-persistent-data \
  lvm2
# 安装docker官方仓库(失败 使用阿里云仓库)
$ yum-config-manager \
    --add-repo \
    https://download.docker.com/linux/centos/docker-ce.repo
# 如果上面执行后如下报错,添加阿里云的源即可.
Loaded plugins: fastestmirror
adding repo from: https://download.docker.com/linux/centos/docker-ce.repo
grabbing file https://download.docker.com/linux/centos/docker-ce.repo to /etc/yum.repos.d/docker-ce.repo
Could not fetch/save url https://download.docker.com/linux/centos/docker-ce.repo to file /etc/yum.repos.d/docker-ce.repo: [Errno 12] Timeout on https://download.docker.com/linux/centos/docker-ce.repo: (28, 'Resolving timed out after 30455 milliseconds')
$ yum-config-manager --add-repo http://mirrors.aliyun.com/docker-ce/linux/centos/docker-ce.repo
# 安装docker
$ yum install -y docker-ce
# 启动
$ systemctl enable docker && systemctl start docker

$ vim /etc/docker/daemon.json
{
  "registry-mirrors": ["https://registry.docker-cn.com"]
}

$ docker pull jenkins/jenkins:lts

$ docker build -f jenkins-data-dockerfile -t jenkins-data .
$ docker build -f jenkins-master-dockerfile -t jenins-master .
# 从节点宿主机上执行
$ docker build -f jenkins-slave-dockerfile -t jenins-slave .

# 创建用户持久化jenkins数据文件的目录及日志目录.
$ mkdir -p {/data/jenkins,/data/logs/jenkins}
# 容器内启动jenkins服务使用的是jenkins用户,所以必须修改目录用户拥有者为
$ chown 1000:1000 {/data/jenkins,/data/logs/jenkins}
# 启动数据卷jenkins-datas
$ docker run --name jenkins-data \
-v /data/jenkins:/var/jenkins_home \
-v /data/logs/jenkins:/var/log/jenkins \
jenkins-data
# 启动jenkins-master.(构建dockerfile见附录.)
$ docker run -d \
-p 19875:8080 \
-p 50000:50000 \
--volumes-from jenkins-data \
--name jenkins-master \
jenkins-master

$ docker run -ti -d \
-p 19222:22 \
--restart on-failure \
--network host \ 
--name jenkins-slave \
jenkins-slave

$ vim jenkins-data-dockerfile
FROM debian:jessie
# Create the jenkins user
RUN useradd -d "/var/jenkins_home" -u 1000 -m -s /bin/bash jenkins
# Create the folders and volume mount points
RUN mkdir -p /var/log/jenkins
RUN chown -R jenkins:jenkins /var/log/jenkins
VOLUME ["/var/log/jenkins", "/var/jenkins_home"]
USER jenkins
CMD ["echo", "Data container for Jenkins"]

$ vim jenkins-master-dockerfile
FROM jenkins/jenkins:lts
# 增加swarm:3.13插件.https://plugins.jenkins.io/swarm
USER root
RUN /usr/local/bin/install-plugins.sh docker_swarm Ansible Multijob Pipeline
USER jenkins

FROM centos:centos7
# 创建用户及修改密码
RUN groupadd -g 1000 jenkins_slave
RUN useradd -d /home/jenkins_home -s /bin/bash \
-m jenkins_slave -u 1000 -g jenkins_slave
RUN echo 'ys123456' | passwd --stdin root
RUN echo 'jpass' | passwd --stdin jenkins_slave
# 安装依赖包
RUN yum install -y passwd openssl openssh-server wget git vim java-1.8.0-openjdk java-1.8.0-openjdk-devel ansible
# 设置maven,安装路径保持和jenkins-master中的一致.
RUN rm -rf /opt/apache-maven* && \
wget -O /opt/apache-maven-3.5.4.tar.gz http://mirrors.shu.edu.cn/apache/maven/maven-3/3.5.4/binaries/apache-maven-3.5.4-bin.tar.gz && \
tar -xvf /opt/apache-maven-3.5.4.tar.gz -C /opt/ && \
mv /opt/apache-maven-3.5.4 /opt/maven && \
rm -rf /opt/apache-maven-3.5.4 && \
rm -rf /opt/apache-maven-3.5.4.tar.gz && \
echo "export MAVEN_HOME=/opt/maven" >> /etc/profile && \
echo 'PATH=$PATH:$MAVEN_HOME/bin' >> /etc/profile && \
source /etc/profile
# 设置jdk,安装路径保持和jenkins-master中的一致.
RUN mkdir -p /usr/local/java && \
wget --no-cookies \
--no-check-certificate \
--header "Cookie: oraclelicense=accept-securebackup-cookie" \
http://download.oracle.com/otn-pub/java/jdk/8u171-b11/512cd62ec5174c3487ac17c61aaa89e8/jdk-8u171-linux-x64.tar.gz \
-O /usr/local/java/jdk1.8.tar.gz
RUN tar -xvf /usr/local/java/jdk1.8.tar.gz -C /usr/local/java && mv /usr/local/java/jdk1.8.0_171 /usr/local/java/jdk1.8 && echo 'export JAVA_HOME=/usr/local/java/jdk1.8' >> /etc/profile && echo 'PATH=$PATH:$JAVA_HOME/bin' && source /etc/profile
# 设置jenkins_home目录,保持和jenkins-master一致.(根据需要自己修改路径)
RUN mkdir -p /root/.jenkins && echo 'export JENKINS_HOME=/root/.jenkins/' >> /etc/profile && source /etc/profile
# 生成密钥
RUN ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key -N ''
RUN ssh-keygen -q -t ecdsa -f /etc/ssh/ssh_host_ecdsa_key -N ''
RUN sed -i 's|session required pam_loginuid.so|session optional pam_loginuid.so|g' /etc/pam.d/sshd
RUN mkdir -p /root/.ssh && chown root.root /root && chmod 700 /root/.ssh

# 下载脚本.这里是因为脚本构建用到了许多脚本.
RUN git clone https://github.com/steven-ji/proxy-scripts.git /opt/scripts
RUN chown -R 1000:1000 /opt/scripts

#设置时区
RUN /bin/cp /usr/share/zoneinfo/Asia/Shanghai /etc/localtime && echo 'Asia/Shanghai' >/etc/timezone

EXPOSE 22

CMD ip addr ls eth0 | awk '{print $2}' | egrep -o '([0-9]+\.){3}[0-9]+';/usr/sbin/sshd -D

$ docker run -d \
  --hostname 192.168.1.222 \
  --publish 443:443 --publish 80:80 --publish 22:22 \
  --name gitlab \
  --restart always \
  --volume /data/gitlab/config:/etc/gitlab \
  --volume /data/gitlab/logs:/var/log/gitlab \
  --volume /data/gitlab/data:/var/opt/gitlab \
  --network host \
  gitlab/gitlab-ce:latest
# 443 https访问端口,80 http访问端口, 22 docker容器端口.
# /data/gitlab/config配置文件目录
# /data/gitlab/logs日志存储目录
# /data/gitlab/data应用数据存储目录

$ cp -rf gitlab-11-3-stable-zh/* /opt/gitlab/embedded/service/gitlab-rails/
$ gitlab-ctl reconfigure
$ gitlab-ctl restart

$ docker run -d \
  --hostname 192.168.1.222 \
  --publish 443:443 --publish 80:80 --publish 22:22 \
  --name gitlab \
  --restart always \
  --volume /data/gitlab/config:/etc/gitlab \
  --volume /data/gitlab/logs:/var/log/gitlab \
  --volume /data/gitlab/data:/var/opt/gitlab \
  --volume /data/gitlab/data/zh/gitlab:/opt/gitlab/embedded/service/gitlab-rails \
  --network host \
  gitlab/gitlab-ce:11.3.5-ce.0

$ git clone https://github.com/steven-ji/gitlab-ce-zh.git

$ vim version.sh
export VERSIONS=(
    10.7.7
    10.8.7
    11.0.5
    11.1.4
    11.3.5
)

$ ./build generate 11.3

$ docker pull jilingjun1014/gitlab-zh:v11.3.5
$ docker run -d \
  --publish 443:443 --publish 80:80 --publish 22:22 \
  --name gitlab \
  --restart always \
  --volume /data/gitlab/config:/etc/gitlab \
  --volume /data/gitlab/logs:/var/log/gitlab \
  --volume /data/gitlab/data:/var/opt/gitlab \
  --network host \
  jilingjun1014/gitlab-zh:v11.3.5

$ touch /data/gitlab/config/gitlab.rb

gitlab_rails['gitlab_email_from'] = "username@company.com"
gitlab_rails['smtp_enable'] = true
gitlab_rails['smtp_address'] = "smtp.mxhichina.com"
gitlab_rails['smtp_port'] = 465
gitlab_rails['smtp_user_name'] = "username@company.com"
gitlab_rails['smtp_password'] = "password"
gitlab_rails['smtp_domain'] = "mxhichina.com"
gitlab_rails['smtp_authentication'] = "login"
gitlab_rails['smtp_enable_starttls_auto'] = true
gitlab_rails['smtp_tls'] = true

# ssh到Gitlab的docker容器中.
$ docker exec -ti gitlab /bin/bash
$ gitlab-rails console
$ Notify.test_email('destination_email@address.com', 'Message Subject', 'Message Body').deliver_now

# 配置文件中添加如下,则访问GitLab的路径就是:http://gitlab.example.com
external_url "http://gitlab.example.com"
external_url "https://gitlab.example.com"
# 重新加载配置
$ gitlab-ctl reconfigure

external_url "http://gitlab.example.com:9080"
external_url "https://gitlab.example.com:9443"

# set access url
external_url "http://gitlab.example.com"
external_url "https://gitlab.example.com"
# compatable http
nginx['redirect_http_to_https'] = true
# set certs
nginx['ssl_certificate'] = "/etc/gitlab/ssl/gitlab.example.com.crt"
nginx['ssl_certificate_key'] = "/etc/gitlab/ssl/gitlab.example.com.key"
# set errer page info
nginx['custom_error_pages'] = {
  '404' => {
    'title' => 'Example title',
    'header' => 'Example header',
    'message' => 'Example message'
  }
}

# 关闭内置nginx
nginx['enable'] = false
# 配置访问用户.Debian/Ubuntu the default user is www-data for both Apache/Nginx whereas for RHEL/CentOS the Nginx user is nginx.
web_server['external_users'] = ['www-data','nginx']
# 配置nginx服务器ip白名单
gitlab_rails['trusted_proxies'] = ['192.168.1.0/24', '192.168.2.1', '2001:0db8::/32' ]
# Define the external url
external_url 'http://git.example.com'
# Disable the built-in nginx
nginx['enable'] = false
# Disable the built-in unicorn
unicorn['enable'] = false
# Set the internal API URL
gitlab_rails['internal_api_url'] = 'http://git.example.com'
# Define the web server process user (ubuntu/nginx)
web_server['external_users'] = ['www-data']

# default修改存储目录,alternative增加一个存储目录
git_data_dirs({
  "default" => { "path" => "/var/opt/gitlab/git-data" },
  "alternative" => { "path" => "/mnt/nas/git-data" }
})

$ gitlab-ctl reconfigure
$ gitlab-ctl restart

$ vim /Users/jilingjun/Applications/data/gitlab/config/gitlab.rb
# set access url
external_url "http://gitlab.example.com"
external_url "https://gitlab.example.com"
# set ssh port
gitlab_rails['gitlab_shell_ssh_port'] = 9022
# compatable http
nginx['redirect_http_to_https'] = true
# set certs
nginx['ssl_certificate'] = "/etc/gitlab/ssl/gitlab.example.com.crt"
nginx['ssl_certificate_key'] = "/etc/gitlab/ssl/gitlab.example.com.key"
# set errer page info
nginx['custom_error_pages'] = {
  '404' => {
    'title' => 'Example title',
    'header' => 'Example header',
    'message' => 'Example message'
  }
}
# set email config.Here use aliyun enterprise mail.
gitlab_rails['gitlab_email_from'] = "username@company.com"
gitlab_rails['smtp_enable'] = true
gitlab_rails['smtp_address'] = "smtp.mxhichina.com"
gitlab_rails['smtp_port'] = 465
gitlab_rails['smtp_user_name'] = "username@company.com"
gitlab_rails['smtp_password'] = "password"
gitlab_rails['smtp_domain'] = "mxhichina.com"
gitlab_rails['smtp_authentication'] = "login"
gitlab_rails['smtp_enable_starttls_auto'] = true
gitlab_rails['smtp_tls'] = true

$ docker run -d \
  --hostname 192.168.1.222 \
  --publish 443:443 --publish 80:80 --publish 22:22 \
  --name gitlab \
  --restart always \
  --volume /data/gitlab/config:/etc/gitlab \
  --volume /data/gitlab/logs:/var/log/gitlab \
  --volume /data/gitlab/data:/var/opt/gitlab \
  --network host \
  jilingjun1014/gitlab-zh:v11.3.5
  
# See gitlab container logs
$ docker logs -f gitlab

# Update Permission
$ docker exec gitlab update-permissions
$ docker restart gitlab

# See gitlab container logs
$ docker logs -f gitlab

$ show variables like 'binlog_format';
+-----------------------------------------+--------------------------------+
| Variable_name                           | Value                          |
+-----------------------------------------+--------------------------------+
| binlog_format                           | ROW                            |

./gh-ost \
--aliyun-rds=true \
--allow-on-master \
--host= --port= --database= --table= --conf=/opt/account.cnf \
--alter="ADD COLUMN platform int(2) DEFAULT NULL COMMENT '所属平台'" \
--chunk-size=5000 \
--concurrent-rowcount \
--cut-over=atomic \
--cut-over-lock-timeout-seconds=3 \
--initially-drop-ghost-table=true \
--initially-drop-old-table=true \
--initially-drop-socket-file=true \
--timestamp-old-table=true \
--verbose \
--serve-socket-file=/tmp/gh-ost.test.sock \
--switch-to-rbr \
--execute

# --conf设置登录mysql的用户名和密码文件的绝对路径.内容格式如下.
[client]
user=gh-ost
password=123456
# --aliyun-rds=true针对使用阿里云的RDS.
# --allow-on-master没有从节点时,直接连接主mysql时指定.
# --alter表结构操作,如我这里添加字段"ADD COLOUM platform int(2) DEFAULT NULL COMMENT '所属平台'"
# --chunk-size每次复制数据的数量,默认是1000,允许100~100,000之间.
# --concurrent-rowcount一边复制数据一边计算数据量
# --cut-over数据复制的最后一步,安全的对原表和新表进行切换.默认是atomic,而two-step则不安全.
# --cut-over-lock-timeout-seconds执行cut-over时间.默认3秒,可以不用配置.
# --cut-over-exponential-backoff执行cut-over失败后执行指数级等待.
# --exponential-backoff-max-interval执行指数级等待的最大时间间隔.默认是64.如:
# --exact-rowcount真实计算数据总量,执行count()操作.个人觉得没必要,比较耗时.
# --initially-drop-ghost-table(建议使用)清除以前操作遗留下的ghost表
# --initially-drop-old-table(建议使用)清除以前操作遗留下的旧表
# --initially-drop-socket-file(建议使用)清除以前遗留的socket文件
# --timestamp-old-table旧表加上时间戳
# --verbose日志界别debug
# --serve-socket-file=/tmp/gh-ost.test.sock 
# --panic-flag-file=/tmp/gh-ost.panic.flag(暂时不清楚,先不使用)
# --switch-to-rbr(建议添加)这样不用关注mysql的bin log的格式.让gh-ost去执行设置bin-log格式操作.

-aliyun-rds
  	set to 'true' when you execute on Aliyun RDS.
-allow-master-master
  	explicitly allow running in a master-master setup
-allow-nullable-unique-key
  	allow gh-ost to migrate based on a unique key with nullable columns. As long as no NULL values exist, this should be OK. If NULL values exist in chosen key, data may be corrupted. Use at your own risk!
-allow-on-master
  	allow this migration to run directly on master. Preferably it would run on a replica
-alter string
  	alter statement (mandatory)
-approve-renamed-columns ALTER
  	in case your ALTER statement renames columns, gh-ost will note that and offer its interpretation of the rename. By default gh-ost does not proceed to execute. This flag approves that gh-ost's interpretation is correct
-ask-pass
  	prompt for MySQL password
-assume-master-host string
  	(optional) explicitly tell gh-ost the identity of the master. Format: some.host.com[:port] This is useful in master-master setups where you wish to pick an explicit master, or in a tungsten-replicator where gh-ost is unable to determine the master
-assume-rbr
  	set to 'true' when you know for certain your server uses 'ROW' binlog_format. gh-ost is unable to tell, event after reading binlog_format, whether the replication process does indeed use 'ROW', and restarts replication to be certain RBR setting is applied. Such operation requires SUPER privileges which you might not have. Setting this flag avoids restarting replication and you can proceed to use gh-ost without SUPER privileges
-check-flag
  	Check if another flag exists/supported. This allows for cross-version scripting. Exits with 0 when all additional provided flags exist, nonzero otherwise. You must provide (dummy) values for flags that require a value. Example: gh-ost --check-flag --cut-over-lock-timeout-seconds --nice-ratio 0
-chunk-size int
  	amount of rows to handle in each iteration (allowed range: 100-100,000) (default 1000)
-concurrent-rowcount
  	(with --exact-rowcount), when true (default): count rows after row-copy begins, concurrently, and adjust row estimate later on; when false: first count rows, then start row copy (default true)
-conf string
  	Config file
-critical-load string
  	Comma delimited status-name=threshold, same format as --max-load. When status exceeds threshold, app panics and quits
-critical-load-hibernate-seconds int
  	When nonzero, critical-load does not panic and bail out; instead, gh-ost goes into hibernate for the specified duration. It will not read/write anything to from/to any server
-critical-load-interval-millis int
  	When 0, migration immediately bails out upon meeting critical-load. When non-zero, a second check is done after given interval, and migration only bails out if 2nd check still meets critical load
-cut-over string
  	choose cut-over type (default|atomic, two-step) (default "atomic")
-cut-over-exponential-backoff
  	Wait exponentially longer intervals between failed cut-over attempts. Wait intervals obey a maximum configurable with 'exponential-backoff-max-interval').
-cut-over-lock-timeout-seconds int
  	Max number of seconds to hold locks on tables while attempting to cut-over (retry attempted when lock exceeds timeout) (default 3)
-database string
  	database name (mandatory)
-debug
  	debug mode (very verbose)
-default-retries int
  	Default number of retries for various operations before panicking (default 60)
-discard-foreign-keys
  	DANGER! This flag will migrate a table that has foreign keys and will NOT create foreign keys on the ghost table, thus your altered table will have NO foreign keys. This is useful for intentional dropping of foreign keys
-dml-batch-size int
  	batch size for DML events to apply in a single transaction (range 1-100) (default 10)
-exact-rowcount
  	actually count table rows as opposed to estimate them (results in more accurate progress estimation)
-execute
  	actually execute the alter & migrate the table. Default is noop: do some tests and exit
-exponential-backoff-max-interval int
  	Maximum number of seconds to wait between attempts when performing various operations with exponential backoff. (default 64)
-force-named-cut-over
  	When true, the 'unpostpone|cut-over' interactive command must name the migrated table
-force-table-names string
  	table name prefix to be used on the temporary tables
-heartbeat-interval-millis int
  	how frequently would gh-ost inject a heartbeat value (default 100)
-help
  	Display usage
-hooks-hint string
  	arbitrary message to be injected to hooks via GH_OST_HOOKS_HINT, for your convenience
-hooks-path string
  	directory where hook files are found (default: empty, ie. hooks disabled). Hook files found on this path, and conforming to hook naming conventions will be executed
-host string
  	MySQL hostname (preferably a replica, not the master) (default "127.0.0.1")
-initially-drop-ghost-table
  	Drop a possibly existing Ghost table (remains from a previous run?) before beginning operation. Default is to panic and abort if such table exists
-initially-drop-old-table
  	Drop a possibly existing OLD table (remains from a previous run?) before beginning operation. Default is to panic and abort if such table exists
-initially-drop-socket-file
  	Should gh-ost forcibly delete an existing socket file. Be careful: this might drop the socket file of a running migration!
-master-password string
  	MySQL password on master, if different from that on replica. Requires --assume-master-host
-master-user string
  	MySQL user on master, if different from that on replica. Requires --assume-master-host
-max-lag-millis int
  	replication lag at which to throttle operation (default 1500)
-max-load string
  	Comma delimited status-name=threshold. e.g: 'Threads_running=100,Threads_connected=500'. When status exceeds threshold, app throttles writes
-migrate-on-replica
  	Have the migration run on a replica, not on the master. This will do the full migration on the replica including cut-over (as opposed to --test-on-replica)
-nice-ratio float
  	force being 'nice', imply sleep time per chunk time; range: [0.0..100.0]. Example values: 0 is aggressive. 1: for every 1ms spent copying rows, sleep additional 1ms (effectively doubling runtime); 0.7: for every 10ms spend in a rowcopy chunk, spend 7ms sleeping immediately after
-ok-to-drop-table
  	Shall the tool drop the old table at end of operation. DROPping tables can be a long locking operation, which is why I'm not doing it by default. I'm an online tool, yes?
-panic-flag-file string
  	when this file is created, gh-ost will immediately terminate, without cleanup
-password string
  	MySQL password
-port int
  	MySQL port (preferably a replica, not the master) (default 3306)
-postpone-cut-over-flag-file string
  	while this file exists, migration will postpone the final stage of swapping tables, and will keep on syncing the ghost table. Cut-over/swapping would be ready to perform the moment the file is deleted.
-quiet
  	quiet
-replica-server-id uint
  	server id used by gh-ost process. Default: 99999 (default 99999)
-replication-lag-query string
  	Deprecated. gh-ost uses an internal, subsecond resolution query
-serve-socket-file string
  	Unix socket file to serve on. Default: auto-determined and advertised upon startup
-serve-tcp-port int
  	TCP port to serve on. Default: disabled
-skip-foreign-key-checks
  	set to 'true' when you know for certain there are no foreign keys on your table, and wish to skip the time it takes for gh-ost to verify that
-skip-renamed-columns ALTER
  	in case your ALTER statement renames columns, gh-ost will note that and offer its interpretation of the rename. By default gh-ost does not proceed to execute. This flag tells gh-ost to skip the renamed columns, i.e. to treat what gh-ost thinks are renamed columns as unrelated columns. NOTE: you may lose column data
-stack
  	add stack trace upon error
-switch-to-rbr
  	let this tool automatically switch binary log format to 'ROW' on the replica, if needed. The format will NOT be switched back. I'm too scared to do that, and wish to protect you if you happen to execute another migration while this one is running
-table string
  	table name (mandatory)
-test-on-replica
  	Have the migration run on a replica, not on the master. At the end of migration replication is stopped, and tables are swapped and immediately swap-revert. Replication remains stopped and you can compare the two tables for building trust
-test-on-replica-skip-replica-stop
  	When --test-on-replica is enabled, do not issue commands stop replication (requires --test-on-replica)
-throttle-additional-flag-file string
  	operation pauses when this file exists; hint: keep default, use for throttling multiple gh-ost operations (default "/tmp/gh-ost.throttle")
-throttle-control-replicas string
  	List of replicas on which to check for lag; comma delimited. Example: myhost1.com:3306,myhost2.com,myhost3.com:3307
-throttle-flag-file string
  	operation pauses when this file exists; hint: use a file that is specific to the table being altered
-throttle-http string
  	when given, gh-ost checks given URL via HEAD request; any response code other than 200 (OK) causes throttling; make sure it has low latency response
-throttle-query string
  	when given, issued (every second) to check if operation should throttle. Expecting to return zero for no-throttle, >0 for throttle. Query is issued on the migrated server. Make sure this query is lightweight
-timestamp-old-table
  	Use a timestamp in old table name. This makes old table names unique and non conflicting cross migrations
-tungsten
  	explicitly let gh-ost know that you are running on a tungsten-replication based topology (you are likely to also provide --assume-master-host)
-user string
  	MySQL user
-verbose
  	verbose
-version
  	Print version & exit

# 查询版本
$ pip show docker-py
$ pip show docker
# 卸载,同理pip、pip2、pip3
$ pip uninstall docker
$ pip uninstall docker-py
$ pip uninstall docker-compose
# 安装(--ignore-installed)
$ pip install 'docker-compose>=1.7.0'
$ pip install 'docker-py>=1.7.0'