Blue-Green Deployment pamuhoro wepasi

Munyaya ino tinoshandisa Bash, ssh, docker ΠΈ nginx Isu ticharonga dhizaini isina musono yewebhu application. Blue-green deployment inzira inobvumidza iwe kuti ugadzirise ipapo ipapo application pasina kuramba chikumbiro chimwe chete. Ndiyo imwe yea zero downtime deployment strategy uye yakanyatsokodzera zvikumbiro nemuenzaniso mumwechete, asi kugona kurodha yechipiri, yakagadzirira-kumhanya muenzaniso padyo.

Ngatiti iwe une webhu application iyo vatengi vazhinji vari kushanda nayo, uye hapana zvachose nzira yekuti irare pasi kwemasekonzi akati wandei. Uye iwe unofanirwa chaizvo kuburitsa raibhurari yekuvandudza, kugadzirisa bug, kana chinhu chitsva chinotonhorera. Mune yakajairika mamiriro, iwe unozofanirwa kumisa application, woitsiva uye wotanga zvakare. Kana iri docker, unogona kutanga waitsiva, wobva watangazve, asi pachine nguva yekuti zvikumbiro zvechikumbiro hazvizogadziriswe, nekuti kazhinji application inotora nguva kuti itange kurodha. Zvakadini kana ikatanga, asi ichiita seisingashande? Iri ndiro dambudziko, ngatirigadzirise nemaitiro mashoma uye zvine hunyoro sezvinobvira.

ZVINOTAURWA: Zvizhinji zvechinyorwa zvinoratidzwa mune yekuyedza fomati - muchimiro chekurekodha chesesheni yekoni. Ndinovimba izvi hazvizove zvakanyanya kuoma kunzwisisa uye iyo kodhi ichazvinyora pachayo zvakakwana. Zvemamiriro ekunze, fungidzira kuti idzi hadzisi zvidimbu zvekodhi chete, asi bepa kubva kune "simbi" teletype.

Blue-Green Deployment pamuhoro wepasi

Nzira dzinonakidza dzakaoma kuGoogle nekungoverenga kodhi dzinotsanangurwa pakutanga kwechikamu chimwe nechimwe. Kana chimwe chinhu chisina kujeka, google icho uye chitarise. explainshell (nerombo rakanaka, inoshanda zvakare, nekuda kwekuvhurwa kweteregiramu). Kana iwe usingakwanise kuGoogle chero chinhu, bvunza mumashoko. Ndichafara kuwedzera kune chikamu chinoenderana "Maitiro anofadza".

Ngatitangei.

$ mkdir blue-green-deployment && cd $_

sevhisi

Ngatiite sevhisi yekuyedza toiisa mumudziyo.

Nzira dzinonakidza

  • cat << EOF > file-name (Here Document + I/O Redirection) inzira yekugadzira yakawanda-line faira ine murairo mumwe chete. Zvese bash zvinoverenga kubva /dev/stdin mushure memutsara uyu uye pamberi pemutsara EOF icharekodhwa mukati file-name.
  • wget -qO- URL (explainshell) - buritsa gwaro rakagamuchirwa kuburikidza neHTTP kuenda /dev/stdout (analogue curl URL).

Printout

Ini ndinotyora chaizvo snippet kuti ndigone kuvhenekera kwePython. Pakuguma pachava nechimwe chidimbu chakadai. Funga kuti munzvimbo idzi mapepa akachekwa kuti atumire kune dhipatimendi rekujekesa (apo iyo kodhi yaive neruoko-ruvara nehighlighters), uye ipapo zvidimbu izvi zvakanamirwa kumashure.

$ cat << EOF > uptimer.py
from http.server import BaseHTTPRequestHandler, HTTPServer
from time import monotonic

app_version = 1
app_name = f'Uptimer v{app_version}.0'
loading_seconds = 15 - app_version * 5

class Handler(BaseHTTPRequestHandler):
    def do_GET(self):
        if self.path == '/':
            try:
                t = monotonic() - server_start
                if t < loading_seconds:
                    self.send_error(503)
                else:
                    self.send_response(200)
                    self.send_header('Content-Type', 'text/html')
                    self.end_headers()
                    response = f'<h2>{app_name} is running for {t:3.1f} seconds.</h2>n'
                    self.wfile.write(response.encode('utf-8'))
            except Exception:
                self.send_error(500)
        else:
            self.send_error(404)

