{"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-kombinuese AERODISK vAIR. Baza \u00ebsht\u00eb 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 ne hapim nj\u00eb cik\u00ebl q\u00eb do t\u00eb flas\u00eb p\u00ebr sistemin hibrid t\u00eb zhvilluar nga ne, AERODISK vAIR. Fillimisht d\u00ebshironim q\u00eb me artikullin ton\u00eb t\u00eb par\u00eb t\u00eb flisnim gjith\u00e7ka p\u00ebr gjith\u00e7ka, por sistemi \u00ebsht\u00eb mjaft kompleks, prandaj do ta ham\u00eb elefantin n\u00eb pjes\u00eb. <\/p>\n

<\/p>\n

T\u00eb fillojm\u00eb tregimin 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 do t\u00eb bisedojm\u00eb pak rreth pozicionimit t\u00eb k\u00ebtij zgjidhjeje n\u00eb tregun rus. <\/p>\n

<\/p>\n

N\u00eb artikujt e ardhsh\u00ebm do t\u00eb flasim m\u00eb n\u00eb detaje p\u00ebr komponent\u00ebt e ndrysh\u00ebm arkitekturor\u00eb (kluster, hipervizor, balancues ngarkese, sistem monitorimi etj.), procesin e konfigurimit, do t\u00eb ngrem\u00eb \u00e7\u00ebshtjet e licencimit, do t\u00eb shfaqim testet e crash-it dhe, sigurisht, do t\u00eb shkruajm\u00eb p\u00ebr testimin e ngarkes\u00ebs dhe sizing-un. Po ashtu, do t'i dedikojm\u00eb nj\u00eb artikull ve\u00e7an\u00ebrisht versionit community t\u00eb vAIR.<\/p>\n

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

AERODISK \u00ebsht\u00eb si nj\u00eb histori e ruajtjes s\u00eb t\u00eb dh\u00ebnave? Apo pse filluam ne n\u00eb t\u00eb v\u00ebrtet\u00eb t\u00eb merremi me hibridizimin?<\/h2>\n

<\/p>\n

Fillimisht ideja p\u00ebr t\u00eb krijuar sistemin ton\u00eb hibrid na \u00ebsht\u00eb ardhur dikur rreth vitit 2010. At\u00ebher\u00eb nuk kishte as AERODISK, as zgjidhje t\u00eb ngjashme (sisteme komerciale hibridizimi) n\u00eb treg. Detyra jon\u00eb ishte si m\u00eb posht\u00eb: nga nj\u00eb grup server\u00ebsh me disqe lokale, t\u00eb lidhur p\u00ebrmes nj\u00eb interkonnektiviteti me protokollin Ethernet, t\u00eb krijonim nj\u00eb depo t\u00eb shp\u00ebrndar\u00eb dhe po aty t\u00eb ekzekutonim makinat virtuale dhe rrjetin programor. E gjith\u00eb kjo nevojitej t\u00eb realizohej pa nj\u00eb sistem ruajtjeje (pasi nuk kishim fonde p\u00ebr nj\u00eb sistem t\u00eb till\u00eb dhe as nuk e kishim shpikur sistemin ton\u00eb n\u00eb at\u00eb koh\u00eb).<\/p>\n

<\/p>\n

Provo\u00ebm shum\u00eb zgjidhje open source dhe megjithat\u00eb arrit\u00ebm ta zgjidhnim k\u00ebt\u00eb detyr\u00eb, por zgjidhja ishte shum\u00eb komplekse dhe e v\u00ebshtir\u00eb p\u00ebr t'u p\u00ebrs\u00ebritur. P\u00ebr m\u00eb tep\u00ebr, kjo zgjidhje ishte n\u00eb nj\u00eb lloj kategorie \u00abFunksionon? Mos e prek!\u00bb. Prandaj, pasi e zgjidh\u00ebm at\u00eb detyr\u00eb, nuk vendos\u00ebm t\u00eb zhvillonim m\u00eb tej iden\u00eb e kthimit t\u00eb rezultatit t\u00eb pun\u00ebs son\u00eb n\u00eb nj\u00eb produkt t\u00eb plot\u00eb. <\/p>\n

<\/p>\n

Pas asaj ngjarjeje, ne u larguam nga kjo ide, por ndjenja e asaj detyre vazhdoi t\u00eb na p\u00ebrcjell\u00eb, nd\u00ebrsa dobin\u00eb nga nj\u00eb zgjidhje e till\u00eb e kishte m\u00eb se t\u00eb dukshme. N\u00eb vazhdim, produktet HCI t\u00eb lansuara nga kompanit\u00eb e huaja vet\u00ebm sa e konfirmuan k\u00ebt\u00eb ndjenj\u00eb. <\/p>\n

<\/p>\n

Prandaj, n\u00eb mesin e vitit 2016, ne u kthyem n\u00eb k\u00ebt\u00eb projekt si pjes\u00eb e krijimit t\u00eb nj\u00eb produkti t\u00eb plot\u00eb. N\u00eb at\u00eb koh\u00eb, ne nuk kishim asnj\u00eb marr\u00ebdh\u00ebnie me investitor\u00ebt, prandaj u detyruam t\u00eb blinim stend\u00ebn e zhvillimit me parat\u00eb tona t\u00eb vogla. Duke k\u00ebrkuar n\u00eb Avito p\u00ebr server\u00eb dhe switch-e t\u00eb p\u00ebrdorur, filluam pun\u00ebn.<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

Detyra kryesore fillestare ishte krijimi i nj\u00eb sistemi t\u00eb vetin t\u00eb skedar\u00ebve, pavar\u00ebsisht se sa i thjesht\u00eb, q\u00eb do t\u00eb ishte n\u00eb gjendje t\u00eb shp\u00ebrndante automatikisht dhe n\u00eb m\u00ebnyr\u00eb t\u00eb barabart\u00eb t\u00eb dh\u00ebnat n\u00eb form\u00ebn e blloqeve virtuale n\u00eb nj\u00eb num\u00ebr n t\u00eb nyjeve t\u00eb klusterit, t\u00eb cilat ishin t\u00eb lidhura me nj\u00ebra-tjetr\u00ebn p\u00ebrmes Ethernet-it. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, FS duhej t\u00eb shkall\u00ebzonte mir\u00eb dhe leht\u00ebsisht dhe t\u00eb ishte e pavarur nga sistemet e af\u00ebrta, dmth. t\u00eb ishte e shk\u00ebputur nga vAIR si nj\u00eb \"thjesht ruajtje\".<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

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

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

Ne q\u00ebllimisht refuzuam p\u00ebrdorimin e zgjidhjeve gati t\u00eb hapura open source p\u00ebr organizimin e nj\u00eb depozitimi t\u00eb shp\u00ebrndar\u00eb (ceph, gluster, lustre dhe t\u00eb ngjashme) n\u00eb favor t\u00eb zhvillimit ton\u00eb, pasi tashm\u00eb kishim p\u00ebrvoj\u00eb t\u00eb madhe projektimi me to. Sigurisht, k\u00ebto zgjidhje jan\u00eb t\u00eb shk\u00eblqyera vet\u00eb, dhe para se t\u00eb fillonim pun\u00ebn me Aerodisk, kishim realizuar disa projekte integruese me to. Por nj\u00eb gj\u00eb \u00ebsht\u00eb t\u00eb realizosh nj\u00eb detyr\u00eb specifike p\u00ebr nj\u00eb klient, t\u00eb trajnotosh stafin dhe, ndoshta, t\u00eb blesh mb\u00ebshtetje nga nj\u00eb ofrues i madh, dhe krejt ndryshe \u00ebsht\u00eb t\u00eb krijosh nj\u00eb produkt t\u00eb leht\u00eb p\u00ebr ta riprodhuar, q\u00eb do t\u00eb p\u00ebrdoret p\u00ebr detyra t\u00eb ndryshme, q\u00eb p\u00ebr to, si ofrues, ndoshta nuk do t\u00eb dim\u00eb as vet\u00eb. P\u00ebr q\u00ebllimin e dyt\u00eb, produktet ekzistuese open source nuk na p\u00ebrshtateshin, prandaj vendos\u00ebm ta zhvillonim sistemin e shp\u00ebrndar\u00eb t\u00eb skedar\u00ebve vet\u00eb.
\nPas dy vitesh, forca e disa zhvilluesve (t\u00eb cil\u00ebt kombinonin pun\u00ebn mbi vAIR me pun\u00ebn mbi klasiken SHD Engine) arrit\u00ebn nj\u00eb rezultat t\u00eb caktuar.<\/p>\n

<\/p>\n

N\u00eb vitin 2018, ne shkruam nj\u00eb sistem t\u00eb thjesht\u00eb skedar\u00ebsh dhe e plot\u00ebsuam at\u00eb me lidhjet e nevojshme. Sistemi bashkonte disqet fizike (lokale) nga server\u00eb t\u00eb ndrysh\u00ebm n\u00eb nj\u00eb reservoir t\u00eb shesht\u00eb dhe i \"priste\" ato n\u00eb blloqe virtuale, m\u00eb pas nga blloqet virtuale krijoheshin pajisje bllokues me nj\u00eb nivel t\u00eb caktuar t\u00eb q\u00ebndrueshm\u00ebris\u00eb ndaj d\u00ebshtimeve, mbi t\u00eb cilat, me ndihm\u00ebn e hipervizorit KVM, krijoheshin dhe ekzekutoheshin makinat virtuale. <\/p>\n

<\/p>\n

Ne kemi vendosur ta quajm\u00eb sistemin e skedar\u00ebve ARDFS (kuptoni vet\u00eb se \u00e7far\u00eb do t\u00eb thot\u00eb))<\/p>\n

