Lo mbhalo uhloselwe abaklami bezakhiwo kanye nabantu abasebenza emisebenzini kanye
amaqembu okuphatha. Idokhumenti ichaza iphethini yesibonelo ongayisebenzisa
ngokusetshenziswa kwakho ku-Google Cloud.


Kule phethini, isilinganisi somthwalo siqondisa ithrafikhi kuyo
Injini Yekhompyutha
izimo ku
amaqembu esibonelo aphethwe
ezinikeza okuqukethwe. Uma ucisha, ubuyekeza ifayela
I-HTTP(S) yangaphandle Yokulayisha Ukulinganisa
ukucushwa bese wehluleka kusayithi elimile
Isitoreji Samafu.


Ukuze uqedele lesi sifundo, udinga igama lesizinda elibhalisiwe olilawulayo
futhi ufuna ukuyisebenzisa nale dokhumenti.


Ekusetshenzisweni kokukhiqiza, iwebhusayithi yakho kungenzeka ifake amafayela amaningi kanye
ikhodi eyengeziwe yohlelo lokusebenza emishinini ebonakalayo yeqembu lesibonelo ephethwe
(ama-VM) kunalokhu kuboniswe kulo mbhalo. I-Cloud Storage bese isingatha okwengeziwe
inguqulo emile elinganiselwe enikeza ukusebenza okuncane. Ekuhlulekeni okufudumele
isimo, abasebenzisi babona le webhusayithi ekhawulelwe kuze kube amaqembu esibonelo aphethwe
lulama futhi inganikeza ithrafikhi ukuze uthole ulwazi olugcwele lwewebhusayithi.


Kulesi sifundo, usebenzisa izinsiza ukuze udale indawo njengoba kukhonjisiwe ku-
isithombe esilandelayo:





Uma udinga ukuhluleka, ubuyekeza ukucushwa kwesilinganisi sokulayisha ukuze siqondise
ithrafikhi ku-Cloud Storage, njengoba kukhonjisiwe esithombeni esilandelayo:





Le phethini ye-failover efudumele ibhalansisa izindleko zokuqhuba enye ephethwe
isibonelo iqembu endaweni ehlukile oyisebenzisa kuphela uma izifunda eziyinhloko
hluleka. Izindleko zesayithi elimile zisebenzisa Isitoreji Samafu ziphansi kunokusebenza
elinye iqembu lesibonelo esiphethwe, kodwa kukhona ukubambezeleka okufushane njengoba ubuyekeza umthwalo
ukucushwa kwe-balancer phakathi kwezinketho zokubamba. Iwebhusayithi enomkhawulo
umuzwa Kusitoreji Samafu ungcono kunewebhusayithi engatholakali futhi impofu
ulwazi lwekhasimende.


Ukuze uthole enye indlela esebenzisa i-Cloud DNS esikhundleni seyangaphandle
I-HTTP(S) Yokulayisha Ukulinganisa ukuze ulawule ukuhluleka, bheka
Sebenzisa iseva yewebhu efudumele ebuyisekayo usebenzisa i-Cloud DNS ene-Compute Engine kanye ne-Cloud Storage.
Le phethini iwusizo uma une, noma ufuna ukusebenzisa, i-Cloud DNS.


Ukuze usebenzise izinhlelo zokusebenza ezithembekile ku-Google Cloud, sincoma ukuthi udizayine
ingqalasizinda yesicelo sakho ukubhekana nokucisha. Kuye ngesicelo sakho
kanye nezidingo zebhizinisi, ungase udinge i-failover ebandayo, i-faillover efudumele, noma eshisayo
iphethini ye-failover. Ukuze uthole ukwaziswa okwengeziwe mayelana nendlela yokunquma indlela engcono kakhulu ye
izicelo zakho siqu, bona
Umhlahlandlela wokuhlela ukutakula kwezinhlekelele.


Lo mbhalo usebenzisa isisekelo
Iseva yewebhu ye-Apache,
kodwa indlela efanayo yokusatshalaliswa kwengqalasizinda iyasebenza nakwabanye
izindawo zohlelo lokusebenza okudingeka ukuzenza.
## Izinjongo
 


-

- Dala amaqembu esibonelo aphethwe yisifunda ngesithombe sangokwezifiso se-VM.

- Dala ibhakede le-Cloud Storage.

- Dala futhi ulungiselele i-HTTP(S) yangaphandle Yokulayisha Ukulinganisa.