httpd = HTTPServer(('', 8080), Handler)
server_start = monotonic()
print(f'{app_name} (loads in {loading_seconds} sec.) started.')
httpd.serve_forever()
EOF

$ cat << EOF > Dockerfile
FROM python:alpine
EXPOSE 8080
COPY uptimer.py app.py
CMD [ "python", "-u", "./app.py" ]
EOF

$ docker build --tag uptimer .
Sending build context to Docker daemon  39.42kB
Step 1/4 : FROM python:alpine
 ---> 8ecf5a48c789
Step 2/4 : EXPOSE 8080
 ---> Using cache
 ---> cf92d174c9d3
Step 3/4 : COPY uptimer.py app.py
 ---> a7fbb33d6b7e
Step 4/4 : CMD [ "python", "-u", "./app.py" ]
 ---> Running in 1906b4bd9fdf
Removing intermediate container 1906b4bd9fdf
 ---> c1655b996fe8
Successfully built c1655b996fe8
Successfully tagged uptimer:latest

$ docker run --rm --detach --name uptimer --publish 8080:8080 uptimer
8f88c944b8bf78974a5727070a94c76aa0b9bb2b3ecf6324b784e782614b2fbf

$ docker ps
CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS              PORTS                    NAMES
8f88c944b8bf        uptimer             "python -u ./app.py"   3 seconds ago       Up 5 seconds        0.0.0.0:8080->8080/tcp   uptimer

$ docker logs uptimer
Uptimer v1.0 (loads in 10 sec.) started.

$ wget -qSO- http://localhost:8080
  HTTP/1.0 503 Service Unavailable
  Server: BaseHTTP/0.6 Python/3.8.3
  Date: Sat, 22 Aug 2020 19:52:40 GMT
  Connection: close
  Content-Type: text/html;charset=utf-8
  Content-Length: 484

$ wget -qSO- http://localhost:8080
  HTTP/1.0 200 OK
  Server: BaseHTTP/0.6 Python/3.8.3
  Date: Sat, 22 Aug 2020 19:52:45 GMT
  Content-Type: text/html
<h2>Uptimer v1.0 is running for 15.4 seconds.</h2>

$ docker rm --force uptimer
uptimer

Reverse proxy

Kuti application yedu ikwanise kuchinja zvisingaonekwe, zvinotoda kuti pamberi payo pave nechimwe chinhu chinovanza kutsiviwa kwayo. Inogona kunge iri web server nginx Π² reverse proxy mode. Reverse proxy inotangwa pakati pemutengi uye application. Iyo inogamuchira zvikumbiro kubva kune vatengi uye inoendesa kune iyo application uye inoendesa mberi mhinduro dzechikumbiro kune vatengi.

Iyo yekushandisa uye reverse proxy inogona kubatanidzwa mukati me docker uchishandisa docker network. Nekudaro, mudziyo une application hautombodi kuendesa chiteshi pane iyo host system; izvi zvinobvumira iyo application kuti ive yakasarudzika kure nekutyisidzira kwekunze.

Kana iyo reverse proxy ichigara pane imwe host, iwe uchafanirwa kusiya docker network uye ubatanidze application kune reverse proxy kuburikidza netiweki yevaenzi, uchiendesa chiteshi. Apps parameter --publish, sepamavambo ekutanga uye sezvakaita nereverse proxy.

Isu tichamhanyisa reverse proxy pachiteshi 80, nekuti ichi ndicho chaicho chimiro chinofanirwa kuteerera kune yekunze network. Kana port 80 yakabatikana pane yako test host, shandura parameter --publish 80:80 pamusoro --publish ANY_FREE_PORT:80.

Nzira dzinonakidza

Printout

$ docker network create web-gateway
5dba128fb3b255b02ac012ded1906b7b4970b728fb7db3dbbeccc9a77a5dd7bd

$ docker run --detach --rm --name uptimer --network web-gateway uptimer
a1105f1b583dead9415e99864718cc807cc1db1c763870f40ea38bc026e2d67f