<\/p>\n

Ky prototip dukej mir\u00eb (sigurisht, jo vizualisht, sepse at\u00ebher\u00eb nuk kishte as nj\u00eb dizajn vizual) dhe tregoi rezultate t\u00eb mira n\u00eb performanc\u00eb dhe shkall\u00ebzueshm\u00ebri. Pas rezultatit t\u00eb par\u00eb real, 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.<\/p>\n

<\/p>\n

Ajo koh\u00eb e b\u00ebri t\u00eb qart\u00eb arkitektur\u00ebn e p\u00ebrgjithshme t\u00eb zgjidhjes, e cila deri tani nuk ka p\u00ebsuar ndryshime t\u00eb r\u00ebnd\u00ebsishme.<\/p>\n

<\/p>\n

Le t\u00eb thellojm\u00eb n\u00eb sistemin e skedar\u00ebve ARDFS<\/h2>\n

<\/p>\n

ARDFS \u00ebsht\u00eb baza e vAIR, e cila siguron ruajtjen e t\u00eb dh\u00ebnave t\u00eb shp\u00ebrndara dhe t\u00eb besueshme t\u00eb gjith\u00eb klasterit. Nj\u00eb nga (por jo e vetmja) ve\u00e7ori dalluese e ARDFS \u00ebsht\u00eb se ajo nuk p\u00ebrdor asnj\u00eb menaxhim t\u00eb jasht\u00ebm. server\u00ebsh t\u00eb dedikuar<\/a> I gjith\u00eb ky koncept \u00ebsht\u00eb 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 e gjith\u00eb hap\u00ebsira e disponueshme e shtesave. \u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb kuptoni se rezervuari nuk jan\u00eb ende t\u00eb dh\u00ebna dhe as hap\u00ebsir\u00eb e formatizuar, por thjesht nj\u00eb ndarje, dmth. \u00e7do nod\u00eb me vAIR t\u00eb instaluar kur shtohet n\u00eb klaster automatikisht bashkohet n\u00eb rezervuarin e p\u00ebrbashk\u00ebt ARDFS dhe burimet diskore b\u00ebhen automatikisht t\u00eb zakonshme p\u00ebr t\u00eb gjith\u00eb klasterin (dhe t\u00eb disponueshme p\u00ebr ruajtjen e ardhshme t\u00eb t\u00eb dh\u00ebnave). Ky qasje lejon q\u00eb nodet t\u00eb shtohen dhe hiqen n\u00eb flak\u00eb pa ndonj\u00eb ndikim t\u00eb r\u00ebnd\u00ebsish\u00ebm n\u00eb sistemin q\u00eb po punon. Pra, sistemi \u00ebsht\u00eb shum\u00eb i leht\u00eb p\u00ebr t'u shkall\u00ebzuar me 'blloqe', duke shtuar ose hequr nodet nga klasteri sipas nevoj\u00ebs.<\/p>\n