- Hlola i-failover yeseva yewebhu efudumele ngesilinganisi esibuyekeziwe somthwalo
ukumisa.

- Hlola ukululama nokwehluleka ngohlelo olusha lwebhalansi yomthwalo.

## Izindleko
 








 


 

 Lesi sifundo sisebenzisa izingxenye ezilandelayo ezikhokhisekayo ze-Google Cloud:
 

 


-

- Injini Yekhompyutha

- Inethiwekhi

- Cloud Storage


 

 
 Ukuze wenze isilinganiso sezindleko ngokusekelwe ekusebenziseni kwakho okucatshangelwayo,
 sebenzisa umshini wokubala amanani.

## Ngaphambi kokuthi uqale
 





-













-
 
 
 
 Ngena ngemvume ku-akhawunti yakho ye-Google Cloud. Uma umusha ku
 I-Google Cloud,
 dala i-akhawunti ukuze uhlole ukuthi imikhiqizo yethu isebenza kanjani
 izimo zomhlaba wangempela. Amakhasimende amasha aphinde athole u-$300 kumakhredithi amahhala kuwo
 gijima, uhlole, futhi ukhiphe imithwalo yemisebenzi.
 
 
 
 
 
 

 
 

 
 

 
 
 

 
 










 
 
 

-
 
 

Ku-Google Cloud console, ekhasini lesikhethi sephrojekthi,
 khetha noma dala iphrojekthi ye-Google Cloud.
 
 
 

 
 
 
 



 
 
 








 

-
 


 Qiniseka ukuthi inkokhelo inikwe amandla kuphrojekthi yakho Yefu. Funda ukwenza kanjani
 hlola ukuthi inkokhelo ivuliwe yini kuphrojekthi.

 
 
 


 
 
 
 











 
 

-
 
 
 


 
 
 
 Nika amandla i-Compute Engine API.
 
 
 

 



 
 
 
 

 
 









 





 





 

-
 
 Faka futhi uqalise i-Google Cloud CLI.

 

 
 
 
 
 
 






 
 
 


-
 
 

Ku-Google Cloud console, ekhasini lesikhethi sephrojekthi,
 khetha noma dala iphrojekthi ye-Google Cloud.
 
 
 

 
 
 
 



 
 
 








 

-
 


 Qiniseka ukuthi inkokhelo inikwe amandla kuphrojekthi yakho Yefu. Funda ukwenza kanjani
 hlola ukuthi inkokhelo ivuliwe yini kuphrojekthi.

 
 
 


 
 
 
 











 
 

-
 
 
 


 
 
 
 Nika amandla i-Compute Engine API.
 
 
 

 



 
 
 
 

 
 









 





 





 

-
 
 Faka futhi uqalise i-Google Cloud CLI.

 

 
 
 
 
 
 






 
 
 


Ungaqalisa i-Google Cloud CLI ku-
console ngaphandle kokufaka i-
I-Google Cloud CLI. Ukuze usebenzise i-gcloud CLI ku-
console, sebenzisa i-Cloud Shell

## Lungisa imvelo


Kulesi sigaba, uchaza okunye okuguquguqukayo kwamagama wakho wensiza kanye
izindawo. Lokhu okuguquguqukayo kusetshenziswa imiyalo ye-Google Cloud CLI njengawe
hambisa izinsiza.


Kuwo wonke lo mbhalo, ngaphandle uma kushiwo ngenye indlela, ufaka yonke imiyalo kuyo
Igobolondo Lefu
noma indawo yangakini yokuthuthuka.


-

Faka esikhundleni


nge-ID yakho yephrojekthi. Uma uthanda,
hlinzeka ngesakho isijobelelo segama ukuze uthole izinsiza ezizokusiza ukusesha nokukhomba
kwabo, njenga
PROJECT_ID


uhlelo lokusebenza
Cacisa izifunda ezimbili, njenge


futhi

us-west1
, kanye nendawo engaphakathi kweyodwa yalezo zifunda, njenge

us-west2
. Le zoni ichaza lapho isisekelo sokuqala se-VM
idaliwe esisetshenziselwa ukudala isithombe seqembu lesibonelo eliphethwe

us-west1-a
Ekugcineni, setha isizinda esisetshenziselwa iwebhusayithi yakho emile, njenge