$ docker run --rm --network web-gateway alpine wget -qO- http://uptimer:8080
<h2>Uptimer v1.0 is running for 11.5 seconds.</h2>

$ docker run --detach --publish 80:80 --network web-gateway --name reverse-proxy nginx:alpine
80695a822c19051260c66bf60605dcb4ea66802c754037704968bc42527bf120

$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED              STATUS              PORTS                NAMES
80695a822c19        nginx:alpine        "/docker-entrypoint.…"   27 seconds ago       Up 25 seconds       0.0.0.0:80->80/tcp   reverse-proxy
a1105f1b583d        uptimer             "python -u ./app.py"     About a minute ago   Up About a minute   8080/tcp             uptimer

$ cat << EOF > uptimer.conf
server {
    listen 80;
    location / {
        proxy_pass http://uptimer:8080;
    }
}
EOF

$ docker cp ./uptimer.conf reverse-proxy:/etc/nginx/conf.d/default.conf

$ docker exec reverse-proxy nginx -s reload
2020/06/23 20:51:03 [notice] 31#31: signal process started

$ wget -qSO- http://localhost
  HTTP/1.1 200 OK
  Server: nginx/1.19.0
  Date: Sat, 22 Aug 2020 19:56:24 GMT
  Content-Type: text/html
  Transfer-Encoding: chunked
  Connection: keep-alive
<h2>Uptimer v1.0 is running for 104.1 seconds.</h2>

Seamless deployment

Ngatiburitsei vhezheni nyowani yechishandiso (ine mbiri-yakapetwa yekutanga kuita inosimudzira) uye edza kuiendesa zvisina musono.

Nzira dzinonakidza

  • echo 'my text' | docker exec -i my-container sh -c 'cat > /my-file.txt' - Nyora zvinyorwa my text kufaira /my-file.txt mukati memudziyo my-container.
  • cat > /my-file.txt - Nyora zviri mukati meyakajairwa yekuisa kufaira /dev/stdin.

Printout

$ sed -i "s/app_version = 1/app_version = 2/" uptimer.py

$ docker build --tag uptimer .
Sending build context to Docker daemon  39.94kB
Step 1/4 : FROM python:alpine
 ---> 8ecf5a48c789
Step 2/4 : EXPOSE 8080
 ---> Using cache
 ---> cf92d174c9d3
Step 3/4 : COPY uptimer.py app.py
 ---> 3eca6a51cb2d
Step 4/4 : CMD [ "python", "-u", "./app.py" ]
 ---> Running in 8f13c6d3d9e7
Removing intermediate container 8f13c6d3d9e7
 ---> 1d56897841ec
Successfully built 1d56897841ec
Successfully tagged uptimer:latest

$ docker run --detach --rm --name uptimer_BLUE --network web-gateway uptimer
96932d4ca97a25b1b42d1b5f0ede993b43f95fac3c064262c5c527e16c119e02

$ docker logs uptimer_BLUE
Uptimer v2.0 (loads in 5 sec.) started.

$ docker run --rm --network web-gateway alpine wget -qO- http://uptimer_BLUE:8080
<h2>Uptimer v2.0 is running for 23.9 seconds.</h2>

$ sed s/uptimer/uptimer_BLUE/ uptimer.conf | docker exec --interactive reverse-proxy sh -c 'cat > /etc/nginx/conf.d/default.conf'

$ docker exec reverse-proxy cat /etc/nginx/conf.d/default.conf
server {
    listen 80;
    location / {
        proxy_pass http://uptimer_BLUE:8080;
    }
}

$ docker exec reverse-proxy nginx -s reload
2020/06/25 21:22:23 [notice] 68#68: signal process started

$ wget -qO- http://localhost
<h2>Uptimer v2.0 is running for 63.4 seconds.</h2>

$ docker rm -f uptimer
uptimer

$ wget -qO- http://localhost
<h2>Uptimer v2.0 is running for 84.8 seconds.</h2>

$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED              STATUS              PORTS                NAMES
96932d4ca97a        uptimer             "python -u ./app.py"     About a minute ago   Up About a minute   8080/tcp             uptimer_BLUE
80695a822c19        nginx:alpine        "/docker-entrypoint.…"   8 minutes ago        Up 8 minutes        0.0.0.0:80->80/tcp   reverse-proxy

