🥇Blue-Green Deployment a mafi ƙarancin albashi

A cikin wannan labarin muna amfani Bash, ssh, docker и nginx Za mu tsara tsari mara kyau na aikace-aikacen gidan yanar gizo. Aiwatar da shuɗi-kore wata dabara ce da ke ba ku damar sabunta aikace-aikacen nan take ba tare da kin amincewa da buƙatu ɗaya ba. Yana ɗaya daga cikin dabarun ƙaddamar da lokacin raguwar sifili kuma ya fi dacewa don aikace-aikace tare da misali ɗaya, amma ikon loda na biyu, misalin shirye-shiryen aiwatarwa kusa.

Bari mu ce kuna da aikace-aikacen yanar gizo wanda yawancin abokan ciniki ke aiki da shi, kuma babu kwata-kwata babu yadda za ta yi ta kwanta na daƙiƙa biyu. Kuma da gaske kuna buƙatar fitar da sabuntawar ɗakin karatu, gyara kwaro, ko sabon salo mai kyau. A cikin yanayi na al'ada, kuna buƙatar dakatar da aikace-aikacen, maye gurbin shi kuma sake fara shi. Game da docker, za ku iya fara maye gurbinsa, sannan ku sake kunna shi, amma har yanzu akwai lokacin da ba za a iya sarrafa buƙatun aikace-aikacen ba, saboda yawanci aikace-aikacen yana ɗaukar ɗan lokaci kafin farawa. Idan ya fara, amma ya juya baya aiki fa? Wannan ita ce matsalar, bari mu magance ta da ƙananan hanyoyi kuma da kyau kamar yadda zai yiwu.

RA'AYI: Yawancin labarin ana gabatar da su a cikin sigar gwaji - ta hanyar rikodi na zaman wasan bidiyo. Da fatan wannan ba zai yi wahalar fahimta ba kuma lambar za ta rubuta kanta sosai. Don yanayi, yi tunanin cewa waɗannan ba snippets ne kawai ba, amma takarda daga nau'in teletype na "ƙarfe".

Dabarun masu ban sha'awa waɗanda ke da wahala ga Google kawai ta hanyar karanta lambar an bayyana su a farkon kowane sashe. Idan wani abu kuma bai bayyana ba, google shi kuma duba shi. bayani (An yi sa'a, yana sake aiki, saboda buɗewa na telegram). Idan ba za ku iya Google komai ba, tambaya a cikin sharhi. Zan yi farin ciki don ƙara zuwa sashin da ya dace "Hanyoyin ban sha'awa".

Bari mu fara

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

sabis

Bari mu yi sabis na gwaji kuma mu sanya shi a cikin akwati.

Dabaru masu ban sha'awa

cat << EOF > file-name (Nan Takardu + Juyawa I/O) hanya ce ta ƙirƙirar fayil ɗin layi mai yawa tare da umarni ɗaya. Komai bash ya karanta daga /dev/stdin bayan wannan layi da kuma kafin layi EOF za a rubuta a ciki file-name.
wget -qO- URL (bayani) - fitar da takaddun da aka karɓa ta hanyar HTTP zuwa /dev/stdout (analogue curl URL).

Kwafi

Na karya snippet na musamman don ba da damar haskakawa ga Python. A ƙarshe za a sami wani yanki kamar wannan. Yi la'akari da cewa a cikin waɗannan wurare an yanke takarda don aika zuwa sashen haskakawa (inda lambar ta kasance mai launin hannu tare da masu haskakawa), sannan waɗannan sassan an manne da baya.

$ 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

Mai juyawa wakili

Domin aikace-aikacenmu ya sami damar canzawa ba tare da lura ba, ya zama dole a sami wani mahaluƙi a gabansa wanda zai ɓoye maye gurbinsa. Zai iya zama sabar yanar gizo nginx в yanayin juyawa. An kafa wakili na baya tsakanin abokin ciniki da aikace-aikacen. Yana karɓar buƙatun abokan ciniki kuma yana tura su zuwa aikace-aikacen kuma yana tura martanin aikace-aikacen ga abokan ciniki.

Ana iya haɗa aikace-aikacen da wakili na baya a cikin docker ta amfani da docker network. Don haka, kwantena tare da aikace-aikacen baya buƙatar tura tashar jiragen ruwa akan tsarin runduna; wannan yana ba da damar aikace-aikacen ya zama mafi ƙasƙanci daga barazanar waje.

Idan wakili na baya yana rayuwa akan wani mai masaukin baki, dole ne ku watsar da hanyar sadarwar docker kuma ku haɗa aikace-aikacen zuwa wakili na baya ta hanyar hanyar sadarwa, tura tashar jiragen ruwa. apps siga --publish, kamar a farkon farawa kuma kamar yadda yake tare da wakili na baya.

Za mu gudanar da reverse proxy akan tashar jiragen ruwa 80, saboda wannan shine ainihin mahallin da ya kamata ya saurari hanyar sadarwa ta waje. Idan tashar tashar jiragen ruwa 80 tana aiki akan mai masaukin gwajin ku, canza siga --publish 80:80 a kan --publish ANY_FREE_PORT:80.