<\/p>\n

P\u00ebrmbi rezervuarin ARDFS shtohen disqet virtuale (objekte ruajtjeje p\u00ebr virtual\u00ebt), t\u00eb cilat nd\u00ebrtohen nga blloqe virtuale me madh\u00ebsi 4 megabajt. T\u00eb dh\u00ebnat ruhen drejtp\u00ebrdrejt n\u00eb disqet virtuale. N\u00eb nivelin e disqeve virtuale gjithashtu p\u00ebrcaktohet nj\u00eb skem\u00eb besueshm\u00ebrie. <\/p>\n

<\/p>\n

Si ndoshta mund t\u00eb keni kuptuar, p\u00ebr disponueshm\u00ebrin\u00eb e sistemit t\u00eb diskut nuk p\u00ebrdorim konceptin RAID (Grupi i tep\u00ebrt i Disqeve t\u00eb Pavarura), por p\u00ebrdorim RAIN (Grupi i tep\u00ebrt i Nod\u00ebve t\u00eb Pavarur). Pra, disponueshm\u00ebria matet, automatizohet dhe menaxhohet n\u00eb baz\u00eb t\u00eb nod\u00ebve, jo t\u00eb disqeve. Disqet, natyrisht, jan\u00eb gjithashtu objekte ruajtjeje, ato, ashtu si gjith\u00e7ka tjet\u00ebr, monitorohen dhe mund t\u00eb kryejn\u00eb t\u00eb gjitha operacionet standarde, p\u00ebrfshir\u00eb nd\u00ebrtimin e nj\u00eb RAID lokal, por klubi operon pik\u00ebrisht me nod\u00ebt. <\/p>\n

<\/p>\n

N\u00eb situata kur shum\u00eb d\u00ebshirohet RAID (p.sh., skenari q\u00eb mb\u00ebshtet d\u00ebshtime t\u00eb shumta n\u00eb klaster\u00ebt e vegj\u00ebl), asgj\u00eb nuk e ndalon p\u00ebrdorimin e kontrollor\u00ebve t\u00eb RAID lokal\u00eb, dhe mbi ta t\u00eb krijohet nj\u00eb ruajtje e zgjatur dhe nj\u00eb arkitektur\u00eb RAIN. Ky skenar \u00ebsht\u00eb plot\u00ebsisht i zbatuesh\u00ebm dhe mb\u00ebshtetet nga ne, prandaj do ta diskutojm\u00eb n\u00eb artikullin ton\u00eb p\u00ebr skenar\u00ebt tipik t\u00eb p\u00ebrdorimit t\u00eb vAIR.<\/p>\n

<\/p>\n

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

<\/p>\n

Mund t\u00eb ket\u00eb dy skema disponueshm\u00ebrie p\u00ebr disqet virtuale n\u00eb vAIR:<\/p>\n

<\/p>\n

1) Faktori i replikimit ose thjesht replikimi \u2013 kjo metod\u00eb disponueshm\u00ebrie \u00ebsht\u00eb e thjesht\u00eb \"si nj\u00eb shkop dhe litar\". Kryhet replikimi sinkron midis nod\u00ebve me faktor 2 (2 kopje p\u00ebr klaster) ose 3 (3 kopje, p\u00ebrkat\u00ebsisht). RF-2 i lejon disqet virtuale t\u00eb p\u00ebrballojn\u00eb d\u00ebshtimin e nj\u00eb nodi n\u00eb klaster, por \"ha\" gjysm\u00ebn e volumit t\u00eb dobish\u00ebm, nd\u00ebrsa RF-3 do t\u00eb p\u00ebrballoj\u00eb d\u00ebshtimin e 2 nod\u00ebve n\u00eb klaster, por do t'i rezervoj\u00eb 2\/3 t\u00eb volumit t\u00eb dobish\u00ebm p\u00ebr nevojat e tij. Kjo skem\u00eb \u00ebsht\u00eb shum\u00eb e ngjashme me RAID-1, dometh\u00ebn\u00eb nj\u00eb disk virtual i konfiguruar n\u00eb RF-2 \u00ebsht\u00eb i q\u00ebndruesh\u00ebm ndaj d\u00ebshtimit t\u00eb cilitdo nod t\u00eb vet\u00ebm t\u00eb klasterit. N\u00eb k\u00ebt\u00eb rast, t\u00eb dh\u00ebnat do t\u00eb jen\u00eb n\u00eb rregull dhe madje I\/O nuk do t\u00eb ndalet. Kur nodi i r\u00ebn\u00eb t\u00eb kthehet n\u00eb pun\u00eb, do t\u00eb filloj\u00eb rikuperimi\/sinkronizimi 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 modalitetin normal dhe n\u00eb situatat e d\u00ebshtimeve.<\/p>\n

<\/p>\n