Panguva ino, mufananidzo wacho unovakwa zvakananga pane sevha, izvo zvinoda kuti zviwanikwa zvekushandisa zvivepo, uye zvakare inotakura sevha nebasa risingakoshi. Nhanho inotevera ndeyekugovera gungano remufananidzo kumuchina wakasiyana (semuenzaniso, kune CI system) wozoiendesa kune server.

Kutamisa mifananidzo

Nehurombo, hazvina musoro kuendesa mifananidzo kubva kune localhost kuenda kune localhost, saka chikamu ichi chinogona kuongororwa chete kana uine maviri anotambira ane Docker padyo. At least zvinoita sezvizvi:

$ ssh production-server docker image ls
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE

$ docker image save uptimer | ssh production-server 'docker image load'
Loaded image: uptimer:latest

$ ssh production-server docker image ls
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
uptimer             latest              1d56897841ec        5 minutes ago       78.9MB

chikwata docker save inochengetedza data yemufananidzo mu.tar archive, zvichireva kuti inorema zvakapetwa ka1.5 pane yayaizoyera muchimiro chakamisikidzwa. Saka ngatizvizunze muzita rekuchengetedza nguva uye traffic:

$ docker image save uptimer | gzip | ssh production-server 'zcat | docker image load'
Loaded image: uptimer:latest

Iwe unogona zvakare kutarisa maitiro ekurodha (kunyangwe izvi zvichida yechitatu-bato utility):

$ docker image save uptimer | gzip | pv | ssh production-server 'zcat | docker image load'
25,7MiB 0:01:01 [ 425KiB/s] [                   <=>    ]
Loaded image: uptimer:latest

Zano: Kana iwe uchida boka rema paramita kuti ubatanidze kune sevha kuburikidza neSSH, unogona kunge usiri kushandisa iyo faira. ~/.ssh/config.

Kutamisa mufananidzo kuburikidza docker image save/load - Iyi ndiyo yakanyanya minimalistic nzira, asi kwete yega. Pane zvimwe:

  1. Container Registry (indasitiri chiyero).
  2. Batanidza kune docker daemon server kubva kune imwe host:
    1. environment variable DOCKER_HOST.
    2. Command line sarudzo -H kana --host chiridzwa docker-compose.
    3. docker context

Nzira yechipiri (ine zvingasarudzwa zvitatu zvekushandiswa kwayo) inotsanangurwa zvakanaka munyaya yacho Maitiro ekuisa pane ari kure Docker mauto ane docker-compose.

deploy.sh

Zvino ngatiunganidze zvese zvatakaita nemaoko mune imwe script. Ngatitange nebasa repamusoro-soro, uye totarisa mamwe anoshandiswa mairi.

Nzira dzinonakidza

  • ${parameter?err_msg} - imwe ye bash mashiripiti zviperengo (aka parameter kutsiva) Kana parameter zvisina kutaurwa, zvabuda err_msg uye kubuda nekodhi 1.
  • docker --log-driver journald - nekusarudzika, mutyairi wekutema docker ifaira remavara pasina kutenderera. Neiyi nzira, matanda anokurumidza kuzadza dhisiki yese, saka kune nzvimbo yekugadzira inofanirwa kushandura mutyairi kune akangwara.

Deployment script

deploy() {
    local usage_msg="Usage: ${FUNCNAME[0]} image_name"
    local image_name=${1?$usage_msg}

    ensure-reverse-proxy || return 2
    if get-active-slot $image_name
    then
        local OLD=${image_name}_BLUE
        local new_slot=GREEN
    else
        local OLD=${image_name}_GREEN
        local new_slot=BLUE
    fi
    local NEW=${image_name}_${new_slot}
    echo "Deploying '$NEW' in place of '$OLD'..."
    docker run 
        --detach 
        --restart always 
        --log-driver journald 
        --name $NEW 
        --network web-gateway 
        $image_name || return 3
    echo "Container started. Checking health..."
    for i in {1..20}
    do
        sleep 1
        if get-service-status $image_name $new_slot
        then
            echo "New '$NEW' service seems OK. Switching heads..."
            sleep 2  # Ensure service is ready
            set-active-slot $image_name $new_slot || return 4
            echo "'$NEW' service is live!"
            sleep 2  # Ensure all requests were processed
            echo "Killing '$OLD'..."
            docker rm -f $OLD
            docker image prune -f
            echo "Deployment successful!"
            return 0
        fi
        echo "New '$NEW' service is not ready yet. Waiting ($i)..."
    done
    echo "New '$NEW' service did not raise, killing it. Failed to deploy T_T"
    docker rm -f $NEW
    return 5
}

