{"id":37528,"date":"2019-10-31T22:18:10","date_gmt":"2019-10-31T19:18:10","guid":{"rendered":"https:\/\/prohoster.info\/blog\/hranilishha-v-kubernetes-openebs-vs-rook-ceph-vs-rancher-longhorn-vs-storageos-vs-robin-vs-portworx-vs-linstor\/"},"modified":"2019-10-31T22:18:10","modified_gmt":"2019-10-31T19:18:10","slug":"hranilishha-v-kubernetes-openebs-vs-rook-ceph-vs-rancher-longhorn-vs-storageos-vs-robin-vs-portworx-vs-linstor","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/hranilishha-v-kubernetes-openebs-vs-rook-ceph-vs-rancher-longhorn-vs-storageos-vs-robin-vs-portworx-vs-linstor","title":{"rendered":"Kubernetes Storage: OpenEBS vs Rook (Ceph) vs Rancher Longhorn vs StorageOS vs Robin vs Portworx vs Linstor","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Kubernetes<\/p>\n

<\/p>\n

Risi!<\/strong>. N\u00eb komentet, nj\u00eb nga lexuesit sugjeroi t\u00eb provohej Linstor<\/a><\/noindex> (ndoshta ai po punon me t\u00eb vet\u00eb), prandaj e shtova nj\u00eb seksion n\u00eb lidhje me k\u00ebt\u00eb zgjidhje. Gjithashtu shkruaja nj\u00eb postim mbi at\u00eb se si ta instaloni<\/a><\/noindex>, sepse procesi \u00ebsht\u00eb shum\u00eb ndryshe nga t\u00eb tjer\u00ebt.<\/p>\n

<\/p>\n

Po t\u00eb jet\u00eb e sinqert\u00eb, un\u00eb u dor\u00ebzova dhe hoqa dor\u00eb nga Kubernetes<\/a><\/noindex> (sidoqoft\u00eb, p\u00ebr tani). Do t\u00eb p\u00ebrdor Heroku<\/a><\/noindex>. Pse? P\u00ebr shkak t\u00eb ruajtjes! Kush mund t\u00eb mendonte q\u00eb do t\u00eb merresha m\u00eb shum\u00eb me ruajtjet sesa me Kubernetes vet\u00eb. Un\u00eb po p\u00ebrdor Hetzner Cloud<\/a><\/noindex>, sepse \u00ebsht\u00eb e p\u00ebrballueshme dhe performanca \u00ebsht\u00eb e mir\u00eb, dhe q\u00eb nga fillimi un\u00eb kam p\u00ebrgatitur klaster\u00eb me ndihm\u00ebn e Rancher<\/a><\/noindex>. Nuk kam provuar sh\u00ebrbimet e menaxhuara t\u00eb Kubernetes nga Google\/Amazon\/Microsoft\/DigitalOcean etj., sepse doja t\u00eb m\u00ebsoja gjith\u00e7ka vet\u00eb. Gjithashtu, jam kursimtar.<\/p>\n

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

K\u00ebshtu q\u00eb po, kalova shum\u00eb koh\u00eb duke u p\u00ebrpjekur t\u00eb vendosja se cila ruajtje t\u00eb zgjidhja, kur po shqyrtoja stakun e mundsh\u00ebm p\u00ebr Kubernetes. Preferoj zgjidhjet me kod t\u00eb hapur, dhe jo vet\u00ebm p\u00ebr shkak t\u00eb \u00e7mimit, por gjithashtu kam shqyrtuar disa opsione t\u00eb paguara nga kurioziteti, sepse ata kan\u00eb versione falas me kufizime. Kam marr\u00eb disa shifra nga testet e fundit, kur krahasoja opsionet e ndryshme dhe ato mund t\u00eb jen\u00eb interesante p\u00ebr ata q\u00eb studiojn\u00eb ruajtjen n\u00eb Kubernetes. Megjithat\u00eb, personalisht, un\u00eb tani kam hequr dor\u00eb nga Kubernetes. Dua gjithashtu t\u00eb p\u00ebrmend driverin CSI<\/a><\/noindex>, me t\u00eb cilin mund t\u00eb p\u00ebrgatis lloje Hetzner Cloud direkt, por nuk e kam provuar ende. Kam b\u00ebr\u00eb hulumtime p\u00ebr ruajtjet e definuara nga programi n\u00eb cloud, sepse m\u00eb nevojitej replikimi dhe mund\u00ebsia p\u00ebr t\u00eb lidhur shpejt lloje t\u00eb p\u00ebrhershme n\u00eb \u00e7do nod\u00eb, ve\u00e7an\u00ebrisht n\u00eb rast t\u00eb d\u00ebshtimit t\u00eb nodave dhe situatave t\u00eb ngjashme. Disa zgjidhje ofrojn\u00eb snapse n\u00eb koh\u00eb dhe backupe off site, q\u00eb \u00ebsht\u00eb e leverdisshme.<\/p>\n

<\/p>\n

Kam testuar 6-7 zgjidhje p\u00ebr ruajtje:<\/p>\n

<\/p>\n

OpenEBS<\/a><\/noindex><\/h3>\n

<\/p>\n

, si\u00e7 e thash\u00eb m\u00eb par\u00eb, pasi kam testuar shumic\u00ebn e opsioneve nga lista, fillimisht u ndala te OpenEBS. OpenEBS \u00ebsht\u00eb shum\u00eb e leht\u00eb p\u00ebr tu instaluar dhe p\u00ebrdorur, por, p\u00ebr t\u00eb qen\u00eb e sinqert\u00eb, pas testeve me t\u00eb dh\u00ebna reale n\u00ebn ngarkes\u00eb, performanca e tij m\u00eb zhg\u00ebnjeu. Ky \u00ebsht\u00eb nj\u00eb projekt me kod t\u00eb hapur dhe zhvilluesit n\u00eb kanalin e tyre n\u00eb postimin e kaluar<\/a><\/noindex>, pasi q\u00eb provoi shumic\u00ebn e mund\u00ebsive nga lista, n\u00eb fillim u ndala te OpenEBS. OpenEBS \u00ebsht\u00eb shum\u00eb e leht\u00eb p\u00ebr t'u instaluar dhe p\u00ebrdorur, por, p\u00ebr t\u00eb qen\u00eb e sinqert\u00eb, pas testeve me t\u00eb dh\u00ebna reale n\u00ebn ngarkes\u00eb, performanca e tij m\u00eb zhg\u00ebnjeu. Ky \u00ebsht\u00eb nj\u00eb projekt me burim t\u00eb hapur, dhe zhvilluesit e tij jan\u00eb Slack<\/a><\/noindex> gjithmon\u00eb m\u00eb ndihmonin kur kisha nevoj\u00eb p\u00ebr asistenc\u00eb. Fatkeq\u00ebsisht, ka performanc\u00eb shum\u00eb t\u00eb ul\u00ebt n\u00eb krahasim me opsionet e tjera, prandaj isha i detyruar t\u00eb b\u00ebja testet p\u00ebrs\u00ebri. Tani OpenEBS ka 3 motor\u00eb ruajtje, por un\u00eb po publikoj rezultatet e benchmark p\u00ebr cStor. Nuk kam t\u00eb dh\u00ebna p\u00ebr Jiva dhe LocalPV.<\/p>\n

<\/p>\n

Me fjal\u00eb t\u00eb thjeshta, Jiva \u00ebsht\u00eb pak m\u00eb e shpejt\u00eb, ndersa LocalPV \u00ebsht\u00eb ndoshta m\u00eb e shpejt\u00eb, pa asnj\u00ebsoj, se benchmarku i diskut q\u00eb i ka drejtp\u00ebrdrejt. Problemi me LocalPV \u00ebsht\u00eb se mund t\u00eb qaseni n\u00eb at\u00eb vet\u00ebm n\u00eb nod\u00ebn ku \u00ebsht\u00eb p\u00ebrgatitur, dhe nuk ka replikim t\u00eb asnj\u00eb lloji. Kam pasur disa probleme me rikuperimin e backuput p\u00ebrmes Velero<\/a><\/noindex> n\u00eb nj\u00eb klaster t\u00eb ri, sepse emrat e nodave ishin t\u00eb ndrysh\u00ebm. Kur b\u00ebhet fjal\u00eb p\u00ebr backupe, cStor ka nj\u00eb plugin p\u00ebr Velero<\/a><\/noindex>, me t\u00eb cilin mund t\u00eb b\u00ebni backupe off site t\u00eb snapseve n\u00eb koh\u00eb, q\u00eb \u00ebsht\u00eb m\u00eb e leht\u00eb sesa backupe n\u00eb nivelin e skedareve me Velero-Restic. Un\u00eb shkrova disa skripta<\/a><\/noindex>, \u0447\u0442\u043e\u0431\u044b \u0431\u044b\u043b\u043e \u043f\u0440\u043e\u0449\u0435 \u0443\u043f\u0440\u0430\u0432\u043b\u044f\u0442\u044c \u0431\u044d\u043a\u0430\u043f\u0430\u043c\u0438 \u0438 \u0432\u043e\u0441\u0441\u0442\u0430\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u044f\u043c\u0438 \u0441 \u044d\u0442\u0438\u043c \u043f\u043b\u0430\u0433\u0438\u043d\u043e\u043c. \u0412 \u0446\u0435\u043b\u043e\u043c, \u043c\u043d\u0435 \u043e\u0447\u0435\u043d\u044c \u043d\u0440\u0430\u0432\u0438\u0442\u0441\u044f OpenEBS, \u043d\u043e \u0432\u043e\u0442 \u0435\u0433\u043e \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c…<\/p>\n

<\/p>\n

Rook<\/a><\/noindex><\/h3>\n

<\/p>\n

Rook gjithashtu ka kod t\u00eb hapur, dhe p\u00ebrve\u00e7 opsioneve t\u00eb tjera n\u00eb list\u00eb, dallohet si nj\u00eb orkestrim ruajtjeje q\u00eb kryen detyra t\u00eb komplikuara p\u00ebr menaxhimin e ruajtjes me backend t\u00eb ndrysh\u00ebm, si\u00e7 \u00ebsht\u00eb Ceph<\/a><\/noindex>, EdgeFS<\/a><\/noindex> dhe t\u00eb tjer\u00eb, q\u00eb e b\u00ebn pun\u00ebn shum\u00eb m\u00eb t\u00eb leht\u00eb. Kam pasur probleme me EfgeFS kur e provova disa muaj m\u00eb par\u00eb, k\u00ebshtu q\u00eb kam testuar kryesisht me Ceph. Ceph ofron jo vet\u00ebm ruajtje blloqesh, por edhe ruajtje objektesh, e cila \u00ebsht\u00eb e p\u00ebrputhshme me S3\/Swift dhe sistemin e skedar\u00ebve t\u00eb shp\u00ebrndar\u00eb. Ajo q\u00eb m\u00eb p\u00eblqen te Ceph \u00ebsht\u00eb mund\u00ebsia p\u00ebr t\u00eb shp\u00ebrndar\u00eb t\u00eb dh\u00ebnat e llojeve n\u00eb disa disqe, q\u00eb lloji t\u00eb p\u00ebrdor\u00eb m\u00eb shum\u00eb hap\u00ebsir\u00eb ruajtjeje sesa mund t\u00eb p\u00ebrmbaj\u00eb nj\u00eb disk i vet\u00ebm. Kjo \u00ebsht\u00eb shum\u00eb e dobishme. Nj\u00eb tjet\u00ebr funksion i shk\u00eblqyer \u00ebsht\u00eb kur shtoni disqe n\u00eb klaster, ai automatikisht ri-shp\u00ebrndan t\u00eb dh\u00ebnat n\u00eb t\u00eb gjith\u00eb disqet.<\/p>\n

<\/p>\n

N\u00eb Ceph ka snapse, por, sa di un\u00eb, ato nuk mund t\u00eb p\u00ebrdoren direkt n\u00eb Rook\/Kubernetes. Sidoqoft\u00eb, nuk kam hyr\u00eb thell\u00eb n\u00eb k\u00ebt\u00eb. Nd\u00ebrkoh\u00eb, nuk ka backupe off site, k\u00ebshtu q\u00eb do t\u00eb duhet t\u00eb p\u00ebrdorni di\u00e7ka me Velero\/Restic, por k\u00ebtu vet\u00ebm backupe n\u00eb nivelin e skedareve, e jo snapse n\u00eb koh\u00eb. Megjithat\u00eb, n\u00eb Rook m\u00eb ka p\u00eblqyer shum\u00eb puna e thjesht\u00eb me Ceph - ai fsheh pothuajse t\u00eb gjitha gj\u00ebrat e komplikuara dhe ofron mjete p\u00ebr t\u00eb komunikuar me Ceph drejtp\u00ebrdrejt p\u00ebr diagnostikim. Fatkeq\u00ebsisht, gjat\u00eb testeve t\u00eb stresit t\u00eb volumeve t\u00eb Ceph, kam pasur vazhdimisht k\u00ebt\u00eb problem<\/a><\/noindex>, p\u00ebr t\u00eb cilin Ceph b\u00ebhet i paq\u00ebndruesh\u00ebm. Deri tani nuk \u00ebsht\u00eb e qart\u00eb n\u00ebse \u00ebsht\u00eb nj\u00eb gabim n\u00eb vet\u00eb Ceph apo n\u00eb m\u00ebnyr\u00ebn se si Rook menaxhon Ceph. Kam b\u00ebr\u00eb disa ndryshime n\u00eb konfigurimet e memories dhe situata p\u00ebrmir\u00ebsua, por problemi nuk u zgjidh plot\u00ebsisht. Ceph ka nj\u00eb performanc\u00eb t\u00eb mir\u00eb, si\u00e7 e tregon benchmarket m\u00eb posht\u00eb. Gjithashtu, ka nj\u00eb panel t\u00eb mir\u00eb monitorimi.<\/p>\n

<\/p>\n

Rancher Longhorn<\/a><\/noindex><\/h3>\n

<\/p>\n

M\u00eb p\u00eblqen shum\u00eb Longhorn. M\u00eb duket se \u00ebsht\u00eb nj\u00eb zgjidhje e q\u00eblluar. Megjithat\u00eb, vet\u00eb zhvilluesit (Rancher Labs) pranojn\u00eb se p\u00ebr ambientin e pun\u00ebs nuk \u00ebsht\u00eb ende i p\u00ebrshtatsh\u00ebm, dhe kjo duket. Ka kod t\u00eb hapur dhe performanc\u00eb t\u00eb mir\u00eb (edhe pse optimizimi nuk \u00ebsht\u00eb b\u00ebr\u00eb ende), por volume jan\u00eb shum\u00eb t\u00eb ngadalta n\u00eb lidhje me podin, dhe n\u00eb rastet m\u00eb t\u00eb k\u00ebqija, mund t\u00eb zgjas\u00eb 15\u201316 minuta, ve\u00e7an\u00ebrisht pas rikthimit t\u00eb nj\u00eb backup-i t\u00eb madh ose p\u00ebrmir\u00ebsimit t\u00eb ngarkes\u00ebs s\u00eb pun\u00ebs. Ka snapshot-e dhe backup-e jasht\u00eb p\u00ebr k\u00ebto snapshot-e, por ato p\u00ebrfshihen vet\u00ebm p\u00ebr volume, prandaj gjithsesi do t'ju duhet di\u00e7ka si Velero p\u00ebr backup-in e burimeve t\u00eb tjera. Backup-et dhe rikthimet jan\u00eb shum\u00eb t\u00eb besueshme, por jasht\u00ebzakonisht t\u00eb ngadalta. Serious, thjesht jasht\u00ebzakonisht t\u00eb ngadalta. P\u00ebrdorimi i burimeve t\u00eb procesorit dhe ngarkesa e sistemit shpesh rriten gjat\u00eb pun\u00ebs me t\u00eb dh\u00ebna me volum t\u00eb mes\u00ebm n\u00eb Longhorn. Ka nj\u00eb panel monitorimi t\u00eb dobish\u00ebm p\u00ebr t\u00eb menaxhuar Longhorn. Kam th\u00ebn\u00eb tashm\u00eb se m\u00eb p\u00eblqen Longhorn, por k\u00ebrkon pun\u00eb t\u00eb madhe.<\/p>\n

<\/p>\n

StorageOS<\/a><\/noindex><\/h3>\n

<\/p>\n

StorageOS \u00ebsht\u00eb prodhimi i par\u00eb me pages\u00eb n\u00eb list\u00eb. Ka nj\u00eb version p\u00ebr zhvillues me nj\u00eb madh\u00ebsi t\u00eb kufizuar t\u00eb ruajtjes q\u00eb menaxhohet prej 500 GB, por numri i nyjeve nuk \u00ebsht\u00eb mendoj i kufizuar. N\u00eb departamentin e shitjeve m\u00eb than\u00eb se \u00e7mimi fillon nga $125 n\u00eb muaj p\u00ebr 1 TB, n\u00ebse e mbaj mend sakt\u00eb. Ka nj\u00eb panel monitorimi baz\u00eb dhe nj\u00eb CLI t\u00eb dobish\u00ebm, por me performanc\u00ebn ndodhin gj\u00ebra t\u00eb \u00e7uditshme: n\u00eb disa benchmarke ajo \u00ebsht\u00eb mjaft e pranueshme, por n\u00eb testin e stresit t\u00eb volumeve shpejt\u00ebsia nuk m\u00eb p\u00eblqeu fare. N\u00eb p\u00ebrgjith\u00ebsi, nuk di \u00e7far\u00eb t\u00eb them. Prandaj nuk m\u00eb ndoqi shum\u00eb. Nuk ka backup-e jasht\u00eb dhe do t\u00eb duhet gjithashtu t\u00eb p\u00ebrdorni Velero me Restic p\u00ebr backupin e volumeve. E \u00e7uditshme, pasi prodhimi \u00ebsht\u00eb me pages\u00eb. Po ashtu, zhvilluesit nuk ishin shum\u00eb t\u00eb interesuar p\u00ebr t\u00eb komunikuar n\u00eb Slack.<\/p>\n

<\/p>\n

Robin<\/a><\/noindex><\/h3>\n

<\/p>\n

M\u00eb p\u00ebrmendi Robin n\u00eb Reddit nga drejtori i tyre teknik. Nuk kisha d\u00ebgjuar m\u00eb par\u00eb p\u00ebr t\u00eb. Ndoshta sepse po k\u00ebrkoja zgjidhje falas, ndryshe nga Robin q\u00eb \u00ebsht\u00eb me pages\u00eb. Ata kan\u00eb nj\u00eb version falas mjaft bujar me ruajtje prej 10 TB dhe tre nyje. N\u00eb p\u00ebrgjith\u00ebsi, produkti \u00ebsht\u00eb mjaft i mir\u00eb dhe me funksionalitete t\u00eb k\u00ebndshme. Ka nj\u00eb CLI t\u00eb shk\u00eblqyer, por ajo q\u00eb \u00ebsht\u00eb m\u00eb e mira \u00ebsht\u00eb se mund t\u00eb b\u00ebni snapshot dhe backup t\u00eb gjith\u00eb aplikacionit (n\u00eb selektorin e burimeve quhet l\u00ebshime Helm ose \"flex apps\"), duke p\u00ebrfshir\u00eb volume dhe burime t\u00eb tjera, k\u00ebshtu q\u00eb mund t\u00eb shmangni Velero. Dhe gjith\u00e7ka do t\u00eb ishte e shk\u00eblqyer, n\u00ebse nuk do t\u00eb kishte nj\u00eb detaj t\u00eb vog\u00ebl: n\u00ebse rikthen (ose \"importon\", si\u00e7 quhet n\u00eb Robin) aplikacionin n\u00eb nj\u00eb klaster t\u00eb ri\u2014p\u00ebr shembull, n\u00eb rastin e rikthimit pas nj\u00eb aksidenti\u2014rikthimi, natyrisht, funksionon, por nuk mund t\u00eb vazhdohet backupi i aplikacionit. N\u00eb k\u00ebt\u00eb l\u00ebshim, kjo thjesht nuk \u00ebsht\u00eb e mundur, dhe zhvilluesit e konfirmuan. Kjo, leht\u00ebsisht, \u00ebsht\u00eb \u00e7uditshme, ve\u00e7an\u00ebrisht duke marr\u00eb parasysh avantazhet e tjera (p\u00ebr shembull, backupet dhe rikthimet jasht\u00ebzakonisht t\u00eb shpejta). Zhvilluesit premtojn\u00eb t\u00eb rregullojn\u00eb gjith\u00e7ka p\u00ebr l\u00ebshimin e ardhsh\u00ebm. Performanca, n\u00eb t\u00ebr\u00ebsi, \u00ebsht\u00eb e mir\u00eb, por kam v\u00ebn\u00eb re nj\u00eb \u00e7udit\u00ebsi: n\u00ebse nisni nj\u00eb benchmark direkt n\u00eb volumin e lidhur me hostin, shpejt\u00ebsia e leximit \u00ebsht\u00eb shum\u00eb m\u00eb e lart\u00eb se sa n\u00eb t\u00eb nj\u00ebjtin volum, por brenda podit. T\u00eb gjith\u00eb rezultatet e tjera jan\u00eb identike, por teorikisht nuk duhet t\u00eb ket\u00eb ndryshim. Edhe pse ata po punojn\u00eb mbi k\u00ebt\u00eb, isha i m\u00ebrzitur p\u00ebr problemin me rikthimin dhe backup-in\u2014m\u00eb dukej se p\u00ebrfundimisht e kisha gjetur zgjidhjen e duhur, dhe isha madje i gatsh\u00ebm t\u00eb paguaja p\u00ebr t\u00eb, kur do t\u00eb m\u00eb duhej m\u00eb shum\u00eb hap\u00ebsir\u00eb ose m\u00eb shum\u00eb server\u00eb.<\/p>\n

<\/p>\n

Portworx<\/a><\/noindex><\/h3>\n

<\/p>\n

K\u00ebtu nuk kam shum\u00eb p\u00ebr t\u00eb th\u00ebn\u00eb. Ky \u00ebsht\u00eb nj\u00eb produkt me pages\u00eb, po aq t\u00eb mrekulluesh\u00ebm sa dhe t\u00eb shtrenjt\u00eb. Performanca \u00ebsht\u00eb thjesht e mahnitshme. Deri tani, kjo \u00ebsht\u00eb treguesi m\u00eb i mir\u00eb. N\u00eb Slack m\u00eb than\u00eb se \u00e7mimi fillon nga $205 n\u00eb muaj p\u00ebr nod, si\u00e7 \u00ebsht\u00eb specifikuar n\u00eb tregun GKE t\u00eb Google. Nuk e di n\u00ebse do t\u00eb jet\u00eb m\u00eb lir\u00eb n\u00ebse blihet drejtperdrejt. N\u00eb \u00e7do rast, nuk mund ta lejoj veten nj\u00eb di\u00e7ka t\u00eb till\u00eb, k\u00ebshtu q\u00eb isha shum\u00eb i zhg\u00ebnjyer q\u00eb licenca e zhvilluesit (p\u00ebr deri n\u00eb 1 TB dhe 3 nod) \u00ebsht\u00eb praktikisht e pavler\u00eb me Kubernetes, n\u00ebse nuk jeni t\u00eb k\u00ebnaqur me p\u00ebrgatitjen statike. Shpresoja q\u00eb licenca korporative t\u00eb zvog\u00eblohej automatikisht n\u00eb nivelin e zhvilluesit pas periudh\u00ebs s\u00eb prov\u00ebs, por nuk ndodhi. Licenca e zhvilluesit mund t\u00eb p\u00ebrdoret vet\u00ebm drejtperdrejt me Docker, dhe konfigurimi n\u00eb Kubernetes \u00ebsht\u00eb shum\u00eb i r\u00ebnd\u00eb dhe i kufizuar. Sigurisht, preferoj burimin e hapur, por n\u00ebse do t\u00eb kisha para, do ta zgjedhja Portworx. Deri tani, performanca e tij \u00ebsht\u00eb thjesht e pakrahasueshme me opsionet e tjera.<\/p>\n

<\/p>\n

Linstor<\/a><\/noindex><\/h3>\n

<\/p>\n

E kam shtuar k\u00ebt\u00eb seksion pas publikimit t\u00eb postit, kur nj\u00eb lexues sugjeroi t\u00eb provonim Linstor. E provova dhe m\u00eb p\u00eblqeu! Por duhet t\u00eb ndaj m\u00eb shum\u00eb koh\u00eb p\u00ebr t\u00eb studiuar. Tani mund t\u00eb them se performanca nuk \u00ebsht\u00eb e keqe (rezultatet e benchmarkut i kam shtuar m\u00eb posht\u00eb). N\u00eb thelb, kam marr\u00eb t\u00eb nj\u00ebjt\u00ebn performanc\u00eb si p\u00ebr disksin direkt, pa asnj\u00eb humbje. (Mos pyetni pse Portworx ka numra m\u00eb t\u00eb mir\u00eb se benchmarku i disksit direkt. Nuk kam iden\u00eb. Magji, ndoshta.) Prandaj, Linstor deri tani duket shum\u00eb efikas. Installimi nuk \u00ebsht\u00eb aq i v\u00ebshtir\u00eb, por as aq i leht\u00eb sa opsionet e tjera. Fillimisht m\u00eb duhet t\u00eb instaloj Linstor (moduli i kernelit dhe mjetet\/ sh\u00ebrbimet) dhe t\u00eb konfiguroni LVM p\u00ebr thin provisioning dhe mb\u00ebshtetje p\u00ebr snapshots jasht\u00eb Kubernetes, direkt n\u00eb host, dhe pastaj t\u00eb krijoj burimet e nevojshme p\u00ebr t\u00eb p\u00ebrdorur depozitat nga Kubernetes. Nuk m\u00eb p\u00eblqeu q\u00eb nuk funksionoi n\u00eb CentOS dhe duhet t\u00eb p\u00ebrdorja Ubuntu. Nuk \u00ebsht\u00eb problem, megjithat\u00eb, por \u00ebsht\u00eb pak irritues, sepse n\u00eb dokumentacion (i cili, p\u00ebr mendimin tim, \u00ebsht\u00eb i shk\u00eblqyer) p\u00ebrmenden disa paketa q\u00eb nuk mund t\u00eb gjej n\u00eb depozitat e specifikuara Epel. N\u00eb Linstor ka snapshots, por nuk ka backup off-site, k\u00ebshtu q\u00eb p\u00ebrs\u00ebri duhet t\u00eb p\u00ebrdor Velero me Restic p\u00ebr backup t\u00eb volumet. Do t\u00eb preferoja snapshots p\u00ebrve\u00e7 backups n\u00eb nivelin e skedar\u00ebve, por kjo mund t\u00eb durohet, n\u00ebse zgjidhja \u00ebsht\u00eb efikase dhe e besueshme. Linstor ka kod t\u00eb hapur, por ofron mb\u00ebshtetje me pages\u00eb. N\u00ebse e kuptoj sakt\u00eb, mund ta p\u00ebrdorni pa kufizime, edhe n\u00ebse nuk keni nj\u00eb marr\u00ebveshje mb\u00ebshtetje, por duhet ta sqaroni. Nuk e di se sa e verifikuar \u00ebsht\u00eb Linstor p\u00ebr Kubernetes, por vet\u00eb niveli i ruajtjes \u00ebsht\u00eb jasht\u00eb Kubernetes dhe, sipas dukjes, zgjidhja nuk \u00ebsht\u00eb krijuar dje, prandaj ndoshta \u00ebsht\u00eb verifikuar n\u00eb kushte reale. A ka ndonj\u00eb zgjidhje k\u00ebtu q\u00eb do t\u00eb m\u00eb b\u00ebj\u00eb t\u00eb rishikoj dhe t\u00eb kthehem n\u00eb Kubernetes? Nuk e di, nuk e di. Duhet ende t\u00eb hetoj, t\u00eb shqyrtoj replikimin. Do e shohim. Por p\u00ebrshtypja e par\u00eb \u00ebsht\u00eb e mir\u00eb. Un\u00eb do t\u00eb preferoja me siguri t\u00eb p\u00ebrdorja klastrat e mia t\u00eb Kubernetes n\u00eb vend t\u00eb Heroku, p\u00ebr t\u00eb fituar m\u00eb shum\u00eb liri dhe p\u00ebr t\u00eb m\u00ebsuar di\u00e7ka t\u00eb re. Duke qen\u00eb se Linstor instalohet jo kaq leht\u00eb si t\u00eb tjer\u00ebt, s\u00eb shpejti do t\u00eb shkruaj nj\u00eb postim p\u00ebr k\u00ebt\u00eb.<\/p>\n

<\/p>\n

Benchmark<\/h3>\n

<\/p>\n

P\u00ebr fat t\u00eb keq, kam ruajtur pak sh\u00ebnime mbi krahasimin, sepse nuk mendova se do t\u00eb shkruaja p\u00ebr k\u00ebt\u00eb. Kam vet\u00ebm rezultatet e benchmarkut themelor fio dhe vet\u00ebm p\u00ebr klastra me nj\u00eb nod, k\u00ebshtu q\u00eb p\u00ebr konfigurimet e replikimit nuk kam ende numra. Por nga k\u00ebto rezultate mund t\u00eb marr\u00ebsh nj\u00eb ide t\u00eb p\u00ebraf\u00ebrt se \u00e7far\u00eb mund t\u00eb pres\u00ebsh nga secili opsion, sepse i kam krahasuar ato n\u00eb server\u00eb t\u00eb nj\u00ebjt\u00eb t\u00eb cloud, 4 b\u00ebrthama, 16 GB RAM, me nj\u00eb disk shtes\u00eb 100 GB p\u00ebr volumet e testuara. Kam realizuar benchmarket tri her\u00eb p\u00ebr \u00e7do zgjidhje dhe kam llogaritur rezultatin mesatar, duke resetuar gjithashtu serverin p\u00ebr \u00e7do produkt. E gjith\u00eb kjo nuk \u00ebsht\u00eb aspak shkencore, thjesht p\u00ebr t\u00eb kuptuar n\u00eb m\u00ebnyr\u00eb t\u00eb p\u00ebrgjithshme. N\u00eb teste t\u00eb tjera kam kopjuar 38 GB foto dhe video nga nj\u00eb volum dhe n\u00eb at\u00eb, p\u00ebr t\u00eb testuar leximin dhe shkruan, por fatkeq\u00ebsisht nuk kam ruajtur numrat. N\u00ebse e p\u00ebrmbledh: Portworx ishte shum\u00eb m\u00eb i shpejt\u00eb.<\/p>\n

<\/p>\n

P\u00ebr benchmarkun e volumit p\u00ebrdora k\u00ebt\u00eb manifest:<\/p>\n

<\/p>\n

kind: PersistentVolumeClaim\napiVersion: v1\nmetadata:\n  name: dbench\nspec:\n  storageClassName: ...\n  accessModes:\n    - ReadWriteOnce\n  resources:\n    requests:\n      storage: 5Gi\n---\napiVersion: batch\/v1\nkind: Job\nmetadata:\n  name: dbench\nspec:\n  template:\n    spec:\n      containers:\n      - name: dbench\n        image: sotoaster\/dbench:latest\n        imagePullPolicy: IfNotPresent\n        env:\n          - name: DBENCH_MOUNTPOINT\n            value: \/data\n          - name: FIO_SIZE\n            value: 1G\n        volumeMounts:\n        - name: dbench-pv\n          mountPath: \/data\n      restartPolicy: Never\n      volumes:\n      - name: dbench-pv\n        persistentVolumeClaim:\n          claimName: dbench\n  backoffLimit: 4<\/code><\/pre>\n
<\/p>\n
Fillova fillova fillova fillova.<\/p>\n
<\/p>\n
\"Kubernetes<\/a><\/noindex><\/p>\n
<\/p>\n
Fillova fillova fillova fillova.<\/p>\n
<\/p>\n
P\u00ebrfundimi<\/h3>\n
<\/p>\n
Fillova fillova fillova fillova.<\/p>\n
Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
\u041e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435!. \u0412 \u043a\u043e\u043c\u043c\u0435\u043d\u0442\u0430\u0445 \u043e\u0434\u0438\u043d \u0438\u0437 \u0447\u0438\u0442\u0430\u0442\u0435\u043b\u0435\u0439 \u043f\u0440\u0435\u0434\u043b\u043e\u0436\u0438\u043b \u043f\u043e\u043f\u0440\u043e\u0431\u043e\u0432\u0430\u0442\u044c Linstor (\u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e, \u043e\u043d \u0441\u0430\u043c \u043d\u0430\u0434 \u043d\u0438\u043c \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442), \u0442\u0430\u043a \u0447\u0442\u043e \u044f \u0434\u043e\u0431\u0430\u0432\u0438\u043b \u0440\u0430\u0437\u0434\u0435\u043b \u043e\u0431 \u044d\u0442\u043e\u043c \u0440\u0435\u0448\u0435\u043d\u0438\u0438. \u0415\u0449\u0435 \u044f \u043d\u0430\u043f\u0438\u0441\u0430\u043b \u043f\u043e\u0441\u0442 \u043e \u0442\u043e\u043c, \u043a\u0430\u043a \u0435\u0433\u043e \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u0438\u0442\u044c, \u043f\u043e\u0442\u043e\u043c\u0443 \u0447\u0442\u043e \u043f\u0440\u043e\u0446\u0435\u0441\u0441 \u0441\u0438\u043b\u044c\u043d\u043e \u043e\u0442\u043b\u0438\u0447\u0430\u0435\u0442\u0441\u044f \u043e\u0442 \u043e\u0441\u0442\u0430\u043b\u044c\u043d\u044b\u0445. \u0415\u0441\u043b\u0438 \u0447\u0435\u0441\u0442\u043d\u043e, \u044f \u0441\u0434\u0430\u043b\u0441\u044f \u0438 \u043e\u0442\u043a\u0430\u0437\u0430\u043b\u0441\u044f \u043e\u0442 Kubernetes (\u0432\u043e \u0432\u0441\u044f\u043a\u043e\u043c \u0441\u043b\u0443\u0447\u0430\u0435, \u043f\u043e\u043a\u0430). \u0411\u0443\u0434\u0443 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c Heroku. \u041f\u043e\u0447\u0435\u043c\u0443? […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":28163,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-37528","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":"Fillova fillova fillova fillova.","description":"Fillova fillova fillova fillova.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/hranilishha-v-kubernetes-openebs-vs-rook-ceph-vs-rancher-longhorn-vs-storageos-vs-robin-vs-portworx-vs-linstor","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\u0425\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0430 \u0432 Kubernetes: OpenEBS vs Rook (Ceph) vs Rancher Longhorn vs StorageOS vs Robin vs Portworx vs Linstor | ProHoster","og:description":"\u041e\u0431\u043d\u043e\u0432\u043b\u0435\u043d\u0438\u0435!. \u0412 \u043a\u043e\u043c\u043c\u0435\u043d\u0442\u0430\u0445 \u043e\u0434\u0438\u043d \u0438\u0437 \u0447\u0438\u0442\u0430\u0442\u0435\u043b\u0435\u0439 \u043f\u0440\u0435\u0434\u043b\u043e\u0436\u0438\u043b \u043f\u043e\u043f\u0440\u043e\u0431\u043e\u0432\u0430\u0442\u044c Linstor (\u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e, \u043e\u043d \u0441\u0430\u043c \u043d\u0430\u0434 \u043d\u0438\u043c \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442), \u0442\u0430\u043a \u0447\u0442\u043e \u044f \u0434\u043e\u0431\u0430\u0432\u0438\u043b \u0440\u0430\u0437\u0434\u0435\u043b \u043e\u0431 \u044d\u0442\u043e\u043c \u0440\u0435\u0448\u0435\u043d\u0438\u0438. \u0415\u0449\u0435 \u044f \u043d\u0430\u043f\u0438\u0441\u0430\u043b \u043f\u043e\u0441\u0442 \u043e \u0442\u043e\u043c, \u043a\u0430\u043a \u0435\u0433\u043e \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u0438\u0442\u044c, \u043f\u043e\u0442\u043e\u043c\u0443 \u0447\u0442\u043e \u043f\u0440\u043e\u0446\u0435\u0441\u0441 \u0441\u0438\u043b\u044c\u043d\u043e \u043e\u0442\u043b\u0438\u0447\u0430\u0435\u0442\u0441\u044f \u043e\u0442 \u043e\u0441\u0442\u0430\u043b\u044c\u043d\u044b\u0445. \u0415\u0441\u043b\u0438 \u0447\u0435\u0441\u0442\u043d\u043e, \u044f \u0441\u0434\u0430\u043b\u0441\u044f \u0438 \u043e\u0442\u043a\u0430\u0437\u0430\u043b\u0441\u044f \u043e\u0442 Kubernetes (\u0432\u043e \u0432\u0441\u044f\u043a\u043e\u043c \u0441\u043b\u0443\u0447\u0430\u0435, \u043f\u043e\u043a\u0430). \u0411\u0443\u0434\u0443 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u044c Heroku. \u041f\u043e\u0447\u0435\u043c\u0443?","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/hranilishha-v-kubernetes-openebs-vs-rook-ceph-vs-rancher-longhorn-vs-storageos-vs-robin-vs-portworx-vs-linstor","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:18:10+00:00","article:modified_time":"2019-10-31T19:18:10+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"37528","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-01-23 18:13:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 01:25:26","updated":"2026-01-23 18:13:20","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\/37528","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=37528"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/37528\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/28163"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=37528"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=37528"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=37528"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}