{"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\/cs\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes","title":{"rendered":"Praktick\u00fd p\u0159\u00edklad p\u0159ipojen\u00ed \u00falo\u017ei\u0161t\u011b na b\u00e1zi Ceph do klastru Kubernetes","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Container Storage Interface (CSI) je jednotn\u00fd rozhran\u00ed pro interakci Kubernetes a syst\u00e9m\u016f pro ukl\u00e1d\u00e1n\u00ed dat. Kr\u00e1tce o n\u011bm jsme ji\u017e <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/519130\/\">psali<\/a><\/noindex>, a dnes podrobn\u011bji prozkoum\u00e1me vazbu CSI a Ceph: uk\u00e1\u017eeme, jak <noindex><a rel=\"nofollow\" href=\"http:\/\/to.slurm.io\/WkM2Eg\">p\u0159ipojit \u00falo\u017ei\u0161t\u011b Ceph<\/a><\/noindex> k clusteru Kubernetes.<br \/>\nV \u010dl\u00e1nku jsou uvedeny skute\u010dn\u00e9, i kdy\u017e pon\u011bkud zjednodu\u0161en\u00e9 p\u0159\u00edklady pro lep\u0161\u00ed pochopen\u00ed. Instalaci a konfiguraci cluster\u016f Ceph a Kubernetes nebudeme prob\u00edrat.<\/p>\n<p>Zaj\u00edm\u00e1 v\u00e1s, jak to funguje?<\/p>\n<p><img decoding=\"async\" alt=\"Praktick\u00fd p\u0159\u00edklad p\u0159ipojen\u00ed \u00falo\u017ei\u0161t\u011b na b\u00e1zi Ceph do klastru Kubernetes\" src=\"\/wp-content\/uploads\/2020\/09\/db0a1d1e4c38c693f591057a219c141c.jpg\" style=\"display:block;margin: 0 auto;\"><\/p>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>Tak\u017ee m\u00e1te k dispozici cluster Kubernetes, nap\u0159\u00edklad <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes-sigs\/kubespray\">kubespray<\/a><\/noindex>. Vedle n\u011bj b\u011b\u017e\u00ed cluster Ceph \u2013 ten m\u016f\u017eete tak\u00e9 nainstalovat, nap\u0159\u00edklad t\u00edmto <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/ceph\/ceph-ansible\">bal\u00ed\u010dkem playbook\u016f<\/a><\/noindex>. Douf\u00e1m, \u017ee nen\u00ed t\u0159eba zd\u016fraz\u0148ovat, \u017ee pro produk\u010dn\u00ed nasazen\u00ed by mezi nimi m\u011bla b\u00fdt s\u00ed\u0165 s propustnost\u00ed minim\u00e1ln\u011b 10 Gbit\/s.<\/p>\n<p>Pokud to v\u0161echno m\u00e1te, jdeme na to!<\/p>\n<p>Nejprve se p\u0159ihl\u00e1s\u00edme na jeden z uzl\u016f clusteru Ceph a zkontrolujeme, \u017ee je v\u0161e v po\u0159\u00e1dku:<\/p>\n<pre><code class=\"plaintext\">ceph health\nceph -s<\/code><\/pre>\n<p>D\u00e1le vytv\u00e1\u0159\u00edme pool pro RBD disky:<\/p>\n<pre><code class=\"plaintext\">ceph osd pool create kube 32\nceph osd pool application enable kube rbd<\/code><\/pre>\n<p>P\u0159ech\u00e1z\u00edme do clusteru Kubernetes. Tam nejprve nainstalujeme Ceph CSI driver pro RBD. Instalaci provedeme, jak se pat\u0159\u00ed, p\u0159es Helm.<br \/>\nP\u0159id\u00e1me repozit\u00e1\u0159 s chartem, z\u00edsk\u00e1me sadu prom\u011bnn\u00fdch chartu ceph-csi-rbd:<\/p>\n<pre><code class=\"plaintext\">helm repo add ceph-csi https:\/\/ceph.github.io\/csi-charts\nhelm inspect values ceph-csi\/ceph-csi-rbd &gt; cephrbd.yml<\/code><\/pre>\n<p>Nyn\u00ed je t\u0159eba vyplnit soubor cephrbd.yml. K tomu zjist\u00edme ID clusteru a IP adresy monitor\u016f v Ceph:<\/p>\n<pre><code class=\"plaintext\">ceph fsid  # t\u00edm zjist\u00edme clusterID\nceph mon dump  # a tak uvid\u00edme IP adresy monitor\u016f<\/code><\/pre>\n<p>Z\u00edskan\u00e9 hodnoty vlo\u017e\u00edme do souboru cephrbd.yml. Sou\u010dasn\u011b zapneme vytvo\u0159en\u00ed politik PSP (Pod Security Policies). Mo\u017enosti v sekc\u00edch <strong>nodeplugin<\/strong> a <strong>provisioner<\/strong> u\u017e jsou v souboru, m\u016f\u017eeme je upravit tak, jak je uvedeno n\u00ed\u017ee:<\/p>\n<pre><code class=\"plaintext\">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<p>D\u00e1le u\u017e jen zb\u00fdv\u00e1 nainstalovat chart do clusteru Kubernetes.<\/p>\n<pre><code class=\"plaintext\">helm upgrade -i ceph-csi-rbd ceph-csi\/ceph-csi-rbd -f cephrbd.yml -n ceph-csi-rbd --create-namespace<\/code><\/pre>\n<p>Skv\u011ble, RBD driver funguje!<br \/>\nVytvo\u0159\u00edme v Kubernetes novou StorageClass. K tomu bude zase pot\u0159eba trochu pracovat s Ceph.<\/p>\n<p>Vytv\u00e1\u0159\u00edme nov\u00e9ho u\u017eivatele v Ceph a ud\u011blujeme mu pr\u00e1va na z\u00e1pis do poolu <strong>kube<\/strong>:<\/p>\n<pre><code class=\"plaintext\">ceph auth get-or-create client.rbdkube mon 'profile rbd' osd 'profile rbd pool=kube'<\/code><\/pre>\n<p>A te\u010f se pod\u00edv\u00e1me na p\u0159\u00edstupov\u00fd kl\u00ed\u010d to v\u0161e ve stejn\u00e9m m\u00edst\u011b:<\/p>\n<pre><code class=\"plaintext\">ceph auth get-key client.rbdkube<\/code><\/pre>\n<p>P\u0159\u00edkaz vyd\u00e1 n\u011bco takov\u00e9ho:<\/p>\n<pre><code class=\"plaintext\">AQCO9NJbhYipKRAAMqZsnqqS\/T8OYQX20xIa9A==<\/code><\/pre>\n<p>Ulo\u017e\u00edme tuto hodnotu do Secret v clusteru Kubernetes \u2013 tam, kde je pot\u0159eba <strong>userKey<\/strong>:<\/p>\n<pre><code class=\"plaintext\">---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: csi-rbd-secret\n  namespace: ceph-csi-rbd\nstringData:\n  # Hodnoty kl\u00ed\u010d\u016f odpov\u00eddaj\u00ed u\u017eivatelsk\u00e9mu jm\u00e9nu a jeho kl\u00ed\u010di, jak je uvedeno v\n  # clusteru Ceph. ID u\u017eivatele mus\u00ed m\u00edt p\u0159\u00edstup k poolu,\n  # uveden\u00e9mu ve storage class\n  userID: rbdkube\n  userKey:<\/code><\/pre>\n<p>A vytvo\u0159\u00edme n\u00e1\u0161 tajn\u00fd kl\u00ed\u010d:<\/p>\n<pre><code class=\"plaintext\">kubectl apply -f secret.yaml<\/code><\/pre>\n<p>D\u00e1le pot\u0159ebujeme zhruba takov\u00fd manifest StorageClass:<\/p>\n<pre><code class=\"plaintext\">---\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   # Tyto tajn\u00e9 kl\u00ed\u010de mus\u00ed obsahovat \u00fadaje pro autorizaci\n   # ve va\u0161em poolu.\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<p>Je t\u0159eba vyplnit <strong>clusterID<\/strong>, kter\u00fd jsme ji\u017e zjistili p\u0159\u00edkazem <em>ceph fsid<\/em>, a aplikovat tento manifest v clusteru Kubernetes:<\/p>\n<pre><code class=\"plaintext\">kubectl apply -f storageclass.yaml<\/code><\/pre>\n<p>Abychom ov\u011b\u0159ili funkci cluster\u016f ve spojen\u00ed, vytvo\u0159\u00edme n\u00e1sleduj\u00edc\u00ed PVC (Persistent Volume Claim):<\/p>\n<pre><code class=\"plaintext\">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<p>Hned se pod\u00edv\u00e1me, jak Kubernetes vytvo\u0159il v Ceph po\u017eadovan\u00fd objem:<\/p>\n<pre><code class=\"plaintext\">kubectl get pvc\nkubectl get pv<\/code><\/pre>\n<p>Vypad\u00e1 to skv\u011ble! Jak to vypad\u00e1 na stran\u011b Ceph?<br \/>\nZ\u00edsk\u00e1v\u00e1me seznam objem\u016f v poolu a prohl\u00ed\u017e\u00edme si informace o na\u0161em objemu:<\/p>\n<pre><code class=\"plaintext\">rbd ls -p kube\nrbd -p kube info csi-vol-eb3d257d-8c6c-11ea-bff5-6235e7640653  # zde bude samoz\u0159ejm\u011b jin\u00fd ID objemu, kter\u00fd vydala p\u0159edchoz\u00ed p\u0159\u00edkaz<\/code><\/pre>\n<p>Te\u010f se pod\u00edvejme, jak funguje zm\u011bna velikosti objemu RBD.<br \/>\nZm\u011bn\u00edme velikost objemu v manifestu pvc.yaml na 2Gi a aplikujeme jej:<\/p>\n<pre><code class=\"plaintext\">kubectl apply -f pvc.yaml<\/code><\/pre>\n<p>Po\u010dk\u00e1me, a\u017e zm\u011bny vstoup\u00ed v platnost, a znovu se pod\u00edv\u00e1me na velikost objemu.<\/p>\n<pre><code class=\"plaintext\">rbd -p kube info csi-vol-eb3d257d-8c6c-11ea-bff5-6235e7640653\n\nkubectl get pv\nkubectl get pvc<\/code><\/pre>\n<p>Vid\u00edme, \u017ee velikost PVC se nezm\u011bnila. Chcete-li zjistit d\u016fvod, m\u016f\u017eete po\u017e\u00e1dat Kubernetes o popis PVC ve form\u00e1tu YAML:<\/p>\n<pre><code class=\"plaintext\">kubectl get pvc rbd-pvc -o yaml<\/code><\/pre>\n<p>A tady je probl\u00e9m:<\/p>\n<p><em>message: Waiting for user to (re-)start a pod to finish file system resize of volume on node. type: FileSystemResizePending<\/em><\/p>\n<p>To znamen\u00e1, \u017ee disk se zv\u011bt\u0161il, ale souborov\u00fd syst\u00e9m na n\u011bm nikoli.<br \/>\nAbychom zv\u011bt\u0161ili souborov\u00fd syst\u00e9m, mus\u00edme p\u0159imontovat objem. N\u00e1\u0161 vytvo\u0159en\u00fd PVC\/PV se moment\u00e1ln\u011b nijak nevyu\u017e\u00edv\u00e1.<\/p>\n<p>M\u016f\u017eeme vytvo\u0159it testovac\u00ed Pod, nap\u0159\u00edklad takto:<\/p>\n<pre><code class=\"plaintext\">---\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<p>A nyn\u00ed se pod\u00edvejme na PVC:<\/p>\n<pre><code class=\"plaintext\">kubectl get pvc<\/code><\/pre>\n<p>Velikost se zm\u011bnila, v\u0161e je v po\u0159\u00e1dku.<\/p>\n<p>V prvn\u00ed \u010d\u00e1sti jsme pracovali s blokov\u00fdm za\u0159\u00edzen\u00edm RBD (co\u017e je zkratka pro Rados Block Device), ale takto to nelze prov\u00e1d\u011bt, pokud je t\u0159eba, aby s t\u00edmto diskem sou\u010dasn\u011b pracovaly r\u016fzn\u00e9 mikroslu\u017eby. Pro pr\u00e1ci s soubory, a ne s obrazem disku, je mnohem lep\u0161\u00ed CephFS.<br \/>\nNa p\u0159\u00edkladu cluster\u016f Ceph a Kubernetes nastav\u00edme CSI a dal\u0161\u00ed pot\u0159ebn\u00e9 entity pro pr\u00e1ci s CephFS.<\/p>\n<p>Z\u00edsk\u00e1me hodnoty z pot\u0159ebn\u00e9ho nov\u00e9ho Helm chartu:<\/p>\n<pre><code class=\"plaintext\">helm inspect values ceph-csi\/ceph-csi-cephfs &gt; cephfs.yml<\/code><\/pre>\n<p>Znovu je t\u0159eba vyplnit soubor cephfs.yml. Jako d\u0159\u00edve n\u00e1m pomohou p\u0159\u00edkazy Ceph:<\/p>\n<pre><code class=\"plaintext\">ceph fsid\nceph mon dump<\/code><\/pre>\n<p>Vypl\u0148ujeme soubor s hodnotami p\u0159ibli\u017en\u011b takto:<\/p>\n<pre><code class=\"plaintext\">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<p>V\u0161imn\u011bte si, \u017ee adresy monitor\u016f jsou uvedeny v jednoduch\u00e9 form\u011b address:port. Pro p\u0159ipojen\u00ed cephfs na uzlu se tyto adresy p\u0159ed\u00e1vaj\u00ed j\u00e1drov\u00e9mu modulu, kter\u00fd je\u0161t\u011b neum\u00ed pracovat s protokolem monitor\u016f v2.<br \/>\nPort pro httpMetrics (kam bude Prometheus pos\u00edlat metriky pro monitoring) m\u011bn\u00edme, aby nedo\u0161lo k konfliktu s nginx-proxy, kter\u00fd se instaluje pomoc\u00ed Kubespray. Mo\u017en\u00e1 to nebudete pot\u0159ebovat.<\/p>\n<p>Nainstalujeme Helm chart do clusteru Kubernetes:<\/p>\n<pre><code class=\"plaintext\">helm upgrade -i ceph-csi-cephfs ceph-csi\/ceph-csi-cephfs -f cephfs.yml -n ceph-csi-cephfs --create-namespace<\/code><\/pre>\n<p>P\u0159ejdeme do \u00falo\u017ei\u0161t\u011b dat Ceph, abychom zde vytvo\u0159ili samostatn\u00e9ho u\u017eivatele. V dokumentaci je uvedeno, \u017ee provizoru CephFS jsou pot\u0159eba administr\u00e1torsk\u00e1 pr\u00e1va pro cluster. Ale vytvo\u0159\u00edme samostatn\u00e9ho u\u017eivatele <em>fs<\/em> s omezen\u00fdmi pr\u00e1vy:<\/p>\n<pre><code class=\"plaintext\">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<p>A hned se pod\u00edv\u00e1me na jeho p\u0159\u00edstupov\u00fd kl\u00ed\u010d, kter\u00fd budeme pot\u0159ebovat d\u00e1le:<\/p>\n<pre><code class=\"plaintext\">ceph auth get-key client.fs<\/code><\/pre>\n<p>Vytvo\u0159\u00edme samostatn\u00e9 Secret a StorageClass.<br \/>\nNic nov\u00e9ho, u\u017e jsme to vid\u011bli na p\u0159\u00edkladu RBD:<\/p>\n<pre><code class=\"plaintext\">---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: csi-cephfs-secret\n  namespace: ceph-csi-cephfs\nstringData:\n  # Je nutn\u00e9 pro dynamicky vytv\u00e1\u0159en\u00e9 svazky\n  adminID: fs\n  adminKey:<\/code><\/pre>\n<p>Pou\u017e\u00edv\u00e1me manifest:<\/p>\n<pre><code class=\"plaintext\">kubectl apply -f secret.yaml<\/code><\/pre>\n<p>A nyn\u00ed \u2013 samostatn\u00fd StorageClass:<\/p>\n<pre><code class=\"plaintext\">---\napiVersion: storage.k8s.io\/v1\nkind: StorageClass\nmetadata:\n  name: csi-cephfs-sc\nprovisioner: cephfs.csi.ceph.com\nparameters:\n  clusterID: \n\n  # N\u00e1zev souborov\u00e9ho syst\u00e9mu CephFS, ve kter\u00e9m bude vytvo\u0159en objem\n  fsName: cephfs\n\n  # (voliteln\u00e9) Pool Ceph, ve kter\u00e9m budou ulo\u017eena data objemu\n  # pool: cephfs_data\n\n  # (voliteln\u00e9) Volby p\u0159ipojen\u00ed Ceph-fuse odd\u011blen\u00e9 \u010d\u00e1rkami\n  # nap\u0159\u00edklad:\n  # fuseMountOptions: debug\n\n  # (voliteln\u00e9) Volby p\u0159ipojen\u00ed CephFS pro j\u00e1dro odd\u011blen\u00e9 \u010d\u00e1rkami\n  # Viz man mount.ceph pro seznam t\u011bchto voleb. Nap\u0159\u00edklad:\n  # kernelMountOptions: readdir_max_bytes=1048576,norbytes\n\n  # Tajn\u00e9 kl\u00ed\u010de mus\u00ed obsahovat opr\u00e1vn\u011bn\u00ed pro admina a\/nebo u\u017eivatele 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  # (voliteln\u00e9) Ovlada\u010d m\u016f\u017ee pou\u017e\u00edvat bu\u010f ceph-fuse (fuse), \n  # nebo ceph kernelclient (kernel).\n  # Pokud nen\u00ed uvedeno, bude pou\u017eit v\u00fdchoz\u00ed zp\u016fsob p\u0159ipojen\u00ed objem\u016f, \n  # co\u017e je ur\u010deno hled\u00e1n\u00edm ceph-fuse a mount.ceph\n  # mounter: kernel\nreclaimPolicy: Delete\nallowVolumeExpansion: true\nmountOptions:\n  - debug<\/code><\/pre>\n<p>Vypln\u00edme to tady <strong>clusterID<\/strong> a aplikujeme v Kubernetes:<\/p>\n<pre><code class=\"plaintext\">kubectl apply -f storageclass.yaml<\/code><\/pre>\n<h2 id=\"proverka\">Kontrola<\/h2>\n<p>Pro kontrolu, jak bylo uvedeno v p\u0159edchoz\u00edm p\u0159\u00edkladu, vytvo\u0159\u00edme PVC:<\/p>\n<pre><code class=\"plaintext\">---\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<p>A zkontrolujeme existenci PVC\/PV:<\/p>\n<pre><code class=\"plaintext\">kubectl get pvc\nkubectl get pv<\/code><\/pre>\n<p>Pokud chcete vid\u011bt soubory a adres\u00e1\u0159e v CephFS, m\u016f\u017eete tento souborov\u00fd syst\u00e9m p\u0159ipojit n\u011bkde jinde. Nap\u0159\u00edklad, jak je uk\u00e1z\u00e1no n\u00ed\u017ee.<\/p>\n<p>P\u016fjdeme na jeden z uzl\u016f klastru Ceph a provedeme n\u00e1sleduj\u00edc\u00ed kroky:<\/p>\n<pre><code class=\"plaintext\"># \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 &gt;\/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\" &gt;&gt; \/etc\/fstab\n\nmount \/mnt\/cephfs<\/code><\/pre>\n<p>Samoz\u0159ejm\u011b, takov\u00e9 p\u0159ipojen\u00ed FS na uzlu Ceph je vhodn\u00e9 v\u00fdhradn\u011b pro v\u00fdukov\u00e9 \u00fa\u010dely, co\u017e d\u011bl\u00e1me na na\u0161ich <noindex><a rel=\"nofollow\" href=\"http:\/\/slurm.io\">kurzech Slurm<\/a><\/noindex>. Nemysl\u00edm si, \u017ee by to n\u011bkdo d\u011blal v produk\u010dn\u00edm prost\u0159ed\u00ed, je velk\u00e9 riziko omylem p\u0159epsat d\u016fle\u017eit\u00e9 soubory.<\/p>\n<p>A nakonec se pod\u00edvejme, jak je to v p\u0159\u00edpad\u011b CephFS se zm\u011bnou velikosti objemu. Vrac\u00edme se do Kubernetes a uprav\u00edme n\u00e1\u0161 manifest pro PVC \u2014 zv\u011bt\u0161\u00edme tam velikost, nap\u0159\u00edklad na 7Gi.<\/p>\n<p>Aplikujeme upraven\u00fd soubor:<\/p>\n<pre><code class=\"plaintext\">kubectl apply -f pvc.yaml<\/code><\/pre>\n<p>Pod\u00edv\u00e1me se na p\u0159ipojen\u00fd adres\u00e1\u0159, jak se zm\u011bnilo kv\u00f3ty:<\/p>\n<pre><code class=\"plaintext\">getfattr -n ceph.quota.max_bytes<\/code><\/pre>\n<p>K proveden\u00ed tohoto p\u0159\u00edkazu budete mo\u017en\u00e1 muset do syst\u00e9mu nainstalovat bal\u00ed\u010dek <strong>attr<\/strong>.<\/p>\n<h2 id=\"glaza-boyatsya-a-ruki-delayut\">O\u010di se boj\u00ed, ale ruce d\u011blaj\u00ed<\/h2>\n<p>Na prvn\u00ed pohled se v\u0161echny tyto magie a dlouh\u00e9 manifesty YAML zdaj\u00ed slo\u017eit\u00e9, ale v praxi si se nimi studenti Sl\u00e9rmu docela rychle porad\u00ed.<br \/>\nV tomto \u010dl\u00e1nku se nezab\u00fdv\u00e1me podrobnostmi \u2013 na to je ofici\u00e1ln\u00ed dokumentace. Pokud v\u00e1s zaj\u00edmaj\u00ed detaily nastaven\u00ed \u00falo\u017ei\u0161t\u011b Ceph v kombinaci s Kubernetes, pomohou tyto odkazy:<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/kubernetes.io\/docs\/concepts\/storage\/volumes\/\">Obecn\u00e9 principy fungov\u00e1n\u00ed Kubernetes s objemy<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/ceph.readthedocs.io\/en\/latest\/rbd\/\">Dokumentace k RBD<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/docs.ceph.com\/docs\/master\/rbd\/rbd-kubernetes\/\">Integrace RBD a Kubernetes z pohledu Ceph<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/ceph\/ceph-csi\/blob\/master\/docs\/deploy-rbd.md\">Integrace RBD a Kubernetes z pohledu CSI<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/ceph.readthedocs.io\/en\/latest\/cephfs\/\">Obecn\u00e1 dokumentace k CephFS<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/ceph\/ceph-csi\/blob\/master\/docs\/deploy-cephfs.md\">Integrace CephFS a Kubernetes z pohledu CSI<\/a><\/noindex><\/p>\n<p>Na kurzu Sl\u00e9rm <noindex><a rel=\"nofollow\" href=\"http:\/\/to.slurm.io\/6p9lng\">Z\u00e1klady Kubernetes<\/a><\/noindex> m\u016f\u017eete zaj\u00edt je\u0161t\u011b o kousek d\u00e1l a nasadit v Kubernetes skute\u010dnou aplikaci, kter\u00e1 bude pou\u017e\u00edvat CephFS jako \u00falo\u017ei\u0161t\u011b pro soubory. Pomoc\u00ed GET\/POST dotaz\u016f budete moci p\u0159en\u00e1\u0161et soubory a z\u00edsk\u00e1vat je z Ceph.<\/p>\n<p>A pokud v\u00e1s v\u00edce zaj\u00edm\u00e1 uchov\u00e1v\u00e1n\u00ed dat, p\u0159ihlaste se na <noindex><a rel=\"nofollow\" href=\"http:\/\/to.slurm.io\/WkM2Eg\">nov\u00fd kurz o Ceph<\/a><\/noindex>. B\u011bhem beta testov\u00e1n\u00ed lze kurz z\u00edskat se slevou a ovlivnit jeho obsah.<\/p>\n<p><em>Autor \u010dl\u00e1nku: Alexander Shvalov, praktikuj\u00edc\u00ed in\u017een\u00fdr <noindex><a rel=\"nofollow\" href=\"http:\/\/to.slurm.io\/ophLww\">Southbridge<\/a><\/noindex>, Certified Kubernetes Administrator, autor a v\u00fdvoj\u00e1\u0159 kurz\u016f Sl\u00e9rm.<\/em><\/p>\n<p>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/519642\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>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 [&hellip;]<\/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<!-- All in One SEO 5.0.3 - aioseo.com -->\n\t<meta name=\"description\" content=\"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.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"cs_CZ\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\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\" \/>\n\t\t<meta property=\"og:description\" content=\"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.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-09-20T17:42:27+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2021-01-02T11:05:08+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Praktick\u00fd p\u0159\u00edklad p\u0159ipojen\u00ed \u00falo\u017ei\u0161t\u011b zalo\u017een\u00e9ho na Ceph do clusteru Kubernetes | ProHoster","description":"Container Storage Interface (CSI) je unifikovan\u00e9 rozhran\u00ed pro interakci Kubernetes a syst\u00e9m\u016f pro ukl\u00e1d\u00e1n\u00ed dat.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/prakticheskij-primer-podklyucheniya-hranilishha-na-baze-ceph-v-klaster-kubernetes","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","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.","og:url":"https:\/\/prohoster.info\/cs\/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","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/94739","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=94739"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/94739\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/94740"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=94739"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=94739"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=94739"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}