Zvishandiso zvakashandiswa:

  • ensure-reverse-proxy -Iva nechokwadi chekuti reverse proxy iri kushanda (inobatsira pakutumira kwekutanga)
  • get-active-slot service_name - Inoona kuti ndeipi slot iri kushanda kune yakapihwa sevhisi (BLUE kana GREEN)
  • get-service-status service_name deployment_slot -Inoona kana sevhisi yakagadzirira kugadzirisa zvikumbiro zvinouya
  • set-active-slot service_name deployment_slot - Inochinja iyo nginx config mune reverse proxy mudziyo

Mukuronga:

ensure-reverse-proxy() {
    is-container-up reverse-proxy && return 0
    echo "Deploying reverse-proxy..."
    docker network create web-gateway
    docker run 
        --detach 
        --restart always 
        --log-driver journald 
        --name reverse-proxy 
        --network web-gateway 
        --publish 80:80 
        nginx:alpine || return 1
    docker exec --interactive reverse-proxy sh -c "> /etc/nginx/conf.d/default.conf"
    docker exec reverse-proxy nginx -s reload
}

is-container-up() {
    local container=${1?"Usage: ${FUNCNAME[0]} container_name"}

    [ -n "$(docker ps -f name=${container} -q)" ]
    return $?
}

get-active-slot() {
    local service=${1?"Usage: ${FUNCNAME[0]} service_name"}

    if is-container-up ${service}_BLUE && is-container-up ${service}_GREEN; then
        echo "Collision detected! Stopping ${service}_GREEN..."
        docker rm -f ${service}_GREEN
        return 0  # BLUE
    fi
    if is-container-up ${service}_BLUE && ! is-container-up ${service}_GREEN; then
        return 0  # BLUE
    fi
    if ! is-container-up ${service}_BLUE; then
        return 1  # GREEN
    fi
}

get-service-status() {
    local usage_msg="Usage: ${FUNCNAME[0]} service_name deployment_slot"
    local service=${1?usage_msg}
    local slot=${2?$usage_msg}

    case $service in
        # Add specific healthcheck paths for your services here
        *) local health_check_port_path=":8080/" ;;
    esac
    local health_check_address="http://${service}_${slot}${health_check_port_path}"
    echo "Requesting '$health_check_address' within the 'web-gateway' docker network:"
    docker run --rm --network web-gateway alpine 
        wget --timeout=1 --quiet --server-response $health_check_address
    return $?
}

set-active-slot() {
    local usage_msg="Usage: ${FUNCNAME[0]} service_name deployment_slot"
    local service=${1?$usage_msg}
    local slot=${2?$usage_msg}
    [ "$slot" == BLUE ] || [ "$slot" == GREEN ] || return 1

    get-nginx-config $service $slot | docker exec --interactive reverse-proxy sh -c "cat > /etc/nginx/conf.d/$service.conf"
    docker exec reverse-proxy nginx -t || return 2
    docker exec reverse-proxy nginx -s reload
}

shanda get-active-slot inoda tsananguro shoma:

Sei ichidzosa nhamba uye isingabudisi tambo?

Zvakadaro, mune yekufona basa tinotarisa mhedzisiro yebasa rayo, uye kutarisa yekubuda kodhi uchishandisa bash iri nyore pane kutarisa tambo. Mukuwedzera, kuwana tambo kubva mairi iri nyore kwazvo:
get-active-slot service && echo BLUE || echo GREEN.

Mamiriro matatu akakwana here kusiyanisa nyika dzese?

Blue-Green Deployment pamuhoro wepasi

Kunyange maviri achakwana, wekupedzisira ari pano kungoperera, kuti usanyora else.