Ne kemi nj\u00eb makin\u00eb virtuale me 8MB t\u00eb dh\u00ebnash unike (t\u00eb dobishme), e cila punon n\u00eb 4 nodet vAIR. \u00cbsht\u00eb e qart\u00eb se n\u00eb realitet nj\u00eb volum kaq i vog\u00ebl nuk do t\u00eb jet\u00eb i mundur, por p\u00ebr diagram\u00ebn q\u00eb pasqyron logjik\u00ebn e pun\u00ebs s\u00eb ARDFS, ky shembull \u00ebsht\u00eb m\u00eb i qart\u00eb. AB jan\u00eb blloqe virtuale prej 4MB q\u00eb p\u00ebrmbajn\u00eb t\u00eb dh\u00ebna unike t\u00eb makin\u00ebs virtuale. N\u00eb RF-2 krijohen dy kopje t\u00eb k\u00ebtyre blloqeve A1 + A2 dhe B1 + B2, p\u00ebrkat\u00ebsisht. K\u00ebto blloqe \u201cshp\u00ebrndahen\u201d n\u00eb nodet, duke shmangur mbivendosjen e t\u00eb nj\u00ebjtave t\u00eb dh\u00ebna n\u00eb nj\u00eb nod\u00eb, dometh\u00ebn\u00eb kopja A1 nuk do t\u00eb jet\u00eb n\u00eb nj\u00eb nod\u00eb me kopjen A2. Me B1 dhe B2 \u00ebsht\u00eb e ngjashme.<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

N\u00eb rast se nj\u00ebra nga nodet ndalon (p.sh., nodi nr. 3, ku ndodhet kopja B1), kjo kopje aktivizohet automatikisht n\u00eb nodin ku nuk ka kopje t\u00eb kopjes s\u00eb saj (dometh\u00ebn\u00eb kopjes B2). <\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

K\u00ebshtu, disku virtual (dhe VM, p\u00ebrkat\u00ebsisht) do t'i mbijetoj\u00eb leht\u00eb ndalimit t\u00eb nj\u00eb nodi n\u00eb skem\u00ebn RF-2.<\/p>\n

<\/p>\n

Skema me replikim, megjith\u00ebse e thjesht\u00eb dhe e besueshme, vuan nga t\u00eb nj\u00ebjtin problem si RAID1 \u2013 hap\u00ebsir\u00eb e vog\u00ebl t\u00eb dobishme.<\/p>\n

<\/p>\n

2) Kodimi i fshirjes ose kodimi i fshirjes (i njohur gjithashtu si \u00abkodim i tepric\u00ebs\u00bb ose \u00abkod i tepric\u00ebs\u00bb) ekziston p\u00ebr t\u00eb zgjidhur problemin e m\u00ebsip\u00ebrm. EC \u00ebsht\u00eb nj\u00eb skem\u00eb teprice q\u00eb garanton nj\u00eb akses t\u00eb lart\u00eb n\u00eb t\u00eb dh\u00ebna me m\u00eb pak shpenzime n\u00eb hap\u00ebsir\u00ebn e diskut krahasuar me replikimin. Parimi i funksionimit t\u00eb k\u00ebtij mekanizmi \u00ebsht\u00eb i ngjash\u00ebm me RAID 5, 6, 6P. <\/p>\n

<\/p>\n

N\u00eb kodimin EC, procesi e ndan bllokun virtual (p\u00ebr default 4MB) n\u00eb disa \u2018cop\u00ebza t\u00eb dh\u00ebnash\u2019 m\u00eb t\u00eb vogla, var\u00ebsisht nga skema EC (p.sh., skema 2 + 1 e ndan \u00e7do bllok 4 MB n\u00eb 2 copa prej 2MB). Pas k\u00ebsaj, ky proces gjeneron p\u00ebr \u2018cop\u00ebzat e t\u00eb dh\u00ebnave\u2019 \u2018cop\u00ebza pariteti\u2019 me madh\u00ebsi jo m\u00eb t\u00eb madhe se nj\u00eb nga pjes\u00ebt e ndara m\u00eb par\u00eb. Kur dekodohet, EC gjeneron cop\u00ebt q\u00eb mungojn\u00eb duke lexuar t\u00eb dh\u00ebnat \u2018e mbetura\u2019 n\u00eb t\u00eb gjith\u00eb klasterin. <\/p>\n

<\/p>\n

P\u00ebr shembull, disku virtual me skem\u00ebn EC 2 + 1, e realizuar n\u00eb 4 nodet e klasterit, do t\u00eb p\u00ebrballoj\u00eb leht\u00ebsisht ndalimin e nj\u00eb nodi n\u00eb klaster ashtu si RF-2. Nd\u00ebrsa shpenzimet do t\u00eb jen\u00eb m\u00eb t\u00eb ulta, n\u00eb ve\u00e7anti koeficienti i kapacitetit t\u00eb d\u00ebgjuesh\u00ebm n\u00eb RF-2 \u00ebsht\u00eb 2, nd\u00ebrsa p\u00ebr EC 2 + 1 do t\u00eb jet\u00eb 1,5. <\/p>\n

<\/p>\n

N\u00ebse p\u00ebr ta p\u00ebrshkruar m\u00eb thjesht\u00eb, thelbi \u00ebsht\u00eb se blloku virtual ndahet n\u00eb 2-8 (pse nga 2 deri n\u00eb 8 shih m\u00eb posht\u00eb) \u2018cop\u00ebza\u2019, dhe p\u00ebr k\u00ebto cop\u00ebza llogariten \u2018cop\u00ebza\u2019 pariteti t\u00eb nj\u00ebjt\u00eb n\u00eb volum. <\/p>\n

<\/p>\n

