{"id":38542,"date":"2019-10-31T22:24:25","date_gmt":"2019-10-31T19:24:25","guid":{"rendered":"https:\/\/prohoster.info\/blog\/giperkonvergentnoe-reshenie-aerodisk-vair-osnova-fajlovaya-sistema-ardfs\/"},"modified":"2019-10-31T22:24:25","modified_gmt":"2019-10-31T19:24:25","slug":"giperkonvergentnoe-reshenie-aerodisk-vair-osnova-fajlovaya-sistema-ardfs","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/giperkonvergentnoe-reshenie-aerodisk-vair-osnova-fajlovaya-sistema-ardfs","title":{"rendered":"Zgjidhja hiper-konvergjente AERODISK vAIR. Thelbi \u2014 sistemi i skedar\u00ebve ARDFS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Zgjidhja<\/p>\n

<\/p>\n

P\u00ebrsh\u00ebndetje, lexues t\u00eb Habr\u00ebs. Me k\u00ebt\u00eb artikull hapim nj\u00eb cik\u00ebl q\u00eb do t\u00eb flas\u00eb p\u00ebr sistemin hiper-konvergjent AERODISK vAIR t\u00eb zhvilluar nga ne. Fillimisht donim q\u00eb me artikullin e par\u00eb t\u00eb flisnim gjith\u00e7ka rreth gjith\u00e7kaje, por sistemi \u00ebsht\u00eb mjaft kompleks, k\u00ebshtu q\u00eb do ta ham\u00eb elefantin p\u00ebr copa. <\/p>\n

<\/p>\n

Le t\u00eb fillojm\u00eb historin\u00eb me krijimin e sistemit, t\u00eb thellohemi n\u00eb sistemin e skedar\u00ebve ARDFS, i cili \u00ebsht\u00eb baza e vAIR, dhe gjithashtu t\u00eb diskutojm\u00eb pak mbi pozicionimin e k\u00ebtij zgjidhjeje n\u00eb tregun rus. <\/p>\n

<\/p>\n

N\u00eb artikujt e m\u00ebvonsh\u00ebm do t\u00eb flasim m\u00eb holl\u00ebsisht p\u00ebr komponent\u00ebt e ndrysh\u00ebm arkitekturor\u00eb (klaster, hiperparalelizues, balancues ngarkese, sistem monitorimi etj.), procesin e konfigurimit, do t\u00eb ngrem\u00eb pyetje mbi licencimin, do t\u00eb tregojm\u00eb ndarjen e testeve t\u00eb d\u00ebshtimit dhe, natyrisht, do t\u00eb shkruajm\u00eb p\u00ebr testimin e ngarkes\u00ebs dhe dimensionimin. Po ashtu, do t\u2019i dedikojm\u00eb nj\u00eb artikull ve\u00e7mas versionit komunitar t\u00eb vAIR.<\/p>\n

<\/a><\/noindex><\/p>\n

A \u00ebsht\u00eb AERODISK nj\u00eb lloj historie rreth sistemeve t\u00eb ruajtjes? Apo pse kemi filluar t\u00eb merremi me hiper-konvergjenc\u00ebn?<\/h2>\n

<\/p>\n

Fillimi i ide\u00ebs p\u00ebr t\u00eb krijuar nj\u00eb hiper-konsolidim na erdhi diku rreth vitit 2010. At\u00ebher\u00eb nuk kishte as Aerodisk dhe as zgjidhje t\u00eb ngjashme (sisteme komerciale hiper-konsolidimi) n\u00eb treg. Detyra jon\u00eb ishte si vijon: nga nj\u00eb grup serverash me disqe lokale, t\u00eb bashkuar me interkonnektin p\u00ebrmes protokollit Ethernet, duhej t\u00eb krijonim nj\u00eb depot t\u00eb shtrir\u00eb dhe t\u00eb nisnim aty makinat virtuale dhe rrjetin e programit. K\u00ebto k\u00ebrkesa duhej t\u00eb realizoheshin pa SAN (sepse nuk kishte para p\u00ebr SAN dhe lidhjet e saja, dhe ne ende nuk e kishim shpikur SAN-n\u00eb ton\u00eb).<\/p>\n

<\/p>\n

Provova shum\u00eb zgjidhje open source dhe megjithat\u00eb e zgjidh\u00ebm k\u00ebt\u00eb detyr\u00eb, por zgjidhja ishte shum\u00eb e nd\u00ebrlikuar dhe e v\u00ebshtir\u00eb p\u00ebr t'u p\u00ebrs\u00ebritur. P\u00ebr m\u00eb tep\u00ebr, kjo zgjidhje ishte nj\u00eb nga ato 'Punon? Mos e prek!'. Prandaj, pasi e zgjidh\u00ebm k\u00ebt\u00eb detyr\u00eb, nuk vazhduam m\u00eb me iden\u00eb p\u00ebr ta kthyer rezultatin e pun\u00ebs son\u00eb n\u00eb nj\u00eb produkt t\u00eb plot\u00eb. <\/p>\n

<\/p>\n

Pas atij rasti, ne u t\u00ebrhoq\u00ebm nga kjo ide, por ndiheshim akoma se kjo detyr\u00eb ishte n\u00eb t\u00eb v\u00ebrtet\u00eb e zgjidhshme dhe p\u00ebrfitimi nga nj\u00eb zgjidhje e till\u00eb ishte m\u00eb shum\u00eb se i duksh\u00ebm. M\u00eb pas, produktet HCI t\u00eb kompanive nd\u00ebrkomb\u00ebtare e konfirmuan k\u00ebt\u00eb ndjenj\u00eb. <\/p>\n

<\/p>\n

Prandaj, n\u00eb mes t\u00eb vitit 2016, u rikthyem n\u00eb k\u00ebt\u00eb projekt si pjes\u00eb e krijimit t\u00eb nj\u00eb produkti t\u00eb plot\u00eb. At\u00ebher\u00eb nuk kishim marr\u00ebdh\u00ebnie me investitor\u00ebt, k\u00ebshtu q\u00eb na duhej t\u00eb blinim stend\u00ebn e zhvillimit me parat\u00eb tona t\u00eb pakta. Duke renditur server\u00eb dhe switch-e t\u00eb p\u00ebrdorura n\u00eb Avito, e nisa pun\u00ebn.<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

Detyra kryesore fillestare ishte krijimi i nj\u00eb sistemi t\u00eb skedave, ndon\u00ebse t\u00eb thjesht\u00eb, por t\u00eb vetin, q\u00eb do t\u00eb ishte n\u00eb gjendje t\u00eb shp\u00ebrndante automatikisht dhe n\u00eb m\u00ebnyr\u00eb uniforme t\u00eb dh\u00ebnat n\u00eb form\u00ebn e blloqeve virtual\u00eb n\u00eb nj\u00eb num\u00ebr n-nodesh t\u00eb klasterit, t\u00eb cilat jan\u00eb t\u00eb lidhura me interkoneksionin p\u00ebrmes Ethernet-it. Po ashtu, Sistemi i Skedave duhet t\u00eb ishte i shkall\u00ebzuar mir\u00eb dhe leht\u00ebsisht, dhe t\u00eb ishte i pavarur nga sistemet p\u00ebrkat\u00ebse, pra t\u00eb ishte i ndar\u00eb nga vAIR si 'thjesht nj\u00eb depo'.<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

Koncepsioni i par\u00eb i vAIR<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

Ne vendos\u00ebm q\u00eb t\u00eb heqim dor\u00eb nga p\u00ebrdorimi i zgjidhjeve open source t\u00eb gatshme p\u00ebr organizimin e nj\u00eb ruajtjeje t\u00eb shp\u00ebrndara (si ceph, gluster, lustre dhe t\u00eb ngjashme) n\u00eb favor t\u00eb zhvillimit ton\u00eb, pasi kishim p\u00ebrvoj\u00eb t\u00eb konsiderueshme me to. Pa dyshim, k\u00ebto zgjidhje vet\u00eb jan\u00eb fantastike, dhe para pun\u00ebs mbi Aerodisk, kemi realizuar disa projekte integruese me to. Por \u00ebsht\u00eb nj\u00eb gj\u00eb t\u00eb realizosh nj\u00eb detyr\u00eb specifike p\u00ebr nj\u00eb klient, t\u00eb trajnojosh staf dhe ndoshta t\u00eb blesh mb\u00ebshtetje nga nj\u00eb ofrues i madh, dhe \u00ebsht\u00eb nj\u00eb gj\u00eb krejt tjet\u00ebr t\u00eb krijosh nj\u00eb produkt t\u00eb leht\u00eb p\u00ebr t'u shp\u00ebrndar\u00eb q\u00eb do t\u00eb p\u00ebrdoret p\u00ebr detyra t\u00eb ndryshme, p\u00ebr t\u00eb cilat si ofrues ndoshta as vet\u00eb nuk do t\u00eb dim\u00eb. P\u00ebr k\u00ebt\u00eb q\u00ebllim t\u00eb dyt\u00eb, produktet ekzistuese open source nuk ishin t\u00eb p\u00ebrshtatshme p\u00ebr ne, prandaj vendos\u00ebm ta zhvillojm\u00eb sistemin e skedar\u00ebve t\u00eb shp\u00ebrndar\u00eb vet\u00eb.
\nPas dy vitesh, p\u00ebrmes disa zhvilluesve (t\u00eb cil\u00ebt kombinonin pun\u00ebn mbi vAIR me pun\u00ebn mbi sistemin klasik t\u00eb ruajtjes Engine) arrit\u00ebm nj\u00eb rezultat t\u00eb caktuar.<\/p>\n

<\/p>\n

Deri n\u00eb vitin 2018, ne krijuam nj\u00eb sistem t\u00eb thjesht\u00eb skedar\u00ebsh dhe e plot\u00ebsuam at\u00eb me lidhjet e nevojshme. Sistemi bashkonte disk\u00ebt fizik\u00eb (lokal\u00eb) nga server\u00eb t\u00eb ndrysh\u00ebm n\u00eb nj\u00eb rezervuar t\u00eb shesht\u00eb p\u00ebrmes interkonnektit t\u00eb brendsh\u00ebm dhe i ndante ata n\u00eb blloqe virtuale, nga t\u00eb cilat krijoheshin pajisje bllokues me nj\u00eb far\u00eb niveli t\u00eb q\u00ebndrueshm\u00ebris\u00eb, n\u00eb t\u00eb cilat me ndihm\u00ebn e hipervizorit KVM krijoheshin dhe ekzekutoheshin makinat virtuale. <\/p>\n

<\/p>\n

Ne nuk u shqet\u00ebsuam shum\u00eb p\u00ebr emrin e sistemit t\u00eb skedar\u00ebve dhe e quajt\u00ebm thjesht ARDFS (merrni nj\u00eb guess se \u00e7far\u00eb do t\u00eb thot\u00eb))<\/p>\n

<\/p>\n

Ky prototip duket i mir\u00eb (n\u00eb sensin e performanc\u00ebs, jo n\u00eb aspektin vizual, pasi ende nuk kishte paraqitje vizuale) dhe tregoi rezultate t\u00eb mira n\u00eb performanc\u00eb dhe shkall\u00ebzim. Pas rezultatit t\u00eb par\u00eb realist, ne e vazhduam k\u00ebt\u00eb projekt, duke organizuar nj\u00eb mjedis t\u00eb plot\u00eb zhvillimi dhe nj\u00eb ekip t\u00eb ve\u00e7ant\u00eb q\u00eb merrej vet\u00ebm me vAIR-in.<\/p>\n

<\/p>\n

Ateher\u00eb, arkitektura e p\u00ebrgjithshme e zgjidhjes ishte pjekur, e cila ende nuk ka p\u00ebsuar ndryshime t\u00eb r\u00ebnd\u00ebsishme.<\/p>\n

<\/p>\n

T\u00eb zhytim n\u00eb sistemin e skedar\u00ebve ARDFS<\/h2>\n

<\/p>\n

ARDFS \u00ebsht\u00eb themeli i vAIR, i cili siguron ruajtjen e shp\u00ebrndar\u00eb dhe t\u00eb q\u00ebndrueshme t\u00eb t\u00eb dh\u00ebnave p\u00ebr t\u00eb gjith\u00eb klasterin. Nj\u00eb nga (por jo e vetmja) ve\u00e7ori e dallueshme e ARDFS \u00ebsht\u00eb se ai nuk p\u00ebrdor asnj\u00eb i server\u00ebve t\u00eb dedikuar<\/a> n\u00ebn menaxhim dhe kontroll. Kjo ishte menduar fillimisht p\u00ebr t\u00eb thjeshtuar konfigurimin e zgjidhjes dhe p\u00ebr besueshm\u00ebrin\u00eb e saj. <\/p>\n

<\/p>\n

Struktura e ruajtjes<\/h3>\n

<\/p>\n

N\u00eb t\u00eb gjitha nodet e klasterit, ARDFS organizon nj\u00eb rezervuar logjik nga t\u00eb gjitha hap\u00ebsirat e diskut t\u00eb disponuesh\u00ebm. \u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb kuptohet se rezervuari nuk jan\u00eb ende t\u00eb dh\u00ebnat dhe as hap\u00ebsira e formatizuar, por thjesht nj\u00eb sh\u00ebnim, pra \u00e7do nod me vAIR t\u00eb instaluar, kur shtohet n\u00eb klaster, automatikisht shtohet n\u00eb rezervuarin e p\u00ebrbashk\u00ebt ARDFS dhe burimet e diskut automatizohen b\u00ebhen t\u00eb p\u00ebrbashk\u00ebta p\u00ebr t\u00eb gjith\u00eb klasterin (dhe t\u00eb disponueshme p\u00ebr ruajtjen e t\u00eb dh\u00ebnave n\u00eb t\u00eb ardhmen). Ky qasje lejon q\u00eb nodet t\u00eb shtohen dhe hiqen n\u00eb fluk t\u00eb pa pasur ndonj\u00eb ndikim t\u00eb r\u00ebnd\u00ebsish\u00ebm n\u00eb sistemin q\u00eb \u00ebsht\u00eb duke funksionuar tashm\u00eb. Pra, sistemi \u00ebsht\u00eb shum\u00eb i leht\u00eb p\u00ebr t'u zgjeruar n\u00eb m\u00ebnyr\u00eb \u201dnd\u00ebrtesash\u201d, duke shtuar ose hequr nodet n\u00eb klaster sipas nevoj\u00ebs.<\/p>\n

<\/p>\n

Mbi grupin ARDFS shtohen disqet virtual\u00eb (objekte ruajtjeje p\u00ebr virtualizim), t\u00eb cilat nd\u00ebrtohen nga blloqe virtuale me madh\u00ebsi 4 megabajt. T\u00eb dh\u00ebnat ruhen drejtp\u00ebrdrejt n\u00eb disqet virtual\u00eb. N\u00eb nivelin e disqeve virtual\u00eb p\u00ebrcaktohet gjithashtu nj\u00eb skem\u00eb p\u00ebr q\u00ebndrueshm\u00ebrin\u00eb ndaj d\u00ebshtimeve. <\/p>\n

<\/p>\n

Si\u00e7 mund t\u00eb ishte kuptuar tashm\u00eb, p\u00ebr q\u00ebndrueshm\u00ebrin\u00eb e n\u00ebn-sistemit t\u00eb disqeve ne nuk p\u00ebrdorim konceptin RAID (Grupi i disqeve t\u00eb pavarur), por p\u00ebrdorim RAIN (Grupi i n\u00ebnndeshk\u00ebve t\u00eb pavarur). K\u00ebtu, q\u00ebndrueshm\u00ebria matet, automatizohet dhe menaxhohet duke u bazuar n\u00eb n\u00ebnndeshk\u00eb, jo n\u00eb disqe. Disqet, pa dyshim, jan\u00eb gjithashtu objekte ruajtjeje; ato, ashtu si gjith\u00e7ka tjet\u00ebr, monitorohen dhe mund t\u00eb kryhen t\u00eb gjitha operacionet standarde, p\u00ebrfshir\u00eb krijimin e nj\u00eb RAID lokal t\u00eb harduerit, por klasteri menaxhon pik\u00ebrisht n\u00ebnndeshk\u00eb. <\/p>\n

<\/p>\n

N\u00eb nj\u00eb situat\u00eb kur d\u00ebshira p\u00ebr RAID \u00ebsht\u00eb shum\u00eb e madhe (p.sh., nj\u00eb skenar q\u00eb mb\u00ebshtet d\u00ebshtime t\u00eb shumta n\u00eb klaster t\u00eb vogla), asgj\u00eb nuk e pengon p\u00ebrdorimin e kontrolleve RAID lokale, nd\u00ebrsa sip\u00ebr mund t\u00eb krijohet ruajtje e zgjatur dhe nj\u00eb arkitektur\u00eb RAIN. Ky skenar \u00ebsht\u00eb plot\u00ebsisht i vlefsh\u00ebm dhe mb\u00ebshtetet nga ne, prandaj ne do ta diskutojm\u00eb at\u00eb n\u00eb artikullin ton\u00eb mbi skenar\u00ebt tipik\u00eb t\u00eb p\u00ebrdorimit vAIR.<\/p>\n

<\/p>\n

Skemat e q\u00ebndrueshm\u00ebris\u00eb s\u00eb ruajtjes<\/h3>\n

<\/p>\n

Ka dy skema q\u00ebndrueshm\u00ebrie p\u00ebr disqet virtuale n\u00eb vAIR:<\/p>\n

<\/p>\n

1) Faktor i replikimit ose thjesht replikimi \u2013 ky metod p\u00ebr q\u00ebndrueshm\u00ebri \u00ebsht\u00eb i thjesht\u00eb \"si nj\u00eb shkop dhe nj\u00eb tel\". Kryhet replikimi sinhron midis node-ve me faktor 2 (2 kopje n\u00eb klaster) ose 3 (3 kopje, p\u00ebrkat\u00ebsisht). RF-2 lejon diskun virtual t\u00eb mbaj\u00eb d\u00ebshtimin e nj\u00eb node n\u00eb klaster, por \"han\" gjysm\u00ebn e hap\u00ebsir\u00ebs s\u00eb dobishme, nd\u00ebrsa RF-3 mbijeton d\u00ebshtimin e 2-nodeve n\u00eb klaster, por rezervon tashm\u00eb 2\/3 t\u00eb hap\u00ebsir\u00ebs s\u00eb dobishme p\u00ebr nevojat e tij. Kjo skem\u00eb i ngjan shum\u00eb RAID-1, q\u00eb do t\u00eb thot\u00eb se disku virtual, i konfiguruar n\u00eb RF-2, \u00ebsht\u00eb i q\u00ebndruesh\u00ebm ndaj d\u00ebshtimit t\u00eb \u00e7do node n\u00eb klaster. N\u00eb k\u00ebt\u00eb rast, gjith\u00e7ka do t\u00eb jet\u00eb mir\u00eb me t\u00eb dh\u00ebnat dhe madje hyrja-dalja nuk do t\u00eb ndalet. Kur node-ja e r\u00ebzuar t\u00eb kthehet n\u00eb pun\u00eb, do t\u00eb filloj\u00eb rikuperimi\/sinhronizimi automatik i t\u00eb dh\u00ebnave. <\/p>\n