Chete basa rinodzosa nginx configs rinoramba risina kutsanangurwa: get-nginx-config service_name deployment_slot. Nekufananidza nehutano hwehutano, pano unogona kuseta chero config kune chero sevhisi. Pakati pezvinhu zvinonakidza - chete cat <<- EOF, iyo inokutendera kuti ubvise ma tabo ese pakutanga. Ichokwadi, mutengo wekugadzirisa zvakanaka unosanganiswa ma tabo ane nzvimbo, iyo nhasi inoonekwa seyakaipa kwazvo fomu. Asi bash mauto ma tabo, uye zvingave zvakare zvakanaka kuve neyakajairika fomati mu nginx config. Muchidimbu, kusanganisa ma tabo nenzvimbo pano zvinonyatsoita senge mhinduro yakanaka kubva mukuipa. Nekudaro, iwe hauzoone izvi mune snippet pazasi, sezvo Habr "anozviita nemazvo" nekuchinja ese ma tabo kune 4 nzvimbo uye kuita EOF kusashanda. Uye pano zvinoonekwa.

Kuti usasimuka kaviri, ini ndichakuudza ipapo ipapo cat << 'EOF', izvo zvichasangana gare gare. Kana ukanyora zviri nyore cat << EOF, ipapo mukati meheredoc tambo inopindirwa (misiyano inowedzerwa ($foo), kuraira kufona ($(bar)) nezvimwewo), uye kana ukavharira magumo egwaro mune imwe makotesheni, ipapo kududzira kunovharwa uye chiratidzo $ inoratidzwa sezvairi. Zvaunoda kuisa script mukati meimwe script.

get-nginx-config() {
    local usage_msg="Usage: ${FUNCNAME[0]} service_name deployment_slot"
    local service=${1?$usage_msg}
    local slot=${2?$usage_msg}
    [ "$slot" == BLUE ] || [ "$slot" == GREEN ] || return 1

    local container_name=${service}_${slot}
    case $service in
        # Add specific nginx configs for your services here
        *) nginx-config-simple-service $container_name:8080 ;;
    esac
}

nginx-config-simple-service() {
    local usage_msg="Usage: ${FUNCNAME[0]} proxy_pass"
    local proxy_pass=${1?$usage_msg}

cat << EOF
server {
    listen 80;
    location / {
        proxy_pass http://$proxy_pass;
    }
}
EOF
}

Iyi ndiyo script yese. Uye saka gist neichi script yekurodha kuburikidza ne wget kana curl.

Kuita zvinyorwa zveparameterized pane server iri kure

Yasvika nguva yekugogodza pane yakananga server. Nguva ino localhost zvakakodzera chaizvo:

$ ssh-copy-id localhost
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
himura@localhost's password: 

Number of key(s) added: 1

Now try logging into the machine, with:   "ssh 'localhost'"
and check to make sure that only the key(s) you wanted were added.

Isu takanyora deployment script iyo inodhawunirodha chifananidzo chakafanovakwa kune yakanangwa server uye isina musono kutsiva sevhisi mudziyo, asi isu tingaite sei pamushini uri kure? Iyo script ine nharo, sezvo iri yepasirese uye inogona kuendesa masevhisi akati wandei kamwechete pasi peimwe reverse proxy (unogona kushandisa nginx configs kuona kuti ndeipi url ichava sevhisi). Iyo script haigoni kuchengetwa pavhavha, sezvo munyaya iyi isu hatizokwanisi kuigadzirisa pakarepo (nechinangwa chekugadzirisa bug uye kuwedzera mabasa matsva), uye kazhinji, nyika = yakaipa.

Solution 1: Zvichakadaro chengetedza iyo script pane server, asi ikope nguva dzese kuburikidza scp. Zvadaro batanidza kuburikidza ssh uye ita script nenharo dzinodiwa.

Cons:

  • Zviito zviviri pane chimwe
  • Panogona kunge pasina nzvimbo yaunokopa, kana kuti panogona kunge isingakwanisi kuwana, kana script inogona kuitwa panguva yekutsiva.
  • Zvinokurudzirwa kuti uzvichenese (bvisa script).
  • Atova zviito zvitatu.