Si n\u00eb fund, t\u00eb dh\u00ebnat dhe pariteti shp\u00ebrndahen n\u00eb m\u00ebnyr\u00eb uniforme n\u00eb t\u00eb gjitha nodet e klasterit. Po ashtu, si n\u00eb rastin e replikimit, ARDFS automatikisht shp\u00ebrndan t\u00eb dh\u00ebnat n\u00eb nodet n\u00eb nj\u00eb m\u00ebnyr\u00eb q\u00eb parandalon ruajtjen e t\u00eb nj\u00ebjtave t\u00eb dh\u00ebna (kopia e t\u00eb dh\u00ebnave dhe pariteti i tyre) n\u00eb nj\u00eb nod, p\u00ebr t\u00eb eliminuar mund\u00ebsin\u00eb e humbjes s\u00eb t\u00eb dh\u00ebnave, n\u00ebse t\u00eb dh\u00ebnat dhe pariteti i tyre ndodhen papritur n\u00eb nj\u00eb nod ruajtjeje q\u00eb d\u00ebshtojn\u00eb. <\/p>\n

<\/p>\n

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

<\/p>\n

Bloket A dhe B ndahen n\u00eb dy pjes\u00eb nga 2 MB secila (n\u00eb dy sepse 2+1), dmth n\u00eb A1+A2 dhe B1+B2. Ndryshe nga replika, A1 nuk \u00ebsht\u00eb nj\u00eb kopje e A2, \u00ebsht\u00eb nj\u00eb bllok virtual A, i ndar\u00eb n\u00eb dy pjes\u00eb, ashtu si dhe blloku B. N\u00eb p\u00ebrfundim, kemi dy grupe prej 4MB, n\u00eb secilin prej t\u00eb cil\u00ebve ndodhen dy pjes\u00eb t\u00eb dy megabajteve. Pastaj, p\u00ebr secilin prej k\u00ebtyre grupeve llogaritet pariteti me nj\u00eb volum jo m\u00eb shum\u00eb se nj\u00eb pjes\u00eb (dmth 2 MB), k\u00ebshtu q\u00eb marrim p\u00ebrve\u00e7 + 2 pjes\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 tej, cop\u00ebzat \"shp\u00ebrndahen\" n\u00eb nodet n\u00eb nj\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb dh\u00ebnat t\u00eb mos p\u00ebrputhen me paritetin e tyre. K\u00ebshtu, A1 dhe A2 nuk do t\u00eb jen\u00eb n\u00eb t\u00eb nj\u00ebjt\u00ebn nod me A-P.<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

N\u00eb rast t\u00eb defektit t\u00eb nj\u00eb nodi (le t\u00eb themi, nodi i tret\u00eb), blloku i r\u00ebn\u00eb B1 do t\u00eb rikthehet automatikisht nga pariteti B-P, i ruajtur n\u00eb nodin nr. 2, dhe do t\u00eb aktivizohet n\u00eb nodin ku nuk ka paritet B, dmth. cop\u00ebza B-P. N\u00eb k\u00ebt\u00eb shembull \u2013 kjo \u00ebsht\u00eb nodi nr. 1.<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

Jam i sigurt q\u00eb lexuesi ka nj\u00eb pyetje:<\/p>\n

<\/p>\n

\"Gjith\u00e7ka q\u00eb keni p\u00ebrshkruar, \u00ebsht\u00eb realizuar prej koh\u00ebsh nga konkurrent\u00ebt dhe n\u00eb zgjidhjet open source, cila \u00ebsht\u00eb ndryshimi i implementimit tuaj t\u00eb EC n\u00eb ARDFS?\"<\/p><\/blockquote>\n

M\u00eb pas do t\u00eb paraqiten karakteristikat interesante t\u00eb funksionimit t\u00eb ARDFS.<\/p>\n

<\/p>\n

Kodimi i shkat\u00ebrrimit me theks n\u00eb fleksibilitet<\/h3>\n

<\/p>\n

Fillimisht ne parashikuam nj\u00eb skem\u00eb mjaft fleksib\u00ebl EC X+Y, ku X \u00ebsht\u00eb numri nga 2 deri n\u00eb 8, dhe Y \u00ebsht\u00eb numri nga 1 deri n\u00eb 8, por gjithmon\u00eb m\u00eb i vog\u00ebl ose i barabart\u00eb me X. Kjo skem\u00eb \u00ebsht\u00eb parashikuar p\u00ebr fleksibilitet. Rritja e numrit t\u00eb cop\u00ebzave t\u00eb t\u00eb dh\u00ebnave (X), n\u00eb t\u00eb cilat ndahet blloku virtual, lejon uljen e kostove operative, pra rritjen e hap\u00ebsir\u00ebs s\u00eb dobishme.
\nRritja e numrit t\u00eb cop\u00ebzave t\u00eb paritetit (Y) rrit q\u00ebndrueshm\u00ebrin\u00eb e diskut virtual. Sa m\u00eb e madhe t\u00eb jet\u00eb vlera e Y, aq m\u00eb shum\u00eb nodet n\u00eb klaster mund t\u00eb d\u00ebshtojn\u00eb. Natyrisht, rritja e volumit t\u00eb paritetit ul volumetrin\u00eb e kapacitetit t\u00eb dobish\u00ebm, por kjo \u00ebsht\u00eb nj\u00eb \u00e7mim p\u00ebr q\u00ebndrueshm\u00ebri. <\/p>\n

<\/p>\n

Var\u00ebsia e performanc\u00ebs n\u00eb skemat EC \u00ebsht\u00eb pothuajse e drejtp\u00ebrdrejt\u00eb: sa m\u00eb shum\u00eb \"cop\u00ebza\", aq m\u00eb e ul\u00ebt \u00ebsht\u00eb performanca, k\u00ebtu, \u00ebsht\u00eb e qart\u00eb, nevojitet nj\u00eb vler\u00ebsim i balancuar. <\/p>\n

<\/p>\n

