🥇Panyebaran Biru-Ijo kanthi upah minimum

Ing artikel iki kita nggunakake bash, SSH, docker и nginx Kita bakal ngatur tata letak aplikasi web sing mulus. Penyebaran biru-ijo minangka teknik sing ngidini sampeyan nganyari aplikasi kanthi cepet tanpa nolak panjaluk siji. Iku salah siji saka strategi panyebaran downtime nul lan paling cocog kanggo aplikasi karo siji conto, nanging kemampuan kanggo mbukak liyane, contone siap mbukak ing cedhak.

Contone, sampeyan duwe aplikasi web sing akeh klien aktif digunakake, lan pancen ora ana cara kanggo ngapusi sajrone sawetara detik. Lan sampeyan pancene kudu nggulung nganyari perpustakaan, ndandani bug, utawa fitur keren anyar. Ing kahanan normal, sampeyan kudu mungkasi aplikasi, ngganti lan miwiti maneh. Ing kasus docker, sampeyan bisa ngganti dhisik, banjur miwiti maneh, nanging isih ana wektu nalika panjaluk aplikasi kasebut ora bakal diproses, amarga biasane aplikasi butuh sawetara wektu kanggo mbukak. Apa yen diwiwiti, nanging ora bisa digunakake? Iki minangka masalah, ayo dirampungake kanthi cara minimal lan kanthi elegan.

DISCLAIMER: Umume artikel ditampilake ing format eksperimen - ing bentuk rekaman sesi konsol. Muga-muga iki ora angel banget dingerteni lan kode kasebut bakal didokumentasikake kanthi cekap. Kanggo atmosfer, bayangake manawa iki ora mung potongan kode, nanging kertas saka teletype "wesi".

Teknik menarik sing angel kanggo Google mung kanthi maca kode kasebut diterangake ing wiwitan saben bagean. Yen ana sing ora jelas, google lan priksa. nerangakeshell (Untung, bisa digunakake maneh, amarga telegram mbukak blokir). Yen sampeyan ora bisa Google, takon ing komentar. Aku bakal seneng nambah menyang bagean sing cocog "Teknik menarik".

Ayo miwiti.

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

layanan

Ayo nggawe layanan eksperimen lan sijine ing wadhah.

Techniques menarik

cat << EOF > file-name (Kene Dokumen + Pangalihan I/O) minangka cara kanggo nggawe file multi-line kanthi siji printah. Kabeh bash maca saka /dev/stdin sawise baris iki lan sadurunge baris EOF bakal direkam ing file-name.
wget -qO- URL (nerangakeshell) - output dokumen ditampa liwat HTTP kanggo /dev/stdout (analog curl URL).

Cetakan

Aku khusus break snippet kanggo mbisakake nyorot kanggo Python. Ing pungkasan bakal ana potongan liyane kaya iki. Coba manawa ing papan kasebut kertas dipotong kanggo dikirim menyang departemen sing nyorot (ing endi kode kasebut diwarnai nganggo highlighter), banjur potongan kasebut ditempelake maneh.

$ 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

Proksi mbalikke

Supaya aplikasi kita bisa ngganti tanpa disadari, perlu ana entitas liyane ing ngarepe sing bakal ndhelikake panggantos kasebut. Bisa dadi server web nginx в mode proxy mbalikke. A proxy mbalikke ditetepake antarane klien lan aplikasi. Iku nampa panjalukan saka klien lan nerusake menyang aplikasi lan nerusake respon aplikasi kanggo klien.

Aplikasi lan proxy mbalikke bisa disambungake ing docker nggunakake jaringan docker. Mangkono, wadhah karo aplikasi malah ora perlu nerusake port ing sistem host; iki ngidini aplikasi bisa diisolasi kanthi maksimal saka ancaman eksternal.

Yen proxy mbalikke urip ing host liyane, sampeyan kudu ninggalake jaringan docker lan nyambungake aplikasi menyang proxy mbalikke liwat jaringan host, nerusake port app paramèter --publish, kaya ing wiwitan pisanan lan kaya proxy mbalikke.

Kita bakal mbukak proxy mbalikke ing port 80, amarga iki persis entitas sing kudu ngrungokake jaringan eksternal. Yen port 80 sibuk ing host test, ganti parameter kasebut --publish 80:80 ing --publish ANY_FREE_PORT:80.

Techniques menarik

