{"id":77266,"date":"2020-04-09T13:42:08","date_gmt":"2020-04-09T11:42:08","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/tips-tricks-v-rabote-s-ceph-v-nagruzhennyh-proektah"},"modified":"2020-04-09T13:42:08","modified_gmt":"2020-04-09T11:42:08","slug":"tips-tricks-v-rabote-s-ceph-v-nagruzhennyh-proektah","status":"publish","type":"post","link":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/tips-tricks-v-rabote-s-ceph-v-nagruzhennyh-proektah","title":{"rendered":"N\u00e4pun\u00e4ited ja trikid Ceph-i kasutamiseks koormatud projektides","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Nipid ja trikid Ceph&#039;iga t\u00f6\u00f6tamiseks koormatud projektides\" src=\"\/wp-content\/uploads\/2020\/04\/1d60f91e55b20a5dc4346bd8087bc11e.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKasutades Ceph'i kui v\u00f5rgu salvestusruumi erinevate koormustega projektides, v\u00f5ime kokku puutuda erinevate probleemidega, mis esmapilgul ei tundu lihtsad v\u00f5i triviaalsetena. N\u00e4iteks:<\/p>\n<ul>\n<li> andmete migratsioon vana Ceph'ist uude, osaliselt kasutades eelmisi servereid uues klastris;<\/li>\n<li> probleemi lahendamine Ceph'i kettaruumi jaotuse osas.<\/li>\n<\/ul>\n<p>\nSelliste \u00fclesannete lahendamisel seisame silmitsi vajadusega \u00f5igesti eemaldada OSD andmete kaotamata, mis on eriti oluline suurte andmemahtude korral. Just sellest juttu tuleb artiklis.<\/p>\n<p>Allpool kirjeldatud meetodid kehtivad k\u00f5ikide Ceph'i versioonide jaoks. Lisaks arvestatakse selle faktiga, et Ceph's v\u00f5ib talletuda suur andmemahutus: andmete kaotuse ja muude probleemide v\u00e4ltimiseks jagatakse m\u00f5ned toimingud mitmeks.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Eess\u00f5na OSD-st<\/h3>\n<p>\nKuna kaks kolmest k\u00e4sitletavast retseptist on p\u00fchendatud OSD-le (<noindex><a rel=\"nofollow\" href=\"https:\/\/docs.ceph.com\/docs\/master\/man\/8\/ceph-osd\/\">Objekti salvestamise deemon<\/a><\/noindex>), enne praktilisse ossa sukeldumist \u2014 l\u00fchidalt, mis see tegelikult on Ceph'is ja miks see on nii oluline.<\/p>\n<p>Esiteks tuleb \u00f6elda, et kogu Ceph'i klaster koosneb paljusid OSD-dest. Mida rohkem neid on, seda suurem on vaba andmemaht Ceph'is. Sealt on lihtne m\u00f5ista <b>OSD peamist funktsiooni<\/b>: see salvestab Ceph'i objektide andmed klastris olevate node'ide failis\u00fcsteemidesse ja pakub neile v\u00f5rgu ligip\u00e4\u00e4su (lugemiseks, kirjutamiseks ja muudele p\u00e4ringutele).<\/p>\n<p>Samuti seadistatakse replikatsiooni parameetrid, kopeerides objekte erinevate OSD-de vahel. Ja siin v\u00f5ime kokku puutuda erinevate probleemidega, mille lahendamist k\u00e4sitletakse hiljem.<\/p>\n<h2>Juhtum nr 1. OSD turvaline eemaldamine Ceph'i klastrist andmete kaotamata<\/h2>\n<p>\nOSD eemaldamise vajadus v\u00f5ib tuleneda serveri eemaldamisest klastrist - n\u00e4iteks asendamiseks teise serveriga - mis juhtus ka meie puhul, andes p\u00f5hjuse artikli kirjutamiseks. Seega on operatsioonide l\u00f5ppeesm\u00e4rk eemaldada k\u00f5ik OSD-d ja mon\u2019id antud serveris, et see saaks v\u00e4lja l\u00fclitada.<\/p>\n<p>Mugavuse ja olukorra v\u00e4ltimiseks, kus oleme k\u00e4skude t\u00e4itmise protsessis eksinud vajaliku OSD m\u00e4\u00e4ramisel, seame eraldi muutuja, mille v\u00e4\u00e4rtuseks saab eemaldatava OSD number. Nimetame selle <code>${ID}<\/code> \u2014 siin ja edaspidi asendab see muutuja OSD numbri, millega me t\u00f6\u00f6tame.<\/p>\n<p>Vaadake seisundit enne t\u00f6\u00f6de alustamist:<\/p>\n<pre><code class=\"bash\">root@hv-1 ~ # ceph osd tree\nID CLASS WEIGHT  TYPE NAME      STATUS REWEIGHT PRI-AFF\n-1       0.46857 root default\n-3       0.15619      host hv-1\n-5       0.15619      host hv-2\n 1   ssd 0.15619      osd.1     up     1.00000  1.00000\n-7       0.15619      host hv-3\n 2   ssd 0.15619      osd.2     up     1.00000  1.00000<\/code><\/pre>\n<p>\nOSD eemaldamiseks on vajalik sujuvalt <code>reweight<\/code> seda nulli. Nii v\u00e4hendame OSD-s olevate andmete hulka, suunates need teistesse OSD-desse. Selle jaoks tuleb k\u00e4ivitada j\u00e4rgmised k\u00e4sud:<\/p>\n<pre><code class=\"bash\">ceph osd reweight osd.${ID} 0.98\nceph osd reweight osd.${ID} 0.88\nceph osd reweight osd.${ID} 0.78<\/code><\/pre>\n<p>\n\u2026 ja nii edasi kuni nullini.<\/p>\n<p><b>Sujuv tasakaalustus on vajalik<\/b>, et andmeid ei kaotataks. See on eriti oluline, kui OSD-s on palju andmeid. Et veenduda, et p\u00e4rast k\u00e4skude t\u00e4itmist <code>reweight<\/code> on k\u00f5ik l\u00e4inud edukalt, saab k\u00e4ivitada <code>ceph -s<\/code> v\u00f5i avada eraldi terminaliaknas <code>ceph -w<\/code> kui soovite j\u00e4lgida muudatusi reaalajas.<\/p>\n<p>Kui OSD on \"t\u00fchjendatud\", saab alustada selle eemaldamise standardset protseduuri. Selleks viime soovitud OSD seisundisse <code>down<\/code>:<\/p>\n<pre><code class=\"bash\">ceph osd down osd.${ID}<\/code><\/pre>\n<p>\n\"T\u00f5mbame\" OSD klastrist v\u00e4lja:<\/p>\n<pre><code class=\"bash\">ceph osd out osd.${ID}<\/code><\/pre>\n<p>\nPeatame OSD teenuse ja eemaldame selle jagamise failis\u00fcsteemist:<\/p>\n<pre><code class=\"bash\">systemctl stop ceph-osd@${ID}\numount \/var\/lib\/ceph\/osd\/ceph-${ID}<\/code><\/pre>\n<p>\nEemaldame OSD <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.ceph.com\/docs\/nautilus\/rados\/operations\/crush-map\/\">CRUSH kaardist<\/a><\/noindex>:<\/p>\n<pre><code class=\"bash\">ceph osd crush remove osd.${ID}<\/code><\/pre>\n<p>\nEemaldame OSD kasutaja:<\/p>\n<pre><code class=\"bash\">ceph auth del osd.${ID}<\/code><\/pre>\n<p>\nJa l\u00f5puks eemaldame ise OSD:<\/p>\n<pre><code class=\"bash\">ceph osd rm osd.${ID}<\/code><\/pre>\n<p>\n<b>M\u00e4rkus<\/b>: kui kasutate Ceph Luminous v\u00f5i uuemat versiooni, siis v\u00f5ivad \u00fclaltoodud OSD eemaldamise toimetamised kokku leppida kahes k\u00e4sus:<\/p>\n<pre><code class=\"bash\">ceph osd out osd.${ID}\nceph osd purge osd.${ID}\n<\/code><\/pre>\n<p>\nKui p\u00e4rast \u00fclaltoodud k\u00e4skude t\u00e4itmist k\u00e4ivitada k\u00e4sk <code>ceph osd tree<\/code>, siis peaks olema n\u00e4ha, et serveris, kus t\u00f6\u00f6d tehti, pole enam OSD-sid, mille jaoks operatsioone tehti:<\/p>\n<pre><code class=\"bash\">root@hv-1 ~ # ceph osd tree\nID CLASS WEIGHT  TYPE NAME     STATUS REWEIGHT PRI-AFF\n-1       0.46857      root default\n-3       0.15619      host hv-1\n-5       0.15619      host hv-2\n-7       0.15619      host hv-3\n 2   ssd 0.15619      osd.2    up     1.00000  1.00000<\/code><\/pre>\n<p>\nM\u00e4rgin ka, et Ceph klastri olek muudab <code>HEALTH_WARN<\/code>, samuti m\u00e4rkame OSD-de arvu v\u00e4hendamist ja saadaval oleva kettaruumi v\u00e4henemist. <\/p>\n<p>Edasi kirjeldatakse toiminguid, mis on vajalikud, kui soovite serveri t\u00e4ielikult peatada ja seega ka Ceph-st eemaldada. Sellisel juhul on oluline meeles pidada, et <b>enne serveri v\u00e4ljal\u00fclitamist tuleb eemaldada k\u00f5ik OSD-d<\/b> selles serveris.<\/p>\n<p>Kui selles serveris pole enam OSD-sid, tuleb nende eemaldamise j\u00e4rel OSD kaardilt v\u00e4lja j\u00e4tta server <code>hv-2<\/code>, k\u00e4ivitades j\u00e4rgmise k\u00e4su:<\/p>\n<pre><code class=\"bash\">ceph osd crush rm hv-2<\/code><\/pre>\n<p>\nKustutame <code>mon<\/code> serverist <code>hv-2<\/code>, k\u00e4ivitades alloleva k\u00e4su teises serveris (st sel juhul \u2014 <code>hv-1<\/code>):<\/p>\n<pre><code class=\"bash\">ceph-deploy mon destroy hv-2<\/code><\/pre>\n<p>\nP\u00e4rast seda v\u00f5ib serveri kinni panna ja liikuda j\u00e4rgmiste toimingute juurde (n\u00e4iteks selle uuesti seadistamine jne.).<\/p>\n<h2>Juhtum nr 2. Diskiruumi jaotus juba loodud Ceph-klastris<\/h2>\n<p>\nTeise loo alustamiseks teen sissejuhatuse PG (<noindex><a rel=\"nofollow\" href=\"https:\/\/docs.ceph.com\/docs\/mimic\/rados\/operations\/placement-groups\/\">Placement Groups<\/a><\/noindex>). PG peamine roll Cephis on eelk\u00f5ige Ceph-objektide agregatsioon ja edasine replikatsioon OSDs. PG vajaliku arvu arvutamise valem on toodud <noindex><a rel=\"nofollow\" href=\"https:\/\/docs.ceph.com\/docs\/mimic\/rados\/operations\/placement-groups\/#choosing-the-number-of-placement-groups\">vastavas jaos<\/a><\/noindex> Cephi dokumentatsioonis. Seal k\u00e4sitletakse seda k\u00fcsimust ka konkreetsete n\u00e4idete kaudu.<\/p>\n<p>Nii et \u00fcks levinumaid probleme Cephi kasutamise ajal on OSD ja PG vahelise tasakaalu puudumine klastris.<\/p>\n<p>Esiteks v\u00f5ib see tekitada olukorra, kus v\u00e4ikese mahuga basseinis on liiga palju PG-sid, mis on sisuliselt diskiruumi ebaefektiivne kasutamine klastris. Teiseks, praktikas tekib t\u00f5sisem probleem: andmete \u00fclek\u00fcllus \u00fches OSD-s. See toob kaasa klastris k\u00f5igepealt oleku <code>HEALTH_WARN<\/code>, ja siis <code>HEALTH_ERR<\/code>. K\u00f5ik selle t\u00f5ttu, et Ceph arvutab saadaval oleva andmemahu (mida saab kontrollida <code>MAX AVAIL<\/code> k\u00e4sku andmete v\u00e4ljastamise ajal <code>ceph df<\/code> iga basseini kohta eraldi) OSD-s saadaval oleva andmemahu p\u00f5hjal. Kui v\u00e4hemalt \u00fches OSD-s on ruumi liiga v\u00e4he, siis rohkem andmeid salvestada ei \u00f5nnestu, kuni andmed on k\u00f5ikides OSD-des korralikult jaotatud.<\/p>\n<p>Oluline on m\u00e4rkida, et need probleemid <b>lahendatakse suuresti Ceph-klastri seadistamise etapis.<\/b>\u00dcks t\u00f6\u00f6riist, mida kasutada, on <noindex><a rel=\"nofollow\" href=\"http:\/\/blog.easter-eggs.org\/index.php\/post\/2013\/09\/27\/%5BLibvirt%5D-Migrating-from-on-disk-raw-images-to-RBD-storage\">Ceph PGCalc<\/a><\/noindex>. Selle abil arvutatakse visuaalselt vajalik PG-de arv. Sellegipoolest v\u00f5ib selle poole p\u00f6\u00f6rduda ka olukordades, kui Ceph-klaster <i>juba<\/i> on vale seadistusega. Siinkohal tuleb m\u00e4rkida, et t\u00f5rgete parandamise k\u00e4igus peate t\u00f5en\u00e4oliselt PG-de arvu v\u00e4hendama, kuid see v\u00f5imalus ei ole vanades Cephi versioonides saadaval (see ilmus alles versiooniga <noindex><a rel=\"nofollow\" href=\"https:\/\/ceph.com\/rados\/new-in-nautilus-pg-merging-and-autotuning\/\">Nautilus<\/a><\/noindex>).<\/p>\n<p>Nii et kujutame ette j\u00e4rgmist stsenaariumi: klastril on olek <code>HEALTH_WARN<\/code> selle t\u00f5ttu, et \u00fches OSD-s on ruum otsa saamas. Seda t\u00f5endab t\u00f5rge <code>HEALTH_WARN: 1 near full osd<\/code>. Allpool on toodud algoritm, et sellisest olukorrast v\u00e4lja p\u00e4\u00e4seda.<\/p>\n<p>Esmalt on vaja olemasolevad andmed jagada teiste OSDe vahel. Sarnast toimingut oleme juba teinud esimeses juhtumis, kui me \"kuivasime\" s\u00f5lme \u2014 ainsaks erinevuseks on see, et n\u00fc\u00fcd tuleb v\u00e4\u00e4rtust veidi v\u00e4hendada. <code>reweight<\/code>. N\u00e4iteks 0.95:<\/p>\n<pre><code class=\"bash\">ceph osd reweight osd.${ID} 0.95<\/code><\/pre>\n<p>\nNii vabanevad OSDes kettaruumi ja k\u00f5rvaldatakse viga ceph health'is. Siiski, nagu juba mainitud, tekib see probleem enamasti vale Cephi seadistamise t\u00f5ttu algstaadiumis: on \u00e4\u00e4rmiselt oluline teha rekondigureerimine, et see ei korduks tulevikus.<\/p>\n<p>Meie konkreetses juhul k\u00f5ik seisnes:<\/p>\n<ul>\n<li> liialt k\u00f5rge v\u00e4\u00e4rtus <code>replication_count<\/code> \u00fches basseinist,<\/li>\n<li> liialt k\u00f5rge PG arv \u00fches basseinist ja liiga madal \u2014 teises. <\/li>\n<\/ul>\n<p>\nKasutame juba mainitud kalkulaatorit. Selles on selgelt n\u00e4ha, mida sisestada, ja p\u00f5him\u00f5tteliselt pole seal midagi keerulist. Sisestades vajalikud parameetrid, saame j\u00e4rgmised soovitused:<\/p>\n<p><i><b>M\u00e4rkus<\/b>: kui seadistate Cephi klastrit nullist, osutub kalkulaatori abiks veel \u00fcks kasulik funktsioon, nimelt k\u00e4skude genereerimine, mis loob basseinid nullist tabelis toodud parameetritega.<\/i><\/p>\n<p>Kitsendatud aitab viimane veerg \u2014 <i>Suggested PG Count<\/i>. Meie puhul on kasulik ka teine, kus on m\u00e4rgitud replikatsiooni parameeter, kuna otsustasime muuta ka replikatsiooni kordajat.<\/p>\n<p>Nii et esmalt tuleb muuta replikatsiooni parameetreid \u2014 seda tuleks teha esimesena, kuna kordaja v\u00e4hendamine vabastab kettaruumi. K\u00e4skude t\u00e4itmise protsessis v\u00f5ib t\u00e4heldada, et vaba kettamaht kasvab:<\/p>\n<pre><code class=\"bash\">ceph osd pool $pool_name set $replication_size<\/code><\/pre>\n<p>\nJa p\u00e4rast selle l\u00f5petamist \u2014 muutke parameetreid <code>pg_num<\/code> ja <code>pgp_num<\/code> j\u00e4rgmiselt:<\/p>\n<pre><code class=\"bash\">ceph osd pool set $pool_name pg_num $pg_number\nceph osd pool set $pool_name pgp_num $pg_number<\/code><\/pre>\n<p>\n<b>Oluline<\/b>: peame j\u00e4rjestikku igas basseinis muutma PG arvu ja mitte muutma v\u00e4\u00e4rtusi teistes basseinides, kuni hoiatused kaovad <i>\"Degraded data redundancy\"<\/i> ja <i>\"n-number of pgs degraded\"<\/i>.<\/p>\n<p>Kontrollida, et k\u00f5ik l\u00e4ks sujuvalt, saab ka k\u00e4skude v\u00e4ljundite kaudu <code>ceph health detail<\/code> ja <code>ceph -s<\/code>.<\/p>\n<h2>Juhtum nr 3. Virtuaalse masina migratsioon LVM-ist Ceph RBD-sse<\/h2>\n<p>\nKui projektis kasutatakse virtuaalseid masinaid, mis on paigaldatud renditud bare-metal serveritele, tekib sageli k\u00fcsimus, kuidas tagada uuendatav salvestuslahendus. Samuti on oluline, et salvestuspinda oleks piisavalt... Teine levinud olukord: virtuaalne masin, millel on serveris kohalik salvestus, vajab ketta laiendamist, aga vaba kettaruumi pole j\u00e4\u00e4nud.<\/p>\n<p>Selle probleemi saab lahendada erinevate meetoditega \u2014 n\u00e4iteks migratsiooniga teisele serverile (kui selline on olemas) v\u00f5i uute ketaste lisamisega serverisse. Kuid see ei \u00f5nnestu alati, seega v\u00f5ib migratsioon LVM-ist Ceph-i olla suurep\u00e4rane lahendus. Sellise variandi valimisel lihtsustame ka edasist migratsiooniprotsessi serverite vahel, sest ei ole vaja kohalikku salvestust \u00fchest h\u00fcperviisorist teise viia. Ainuke takistus on see, et virtuaalne masin tuleb t\u00f6\u00f6de ajaks peatada.<\/p>\n<p>Tuleks tuua j\u00e4rgmine retsept <noindex><a rel=\"nofollow\" href=\"http:\/\/blog.easter-eggs.org\/index.php\/post\/2013\/09\/27\/%5BLibvirt%5D-Migrating-from-on-disk-raw-images-to-RBD-storage\">selle blogi artiklist<\/a><\/noindex>, mille juhised on praktikas proovitud. Muide, <b>seal on kirjeldatud ka s\u00fcsteemi migratsiooni viisi,<\/b>aga meie juhul ei olnud see vajalik, seega me ei kontrollinud seda. Kui see on teie projekti jaoks kriitiline \u2014 oleme t\u00e4nulikud, kui jagate tulemusi kommentaarides.<\/p>\n<p>L\u00e4heme praktilise osa juurde. N\u00e4ites kasutame virsh\u2019i ja vastavalt libvirt\u2019i. Esiteks veenduge, et Ceph\u2019i bassein, kuhu andmed migratsiooniks suunatakse, on libvirt\u2019iga \u00fchendatud:<\/p>\n<pre><code class=\"bash\">virsh pool-dumpxml $ceph_pool<\/code><\/pre>\n<p>\nBasseini kirjelduses peaksid olema Ceph\u2019i \u00fchenduse andmed koos autoriseerimise andmetega. <\/p>\n<p>J\u00e4rgmine samm on see, et LVM-pilt konverteeritakse Ceph RBD-ks. T\u00e4itmise aeg s\u00f5ltub peamiselt pildi suurusest:<\/p>\n<pre><code class=\"bash\">qemu-img convert -p -O rbd \/dev\/main\/$vm_image_name rbd:$ceph_pool\/$vm_image_name<\/code><\/pre>\n<p>\nP\u00e4rast konversiooni j\u00e4\u00e4b LVM-pilt, mis on kasulik juhul, kui migratsioon virtuaalsest masinast RBD-sse ei \u00f5nnestu ja muudatused tuleb tagasi rullida. Samuti \u2014 muutuste kiireks tagasi rullimiseks \u2014 teeme varukoopia virtuaalse masina konfigureerimisfailist:<\/p>\n<pre><code class=\"bash\">virsh dumpxml $vm_name &gt; $vm_name.xml\ncp $vm_name.xml $vm_name_backup.xml<\/code><\/pre>\n<p>\n\u2026 ja redigeerime originaali (<code>vm_name.xml<\/code>). Leidke plokk ketta kirjeldusega (algab realt <code>&lt;disk type='file' device='disk'&gt;<\/code> ja l\u00f5peb <code>&lt;\/disk&gt;<\/code>) ja toome selle j\u00e4rgmisesse vormi:<\/p>\n<pre><code class=\"xml\"><address \/><\/code><\/pre>\n<p>\nVaatame m\u00f5ningaid detaile:<\/p>\n<ol>\n<li> Protokollis <code>source<\/code> tuletatakse vahehoidla aadress Ceph RBD (see on aadress, mis n\u00e4itab Ceph basseini ja RBD pilti, mis m\u00e4\u00e4rati esimeses etapis).<\/li>\n<li> Plokis <code>secret<\/code> n\u00e4idatakse t\u00fc\u00fcpi <code>ceph<\/code>, samuti salajase ID, et kasutada sellele \u00fchendust. Selle uuid'i saab teada k\u00e4suga <code>virsh secret-list<\/code>.<\/li>\n<li> Plokis <code>host<\/code> n\u00e4idatakse Ceph j\u00e4lgijate aadresse.<\/li>\n<\/ol>\n<p>\nP\u00e4rast konfiguratsioonifaili redigeerimist ja LVM-i \u00fcmberkujundamist RBD-sse saab rakendada muudetud konfiguratsioonifaili ja k\u00e4ivitada virtuaalse masina:<\/p>\n<pre><code class=\"bash\">virsh define $vm_name.xml\nvirsh start $vm_name<\/code><\/pre>\n<p>\nOn aeg kontrollida, kas virtuaalne masin k\u00e4ivitus \u00f5igesti: seda saab teha n\u00e4iteks, \u00fchendudes temaga SSH kaudu v\u00f5i l\u00e4bi <code>virsh<\/code>. <\/p>\n<p>Kui virtuaalne masin t\u00f6\u00f6tab \u00f5igesti ja te ei leidnud muid probleeme, saate eemaldada LVM-pildi, mis ei ole enam kasutuses:<\/p>\n<pre><code class=\"bash\">lvremove main\/$vm_image_name<\/code><\/pre>\n<p><\/p>\n<h2>Kokkuv\u00f5te<\/h2>\n<p>\nK\u00f5ikide kirjeldatud juhtumite korral oleme praktikas kokku puutunud \u2014 loodame, et juhised aitavad ka teisi haldureid sarnaste probleemide lahendamisel. Kui teil on m\u00e4rkusi v\u00f5i muid sarnaseid kogemusi Ceph'i kasutamisest \u2014 oleksime r\u00f5\u00f5msad neid kommenteerida!<\/p>\n<h2>P.S.<\/h2>\n<p>\nLugege ka meie blogist:<\/p>\n<ul>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/477680\/\">Meie k\u00e4ed ei ole igavlemiseks: Rooki klastri taastamine K8s'is<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/451818\/\">Rook v\u00f5i mitte Rook \u2014 see on k\u00fcsimus<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/348044\/\">Rook on \u201eiseteenindav\u201c andmesalvestus Kubernetes'i jaoks<\/a><\/noindex>\u00bb;<\/li>\n<li> \u00ab<noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/329666\/\">Loome p\u00fcsiva salvestuse Kubernetese Ceph'i baasprovisioneerimisega<\/a><\/noindex>\u00bb.<\/li>\n<\/ul>\n<p>Allikas: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/flant\/blog\/495870\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0418\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044f Ceph \u043a\u0430\u043a \u0441\u0435\u0442\u0435\u0432\u043e\u0435 \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0435 \u0432 \u0440\u0430\u0437\u043d\u044b\u0445 \u043f\u043e \u043d\u0430\u0433\u0440\u0443\u0436\u0435\u043d\u043d\u043e\u0441\u0442\u0438 \u043f\u0440\u043e\u0435\u043a\u0442\u0430\u0445, \u043c\u044b \u043c\u043e\u0436\u0435\u043c \u0441\u0442\u043e\u043b\u043a\u043d\u0443\u0442\u044c\u0441\u044f \u0441 \u0440\u0430\u0437\u043b\u0438\u0447\u043d\u044b\u043c\u0438 \u0437\u0430\u0434\u0430\u0447\u0430\u043c\u0438, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0441 \u043f\u0435\u0440\u0432\u043e\u0433\u043e \u0432\u0437\u0433\u043b\u044f\u0434\u0430 \u043d\u0435 \u043a\u0430\u0436\u0443\u0442\u0441\u044f \u043f\u0440\u043e\u0441\u0442\u044b\u043c\u0438 \u0438\u043b\u0438 \u0442\u0440\u0438\u0432\u0438\u0430\u043b\u044c\u043d\u044b\u043c\u0438. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440: \u043c\u0438\u0433\u0440\u0430\u0446\u0438\u044f \u0434\u0430\u043d\u043d\u044b\u0445 \u0438\u0437 \u0441\u0442\u0430\u0440\u043e\u0433\u043e Ceph \u0432 \u043d\u043e\u0432\u044b\u0439 \u0441 \u0447\u0430\u0441\u0442\u0438\u0447\u043d\u044b\u043c \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0438\u0445 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432 \u0432 \u043d\u043e\u0432\u043e\u043c \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u0435; \u0440\u0435\u0448\u0435\u043d\u0438\u0435 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u0435\u043d\u0438\u044f \u0434\u0438\u0441\u043a\u043e\u0432\u043e\u0433\u043e \u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0441\u0442\u0432\u0430 \u0432 Ceph. \u0420\u0430\u0437\u0431\u0438\u0440\u0430\u044f\u0441\u044c \u0441 \u0442\u0430\u043a\u0438\u043c\u0438 \u0437\u0430\u0434\u0430\u0447\u0430\u043c\u0438, \u043c\u044b \u0441\u0442\u0430\u043b\u043a\u0438\u0432\u0430\u0435\u043c\u0441\u044f \u0441 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":77267,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-77266","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.1.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0418\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044f Ceph \u043a\u0430\u043a \u0441\u0435\u0442\u0435\u0432\u043e\u0435 \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0435 \u0432.\" \/>\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\/et\/blog\/administrirovanie\/tips-tricks-v-rabote-s-ceph-v-nagruzhennyh-proektah\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"et_EE\" \/>\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\udd47Tips &amp; tricks \u0432 \u0440\u0430\u0431\u043e\u0442\u0435 \u0441 Ceph \u0432 \u043d\u0430\u0433\u0440\u0443\u0436\u0435\u043d\u043d\u044b\u0445 \u043f\u0440\u043e\u0435\u043a\u0442\u0430\u0445 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0418\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044f Ceph \u043a\u0430\u043a \u0441\u0435\u0442\u0435\u0432\u043e\u0435 \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0435 \u0432.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/tips-tricks-v-rabote-s-ceph-v-nagruzhennyh-proektah\" \/>\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-04-09T11:42:08+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-04-09T11:42: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\udd47Nipid ja trikid Ceph'iga t\u00f6\u00f6tamiseks koormatud projektides | ProHoster","description":"Kasutades Ceph'i kui v\u00f5rgus\u00fcsteemi.","canonical_url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/tips-tricks-v-rabote-s-ceph-v-nagruzhennyh-proektah","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"et_EE","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\udd47Tips &amp; tricks \u0432 \u0440\u0430\u0431\u043e\u0442\u0435 \u0441 Ceph \u0432 \u043d\u0430\u0433\u0440\u0443\u0436\u0435\u043d\u043d\u044b\u0445 \u043f\u0440\u043e\u0435\u043a\u0442\u0430\u0445 | ProHoster","og:description":"\u0418\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044f Ceph \u043a\u0430\u043a \u0441\u0435\u0442\u0435\u0432\u043e\u0435 \u0445\u0440\u0430\u043d\u0438\u043b\u0438\u0449\u0435 \u0432.","og:url":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/tips-tricks-v-rabote-s-ceph-v-nagruzhennyh-proektah","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-04-09T11:42:08+00:00","article:modified_time":"2020-04-09T11:42:08+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"77266","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 17:20:51","updated":"2022-10-02 10:23:09","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/77266","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/comments?post=77266"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/77266\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/77267"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=77266"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=77266"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=77266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}