Ky qasje lejon administrator\u00ebt t\u00eb konfigurojn\u00eb ruajtjen e zgjatur sa m\u00eb fleksib\u00ebl. Brenda grupit ARDFS \u00ebsht\u00eb e mundur t\u00eb p\u00ebrdoren \u00e7do skem\u00eb t\u00eb q\u00ebndrueshm\u00ebris\u00eb dhe kombinime t\u00eb 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 krahasimi e disa (jo t\u00eb gjitha t\u00eb mundshme) skemave RF dhe EC.<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

Nga tabela tregohet se edhe kombinimi m\u00eb \"i avancuar\" EC 8+7, i cili lejon humbjen e deri n\u00eb 7 nod\u00ebve n\u00eb klaster, \"hap\" m\u00eb pak hap\u00ebsir\u00eb t\u00eb dobishme (1,875 ndaj 2), se sa replikimi standard, dhe mbron 7 her\u00eb m\u00eb mir\u00eb, q\u00eb e b\u00ebn k\u00ebt\u00eb mekaniz\u00ebm mbrojtjeje ndon\u00ebse m\u00eb t\u00eb nd\u00ebrlikuar, por duksh\u00ebm m\u00eb t\u00ebrheq\u00ebs n\u00eb situatat kur \u00ebsht\u00eb e nevojshme t\u00eb sigurohet nj\u00eb besueshm\u00ebri maksimale n\u00eb kushte t\u00eb munges\u00ebs s\u00eb hap\u00ebsir\u00ebs diskore. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, duhet t\u00eb kuptohet se \u00e7do \"plus\" n\u00eb X ose Y do t\u00eb jet\u00eb nj\u00eb shpenzim shtes\u00eb n\u00eb performanc\u00eb, prandaj n\u00eb trek\u00ebnd\u00ebshin mes besueshm\u00ebris\u00eb, kursimit dhe performanc\u00ebs duhet t\u00eb zgjidhet me shum\u00eb kujdes. P\u00ebr k\u00ebt\u00eb arsye, nj\u00eb artikull t\u00eb ve\u00e7ant\u00eb do t'i kushtohet dimensionimit t\u00eb kodimit t\u00eb larg\u00ebt.<\/p>\n

<\/p>\n

\"Zgjidhja<\/p>\n

<\/p>\n

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

<\/p>\n

ARDFS \u0437\u0430\u043f\u0443\u0441\u043a\u0430het lokal n\u00eb t\u00eb gjitha nod\u00ebt e klasterit dhe sinkronizon ato me mjete t\u00eb veta p\u00ebrmes nd\u00ebrfaqeve t\u00eb dedikuara Ethernet. Nj\u00eb aspekt i r\u00ebnd\u00ebsish\u00ebm \u00ebsht\u00eb se ARDFS sinkronizon automatikisht jo vet\u00ebm t\u00eb dh\u00ebnat, por edhe metadat\u00ebn e lidhur me ruajtjen. Gjat\u00eb pun\u00ebs mbi ARDFS kemi studiuar paralelisht nj\u00eb s\u00ebr\u00eb zgjidhjesh ekzistuese dhe kemi zbuluar se shum\u00eb b\u00ebjn\u00eb sinkronizimin e metadata-s s\u00eb sistemit t\u00eb skedar\u00ebve me an\u00eb t\u00eb nj\u00eb DB t\u00eb shp\u00ebrndara t\u00eb jashtme, t\u00eb cil\u00ebn ne gjithashtu e p\u00ebrdorim p\u00ebr sinkronizimin, por vet\u00ebm p\u00ebr konfigurimet, e jo p\u00ebr metadatat e FS (p\u00ebr k\u00ebt\u00eb dhe p\u00ebr sisteme t\u00eb tjera lidhur do t\u00eb flasim n\u00eb artikullin tjet\u00ebr). <\/p>\n

<\/p>\n

Sinkronizimi i metadata t\u00eb FS-s\u00eb duke p\u00ebrdorur nj\u00eb DB t\u00eb jashtme \u00ebsht\u00eb nj\u00eb zgjidhje, natyrisht, e funksionueshme, por k\u00ebshtu konsistenca e t\u00eb dh\u00ebnave t\u00eb ruajtura n\u00eb ARDFS do t\u00eb varej nga DB e jashtme dhe sjellja e saj (nd\u00ebrsa ajo, p\u00ebr t\u00eb mos th\u00ebn\u00eb ndryshe - \u00ebsht\u00eb nj\u00eb zonj\u00eb e kaprici), gj\u00eb q\u00eb sipas mendimit ton\u00eb \u00ebsht\u00eb e keqe. Pse? N\u00ebse metadata e FS-s\u00eb d\u00ebmtohet, edhe t\u00eb dh\u00ebnat e vet\u00eb FS-s\u00eb mund t\u2019i themi \u00abmirupafshim\u00bb, prandaj vendos\u00ebm t\u00eb ndjekim nj\u00eb rrug\u00eb m\u00eb t\u00eb komplikuar, por m\u00eb t\u00eb besueshme. <\/p>\n

<\/p>\n

Ne e zhvilluam n\u00eb m\u00ebnyr\u00eb t\u00eb pavarur n\u00ebn-sistemin e sinkronizimit t\u00eb metadata p\u00ebr ARDFS, dhe ai jeton plot\u00ebsisht i pavarur nga n\u00ebn-sistemat e tjera. Kjo do t\u00eb thot\u00eb, asnj\u00eb n\u00ebn-sistem tjet\u00ebr nuk mund t\u00eb d\u00ebmtoj\u00eb t\u00eb dh\u00ebnat e ARDFS. Sipas mendimit ton\u00eb, kjo \u00ebsht\u00eb rruga m\u00eb e besueshme dhe e duhur, n\u00ebse \u00ebsht\u00eb kjo n\u00eb t\u00eb v\u00ebrtet\u00eb - koha do ta tregoj\u00eb. P\u00ebr m\u00eb tep\u00ebr, me k\u00ebt\u00eb qasje shfaqet nj\u00eb p\u00ebrfitim shtes\u00eb. ARDFS mund t\u00eb p\u00ebrdoret pavar\u00ebsisht nga vAIR, thjesht si nj\u00eb magazin\u00eb e shtrir\u00eb, gj\u00eb q\u00eb me siguri do ta shfryt\u00ebzojm\u00eb n\u00eb produktet tona t\u00eb ardhshme.<\/p>\n

