{"id":33803,"date":"2019-10-31T21:54:45","date_gmt":"2019-10-31T18:54:45","guid":{"rendered":"https:\/\/prohoster.info\/blog\/on-vam-ne-drook\/"},"modified":"2019-10-31T21:54:45","modified_gmt":"2019-10-31T18:54:45","slug":"on-vam-ne-drook","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/on-vam-ne-drook","title":{"rendered":"Ai nuk \u00ebsht\u00eb dRook p\u00ebr ty","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Me q\u00eb po b\u00ebhet gjithnj\u00eb e m\u00eb popullor Rook, d\u00ebshiroj t\u00eb flas p\u00ebr pengesat dhe problemet q\u00eb ju presin n\u00eb rrug\u00eb.<\/p>\n

P\u00ebr veten: Eksperienc\u00eb n\u00eb administrimin e ceph nga versioni hammer, themelues i komunitetit t.me\/ceph_ru<\/a><\/noindex> n\u00eb telegram.<\/p>\n

P\u00ebr t\u00eb mos qen\u00eb thjesht fjal\u00eb boshe, do t\u00eb referohem n\u00eb postimet e pranuara n\u00eb habr (sipas rendit) p\u00ebr problemet me ceph. Me shumic\u00ebn e k\u00ebtyre problemeve kam hasur edhe un\u00eb. Lidhjet me materialin e p\u00ebrdorur n\u00eb fund t\u00eb postit.<\/p>\n

N\u00eb postimin p\u00ebr Rook ne p\u00ebrmendim ceph jo rast\u00ebsisht \u2014 Rook n\u00eb thelb \u00ebsht\u00eb ceph i mb wrapped n\u00eb kubernetes, dhe kjo do t\u00eb thot\u00eb se trash\u00ebgon t\u00eb gjitha problemet e tij. Nga problemet e ceph edhe do t\u00eb fillojm\u00eb.
\n<\/a><\/noindex><\/p>\n

Thjeshtimi i menaxhimit t\u00eb klasterit<\/h3>\n

\nNj\u00eb nga avantazhet e Rook \u00ebsht\u00eb leht\u00ebsia e menaxhimit t\u00eb ceph p\u00ebrmes kubernetes.<\/p>\n

Megjithat\u00eb, ceph ka m\u00eb shum\u00eb se 1000 parametra p\u00ebr konfigurim, n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb p\u00ebrmes rook ne mund t\u00eb rregullojm\u00eb vet\u00ebm nj\u00eb pjes\u00eb t\u00eb vog\u00ebl t\u00eb tyre.<\/p>\n

Shembull n\u00eb Luminous
\n> ceph daemon mon.a config show | wc -l
\n1401<\/p><\/blockquote>\n

Rook pozicionohet si nj\u00eb m\u00ebnyr\u00eb e leht\u00eb p\u00ebr t\u00eb instaluar dhe p\u00ebrdit\u00ebsuar ceph<\/b>
\nMe instalimin e ceph pa Rook nuk ka asnj\u00eb problem \u2014 skenari ansible shkruhet p\u00ebr 30 minuta, por me p\u00ebrdit\u00ebsimin ka masa t\u00eb m\u00ebdha problematikash. <\/p>\n

Citim nga posta e Krok<\/i><\/p>\n

Shembull: funksionimi i gabuar i crush tunables pas p\u00ebrdit\u00ebsimit nga hummer n\u00eb jewel<\/p>\n

> ceph osd crush show-tunables
\n{
\n\u2026
\n \u00abstraw_calc_version\u00bb: 1,
\n \u00aballowed_bucket_algs\u00bb: 22,
\n \u00abprofile\u00bb: \u00abunknown\u00bb,
\n \u00aboptimal_tunables\u00bb: 0,
\n\u2026
\n}<\/p><\/blockquote>\n

Por edhe n\u00eb kuad\u00ebr t\u00eb versioneve m\u00eb t\u00eb vogla ka probleme.<\/p>\n

Shembull: P\u00ebrdit\u00ebsimi 12.2.6 q\u00eb \u00e7on klasterin n\u00eb gjendjen health err dhe PG n\u00eb gjendje t\u00eb mbase t\u00eb d\u00ebmtuar
\nceph.com\/releases\/v12-2-8-released<\/a><\/noindex><\/p>\n

Nuk p\u00ebrdit\u00ebsohet, prit dhe testoni? Por ne duket se p\u00ebrdorim Rook edhe p\u00ebr leht\u00ebsimin e p\u00ebrdit\u00ebsimeve.<\/p>\n

V\u00ebshtir\u00ebsia e rikuperimit n\u00eb katastrof\u00eb t\u00eb klasterit n\u00eb Rook <\/h3>\n

\nShembull: OSD bie me gabim duke hedhur probleme posht\u00eb vetes. Ju dyshoni se problemi \u00ebsht\u00eb n\u00eb nj\u00eb nga parametrat n\u00eb konfigurim, d\u00ebshironi t\u00eb ndryshoni konfigurimin p\u00ebr nj\u00eb demon t\u00eb caktuar, por nuk mundeni, sepse keni kubernetes dhe DaemonSet.<\/p>\n

Nuk ka alternativ\u00eb. ceph tell osd.Num injectargs nuk funksionon \u2014 OSD \u00ebsht\u00eb i shtrir\u00eb.<\/p>\n

V\u00ebshtir\u00ebsia e debug<\/h3>\n

\nP\u00ebr disa konfigurime dhe teste t\u00eb performanc\u00ebs \u00ebsht\u00eb e nevojshme t\u00eb lidheni direkt me soketin e demonit osd. N\u00eb rastin e Rook, p\u00ebr fillim duhet t\u00eb gjeni kontejnerin e duhur, pastaj t\u00eb hyni n\u00eb t\u00eb, t\u00eb zbulojn\u00eb munges\u00ebn e mjeteve p\u00ebr debug dhe t\u00eb shqet\u00ebsohen shum\u00eb.<\/p>\n

V\u00ebshtir\u00ebsia e koleksionit t\u00eb OSD n\u00eb m\u00ebnyr\u00eb t\u00eb nd\u00ebrsjell\u00eb<\/h3>\n

\nShembull: OSD bie p\u00ebr shkak t\u00eb OOM, fillon rebalance, pas k\u00ebsaj bien t\u00eb tjer\u00ebt.<\/p>\n

Zgjidhja: Ngri OSD-n\u00eb nj\u00eb nga nj\u00eb, pritni q\u00eb ajo t\u00eb aktivizohet plot\u00ebsisht n\u00eb klaster dhe ngriheni t\u00eb tjerat. (M\u00eb shum\u00eb n\u00eb raportin Ceph. Anatomia e katastrof\u00ebs).<\/p>\n

N\u00eb rastin e instalimeve baremetal, kjo b\u00ebhet leht\u00ebsisht manualisht, nd\u00ebrsa n\u00eb rastin e Rook dhe nj\u00eb OSD n\u00eb nod, nuk ka probleme t\u00eb ve\u00e7anta; problemet me ngritjen e radh\u00ebs do t\u00eb ndodhin n\u00ebse OSD > 1 n\u00eb nod. <\/p>\n

Sigurisht, ato jan\u00eb t\u00eb zgjidhshme, por ne po sollim Rook p\u00ebr thjeshtim, nd\u00ebrsa marrim komplike.<\/p>\n

V\u00ebshtir\u00ebsia e p\u00ebrcaktimit t\u00eb limiteve p\u00ebr demon\u00ebt ceph.<\/h3>\n

\nP\u00ebr instalimet baremetal t\u00eb ceph, \u00ebsht\u00eb mjaft e leht\u00eb t\u00eb llogaris\u00ebsh burimet e nevojshme p\u00ebr klasterin \u2014 formula dhe k\u00ebrkime jan\u00eb t\u00eb disponueshme. Duke p\u00ebrdorur CPU t\u00eb dob\u00ebt, do t'ju duhet ende t\u00eb kryeni nj\u00eb s\u00ebr\u00eb testesh t\u00eb performanc\u00ebs, t\u00eb m\u00ebsoni se \u00e7far\u00eb \u00ebsht\u00eb Numa, por gjithsesi kjo \u00ebsht\u00eb m\u00eb e thjesht\u00eb se n\u00eb Rook.<\/p>\n

N\u00eb rastin e Rook, p\u00ebrve\u00e7 limiteve t\u00eb memories q\u00eb mund t\u00eb llogariten, lind edhe pyetja e caktimit t\u00eb limites CPU.<\/p>\n

Dhe k\u00ebtu do t'ju duhet t\u00eb b\u00ebni teste t\u00eb performanc\u00ebs. N\u00eb rastin e zvog\u00eblimit t\u00eb limiteve, do t\u00eb merrni nj\u00eb klaster t\u00eb ngadalsh\u00ebm; n\u00eb rastin e vendosjes s\u00eb unlimit, do t\u00eb keni p\u00ebrdorim aktiv t\u00eb CPU gjat\u00eb ribalancimit, gj\u00eb q\u00eb do t\u00eb ndikoj\u00eb n\u00eb aplikacionet tuaja n\u00eb kubernetes.<\/p>\n

Problemet me nd\u00ebrveprimin rrjet v1.<\/h3>\n

\nP\u00ebr ceph, rekomandohet t\u00eb p\u00ebrdorni nj\u00eb rrjet 2x10gb. Nj\u00eb p\u00ebr trafikun e klient\u00ebve, tjetra p\u00ebr nevoja sh\u00ebrbimi t\u00eb ceph (ribalanc). N\u00ebse jetoni me ceph n\u00eb baremetal, at\u00ebher\u00eb kjo ndarje \u00ebsht\u00eb leht\u00eb e konfigurueshme, n\u00ebse jetoni me Rook, ndarja e rrjeteve do t\u00eb shkaktoj\u00eb probleme, pasi jo \u00e7do konfigurim klasteri lejon q\u00eb t\u2019i jepni pod-it dy rrjete t\u00eb ndryshme.<\/p>\n

Problemet me nd\u00ebrveprimin rrjet v2.<\/h3>\n

\nN\u00ebse refuzoni t\u00eb ndaheni rrjetet, at\u00ebher\u00eb gjat\u00eb ribalancit, trafiku i ceph do t\u00eb mbush\u00eb t\u00eb gjith\u00eb kanalin dhe aplikacionet tuaja n\u00eb kubernetes do t\u00eb ngadal\u00ebsohen ose do t\u00eb bien. Mund t\u00eb ulni shpejt\u00ebsin\u00eb e ribalancit t\u00eb ceph, por at\u00ebher\u00eb p\u00ebr shkak t\u00eb ribalancit t\u00eb gjat\u00eb, rreziku i r\u00ebnies s\u00eb nod\u00ebs s\u00eb dyt\u00eb nga klasteri p\u00ebr shkak t\u00eb disqeve ose OOM do t\u00eb rritet, dhe atje do t\u00eb keni nj\u00eb garancin\u00eb e leximit vet\u00ebm n\u00eb klaster.<\/p>\n

Ribalanc i gjat\u00eb - ngadal\u00ebsim i gjat\u00eb i aplikacioneve.<\/h3>\n

\nCitim nga postimi Ceph. Anatomia e katastrof\u00ebs.<\/i><\/p>\n

Performanca e klasterit testues:<\/p>\n

Operacioni i shkruan me madh\u00ebsi 4 Kbyte merr 1 ms, performanca 1000 operacione\/sekond n\u00eb 1 thread.<\/p>\n

Operacioni me madh\u00ebsi 4 Mbyte (madh\u00ebsia e objektit) merr 22 ms, performanca 45 operacione\/sekond.<\/p>\n

Prandaj, kur nj\u00eb nga tre domenet d\u00ebshton, klasteri ndodhet p\u00ebr nj\u00eb koh\u00eb n\u00eb nj\u00eb gjendje t\u00eb degraduar, dhe gjysma e objekteve t\u00eb nxehta shp\u00ebrndahet n\u00eb versione t\u00eb ndryshme, at\u00ebher\u00eb gjysma e operacioneve t\u00eb shkrimit do t\u00eb fillojn\u00eb me nj\u00eb rikuperim t\u00eb detyruar.<\/p>\n

Koha e rikuperimit t\u00eb detyruar llogaritet p\u00ebr rreth \u2014 operacionet e shkrimit n\u00eb objektin e degraduar.<\/p>\n

S\u00eb pari lexojm\u00eb 4 MB n\u00eb 22 ms, shkruajm\u00eb 22 ms, dhe pastaj 1 ms shkruajm\u00eb 4 KB t\u00eb dh\u00ebnash. N\u00eb total, 45 ms p\u00ebr nj\u00eb operacion shkrimi n\u00eb objektin e degraduar n\u00eb SSD, kur performanca standarde ishte 1 ms \u2014 nj\u00eb r\u00ebnie performance 45 her\u00eb.<\/p>\n

Sa m\u00eb i madh t\u00eb jet\u00eb p\u00ebrqindja e objekteve t\u00eb degraduara, aq m\u00eb e frikshme b\u00ebhet situata.<\/p><\/blockquote>\n

Pra, shpejt\u00ebsia e ribalancimit \u00ebsht\u00eb kritikisht e r\u00ebnd\u00ebsishme p\u00ebr funksionimin e duhur t\u00eb klasterit.<\/p>\n

Konfigurime specifike p\u00ebr server\u00ebt p\u00ebr ceph<\/h3>\n

\nceph shpesh k\u00ebrkon nj\u00eb tuning specifik t\u00eb hostit. <\/p>\n

Shembuj: konfigurimet sysctl dhe JumboFrame, disa nga k\u00ebto konfigurime mund t\u00eb ken\u00eb nj\u00eb ndikim negativ n\u00eb payload-in tuaj.<\/p>\n

K\u00ebrkesa reale p\u00ebr Rook mbetet n\u00ebn pyetje<\/h3>\n

\nN\u00ebse jeni n\u00eb cloud, keni ruajtje nga ofruesi tuaj i cloud-it, q\u00eb \u00ebsht\u00eb shum\u00eb m\u00eb e p\u00ebrshtatshme. <\/p>\n

N\u00ebse jeni n\u00eb server\u00ebt tuaj, menaxhimi i ceph do t\u00eb jet\u00eb m\u00eb i leht\u00eb pa kubernetes. <\/p>\n

A po merrni me qira server\u00eb n\u00eb nj\u00eb hostim me kosto t\u00eb ul\u00ebt? At\u00ebher\u00eb ju presin shum\u00eb telashe me rrjetin, vonesat dhe kapacitetin, q\u00eb ndikon ndjesh\u00ebm n\u00eb ceph.<\/p>\n

Pra, n\u00eb p\u00ebrfundim:<\/b> Zbatimi i kuberentes dhe zbatimi i ruajtjes jan\u00eb detyra t\u00eb ndryshme me k\u00ebrkesa t\u00eb ndryshme dhe mund\u00ebsi t\u00eb ndryshme zgjidhjesh \u2014 t'i p\u00ebrzieni ata do t\u00eb thot\u00eb t\u00eb b\u00ebni nj\u00eb trade-off potencialisht t\u00eb rreziksh\u00ebm n\u00eb favor t\u00eb nj\u00ebri-tjetrit. T\u00eb p\u00ebrputhni k\u00ebto zgjidhje do t\u00eb jet\u00eb shum\u00eb e v\u00ebshtir\u00eb edhe n\u00eb faz\u00ebn e projektimit, dhe ka ende periudha eksperimentimi.<\/p>\n

Lista e letrave t\u00eb p\u00ebrdorura:<\/p>\n

Posti #1<\/a><\/noindex> Po flisni p\u00ebr Ceph\u2026 a \u00ebsht\u00eb v\u00ebrtet kaq i mir\u00eb?
\nPosti #2<\/a><\/noindex> Ceph. Anatomia e katastrof\u00ebs
\n
Burimi: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

\u0412 \u0441\u0432\u044f\u0437\u0438 \u0441 \u043d\u0430\u0431\u0438\u0440\u0430\u044e\u0449\u0435\u0439 \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u043e\u0441\u0442\u044c\u044e Rook \u0445\u043e\u0447\u0435\u0442\u0441\u044f \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u0442\u044c \u043e \u0435\u0433\u043e \u043f\u043e\u0434\u0432\u043e\u0434\u043d\u044b\u0445 \u043a\u0430\u043c\u043d\u044f\u0445 \u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430\u0445, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0436\u0434\u0443\u0442 \u0432\u0430\u0441 \u043d\u0430 \u043f\u0443\u0442\u0438. \u041e \u0441\u0435\u0431\u0435: \u041e\u043f\u044b\u0442 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f ceph \u0441 \u0432\u0435\u0440\u0441\u0438\u0438 hammer, \u043e\u0441\u043d\u043e\u0432\u0430\u0442\u0435\u043b\u044c \u043a\u043e\u043c\u044c\u044e\u043d\u0438\u0442\u0438 t.me\/ceph_ru \u0432 \u0442\u0435\u043b\u0435\u0433\u0440\u0430\u043c. \u0414\u0430\u0431\u044b \u043d\u0435 \u0431\u044b\u0442\u044c \u0433\u043e\u043b\u043e\u0441\u043b\u043e\u0432\u043d\u044b\u043c \u044f \u0431\u0443\u0434\u0443 \u0441\u0441\u044b\u043b\u0430\u0442\u044c\u0441\u044f \u043d\u0430 \u043f\u0440\u0438\u043d\u044f\u0442\u044b\u0435 \u0445\u0430\u0431\u0440\u043e\u043c (\u0441\u0443\u0434\u044f \u043f\u043e \u0440\u0435\u0439\u0442\u0438\u043d\u0433\u0443) \u043f\u043e\u0441\u0442\u044b \u043e \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430\u0445 \u0441 ceph. \u0421 \u0431\u041e\u043b\u044c\u0448\u0435\u0439 \u0447\u0430\u0441\u0442\u044c\u044e \u043f\u0440\u043e\u0431\u043b\u0435\u043c \u0432 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-33803","post","type-post","status-publish","format-standard","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\udd47Ai nuk \u00ebsht\u00eb dRook | ProHoster","description":"Me rritjen n\u00eb popullaritet t\u00eb Rook, d\u00ebshiroj t\u00eb flas p\u00ebr pengesat e tij dhe problemet q\u00eb ju presin n\u00eb rrug\u00eb. P\u00ebr veten: Eksperienc\u00eb n\u00eb administrimin e ceph q\u00eb nga versione hammer, themelues i komunitetit.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/on-vam-ne-drook","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\u041e\u043d \u0432\u0430\u043c \u043d\u0435 \u0434Rook | ProHoster","og:description":"\u0412 \u0441\u0432\u044f\u0437\u0438 \u0441 \u043d\u0430\u0431\u0438\u0440\u0430\u044e\u0449\u0435\u0439 \u043f\u043e\u043f\u0443\u043b\u044f\u0440\u043d\u043e\u0441\u0442\u044c\u044e Rook \u0445\u043e\u0447\u0435\u0442\u0441\u044f \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u0442\u044c \u043e \u0435\u0433\u043e \u043f\u043e\u0434\u0432\u043e\u0434\u043d\u044b\u0445 \u043a\u0430\u043c\u043d\u044f\u0445 \u0438 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0430\u0445, \u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0436\u0434\u0443\u0442 \u0432\u0430\u0441 \u043d\u0430 \u043f\u0443\u0442\u0438. \u041e \u0441\u0435\u0431\u0435: \u041e\u043f\u044b\u0442 \u0430\u0434\u043c\u0438\u043d\u0438\u0441\u0442\u0440\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u044f ceph \u0441 \u0432\u0435\u0440\u0441\u0438\u0438 hammer, \u043e\u0441\u043d\u043e\u0432\u0430\u0442\u0435\u043b\u044c \u043a\u043e\u043c\u044c\u044e\u043d\u0438\u0442\u0438","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/on-vam-ne-drook","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-31T18:54:45+00:00","article:modified_time":"2019-10-31T18:54:45+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"33803","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-21 16:46:22","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:33:24","updated":"2026-01-21 16:46:22","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\/33803","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=33803"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/33803\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=33803"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=33803"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=33803"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}