"Ing jaringan Docker sing digawe pangguna, sampeyan bisa komunikasi karo kontaner ora mung nganggo alamat IP. Jeneng wadah uga ditanggulangi dadi alamat IP" (artikel "Jaringan nganggo wadhah mandiri", bagean "Gunakake jaringan jembatan sing ditemtokake pangguna", titik 5 saka kode docker).

Cetakan

$ 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>

Penyebaran mulus

Ayo dadi muter versi anyar saka aplikasi (kanthi ngedongkrak kinerja wiwitan kaping pindho) lan nyoba kanggo masang iku seamlessly.

Techniques menarik

echo 'my text' | docker exec -i my-container sh -c 'cat > /my-file.txt' - Tulis teks my text kanggo file /my-file.txt ing njero wadhah my-container.
cat > /my-file.txt - Tulis isi input standar menyang file /dev/stdin.

Cetakan

$ 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

Ing tahap iki, gambar dibangun langsung ing server, sing mbutuhake sumber aplikasi ana, lan uga ngemot server kanthi karya sing ora perlu. Langkah sabanjure yaiku nyedhiakke perakitan gambar menyang mesin sing kapisah (contone, menyang sistem CI) banjur transfer menyang server.

Ngirim gambar

Sayange, ora ana gunane nransfer gambar saka localhost menyang localhost, mula bagean iki mung bisa ditliti yen sampeyan duwe loro host karo Docker ing tangan. Minimal katon kaya iki:

$ 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

tim docker save nyimpen data gambar ing arsip .tar, tegese bobote kira-kira 1.5 kaping luwih saka bobot ing wangun teken. Dadi ayo goyangake kanthi jeneng ngirit wektu lan lalu lintas:

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

Sampeyan uga bisa ngawasi proses download (sanajan mbutuhake sarana pihak katelu):

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

Tip: Yen sampeyan butuh akeh parameter kanggo nyambung menyang server liwat SSH, sampeyan bisa uga ora nggunakake file kasebut ~/.ssh/config.

Transfer gambar liwat docker image save/load - Iki cara paling minimalistic, nanging ora mung siji. Ana liyane:

Registry Kontainer (standar industri).
Sambungake menyang server daemon docker saka host liyane:
1. variabel lingkungan DOCKER_HOST.
2. Pilihan baris printah -H utawa --host instrumen docker-compose.
3. docker context

Cara liya (kanthi telung opsi kanggo implementasine) uga diterangake ing artikel kasebut Cara masang ing host Docker remot karo docker-compose.

`deploy.sh`

Saiki ayo ngumpulake kabeh sing ditindakake kanthi manual dadi siji skrip. Ayo dadi miwiti karo fungsi ndhuwur-tingkat, lan banjur katon ing liyane digunakake ing.

Techniques menarik

${parameter?err_msg} - salah sawijining mantra sihir bash (alias substitusi parameter). Yen parameter ora kasebut, output err_msg lan metu nganggo kode 1.
docker --log-driver journald - minangka standar, driver logging docker minangka file teks tanpa rotasi. Kanthi pendekatan iki, log cepet ngisi kabeh disk, saengga kanggo lingkungan produksi kudu ngganti driver menyang sing luwih pinter.

skrip penyebaran

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
}

Fitur sing digunakake:

ensure-reverse-proxy - Priksa manawa proxy mbalikke bisa digunakake (migunani kanggo panyebaran pisanan)
get-active-slot service_name - Nemtokake slot sing saiki aktif kanggo layanan tartamtu (BLUE utawa GREEN)
get-service-status service_name deployment_slot - Nemtokake manawa layanan wis siyap kanggo ngolah panjaluk sing mlebu
set-active-slot service_name deployment_slot - Ngganti konfigurasi nginx ing wadhah proxy mbalikke

Ing urutan:

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
}

fungsi get-active-slot mbutuhake panjelasan sethithik:

Napa ngasilake nomer lan ora ngasilake senar?

Oalah, ing fungsi nelpon kita mriksa asil karya, lan mriksa kode metu nggunakake bash luwih gampang saka mriksa string. Kajaba iku, njupuk senar saka iku gampang banget:
get-active-slot service && echo BLUE || echo GREEN.

Apa telung kahanan pancen cukup kanggo mbedakake kabeh negara?

Malah loro bakal cukup, sing pungkasan kene mung kanggo jangkep, supaya ora nulis else.