example.com
PROJECT_ID=
PROJECT_ID
NAME_SUFFIX= uhlelo lokusebenza
REGION1= us-west1
REGION2= us-west2
IZONE= us-west1-a
DOMAIN= example.com
 

## Dala i-VPC kanye ne-subnet


Ukuze unikeze ukufinyelela kwenethiwekhi kuma-VM, udala i-Virtual Private Cloud (VPC)
kanye nama-subnet. Njengoba udinga amaqembu esibonelo aphethwe ezifundeni ezimbili, udala eyodwa
subnet esifundeni ngasinye. Ukuze uthole ulwazi olwengeziwe mayelana nezinzuzo zesiko
imodi ye-subnet yokuphatha ububanzi bamakheli e-IP asetshenziswa endaweni yangakini, bheka
Sebenzisa amanethiwekhi e-VPC emodi yangokwezifiso.


-

Dala i-VPC ngemodi ye-subnet yangokwezifiso:

amanethiwekhi ekhompyutha e-gcloud akha inethiwekhi-$NAME_SUFFIX --subnet-mode=custom


Manje dala ama-subnet amabili ku-VPC entsha, eyodwa ngayinye
isifunda. Chaza ububanzi bekheli lakho, njengokuthi


futhi
10.1.0.0/20
, lokho
ngena ebangeni lenethiwekhi yakho:
10.2.0.0/20
gcloud compute networks subnets kudala n subnet-$NAME_SUFFIX-$REGION1 n --network=network-$NAME_SUFFIX n --range=
10.1.0.0/20n --region=$REGION1

gcloud compute networks subnets kudala n subnet-$NAME_SUFFIX-$REGION2 n --network=network-$NAME_SUFFIX n --range= 10.2.0.0/20n --region=$REGION2
 

## Dala imithetho ye-firewall


Ukuze uvumele ithrafikhi yenethiwekhi ukuthi igeleze kahle ku-VPC, sebenzisa
imithetho ye-firewall.


-

Dala imithetho ye-firewall ukuvumela ithrafikhi yewebhu nokuhlolwa kwezempilo komthwalo
ibhalansi namaqembu esibonelo aphethwe:



I-gcloud compute firewall-rules idala ukuvumela-http-$NAME_SUFFIX n --network=network-$NAME_SUFFIX n --direction=INGRESS n --priority=1000 n --action=ALLOW n --rules=tcp:80 n -- umthombo-range=0.0.0.0/0 n --target-tags=http-server

I-gcloud compute firewall-rules idala i-vumela-health-check-$NAME_SUFFIX n --network=network-$NAME_SUFFIX n --action=vumela n --direction=ingress n --source-ranges=130.211.0.0/22,35.191. 0.0/16 n --target-tags=vumela-isheke-impilo n --rules=tcp:80

Umthetho we-HTTP uvumela ithrafikhi kunoma iyiphi i-VM lapho i-
I-http-servertag isetshenzisiwe,
kanye nanoma yimuphi umthombo osebenzisa i-
0.0.0.0/0ububanzi. Okwe
umthetho wokuhlola impilo,
ububanzi obuzenzakalelayo be-Google Cloud busethelwe ukuvumela ingxenyekazi ukuthi isebenze kahle
hlola impilo yezinsiza.

Ukuvumela ithrafikhi ye-SSH ekucushweni kokuqala kwesithombe esiyisisekelo se-VM, ububanzi
umthetho firewall endaweni yakho usebenzisa


--umthombo-ububanzi bepharamitha.
Kungase kudingeke ukuthi usebenze nethimba lakho lenethiwekhi ukuze unqume ukuthi yibuphi ububanzi bomthombo
inhlangano yakho isebenzisa

Faka esikhundleni

ngezikophu zekheli lakho le-IP:
IP_ADDRESS_SCOPE
I-gcloud compute firewall-rules idala ukuvumela-ssh-$NAME_SUFFIX n --network=network-$NAME_SUFFIX n --direction=INGRESS n --priority=1000 n --action=ALLOW n --rules=tcp:22 n -- imithombo-amabanga=
IP_ADDRESS_SCOPE
 

Ngemuva kokuthi udale imithetho yohlelo lokuvikela, qinisekisa ukuthi imithetho emithathu ibiyilo
wengeze:
gcloud compute firewall-rules-rules list n --project=$PROJECT_ID n --filter="NETWORK=network-$NAME_SUFFIX"Isibonelo esilandelayo esiphumayo sibonisa ukuthi imithetho emithathu ibikade ilungile
idaliwe:

YIBA OKUMQOKA OKUQONDISWA KWENEWEKHI VUMELA
vumela-impilo-hlola-uhlelo lokusebenza lwenethiwekhi-uhlelo lokusebenza lwe-INGRESS 1000 tcp:80
vumela-http-app network network-app INGRESS 1000 tcp:80
vumela-ssh-app network-app INGRESS 1000 tcp:22


## Dala futhi ulungiselele isithombe esiyisisekelo se-VM


Ukuze udale ama-VM afanayo owasebenzisayo ngaphandle kokucushwa okwengeziwe, wena
sebenzisa isithombe se-VM sangokwezifiso. Lesi sithombe sithwebula i-OS ne-Apache ukucushwa, futhi
isetshenziselwa ukudala i-VM ngayinye eqenjini lesibonelo eliphethwe ezinyathelweni ezilandelayo.


Ku-VM, udala okuyisisekelo
index.html ifayela kudiski eqhubekayo kanye
khweza ku
/var/www/example.com. Ifayela lokucushwa le-Apache ku

/etc/apache2/sites-available/example.com.conf inikeza okuqukethwe kwewebhu kusuka
kufakwe indawo yediski eqhubekayo

Umdwebo olandelayo ubonisa ikhasi le-HTML eliyisisekelo elinikezwa i-Apache eligcinwe
kudiski eqhubekayo:





Wakha le ndawo ngezinyathelo ezilandelayo.


-

Dala i-VM eyisisekelo ngediski eqhubekayo enamathiselwe:



i-gcloud compute izehlakalo zenza i-vm-base-$NAME_SUFFIX n --zone=$ZONE n --machine-type=n1-standard-1 n --subnet=subnet-$NAME_SUFFIX-$REGION1 n --tags=http-server n --image=debian-10-buster-v20210420 n --image-project=debian-cloud n --boot-disk-size=10GB n --boot-disk-type=pd-balanced n --boot-disk- device-name=vm-base-$NAME_SUFFIX n --create-disk=type=pd-ssd,name=disk-base-$NAME_SUFFIX,size=10GB,device-name=disk-base-$NAME_SUFFIX

Usebenzisa amapharamitha achazwe ekuqaleni kwale dokhumenti ukuqamba i-VM kanye
xhuma ku-subnet efanele. Amagama nawo anikezwa kusukela kumapharamitha we
i-boot disk ne-data disk.

Ukuze ufake futhi ulungiselele iwebhusayithi elula, xhuma ku-base VM usebenzisa
I-SSH:

I-gcloud compute ssh vm-base-$NAME_SUFFIX --zone=$ZONE


Esikhathini sakho se-SSH ku-VM, dala iskripthi ukuze ulungiselele i-VM ku-
umhleli ozikhethele. Isibonelo esilandelayo sisetshenziswa
Nano
njengomhleli:



I-nano configure-vm.
Namathisela iskripthi sokumisa esilandelayo efayeleni:



umgqomo/bash

NAME_SUFFIX=
uhlelo lokusebenza

# Dala umkhombandlela wamafayela ewebhusayithi ayisisekelo
sudo mkdir -p /var/www/example.com
sudo chmod a+w /var/www/example.com
sudo chown -R www-data: /var/www/example.com

# Thola igama lediski, bese ulifometha bese ulifaka
DISK_NAME="google-disk-base-$NAME_SUFFIX"DISK_PATHthola /dev/disk/by-id -name DISK_NAME}"| xargs -Ireadlink -f n
sudo mkfs.ext4 -m 0 -E lazy_itable_init=0,lazy_journal_init=0,lahla $DISK_PATH
sudo mount -o lahla, okuzenzakalelayo $DISK_PATH /var/www/example.com

# Faka i-Apache
sudo apt-get update&& sudo apt-get -y faka i-apache2

# Bhala ifayela le-HTML eliyisisekelo kudiski eqhubekayo efakiwe
sudo tee -a /var/www/example.com/index.html >/dev/null EOF'



 HA / DR isibonelo


 
Siyakwamukela kuwebhusayithi ye-Compute Engine ene-failover efudumele ku-Cloud Storagep>
*:80>
 ServerName www.example.com

 ServerAdmin webmaster@localhost
 DocumentRoot /var/www/example.com

 ErrorLog ${APACHE_LOG_DIR}/error.log
 CustomLog ${APACHE_LOG_DIR}/access.log combined