<\/p>\n

M\u00eb posht\u00eb jan\u00eb shembuj t\u00eb shp\u00ebrndarjes s\u00eb t\u00eb dh\u00ebnave RF-2 dhe RF-3 n\u00eb modusin normal dhe n\u00eb situata d\u00ebshtimi.<\/p>\n

<\/p>\n

Kemi nj\u00eb makin\u00eb virtuale me kapacitet 8MB t\u00eb dh\u00ebnash unike (t\u00eb dobishme), e cila funksionon n\u00eb 4 nodet vAIR. Nd\u00ebrsa n\u00eb realitet \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb ket\u00eb nj\u00eb kapacitet kaq t\u00eb vog\u00ebl, p\u00ebr skem\u00ebn q\u00eb reflekton logjik\u00ebn e funksionimit t\u00eb ARDFS, ky shembull \u00ebsht\u00eb m\u00eb i kuptuesh\u00ebm. AB p\u00ebrfaq\u00ebson blloqet virtuale prej 4MB, t\u00eb cilat p\u00ebrmbajn\u00eb t\u00eb dh\u00ebnat unike t\u00eb makin\u00ebs virtuale. Me RF-2 krijohen dy kopje t\u00eb k\u00ebtyre blloqeve A1+A2 dhe B1+B2, p\u00ebrkat\u00ebsisht. K\u00ebto blloqe shp\u00ebrndahen n\u00eb nodet, duke shmangur p\u00ebrputhjen e t\u00eb nj\u00ebjtave t\u00eb dh\u00ebna n\u00eb nj\u00eb nod, q\u00eb do t\u00eb thot\u00eb se kopja A1 nuk do t\u00eb jet\u00eb n\u00eb t\u00eb nj\u00ebjtin nod me kopjen A2. Me B1 dhe B2 \u00ebsht\u00eb e ngjashme.<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