<\/p>\n

Si rezultat, pasi zhvilluam ARDFS, mor\u00ebm nj\u00eb sistem t\u00eb fileve fleksib\u00ebl dhe t\u00eb besuesh\u00ebm, q\u00eb ofron nj\u00eb zgjedhje se ku mund t\u00eb kursehen kapacitetet ose t\u2019i jepni gjith\u00e7ka performanc\u00ebs, ose t\u00eb b\u00ebni magazinimin jasht\u00ebzakonisht t\u00eb besuesh\u00ebm p\u00ebr nj\u00eb \u00e7mim t\u00eb arsyesh\u00ebm, por duke ulur k\u00ebrkesat p\u00ebr performanc\u00eb. <\/p>\n

<\/p>\n

Bashk\u00eb me nj\u00eb politik\u00eb t\u00eb thjesht\u00eb licencimi dhe nj\u00eb model fleksib\u00ebl shp\u00ebrndarjeje (p\u00ebr t\u00eb mos e humbur baz\u00ebn, vAIR licencohet sipas nyjave, dhe \u00ebsh\u00eb i disponuesh\u00ebm ose si software, ose si PAK) kjo lejon q\u00eb t\u00eb precisohet zgjidhja p\u00ebr k\u00ebrkesa t\u00eb ndryshme t\u00eb klient\u00ebve dhe m\u00eb tej ta mir\u00ebmbaj\u00eb leht\u00ebsisht k\u00ebt\u00eb balanc\u00eb. <\/p>\n

<\/p>\n

Kush i nevojitet k\u00ebtij mrekullie?<\/h2>\n

<\/p>\n

Nga nj\u00ebra an\u00eb, mund t\u00eb thuhet se n\u00eb treg tashm\u00eb ka lojtar\u00eb, t\u00eb cil\u00ebt kan\u00eb zgjidhje serioze n\u00eb fush\u00ebn e hiper-konvergjenc\u00ebs, dhe ku ne, n\u00eb thelb, po hyjm\u00eb. Kjo duket se \u00ebsht\u00eb nj\u00eb pohim i 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, ndonj\u00ebher\u00eb njer\u00ebzit thjesht nuk dinin se k\u00ebto zgjidhje ekzistonin, ndonj\u00ebher\u00eb k\u00ebt\u00eb e shihnin si t\u00eb shtrenjt\u00eb, n\u00eb disa raste kishte teste t\u00eb d\u00ebshtuara t\u00eb zgjidhjeve alternative, dhe n\u00eb disa raste ndalohen blerjet p\u00ebr shkak t\u00eb sanksioneve. N\u00eb p\u00ebrgjith\u00ebsi, fusha doli t\u00eb ishte e paprekur, prandaj ne vendos\u00ebm t\u00eb fillojm\u00eb nj\u00eb pun\u00eb t\u00eb re))). <\/p>\n

<\/p>\n

Kur \u00ebsht\u00eb HHD 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 p\u00ebrdorim skem\u00ebn klasike me S\u00c7D dhe kur \u2013 hiperconvergent? Shum\u00eb kompani \u2013 prodhues t\u00eb GKS (ve\u00e7an\u00ebrisht ata q\u00eb nuk kan\u00eb S\u00c7D n\u00eb portofolin e tyre) thon\u00eb: \"S\u00c7D po kalon, vet\u00ebm hiperconvergent!\". Ky \u00ebsht\u00eb nj\u00eb pohim i guximsh\u00ebm, por nuk e reflekton plot\u00ebsisht realitetin. <\/p>\n

<\/p>\n

Sinqerisht, tregu i S\u00c7D-ve po kalon n\u00eb drejtim t\u00eb hiperconvergent\u00ebve dhe zgjidhjeve t\u00eb ngjashme, por gjithmon\u00eb ka \"por\".<\/p>\n

<\/p>\n

S\u00eb pari, qendrat e t\u00eb dh\u00ebnave dhe infrastrukturat IT t\u00eb nd\u00ebrtuara sipas skem\u00ebs klasike me S\u00c7D nuk mund t\u00eb p\u00ebrshtaten aq leht\u00eb, prandaj modernizimi dhe nd\u00ebrtimi i tillave \u00ebsht\u00eb ende nj\u00eb trash\u00ebgimi p\u00ebr 5-7 vitet e ardhshme.<\/p>\n

<\/p>\n

S\u00eb dyti, ato infrastruktura q\u00eb po nd\u00ebrtohen aktualisht n\u00eb mas\u00eb (duke u referuar RF) po nd\u00ebrtohen sipas skem\u00ebs klasike me p\u00ebrdorimin e S\u00c7D dhe jo sepse njer\u00ebzit nuk din\u00eb p\u00ebr hiperconvergent\u00ebt, por sepse tregu i hiperconvergent\u00ebve \u00ebsht\u00eb i ri, zgjidhjet dhe standardet ende nuk jan\u00eb formuar, specialist\u00ebt IT ende nuk jan\u00eb trajnuar, ka pak p\u00ebrvoj\u00eb dhe duhet t\u00eb nd\u00ebrtohen qendrat e t\u00eb dh\u00ebnave k\u00ebtu dhe tani. Dhe kjo prirje do t\u00eb vazhdoj\u00eb edhe p\u00ebr 3-5 vite (dhe pastaj nj\u00eb trash\u00ebgimi, shiko pika 1).<\/p>\n

<\/p>\n