EOF

# Nika amandla ifayela lokumisa le-Apache bese ulayisha kabusha isevisi
sudo a2dissite 000-okuzenzakalelayo
sudo a2ensite example.com.conf
sudo systemctl layisha kabusha i-apache2

Buyekeza i
okuguquguqukayo ukuze kufane nenani elibekwe kulo
ukuqala kwalo mbhalo, njenge

NAME_SUFFIX uhlelo lokusebenza.

Bhala ifayela bese uphuma kumhleli wakho. Isibonelo, ku-Nano usebenzisa

Ctrl-Oto bhala ifayela, bese uphuma nge
I-Ctrl-X.

Yenza iskripthi sokumisa sisebenze, bese usiqhuba:

chmod +x lungiselela-vm../configure-vm.
Phuma kusikhathi se-SSH uye ku-VM:

Phuma


Thola ikheli le-IP le-VM futhi ulisebenzise

curl ukuze ubone ikhasi lewebhu eliyisisekelo:


curl $(izimo zekhompyutha ze-gcloud zichaza i-vm-base-$NAME_SUFFIX n --zone $ZONE n --format="value(networkInterfaces.accessConfigs.[0].natIPn
Iwebhusayithi eyisisekelo ibuyiselwa, njengoba kukhonjisiwe kumphumela olandelayo oyisibonelo:








 HA / DR isibonelo


 
Siyakwamukela kuwebhusayithi ye-Compute Engine ene-failover efudumele ku-Cloud Storagep>

I-gcloud compute izithombe yenza isithombe-idiski-$NAME_SUFFIX n --source-disk=disk-base-$NAME_SUFFIX n --source-disk-zone=$ZONE

# Dala izifanekiso zesibonelo
izifanekiso zekhompyutha ze-gcloud zakha isifanekiso-$NAME_SUFFIX-$REGION1 n --machine-type=n1-standard-1 n --subnet=projects/$PROJECT_ID/regiions/$REGION1/subnetworks/subnet-$NAME_SUFFIX-$REGION1 n --region=$REGION1 n --tags=http-server n --metadatastartup-script /bin/bashn'echo\ UUIDblkid\ -s\ UUID\ -o\ value\ /dev/sdb /var/www/example. com\ ext4\ lahla,okuzenzakalelayo,akuphumeleli\ 0\ 2 ee\ -a\ /etc/fstabn'mount\ -a n --image=image-$NAME_SUFFIX n --create-disk=image=image-disk-$NAME_SUFFIX ,susa ngokuzenzakalelayo=yebo

izifanekiso zekhompyutha ze-gcloud zakha isifanekiso-$NAME_SUFFIX-$REGION2 n --machine-type=n1-standard-1 n --subnet=projects/$PROJECT_ID/regiions/$REGION2/subnetworks/subnet-$NAME_SUFFIX-$REGION2 n --region=$REGION2 n --tags=http-server n --metadatastartup-script /bin/bashn'echo\ UUIDblkid\ -s\ UUID\ -o\ value\ /dev/sdb /var/www/example. com\ ext4\ lahla,okuzenzakalelayo,akuphumeleli\ 0\ 2 ee\ -a\ /etc/fstabn'mount\ -a n --image=image-$NAME_SUFFIX n --create-disk=image=image-disk-$NAME_SUFFIX ,susa ngokuzenzakalelayo=yebo

# Dala isheke lezempilo lezimo ze-VM
i-gcloud compute health-check idala i-http-basic-check-$NAME_SUFFIX n --port 80

# Dala amaqembu esibonelo aphethwe
I-gcloud compute example-groups ilawule ukudala isibonelo-iqembu-$NAME_SUFFIX-$REGION1 n --template=template-$NAME_SUFFIX-$REGION1 n --size=2 n --region=$REGION1 n --health-check=http- isheke eliyisisekelo-$NAME_SUFFIX

I-gcloud compute example-groups ikwazile ukudala isibonelo-iqembu-$NAME_SUFFIX-$REGION2 n --template=template-$NAME_SUFFIX-$REGION2 n --size=2 n --region=$REGION2 n --health-check=http- isheke eliyisisekelo-$NAME_SUFFIX


## Dala futhi ulungiselele isilinganisi somthwalo


Ukuze abasebenzisi bafinyelele iwebhusayithi yakho, udinga ukuvumela ithrafikhi ukuthi idlulele kuma-VM
asebenza emaqenjini esibonelo aphethwe. Futhi ufuna ukuqondisa kabusha ngokuzenzakalelayo
ithrafikhi eya kuma-VM amasha uma kukhona ukwehluleka kwendawo eqenjini lesibonelo eliphethwe.


Esigabeni esilandelayo, udala i-
isilinganisi somthwalo wangaphandle
ngesevisi engemuva yethrafikhi ye-HTTP echwebeni
80, sebenzisa isheke lezempilo elidalwe ezinyathelweni ezedlule, bese ubala i-IP yangaphandle
ikheli lidlulele kusevisi yangemuva.


Ukuze uthole ukwaziswa okwengeziwe, bheka
Ungasetha kanjani isilinganisi esilula sokulayisha se-HTTP.


-

Dala futhi ulungiselele isilinganisi somthwalo sohlelo lwakho lokusebenza:

# Lungiselela imithetho yembobo ye-HTTP port 80
I-gcloud compute example-groups set-named-ports-n incident-iqembu-$NAME_SUFFIX-$REGION1 n --named-ports http:80 n --region $REGION1


i-gcloud compute example-groups set-named-ports-n incident-group-$NAME_SUFFIX-$REGION2 n --named-ports http:80 n --region $REGION2

# Dala isevisi yasemuva bese wengeza amaqembu esibonelo aphethwe kuyo
gcloud compute backend-services create n web-backend-service-$NAME_SUFFIX n --protocol=HTTP n --port-name=http n --health-checks=http-basic-check-$NAME_SUFFIX n --global

gcloud compute backend-services add-backend n web-backend-service-$NAME_SUFFIX n --instance-group=isibonelo-group-$NAME_SUFFIX-$REGION1 n --isibonelo-group-region=$REGION1 n --global

gcloud compute backend-services add-backend n web-backend-service-$NAME_SUFFIX n --instance-group=isibonelo-group-$NAME_SUFFIX-$REGION2 n --isibonelo-group-region=$REGION2 n --global

# Dala imephu ye-URL yenkonzo yasemuva
I-gcloud compute url-maps yakha i-web-map-http-$NAME_SUFFIX n --default-service web-backend-service-$NAME_SUFFIX

# Lungiselela ukudluliselwa kwethrafikhi ye-HTTP
I-gcloud compute target-http-proxies idala n http-lb-proxy-$NAME_SUFFIX n --url-map web-map-http-$NAME_SUFFIX

Imithetho ye-gcloud compute yokudlulisa-yakha n http-content-rule-$NAME_SUFFIX n --global n --target-http-proxy=http-lb-proxy-$NAME_SUFFIX n --ports=80


Thola ikheli le-IP lomthetho wokudlulisela wethrafikhi yewebhu:

I-IP_ADDRESSgcloud ikhola ukudlulisa-imithetho ichaza i-http-content-rule-$NAME_SUFFIX n --global n --format="value(IPAddressn)

Sebenzisa

curl, noma uvule isiphequluli sakho sewebhu, ukuze ubuke iwebhusayithi usebenzisa i-IP
ikheli lebhalansi yomthwalo kusukela esinyathelweni sangaphambilini:


curl $IP_ADDRESS

Kuthatha amaminithi ambalwa ukuthi isilinganisi somthwalo siqedele ukusebenzisa futhi siqede
ukuqondisa kahle ithrafikhi ku-backend yakho. Iphutha le-HTTP 404 libuyiselwa uma i
isilinganisi sokulayisha sisasebenza. Uma kudingeka, linda imizuzu embalwa bese uzama
finyelela iwebhusayithi futhi.


Iwebhusayithi eyisisekelo ibuyiselwa, njengoba kukhonjisiwe kumphumela olandelayo oyisibonelo:




 HA / DR isibonelo


 
Siyakwamukela kuwebhusayithi ye-Compute Engine ene-failover efudumele ku-Cloud Storagep>

amaqembu esibonelo aphethwe ayalulama futhi anganikeza ithrafikhi kuwebhusayithi egcwele
isipiliyoni.


-

Qinisekisa isizinda
ofuna ukulisebenzisa ngebhakede lakho Lesitoreji Samafu.

Dala ibhakede le-Cloud Storage ukuze lifane negama lesizinda sakho
futhi ufuna ukusebenzisa:



gsutil mb gsstatic-web.$DOMAIN

I
DOMAINokuguquguqukayo okuchazwe ekuqaleni kwale dokhumenti kuyasetshenziswa, njengokuthi

. Lesi sibonelo sigcina amafayela amile kokuthi

example.com
static-web.example.com.

Dala ifayela lasendaweni olikopishela ebhakedeni Lesitoreji Samafu ku
Okulandelayo:

cat< index.html




 HA / DR example


 
Welcome to a test static web server with warm failover from Cloud Storagep>





 HA / DR example


 
Welcome to a test static web server with warm failover from Cloud Storagep>


curlagain, or open your web browser, to access the IP address of the
load balancer:


curl $IP_ADDRESS

It might take a few minutes for the load balancer to update the configuration
and to correctly direct traffic back to your managed instance groups. If
needed, wait a few minutes and try to access the website again.


The main website from the managed instance groups is returned, as shown in the
following example output:





 HA / DR example


 p>Welcome to a Compute Engine website with warm failover to Cloud Storagep>




## Clean up
 


 To avoid incurring charges to your Google Cloud account for the resources used in this
 tutorial, either delete the project that contains the resources, or keep the project and
 delete the individual resources.

 
 


To delete the individual resources created in this document, complete the
following steps:


- 

Delete the Cloud Storage bucket:

gsutil rm -r gsstatic-web.$DOMAIN


Delete the load balancer configuration:

gcloud compute forwarding-rules delete n http-content-rule-$NAME_SUFFIX --global --quiet

gcloud compute target-http-proxies delete n http-lb-proxy-$NAME_SUFFIX --quiet

gcloud compute url-maps delete web-map-http-$NAME_SUFFIX --quiet

gcloud compute url-maps delete web-map-http-bucket-$NAME_SUFFIX --quiet

gcloud compute backend-services delete n web-backend-service-$NAME_SUFFIX --global --quiet

gcloud compute backend-buckets delete web-bucket-$NAME_SUFFIX --quiet


Delete the managed instance groups and health check:

gcloud compute instance-groups managed delete n instance-group-$NAME_SUFFIX-$REGION1 n --region=$REGION1 --quiet

gcloud compute instance-groups managed delete n instance-group-$NAME_SUFFIX-$REGION2 n --region=$REGION2 --quiet

gcloud compute health-checks delete http-basic-check-$NAME_SUFFIX --quiet


Delete the instance templates, images, base VM, and persistent disks:

gcloud compute instance-templates delete n template-$NAME_SUFFIX-$REGION1 --quiet

gcloud compute instance-templates delete n template-$NAME_SUFFIX-$REGION2 --quiet

gcloud compute images delete image-$NAME_SUFFIX --quiet

gcloud compute images delete image-disk-$NAME_SUFFIX --quiet

gcloud compute instances delete vm-base-$NAME_SUFFIX n --zone=$ZONE --quiet


Delete the firewall rules.

gcloud compute firewall-rules delete n allow-health-check-$NAME_SUFFIX --quiet

gcloud compute firewall-rules delete n allow-ssh-$NAME_SUFFIX --quiet

gcloud compute firewall-rules delete n allow-http-$NAME_SUFFIX --quiet


Delete the subnet and VPC.


gcloud compute networks subnets delete n subnet-$NAME_SUFFIX-$REGION1 --region=$REGION1 --quiet

gcloud compute networks subnets delete n subnet-$NAME_SUFFIX-$REGION2 --region=$REGION2 --quiet

gcloud compute networks delete network-$NAME_SUFFIX --quiet


## What's next
 


- 

- For an alternative approach that uses Cloud DNS instead of external
HTTP(S) Load Balancing to control the failover, see
Deploy a warm recoverable web server using Cloud DNS with Compute Engine and Cloud Storage.
This pattern is useful if you have, or want to use, Cloud DNS. 

- To learn how how to determine the best approach for your own applications and
which recovery method to use, see the
Disaster recovery planning guide. 

- To see other patterns for applications, such as cold and hot failover, see
Disaster recovery scenarios for applications. 

- For more ways to handle scale and availability, see the
Patterns for scalable and resilient apps. 

- 

Explore reference architectures, diagrams, tutorials, and best practices about Google Cloud.
Take a look at our
Cloud Architecture Center.