Solution 2:

  • Chengetedza tsananguro dzebasa chete mune script uye usashandise chero chinhu
  • Nekubatsirwa kwe sed wedzera basa rekufona kusvika kumagumo
  • Tumira zvese zvakananga ku shh kuburikidza nepombi (|)

Pros:

  • Chokwadi asina state
  • Hapana boilerplate masangano
  • Kunzwa kutonhorera

Ngatingozviita pasina Ansible. Hongu, zvinhu zvose zvakatogadzirwa. Hongu, bhasikoro. Tarisa kuti bhasikoro riri nyore sei, rakanaka uye minimalistic:

$ cat << 'EOF' > deploy.sh
#!/bin/bash

usage_msg="Usage: $0 ssh_address local_image_tag"
ssh_address=${1?$usage_msg}
image_name=${2?$usage_msg}

echo "Connecting to '$ssh_address' via ssh to seamlessly deploy '$image_name'..."
( sed "$a deploy $image_name" | ssh -T $ssh_address ) << 'END_OF_SCRIPT'
deploy() {
    echo "Yay! The '${FUNCNAME[0]}' function is executing on '$(hostname)' with argument '$1'"
}
END_OF_SCRIPT
EOF

$ chmod +x deploy.sh

$ ./deploy.sh localhost magic-porridge-pot
Connecting to localhost...
Yay! The 'deploy' function is executing on 'hut' with argument 'magic-porridge-pot'

Nekudaro, isu hatigone kuve nechokwadi chekuti arikure host ane bash yakakwana, saka isu tichawedzera cheki diki pakutanga (ichi panzvimbo ye shellbang):

if [ "$SHELL" != "/bin/bash" ]
then
    echo "The '$SHELL' shell is not supported by 'deploy.sh'. Set a '/bin/bash' shell for '$USER@$HOSTNAME'."
    exit 1
fi

Uye zvino ndezvechokwadi:

$ docker exec reverse-proxy rm /etc/nginx/conf.d/default.conf

$ wget -qO deploy.sh https://git.io/JUURc

$ chmod +x deploy.sh

$ ./deploy.sh localhost uptimer
Sending gzipped image 'uptimer' to 'localhost' via ssh...
Loaded image: uptimer:latest
Connecting to 'localhost' via ssh to seamlessly deploy 'uptimer'...
Deploying 'uptimer_GREEN' in place of 'uptimer_BLUE'...
06f5bc70e9c4f930e7b1f826ae2ca2f536023cc01e82c2b97b2c84d68048b18a
Container started. Checking health...
Requesting 'http://uptimer_GREEN:8080/' within the 'web-gateway' docker network:
  HTTP/1.0 503 Service Unavailable
wget: server returned error: HTTP/1.0 503 Service Unavailable
New 'uptimer_GREEN' service is not ready yet. Waiting (1)...
Requesting 'http://uptimer_GREEN:8080/' within the 'web-gateway' docker network:
  HTTP/1.0 503 Service Unavailable
wget: server returned error: HTTP/1.0 503 Service Unavailable
New 'uptimer_GREEN' service is not ready yet. Waiting (2)...
Requesting 'http://uptimer_GREEN:8080/' within the 'web-gateway' docker network:
  HTTP/1.0 200 OK
  Server: BaseHTTP/0.6 Python/3.8.3
  Date: Sat, 22 Aug 2020 20:15:50 GMT
  Content-Type: text/html

New 'uptimer_GREEN' service seems OK. Switching heads...
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
2020/08/22 20:15:54 [notice] 97#97: signal process started
The 'uptimer_GREEN' service is live!
Killing 'uptimer_BLUE'...
uptimer_BLUE
Total reclaimed space: 0B
Deployment successful!

Zvino unogona kuvhura http://localhost/ mubrowser, mhanyisa kutumirwa zvakare uye ita shuwa kuti inomhanya isina mutsetse nekuvandudza peji zvinoenderana neCD panguva yekurongeka.

Usakanganwa kuchenesa wapedza basa :3

$ docker rm -f uptimer_GREEN reverse-proxy 
uptimer_GREEN
reverse-proxy

$ docker network rm web-gateway 
web-gateway

$ cd ..

$ rm -r blue-green-deployment

Source: www.habr.com