Dabaru masu ban sha'awa

"A cikin hanyoyin sadarwar Docker da aka ƙirƙira mai amfani, zaku iya sadarwa tare da kwantena ba kawai ta adireshin IP ba. Ana kuma warware sunan kwandon cikin adireshin IP ɗin sa" (labarin "Cibiyar sadarwa tare da kwantena kadai", sashi "Yi amfani da hanyoyin sadarwar gada da aka ayyana", aya ta 5 na lambar docker).

Kwafi

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

Ƙaddamar da aiki mara kyau

Bari mu fitar da sabon sigar aikace-aikacen (tare da haɓaka aikin farawa sau biyu) kuma muyi ƙoƙarin tura shi ba tare da matsala ba.

Dabaru masu ban sha'awa

echo 'my text' | docker exec -i my-container sh -c 'cat > /my-file.txt' - Rubuta rubutu my text da fayil /my-file.txt cikin akwati my-container.
cat > /my-file.txt - Rubuta abubuwan da ke cikin daidaitaccen shigarwar zuwa fayil /dev/stdin.

Kwafi

$ 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

A wannan matakin, an gina hoton kai tsaye akan uwar garken, wanda ke buƙatar tushen aikace-aikacen su kasance a wurin, kuma yana ɗaukar sabar tare da aikin da ba dole ba. Mataki na gaba shine raba taron hoton zuwa na'ura daban (misali, zuwa tsarin CI) sannan a canza shi zuwa uwar garken.

Canja wurin hotuna

Abin takaici, ba shi da ma'ana don canja wurin hotuna daga localhost zuwa localhost, don haka za a iya bincika wannan sashe idan kuna da runduna biyu tare da Docker a hannu. A taƙaice yana kama da wani abu kamar haka:

$ 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

tawagar docker save yana adana bayanan hoto a cikin .tar .tar, ma'ana yana awo kusan sau 1.5 fiye da yadda zai auna cikin matsi. Don haka bari mu girgiza shi da sunan ceton lokaci da zirga-zirga:

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

Hakanan zaka iya saka idanu akan tsarin saukewa (kodayake wannan yana buƙatar kayan aiki na ɓangare na uku):

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

Tukwici: Idan kuna buƙatar tarin sigogi don haɗawa zuwa uwar garken ta hanyar SSH, ƙila ba za ku yi amfani da fayil ɗin ba ~/.ssh/config.

Canja wurin hoton ta hanyar docker image save/load - Wannan ita ce mafi ƙarancin hanya, amma ba ita kaɗai ba. Akwai wasu:

Rijistar kwantena (misali masana'antu).
Haɗa zuwa uwar garken docker daemon daga wani runduna:
1. m yanayi DOCKER_HOST.
2. Zaɓin layin umarni -H ko --host kayan aiki docker-compose.
3. docker context

Hanya na biyu (tare da zaɓuɓɓuka guda uku don aiwatar da shi) an kwatanta shi da kyau a cikin labarin Yadda ake tura runduna Docker masu nisa tare da rubutaccen docker.

`deploy.sh`

Yanzu bari mu tattara duk abin da muka yi da hannu zuwa rubutu ɗaya. Bari mu fara da aikin babban matakin, sannan mu kalli sauran da aka yi amfani da su a ciki.

Dabaru masu ban sha'awa

${parameter?err_msg} - daya daga cikin sihirin bash (aka maye gurbin siga). Idan parameter ba a ƙayyade ba, fitarwa err_msg kuma fita da code 1.
docker --log-driver journald - ta hanyar tsoho, direban docker log fayil fayil ne na rubutu ba tare da wani juyi ba. Tare da wannan hanyar, rajistan ayyukan da sauri suna cika faifai gabaɗaya, don haka don yanayin samarwa ya zama dole don canza direba zuwa mafi wayo.

Rubutun turawa

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
}

Abubuwan da aka yi amfani da su:

ensure-reverse-proxy - Tabbatar cewa wakili na baya yana aiki (yana da amfani don turawa na farko)
get-active-slot service_name - Yana ƙayyade wane rami a halin yanzu yana aiki don sabis ɗin da aka bayar (BLUE ko GREEN)
get-service-status service_name deployment_slot - Yana ƙayyade ko sabis ɗin yana shirye don aiwatar da buƙatun masu shigowa
set-active-slot service_name deployment_slot - Yana canza saitin nginx a cikin kwandon wakili na baya

Domin:

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
}

aiki get-active-slot yana buƙatar ɗan bayani:

Me yasa yake mayar da lamba kuma baya fitar da kirtani?

Ko ta yaya, a cikin aikin kira muna duba sakamakon aikinsa, kuma duba lambar fita ta amfani da bash ya fi sauƙi fiye da duba kirtani. Bugu da kari, samun kirtani daga gare ta abu ne mai sauqi:
get-active-slot service && echo BLUE || echo GREEN.

Shin da gaske ne sharuɗɗa guda uku sun isa su bambanta duka jihohi?

Ko biyu za su isa, na ƙarshe yana nan don cikawa kawai, don kada a rubuta else.