N\u00eb rastin e d\u00ebshtimit t\u00eb nj\u00ebrit nga nodet (p.sh., nodi nr. 3, ku ndodhet kopja B1), kjo kopje aktivizohet automatikisht n\u00eb nodin ku nuk ka kopjen e saj (pra kopjen B2). <\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

K\u00ebshtu, disku virtual (dhe VM, p\u00ebrkat\u00ebsisht) leht\u00eb do t\u00eb p\u00ebrballojn\u00eb d\u00ebshtimin e nj\u00eb nodi n\u00eb skem\u00ebn RF-2.<\/p>\n

<\/p>\n

Skema me replikim, p\u00ebrkund\u00ebr thjesht\u00ebsis\u00eb dhe besueshm\u00ebris\u00eb s\u00eb saj, ka t\u00eb nj\u00ebjtin defekt si RAID1 \u2013 hap\u00ebsira e dobishme \u00ebsht\u00eb e vog\u00ebl.<\/p>\n

<\/p>\n

2) Kodimi i fshirjes ose kodimi eliminues (i njohur gjithashtu si \"kodimi i tepric\u00ebs\") ka si q\u00ebllim zgjidhjen e problemit t\u00eb p\u00ebrmendur m\u00eb sip\u00ebr. EC \u00ebsht\u00eb nj\u00eb skem\u00eb tepric\u00ebs q\u00eb siguron nj\u00eb disponibilitet t\u00eb lart\u00eb t\u00eb dh\u00ebnash me shpenzime m\u00eb t\u00eb ul\u00ebta n\u00eb kapacitetin e diskut krahasuar me replikimin. Princi i funksionimit t\u00eb k\u00ebtij mekanizmi \u00ebsht\u00eb i ngjash\u00ebm me RAID 5, 6, 6P. <\/p>\n

<\/p>\n

Gjat\u00eb kodimit, procesi EC ndan nj\u00eb bllok virtual (n\u00eb m\u00ebnyr\u00eb default 4MB) n\u00eb disa \"cop\u00ebza t\u00eb dh\u00ebnash\" m\u00eb t\u00eb vogla n\u00eb vart\u00ebsi t\u00eb skem\u00ebs EC (p\u00ebr shembull, skema 2+1 e ndan \u00e7do bllok 4 MB n\u00eb 2 cop\u00ebza prej 2MB). M\u00eb pas, ky proces gjeneron p\u00ebr \"cop\u00ebzat e dh\u00ebnash\" \"cop\u00ebza pariteti\" q\u00eb nuk kalojn\u00eb madh\u00ebsin\u00eb e nj\u00eb prej pjes\u00ebve t\u00eb ndara m\u00eb par\u00eb. Gjat\u00eb dekodimit, EC gjeneron cop\u00ebzat e munguar duke lexuar t\u00eb dh\u00ebnat \"e mbijetuara\" n\u00eb t\u00eb gjith\u00eb klasterin. <\/p>\n

<\/p>\n

P\u00ebr shembull, nj\u00eb diskut virtual me skem\u00ebn EC 2 + 1, i realizuar n\u00eb 4 node t\u00eb klasterit, mund t\u00eb p\u00ebrballoj\u00eb nj\u00eb d\u00ebshtim t\u00eb nj\u00eb node n\u00eb klaster ashtu si RF-2. N\u00eb k\u00ebt\u00eb m\u00ebnyr\u00eb, shpenzimet e operimit do t\u00eb jen\u00eb m\u00eb t\u00eb ul\u00ebta, konkretisht, koeficienti i dobish\u00ebm i kapacitetit kur RF-2 \u00ebsht\u00eb 2, nd\u00ebrsa me EC 2+1 do t\u00eb jet\u00eb 1,5. <\/p>\n

<\/p>\n

P\u00ebr ta p\u00ebrshkruar thjesht, thelbi q\u00ebndron n\u00eb at\u00eb se blloku virtual ndahet n\u00eb 2-8 (pse nga 2 deri n\u00eb 8, shih m\u00eb posht\u00eb) \"cop\u00ebza\", dhe p\u00ebr k\u00ebto cop\u00ebza llogariten \"cop\u00ebza\" pariteti me t\u00eb nj\u00ebjtin v\u00ebllim. <\/p>\n

<\/p>\n

N\u00eb p\u00ebrfundim, t\u00eb dh\u00ebnat dhe pariteti shp\u00ebrndahen nj\u00ebtrajt\u00ebsisht n\u00eb t\u00eb gjitha nodet e klasterit. P\u00ebr m\u00eb tep\u00ebr, ashtu si n\u00eb replikim, ARDFS n\u00eb m\u00ebnyr\u00eb automatike shp\u00ebrndan t\u00eb dh\u00ebnat n\u00eb nodet n\u00eb nj\u00eb m\u00ebnyr\u00eb q\u00eb nuk lejon ruajtjen e t\u00eb dh\u00ebnave identike (kopjeve t\u00eb t\u00eb dh\u00ebnave dhe paritetit t\u00eb tyre) n\u00eb nj\u00eb nod\u00eb, p\u00ebr t\u00eb eliminuar mund\u00ebsin\u00eb e humbjes s\u00eb t\u00eb dh\u00ebnave n\u00eb rast se t\u00eb dh\u00ebnat dhe pariteti i tyre papritur ndodhen n\u00eb nj\u00eb nod\u00eb ruajtjeje q\u00eb del jasht\u00eb funksionit. <\/p>\n

<\/p>\n

M\u00eb posht\u00eb \u00ebsht\u00eb nj\u00eb shembull, me t\u00eb nj\u00ebjt\u00ebn virtualk\u00eb prej 8 MB dhe 4 nodet, por tashm\u00eb me skem\u00ebn EC 2+1. <\/p>\n

<\/p>\n

Blloqet A dhe B ndahen n\u00eb dy cop\u00eb secila nga 2 MB (n\u00eb dy sepse 2+1), dmth A1+A2 dhe B1+B2. Ndryshe nga replika, A1 nuk \u00ebsht\u00eb kopje e A2, kjo \u00ebsht\u00eb nj\u00eb bllok virtual A, e ndar\u00eb n\u00eb dy pjes\u00eb, ashtu si dhe blloku B. K\u00ebshtu, ne krijojm\u00eb dy grupe me 4MB, n\u00eb secilin prej t\u00eb cil\u00ebve ndodhen dy cop\u00eb dymegabajt\u00ebshe. M\u00eb tej, p\u00ebr secil\u00ebn nga k\u00ebto grupe llogaritet pariteti i volumit jo m\u00eb shum\u00eb se nj\u00eb cop\u00eb (dmth 2 MB), fituam p\u00ebr m\u00eb tep\u00ebr + 2 cop\u00eb pariteti (A-P dhe B-P). N\u00eb p\u00ebrfundim, kemi 4\u00d72 t\u00eb dh\u00ebna + 2\u00d72 paritet.<\/p>\n

<\/p>\n

M\u00eb pas, pjes\u00ebt \"rregullohen\" n\u00eb nodet n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb dh\u00ebnat t\u00eb mos kryq\u00ebzohen me paritetin e tyre. Pra, A1 dhe A2 nuk do t\u00eb q\u00ebndrojn\u00eb n\u00eb t\u00eb nj\u00ebjt\u00ebn nod\u00eb me A-P.<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

N\u00eb rast se d\u00ebshtojn\u00eb nj\u00eb nodet (le t\u00eb supozojm\u00eb, po ashtu, edhe e treta) blloku i r\u00ebn\u00eb B1 do t\u00eb rikthehet automatikisht nga pariteti B-P, i cili ruhet n\u00eb nod\u00ebn nr. 2, dhe do t\u00eb aktivizohet n\u00eb nod\u00ebn ku nuk ka B-paritet, dmth. pjes\u00ebs B-P. N\u00eb k\u00ebt\u00eb shembull \u2013 \u00ebsht\u00eb nod\u00eb nr. 1.<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

Jam i sigurt se lexuesit kan\u00eb pyetje:<\/p>\n

<\/p>\n

\"\u00c7do gj\u00eb q\u00eb keni p\u00ebrshkruar, \u00ebsht\u00eb realizuar p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb nga konkurent\u00ebt, dhe n\u00eb zgjidhjet open source, n\u00eb \u00e7far\u00eb ndryshimi \u00ebsht\u00eb implementimi juaj EC n\u00eb ARDFS?\"<\/p><\/blockquote>\n

M\u00eb pas do t\u00eb vijn\u00eb karakteristika interesante t\u00eb funksionimit t\u00eb ARDFS.<\/p>\n

<\/p>\n

Kodimi i humbjes me fokus n\u00eb fleksibilitet<\/h3>\n

<\/p>\n

Fillimisht, ne parashikuam nj\u00eb skem\u00eb mjaft t\u00eb p\u00ebrshtatshme EC X+Y, ku X \u00ebsht\u00eb nj\u00eb num\u00ebr nga 2 deri n\u00eb 8, dhe Y \u00ebsht\u00eb nj\u00eb num\u00ebr nga 1 n\u00eb 8, por gjithmon\u00eb m\u00eb i vog\u00ebl ose i barabart\u00eb me X. Kjo skem\u00eb \u00ebsht\u00eb e parashikuar p\u00ebr fleksibilitet. Rritja e numrit t\u00eb copave t\u00eb t\u00eb dh\u00ebnave (X), n\u00eb t\u00eb cilat ndahen blloket virtuale, lejon uljen e kostove t\u00eb mbatjes, pra rritjen e hap\u00ebsir\u00ebs s\u00eb dobishme.
\nRritja e numrit t\u00eb copave t\u00eb paritetit (Y) rrit q\u00ebndrueshm\u00ebrin\u00eb e disku virtual. Sa m\u00eb i madh t\u00eb jet\u00eb vlera e Y, aq m\u00eb shum\u00eb nod t\u00eb klasit mund t\u00eb dalin jasht\u00eb funksionimit. Natyrisht, rritja e volumit t\u00eb paritetit ulet kapacitetin e dobish\u00ebm, por kjo \u00ebsht\u00eb nj\u00eb kosto p\u00ebr q\u00ebndrueshm\u00ebri. <\/p>\n

<\/p>\n

Var\u00ebsia e performanc\u00ebs nga skemat EC \u00ebsht\u00eb pothuajse e drejtp\u00ebrdrejt\u00eb: sa m\u00eb shum\u00eb \"cop\u00ebza\", aq m\u00eb ul\u00ebt \u00ebsht\u00eb performanca, k\u00ebtu, si\u00e7 e kuptoni, \u00ebsht\u00eb e nevojshme nj\u00eb qasje e balancuar. <\/p>\n

<\/p>\n

Ky qasje lejon administrator\u00ebt t\u00eb konfigurojn\u00eb maksimalisht fleksib\u00ebl magazin\u00ebn e shtrir\u00eb. Brenda grumbullit ARDFS, mund t\u00eb p\u00ebrdoren \u00e7do skem\u00eb q\u00ebndrueshm\u00ebrie dhe kombinimin e tyre, q\u00eb gjithashtu, sipas mendimit ton\u00eb, \u00ebsht\u00eb shum\u00eb e dobishme. <\/p>\n

<\/p>\n

M\u00eb posht\u00eb \u00ebsht\u00eb nj\u00eb tabel\u00eb krahasuese e disa (jo t\u00eb gjitha) skemave RF dhe EC.<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

Nga tabela duket se edhe kombinimi m\u00eb \"i ve\u00e7ant\u00eb\" EC 8+7, i cili lejon humbjen e deri n\u00eb 7 nod\u00ebve nj\u00ebkoh\u00ebsisht n\u00eb klaster, \"humb\" hap\u00ebsir\u00eb t\u00eb dobishme m\u00eb pak (1,875 p\u00ebrball\u00eb 2), se sa replikimi standard, dhe mbron 7 her\u00eb m\u00eb mir\u00eb, \u00e7ka e b\u00ebn k\u00ebt\u00eb mekaniz\u00ebm mbrojtjeje, ndon\u00ebse m\u00eb t\u00eb nd\u00ebrlikuar, shum\u00eb m\u00eb t\u00ebrheq\u00ebs n\u00eb situata kur nevojitet maksimalizimi i besueshm\u00ebris\u00eb n\u00eb kushte t\u00eb munges\u00ebs s\u00eb hap\u00ebsir\u00ebs s\u00eb diskut. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, \u00ebsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb kuptohet se \u00e7do \"plus\" n\u00eb X ose Y do t\u00eb sjell\u00eb nj\u00eb shpenzim shtes\u00eb n\u00eb performanc\u00eb, prandaj n\u00eb triangle nd\u00ebrmjet besueshm\u00ebris\u00eb, kursimit dhe performanc\u00ebs, duhen b\u00ebr\u00eb zgjedhje shum\u00eb t\u00eb kujdesshme. P\u00ebr k\u00ebt\u00eb arsye, do t'i kushtojm\u00eb nj\u00eb artikull t\u00eb ve\u00e7ant\u00eb sizing-ut t\u00eb kodimit q\u00eb sillet larg.<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

Besueshm\u00ebria dhe autonomia e sistemit t\u00eb skedar\u00ebve<\/h3>\n

<\/p>\n

ARDFS \u0437\u0430\u043f\u0443\u0441\u043a\u0430het lokalisht n\u00eb t\u00eb gjitha nodet e klasterit dhe sinkronizon mjetet e veta p\u00ebrmes nd\u00ebrfaqeve t\u00eb dedikuara Ethernet. Nj\u00eb pik\u00eb e r\u00ebnd\u00ebsishme \u00ebsht\u00eb se ARDFS sinkronizon vet\u00eb jo vet\u00ebm t\u00eb dh\u00ebnat, por edhe metadatat q\u00eb lidhen me ruajtjen. Gjat\u00eb pun\u00ebs n\u00eb ARDFS, ne paralelisht studiuam nj\u00eb s\u00ebr\u00eb zgjidhjesh ekzistuese dhe zbuluam se shum\u00eb prej tyre e b\u00ebjn\u00eb sinkronizimin e metadatave t\u00eb sistemit t\u00eb skedar\u00ebve duke p\u00ebrdorur nj\u00eb DB t\u00eb shp\u00ebrndar\u00eb t\u00eb jashtme, e cila ne gjithashtu e p\u00ebrdorim p\u00ebr sinkronizimin, por vet\u00ebm t\u00eb konfigurimeve, e jo t\u00eb metadatave t\u00eb FS (p\u00ebr k\u00ebt\u00eb dhe sisteme t\u00eb tjera p\u00ebrkat\u00ebse n\u00eb artikullin e ardhsh\u00ebm). <\/p>\n

<\/p>\n

Sinkronizimi i metadatave t\u00eb FS p\u00ebrmes nj\u00eb DB t\u00eb jashtme \u00ebsht\u00eb sigurisht nj\u00eb zgjidhje funksionale, por at\u00ebher\u00eb konsistenc\u00ebn e t\u00eb dh\u00ebnave t\u00eb ruajtura n\u00eb ARDFS do ta varej nga DB e jashtme dhe nga sjellja e saj (e cila, t\u00eb them t\u00eb drejt\u00ebn \u2014 \u00ebsht\u00eb nj\u00eb zonj\u00eb kapricioze), q\u00eb n\u00eb mendimin ton\u00eb \u00ebsht\u00eb e keqe. Pse? N\u00ebse metadat e FS d\u00ebmtohen, t\u00eb dh\u00ebnat e vet\u00eb FS gjithashtu mund t\u00eb thon\u00eb \u00ablamtumir\u00eb\u00bb, prandaj ne vendos\u00ebm t\u00eb ndiqnim nj\u00eb rrug\u00eb m\u00eb t\u00eb komplikuar, por m\u00eb t\u00eb besueshme. <\/p>\n

<\/p>\n

Ne kemi zhvilluar nga vet\u00eb sistemin e sinkronizimit t\u00eb t\u00eb dh\u00ebnave p\u00ebr ARDFS, dhe ai funksionon plot\u00ebsisht n\u00eb m\u00ebnyr\u00eb t\u00eb pavarur nga sistemet e tjera t\u00eb ngjashme. Kjo do t\u00eb thot\u00eb se asnj\u00eb sistem tjet\u00ebr nuk mund ta d\u00ebmtoj\u00eb t\u00eb dh\u00ebnat e ARDFS. N\u00eb mendimin ton\u00eb, ky \u00ebsht\u00eb rruga m\u00eb e sigurt dhe e duhur, por koha do t\u00eb tregoj\u00eb n\u00ebse \u00ebsht\u00eb v\u00ebrtet k\u00ebshtu. P\u00ebrve\u00e7 k\u00ebsaj, ky qasje sjell nj\u00eb avantazh t\u00eb shtuar. ARDFS mund t\u00eb p\u00ebrdoret pavar\u00ebsisht nga vAIR, thjesht si nj\u00eb depo e zgjeruar, dhe ne do t\u00eb sigurohemi ta shfryt\u00ebzojm\u00eb ndjesh\u00ebm n\u00eb produktet tona t\u00eb ardhshme.<\/p>\n

<\/p>\n

N\u00eb fund, duke krijuar ARDFS, ne fituam nj\u00eb sistem fleksib\u00ebl dhe t\u00eb besuesh\u00ebm dosjesh, q\u00eb ofron mund\u00ebsin\u00eb p\u00ebr t\u00eb kursyer hap\u00ebsir\u00eb \u200b\u200bapo p\u00ebr t\u00eb investuar t\u00eb gjith\u00eb n\u00eb performanc\u00eb, ose p\u00ebr ta b\u00ebr\u00eb depozita jasht\u00ebzakonisht t\u00eb besueshme p\u00ebr nj\u00eb \u00e7mim t\u00eb arsyesh\u00ebm, duke ulur k\u00ebrkesat p\u00ebr performanc\u00eb. <\/p>\n

<\/p>\n

S\u00eb bashku me nj\u00eb politik\u00eb t\u00eb thjesht\u00eb licencimi dhe nj\u00eb model fleksib\u00ebl t\u00eb shp\u00ebrndarjes (p\u00ebr t\u00eb ardhmen, vAIR licencohet sipas node-ve dhe ofrohet si softuer ose si PAK), kjo lejon nj\u00eb p\u00ebrshtatje shum\u00eb t\u00eb sakt\u00eb t\u00eb zgjidhjes sipas k\u00ebrkesave t\u00eb ndryshme t\u00eb klient\u00ebve dhe m\u00eb pas mb\u00ebshtetje t\u00eb leht\u00eb t\u00eb k\u00ebtij balansimi. <\/p>\n

<\/p>\n

Kush ka nevoj\u00eb p\u00ebr k\u00ebt\u00eb mrekulli?<\/h2>\n

<\/p>\n

Nga nj\u00ebra an\u00eb, mund t\u00eb thuhet se n\u00eb treg tashm\u00eb ka lojtar\u00eb me zgjidhje serioze n\u00eb fush\u00ebn e hiper-konvergjenc\u00ebs, dhe ku n\u00eb t\u00eb v\u00ebrtet\u00eb po hyjm\u00eb. Duket se kjo deklarat\u00eb \u00ebsht\u00eb e sakt\u00eb, POR...<\/p>\n

<\/p>\n

Nga ana tjet\u00ebr, duke dal\u00eb \"n\u00eb terren\" dhe duke biseduar me klient\u00ebt, ne dhe partner\u00ebt tan\u00eb shohim se kjo nuk \u00ebsht\u00eb aspak e v\u00ebrtet\u00eb. Ka shum\u00eb detyra p\u00ebr hiper-konvergjenc\u00ebn, disa njer\u00ebz thjesht nuk e dinin se k\u00ebto zgjidhje ekzistonin, disa mendonin se ishin t\u00eb shtrenjta, disa kishin teste t\u00eb d\u00ebshtuara me zgjidhje alternative, dhe disa madje ndalojn\u00eb blerjen p\u00ebr shkak t\u00eb sanksioneve. N\u00eb p\u00ebrgjith\u00ebsi, fusha u tregua e pap\u00ebrpunuar, prandaj shkuam p\u00ebr ta p\u00ebrmir\u00ebsuar))). <\/p>\n

<\/p>\n

Kur \u00ebsht\u00eb ruja m\u00eb e mir\u00eb se GKS?<\/h3>\n

<\/p>\n

Gjat\u00eb pun\u00ebs me tregun, shpesh na pyesin se kur \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb aplikosh skem\u00ebn klasike me ruja, dhe kur - hiper-konvergjenc\u00ebn? Shum\u00eb kompani - prodhues t\u00eb GKS (sidomos ato q\u00eb nuk kan\u00eb ruja n\u00eb portofol) thon\u00eb: \"Ruja po e humb r\u00ebnd\u00ebsin\u00eb, vet\u00ebm hiper-konvergjenc\u00eb!\". Kjo \u00ebsht\u00eb nj\u00eb deklarat\u00eb guximtare, por nuk e pasqyron plot\u00ebsisht realitetin. <\/p>\n

<\/p>\n

T\u00eb them t\u00eb v\u00ebrtet\u00ebn, tregu i ruja v\u00ebrtet po kalon n\u00eb drejtim t\u00eb hiper-konvergjenc\u00ebs dhe zgjidhjeve t\u00eb ngjashme, por gjithmon\u00eb ka nj\u00eb \"por\".<\/p>\n

<\/p>\n

S\u00eb pari, qendrat e t\u00eb dh\u00ebnave dhe infrastrukturat IT t\u00eb nd\u00ebrtuara sipas nj\u00eb skeme klasike me sistemin e ruajtjes (S\u0425\u0414) nuk mund t\u00eb riparohen kaq leht\u00eb, prandaj modernizimi dhe zgjerimi i k\u00ebtyre infrastrukturave \u00ebsht\u00eb nj\u00eb trash\u00ebgimi e 5-7 viteve t\u00eb fundit.<\/p>\n

<\/p>\n

S\u00eb dyti, ato infrastrukturat q\u00eb po nd\u00ebrtohen aktualisht masivisht (n\u00eb Rusi) nd\u00ebrtohen sipas nj\u00eb skeme klasike p\u00ebr p\u00ebrdorimin e S\u0425\u0414, dhe nuk \u00ebsht\u00eb se njer\u00ebzit nuk e din\u00eb p\u00ebr hiper-konvergenc\u00ebn, por sepse tregu i hiper-konvergenc\u00ebs \u00ebsht\u00eb i ri, zgjidhjet dhe standardet ende nuk jan\u00eb stabilizuar, specialist\u00ebt IT ende nuk jan\u00eb t\u00eb trajnuar, p\u00ebrvoja \u00ebsht\u00eb e pak\u00ebt, dhe qendrat e t\u00eb dh\u00ebnave duhet nd\u00ebrtuar k\u00ebtu dhe tani. Dhe kjo tendenc\u00eb do t\u00eb vazhdoj\u00eb p\u00ebr 3-5 vite (pastaj edhe nj\u00eb trash\u00ebgimi, shih pik\u00ebn 1).<\/p>\n

<\/p>\n

S\u00eb treti, ka nj\u00eb kufizim teknik vet\u00ebm p\u00ebr disa vonesa t\u00eb vogla prej 2 milisekondash gjat\u00eb regjistrimit (pa marr\u00eb parasysh cache-in lokal, sigurisht) q\u00eb jan\u00eb \u00e7mimi p\u00ebr ruajtjen e shp\u00ebrndar\u00eb. <\/p>\n

<\/p>\n

Dhe mos harrojm\u00eb p\u00ebrdorimin e server\u00ebve fizik\u00eb t\u00eb m\u00ebdhenj, t\u00eb cil\u00ebt preferojn\u00eb shkall\u00ebzimin vertical t\u00eb sistemit t\u00eb ruajtjes.<\/p>\n

<\/p>\n

Ka shum\u00eb detyra t\u00eb nevojshme dhe t\u00eb njohura, ku storage back-end performon m\u00eb mir\u00eb se hyper-converged. Sigurisht, prodhues q\u00eb nuk kan\u00eb storage back-end n\u00eb portofolin e produkteve t\u00eb tyre nuk do t\u00eb bien dakord me ne, por jemi t\u00eb gatsh\u00ebm t\u00eb argumentojm\u00eb. Natyrisht, si zhvillues t\u00eb t\u00eb dy produkteve, n\u00eb nj\u00eb nga publikimet e ardhshme do t\u00eb b\u00ebjm\u00eb nj\u00eb krahasim midis storage back-end dhe hyper-converged, ku do t\u00eb demonstrojm\u00eb qart\u00eb se n\u00eb cilat kushte \u00ebsht\u00eb m\u00eb mir\u00eb.<\/p>\n

<\/p>\n

Ku do t\u00eb punojn\u00eb m\u00eb mir\u00eb zgjidhjet hyper-converged se storage back-end?<\/h3>\n

<\/p>\n

Duke marr\u00eb parasysh pikat e m\u00ebsip\u00ebrme, mund t\u00eb dalim n\u00eb tri p\u00ebrfundime t\u00eb qarta: <\/p>\n

<\/p>\n

    \n
  1. Aty ku dy millisekonda vones\u00eb n\u00eb shkrim, q\u00eb ndodhin n\u00eb \u00e7do produktivitet (n\u00eb k\u00ebt\u00eb moment nuk flasim p\u00ebr sintetik, nj\u00eb dit\u00eb sintetik mund t\u00eb tregojn\u00eb edhe nanosekonda), jan\u00eb t\u00eb pranuara, hyper-converged do t\u00eb p\u00ebrshtatet.<\/li>\n
  2. Aty ku ngarkesa nga serverat fizik\u00eb t\u00eb m\u00ebdhenj mund t\u00eb shnd\u00ebrrohet n\u00eb shum\u00eb t\u00eb vogla virtual dhe t\u00eb shp\u00ebrndahen n\u00eb node, aty hyper-converged gjithashtu do t\u00eb funksionoj\u00eb mir\u00eb.<\/li>\n
  3. Aty ku shkall\u00ebzimi horizontal \u00ebsht\u00eb m\u00eb i r\u00ebnd\u00ebsish\u00ebm se ai vertikal, gjithashtu hyper-converged do t\u00eb realizohet mrekullisht.<\/li>\n<\/ol>\n

    <\/p>\n

    Cilat jan\u00eb k\u00ebto zgjidhje?<\/h3>\n

    <\/p>\n

      \n
    1. T\u00eb gjith\u00eb sh\u00ebrbimet standarde t\u00eb infrastruktur\u00ebs (sh\u00ebrbimi i katalog\u00ebve, posta, SED, server\u00ebt e skedar\u00ebve, sistemet e vogla ose t\u00eb mesme ERP dhe BI etj.). Ne i quajm\u00eb k\u00ebto \"llogaritje t\u00eb zakonshme\". <\/li>\n
    2. Infrastruktura e ofruesve t\u00eb cloud, ku \u00ebsht\u00eb e nevojshme t\u00eb zgjeroheni horizontalisht shpejt dhe standardizuar dhe t\u00eb krijoni leht\u00ebsisht nj\u00eb num\u00ebr t\u00eb madh makinash virtuale p\u00ebr klient\u00ebt.<\/li>\n
    3. Infrastruktura tavolina virtuale<\/a> (VDI), ku shum\u00eb virtuale t\u00eb vogla t\u00eb p\u00ebrdoruesve nisen dhe lundrojn\u00eb qet\u00ebsisht brenda nj\u00eb klasteri t\u00eb nj\u00ebtrajtsh\u00ebm.<\/li>\n
    4. Rrjetet filiale, ku n\u00eb \u00e7do filial \u00ebsht\u00eb e nevojshme t\u00eb sigurohet nj\u00eb infrastruktur\u00eb standarde, me q\u00ebndrim t\u00eb q\u00ebndruesh\u00ebm, por gjithashtu me kosto t\u00eb ul\u00ebt nga 15-20 makina virtuale.<\/li>\n
    5. \u00c7do llogaritje t\u00eb shp\u00ebrndar\u00eb (sh\u00ebrbimet big data, p\u00ebr shembull). Atje ku ngarkesa nuk shkon \"thell\u00eb\", por \"gjer\u00eb\". <\/li>\n
    6. Mjediset testuese, ku lejohet vonesa e vog\u00ebl shtes\u00eb, por ka kufizime buxhetore, sepse jan\u00eb teste.<\/li>\n<\/ol>\n

      <\/p>\n

      N\u00eb k\u00ebt\u00eb moment, p\u00ebr k\u00ebto detyra ne kemi krijuar AERODISK vAIR dhe pik\u00ebrisht mbi to po b\u00ebjm\u00eb p\u00ebrpjekje (deri tani me sukses). Mund\u00ebsisht, kjo do t\u00eb ndryshoj\u00eb shpejt, pasi bota nuk q\u00ebndron n\u00eb vend.<\/p>\n

      <\/p>\n

      Dhe k\u00ebshtu\u2026<\/h3>\n

      <\/p>\n

      K\u00ebtu p\u00ebrfundon pjesa e par\u00eb e nj\u00eb cikli t\u00eb madh artikujsh; n\u00eb artikullin e ardhsh\u00ebm do t\u00eb flasim p\u00ebr arkitektur\u00ebn e zgjidhjes dhe komponent\u00ebt e p\u00ebrdorur.<\/p>\n

      <\/p>\n

      Do t\u00eb jemi t\u00eb lumtur p\u00ebr pyetje, propozime dhe debate konstruktive.<\/p>\n

      Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

      \u041f\u0440\u0438\u0432\u0435\u0442, \u0447\u0438\u0442\u0430\u0442\u0435\u043b\u0438 \u0425\u0430\u0431\u0440\u0430. \u042d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435\u0439 \u043c\u044b \u043e\u0442\u043a\u0440\u044b\u0432\u0430\u0435\u043c \u0446\u0438\u043a\u043b, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0431\u0443\u0434\u0435\u0442 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0442\u044c \u043e \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0430\u043d\u043d\u043e\u0439 \u043d\u0430\u043c\u0438 \u0433\u0438\u043f\u0435\u0440\u043a\u043e\u043d\u0432\u0435\u0440\u0433\u0435\u043d\u0442\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u0435 AERODISK vAIR. \u0418\u0437\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u043e \u043c\u044b \u0445\u043e\u0442\u0435\u043b\u0438 \u043f\u0435\u0440\u0432\u043e\u0439 \u0436\u0435 \u0441\u0442\u0430\u0442\u044c\u0435\u0439 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u0442\u044c \u0432\u0441\u0451 \u043e\u0431\u043e \u0432\u0441\u0451\u043c, \u043d\u043e \u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u0434\u043e\u0432\u043e\u043b\u044c\u043d\u043e \u0441\u043b\u043e\u0436\u043d\u0430\u044f, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0431\u0443\u0434\u0435\u043c \u0435\u0441\u0442\u044c \u0441\u043b\u043e\u043d\u0430 \u043f\u043e \u0447\u0430\u0441\u0442\u044f\u043c. \u041d\u0430\u0447\u043d\u0435\u043c \u0440\u0430\u0441\u0441\u043a\u0430\u0437 \u0441 \u0438\u0441\u0442\u043e\u0440\u0438\u0438 \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u044f \u0441\u0438\u0441\u0442\u0435\u043c\u044b, \u0443\u0433\u043b\u0443\u0431\u0438\u043c\u0441\u044f \u0432 \u0444\u0430\u0439\u043b\u043e\u0432\u0443\u044e \u0441\u0438\u0441\u0442\u0435\u043c\u0443 ARDFS, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0441\u043d\u043e\u0432\u043e\u0439 vAIR, \u0430 \u0442\u0430\u043a\u0436\u0435 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28919,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-38542","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47 Zgjidhja hiper-konvergjente AERODISK vAIR. Baza \u2014 sistemi i skedar\u00ebve ARDFS | ProHoster","description":"P\u00ebrsh\u00ebndetje, lexues t\u00eb Habra. Me k\u00ebt\u00eb artikull fillojm\u00eb nj\u00eb cik\u00ebl q\u00eb do t\u00eb flas\u00eb p\u00ebr sistemin ton\u00eb hiper-konvergjent AERODISK vAIR. Fillimisht, d\u00ebshironim q\u00eb me artikullin e par\u00eb t\u00eb flasim p\u00ebr gjith\u00e7ka, por sistemi \u00ebsht\u00eb mjaft kompleks, prandaj do t\u00eb ham\u00eb elefantin n\u00eb pjes\u00eb. Do t\u00eb fillojm\u00eb me historin\u00eb e krijimit t\u00eb sistemit, do t\u00eb thellohemi n\u00eb sistemin e skedar\u00ebve ARDFS, i cili \u00ebsht\u00eb baza e vAIR, si dhe","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/giperkonvergentnoe-reshenie-aerodisk-vair-osnova-fajlovaya-sistema-ardfs","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0413\u0438\u043f\u0435\u0440\u043a\u043e\u043d\u0432\u0435\u0440\u0433\u0435\u043d\u0442\u043d\u043e\u0435 \u0440\u0435\u0448\u0435\u043d\u0438\u0435 AERODISK vAIR. \u041e\u0441\u043d\u043e\u0432\u0430 \u2014 \u0444\u0430\u0439\u043b\u043e\u0432\u0430\u044f \u0441\u0438\u0441\u0442\u0435\u043c\u0430 ARDFS | ProHoster","og:description":"\u041f\u0440\u0438\u0432\u0435\u0442, \u0447\u0438\u0442\u0430\u0442\u0435\u043b\u0438 \u0425\u0430\u0431\u0440\u0430. \u042d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0435\u0439 \u043c\u044b \u043e\u0442\u043a\u0440\u044b\u0432\u0430\u0435\u043c \u0446\u0438\u043a\u043b, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0431\u0443\u0434\u0435\u0442 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u0442\u044c \u043e \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0430\u043d\u043d\u043e\u0439 \u043d\u0430\u043c\u0438 \u0433\u0438\u043f\u0435\u0440\u043a\u043e\u043d\u0432\u0435\u0440\u0433\u0435\u043d\u0442\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u0435 AERODISK vAIR. \u0418\u0437\u043d\u0430\u0447\u0430\u043b\u044c\u043d\u043e \u043c\u044b \u0445\u043e\u0442\u0435\u043b\u0438 \u043f\u0435\u0440\u0432\u043e\u0439 \u0436\u0435 \u0441\u0442\u0430\u0442\u044c\u0435\u0439 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u0430\u0442\u044c \u0432\u0441\u0451 \u043e\u0431\u043e \u0432\u0441\u0451\u043c, \u043d\u043e \u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u0434\u043e\u0432\u043e\u043b\u044c\u043d\u043e \u0441\u043b\u043e\u0436\u043d\u0430\u044f, \u043f\u043e\u044d\u0442\u043e\u043c\u0443 \u0431\u0443\u0434\u0435\u043c \u0435\u0441\u0442\u044c \u0441\u043b\u043e\u043d\u0430 \u043f\u043e \u0447\u0430\u0441\u0442\u044f\u043c. \u041d\u0430\u0447\u043d\u0435\u043c \u0440\u0430\u0441\u0441\u043a\u0430\u0437 \u0441 \u0438\u0441\u0442\u043e\u0440\u0438\u0438 \u0441\u043e\u0437\u0434\u0430\u043d\u0438\u044f \u0441\u0438\u0441\u0442\u0435\u043c\u044b, \u0443\u0433\u043b\u0443\u0431\u0438\u043c\u0441\u044f \u0432 \u0444\u0430\u0439\u043b\u043e\u0432\u0443\u044e \u0441\u0438\u0441\u0442\u0435\u043c\u0443 ARDFS, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u044f\u0432\u043b\u044f\u0435\u0442\u0441\u044f \u043e\u0441\u043d\u043e\u0432\u043e\u0439 vAIR, \u0430 \u0442\u0430\u043a\u0436\u0435","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/giperkonvergentnoe-reshenie-aerodisk-vair-osnova-fajlovaya-sistema-ardfs","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:24:25+00:00","article:modified_time":"2019-10-31T19:24:25+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"38542","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-02-09 13:06:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:07:40","updated":"2026-02-09 13:06:19"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/38542","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=38542"}],"version-history":[{"count":2,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/38542\/revisions"}],"predecessor-version":[{"id":158207,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/38542\/revisions\/158207"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/28919"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=38542"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=38542"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=38542"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}