S\u00eb treti, ka nj\u00eb kufizim t\u00eb past\u00ebr teknik n\u00eb vonesat shtes\u00eb t\u00eb vogla prej 2 milisekondash n\u00eb shkruarje (pa marr\u00eb parasysh cache-in lokal, sigurisht), t\u00eb cilat jan\u00eb kosto p\u00ebr ruajtjen e ndar\u00eb. <\/p>\n

<\/p>\n

Dhe mos harrojm\u00eb p\u00ebrdorimin e server\u00ebve fizik\u00eb t\u00eb m\u00ebdhenj, t\u00eb cilat preferojn\u00eb skalimin vertikal t\u00eb sistemit t\u00eb diskut.<\/p>\n

<\/p>\n

Ka shum\u00eb detyra t\u00eb nevojshme dhe popullore, ku S\u00c7D sillet m\u00eb mir\u00eb se GKS. Sigurisht, prodhuesit q\u00eb nuk kan\u00eb S\u00c7D n\u00eb portofolin e tyre nuk do t\u00eb bien dakord me ne, por ne jemi t\u00eb gatsh\u00ebm t\u00eb argumentohemi. 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 t\u00eb S\u00c7D dhe GKS, ku do t\u00eb demonstrojm\u00eb qart\u00eb se n\u00eb cilat kushte performojn\u00eb m\u00eb mir\u00eb.<\/p>\n

<\/p>\n

N\u00eb cilat zgjidhje hiperconvergente do t\u00eb punojn\u00eb m\u00eb mir\u00eb se S\u00c7D?<\/h3>\n

<\/p>\n

Duke u bazuar n\u00eb th\u00ebniet m\u00eb sip\u00ebr, mund t\u00eb nxjerrim tri p\u00ebrfundime t\u00eb qarta: <\/p>\n

<\/p>\n

    \n
  1. Aty ku vonesat shtes\u00eb prej 2 milisekondash n\u00eb shkruarje, t\u00eb cilat shfaqen gjithmon\u00eb n\u00eb \u00e7do produktiv (k\u00ebshtu q\u00eb nuk po flasim p\u00ebr sintetiken, sepse n\u00eb sintetike mund t\u00eb tregoni edhe nanosekonda), jan\u00eb t\u00eb pranueshme, hiperconvergent i p\u00ebrshtatet.<\/li>\n
  2. Aty ku ngarkohet nga servera fizik\u00eb t\u00eb m\u00ebdhenj mund t\u00eb shnd\u00ebrrohet n\u00eb shum\u00eb t\u00eb vogla virtuale dhe t\u00eb shp\u00ebrndahen n\u00eb node, atje gjithashtu do t\u00eb pikaset si\u00e7 duhet hyperconverged.<\/li>\n
  3. Aty ku shkall\u00ebzimi horizontal \u00ebsht\u00eb m\u00eb prioritare se ai vertical, do t\u00eb pritet gjithashtu q\u00eb GKS t\u00eb p\u00ebrshtatet n\u00eb m\u00ebnyr\u00eb t\u00eb shk\u00eblqyer.<\/li>\n<\/ol>\n

    <\/p>\n

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

    <\/p>\n

      \n
    1. T\u00eb gjitha sh\u00ebrbimet standarde t\u00eb infrastruktur\u00ebs (sh\u00ebrbimi i katalog\u00ebve, posta, SED, server\u00ebt e skedar\u00ebve, sistemi ERP dhe BI t\u00eb vogla ose t\u00eb mesme etj.). Ne i quajm\u00eb k\u00ebto \"llogaritje t\u00eb p\u00ebrbashk\u00ebta\". <\/li>\n
    2. Infrastruktura e ofruesve t\u00eb sh\u00ebrbimeve n\u00eb cloud, ku \u00ebsht\u00eb e nevojshme t\u00eb zgjerohet horizontalisht shpejt dhe standardizuar dhe t\u00eb priten leht\u00ebsisht nj\u00eb num\u00ebr i madh makinash virtuale p\u00ebr klient\u00ebt.<\/li>\n
    3. Infrastruktura e skripteve virtuale<\/a> (VDI), ku shum\u00eb makina virtuale t\u00eb vogla t\u00eb p\u00ebrdoruesve aktivizohen dhe notojn\u00eb qet\u00ebsisht brenda nj\u00eb klasteri uniforme.<\/li>\n
    4. Rrjetet filial, ku n\u00eb \u00e7do filial \u00ebsht\u00eb e nevojshme t\u00eb arrihet nj\u00eb infrastruktur\u00eb standarde, me q\u00ebndrim t\u00eb besuesh\u00ebm, por nj\u00ebkoh\u00ebsisht t\u00eb p\u00ebrballueshme nga 15-20 makina virtuale.<\/li>\n
    5. \u00c7do llogaritje e shp\u00ebrndar\u00eb (sh\u00ebrbimet big data, p\u00ebr shembull). Aty ku ngarkesa shkon jo \"thell\u00eb\", por \"gjer\u00eb\". <\/li>\n
    6. Mjedise testuese, ku jan\u00eb t\u00eb pranueshme vonesa t\u00eb vogla, por ka kufizime buxhetore, pasi 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 kemi vendosur theksin tek to (deri tani me sukses). Mund t\u00eb ndodhi q\u00eb kjo t\u00eb ndryshoj\u00eb s\u00eb shpejti, pasi bota nuk q\u00ebndron n\u00eb vend.<\/p>\n

      <\/p>\n

      Pra\u2026<\/h3>\n

      <\/p>\n

      Kjo \u00ebsht\u00eb pjesa e par\u00eb e nj\u00eb cikli t\u00eb madh artikujsh, n\u00eb artikullin e ardhsh\u00ebm ne 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 debata 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\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\udd47Zgjidhja hyperconverged AERODISK vAIR. Baza \u2014 sistemi i skedar\u00ebve ARDFS | ProHoster","description":"","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: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","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"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}]}}