Mung fungsi sing ngasilake konfigurasi nginx tetep ora ditemtokake: get-nginx-config service_name deployment_slot. Kanthi analogi karo mriksa kesehatan, ing kene sampeyan bisa nyetel konfigurasi kanggo layanan apa wae. Saka iku menarik - mung cat <<- EOF, sing ngidini sampeyan mbusak kabeh tab ing wiwitan. Bener, rega format sing apik yaiku campuran tab karo spasi, sing saiki dianggep minangka bentuk sing ala banget. Nanging bash pasukan tab, lan iku uga bakal becik kanggo duwe format normal ing nginx config. Ing cendhak, nyampur tab karo spasi ing kene pancene kaya solusi sing paling apik saka sing paling awon. Nanging, sampeyan ora bakal bisa ndeleng iki ing cuplikan ing ngisor iki, amarga Habr "nglakoni kanthi becik" kanthi ngganti kabeh tab dadi 4 spasi lan nggawe EOF ora sah. Lan ing kene katon.

Supaya ora tangi kaping pindho, aku bakal ngandhani sampeyan langsung cat << 'EOF', sing bakal ditemoni mengko. Yen sampeyan nulis kanthi prasaja cat << EOF, banjur ing heredoc string diinterpolasi (variabel ditambahi ($foo), telpon perintah ($(bar)) lan liya-liyane), lan yen sampeyan nutupi mburi dokumen ing kuotasi siji, interpolasi dipateni lan simbol $ ditampilake minangka. Apa sampeyan kudu nglebokake script ing script liyane.

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
}

Iki kabeh skrip. Lan supaya inti karo script iki kanggo ngundhuh liwat wget utawa curl.

Nglakokake skrip parameter ing server remot

Iku wektu kanggo ngalahake server target. wektu iki localhost cukup cocok:

$ 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.

Kita wis nulis skrip penyebaran sing ndownload gambar sing wis dibangun menyang server target lan ngganti wadhah layanan kanthi lancar, nanging kepiye carane bisa ditindakake ing mesin remot? Skrip kasebut nduweni argumen, amarga iku universal lan bisa nyebarake sawetara layanan bebarengan ing siji proxy mbalikke (sampeyan bisa nggunakake konfigurasi nginx kanggo nemtokake url sing bakal dadi layanan). Skrip ora bisa disimpen ing server, amarga ing kasus iki, kita ora bakal bisa nganyari kanthi otomatis (kanggo mbecike bug lan nambah layanan anyar), lan umume, negara = ala.

Solusi 1: Isih nyimpen script ing server, nanging nyalin saben wektu liwat scp. Banjur nyambung liwat ssh lan nglakokake skrip kanthi argumen sing dibutuhake.

Cons:

Loro tumindak tinimbang siji
Bisa uga ora ana papan kanggo nyalin, utawa ora bisa diakses, utawa skrip bisa dieksekusi nalika diganti.
Apike kanggo ngresiki sawise dhewe (mbusak script).
Wis telung tumindak.

Solusi 2:

Tansah definisi fungsi mung ing skrip lan ora mbukak apa-apa
Kanthi bantuan saka sed nambah telpon fungsi kanggo mburi
Kirim kabeh langsung menyang shh liwat pipa (|)

Pros:

Pancen stateless
Ora ana entitas boilerplate
Koyo kelangan

Ayo kita nindakake tanpa Ansible. Ya, kabeh wis diciptakake. Ya, sepeda. Delengen carane prasaja, elegan lan minimalis sepeda kasebut:

$ 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'

Nanging, kita ora bisa yakin manawa host remot duwe bash sing cukup, mula kita bakal nambah priksa cilik ing wiwitan (iki tinimbang 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

Lan saiki nyata:

$ 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!

Saiki sampeyan bisa mbukak http://localhost/ ing browser, mbukak penyebaran prajurit maneh lan priksa manawa iku mlaku seamlessly dening nganyari kaca miturut CD sak tata letak.

Ojo lali resik-resik sak wise nyambut gawe :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

Penyebaran Biru-Ijo kanthi upah minimum

layanan

Techniques menarik

Cetakan

Proksi mbalikke

Techniques menarik

Cetakan

Penyebaran mulus

Techniques menarik

Cetakan

Ngirim gambar

deploy.sh

Techniques menarik

skrip penyebaran

Nglakokake skrip parameter ing server remot

Ojo lali resik-resik sak wise nyambut gawe :3

`deploy.sh`