Kweli nqaku sisebenzisa , , ΠΈ Siza kuququzelela uyilo olungenamthungo lwesicelo sewebhu. bubuchule obukuvumela ukuba uhlaziye ngokukhawuleza isicelo ngaphandle kokwala isicelo esinye. Yenye yezicwangciso ezilithi zero downtime deployment kwaye ifaneleke kakhulu kwizicelo ezinomzekelo omnye, kodwa ukukwazi ukulayisha okwesibini, umzekelo olungele ukuqhutywa kufutshane.
Masithi unesicelo sewebhu apho abathengi abaninzi basebenza ngokukhutheleyo, kwaye akukho ndlela yakulala phantsi imizuzwana embalwa. Kwaye kufuneka ukhuphe uhlaziyo lwethala leencwadi, ukulungiswa kwebug, okanye into entsha epholileyo. Kwimeko eqhelekileyo, kuya kufuneka umise isicelo, ubeke endaweni yaso kwaye uqale kwakhona. Kwimeko ye-docker, unokuqala endaweni yayo, emva koko uyiqalise kwakhona, kodwa kusekho ixesha apho izicelo kwisicelo zingasayi kuqhutyelwa phambili, kuba ngokuqhelekileyo isicelo sithatha ixesha elithile ukulayisha ekuqaleni. Kuthekani ukuba iqala, kodwa ibonakala ingasebenzi? Le yingxaki, masiyisombulule ngeendlela ezincinci kwaye ngobuqhetseba kangangoko sinakho.
INKCAZELO: Uninzi lwenqaku linikezelwe kwifomathi yovavanyo - ngendlela yokurekhoda kweseshoni ye-console. Ngethemba ukuba oku akuyi kuba nzima kakhulu ukuyiqonda kwaye ikhowudi iya kuzibhala ngokwayo ngokwaneleyo. Kwi-atmosphere, khawufane ucinge ukuba ezi ayizoziqwengana nje zekhowudi, kodwa iphepha elivela kwi-teletype "yentsimbi".
Iindlela ezinomdla ezinzima kuGoogle ngokufunda ikhowudi zichazwe ekuqaleni kwecandelo ngalinye. Ukuba kukho enye into engacacanga, yi-google kwaye uyijonge. (Ngethamsanqa, iphinda isebenze, ngenxa yokuvulwa kwetelegram). Ukuba awukwazi ukwenza nantoni na kuGoogle, buza kumagqabantshintshi. Ndiya kukuvuyela ukongeza kwicandelo elihambelanayo "Iindlela ezinomdla".
Masiqalise.
$ mkdir blue-green-deployment && cd $_inkonzo
Masenze inkonzo yovavanyo kwaye siyibeke kwisikhongozeli.
ubuchule obunomdla
cat << EOF > file-name( + ) yindlela yokwenza ifayile yemigca emininzi ngomyalelo omnye. Yonke into bash ifunda ukusuka/dev/stdinemva kwalo mgca naphambi komgcaEOFizakurekhodwa kwifile-name.wget -qO- URL() β khupha uxwebhu olufunyenwe ngeHTTP ukuya/dev/stdout(i-analoguecurl URL).
Shicilela iphume
Ndophula ngokuthe ngqo i-snippet ukunika amandla ukuqaqambisa iPython. Ekugqibeleni kuya kubakho enye into efana nale. Qwalasela ukuba kwezi ndawo iphepha lanqunyulwa ukuba lithunyelwe kwisebe lokugqamisa (apho ikhowudi yayinombala wezandla kunye ne-highlighters), kwaye ke ezi ziqwenga zahlanganiswa emva.
$ cat << EOF > uptimer.pyfrom 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
uptimerReverse proxy
Ukuze isicelo sethu sikwazi ukutshintsha singaqatshelwa, kuyimfuneko ukuba kubekho enye into phambi kwayo eya kufihla ukutshintshwa kwayo. Isenokuba ngumncedisi wewebhu Π² . Ummeli obuyela umva usekiwe phakathi komxhasi kunye nesicelo. Yamkela izicelo zabaxhasi kwaye izigqithisele kwisicelo kwaye ithumele iimpendulo zesicelo kubaxumi.
Isicelo kunye neproxy ebuyela umva inokudityaniswa ngaphakathi kwidocker usebenzisa . Ngoko ke, isikhongozeli esinesicelo asifuni kuthumela ngaphambili izibuko kwindlela yenginginya, oku kuvumela isicelo ukuba sibekwe bucala kakhulu kwizoyikiso zangaphandle.
Ukuba umva ummeli ongomnye uhlala komnye umamkeli, kuya kufuneka ulahle inethiwekhi ye-docker kwaye uqhagamshele isicelo kwi-proxy ebuya umva ngapha komsebenzi womnatha womkhosi, udlulisela phambili izibuko. zicelo ipharamitha --publish, njengasekuqaleni nanjengakwiproksi engasemva.
Siza kuqhuba i-reverse proxy kwi-port 80, kuba eli liqumrhu elimele ukumamela inethiwekhi yangaphandle. Ukuba i-port 80 ixakekile kwi-host host yakho, tshintsha iparameter --publish 80:80 phezu --publish ANY_FREE_PORT:80.
ubuchule obunomdla
- βKwiintanethi zeDocker ezenziwe ngabasebenzisi, unokunxibelelana nezikhongozeli kungekuphela ngedilesi ye-IP. Igama lesikhongozeli lisonjululwe kwidilesi yalo ye-IP" (, inqaku lesi-5 lekhowudi yedocker).
Shicilela iphume
$ 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>Ukusasazwa ngaphandle komthungo
Masikhuphe uguqulelo olutsha lwesicelo (ngokuphinda-phindwe kabini konyuselo lokusebenza) kwaye sizame ukuyibeka ngaphandle komthungo.
ubuchule obunomdla
echo 'my text' | docker exec -i my-container sh -c 'cat > /my-file.txt'β Bhala isicatshulwamy textukwenza ifayile/my-file.txtngaphakathi kwesikhongozelimy-container.cat > /my-file.txtβ Bhala imixholo yegalelo eliqhelekileyo kwifayile/dev/stdin.
Shicilela iphume
$ 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-proxyNgeli nqanaba, umfanekiso wakhiwe ngokuthe ngqo kumncedisi, ofuna ukuba imithombo yesicelo ibe khona, kwaye iphinde ilayishe umncedisi ngomsebenzi ongadingekile. Isinyathelo esilandelayo kukunika indibano yomfanekiso kumatshini owahlukileyo (umzekelo, kwinkqubo yeCI) uze uyidlulisele kumncedisi.
Ukuhanjiswa kwemifanekiso
Ngelishwa, akukho ngqiqweni ukuhambisa imifanekiso ukusuka kwihostela yasekhaya ukuya kwihostela yasekhaya, ke eli candelo linokuhlolwa kuphela ukuba unenginginya ezimbini ezineDocker ekufutshane. Ubuncinci ijongeka ngolu hlobo:
$ 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.9MBIqela docker save igcina idatha yomfanekiso kwindawo yogcino .tar, ithetha ukuba inobunzima obumalunga namaxesha ayi-1.5 ngaphezulu kunobunzima obunobunzima kwifomu ecinezelweyo. Ke masiyishukumise egameni lokonga ixesha kunye netrafikhi:
$ docker image save uptimer | gzip | ssh production-server 'zcat | docker image load'
Loaded image: uptimer:latestUnako kwakhona ukubeka esweni inkqubo yokukhuphela (nangona oku kufuna into eluncedo yomntu wesithathu):
$ docker image save uptimer | gzip | pv | ssh production-server 'zcat | docker image load'
25,7MiB 0:01:01 [ 425KiB/s] [ <=> ]
Loaded image: uptimer:latestIngcebiso: Ukuba ufuna iqela leeparamitha ukuqhagamshela kumncedisi nge SSH, usenokungasebenzisi ifayile.
~/.ssh/config.
Ukuhambisa umfanekiso nge docker image save/load - Le yeyona ndlela incinci, kodwa ingeyiyo yodwa. Kukho abanye:
- IRegistry yesikhongozeli (umgangatho weshishini).
- Qhagamshela kwi-docker daemon server esuka komnye umamkeli:
- ukuguquguquka kokusingqongileyo
DOCKER_HOST. - Ukhetho lomgca womyalelo
-Hokanye--hostisixhobodocker-compose. docker context
- ukuguquguquka kokusingqongileyo
Indlela yesibini (kunye neenketho ezintathu zokuphunyezwa kwayo) ichazwe kakuhle kwinqaku .
deploy.sh
Ngoku masiqokelele yonke into esiyenzileyo ngesandla kwisikripthi esinye. Masiqale ngomsebenzi okwinqanaba eliphezulu, kwaye emva koko sijonge ezinye ezisetyenziswe kuwo.
ubuchule obunomdla
${parameter?err_msg}-enye yomlingo we-bash (aka ). Ukubaparameterayichazwanga, imvelisoerr_msgkwaye uphume ngekhowudi yoku-1.docker --log-driver journald- ngokuzenzekelayo, umqhubi wokuloga kwi-docker yifayile yokubhaliweyo ngaphandle kokujikeleza. Ngale ndlela, iilogi zizalise ngokukhawuleza idiski yonke, ngoko ke kwindawo yokuvelisa kuyimfuneko ukutshintsha umqhubi ukuba abe nobuchule.
Ukusasazwa kweskripthi
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
}Iimpawu ezisetyenzisiweyo:
ensure-reverse-proxy-Iqinisekisa ukuba iproxy engasemva iyasebenza (iluncedo kubhengezo lokuqala)get-active-slot service_name- Imisela ukuba yeyiphi indawo esebenzayo ngoku kwinkonzo enikiweyo (BLUEokanyeGREEN)get-service-status service_name deployment_slotβ Imisela ukuba ingaba inkonzo ikulungele na ukujongana nezicelo ezingenayoset-active-slot service_name deployment_slot-Itshintsha inginx config kwisingxobo sommeli esingasemva
Ngendle:
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
}Umsebenzi get-active-slot ifuna ingcaciso encinci:
Kutheni ibuyisela inani kwaye ingakhuphi umtya?
Nangona kunjalo, kumsebenzi wokufowuna sijonga isiphumo somsebenzi wayo, kwaye ukujonga ikhowudi yokuphuma usebenzisa i-bash kulula kakhulu kunokukhangela umtya. Ukongeza, ukufumana umtya kuyo kulula kakhulu:
get-active-slot service && echo BLUE || echo GREEN.
Ngaba iimeko ezintathu ngokwenene zanele ukwahlula onke amazwe?
Nokuba zimbini ziya kwanela, eyokugqibela ilapha nje ukuphelela, ukuze ungabhali else.
Kuphela ngumsebenzi obuyisela i-nginx configs uhlala ungachazwanga: get-nginx-config service_name deployment_slot. Ngokufaniswa nokujonga impilo, apha unokuseta nayiphi na i-config yayo nayiphi na inkonzo. Kwizinto ezinomdla - kuphela cat <<- EOF, ekuvumela ukuba ususe zonke iithebhu ekuqaleni. Enyanisweni, ixabiso lokufomatha okulungileyo lixutywe iithebhu kunye nezithuba, namhlanje zibhekwa njengefomu embi kakhulu. Kodwa i-bash inyanzela iithebhu, kwaye kuya kuba kuhle ukuba nokufomatha okuqhelekileyo kwinginx config. Ngamafutshane, ukuxuba iithebhu kunye nezithuba apha ngokwenene kubonakala ngathi sesona sisombululo silungileyo. Nangona kunjalo, awuyi kubona oku kwi-snippet engezantsi, ekubeni uHabr "wenza kakuhle" ngokutshintsha zonke iithebhu kwiindawo ze-4 kunye nokwenza i-EOF ingasebenzi. .
Ukuze ungavuki kabini, ndiza kukuxelela kwangoko malunga
cat << 'EOF', esiza kudibana nayo kamva. Ukuba ubhala ngokululacat << EOF, ngoko ngaphakathi kweheredoc umtya uyadityaniswa (iinguqu ziyandiswa ($foo), imiyalelo iminxeba ($(bar)) njl.), kwaye ukuba uvalela isiphelo soxwebhu kwizicaphulo ezilodwa, uguqulelo luvaliwe kwaye nesimboli$iboniswa njengoko injalo. Yintoni oyifunayo ukufaka iskripthi ngaphakathi kwesinye iskripthi.
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
}Esi siskripthi sonke. Kwaye ukukhuphela nge-wget okanye i-curl.
Ukwenza izikripthi ezineparameterized kwiseva ekude
Lixesha lokunkqonkqoza kumncedisi ekujoliswe kuwo. Ngeli xesha localhost kufanelekile:
$ 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.Sibhale iskripthi sokusasaza esikhuphela umfanekiso owakhelwe ngaphambili kwiseva ekujoliswe kuyo kwaye ngokungenamthungo endaweni yesikhongozeli senkonzo, kodwa singayiphumeza njani kumatshini okude? Umbhalo uneengxoxo, kuba ukwindawo yonke kwaye unokubeka iinkonzo ezininzi ngaxeshanye phantsi kommeli omnye umva (ungasebenzisa i-nginx configs ukumisela ukuba yeyiphi i-url eyakuba yeyiphi inkonzo). Isikripthi asikwazi ukugcinwa kumncedisi, ekubeni kulo mzekelo asiyi kukwazi ukuyihlaziya ngokuzenzekelayo (ngenjongo yokulungiswa kwe-bug kunye nokongeza iinkonzo ezintsha), kwaye ngokubanzi, urhulumente = ububi.
Isisombululo 1: Usagcina iskripthi kwiseva, kodwa uyikopishe ngalo lonke ixesha scp. Emva koko qhagamshela nge ssh kwaye uphumeze okushicilelweyo ngeengxoxo eziyimfuneko.
Umgcini:
- Izenzo ezibini endaweni yesinye
- Akunakubakho indawo apho ukopisha khona, okanye kungabikho ukufikelela kuyo, okanye iskripthi sinokuphunyezwa ngexesha lokutshintshwa.
- Kuyacetyiswa ukuba ucoce emva kwakho (cima iskripthi).
- Sele zithathu izenzo.
Isisombululo 2:
- Gcina kuphela iinkcazo zomsebenzi kwiscript kwaye ungasebenzi nto konke konke
- Ngo kunceda
sedyongeza umnxeba womsebenzi ekupheleni - Yithumele yonke ngokuthe ngqo kwi-shh ngombhobho (
|)
Iinkonzo:
- Ngokwenene ayinammiselo
- Akukho ziko lebhoilerplate
- Ukuziva upholile
Masenze nje ngaphandle koAnsible. Ewe, yonke into sele iyilwe. Ewe, ibhayisekile. Jonga indlela ilula, ubuhle kunye nobuncinci ngayo ibhayisekile:
$ 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_SCRIPTEOF
$ 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'Nangona kunjalo, asinakuqiniseka ukuba inginginya ekude ine-bash eyaneleyo, ngoko ke siyakongeza itshekhi encinci ekuqaleni (le endaweni ye ):
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
fiKwaye ngoku iyinyani:
$ 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!Ngoku ungavula kwisikhangeli, sebenzisa ukusasazwa kwakhona kwaye uqinisekise ukuba ibaleka ngokungenamthungo ngokuhlaziya iphepha ngokweCD ngexesha loyilo.
Ungalibali ukucoca emva komsebenzi :3
$ docker rm -f uptimer_GREEN reverse-proxy
uptimer_GREEN
reverse-proxy
$ docker network rm web-gateway
web-gateway
$ cd ..
$ rm -r blue-green-deploymentumthombo: www.habr.com