{"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":"Ruajtja e t\u00eb dh\u00ebnave n\u00eb Kubernetes: OpenEBS vs Rook (Ceph) vs Rancher Longhorn vs StorageOS vs Robin vs Portworx vs Linstor","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"Ruajtja<\/p>\n

<\/p>\n

Update!<\/strong>. One of the readers suggested trying Linstor<\/a><\/noindex> (perhaps he is working on it himself), so I added a section about this solution. I also wrote a post about how to install it<\/a><\/noindex>, because the process is quite different from others.<\/p>\n

<\/p>\n

To be honest, I gave up and turned away from Kubernetes<\/a><\/noindex> (for now at least). I will use Heroku<\/a><\/noindex>. Why? Because of storage! Who would have thought I would spend more time on storage than on Kubernetes itself. I'm using Hetzner Cloud<\/a><\/noindex>, because it's inexpensive and performs well, and right from the start I deployed clusters using Rancher<\/a><\/noindex>. I haven't tried managed Kubernetes services from Google\/Amazon\/Microsoft\/DigitalOcean, and others, because I wanted to learn everything myself. And I'm also cost-conscious.<\/p>\n

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

So yes, I spent a lot of time trying to decide which storage to choose when I was estimating a possible stack on Kubernetes. I prefer open-source solutions, not only because of the price, but I also explored a couple of paid options out of curiosity, because they offer free versions with limitations. I noted some figures from my recent tests comparing different options, which may interest those exploring storage in Kubernetes. Although personally, for now, I've parted ways with Kubernetes. I also want to mention the CSI driver<\/a><\/noindex>, which allows you to prepare Hetzner Cloud volumes directly, but I haven't tried it yet. I studied cloud software-defined storage because I needed replication and the ability to quickly attach persistent volumes to any node, especially in case of node failures and similar situations. Some solutions offer snapshots at a point in time and offsite backups, which is convenient.<\/p>\n

<\/p>\n

I tested 6-7 storage solutions:<\/p>\n

<\/p>\n

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

<\/p>\n

As I mentioned in the previous post<\/a><\/noindex>, after testing most options from the list, I initially settled on OpenEBS. OpenEBS is very easy to install and use, but to be honest, after tests with real data under load, its performance disappointed me. It's open-source, and the developers are on their Slack channel<\/a><\/noindex> kan\u00eb gjithmon\u00eb shum\u00eb t\u00eb ndihmojn\u00eb, kur kam pasur nevoj\u00eb p\u00ebr ndihm\u00eb. Fatkeq\u00ebsisht, ai ka nj\u00eb performanc\u00eb shum\u00eb t\u00eb ul\u00ebt n\u00eb krahasim me opsionet e tjera, prandaj pata nevoj\u00eb t\u00eb b\u00ebja testet p\u00ebrs\u00ebri. Tani OpenEBS ka 3 motor\u00eb ruajtjeje, por po publikoj rezultatet e benchmarkut p\u00ebr cStor. Nuk kam ende numra p\u00ebr Jiva dhe LocalPV.<\/p>\n

<\/p>\n

N\u00eb dy fjal\u00eb, Jiva \u00ebsht\u00eb pak m\u00eb e shpejt\u00eb, nd\u00ebrsa LocalPV \u00ebsht\u00eb v\u00ebrtet e shpejt\u00eb, ashtu si benchmark-u i diskut direkt. Problemi me LocalPV \u00ebsht\u00eb se aksesin mund ta fitosh vet\u00ebm n\u00eb nod\u00ebn ku \u00ebsht\u00eb p\u00ebrgatitur, dhe nuk ka replikim. Kam pasur disa probleme me rikuperimin e backup-it p\u00ebr Velero<\/a><\/noindex> n\u00eb klusterin e ri, sepse emrat e nod\u00ebs ishin t\u00eb ndrysh\u00ebm. N\u00ebse flasim p\u00ebr backup-et, cStor ka nj\u00eb plugin p\u00ebr Velero<\/a><\/noindex>, me t\u00eb cilin mund t\u00eb b\u00ebsh backup-e off-site t\u00eb snapshot-eve n\u00eb nj\u00eb moment t\u00eb caktuar, q\u00eb \u00ebsht\u00eb m\u00eb e p\u00ebrshtatshme se backup-et n\u00eb nivelin e skedar\u00ebve me Velero-Restic. Kam shkruar disa skripta<\/a><\/noindex>, p\u00ebr ta b\u00ebr\u00eb m\u00eb t\u00eb leht\u00eb menaxhimin e kopjeve rezerv\u00eb dhe rikuperimeve me k\u00ebt\u00eb plugin. N\u00eb p\u00ebrgjith\u00ebsi, m\u00eb p\u00eblqen shum\u00eb OpenEBS, por performanca e tij\u2026<\/p>\n

<\/p>\n

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

<\/p>\n

Rook gjithashtu ka kod t\u00eb hapur, dhe nga opsionet e tjera n\u00eb list\u00eb, ai dallon sepse \u00ebsht\u00eb nj\u00eb orkestrues ruajtjeje, i cili kryen detyra t\u00eb komplikuara p\u00ebr menaxhim ruajtjeje me backend t\u00eb ndryshme, p\u00ebr shembull Ceph<\/a><\/noindex>, EdgeFS<\/a><\/noindex> dhe t\u00eb tjera, 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 bllok\u00ebsh, por edhe ruajtje objektesh, e cila \u00ebsht\u00eb e p\u00ebrputhshme me S3\/Swift dhe nj\u00eb sistem skedar\u00ebsh t\u00eb shp\u00ebrndar\u00eb. Ajo q\u00eb m\u00eb p\u00eblqen n\u00eb Ceph \u00ebsht\u00eb mund\u00ebsia p\u00ebr t\u00eb shp\u00ebrndar\u00eb t\u00eb dh\u00ebnat e volumit n\u00eb disa disqe, k\u00ebshtu q\u00eb volumi mund t\u00eb p\u00ebrdor\u00eb m\u00eb shum\u00eb hap\u00ebsir\u00eb disku sesa mund t\u00eb ruhet n\u00eb nj\u00eb disk t\u00eb vet\u00ebm. Kjo \u00ebsht\u00eb e dobishme. Nj\u00eb ve\u00e7ori tjet\u00ebr e shk\u00eblqyer \u00ebsht\u00eb q\u00eb kur shton disqe n\u00eb kluster, ai automatikisht riban t\u00eb dh\u00ebnat n\u00eb t\u00eb gjitha disqet.<\/p>\n

<\/p>\n

Ceph ka snapshotet, por, sa e njohur, nuk mund t\u00eb p\u00ebrdoren drejtp\u00ebrdrejt n\u00eb Rook\/Kubernetes. Megjithat\u00eb, nuk jam thelluar shum\u00eb n\u00eb k\u00ebt\u00eb. Nuk ka backup off-site, k\u00ebshtu q\u00eb do t\u00eb duhet t\u00eb p\u00ebrdor\u00ebsh di\u00e7ka me Velero\/Restic, por aty jan\u00eb vet\u00ebm backupet n\u00eb nivelin e skedar\u00ebve dhe jo snapshotet n\u00eb nj\u00eb moment t\u00eb caktuar. Megjithat\u00eb, m\u00eb p\u00eblqeu shum\u00eb puna e thjesht\u00eb me Ceph n\u00eb Rook\u2014ai fsheh pothuajse t\u00eb gjith\u00eb gj\u00ebrat e komplikuara dhe ofron mjete p\u00ebr t\u00eb komunikuar drejtp\u00ebrdrejt me Ceph p\u00ebr t\u00eb zgjidhur problemet. Fatkeq\u00ebsisht, gjat\u00eb testimit t\u00eb stresit t\u00eb volumit t\u00eb Ceph, kam pasur vazhdimisht k\u00ebt\u00eb problem<\/a><\/noindex>, i cili e b\u00ebn Ceph t\u00eb paq\u00ebndruesh\u00ebm. Deri tani nuk \u00ebsht\u00eb e qart\u00eb n\u00ebse \u00ebsht\u00eb nj\u00eb defekt n\u00eb vet\u00eb Ceph ose nj\u00eb problem me m\u00ebnyr\u00ebn se si Rook menaxhon Ceph. Kisha luajtur me konfigurimet e memories dhe u b\u00eb m\u00eb mir\u00eb, por problemi nuk u zgjodh plot\u00ebsisht. Ceph ka nj\u00eb performanc\u00eb t\u00eb mir\u00eb, si\u00e7 dallohet nga benchmark-et m\u00eb posht\u00eb. Po ashtu, 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. Mendoj se \u00ebsht\u00eb nj\u00eb zgjidhje e perspektiv\u00ebs. 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 \u00ebsht\u00eb e dukshme. Ka burim t\u00eb hapur dhe performanc\u00eb t\u00eb mir\u00eb (pavar\u00ebsisht q\u00eb ende nuk kan\u00eb punuar n\u00eb optimizimin e saj), por volumet lidh\u00ebn shum\u00eb ngadal\u00eb me podin, duke zgjatur deri n\u00eb 15\u201316 minuta, sidomos pas rikuperimit t\u00eb nj\u00eb backup-i t\u00eb madh ose p\u00ebrmir\u00ebsimit t\u00eb ngarkes\u00ebs s\u00eb pun\u00ebs. Ka snapshotet dhe backupet off-site t\u00eb k\u00ebtyre snapshot-eve, por ato shtrihen vet\u00ebm p\u00ebr volumin, k\u00ebshtu q\u00eb ende do t\u00eb duhet di\u00e7ka si Velero p\u00ebr backupin e burimeve t\u00eb tjera. Backupet dhe rikuperimet jan\u00eb shum\u00eb t\u00eb besueshme, por jasht\u00ebzakonisht t\u00eb ngadalta. Marr\u00ebdh\u00ebnia me resurset e procesorit dhe ngarkesa e sistemit shpesh rriten kur punon me nj\u00eb sasi mesatare t\u00eb t\u00eb dh\u00ebnave n\u00eb Longhorn. Ka nj\u00eb panel monitorimi t\u00eb p\u00ebrshtatsh\u00ebm p\u00ebr t\u00eb menaxhuar Longhorn. Kisha th\u00ebn\u00eb q\u00eb m\u00eb p\u00eblqen Longhorn, por duhet t\u00eb punohet mir\u00eb mbi t\u00eb.<\/p>\n

<\/p>\n

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

<\/p>\n

StorageOS \u00ebsht\u00eb prodotti i par\u00eb me pages\u00eb n\u00eb list\u00eb. Ka nj\u00eb version p\u00ebr zhvilluesit me nj\u00eb madh\u00ebsi t\u00eb kufizuar t\u00eb ruajtjes s\u00eb menaxhuar prej 500 GB, por numri i nyjeve, mendoj, nuk \u00ebsht\u00eb i kufizuar. N\u00eb departamentin e shitjeve m\u00eb than\u00eb se \u00e7mimi fillon nga 125 dollar\u00eb n\u00eb muaj p\u00ebr 1 TB, n\u00ebse e mbaj mend sakt\u00eb. Ka nj\u00eb panel baz\u00eb monitorimi dhe nj\u00eb CLI t\u00eb p\u00ebrshtatsh\u00ebm, por performanca duket ka ndodhur di\u00e7ka e \u00e7uditshme: n\u00eb disa testime renditjeje \u00ebsht\u00eb mjaft e pranueshme, por n\u00eb testin e stresit t\u00eb volumeve, shpejt\u00ebsia m\u00eb la shum\u00eb p\u00ebr t\u00eb d\u00ebshiruar. N\u00eb thelb, nuk e di \u00e7far\u00eb t\u00eb them. Prandaj nuk e kam shqyrtuar shum\u00eb. K\u00ebtu nuk ka kopje rezerv\u00eb off site dhe do t\u00eb duhet t\u00eb p\u00ebrdor Velero me Restic p\u00ebr kopjimin e volumeve. E \u00e7uditshme, pasi produkti \u00ebsht\u00eb me pages\u00eb. Dhe gjithashtu zhvilluesit nuk kishin d\u00ebshir\u00eb t\u00eb komunikonin n\u00eb Slack.<\/p>\n

<\/p>\n

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

<\/p>\n

M\u00ebsova p\u00ebr Robin n\u00eb Reddit nga drejtori i tyre teknik. Nuk kisha d\u00ebgjuar ndonj\u00ebher\u00eb p\u00ebr t\u00eb. Ndoshta sepse k\u00ebrkoja zgjidhje falas, nd\u00ebrsa Robin \u00ebsht\u00eb me pages\u00eb. Ata kan\u00eb nj\u00eb version t\u00eb lir\u00eb mjaft bujar me nj\u00eb ruajtje prej 10 TB dhe tre node. N\u00eb p\u00ebrgjith\u00ebsi, produkti \u00ebsht\u00eb mjaft i mir\u00eb dhe me funksione t\u00eb k\u00ebndshme. Ka nj\u00eb CLI t\u00eb shk\u00eblqyer, por m\u00eb e mira \u00ebsht\u00eb se mund t\u00eb b\u00ebni nj\u00eb snapshot dhe backup t\u00eb gjith\u00eb aplikacionit (n\u00eb selektorin e burimeve quhet l\u00ebshime Helm ose \"flex apps\"), duke p\u00ebrfshir\u00eb volumin dhe burime t\u00eb tjera, k\u00ebshtu q\u00eb mund t\u00eb kaloni pa Velero. Dhe do t\u00eb ishte gjith\u00e7ka e shk\u00eblqyer, n\u00ebse nuk do t\u00eb ishte p\u00ebr nj\u00eb detaj t\u00eb vog\u00ebl: n\u00ebse rikthehet (ose \"importohet\", si\u00e7 quhet n\u00eb Robin) nj\u00eb aplikacion n\u00eb nj\u00eb klaster t\u00eb ri \u2014 p\u00ebr shembull, n\u00eb rastin e rikuperimit pas nj\u00eb katastrofe \u2014 rikthimi, sigurisht, punon, por nuk mund t\u00eb vazhdoj\u00eb backup-i i aplikacionit. N\u00eb k\u00ebt\u00eb l\u00ebshim, kjo thjesht nuk \u00ebsht\u00eb e mundur, dhe zhvilluesit e konfirmuan. Kjo, p\u00ebr ta th\u00ebn\u00eb but\u00eb, \u00ebsht\u00eb e \u00e7uditshme, ve\u00e7an\u00ebrisht kur merrni parasysh avantazhet e tjera (p\u00ebr shembull, backup-et dhe rikthimet jasht\u00ebzakonisht t\u00eb shpejta). Zhvilluesit premtojn\u00eb se do t\u00eb korrigjojn\u00eb gjith\u00e7ka deri n\u00eb l\u00ebshimin e ardhsh\u00ebm. Performanca, n\u00eb p\u00ebrgjith\u00ebsi, \u00ebsht\u00eb e mir\u00eb, por vura re nj\u00eb \u00e7udit\u00ebri: n\u00ebse ekzekuton nj\u00eb benchmark direkt n\u00eb volum, t\u00eb lidhur me hostin, shpejt\u00ebsia e leximit \u00ebsht\u00eb shum\u00eb m\u00eb e lart\u00eb se n\u00eb t\u00eb nj\u00ebjtin volum, por brenda pod-it. T\u00eb gjitha rezultatet e tjera jan\u00eb identike, por n\u00eb teori nuk duhet t\u00eb ket\u00eb ndonj\u00eb ndryshim. Edhe pse po punojn\u00eb mbi k\u00ebt\u00eb, isha i shqet\u00ebsuar p\u00ebr problemin me rikthimin dhe backup-in \u2014 m\u00eb dukej se p\u00ebrfundimisht kisha gjetur zgjidhjen e duhur, dhe isha madje i gatsh\u00ebm t\u00eb paguaja p\u00ebr t\u00eb, kur t\u00eb m\u00eb duhej m\u00eb shum\u00eb hap\u00ebsir\u00eb apo m\u00eb shum\u00eb servera.<\/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 i klas\u00ebs s\u00eb lart\u00eb sa i kushtuesh\u00ebm. P\u00ebrshtatshm\u00ebria \u00ebsht\u00eb thjesht mrekulli. Deri m\u00eb tani, ky \u00ebsht\u00eb treguesi m\u00eb i mir\u00eb. N\u00eb Slack m\u00eb than\u00eb se \u00e7mimi fillon nga 205 dollar\u00eb n\u00eb muaj p\u00ebr nod, si\u00e7 \u00ebsht\u00eb e sh\u00ebnuar n\u00eb tregun e GKE t\u00eb Google. Nuk e di n\u00ebse do t\u00eb jet\u00eb m\u00eb lir\u00eb n\u00ebse blihet direkt. N\u00eb \u00e7do rast, nuk mund ta lejoj dot nj\u00eb gj\u00eb t\u00eb till\u00eb, ndaj u ndjeva shum\u00eb dhe shum\u00eb i zhg\u00ebnjyer q\u00eb licenca e zhvilluesit (deri n\u00eb 1 TB dhe 3 nod) \u00ebsht\u00eb praktikisht e paefektshme me Kubernetes, p\u00ebrve\u00e7 n\u00ebse jeni t\u00eb k\u00ebnaqur me p\u00ebrgatitjen statike. Shpresoja se licenca e korporat\u00ebs do t\u00eb kalonte automatikisht n\u00eb nivelin e zhvilluesit n\u00eb fund t\u00eb periudh\u00ebs provuese, por nuk ndodhi. Licenca e zhvilluesit mund t\u00eb p\u00ebrdoret vet\u00ebm drejtp\u00ebrdrejt me Docker, dhe konfigurimi n\u00eb Kubernetes \u00ebsht\u00eb shum\u00eb i komplikuar dhe i kufizuar. Sigurisht, preferoj open source, por po t\u00eb kisha para, do t\u00eb zgjidhja me siguri Portworx. Deri tani, p\u00ebrformanca e tij \u00ebsht\u00eb thjesht e pa krahasueshme me opsionet e tjera.<\/p>\n

<\/p>\n

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

<\/p>\n

E shtova 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 hulumtoj m\u00eb shum\u00eb. Tani mund t\u00eb them se performanca \u00ebsht\u00eb e k\u00ebnaqshme (rezultatet e benchmarkut i kam shtuar m\u00eb posht\u00eb). N\u00eb thelb, mora t\u00eb nj\u00ebjt\u00ebn performanc\u00eb si me diskun e drejtp\u00ebrdrejt\u00eb, pa asnj\u00eb humbje. (Mos pyesni pse numrat p\u00ebr Portworx jan\u00eb m\u00eb t\u00eb mir\u00eb se benchmarku i diskut t\u00eb drejtp\u00ebrdrejt\u00eb. Nuk e di. Magji, ndoshta.) Pra, Linstor deri tani duket shum\u00eb efikase. Instalimi i tij nuk \u00ebsht\u00eb aspak i thjesht\u00eb, por as shum\u00eb i v\u00ebshtir\u00eb si opsionet e tjera. Fillimisht, m\u00eb duhej t\u00eb instaloj Linstor (moduli i b\u00ebrtham\u00ebs dhe mjetet\/ sh\u00ebrbimet) dhe t\u00eb konfiguroj LVM p\u00ebr thin provisioning dhe mb\u00ebshtetje p\u00ebr snapshotet jasht\u00eb Kubernetes, direkt n\u00eb host, pastaj t\u00eb krijoj burimet e nevojshme p\u00ebr t\u00eb p\u00ebrdorur magazin\u00ebn nga Kubernetes. Nuk m\u00eb p\u00eblqeu q\u00eb nuk funksionoi n\u00eb CentOS dhe m\u00eb duhej t\u00eb p\u00ebrdorja Ubuntu. Nuk \u00ebsht\u00eb tragjike, sigurisht, por \u00ebsht\u00eb pak e bezdisshme, sepse n\u00eb dokumentacion (i cili, p\u00ebr rastin e par\u00eb, \u00ebsht\u00eb shum\u00eb i mir\u00eb) p\u00ebrmenden disa paketa q\u00eb nuk mund t\u00eb gjej n\u00eb repositor\u00ebt e sh\u00ebnuar Epel. N\u00eb Linstor ka snapshotet, por jo backup-e off site, k\u00ebshtu q\u00eb k\u00ebtu isha s\u00ebrish i detyruar t\u00eb p\u00ebrdor Velero me Restic p\u00ebr backup-et e volumit. Do t\u00eb preferoja snapshotet n\u00eb vend t\u00eb backup-eve n\u00eb nivel skedari, por k\u00ebt\u00eb mund ta pranosh n\u00ebse zgjidhja \u00ebsht\u00eb e fuqishme dhe e besueshme. Linstor ka burim t\u00eb hapur, por ka mb\u00ebshtetje me pages\u00eb. N\u00ebse kuptoj drejt, mund ta p\u00ebrdor\u00ebsh pa kufizime, edhe n\u00ebse nuk ke nj\u00eb marr\u00ebveshje mb\u00ebshtetjeje, por kjo duhet t\u00eb sqarohen. Nuk e di sa e testuar \u00ebsht\u00eb Linstor p\u00ebr Kubernetes, por niveli i ruajtjes \u00ebsht\u00eb jasht\u00eb Kubernetes dhe, duket se zgjidhja nuk ka dal\u00eb dje, k\u00ebshtu q\u00eb ndoshta \u00ebsht\u00eb testuar n\u00eb kushte reale. Ka ndonj\u00eb zgjidhje k\u00ebtu q\u00eb do t\u00eb m\u00eb b\u00ebj\u00eb t\u00eb rishikoj dhe t\u00eb kthehem te Kubernetes? Nuk e di, nuk e di. Duhet t\u00eb hap nj\u00eb hulumtim m\u00eb t\u00eb thell\u00eb, t\u00eb studioj replikimin. Do t\u00eb shohim. Por p\u00ebrshtypja e par\u00eb \u00ebsht\u00eb e mir\u00eb. Un\u00eb p\u00ebrfundimisht do t\u00eb preferoja t\u00eb p\u00ebrdorja klastra t\u00eb mia Kubernetes n\u00eb vend t\u00eb Heroku, p\u00ebr t\u00eb fituar m\u00eb shum\u00eb liri dhe p\u00ebr t\u00eb m\u00ebsuar t\u00eb reja. Duke qen\u00eb se instalimi i Linstor nuk \u00ebsht\u00eb aq i leht\u00eb sa t\u00eb tjerat, s\u00eb shpejti do t\u00eb shkruaj nj\u00eb postim rreth k\u00ebsaj.<\/p>\n

<\/p>\n

Benchmark<\/h3>\n

<\/p>\n

Fatkeq\u00ebsisht, kam ruajtur pak t\u00eb dh\u00ebna krahasuese, sepse nuk mendova se do t\u00eb shkruaja p\u00ebr k\u00ebt\u00eb. Kam vet\u00ebm rezultatet e benchmark-\u00ebve bazik\u00eb fio dhe p\u00ebr klaster\u00ebt me nj\u00eb nod, k\u00ebshtu q\u00eb p\u00ebr konfigurimet e replikuara nuk kam ende numra. Por nga k\u00ebto rezultate mund t\u00eb merrni nj\u00eb ide t\u00eb p\u00ebraf\u00ebrt se \u00e7far\u00eb t\u00eb prisni nga \u00e7do opsion, sepse i kam krahasuar ato n\u00eb server\u00eb t\u00eb nj\u00ebjt\u00eb n\u00eb cloud, 4 b\u00ebrthama, 16 GB RAM, me nj\u00eb disk shtes\u00eb 100 GB p\u00ebr volumet e testuara. Kam kryer benchmark-\u00ebt tri her\u00eb p\u00ebr \u00e7do zgjidhje dhe kam llogaritur rezultatin mesatar, p\u00ebrve\u00e7 se kam rikuperuar konfigurimet e serverit p\u00ebr \u00e7do produkt. T\u00eb gjitha k\u00ebto nuk jan\u00eb aspak shkencore, vet\u00ebm n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb kuptoni n\u00eb vijim\u00ebsi. N\u00eb teste t\u00eb tjera kam kopjuar 38 GB foto dhe video nga volumi dhe dhe n\u00eb, p\u00ebr t\u00eb testuar leximin dhe shkrimin, por fatkeq\u00ebsisht nuk ruajta numrat. N\u00eb p\u00ebrmbledhje: Portworx ishte shum\u00eb m\u00eb i shpejt\u00eb.<\/p>\n

<\/p>\n

P\u00ebr benchmark-un e volumit kam p\u00ebrdorur 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
S\u00eb pari krijova nj\u00eb volum me klas\u00ebn p\u00ebrkat\u00ebse t\u00eb ruajtjes, pastaj b\u00ebra nj\u00eb pun\u00eb me fio n\u00eb sfond. Zgjodha 1 GB, p\u00ebr t\u00eb llogaritur performanc\u00ebn dhe p\u00ebr t\u00eb mos pritur shum\u00eb gjat\u00eb. Ja rezultatet:<\/p>\n
<\/p>\n
\"Ruajtja<\/a><\/noindex><\/p>\n
<\/p>\n
Kam theksuar vler\u00ebn m\u00eb t\u00eb mir\u00eb p\u00ebr \u00e7do tregues me t\u00eb gjelb\u00ebr, dhe m\u00eb t\u00eb keqen me t\u00eb kuqe.<\/p>\n
<\/p>\n
P\u00ebrfundim<\/h3>\n
<\/p>\n
Si\u00e7 mund ta shihni, n\u00eb shumic\u00ebn e rasteve Portworx u tregua m\u00eb mir\u00eb se t\u00eb tjer\u00ebt. Por p\u00ebr mua \u00ebsht\u00eb i shtrenjt\u00eb. Nuk e di sa kushton Robin, por ka nj\u00eb version t\u00eb shk\u00eblqyer falas, k\u00ebshtu q\u00eb, n\u00ebse ju nevojitet nj\u00eb produkt i paguar, mund ta provoni (shpresoj se s\u00eb shpejti do t\u00eb riparojn\u00eb problemin me rikuperimin dhe backup-et). Nga tre falas, kam pasur m\u00eb pak probleme me OpenEBS, por performanca e tij \u00ebsht\u00eb e keqe. M\u00eb vjen keq q\u00eb nuk ruajta m\u00eb shum\u00eb rezultate, por shpresoj se numrat e dh\u00ebna dhe komentet e mia do t'ju ndihmojn\u00eb.<\/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\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\udd47Ruajtja n\u00eb Kubernetes: OpenEBS vs Rook (Ceph) vs Rancher Longhorn vs StorageOS vs Robin vs Portworx vs Linstor | ProHoster","description":"","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: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}]}}