Ayyukan da ke dawo da saitunan nginx kawai ba a bayyana su ba: get-nginx-config service_name deployment_slot. Ta misali tare da duba lafiya, a nan za ku iya saita kowane saiti don kowane sabis. Daga cikin abubuwan ban sha'awa - kawai cat <<- EOF, wanda ke ba ka damar cire duk shafuka a farkon. Gaskiya ne, farashin tsari mai kyau yana haɗuwa da shafuka tare da sarari, wanda a yau ana la'akari da mummunan nau'i. Amma bash tilasta shafuka, kuma zai yi kyau a sami tsari na yau da kullun a cikin saitin nginx. A takaice, hada shafuka tare da sarari anan da gaske yana kama da mafi kyawun mafita daga mafi munin yanayi. Duk da haka, ba za ku ga wannan a cikin snippet da ke ƙasa ba, tun da Habr "yana yin kyau" ta hanyar canza duk shafuka zuwa wurare 4 da yin EOF mara aiki. Kuma a nan abin lura ne.

Don kada ku tashi sau biyu, zan gaya muku nan da nan cat << 'EOF', wanda za a ci karo da shi daga baya. Idan ka rubuta a sauƙaƙe cat << EOF, sannan a cikin heredoc an haɗa kirtani (ana faɗaɗa sauye-sauye ($foo), kiran kira ($(bar)) da dai sauransu), kuma idan kun haɗa ƙarshen daftarin aiki a cikin ƙididdiga guda ɗaya, to interpolation ba shi da rauni kuma alamar. $ ana nunawa kamar yadda yake. Abin da kuke buƙatar saka rubutun a cikin wani rubutun.

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
}

Wannan shine duka rubutun. Say mai gist da wannan rubutun don saukewa ta hanyar wget ko curl.

Ana aiwatar da madaidaitan rubutun akan sabar mai nisa

Lokaci yayi da za a buga kan uwar garken manufa. Wannan karon localhost dace sosai:

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

Mun rubuta rubutun turawa wanda ke zazzage hoton da aka riga aka gina zuwa uwar garken manufa kuma ya maye gurbin kwandon sabis ɗin ba tare da matsala ba, amma ta yaya za mu iya aiwatar da shi a kan na'ura mai nisa? Rubutun yana da gardama, tunda duniya ce kuma tana iya tura ayyuka da yawa lokaci ɗaya a ƙarƙashin wakili na baya (zaka iya amfani da saitunan nginx don sanin wane url ne zai zama sabis ɗin). Ba za a iya adana rubutun a kan uwar garke ba, tun da yake a wannan yanayin ba za mu iya sabunta shi ta atomatik ba (don manufar gyaran kwari da ƙara sababbin ayyuka), kuma a gaba ɗaya, jihar = mugunta.

Magani 1: Har yanzu adana rubutun akan uwar garken, amma kwafi kowane lokaci ta hanyar scp. Sannan haɗa ta hanyar ssh kuma aiwatar da rubutun tare da hujjoji masu dacewa.

Fursunoni:

Ayyuka biyu maimakon ɗaya
Wataƙila ba za a sami wurin da za ku kwafi ba, ko kuma ba za a iya samun damar yin amfani da shi ba, ko kuma ana iya aiwatar da rubutun a lokacin canji.
Yana da kyau a tsaftace bayan kanku (share rubutun).
Tuni ayyuka uku.

Magani 2:

Ajiye ma'anar ayyuka kawai a cikin rubutun kuma gudanar da komai kwata-kwata
Tare da taimakon sed ƙara kiran aiki zuwa ƙarshe
Aika shi duka kai tsaye zuwa shh ta bututu (|)

Sakamakon:

Haƙiƙa marar ƙasa
Babu mahallin tukunyar jirgi
Jin sanyi

Mu yi kawai ba tare da Mai yiwuwa ba. Haka ne, an riga an ƙirƙira komai. Ee, keke. Dubi yadda babur ɗin ya kasance mai sauƙi, kyakkyawa da ƙarancin ƙima:

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

Koyaya, ba za mu iya tabbatar da cewa mai watsa shiri mai nisa yana da isasshen bash, don haka za mu ƙara ɗan ƙaramin dubawa a farkon (wannan maimakon harsashi):

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

Kuma yanzu gaskiya ne:

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

Yanzu zaku iya buɗewa http://localhost/ a cikin burauzar, sake gudanar da aikin kuma tabbatar da cewa yana gudana ba tare da matsala ba ta hanyar sabunta shafin bisa ga CD yayin shimfidawa.

Kar a manta da tsaftacewa bayan aiki: 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

Ƙaddamar da Blue-Green a mafi ƙarancin albashi

sabis

Dabaru masu ban sha'awa

Kwafi

Mai juyawa wakili

Dabaru masu ban sha'awa

Kwafi

Ƙaddamar da aiki mara kyau

Dabaru masu ban sha'awa

Kwafi

Canja wurin hotuna

deploy.sh

Dabaru masu ban sha'awa

Rubutun turawa

Ana aiwatar da madaidaitan rubutun akan sabar mai nisa

Kar a manta da tsaftacewa bayan aiki: 3

`deploy.sh`