Hlaziya!. Kwizimvo, omnye wabafundi ucebise ukuba kuzanywe (mhlawumbi usebenza kuyo ngokwakhe) ngoko ndongeze icandelo malunga nesi sisombululo. Ndabhala nam , kuba inkqubo ihluke kakhulu kwabanye.
Xa ndithetha inyani ndancama ndancama (ubuncinci okwangoku). Ndiza kusebenzisa . Ngoba? Ngenxa yokugcina! Ngubani owayenokucinga ukuba ndiza kujonga ngakumbi ngogcino kuneKubernetes ngokwayo. ndisebenzise kuba ayibizi kwaye ukusebenza kuhle kwaye kwasekuqaleni bendithumela amaqela ndisebenzisa . Andizange ndizame iinkonzo ezilawulwayo zeKubernetes ezivela kuGoogle/Amazon/Microsoft/DigitalOcean, njl., njl., kuba ndandifuna ukufunda yonke into ngokwam. Ndiyayonga.
Ke ewe, ndichithe ixesha elininzi ndizama ukugqiba ukuba yeyiphi indawo yokugcina endinokuyikhetha xa ndivavanya istaki se-Kubernetes esinokwenzeka. Ndikhetha izisombululo zemithombo evulekileyo, kungekuphela ngenxa yexabiso, kodwa ndiye ndajonga kwiinketho ezimbalwa ezihlawulweyo ngenxa yomdla kuba zineenguqulelo zasimahla ezinemida. Ndibhale phantsi amanye amanani kuvavanyo lwamva nje xa ndithelekisa iinketho ezahlukeneyo, kwaye zinokuba nomdla kwabo bafunda malunga nokugcinwa kweKubernetes. Nangona ndithe ndohlukana noKubernetes okwangoku. Nam ndifuna ukukhankanya , enokubonelela ngokuthe ngqo imiqulu ye-Hetzner Cloud, kodwa andikayizama okwangoku. Ndajonga kwi-software-echazwe kwi-software echazwe kwi-software kuba ndifuna ukuphindaphinda kunye nokukwazi ukunyusa ngokukhawuleza iivolumu eziqhubekayo kuyo nayiphi na indawo, ngakumbi xa kukho ukusilela kwe-node kunye nezinye iimeko ezifanayo. Ezinye izisombululo zibonelela nge-point-in-time snapshots kunye ne-off-site backups, efanelekileyo.
Ndivavanye izisombululo ze-6-7 zokugcina:
Njengoko besenditshilo Emva kokuvavanya uninzi lweenketho kuluhlu, ndahlala ndahlala kwi-OpenEBS. I-OpenEBS ilula kakhulu ukuyifaka kunye nokusetyenziswa, kodwa ukunyaniseka, emva kokuvavanya ngedatha yangempela phantsi komthwalo, ndaphoxeka ngokusebenza kwayo. Lo ngumthombo ovulekileyo, kwaye abaphuhlisi babodwa soloko ndiluncedo kakhulu xa ndifuna uncedo. Ngelishwa, inokusebenza kakubi kakhulu xa kuthelekiswa nezinye iinketho, ngoko ke iimvavanyo kwafuneka ziqhutywe kwakhona. I-OpenEBS okwangoku ineenjini zokugcina ezi-3, kodwa ndithumela iziphumo zebenchmark ye-cStor. Andinazo iinombolo zeJiva nezeLocalPV okwangoku.
Ngamafutshane, iJiva ikhawuleza kancinci, kwaye iLocalPV iyakhawuleza ngokubanzi, akukho mbi kunedisk benchmark ngokuthe ngqo. Ingxaki nge-LocalPV kukuba umthamo ungafumaneka kuphela kwi-node apho ulungiswe khona, kwaye akukho kuphindaphinda konke. Ndibe neengxaki zokubuyisela i-backup nge kwiqela elitsha kuba amagama eendawo zokuhlala ahlukile. Ukuba sithetha ngee-backups, i-cStor ine , apho unokwenza i-backups ye-off-site ye-snapshots ngexesha elithile, elilungele ngakumbi kune-file-level backups kunye ne-Velero-Restic. Ndabhala , ukwenza kube lula ukulawula ii-backups kunye nokubuyisela ngale plugin. Ngokubanzi, ndiyithanda kakhulu i-OpenEBS, kodwa ukusebenza kwayo ...
I-Rook iphinde ibe ngumthombo ovulekileyo kwaye ihluke kwezinye iinketho kuluhlu ngokuba yi-orchestrator yokugcina eyenza imisebenzi enzima yokulawula ukugcinwa kunye ne-backends eyahlukeneyo, umz. , kunye nezinye, eziwenza lula umsebenzi. Ndineengxaki nge-EfgeFS xa ndizama kwiinyanga ezimbalwa ezidlulileyo, ngoko ndavavanya kakhulu ngeCeph. I-Ceph ayinikezeli kuphela ukugcinwa kwebhloko, kodwa kunye nokugcinwa kwezinto ezihambelana ne-S3 / Swift kunye nenkqubo yefayile esasazwayo. Into endiyithandayo ngeCeph kukukwazi ukusasaza idatha yevolumu kwiidiski ezininzi ukuze umthamo usebenzise indawo yedisk eninzi kunokuba inokungena kwidiski enye. Ikhululekile. Enye into epholileyo kukuba xa usongeza iidiski kwiqela, isasaza ngokuzenzekelayo idatha kuzo zonke iidiski.
I-Ceph inee-snapshots, kodwa ngokokwazi kwam, ayinakusetyenziswa ngokuthe ngqo eRook/Kubernetes. Enyanisweni, andizange ndingene nzulu kule nto. Kodwa akukho zi-backups ezingaphandle kwendawo, ke kuya kufuneka usebenzise into ngeVelero / Restic, kodwa kukho kuphela i-backups yenqanaba lefayile, hayi i-snapshots yexesha. Eyona nto bendiyithanda kakhulu ngeRook yindlela ekulula ngayo ukusebenza noCeph - ifihla phantse zonke izinto ezintsonkothileyo kwaye ibonelela ngezixhobo zokuthetha noCeph ngokuthe ngqo ukulungisa ingxaki. Ngelishwa, ngexesha lovavanyo loxinzelelo lwemiqulu yeCeph, ndahlala ndineengxaki , ebangela ukuba uCeph angazinzi. Akukacaci ukuba le yimpazamo kwiCeph ngokwayo okanye yingxaki kwindlela uRook alawula ngayo iCeph. Ndikhe ndajongana nesetingi yememori, kwaye yabangcono, kodwa ingxaki ayizange isombululwe ngokupheleleyo. I-Ceph inentsebenzo efanelekileyo, njengoko ubona kwiibhentshi ezingezantsi. Ikwanayo nedeshibhodi elungileyo.
Ndiyithanda kakhulu iLonghorn. Ngokombono wam, esi sisisombululo esithembisayo. Enyanisweni, abaphuhlisi ngokwabo (iRancher Labs) bayavuma ukuba ayikafaneli indawo yokusebenza, kwaye oku kubonisa. Ingumthombo ovulekileyo kwaye inentsebenzo ehloniphekileyo (nangona bengekayiphuculi okwangoku), kodwa imiqulu ithatha ixesha elide ukuxhuma kwi-pod, kwaye kwiimeko ezimbi kakhulu kuthatha imizuzu eyi-15-16, ngakumbi emva kokubuyisela i-backup enkulu okanye ukuphucula umthwalo womsebenzi. Inee-snapshots kunye ne-off-site ye-backups yezi snapshots, kodwa isebenza kuphela kwimiqulu, ke uya kudinga into efana neVelero ukugcina ezinye izixhobo. Ii-backups kunye nokubuyisela zithembeke kakhulu, kodwa zicotha ngokungafanelekanga. Ngokunyanisekileyo, ngokukhawuleza ngokumangalisayo. Ukusetyenziswa kwe-CPU kunye nomthwalo wenkqubo uhlala unyuka xa usebenza ngesixa esiphakathi sedatha eLonghorn. Kukho ideshibhodi efanelekileyo yokulawula iLonghorn. Sele nditshilo ukuba ndiyayithanda iLonghorn, kodwa idinga umsebenzi othile.
I-StorageOS yimveliso yokuqala ehlawulweyo kuluhlu. Inenguqulo yomphuhlisi enobungakanani obulinganiselweyo bokugcina obulawulwayo be-500GB, kodwa andicingi ukuba kukho umda kwinani leendawo. Isebe lokuthengisa lindixelele ukuba iindleko ziqala kwi-$ 125 ngenyanga kwi-TB ye-1, ukuba ndikhumbula ngokuchanekileyo. Kukho ideshibhodi esisiseko kunye ne-CLI efanelekileyo, kodwa kukho into engaqhelekanga eqhubekayo ngokusebenza: kwezinye iibenchmarks ilungile, kodwa kuvavanyo loxinzelelo lwevolumu andizange ndisithande isantya kwaphela. Ngokubanzi, andazi ukuba ndithini. Ngoko andizange ndiqonde nto ingako. Akukho zi-backups ezingaphandle kwesiza apha kwaye kuya kufuneka usebenzise iVelero ene-Restic kwi-backup volumes. Kuyamangalisa, kuba imveliso ihlawulwe. Kwaye abaphuhlisi bebengafuni ukunxibelelana kwi-Slack.
Ndafunda ngoRobin kwiReddit kumlawuli wabo wezobugcisa. Ndandiqala ukuva ngaye. Mhlawumbi ngenxa yokuba ndikhangele izisombululo zamahhala, kodwa uRobin uhlawulwa. Banesisa esihle kakhulu sasimahla kunye ne-10TB yokugcina kunye neenodi ezintathu. Ngokubanzi, imveliso inesidima kwaye ineempawu ezintle. Kukho i-CLI enkulu, kodwa eyona nto ibanda kakhulu kukuba unokufota kwaye ukhuphele isicelo sonke (kumkhethi wesixhobo oku kubizwa ngokuba kukukhutshwa kwe-Helm okanye "ii-apps eziguqukayo"), kubandakanya imiqulu kunye nezinye izixhobo, ukuze ukwazi ukwenza ngaphandle kweVelero. Kwaye yonke into iya kuba yinto emangalisayo ukuba ingabikho kwiinkcukacha ezincinci: ukuba ubuyisela (okanye "ukungenisa", njengoko kubizwa ngokuba yiRobin) isicelo kwiqela elitsha - umzekelo, kwimeko yokubuyisela kwintlekele - ukubuyisela, kunjalo, iyasebenza, kodwa qhubeka ugcino lwesicelo akuvumelekanga. Oku akunakwenzeka kolu kukhutshwa, njengoko abaphuhlisi beqinisekisile. Oku, ukuyibeka ngobumnene, engaqhelekanga, ngakumbi ukuqwalasela ezinye izibonelelo (umzekelo, ukugcinwa ngokukhawuleza okumangalisayo kunye nokubuyisela). Abaphuhlisi bathembisa ukulungisa yonke into ngokukhululwa okulandelayo. Ukusebenza ngokuqhelekileyo kulungile, kodwa ndiqaphele into engaqhelekanga: ukuba ndiqhuba ibhentshimakhi ngokuthe ngqo kwivolumu encanyathiselwe kumsingathi, isantya sokufunda sikhawuleza kakhulu kunokusebenzisa umthamo ofanayo ngaphakathi kwepod. Zonke ezinye iziphumo ziyafana, kodwa kwithiyori akufanele kubekho mahluko. Nangona basebenza kuyo, ndandicaphukile malunga nengxaki yokubuyisela kunye ne-backup - ndacinga ukuba ekugqibeleni ndifumene isisombululo esifanelekileyo, kwaye ndandikulungele ukuyihlawula xa ndifuna indawo engaphezulu okanye iiseva ezingaphezulu.
Andinanto ininzi endinoyithetha apha. Le yimveliso ehlawulwayo, ipholile ngokulinganayo kwaye iyabiza. Ukusebenza kuyamangalisa. Esi sesona salathisi singcono ukuza kuthi ga ngoku. USlack undixelele ukuba amaxabiso aqala kwi-205 yeedola ngenyanga kwindawo nganye, njengoko kudweliswe kwindawo yeMarike ye-GKE kaGoogle. Andazi ukuba kuya kuba cheap xa uthenga ngqo. Andinakukwazi ukuyihlawula loo nto, ndiye ndaphoxeka kakhulu kukuba ilayisenisi yomphuhlisi (ukuya kuthi ga kwi-TB enye kunye ne-1 nodes) ayinamsebenzi nge-Kubernetes ngaphandle kokuba wanelisekile kukubonelela okuzinzileyo. Bendinethemba lokuba ilayisenisi yevolyum izakuthoba ngokuzenzekelayo ibe ngumphuhlisi ekupheleni kwexesha lovavanyo, kodwa akwenzekanga oko. Ilayisensi yomphuhlisi inokusetyenziswa kuphela ngokuthe ngqo kwi-Docker, kwaye uqwalaselo kwi-Kubernetes lunzima kakhulu kwaye lulinganiselwe. Ewe, ndikhetha umthombo ovulekileyo, kodwa ukuba bendinemali, ngokuqinisekileyo bendiya kukhetha iPortworx. Ukuza kuthi ga ngoku, ukusebenza kwayo akufani nokuthelekisa nezinye iinketho.
Ndongeze eli candelo emva kokupapashwa kweposi, xa omnye umfundi ecebisa ukuzama uLinstor. Ndizamile kwaye ndayithanda! Kodwa kusafuneka sembe nzulu. Ngoku ndingatsho ukuba ukusebenza akubi (ndongeze iziphumo zebenchmark engezantsi). Ngokusisiseko, ndifumene ukusebenza okufanayo njengediski ngokuthe ngqo, ngaphandle kokungaphezulu. (Musa ukubuza ukuba kutheni i-Portworx inamanani angcono kune-benchmark ye-drive ngokuthe ngqo. Andinayo ingcamango. Umlingo, ndiyaqikelela.) Ngoko uLinstor ubonakala esebenza kakhulu ngoku. Akunzima ukuyifaka, kodwa akukho lula njengezinye iinketho. Okokuqala kwafuneka ndifake i-Linstor (imodyuli ye-kernel kunye nezixhobo / iinkonzo) kwaye uqwalasele i-LVM yokubonelela okuncinci kunye nenkxaso ye-snapshot ngaphandle kwe-Kubernetes, ngokuthe ngqo kwi-host host, kwaye emva koko udale izixhobo ezifunekayo ukusebenzisa ukugcinwa kwi-Kubernetes. Andizange ndithande ukuba ingasebenzi kwi-CentOS kwaye kwafuneka ndisebenzise Ubuntu. Ayiyoyiki, kunjalo, kodwa iyacaphukisa, kuba uxwebhu (olubalaseleyo, ngendlela) lukhankanya iipakethe ezininzi ezingafumanekiyo kwiindawo zokugcina ze-Epel. I-Linstor ine-snapshots, kodwa ingekho kwi-backups yendawo, ke apha kwakhona kuye kwafuneka ndisebenzise i-Velero ene-Restic kwi-backup volumes. Ndingathanda ii-snapshots endaweni ye-file-level backups, kodwa oku kunokunyamezela ukuba isisombululo siyasebenza kwaye sithembekile. I-Linstor ngumthombo ovulekileyo kodwa uhlawule inkxaso. Ukuba ndiyaqonda ngokuchanekileyo, inokusetyenziswa ngaphandle kwezithintelo, nangona ungenayo inkontileka yenkxaso, kodwa oku kufuneka kucaciswe. Andazi ukuba i-Linstor ivavanywe njani i-Kubernetes, kodwa i-store layer ngokwayo ingaphandle kwe-Kubernetes kwaye, ngokucacileyo, isisombululo asizange sivele izolo, ngoko mhlawumbi sele ivavanyiwe kwiimeko zangempela. Ngaba kukho isisombululo apha esiya kundenza nditshintshe ingqondo kwaye ndibuyele eKubernetes? Andazi. Kusafuneka sembe nzulu kwaye sifunde ukuphindaphinda. Masibone. Kodwa umbono wokuqala ulungile. Ngokuqinisekileyo ndingathanda ukusebenzisa eyam i-Kubernetes amaqela endaweni ye-Heroku ukuze ndibe nenkululeko engakumbi kwaye ndifunde izinto ezintsha. Ekubeni i-Linstor ayilula ukuyifaka njengabanye, ndiya kubhala isithuba malunga nayo kungekudala.
Iimpawu zokuthelekisa
Ngelishwa, andizange ndigcine amanqaku amaninzi malunga nothelekiso kuba andizange ndicinge ukuba ndingabhala ngayo. Ndineziphumo kuphela ukusuka kwiibenchmarks zefio ezisisiseko kwaye kuphela kumaqela eendawo enye kuphela, ngoko ke andinawo amanani ohlengahlengiso oluphindiweyo okwangoku. Kodwa kwezi ziphumo unokufumana umbono ongalunganga wokuba ulindele ntoni kukhetho ngalunye, kuba ndibathelekise kwiiseva ezifanayo zelifu, ii-cores ezi-4, i-16 GB ye-RAM, kunye nediski eyongezelelweyo ye-100 yemithamo evavanyiweyo. Ndiqhube i-benchmarks kathathu kwisisombululo ngasinye kwaye ndibala umphumo oqhelekileyo, kunye nokusetha kwakhona izicwangciso zeseva kwimveliso nganye. Konke oku akuhambelani nenzululwazi ngokupheleleyo, ukukunika nje umbono jikelele. Kwezinye iimvavanyo, ndikhuphe i-38 GB yeefoto kunye namavidiyo ukusuka kwivolumu ukuvavanya ukufunda nokubhala, kodwa, maye, andizange ndigcine amanani. Ngokufutshane: IPortworkx yayikhawuleza kakhulu.
Kwibenchmark yevolumu ndisebenzise lo mboniso:
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
name: dbench
spec:
storageClassName: ...
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 5Gi
---
apiVersion: batch/v1
kind: Job
metadata:
name: dbench
spec:
template:
spec:
containers:
- name: dbench
image: sotoaster/dbench:latest
imagePullPolicy: IfNotPresent
env:
- name: DBENCH_MOUNTPOINT
value: /data
- name: FIO_SIZE
value: 1G
volumeMounts:
- name: dbench-pv
mountPath: /data
restartPolicy: Never
volumes:
- name: dbench-pv
persistentVolumeClaim:
claimName: dbench
backoffLimit: 4Ndaqala ndadala ivolumu kunye neklasi yokugcina efanelekileyo kwaye ndaqhuba umsebenzi kunye ne-fio emva kweemifanekiso. Ndithathe i-1 GB ukuqikelela ukusebenza kwaye ndingalindeli ixesha elide. Nazi iziphumo:
Ndiphawule elona xabiso lemetric nganye eluhlaza kunye nelona libi kakhulu libomvu.
isiphelo
Njengoko ubona, kwiimeko ezininzi iPortworx iqhube ngcono kunezinye. Kodwa kum kuyabiza. Andazi ukuba zingakanani iindleko zeRobin, kodwa zinenguqu enkulu yamahhala, ngoko ke ukuba ufuna imveliso ehlawulwayo, unokuzama (ngethemba lokuba bayayilungisa ingxaki ngokubuyisela kunye nokugcinwa kwe-backups ngokukhawuleza). Kwezithathu zasimahla, bendineengxaki ezincinci nge-OpenEBS, kodwa ukusebenza kwayo kubi. Kubuhlungu ukuba andigcinanga iziphumo ezininzi, kodwa ndiyathemba ukuba amanani kunye nezimvo zam ziyakunceda.
umthombo: www.habr.com