{"id":80491,"date":"2020-05-06T13:42:24","date_gmt":"2020-05-06T11:42:24","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/obrezaem-niti-perehod-s-puppet-enterprise-na-ansible-tower-chast-1"},"modified":"2020-05-06T13:42:24","modified_gmt":"2020-05-06T11:42:24","slug":"obrezaem-niti-perehod-s-puppet-enterprise-na-ansible-tower-chast-1","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/obrezaem-niti-perehod-s-puppet-enterprise-na-ansible-tower-chast-1","title":{"rendered":"Strih\u00e1me nite: prechod z Puppet Enterprise na Ansible Tower. \u010cas\u0165 1","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>N\u00e1rodn\u00e1 informa\u010dn\u00e1 slu\u017eba satelitn\u00fdch \u00fadajov o \u017eivotnom prostred\u00ed (NESDIS) zn\u00ed\u017eila svoje n\u00e1klady na spr\u00e1vu konfigur\u00e1cie Red Hat Enterprise Linux (RHEL) o 35 % prechodom z Puppet Enterprise na Ansible Tower. V tomto videu s kateg\u00f3riou \u201eako sme to urobili\u201c syst\u00e9mov\u00fd in\u017einier Michael Rau vysvet\u013euje d\u00f4vody tejto migr\u00e1cie, zdie\u013ea u\u017eito\u010dn\u00e9 tipy a sk\u00fasenosti z\u00edskan\u00e9 po\u010das prechodu z jedn\u00e9ho SCM na druh\u00e9. <\/p>\n<p>Z tohto videa sa dozviete:<\/p>\n<ul>\n<li>ako ospravedlni\u0165 vedeniu opr\u00e1vnenos\u0165 prechodu z Puppet Enterprise na Ansible Tower;<\/li>\n<li>ak\u00e9 strat\u00e9gie pou\u017ei\u0165 pre najhlad\u0161\u00ed prechod;<\/li>\n<li>tipy na transcoding PE manifestov do Ansible Playbook;<\/li>\n<li>odpor\u00fa\u010dania pre optim\u00e1lnu in\u0161tal\u00e1ciu Ansible Tower.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"Strih\u00e1me nite: prechod z Puppet Enterprise na Ansible Tower. \u010cas\u0165 1\" src=\"\/wp-content\/uploads\/2020\/05\/6c4ee5db9a9f584cd69109549827b5b2.jpg\" style=\"display:block;margin: 0 auto;\" \/><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>V\u00edtam v\u00e1s v\u0161etk\u00fdch, vol\u00e1m sa Michael Rau, som senior syst\u00e9mov\u00fd in\u017einier spolo\u010dnosti ActioNet, ktor\u00e1 pracuje pre N\u00e1rodn\u00fa spr\u00e1vu oce\u00e1nov a atmosf\u00e9ry (NOAA) slu\u017ebu NESDIS. Dnes budeme hovori\u0165 o strihnut\u00ed riadkov \u2013 o mojich vlastn\u00fdch sk\u00fasenostiach s migr\u00e1ciou z Puppet Enterprise na Ansible Tower. T\u00e9ma tejto prezent\u00e1cie je \u201epozrite sa na moje jazvy\u201c, ktor\u00e9 zostali po tom, \u010do som prechod uskuto\u010dnil na za\u010diatku roka. Chcem v\u00e1m poveda\u0165, \u010do som sa v procese nau\u010dil. Tak\u017ee ke\u010f sa rozhodnete pre nie\u010do podobn\u00e9, m\u00f4\u017eete s mojimi sk\u00fasenos\u0165ami prejs\u0165 bez zbyto\u010dn\u00fdch probl\u00e9mov.<\/p>\n<p>Na za\u010diatku ka\u017edej prezent\u00e1cie na Ansible Fest vid\u00edte slidy podobn\u00e9 tomuto. Tento slid predklad\u00e1 pr\u00edbeh automatiz\u00e1cie mojej spolo\u010dnosti. Nie som nov\u00e1\u010dik v tejto oblasti, preto\u017ee pou\u017e\u00edvam Puppet\/Puppet Enterprise od roku 2007. S Ansible som za\u010dal pracova\u0165 v roku 2016 a m\u0148a, rovnako ako mno\u017estvo \u010fal\u0161\u00edch pou\u017e\u00edvate\u013eov tohto produktu, pri\u0165ahovala mo\u017enos\u0165 \u201etrikov\u201c pomocou pr\u00edkazov\u00e9ho riadka a jednoduch\u00e9 scen\u00e1re (playbooks). Na konci roku 2017 som sa obr\u00e1til na svoje vedenie so z\u00e1va\u017en\u00fdmi d\u00f4vodmi pre prechod na Ansible Tower. O chv\u00ed\u013eu v\u00e1m poviem o d\u00f4vodoch, ktor\u00e9 ma na tento krok podnietili. Po z\u00edskan\u00ed s\u00fahlasu vedenia bolo potrebn\u00e9 e\u0161te nieko\u013eko mesiacov na realiz\u00e1ciu my\u0161lienky a prechod som uskuto\u010dnil v janu\u00e1ri-febru\u00e1ri tohto roka. Tak\u017ee sme sa \u00faplne vzdali Puppetu v prospech Ansible, a to je skvel\u00e9. <\/p>\n<p><img decoding=\"async\" alt=\"Strih\u00e1me nite: prechod z Puppet Enterprise na Ansible Tower. \u010cas\u0165 1\" src=\"\/wp-content\/uploads\/2020\/05\/0e179ef00aa22edae72270e53d9787df.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNajviac ma na Ansible l\u00e1ka mo\u017enos\u0165 p\u00edsa\u0165 a pou\u017e\u00edva\u0165 \u00falohy (roles) a scen\u00e1re (playbooks). \u00dalohy s\u00fa skvel\u00e9 na vytv\u00e1ranie r\u00f4znych, ale navz\u00e1jom prepojen\u00fdch \u00faloh (tasks) a umiestnenie v\u0161etk\u00fdch \u00fadajov t\u00fdkaj\u00facich sa t\u00fdchto \u00faloh na jednom mieste. Playbook je syntax YAML, skriptov\u00fd s\u00fabor, ktor\u00fd popisuje akcie pre jeden alebo viac hostite\u013eov. Tieto mo\u017enosti prezentujem pou\u017e\u00edvate\u013eom, predov\u0161etk\u00fdm v\u00fdvoj\u00e1rom softv\u00e9ru. Ansible Tower umo\u017e\u0148uje poveda\u0165: \"nie, nem\u00e1te pr\u00edstup k shell access, ale pon\u00fakam v\u00e1m mo\u017enos\u0165 spusti\u0165 v\u0161etky procesy Tower a re\u0161tartova\u0165 slu\u017ebu, kedyko\u013evek to budete potrebova\u0165.\" Povieme si o pracovnom prostred\u00ed a pou\u017e\u00edvanom hardv\u00e9ri. <\/p>\n<p><img decoding=\"async\" alt=\"Strih\u00e1me nite: prechod z Puppet Enterprise na Ansible Tower. \u010cas\u0165 1\" src=\"\/wp-content\/uploads\/2020\/05\/1dd8f9d0025660a1f3c17a174681caec.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nToto je feder\u00e1lna LAN, 7 fyzick\u00fdch lokal\u00edt prepojen\u00fdch cez cloudov\u00e9 MPLS, 140 serverov RHEL, z \u010doho 99 % s\u00fa virtu\u00e1lne (vSphere), hardv\u00e9r SuperMicro, sie\u0165ov\u00e9 \u00falo\u017eisko NexentaStore, s\u00faprava prep\u00edna\u010dov Cisco, Arista a Cumulus a prostriedky na unified threat management Fortinet UTM na ka\u017edej lokalite. <\/p>\n<p>Feder\u00e1lna sie\u0165 znamen\u00e1, \u017ee mus\u00edm pou\u017ei\u0165 v\u0161etky prostriedky ochrany inform\u00e1ci\u00ed stanoven\u00e9 legislat\u00edvou. Mus\u00edte ma\u0165 na pam\u00e4ti, \u017ee Puppet Enterprise nepodporuje v\u00e4\u010d\u0161inu n\u00e1\u0161ho pou\u017e\u00edvan\u00e9ho hardv\u00e9ru. Sme n\u00faten\u00ed pou\u017e\u00edva\u0165 rozpo\u010dtov\u00e9 zariadenia, preto\u017ee \u0161t\u00e1tne in\u0161tit\u00facie maj\u00fa probl\u00e9my s financovan\u00edm tejto polo\u017eky. Preto kupujeme hardv\u00e9r triedy SuperMicro a zostavujeme na\u0161e zariadenie z jednotliv\u00fdch \u010dast\u00ed, ktor\u00fdch \u00fadr\u017ebu zaru\u010duj\u00fa vl\u00e1dne zmluvy. Pou\u017e\u00edvame Linux a to je jeden z d\u00f4le\u017eit\u00fdch d\u00f4vodov prechodu na Ansible. <\/p>\n<p>Na\u0161a hist\u00f3ria pr\u00e1ce s Puppet je tak\u00e1.<\/p>\n<p><img decoding=\"async\" alt=\"Strih\u00e1me nite: prechod z Puppet Enterprise na Ansible Tower. \u010cas\u0165 1\" src=\"\/wp-content\/uploads\/2020\/05\/a893499e8bbabf1223461f11d737e777.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nV roku 2007 sme mali mal\u00fa sie\u0165 zlo\u017een\u00fa z 20-25 uzlov, v ktorej sme nasadili Puppet. Tieto uzly boli v\u00e4\u010d\u0161inou len \"krabice\" RedHat. V roku 2010 sme za\u010dali pou\u017e\u00edva\u0165 webov\u00e9 rozhranie Puppet Dashboard pre 45 uzlov. Ke\u010f\u017ee sa sie\u0165 na\u010falej roz\u0161irovala, v roku 2014 sme pre\u0161li na PE 3.3, pri\u010dom sme kompletne prepisovali manifest pre 75 uzlov. Toto bolo potrebn\u00e9, preto\u017ee Puppet r\u00e1d men\u00ed pravidl\u00e1, a v tomto pr\u00edpade \u00faplne zmenili jazyk. O rok nesk\u00f4r, ke\u010f prestala podpora 3. verzie Puppet Enterprise, sme boli n\u00faten\u00ed migrova\u0165 na PE 2015.2. Op\u00e4\u0165 sme museli prepisova\u0165 manifest pre nov\u00e9 servery a zak\u00fapi\u0165 licenciu s nadbytkom na 100 uzlov, hoci v tom \u010dase sme mali len 85 uzlov. <\/p>\n<p>U\u017e uplynuli iba 2 roky a op\u00e4\u0165 sme museli vykona\u0165 v\u00fdznamn\u00fa pr\u00e1cu na prechode na nov\u00fa verziu PE 2016.4. K\u00fapili sme licenciu na 300 uzlov, pri\u010dom sme mali len 130. Op\u00e4\u0165 sme museli robi\u0165 v\u00e1\u017ene \u00fapravy v manifeste, preto\u017ee nov\u00e1 verzia jazyka mala syntaktick\u00e9 rozdiely od jazyka verzie 2015. Nakoniec na\u0161a SCM pre\u0161la zo syst\u00e9mu spr\u00e1vy verzi\u00ed SVN na Bitbucket (Git). Takto sme mali na\u0161e \"vz\u0165ahy\" s Puppet.<\/p>\n<p>A tak som musel vysvetli\u0165 vedeniu, pre\u010do mus\u00edme prejs\u0165 na in\u00fa SCM, pri\u010dom som pou\u017eil nasleduj\u00face argumenty. Prv\u00fd \u2013 vysok\u00e1 cena slu\u017eby. Hovoril som s chalanmi z RedHat a povedali, \u017ee n\u00e1klady na \u00fadr\u017ebu siete z 300 uzlov pomocou Ansible Tower predstavuj\u00fa polovicu ceny Puppet Enterprise. Ak zak\u00fapite aj Ansible Engine, n\u00e1klady bud\u00fa pribli\u017ene rovnak\u00e9, ale z\u00edskate ove\u013ea viac funkci\u00ed, ne\u017e pon\u00faka PE. Ke\u010f\u017ee sme \u0161t\u00e1tna spolo\u010dnos\u0165 financovan\u00e1 z feder\u00e1lneho rozpo\u010dtu, to je celkom siln\u00fd argument. <\/p>\n<p><img decoding=\"async\" alt=\"Strih\u00e1me nite: prechod z Puppet Enterprise na Ansible Tower. \u010cas\u0165 1\" src=\"\/wp-content\/uploads\/2020\/05\/8077b9a470286c795a13de3cd6470ce9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDruh\u00fd argument \u2013 univerz\u00e1lnos\u0165. Puppet podporuje iba to zariadenie, na ktorom je nain\u0161talovan\u00fd agent Puppet. To znamen\u00e1, \u017ee na v\u0161etky prep\u00edna\u010de je potrebn\u00e9 nain\u0161talova\u0165 agenta, pri\u010dom mus\u00ed by\u0165 v najnov\u0161ej verzii. A ak \u010das\u0165 va\u0161ich prep\u00edna\u010dov podporuje jednu verziu a \u010das\u0165 druh\u00fa, budete musie\u0165 nain\u0161talova\u0165 na ne nov\u00fa verziu agenta PE, aby v\u0161etky mohli fungova\u0165 v jednom syst\u00e9me SCM.<\/p>\n<p>Syst\u00e9m Ansible Tower funguje jinak, proto\u017ee nem\u00e1 \u017e\u00e1dn\u00e9 agenty, ale m\u00e1 moduly, kter\u00e9 podporuj\u00ed switche Cisco a v\u0161echny ostatn\u00ed switche. Tato SCM podporuje Qubes OS, Linux a 4.NET UTM. Ansible Tower tak\u00e9 podporuje \u0159adi\u010de s\u00ed\u0165ov\u00fdch \u00falo\u017ei\u0161\u0165 NexentaStore, kter\u00e9 jsou zalo\u017eeny na j\u00e1dru Illumos \u2013 open-source opera\u010dn\u00edm syst\u00e9mu zalo\u017een\u00e9m na Unxu. To je velmi mal\u00e1 podpora, ale Ansible Tower ji p\u0159esto poskytuje. <\/p>\n<p>T\u0159et\u00ed argument, kter\u00fd je pro m\u011b i na\u0161i administraci velmi d\u016fle\u017eit\u00fd, je snadnost ovl\u00e1d\u00e1n\u00ed. B\u011bhem 10 let jsem se ovl\u00e1dal moduly a k\u00f3dy manifest\u016f Puppet, ale Ansible jsem se nau\u010dil b\u011bhem t\u00fddne, proto\u017ee s touto SCM je mnohem snaz\u0161\u00ed pracovat. Pokud spou\u0161t\u00edte spustiteln\u00e9 soubory, samoz\u0159ejm\u011b pokud to ned\u011bl\u00e1te zbyte\u010dn\u011b, pak s nimi pracuj\u00ed rozumn\u00ed a citliv\u00ed zpracovatel\u00e9. Playbooky zalo\u017een\u00e9 na YAML se vyzna\u010duj\u00ed snadn\u00fdm u\u010den\u00edm a rychl\u00fdm pou\u017eit\u00edm. Ti, kte\u0159\u00ed o YAML nikdy nesly\u0161eli, si mohou jednodu\u0161e p\u0159e\u010d\u00edst skripty a snadno pochopit, jak to funguje. <\/p>\n<p>Up\u0159\u00edmn\u011b \u0159e\u010deno, Puppet zna\u010dn\u011b komplikuje va\u0161i pr\u00e1ci jako v\u00fdvoj\u00e1\u0159e, proto\u017ee je zalo\u017een na pou\u017eit\u00ed Puppet Master. To je jedin\u00fd stroj, kter\u00fd m\u00e1 pr\u00e1vo komunikovat s agenty Puppet. Pokud jste provedli n\u011bjak\u00e9 zm\u011bny v manifestu a chcete testovat sv\u016fj k\u00f3d, mus\u00edte p\u0159epsat k\u00f3d pro Puppet Master, to znamen\u00e1 nastavit soubor Puppet masteru \/etc\/hosts pro p\u0159ipojen\u00ed v\u0161ech klient\u016f a spustit slu\u017ebu Puppet Server. Teprve pot\u00e9 m\u016f\u017eete testovat funkci s\u00ed\u0165ov\u00e9ho za\u0159\u00edzen\u00ed na jednom hostiteli. To je dost bolestiv\u00fd proces. <br \/>\nV Ansible je v\u0161e mnohem jednodu\u0161\u0161\u00ed. V\u0161e, co mus\u00edte ud\u011blat, je vyvinout k\u00f3d pro stroj, kter\u00fd m\u00e1 mo\u017enost komunikovat pomoc\u00ed protokolu SSH s testovan\u00fdm hostitelem. S t\u00edmto je mnohem snaz\u0161\u00ed pracovat.<\/p>\n<p>Dal\u0161\u00ed velkou v\u00fdhodou Ansible Tower je mo\u017enost vyu\u017e\u00edt ji\u017e existuj\u00edc\u00ed podp\u016frn\u00fd syst\u00e9m a zachovat st\u00e1vaj\u00edc\u00ed konfiguraci za\u0159\u00edzen\u00ed. Tato SCM bez jakoukoli dal\u0161\u00ed akce pou\u017e\u00edv\u00e1 v\u0161echny dostupn\u00e9 informace o va\u0161\u00ed infrastruktu\u0159e a za\u0159\u00edzen\u00ed, virtu\u00e1ln\u00edch stroj\u00edch, serverech atd. M\u016f\u017ee komunikovat s va\u0161imi RH Satellite servery, pokud n\u011bjak\u00e9 m\u00e1te, a poskytuje v\u00e1m takovou integraci, kterou nikdy nez\u00edsk\u00e1te p\u0159i pr\u00e1ci s Puppet.<\/p>\n<p>\u010eal\u0161ou d\u00f4le\u017eitou vecou je podrobn\u00e1 kontrola. Viete, \u017ee Puppet je modul\u00e1rny syst\u00e9m, je to klient-server aplik\u00e1cia, preto mus\u00edte definova\u0165 existuj\u00face aspekty fungovania v\u0161etk\u00fdch va\u0161ich strojov v jednom dlhom manifeste. Pri tom by sa stav ka\u017ed\u00e9ho jednotliv\u00e9ho prvku syst\u00e9mu mal testova\u0165 ka\u017ed\u00fdch polhodinu \u2013 to je predvolen\u00fd interval. Takto Puppet funguje.<\/p>\n<p>Tower v\u00e1s zbavuje tohto. M\u00f4\u017eete bez obmedzen\u00ed vykon\u00e1va\u0165 najr\u00f4znej\u0161ie procesy na r\u00f4znom hardv\u00e9ri, m\u00f4\u017eete robi\u0165 z\u00e1kladn\u00fa pr\u00e1cu, sp\u00fa\u0161\u0165at \u010fal\u0161ie d\u00f4le\u017eit\u00e9 procesy, nastavova\u0165 syst\u00e9mov\u00fa bezpe\u010dnos\u0165, pracova\u0165 s datab\u00e1zami. M\u00f4\u017eete robi\u0165 v\u0161etko, \u010do je v Puppet Enterprise spojen\u00e9 s ur\u010dit\u00fdmi \u0165a\u017ekos\u0165ami. Tak\u017ee ak ste vykonali nastavenie na jednom hoste, bude trva\u0165 nejak\u00fd \u010das, k\u00fdm sa zmeny prejavia na ostatn\u00fdch hostoch. V Ansible sa v\u0161etky zmeny prejavia okam\u017eite.<\/p>\n<p>Nakoniec sa pozrime na bezpe\u010dnostn\u00fd modul. V Ansible Tower je realizovan\u00fd jednoducho \u00fa\u017easne, s ve\u013ekou presnos\u0165ou a d\u00f4vtipom. M\u00f4\u017eete poskytova\u0165 u\u017e\u00edvate\u013eom pr\u00edstup k konkr\u00e9tnym slu\u017eb\u00e1m alebo k konkr\u00e9tnym hostom. Rob\u00edm to so svojimi zamestnancami, ktor\u00ed s\u00fa zvyknut\u00ed pracova\u0165 na Windows, obmedzujem ich pr\u00edstup k shellu Linux. Zais\u0165ujem im tak\u00fd pr\u00edstup k Tower, aby mohli vykon\u00e1va\u0165 iba t\u00fa pr\u00e1cu a sp\u00fa\u0161\u0165a\u0165 iba tie slu\u017eby, ktor\u00e9 sa t\u00fdkaj\u00fa ich kompetencie.<\/p>\n<p><img decoding=\"async\" alt=\"Strih\u00e1me nite: prechod z Puppet Enterprise na Ansible Tower. \u010cas\u0165 1\" src=\"\/wp-content\/uploads\/2020\/05\/f3bd3b26cf20225b6e1800e09dbcfe43.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPozrime sa na veci, ktor\u00e9 je potrebn\u00e9 urobi\u0165 vopred, aby ste u\u013eah\u010dili prechod na Ansible Tower. V prvom rade je potrebn\u00e9 pripravi\u0165 va\u0161e zariadenia. Ak niektor\u00e9 prvky va\u0161ej infra\u0161trukt\u00fary e\u0161te nie s\u00fa v datab\u00e1ze, je potrebn\u00e9 ich tam prida\u0165. Existuj\u00fa syst\u00e9my, ktor\u00e9 nemenia svoje charakteristiky a preto ch\u00fdbaj\u00fa v datab\u00e1ze Puppet, ale ak ich tam pred prechodom na Tower neprid\u00e1te, pr\u00eddete o mno\u017estvo v\u00fdhod. M\u00f4\u017ee to by\u0165 \u201e\u0161pinav\u00e1\u201c, predbe\u017en\u00e1 datab\u00e1za, ale mala by obsahova\u0165 inform\u00e1cie o v\u0161etkom zariaden\u00ed, ktor\u00e9 m\u00e1te. Preto by ste mali nap\u00edsa\u0165 dynamick\u00fd skript zariadenia, ktor\u00fd automaticky zanesie v\u0161etky zmeny infra\u0161trukt\u00fary do datab\u00e1zy, aby Ansible vedel, ak\u00e9 hosty by mali by\u0165 v novom syst\u00e9me. Nebudete musie\u0165 tejto SCM hl\u00e1si\u0165, ak\u00e9 hosty ste pridali a ktor\u00e9 hosty u\u017e neexistuj\u00fa, preto\u017ee to v\u0161etko zist\u00ed automaticky. \u010c\u00edm viac \u00fadajov bude v datab\u00e1ze, t\u00fdm u\u017eito\u010dnej\u0161\u00ed a flexibilnej\u0161\u00ed bude Ansible. Funguje to tak, akoby jednoducho \u010d\u00edtal z datab\u00e1zy \u010diarov\u00fd k\u00f3d stavu zariadenia.<\/p>\n<p>Str\u00e1vte nejak\u00fd \u010das obozn\u00e1men\u00edm sa s pr\u00e1cou pr\u00edkazov\u00e9ho riadku v Ansible. Spustite niektor\u00e9 \u0161peci\u00e1lne pr\u00edkazy, aby ste overili pr\u00e1cu skriptu zariadenia, nap\u00ed\u0161te a spustite niektor\u00e9 jednoduch\u00e9, ale u\u017eito\u010dn\u00e9 scen\u00e1re playbook, pou\u017eite \u0161abl\u00f3ny Jinja2 tam, kde je to vhodn\u00e9. Sk\u00faste nap\u00edsa\u0165 rolu a scen\u00e1r pre komplexn\u00fd viacstup\u0148ov\u00fd proces, pou\u017e\u00edvaj\u00fac \u0161tandardn\u00fa, \u010dasto sa vyskytuj\u00facu konfigur\u00e1ciu zariadenia. Hrajte sa s t\u00fdmito vecami, otestujte, ako to funguje. T\u00fdmto sp\u00f4sobom sa nau\u010d\u00edte pracova\u0165 s n\u00e1strojmi na vytv\u00e1ranie kni\u017en\u00edc pou\u017e\u00edvan\u00fdch v Tower. U\u017e som spomenul, \u017ee moje pr\u00edpravy na prechod trvali pribli\u017ene 3 mesiace. Mysl\u00edm, \u017ee sa v\u00e1m na z\u00e1klade mojej sk\u00fasenosti podar\u00ed urobi\u0165 to r\u00fdchlej\u0161ie. Nepova\u017eujte tento \u010das za straten\u00fd, preto\u017ee nesk\u00f4r poc\u00edtite v\u0161etky v\u00fdhody vykonanej pr\u00e1ce. <\/p>\n<p>\u010ealej je potrebn\u00e9 rozhodn\u00fa\u0165, \u010do o\u010dak\u00e1vate od Ansible Tower, \u010do konkr\u00e9tne by tento syst\u00e9m mal pre v\u00e1s urobi\u0165. <\/p>\n<p><img decoding=\"async\" alt=\"Strih\u00e1me nite: prechod z Puppet Enterprise na Ansible Tower. \u010cas\u0165 1\" src=\"\/wp-content\/uploads\/2020\/05\/4511b3f34d57e489be1103c3b77fc98f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPotrebujete nasadi\u0165 syst\u00e9m na pr\u00e1zdnom hardv\u00e9ri alebo na pr\u00e1zdnych virtu\u00e1lnych strojoch? Alebo chcete zachova\u0165 p\u00f4vodn\u00e9 podmienky a nastavenia existuj\u00faceho hardv\u00e9ru? Toto je ve\u013emi d\u00f4le\u017eit\u00fd aspekt pre fungovanie \u0161t\u00e1tnych spolo\u010dnost\u00ed, preto mus\u00edte ma\u0165 istotu, \u017ee sa v\u00e1m podar\u00ed migrova\u0165 a nasadi\u0165 Ansible na existuj\u00facej konfigur\u00e1cii. Ur\u010dte rutinn\u00e9 administrat\u00edvne procesy, ktor\u00e9 chcete automatizova\u0165. Zistite, \u010di potrebujete nasadi\u0165 \u0161pecifick\u00e9 aplik\u00e1cie a slu\u017eby na novej s\u00fastave. Zostavte zoznam toho, \u010do chcete urobi\u0165, a usporiadajte priority. <\/p>\n<p>Potom prejdite k p\u00edsaniu k\u00f3du skriptov a rol\u00ed, ktor\u00e9 zabezpe\u010dia vykonanie va\u0161ich napl\u00e1novan\u00fdch \u00faloh. Spojte ich do projektov, logickej zbierky s\u00favisiacich skriptov playbookov. Ka\u017ed\u00fd projekt bude patri\u0165 k samostatn\u00e9mu repozit\u00e1ru Git alebo in\u00e9mu repozit\u00e1ru v z\u00e1vislosti od toho, ak\u00e9ho spr\u00e1vcu k\u00f3du pou\u017e\u00edvate. M\u00f4\u017eete spravova\u0165 skripty playbook a adres\u00e1re playbooku tak, \u017ee ich ru\u010dne umiestnite do Project Base Path na servery Tower, alebo umiestnite playbook do ak\u00e9hoko\u013evek syst\u00e9mu spr\u00e1vy zdrojov\u00e9ho k\u00f3du (SCM), ktor\u00fd Tower podporuje, vr\u00e1tane Git, Subversion, Mercurial a Red Hat Insights. V r\u00e1mci jedn\u00e9ho projektu m\u00f4\u017eete ma\u0165 to\u013eko skriptov, ko\u013eko chcete. Napr\u00edklad, vytvoril som jeden z\u00e1kladn\u00fd projekt, v ktorom som umiestnil skript pre z\u00e1kladn\u00e9 prvky RedHat, skript pre z\u00e1klady Linuxu, skripty pre ostatn\u00e9 z\u00e1kladn\u00e9 ukazovatele. Tak\u017ee v jednom projekte existovali r\u00f4zne \u00falohy a skripty, ktor\u00e9 sa spravovali z jedn\u00e9ho Git-repozit\u00e1ra. <\/p>\n<p>Sp\u00fa\u0161\u0165ajte v\u0161etky tieto veci cez pr\u00edkazov\u00fd riadok, je to dobr\u00fd sp\u00f4sob, ako overi\u0165 ich funk\u010dnos\u0165. T\u00fdmto sp\u00f4sobom sa priprav\u00edte na in\u0161tal\u00e1ciu Tower.<\/p>\n<p>Po\u010fme sa trochu porozpr\u00e1va\u0165 o transcodingu manifestu Puppet, preto\u017ee som tomuto venoval ve\u013ea \u010dasu, k\u00fdm som si neuvedomil, \u010do je skuto\u010dne potrebn\u00e9 urobi\u0165. <\/p>\n<p><img decoding=\"async\" alt=\"Strih\u00e1me nite: prechod z Puppet Enterprise na Ansible Tower. \u010cas\u0165 1\" src=\"\/wp-content\/uploads\/2020\/05\/abbc9ffb10b623dc29bcd975dca3bb80.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAko som u\u017e spomenul, Puppet uchov\u00e1va v\u0161etky nastavenia a parametre zariaden\u00ed v jednom dlhom manifeste, a v tomto manifeste s\u00fa zhrnut\u00e9 v\u0161etky \u00falohy, ktor\u00e9 m\u00e1 t\u00e1to SCM vykon\u00e1va\u0165. Pri migr\u00e1cii nie je potrebn\u00e9 napch\u00e1va\u0165 v\u0161etky va\u0161e \u00falohy do jedn\u00e9ho zoznamu, sk\u00f4r prem\u00fd\u0161\u013eajte o \u0161trukt\u00fare nov\u00e9ho syst\u00e9mu: rol\u00e1ch, scen\u00e1roch, zna\u010dk\u00e1ch, skupin\u00e1ch a tom, \u010do by tam malo by\u0165 zahrnut\u00e9. Niektor\u00e9 z nez\u00e1visl\u00fdch prvkov siete by sa mali zl\u00fa\u010di\u0165 do skup\u00edn, pre ktor\u00e9 je mo\u017en\u00e9 vytvori\u0165 scen\u00e1re. Zlo\u017eitej\u0161ie prvky infra\u0161trukt\u00fary, ktor\u00e9 vy\u017eaduj\u00fa zna\u010dn\u00e9 mno\u017estvo zdrojov, ako s\u00fa samostatn\u00e9 triedy, je mo\u017en\u00e9 zl\u00fa\u010di\u0165 do rol\u00ed. Pred migr\u00e1ciou je potrebn\u00e9 to vyjasni\u0165. Ak vytv\u00e1rate rozsiahle rol\u00ed alebo scen\u00e1rov, ktor\u00e9 sa nezmestia na jednu obrazovku, mali by ste pou\u017e\u00edva\u0165 zna\u010dky, aby ste mohli zachyti\u0165 jednotliv\u00e9 \u010dasti infra\u0161trukt\u00fary. <\/p>\n<p>18:00<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ua-hosting\/blog\/500588\/\"> Strihanie l\u00e1n: migr\u00e1cia z Puppet Enterprise na Ansible Tower. \u010cas\u0165 2 <\/a><\/noindex><\/p>\n<h3>Trochu reklamy \ud83d\ude42<\/h3>\n<p>\n\u010eakujeme, \u017ee ost\u00e1vate s nami. P\u00e1\u010dia sa v\u00e1m na\u0161e \u010dl\u00e1nky? Chcete vidie\u0165 viac zauj\u00edmav\u00fdch materi\u00e1lov? Podporte n\u00e1s, vytvoren\u00edm objedn\u00e1vky alebo odpor\u00fa\u010dan\u00edm zn\u00e1mym, <noindex><a rel=\"nofollow\" href=\"https:\/\/ua-hosting.company\/cloudvps\/nl\">cloud VPS pre v\u00fdvoj\u00e1rov od 4,99 dol\u00e1rov<\/a><\/noindex>, <b>unik\u00e1tny ekvivalent entry-level serverov, ktor\u00fd sme pre v\u00e1s vytvorili:<\/b> <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/ua-hosting\/blog\/347386\/\">Cel\u00e1 pravda o VPS (KVM) E5-2697 v3 (6 jadier) 10GB DDR4 480GB SSD 1Gbps od 19 dol\u00e1rov alebo ako spr\u00e1vne rozdeli\u0165 server?<\/a><\/noindex> (k dispoz\u00edcii varianty s RAID1 a RAID10, a\u017e 24 jadier a a\u017e 40GB DDR4).<\/p>\n<p><b>Dell R730xd je dvakr\u00e1t lacnej\u0161\u00ed v d\u00e1tovom centre Equinix Tier IV v Amsterdame?<\/b> Len u n\u00e1s <b><noindex><a rel=\"nofollow\" href=\"https:\/\/ua-hosting.company\/serversnl\">2 x Intel TetraDeca-Core Xeon 2x E5-2697v3 2.6GHz 14C 64GB DDR4 4x960GB SSD 1Gbps 100 TB od 199 dol\u00e1rov<\/a><\/noindex> v Holandsku! <b>Dell R420 \u2014 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 od 99 dol\u00e1rov!<\/b><\/b> Pre\u010d\u00edtajte si o tom <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/ua-hosting\/blog\/329618\/\">Ako vybudova\u0165 infra\u0161trukt\u00faru korpor\u00e1tneho typu s pou\u017eit\u00edm serverov Dell R730xd E5-2650 v4 s cenou 9000 eur za zlomok ceny?<\/a><\/noindex><br \/>\n<br \/>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ua-hosting\/blog\/500400\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041d\u0430\u0446\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u0430\u044f \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u043e\u043d\u043d\u0430\u044f \u0441\u043b\u0443\u0436\u0431\u0430 \u0441\u043f\u0443\u0442\u043d\u0438\u043a\u043e\u0432\u044b\u0445 \u0434\u0430\u043d\u043d\u044b\u0445 \u043e\u0431 \u043e\u043a\u0440\u0443\u0436\u0430\u044e\u0449\u0435\u0439 \u0441\u0440\u0435\u0434\u0435 (NESDIS) \u043d\u0430 35% \u0441\u043d\u0438\u0437\u0438\u043b\u0430 \u0441\u0432\u043e\u0438 \u0437\u0430\u0442\u0440\u0430\u0442\u044b \u043d\u0430 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0435\u0439 Red Hat Enterprise Linux (RHEL), \u043f\u0435\u0440\u0435\u0439\u0434\u044f \u0441 Puppet Enterprise \u043d\u0430 Ansible Tower. \u0412 \u044d\u0442\u043e\u043c \u0432\u0438\u0434\u0435\u043e \u043a\u0430\u0442\u0435\u0433\u043e\u0440\u0438\u0438 \u00ab\u043a\u0430\u043a \u043c\u044b \u044d\u0442\u043e \u0441\u0434\u0435\u043b\u0430\u043b\u0438\u00bb \u0441\u0438\u0441\u0442\u0435\u043c\u043d\u044b\u0439 \u0438\u043d\u0436\u0435\u043d\u0435\u0440 \u041c\u0430\u0439\u043a\u043b \u0420\u0430\u0443 \u043e\u0431\u043e\u0441\u043d\u043e\u0432\u044b\u0432\u0430\u0435\u0442 \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u0435 \u044d\u0442\u043e\u0439 \u043c\u0438\u0433\u0440\u0430\u0446\u0438\u0438, \u0434\u0435\u043b\u0438\u0442\u0441\u044f \u043f\u043e\u043b\u0435\u0437\u043d\u044b\u043c\u0438 \u0441\u043e\u0432\u0435\u0442\u0430\u043c\u0438 \u0438 \u043e\u043f\u044b\u0442\u043e\u043c, \u043f\u043e\u043b\u0443\u0447\u0435\u043d\u043d\u044b\u043c \u0432 \u0440\u0435\u0437\u0443\u043b\u044c\u0442\u0430\u0442\u0435 \u043f\u0435\u0440\u0435\u0445\u043e\u0434\u0430 \u0441 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":80492,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-80491","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.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041d\u0430\u0446\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u0430\u044f \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u043e\u043d\u043d\u0430\u044f \u0441\u043b\u0443\u0436\u0431\u0430 \u0441\u043f\u0443\u0442\u043d\u0438\u043a\u043e\u0432\u044b\u0445 \u0434\u0430\u043d\u043d\u044b\u0445 \u043e\u0431 \u043e\u043a\u0440\u0443\u0436\u0430\u044e\u0449\u0435\u0439 \u0441\u0440\u0435\u0434\u0435 (NESDIS) \u043d\u0430 35% \u0441\u043d\u0438\u0437\u0438\u043b\u0430 \u0441\u0432\u043e\u0438 \u0437\u0430\u0442\u0440\u0430\u0442\u044b \u043d\u0430 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0435\u0439 Red Hat Enterprise Linux (RHEL), \u043f\u0435\u0440\u0435\u0439\u0434\u044f \u0441 Puppet Enterprise \u043d\u0430 Ansible Tower.\" \/>\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\/sk\/blog\/administrirovanie\/obrezaem-niti-perehod-s-puppet-enterprise-na-ansible-tower-chast-1\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\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\u041e\u0431\u0440\u0435\u0437\u0430\u0435\u043c \u043d\u0438\u0442\u0438: \u043f\u0435\u0440\u0435\u0445\u043e\u0434 \u0441 Puppet Enterprise \u043d\u0430 Ansible Tower. \u0427\u0430\u0441\u0442\u044c 1 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041d\u0430\u0446\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u0430\u044f \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u043e\u043d\u043d\u0430\u044f \u0441\u043b\u0443\u0436\u0431\u0430 \u0441\u043f\u0443\u0442\u043d\u0438\u043a\u043e\u0432\u044b\u0445 \u0434\u0430\u043d\u043d\u044b\u0445 \u043e\u0431 \u043e\u043a\u0440\u0443\u0436\u0430\u044e\u0449\u0435\u0439 \u0441\u0440\u0435\u0434\u0435 (NESDIS) \u043d\u0430 35% \u0441\u043d\u0438\u0437\u0438\u043b\u0430 \u0441\u0432\u043e\u0438 \u0437\u0430\u0442\u0440\u0430\u0442\u044b \u043d\u0430 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0435\u0439 Red Hat Enterprise Linux (RHEL), \u043f\u0435\u0440\u0435\u0439\u0434\u044f \u0441 Puppet Enterprise \u043d\u0430 Ansible Tower.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/obrezaem-niti-perehod-s-puppet-enterprise-na-ansible-tower-chast-1\" \/>\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-05-06T11:42:24+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-05-06T11:42:24+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\udd47Strihanie l\u00e1n: migr\u00e1cia z Puppet Enterprise na Ansible Tower. \u010cas\u0165 1 | ProHoster","description":"N\u00e1rodn\u00e1 informa\u010dn\u00e1 slu\u017eba satelitn\u00fdch \u00fadajov o \u017eivotnom prostred\u00ed (NESDIS) zn\u00ed\u017eila svoje n\u00e1klady na spr\u00e1vu konfigur\u00e1cie Red Hat Enterprise Linux (RHEL) o 35 % prechodom z Puppet Enterprise na Ansible Tower.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/obrezaem-niti-perehod-s-puppet-enterprise-na-ansible-tower-chast-1","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","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\u0431\u0440\u0435\u0437\u0430\u0435\u043c \u043d\u0438\u0442\u0438: \u043f\u0435\u0440\u0435\u0445\u043e\u0434 \u0441 Puppet Enterprise \u043d\u0430 Ansible Tower. \u0427\u0430\u0441\u0442\u044c 1 | ProHoster","og:description":"\u041d\u0430\u0446\u0438\u043e\u043d\u0430\u043b\u044c\u043d\u0430\u044f \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u043e\u043d\u043d\u0430\u044f \u0441\u043b\u0443\u0436\u0431\u0430 \u0441\u043f\u0443\u0442\u043d\u0438\u043a\u043e\u0432\u044b\u0445 \u0434\u0430\u043d\u043d\u044b\u0445 \u043e\u0431 \u043e\u043a\u0440\u0443\u0436\u0430\u044e\u0449\u0435\u0439 \u0441\u0440\u0435\u0434\u0435 (NESDIS) \u043d\u0430 35% \u0441\u043d\u0438\u0437\u0438\u043b\u0430 \u0441\u0432\u043e\u0438 \u0437\u0430\u0442\u0440\u0430\u0442\u044b \u043d\u0430 \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u0435 \u043a\u043e\u043d\u0444\u0438\u0433\u0443\u0440\u0430\u0446\u0438\u0435\u0439 Red Hat Enterprise Linux (RHEL), \u043f\u0435\u0440\u0435\u0439\u0434\u044f \u0441 Puppet Enterprise \u043d\u0430 Ansible Tower.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/obrezaem-niti-perehod-s-puppet-enterprise-na-ansible-tower-chast-1","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-05-06T11:42:24+00:00","article:modified_time":"2020-05-06T11:42:24+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"80491","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 16:17:31","updated":"2022-09-28 07:21:37","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/80491","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=80491"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/80491\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media\/80492"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=80491"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=80491"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=80491"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}