{"id":94739,"date":"2020-09-20T19:42:27","date_gmt":"2020-09-20T17:42:27","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes"},"modified":"2021-01-02T13:05:08","modified_gmt":"2021-01-02T11:05:08","slug":"prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes","title":{"rendered":"Nj\u00eb shembull praktik i lidhjes s\u00eb magazin\u00ebs s\u00eb bazuar n\u00eb Ceph n\u00eb nj\u00eb klaster Kubernetes","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Interface e Ruajtjes s\u00eb Kontejner\u00ebve (CSI) - \u00ebsht\u00eb nj\u00eb nd\u00ebrfaqe e standardizuar e bashk\u00ebpunimit midis Kubernetes dhe sistemeve t\u00eb ruajtjes s\u00eb t\u00eb dh\u00ebnave. N\u00eb m\u00ebnyr\u00eb t\u00eb shkurt\u00ebr p\u00ebr t\u00eb, ne tashm\u00eb fol\u00ebm<\/a><\/noindex>, dhe sot do t\u00eb shqyrtojm\u00eb m\u00eb n\u00eb detaje lidhjen CSI dhe Ceph: do t\u00eb tregojm\u00eb se si t\u00eb lidhni ruajtjen Ceph<\/a><\/noindex> me klasterin Kubernetes.
\nN\u00eb artikullin e m\u00ebposht\u00ebm do t\u00eb paraqesim shembuj real\u00eb, edhe pse pak t\u00eb thjeshtuar p\u00ebr leht\u00ebsi n\u00eb kuptim. Instalimi dhe konfigurimi i klastereve Ceph dhe Kubernetes nuk do t\u00eb shqyrtohet.<\/p>\n

Ju intereson si funksionon kjo?<\/p>\n

\"Nj\u00eb<\/p>\n

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

Pra, keni n\u00eb duar nj\u00eb klaster Kubernetes, t\u00eb vendosur, p\u00ebr shembull, kubespray<\/a><\/noindex>. Pran\u00eb punon nj\u00eb klaster Ceph - mund ta instaloni gjithashtu, p\u00ebr shembull, me k\u00ebt\u00eb grup t\u00eb playbook-eve<\/a><\/noindex>. Shpresoj, nuk \u00ebsht\u00eb e nevojshme t\u00eb p\u00ebrmendet se p\u00ebr prodhimin, midis tyre duhet t\u00eb ket\u00eb nj\u00eb rrjet me kapacitet jo m\u00eb t\u00eb ul\u00ebt se 10 Gbit\/s.<\/p>\n

N\u00ebse t\u00eb gjitha k\u00ebto i keni, le t\u00eb fillojm\u00eb!<\/p>\n

Fillimisht, do t\u00eb hyjm\u00eb n\u00eb nj\u00eb nga nodet e klasterit Ceph dhe do t\u00eb kontrollojm\u00eb q\u00eb gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull:<\/p>\n

ceph health\nceph -s<\/code><\/pre>\n
M\u00eb pas, k\u00ebtu do t\u00eb krijojm\u00eb nj\u00eb pool p\u00ebr disk\u00ebt RBD:<\/p>\n
ceph osd pool create kube 32\nceph osd pool application enable kube rbd<\/code><\/pre>\n
Kalojm\u00eb n\u00eb klasterin Kubernetes. Atje, s\u00eb pari do t\u00eb instalojm\u00eb drejtorin Ceph CSI p\u00ebr RBD. Do ta vendosim si\u00e7 duhet, p\u00ebrmes Helm.
\nShtojm\u00eb repositorin me chartin, dhe marrim grupin e variablave t\u00eb chartit ceph-csi-rbd:<\/p>\n
helm repo add ceph-csi https:\/\/ceph.github.io\/csi-charts\nhelm inspect values ceph-csi\/ceph-csi-rbd > cephrbd.yml<\/code><\/pre>\n
Tani duhet t\u00eb plot\u00ebsojm\u00eb skedarin cephrbd.yml. P\u00ebr k\u00ebt\u00eb, le t\u00eb gjejm\u00eb ID-n\u00eb e klashtarit dhe adresat IP t\u00eb monitor\u00ebve n\u00eb Ceph:<\/p>\n
ceph fsid  # k\u00ebshtu do t\u00eb m\u00ebsojm\u00eb clusterID\nceph mon dump  # k\u00ebshtu do t\u00eb shohim adresat IP t\u00eb monitor\u00ebve<\/code><\/pre>\n
Vlerat e marra i shtojm\u00eb n\u00eb skedarin cephrbd.yml. Nd\u00ebrkoh\u00eb aktivizojm\u00eb krijimin e politikave PSP (Pod Security Policies). Opsionet n\u00eb seksionet nodeplugin<\/strong> dhe provisioner<\/strong> jan\u00eb tashm\u00eb n\u00eb skedar, mund t\u00eb korrigjohen si\u00e7 tregohen m\u00eb posht\u00eb:<\/p>\n
csiConfig:\n  - clusterID: \"bcd0d202-fba8-4352-b25d-75c89258d5ab\"\n    monitors:\n      - \"v2:172.18.8.5:3300\/0,v1:172.18.8.5:6789\/0\"\n      - \"v2:172.18.8.6:3300\/0,v1:172.18.8.6:6789\/0\"\n      - \"v2:172.18.8.7:3300\/0,v1:172.18.8.7:6789\/0\"\n\nnodeplugin:\n  podSecurityPolicy:\n    enabled: true\n\nprovisioner:\n  podSecurityPolicy:\n    enabled: true<\/code><\/pre>\n
Pastaj, gjith\u00e7ka q\u00eb na mbetet \u00ebsht\u00eb t\u00eb instalojm\u00eb chart-in n\u00eb klashtarin Kubernetes.<\/p>\n
helm upgrade -i ceph-csi-rbd ceph-csi\/ceph-csi-rbd -f cephrbd.yml -n ceph-csi-rbd --create-namespace<\/code><\/pre>\n
Shum\u00eb mir\u00eb, RBD driver-i po punon!
\nT\u00eb krijojm\u00eb nj\u00eb StorageClass t\u00eb re n\u00eb Kubernetes. P\u00ebr k\u00ebt\u00eb, do t\u00eb nevojitet t\u00eb punojm\u00eb pak m\u00eb shum\u00eb me Ceph.<\/p>\n
Krijojm\u00eb nj\u00eb p\u00ebrdorues t\u00eb ri n\u00eb Ceph dhe i japim t\u00eb drejta p\u00ebr shkrim n\u00eb depo kube<\/strong>:<\/p>\n
ceph auth get-or-create client.rbdkube mon 'profile rbd' osd 'profile rbd pool=kube'<\/code><\/pre>\n
M\u00eb tani le t\u00eb shohim \u00e7el\u00ebsin e aksesit gjithashtu:<\/p>\n
ceph auth get-key client.rbdkube<\/code><\/pre>\n
Komanda do t\u00eb jap\u00eb di\u00e7ka t\u00eb ngjashme me:<\/p>\n
AQCO9NJbhYipKRAAMqZsnqqS\/T8OYQX20xIa9A==<\/code><\/pre>\n
Do ta vler\u00eb n\u00eb Secret n\u00eb klasterin Kubernetes - atje ku nevojitet userKey<\/strong>:<\/p>\n
---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: csi-rbd-secret\n  namespace: ceph-csi-rbd\nstringData:\n  # Vlerat e \u00e7el\u00ebsave jan\u00eb n\u00eb p\u00ebrputhje me emrin e p\u00ebrdoruesit dhe \u00e7el\u00ebsin e tij, si\u00e7 \u00ebsht\u00eb p\u00ebrcaktuar n\u00eb\n  # klasterin Ceph. ID e p\u00ebrdoruesit duhet t\u00eb ket\u00eb qasje n\u00eb rezervuarin,\n  # t\u00eb treguar n\u00eb klas\u00ebn e ruajtjes\n  userID: rbdkube\n  userKey:<\/code><\/pre>\n
Dhe krijojm\u00eb sekretin ton\u00eb:<\/p>\n
kubectl apply -f secret.yaml<\/code><\/pre>\n
Pastaj na nevojitet nj\u00eb manifest i till\u00eb StorageClass:<\/p>\n
---\napiVersion: storage.k8s.io\/v1\nkind: StorageClass\nmetadata:\n   name: csi-rbd-sc\nprovisioner: rbd.csi.ceph.com\nparameters:\n   clusterID: \n   pool: kube\n\n   imageFeatures: layering\n\n   # K\u00ebto sekrete duhet t\u00eb p\u00ebrmbajn\u00eb t\u00eb dh\u00ebna p\u00ebr autorizim\n   # n\u00eb rezervuarin tuaj.\n   csi.storage.k8s.io\/provisioner-secret-name: csi-rbd-secret\n   csi.storage.k8s.io\/provisioner-secret-namespace: ceph-csi-rbd\n   csi.storage.k8s.io\/controller-expand-secret-name: csi-rbd-secret\n   csi.storage.k8s.io\/controller-expand-secret-namespace: ceph-csi-rbd\n   csi.storage.k8s.io\/node-stage-secret-name: csi-rbd-secret\n   csi.storage.k8s.io\/node-stage-secret-namespace: ceph-csi-rbd\n\n   csi.storage.k8s.io\/fstype: ext4\n\nreclaimPolicy: Delete\nallowVolumeExpansion: true\nmountOptions:\n  - discard<\/code><\/pre>\n
Duhet t\u00eb plot\u00ebsojm\u00eb clusterID<\/strong>, i cili e kemi m\u00ebsuar tashm\u00eb me komand\u00ebn ceph fsid<\/em>, dhe apliko k\u00ebt\u00eb manifest n\u00eb klasterin Kubernetes:<\/p>\n
kubectl apply -f storageclass.yaml<\/code><\/pre>\n
P\u00ebr t\u00eb verifikuar funksionimin e klastereve n\u00eb bashk\u00ebpunim, do t\u00eb krijojm\u00eb nj\u00eb PVC (K\u00ebrkes\u00eb p\u00ebr Volume t\u00eb P\u00ebrhersh\u00ebm) t\u00eb till\u00eb:<\/p>\n
apiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: rbd-pvc\nspec:\n  accessModes:\n  - ReadWriteOnce\n  resources:\n    requests:\n      storage: 1Gi\n  storageClassName: csi-rbd-sc<\/code><\/pre>\n
Le t\u00eb shohim menj\u00ebher\u00eb se si Kubernetes krijoi volum\u00ebn e k\u00ebrkuar n\u00eb Ceph:<\/p>\n
kubectl get pvc\nkubectl get pv<\/code><\/pre>\n
Duket se gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull! Por si duket kjo n\u00eb an\u00ebn e Ceph?
\nMarrim list\u00ebn e volumeve n\u00eb rezervuari dhe shohim informacionin p\u00ebr volum\u00ebn ton\u00eb:<\/p>\n
rbd ls -p kube\nrbd -p kube info csi-vol-eb3d257d-8c6c-11ea-bff5-6235e7640653  # k\u00ebtu, sigurisht, do t\u00eb ket\u00eb nj\u00eb ID tjet\u00ebr p\u00ebr volum, q\u00eb u dha nga komanda e m\u00ebparshme<\/code><\/pre>\n
Tani le t\u00eb shohim se si funksionon ndryshimi i madh\u00ebsis\u00eb s\u00eb volumit RBD.
\nNdryshojm\u00eb madh\u00ebsin\u00eb e volumit n\u00eb manifestin pvc.yaml n\u00eb 2Gi dhe e aplikojm\u00eb:<\/p>\n
kubectl apply -f pvc.yaml<\/code><\/pre>\n
T\u00eb presim derisa ndryshimet t\u00eb hyjn\u00eb n\u00eb fuqi dhe t'i hedhim nj\u00eb sy p\u00ebrs\u00ebri madh\u00ebsis\u00eb s\u00eb volumit.<\/p>\n
rbd -p kube info csi-vol-eb3d257d-8c6c-11ea-bff5-6235e7640653\n\nkubectl get pv\nkubectl get pvc<\/code><\/pre>\n
V\u00ebrejm\u00eb se madh\u00ebsia e PVC nuk \u00ebsht\u00eb ndryshuar. P\u00ebr t\u00eb kuptuar arsyen, mund t\u00eb k\u00ebrkojm\u00eb nga Kubernetes p\u00ebrshkrimin e PVC n\u00eb formatin YAML:<\/p>\n
kubectl get pvc rbd-pvc -o yaml<\/code><\/pre>\n
Dhe ja problemi:<\/p>\n
message: Waiting for user to (re-)start a pod to finish file system resize of volume on node. type: FileSystemResizePending<\/em><\/p>\n
Pra, disku u rrit, por sistemi i skedave mbi t\u00eb \u2014 jo.
\nP\u00ebr t\u00eb zgjeruar sistemin e skedave, duhet t\u00eb montoni volumet. Aktualisht, PVC\/PV i krijuar nuk p\u00ebrdoret asnj\u00ebher\u00eb.<\/p>\n
Mund t\u00eb krijojm\u00eb nj\u00eb Pod testues, p.sh. k\u00ebshtu:<\/p>\n
---\napiVersion: v1\nkind: Pod\nmetadata:\n  name: csi-rbd-demo-pod\nspec:\n  containers:\n    - name: web-server\n      image: nginx:1.17.6\n      volumeMounts:\n        - name: mypvc\n          mountPath: \/data\n  volumes:\n    - name: mypvc\n      persistentVolumeClaim:\n        claimName: rbd-pvc\n        readOnly: false<\/code><\/pre>\n
Tani le t\u00eb shikojm\u00eb PVC:<\/p>\n
kubectl get pvc<\/code><\/pre>\n
Madh\u00ebsia ka ndryshuar, gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull.<\/p>\n
N\u00eb pjes\u00ebn e par\u00eb punuam me nj\u00eb pajisje blloku RBD (ky \u00ebsht\u00eb em\u00ebrtimi \u2013 Rados Block Device), por nuk \u00ebsht\u00eb e mundur ta b\u00ebsh k\u00ebt\u00eb n\u00ebse k\u00ebrkohet p\u00ebrdorimi i nj\u00ebkohsh\u00ebm t\u00eb k\u00ebtij disku nga mikrosh\u00ebrbime t\u00eb ndryshme. P\u00ebr pun\u00eb me skedar\u00eb, e jo me imazhin e disku, CephFS \u00ebsht\u00eb shum\u00eb m\u00eb i p\u00ebrshtatsh\u00ebm.
\nN\u00eb shembullin e klashtave Ceph dhe Kubernetes do t\u00eb konfigurimim CSI dhe entitetet e tjera t\u00eb nevojshme p\u00ebr t\u00eb punuar me CephFS.<\/p>\n
Do t\u00eb marrim vlerat nga Helm-charta q\u00eb na nevojitet:<\/p>\n
helm inspect values ceph-csi\/ceph-csi-cephfs > cephfs.yml<\/code><\/pre>\n
S\u00ebrish duhet t\u00eb plot\u00ebsojm\u00eb skedarin cephfs.yml. Si m\u00eb par\u00eb, komandat Ceph do t\u00eb na ndihmojn\u00eb:<\/p>\n
ceph fsid\nceph mon dump<\/code><\/pre>\n
Plot\u00ebsojm\u00eb skedarin me vlera pak a shum\u00eb k\u00ebshtu:<\/p>\n
csiConfig:\n  - clusterID: \"bcd0d202-fba8-4352-b25d-75c89258d5ab\"\n    monitors:\n      - \"172.18.8.5:6789\"\n      - \"172.18.8.6:6789\"\n      - \"172.18.8.7:6789\"\n\nnodeplugin:\n  httpMetrics:\n    enabled: true\n    containerPort: 8091\n  podSecurityPolicy:\n    enabled: true\n\nprovisioner:\n  replicaCount: 1\n  podSecurityPolicy:\n    enabled: true<\/code><\/pre>\n
Vini re se adresat e monitor\u00ebve jan\u00eb t\u00eb dh\u00ebn\u00eb n\u00eb nj\u00eb format t\u00eb thjesht\u00eb address:port. P\u00ebr t\u00eb montuar cephfs n\u00eb nod, k\u00ebto adresa d\u00ebrgohen n\u00eb modul t\u00eb b\u00ebrtham\u00ebs, i cili ende nuk di t\u00eb punoj\u00eb me protokolin e monitor\u00ebve v2.
\nNe e ndryshojm\u00eb portin p\u00ebr httpMetrics (ku Prometheus do t\u00eb shkoj\u00eb p\u00ebr metrikat e monitorimit) q\u00eb t\u00eb mos ket\u00eb konflikte me nginx-proxy, i cili instalohet nga Kubespray. Kjo mund t\u00eb mos jet\u00eb e nevojshme p\u00ebr ju.<\/p>\n
Po instalojm\u00eb Helm-chart n\u00eb klasterin Kubernetes:<\/p>\n
helm upgrade -i ceph-csi-cephfs ceph-csi\/ceph-csi-cephfs -f cephfs.yml -n ceph-csi-cephfs --create-namespace<\/code><\/pre>\n
Tani kalojm\u00eb tek depoja e t\u00eb dh\u00ebnave Ceph p\u00ebr t\u00eb krijuar nj\u00eb p\u00ebrdorues t\u00eb ve\u00e7ant\u00eb. N\u00eb dokumentacion thuhet se provizionuesi CephFS ka nevoj\u00eb p\u00ebr t\u00eb drejta administratori n\u00eb klaster. Por ne do t\u00eb krijojm\u00eb nj\u00eb p\u00ebrdorues t\u00eb ve\u00e7ant\u00eb fs<\/em> me d\u00ebshmi t\u00eb kufizuara:<\/p>\n
ceph auth get-or-create client.fs mon 'allow r' mgr 'allow rw' mds 'allow rws' osd 'allow rw pool=cephfs_data, allow rw pool=cephfs_metadata'<\/code><\/pre>\n
Dhe menj\u00ebher\u00eb do t\u00eb shohim \u00e7el\u00ebsin e tij t\u00eb qasjes, do t\u00eb na nevojitet m\u00eb von\u00eb:<\/p>\n
ceph auth get-key client.fs<\/code><\/pre>\n
Do t\u00eb krijojm\u00eb Secret t\u00eb ve\u00e7ant\u00eb dhe StorageClass.
\nNuk ka asgj\u00eb t\u00eb re, ne k\u00ebt\u00eb e kemi par\u00eb m\u00eb par\u00eb n\u00eb shembullin RBD:<\/p>\n
---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: csi-cephfs-secret\n  namespace: ceph-csi-cephfs\nstringData:\n  # E nevojshme p\u00ebr volumin q\u00eb krijohet dinamikisht\n  adminID: fs\n  adminKey:<\/code><\/pre>\n
Aplikojm\u00eb manifestin:<\/p>\n
kubectl apply -f secret.yaml<\/code><\/pre>\n
Tani \u2013 nj\u00eb StorageClass t\u00eb ve\u00e7ant\u00eb:<\/p>\n
---\napiVersion: storage.k8s.io\/v1\nkind: StorageClass\nmetadata:\n  name: csi-cephfs-sc\nprovisioner: cephfs.csi.ceph.com\nparameters:\n  clusterID: \n\n  # Emri i sistemit t\u00eb skedar\u00ebve CephFS, n\u00eb t\u00eb cilin do t\u00eb krijohet v\u00ebllimi\n  fsName: cephfs\n\n  # (opsionale) Pishina Ceph ku do t\u00eb ruhen t\u00eb dh\u00ebnat e v\u00ebllimit\n  # pool: cephfs_data\n\n  # (opsionale) Opsione t\u00eb monta\u017ehimit t\u00eb ndara me presje p\u00ebr Ceph-fuse\n  # p\u00ebr shembull:\n  # fuseMountOptions: debug\n\n  # (opsionale) Opsione t\u00eb monta\u017ehimit CephFS p\u00ebr kernel t\u00eb ndara me presje\n  # Shihni man mount.ceph p\u00ebr t\u00eb m\u00ebsuar rreth k\u00ebtyre opsioneve. P\u00ebr shembull:\n  # kernelMountOptions: readdir_max_bytes=1048576,norbytes\n\n  # Sekretet duhet t\u00eb p\u00ebrmbajn\u00eb qasje p\u00ebr administratorin dhe\/ose p\u00ebrdoruesin Ceph.\n  csi.storage.k8s.io\/provisioner-secret-name: csi-cephfs-secret\n  csi.storage.k8s.io\/provisioner-secret-namespace: ceph-csi-cephfs\n  csi.storage.k8s.io\/controller-expand-secret-name: csi-cephfs-secret\n  csi.storage.k8s.io\/controller-expand-secret-namespace: ceph-csi-cephfs\n  csi.storage.k8s.io\/node-stage-secret-name: csi-cephfs-secret\n  csi.storage.k8s.io\/node-stage-secret-namespace: ceph-csi-cephfs\n\n  # (opsionale) Driveri mund t\u00eb p\u00ebrdor\u00eb ose ceph-fuse (fuse), \n  # ose ceph kernelclient (kernel).\n  # N\u00ebse nuk p\u00ebrcaktohet, do t\u00eb p\u00ebrdoret monta\u017ehimi i v\u00ebllimeve nga parazgjedhja,\n  # kjo p\u00ebrcaktohet nga k\u00ebrkimi i ceph-fuse dhe mount.ceph\n  # mounter: kernel\nreclaimPolicy: Delete\nallowVolumeExpansion: true\nmountOptions:\n  - debug<\/code><\/pre>\n
Do ta mbushim k\u00ebtu clusterID<\/strong> dhe do ta aplikojm\u00eb n\u00eb Kubernetes:<\/p>\n
kubectl apply -f storageclass.yaml<\/code><\/pre>\n
Kontroll<\/h2>\n
P\u00ebr kontroll, si\u00e7 b\u00ebm\u00eb n\u00eb shembullin e kaluar, do t\u00eb krijojm\u00eb PVC:<\/p>\n
---\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: csi-cephfs-pvc\nspec:\n  accessModes:\n    - ReadWriteMany\n  resources:\n    requests:\n      storage: 5Gi\n  storageClassName: csi-cephfs-sc<\/code><\/pre>\n
Dhe do t\u00eb kontrollojm\u00eb pranin\u00eb e PVC\/PV:<\/p>\n
kubectl get pvc\nkubectl get pv<\/code><\/pre>\n
N\u00ebse d\u00ebshironi t\u00eb shihni skedar\u00ebt dhe katalog\u00ebt n\u00eb CephFS, mund ta montoni k\u00ebt\u00eb sistem skedari diku. P\u00ebr shembull, si\u00e7 tregohet m\u00eb posht\u00eb.<\/p>\n
Shkoni n\u00eb nj\u00eb nga nodet e klasterit Ceph dhe kryeni k\u00ebto veprime:<\/p>\n
# \u0422\u043e\u0447\u043a\u0430 \u043c\u043e\u043d\u0442\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f\nmkdir -p \/mnt\/cephfs\n\n# \u0421\u043e\u0437\u0434\u0430\u0451\u043c \u0444\u0430\u0439\u043b \u0441 \u043a\u043b\u044e\u0447\u043e\u043c \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0430\u0442\u043e\u0440\u0430\nceph auth get-key client.admin >\/etc\/ceph\/secret.key\n\n# \u0414\u043e\u0431\u0430\u0432\u043b\u044f\u0435\u043c \u0437\u0430\u043f\u0438\u0441\u044c \u0432 \/etc\/fstab\n# !! \u0418\u0437\u043c\u0435\u043d\u044f\u0435\u043c ip \u0430\u0434\u0440\u0435\u0441 \u043d\u0430 \u0430\u0434\u0440\u0435\u0441 \u043d\u0430\u0448\u0435\u0433\u043e \u0443\u0437\u043b\u0430\necho \"172.18.8.6:6789:\/ \/mnt\/cephfs ceph name=admin,secretfile=\/etc\/ceph\/secret.key,noatime,_netdev    0       2\" >> \/etc\/fstab\n\nmount \/mnt\/cephfs<\/code><\/pre>\n
Sigurisht, nj\u00eb montim i till\u00eb FS n\u00eb noden Ceph \u00ebsht\u00eb i p\u00ebrshtatsh\u00ebm vet\u00ebm p\u00ebr q\u00ebllime m\u00ebsimore, dhe kjo \u00ebsht\u00eb ajo q\u00eb ne po b\u00ebjm\u00eb n\u00eb kurset tona Sll\u00ebrm.<\/a><\/noindex>Nuk mendoj se ndokush do ta b\u00ebj\u00eb k\u00ebt\u00eb n\u00eb prodhim, ka nj\u00eb rrezik t\u00eb madh p\u00ebr t\u00eb p\u00ebrmbysur skedar\u00eb t\u00eb r\u00ebnd\u00ebsish\u00ebm.<\/p>\n
Dhe n\u00eb fund, le t\u00eb kontrollojm\u00eb si q\u00ebndrojn\u00eb gj\u00ebrat me nd\u00ebrrimin e madh\u00ebsis\u00eb s\u00eb volumit n\u00eb rastin e CephFS. Kthehemi n\u00eb Kubernetes dhe redaktojm\u00eb manifestin ton\u00eb p\u00ebr PVC - do ta rrisim atje madh\u00ebsin\u00eb, p\u00ebr shembull, n\u00eb 7Gi.<\/p>\n
Do ta aplikojm\u00eb skedarin e redaktuar:<\/p>\n
kubectl apply -f pvc.yaml<\/code><\/pre>\n
Le t\u00eb shohim n\u00eb katalogun e montuar si ka ndryshuar kuota:<\/p>\n
getfattr -n ceph.quota.max_bytes<\/code><\/pre>\n
P\u00ebr t\u00eb funksionuar k\u00ebt\u00eb komand\u00eb, ndoshta do t'ju nevojitet t\u00eb instaloni paket\u00ebn n\u00eb sistemin tuaj attr<\/strong>.<\/p>\n
Syri friksohet, por duar b\u00ebjn\u00eb<\/h2>\n
Pamja e k\u00ebtyre magjive dhe manifest\u00ebve t\u00eb gjat\u00eb YAML duket e komplikuar, por n\u00eb praktik\u00eb student\u00ebt e Sly\u00ebrm e menaxhojn\u00eb ato mjaft shpejt.
\nN\u00eb k\u00ebt\u00eb artikull ne nuk thellohemi n\u00eb detaje \u2014 ka dokumentacionin zyrtar p\u00ebr k\u00ebt\u00eb. N\u00ebse jeni t\u00eb interesuar p\u00ebr detajet e konfigurimit t\u00eb depozit\u00ebs Ceph s\u00eb bashku me klasterin Kubernetes, k\u00ebto lidhje do t' ju ndihmojn\u00eb:<\/p>\n
Parimet e p\u00ebrgjithshme t\u00eb pun\u00ebs s\u00eb Kubernetes me volume<\/a><\/noindex>
\nDokumentacioni p\u00ebr RBD<\/a><\/noindex>
\nIntegrimi i RBD dhe Kubernetes nga perspektiva e Ceph<\/a><\/noindex>
\nIntegrimi i RBD dhe Kubernetes nga perspektiva e CSI<\/a><\/noindex>
\nDokumentacioni i p\u00ebrgjithsh\u00ebm p\u00ebr CephFS<\/a><\/noindex>
\nIntegrimi i CephFS dhe Kubernetes nga perspektiva e CSI<\/a><\/noindex><\/p>\n
N\u00eb kursin Sly\u00ebrm Baza Kubernetes<\/a><\/noindex> mund t\u00eb shkoni edhe m\u00eb tej dhe t\u00eb zhvilloni nj\u00eb aplikacion real n\u00eb Kubernetes, i cili do t\u00eb p\u00ebrdor\u00eb CephFS si depo p\u00ebr skedar\u00ebt. N\u00ebp\u00ebrmjet k\u00ebrkesave GET\/POST do t\u00eb jeni n\u00eb gjendje t\u00eb transferoni skedar\u00eb dhe t'i merrni ata nga Ceph.<\/p>\n
Dhe n\u00ebse ju intereson m\u00eb shum\u00eb ruajtja e t\u00eb dh\u00ebnave, regjistrohuni n\u00eb kursin e ri p\u00ebr Ceph<\/a><\/noindex>. Gjat\u00eb testimit beta, kursi mund t\u00eb merret me zbritje dhe t\u00eb ndikoni n\u00eb p\u00ebrmbajtjen e tij.<\/p>\n
Autori i artikullit: Alexander Shvalov, inxhinier praktikues Southbridge<\/a><\/noindex>, Administrator i Certifikuar Kubernetes, autor dhe zhvillues i kurseve Sly\u00ebrm.<\/em><\/p>\n
Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"
Container Storage Interface (CSI) \u2014 \u044d\u0442\u043e \u0443\u043d\u0438\u0444\u0438\u0446\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0439 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441 \u0432\u0437\u0430\u0438\u043c\u043e\u0434\u0435\u0439\u0441\u0442\u0432\u0438\u044f Kubernetes \u0438 \u0441\u0438\u0441\u0442\u0435\u043c \u0445\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u0434\u0430\u043d\u043d\u044b\u0445. \u0412\u043a\u0440\u0430\u0442\u0446\u0435 \u043e \u043d\u0451\u043c \u043c\u044b \u0443\u0436\u0435 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u043b\u0438, \u0430 \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u0435\u0435 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0441\u0432\u044f\u0437\u043a\u0443 CSI \u0438 Ceph: \u043f\u043e\u043a\u0430\u0436\u0435\u043c, \u043a\u0430\u043a \u043f\u043e\u0434\u043a\u043b\u044e\u0447\u0438\u0442\u044c \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0435 Ceph \u043a \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0443 Kubernetes. \u0412 \u0441\u0442\u0430\u0442\u044c\u0435 \u043f\u0440\u0438\u0432\u0435\u0434\u0435\u043d\u044b \u0440\u0435\u0430\u043b\u044c\u043d\u044b\u0435, \u0445\u043e\u0442\u044f \u0438 \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u0443\u043f\u0440\u043e\u0449\u0451\u043d\u043d\u044b\u0435 \u0434\u043b\u044f \u0443\u0434\u043e\u0431\u0441\u0442\u0432\u0430 \u0432\u043e\u0441\u043f\u0440\u0438\u044f\u0442\u0438\u044f \u043f\u0440\u0438\u043c\u0435\u0440\u044b. \u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0443 \u0438 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0443 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432 Ceph \u0438 Kubernetes […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":94740,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-94739","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Shembulli praktik i lidhjes s\u00eb ruajtjes s\u00eb bazuar n\u00eb Ceph n\u00eb klasterin Kubernetes | ProHoster","description":"Container Storage Interface (CSI) \u2014 \u00ebsht\u00eb nj\u00eb nd\u00ebrfaqe e unified p\u00ebr nd\u00ebrveprimin e Kubernetes me sistemet e ruajtjes s\u00eb t\u00eb dh\u00ebnave. N\u00eb p\u00ebrmbledhje p\u00ebr t\u00eb, ne kemi folur tashm\u00eb, dhe sot do t\u00eb shqyrtojm\u00eb m\u00eb thell\u00eb lidhjen midis CSI dhe Ceph: do t\u00eb tregojm\u00eb se si t\u00eb lidhni ruajtjen Ceph me klasterin Kubernetes. Artikulli p\u00ebrmban shembuj t\u00eb v\u00ebrtet\u00eb, ndon\u00ebse pak t\u00eb thjeshtuar p\u00ebr leht\u00ebsimin e perceptimit. Instalimi dhe konfigurimi i klastereve Ceph dhe Kubernetes","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes","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\u041f\u0440\u0430\u043a\u0442\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u043f\u0440\u0438\u043c\u0435\u0440 \u043f\u043e\u0434\u043a\u043b\u044e\u0447\u0435\u043d\u0438\u044f \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0430 \u043d\u0430 \u0431\u0430\u0437\u0435 Ceph \u0432 \u043a\u043b\u0430\u0441\u0442\u0435\u0440 Kubernetes | ProHoster","og:description":"Container Storage Interface (CSI) \u2014 \u044d\u0442\u043e \u0443\u043d\u0438\u0444\u0438\u0446\u0438\u0440\u043e\u0432\u0430\u043d\u043d\u044b\u0439 \u0438\u043d\u0442\u0435\u0440\u0444\u0435\u0439\u0441 \u0432\u0437\u0430\u0438\u043c\u043e\u0434\u0435\u0439\u0441\u0442\u0432\u0438\u044f Kubernetes \u0438 \u0441\u0438\u0441\u0442\u0435\u043c \u0445\u0440\u0430\u043d\u0435\u043d\u0438\u044f \u0434\u0430\u043d\u043d\u044b\u0445. \u0412\u043a\u0440\u0430\u0442\u0446\u0435 \u043e \u043d\u0451\u043c \u043c\u044b \u0443\u0436\u0435 \u0440\u0430\u0441\u0441\u043a\u0430\u0437\u044b\u0432\u0430\u043b\u0438, \u0430 \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u043f\u043e\u0434\u0440\u043e\u0431\u043d\u0435\u0435 \u0440\u0430\u0441\u0441\u043c\u043e\u0442\u0440\u0438\u043c \u0441\u0432\u044f\u0437\u043a\u0443 CSI \u0438 Ceph: \u043f\u043e\u043a\u0430\u0436\u0435\u043c, \u043a\u0430\u043a \u043f\u043e\u0434\u043a\u043b\u044e\u0447\u0438\u0442\u044c \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0435 Ceph \u043a \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0443 Kubernetes. \u0412 \u0441\u0442\u0430\u0442\u044c\u0435 \u043f\u0440\u0438\u0432\u0435\u0434\u0435\u043d\u044b \u0440\u0435\u0430\u043b\u044c\u043d\u044b\u0435, \u0445\u043e\u0442\u044f \u0438 \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u0443\u043f\u0440\u043e\u0449\u0451\u043d\u043d\u044b\u0435 \u0434\u043b\u044f \u0443\u0434\u043e\u0431\u0441\u0442\u0432\u0430 \u0432\u043e\u0441\u043f\u0440\u0438\u044f\u0442\u0438\u044f \u043f\u0440\u0438\u043c\u0435\u0440\u044b. \u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0443 \u0438 \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u043a\u0443 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432 Ceph \u0438 Kubernetes","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes","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":"2020-09-20T17:42:27+00:00","article:modified_time":"2021-01-02T11:05:08+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"94739","title":null,"description":"","keywords":"","keyphrases":null,"primary_term":null,"canonical_url":"","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 11:19:21","updated":"2022-09-30 10:03:10"},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/94739","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=94739"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/94739\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/94740"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=94739"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=94739"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=94739"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}