{"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\/cs\/blog\/administrirovanie\/obrezaem-niti-perehod-s-puppet-enterprise-na-ansible-tower-chast-1","title":{"rendered":"St\u0159ih\u00e1n\u00ed nit\u00ed: p\u0159echod z Puppet Enterprise na Ansible Tower. \u010c\u00e1st 1","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>N\u00e1rodn\u00ed informa\u010dn\u00ed slu\u017eba satelitn\u00edch dat o \u017eivotn\u00edm prost\u0159ed\u00ed (NESDIS) sn\u00ed\u017eila n\u00e1klady na spr\u00e1vu konfigurace Red Hat Enterprise Linux (RHEL) o 35 % p\u0159echodem z Puppet Enterprise na Ansible Tower. V tomto videu kategorie \u201ejak jsme to ud\u011blali\u201c syst\u00e9mov\u00fd in\u017een\u00fdr Michael Rau zd\u016fvod\u0148uje realizaci t\u00e9to migrace, sd\u00edl\u00ed u\u017eite\u010dn\u00e9 tipy a zku\u0161enosti z\u00edskan\u00e9 z p\u0159echodu z jednoho SCM na druh\u00e9. <\/p>\n<p>Z tohoto videa se dozv\u00edte:<\/p>\n<ul>\n<li>jak zd\u016fvodnit veden\u00ed rozumnost p\u0159echodu z Puppet Enterprise na Ansible Tower;<\/li>\n<li>jak\u00e9 strategie pou\u017e\u00edt pro co nejhlad\u0161\u00ed p\u0159echod;<\/li>\n<li>tipy na transcoding PE manifest\u016f do Ansible Playbook;<\/li>\n<li>doporu\u010den\u00ed pro optim\u00e1ln\u00ed instalaci Ansible Tower.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"St\u0159ih\u00e1n\u00ed nit\u00ed: p\u0159echod z Puppet Enterprise na Ansible Tower. \u010c\u00e1st 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>Dobr\u00fd den v\u0161em, jmenuji se Michael Rau, jsem senior syst\u00e9mov\u00fd in\u017een\u00fdr ve spole\u010dnosti ActioNet, kter\u00e1 pracuje pro N\u00e1rodn\u00ed \u00fa\u0159ad pro oce\u00e1n a atmosf\u00e9ru (NOAA) slu\u017ebu NESDIS. Dnes si pov\u00edme o st\u0159ih\u00e1n\u00ed \u0159et\u011bzc\u016f \u2013 o m\u00e9 vlastn\u00ed zku\u0161enosti s migrac\u00ed z Puppet Enterprise na Ansible Tower. T\u00e9ma t\u00e9to prezentace spo\u010d\u00edv\u00e1 v tom, abych \u201ep\u0159edstavil sv\u00e9 jizvy\u201c, kter\u00e9 z\u016fstaly po m\u00e9m p\u0159echodu na za\u010d\u00e1tku roku. Chci sd\u00edlet, co jsem se b\u011bhem tohoto procesu nau\u010dil. Tak\u017ee kdy\u017e se do n\u011b\u010deho podobn\u00e9ho pust\u00edte, budete moci p\u0159echod prov\u00e9st bez zbyte\u010dn\u00fdch obt\u00ed\u017e\u00ed.<\/p>\n<p>Na za\u010d\u00e1tku ka\u017ed\u00e9 prezentace na Ansible Fest vid\u00edte sn\u00edmky podobn\u00e9 tomuto. Tento sn\u00edmek popisuje historii automatizace m\u00e9 firmy. Nejsem v tom nov\u00e1\u010dek, proto\u017ee pou\u017e\u00edv\u00e1m Puppet\/Puppet Enterprise od roku 2007. S Ansible jsem za\u010dal pracovat v roce 2016 a stejn\u011b jako mnoho dal\u0161\u00edch u\u017eivatel\u016f tohoto produktu m\u011b p\u0159il\u00e1kala mo\u017enost \u201etrik\u016f\u201c s pomoc\u00ed p\u0159\u00edkazov\u00e9ho \u0159\u00e1dku a jednoduch\u00e9 skripty (playbooks). Na konci roku 2017 jsem se obr\u00e1til na sv\u00e9 veden\u00ed s v\u00e1\u017en\u00fdmi d\u016fvody pro p\u0159echod na Ansible Tower. Za chv\u00edli v\u00e1m \u0159eknu d\u016fvody, kter\u00e9 m\u011b k tomuto kroku vedly. Po z\u00edsk\u00e1n\u00ed souhlasu veden\u00ed trvalo je\u0161t\u011b n\u011bkolik m\u011bs\u00edc\u016f, ne\u017e jsem realizoval to, co jsem zam\u00fd\u0161lel, a p\u0159echod se uskute\u010dnil v lednu a\u017e \u00fanoru tohoto roku. Tak\u017ee jsme se zcela vzdali Puppet ve prosp\u011bch Ansible, a to je skv\u011bl\u00e9. <\/p>\n<p><img decoding=\"async\" alt=\"St\u0159ih\u00e1n\u00ed nit\u00ed: p\u0159echod z Puppet Enterprise na Ansible Tower. \u010c\u00e1st 1\" src=\"\/wp-content\/uploads\/2020\/05\/0e179ef00aa22edae72270e53d9787df.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNejv\u00edce m\u011b na Ansible p\u0159itahuje mo\u017enost psan\u00ed a pou\u017e\u00edv\u00e1n\u00ed rol\u00ed (roles) a sc\u00e9n\u00e1\u0159\u016f (playbooks). Role jsou skv\u011bl\u00e9 pro vytv\u00e1\u0159en\u00ed r\u016fzn\u00fdch, av\u0161ak vz\u00e1jemn\u011b souvisej\u00edc\u00edch \u00fakol\u016f (tasks) a um\u00edst\u011bn\u00ed v\u0161ech dat vztahuj\u00edc\u00edch se k t\u011bmto \u00fakol\u016fm na jedno m\u00edsto. Playbook je syntaktick\u00fd YAML, skriptov\u00fd soubor, kter\u00fd popisuje akce pro jeden nebo v\u00edce hostitel\u016f. T\u011bmto mo\u017enostem obvykle vysv\u011btluji v\u00fdvoj\u00e1\u0159\u016fm softwaru. Ansible Tower umo\u017e\u0148uje \u0159\u00edci: \u201eNe, nem\u00e1te p\u0159\u00edstup k shellu, ale d\u00e1v\u00e1m v\u00e1m mo\u017enost spustit v\u0161echny procesy Tower a restartovat slu\u017ebu, kdykoli pot\u0159ebujete.\u201c Pov\u00edm v\u00e1m o pracovn\u00edm prost\u0159ed\u00ed a pou\u017e\u00edvan\u00e9m vybaven\u00ed. <\/p>\n<p><img decoding=\"async\" alt=\"St\u0159ih\u00e1n\u00ed nit\u00ed: p\u0159echod z Puppet Enterprise na Ansible Tower. \u010c\u00e1st 1\" src=\"\/wp-content\/uploads\/2020\/05\/1dd8f9d0025660a1f3c17a174681caec.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nJedn\u00e1 se o feder\u00e1ln\u00ed LAN, 7 fyzick\u00fdch lokalit p\u0159ipojen\u00fdch p\u0159es cloudov\u00e9 MPLS, 140 server\u016f RHEL, p\u0159i\u010dem\u017e 99 % z nich je virtu\u00e1ln\u00edch (vSphere), hardware SuperMicro, s\u00ed\u0165ov\u00e9 \u00falo\u017ei\u0161t\u011b NexentaStore, soubor p\u0159ep\u00edna\u010d\u016f Cisco, Arista a Cumulus a prost\u0159edky pro jednotnou spr\u00e1vu hrozeb Fortinet UTM na ka\u017ed\u00e9 lokalit\u011b. <\/p>\n<p>Feder\u00e1ln\u00ed s\u00ed\u0165 znamen\u00e1, \u017ee mus\u00edm pou\u017e\u00edvat v\u0161echny bezpe\u010dnostn\u00ed prost\u0159edky po\u017eadovan\u00e9 z\u00e1kony. M\u011bli byste m\u00edt na pam\u011bti, \u017ee Puppet Enterprise nepodporuje v\u011bt\u0161inu n\u00e1mi pou\u017e\u00edvan\u00e9ho vybaven\u00ed. Jsme nuceni pou\u017e\u00edvat levn\u00e9 hardwarov\u00e9 komponenty, proto\u017ee st\u00e1tn\u00ed instituce \u010del\u00ed probl\u00e9m\u016fm s financov\u00e1n\u00edm t\u00e9to polo\u017eky v\u00fddaj\u016f. Proto nakupujeme hardware t\u0159\u00eddy SuperMicro a sestavujeme na\u0161e vybaven\u00ed z jednotliv\u00fdch \u010d\u00e1st\u00ed, jeho\u017e \u00fadr\u017ebu zaji\u0161\u0165uj\u00ed vl\u00e1dn\u00ed smlouvy. Pou\u017e\u00edv\u00e1me Linux, co\u017e je jeden z d\u016fle\u017eit\u00fdch d\u016fvod\u016f p\u0159echodu na Ansible. <\/p>\n<p>Na\u0161e historie spolupr\u00e1ce s Puppet je n\u00e1sleduj\u00edc\u00ed.<\/p>\n<p><img decoding=\"async\" alt=\"St\u0159ih\u00e1n\u00ed nit\u00ed: p\u0159echod z Puppet Enterprise na Ansible Tower. \u010c\u00e1st 1\" src=\"\/wp-content\/uploads\/2020\/05\/a893499e8bbabf1223461f11d737e777.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nV roce 2007 jsme m\u011bli malou s\u00ed\u0165 20\u201325 uzl\u016f, ve kter\u00e9 jsme zavedli Puppet. V z\u00e1sad\u011b tyto uzly p\u0159edstavovaly pouh\u00e9 \"boxy\" RedHat. V roce 2010 jsme za\u010dali pou\u017e\u00edvat webov\u00e9 rozhran\u00ed Puppet Dashboard pro 45 uzl\u016f. Jak se s\u00ed\u0165 nad\u00e1le rozr\u016fstala, v roce 2014 jsme p\u0159e\u0161li na PE 3.3, provedli jsme celkov\u00fd p\u0159echod s p\u0159episem manifestu pro 75 uzl\u016f. To bylo nutn\u00e9, proto\u017ee Puppet st\u00e1le m\u011bn\u00ed hern\u00ed pravidla, a v tomto p\u0159\u00edpad\u011b zcela zm\u011bnili jazyk. O rok pozd\u011bji, kdy\u017e skon\u010dila podpora 3. verze Puppet Enterprise, jsme museli migrovat na PE 2015.2. Znovu bylo nutn\u00e9 p\u0159epsat manifest podle nov\u00fdch server\u016f a zakoupit licenci s rezervou na 100 uzl\u016f, i kdy\u017e jsme v t\u00e9 dob\u011b m\u011bli pouze 85 uzl\u016f. <\/p>\n<p>Uplynuly pouh\u00e9 2 roky a museli jsme op\u011bt prov\u00e9st zna\u010dnou pr\u00e1ci na p\u0159echodu na novou verzi PE 2016.4. Zakoupili jsme licenci na 300 uzl\u016f, p\u0159i\u010dem\u017e jsme m\u011bli pouze 130. Op\u011bt bylo nutn\u00e9 prov\u00e9st v\u00fdznamn\u00e9 zm\u011bny v manifestu, proto\u017ee nov\u00e1 verze jazyka m\u011bla syntaxi odli\u0161nou od jazyka verze 2015. V d\u016fsledku toho na\u0161e SCM p\u0159e\u0161la z verzeovac\u00edho syst\u00e9mu SVN na Bitbucket (Git). Takov\u00e9 byly na\u0161e \"vztahy\" s Puppet.<\/p>\n<p>Tak\u017ee jsem musel vysv\u011btlit veden\u00ed, pro\u010d se mus\u00edme p\u0159epnout na jinou SCM, a to s n\u00e1sleduj\u00edc\u00edmi argumenty. Prvn\u00ed je vysok\u00e1 cena slu\u017eby. Mluvil jsem s lidmi z RedHat a ti \u0159ekli, \u017ee n\u00e1klady na \u00fadr\u017ebu s\u00edt\u011b se 300 uzly pomoc\u00ed Ansible Tower \u010din\u00ed polovinu n\u00e1klad\u016f Puppet Enterprise. Pokud si je\u0161t\u011b zakoup\u00edte Ansible Engine, cena bude p\u0159ibli\u017en\u011b stejn\u00e1, ale z\u00edsk\u00e1te mnohem v\u00edce funkc\u00ed ne\u017e u PE. Vzhledem k tomu, \u017ee jsme st\u00e1tn\u00ed spole\u010dnost financovan\u00e1 z feder\u00e1ln\u00edho rozpo\u010dtu, je to docela siln\u00fd argument. <\/p>\n<p><img decoding=\"async\" alt=\"St\u0159ih\u00e1n\u00ed nit\u00ed: p\u0159echod z Puppet Enterprise na Ansible Tower. \u010c\u00e1st 1\" src=\"\/wp-content\/uploads\/2020\/05\/8077b9a470286c795a13de3cd6470ce9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDruh\u00fdm argumentem je univerz\u00e1lnost. Puppet podporuje pouze to za\u0159\u00edzen\u00ed, na kter\u00e9m je nainstalov\u00e1n agent Puppet. To znamen\u00e1, \u017ee na v\u0161echny switche je t\u0159eba nainstalovat agenta, a to ve verzi, kter\u00e1 je aktu\u00e1ln\u00ed. A pokud \u010d\u00e1st va\u0161ich switch\u016f podporuje jednu verzi a \u010d\u00e1st jinou, budete muset na n\u011b nainstalovat novou verzi agenta PE, aby v\u0161echny mohly fungovat v jednom syst\u00e9mu 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 dal\u0161\u00ed switche. Tento SCM podporuje Qubes OS, Linux a 4.NET UTM. Ansible Tower tak\u00e9 podporuje \u0159adi\u010de s\u00ed\u0165ov\u00fdch ulo\u017ei\u0161\u0165 NexentaStore, zalo\u017een\u00e9 na j\u00e1dru Illumos \u2013 open-source opera\u010dn\u00edm syst\u00e9mu na b\u00e1zi Unixu. I kdy\u017e jde o omezenou podporu, Ansible Tower ji p\u0159esto poskytuje. <\/p>\n<p>T\u0159et\u00ed argument, velmi d\u016fle\u017eit\u00fd jak pro m\u011b, tak pro na\u0161i administraci, je jednoduchost osvojov\u00e1n\u00ed. Za 10 let jsem se u\u010dil moduly a k\u00f3d manifest\u016f Puppet, ale Ansible jsem se nau\u010dil b\u011bhem t\u00fddne, proto\u017ee s t\u00edmto SCM je mnohem snaz\u0161\u00ed pracovat. Kdy\u017e spou\u0161t\u00edte spustiteln\u00e9 soubory, samoz\u0159ejm\u011b pokud to ned\u011bl\u00e1te bezd\u016fvodn\u011b, zkousnuti jsou rozumn\u00ed a pru\u017en\u00ed zpracovatel\u00e9. Playbooky zalo\u017een\u00e9 na YAML se vyzna\u010duj\u00ed snadn\u00fdm u\u010den\u00edm a rychlost\u00ed pou\u017eit\u00ed. Ti, kte\u0159\u00ed nikdy p\u0159edt\u00edm nesly\u0161eli o YAML, 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 zt\u011b\u017euje 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 provedete n\u011bjak\u00e9 zm\u011bny v manifestu a chcete otestovat sv\u016fj k\u00f3d, mus\u00edte k\u00f3d znovu napsat pro Puppet Master, tedy nastavit soubor Puppet Masteru \/etc\/hosts pro p\u0159ipojen\u00ed v\u0161ech klient\u016f a spustit slu\u017ebu Puppet Server. Teprve pot\u00e9 budete moci vyzkou\u0161et funk\u010dnost s\u00ed\u0165ov\u00e9ho za\u0159\u00edzen\u00ed na jednom hostiteli. To je pom\u011brn\u011b 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 se p\u0159ipojit k testovan\u00e9mu hostiteli p\u0159es SSH protokol. S t\u00edm je mnohem jednodu\u0161\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 hardwaru. Tento SCM bez jak\u00fdchkoliv dal\u0161\u00edch krok\u016f vyu\u017e\u00edv\u00e1 v\u0161echny dostupn\u00e9 informace o va\u0161\u00ed infrastruktu\u0159e a hardware, virtu\u00e1ln\u00edch stroj\u00edch, serverech atd. M\u016f\u017ee komunikovat s va\u0161imi servery RH Satellite, pokud n\u011bjak\u00e9 m\u00e1te, a poskytuje v\u00e1m takovou integraci, kterou nikdy nez\u00edsk\u00e1te, pokud pracujete s Puppet.<\/p>\n<p>Dal\u0161\u00ed d\u016fle\u017eitou v\u011bc\u00ed je podrobn\u00e1 kontrola. V\u00edte, \u017ee Puppet je modul\u00e1rn\u00ed syst\u00e9m, jedn\u00e1 se o klient-server aplikaci, tak\u017ee mus\u00edte definovat existuj\u00edc\u00ed aspekty provozu v\u0161ech va\u0161ich stroj\u016f v jednom dlouh\u00e9m manifestu. Stav ka\u017ed\u00e9ho jednotliv\u00e9ho prvku syst\u00e9mu by m\u011bl b\u00fdt testov\u00e1n ka\u017ed\u00fdch t\u0159icet minut \u2013 to je v\u00fdchoz\u00ed obdob\u00ed. Takto Puppet funguje.<\/p>\n<p>Tower v\u00e1s t\u00e9to pot\u0159eby zbav\u00ed. M\u016f\u017eete bez omezen\u00ed prov\u00e1d\u011bt r\u016fzn\u00e9 procesy na r\u016fzn\u00e9m hardwaru, m\u016f\u017eete vykon\u00e1vat hlavn\u00ed \u00fakoly, spou\u0161t\u011bt dal\u0161\u00ed d\u016fle\u017eit\u00e9 procesy, nastavovat zabezpe\u010den\u00ed, pracovat s datab\u00e1zemi. M\u016f\u017eete d\u011blat v\u0161echno, co v Puppet Enterprise souvis\u00ed s ur\u010dit\u00fdmi obt\u00ed\u017eemi. Pokud jste provedli nastaven\u00ed na jednom hostiteli, chv\u00edli potrv\u00e1, ne\u017e se zm\u011bny projev\u00ed na ostatn\u00edch hostitel\u00edch. V Ansible se v\u0161echny zm\u011bny projev\u00ed sou\u010dasn\u011b.<\/p>\n<p>Nakonec se pod\u00edvejme na bezpe\u010dnostn\u00ed modul. V Ansible Tower je implementov\u00e1n jednodu\u0161e \u00fa\u017easn\u011b, s velkou p\u0159esnost\u00ed a pe\u010dlivost\u00ed. M\u016f\u017eete u\u017eivatel\u016fm poskytovat p\u0159\u00edstup ke konkr\u00e9tn\u00edm slu\u017eb\u00e1m nebo konkr\u00e9tn\u00edm hostitel\u016fm. D\u011bl\u00e1m to se sv\u00fdmi zam\u011bstnanci, kte\u0159\u00ed jsou zvykl\u00ed pracovat na Windows, a omezuji je v p\u0159\u00edstupu k Linuxov\u00e9 shell. Zaji\u0161\u0165uji jim p\u0159\u00edstup k Tower, aby mohli vykon\u00e1vat pouze tu pr\u00e1ci a spou\u0161t\u011bt pouze ty slu\u017eby, kter\u00e9 spadaj\u00ed do jejich kompetence.<\/p>\n<p><img decoding=\"async\" alt=\"St\u0159ih\u00e1n\u00ed nit\u00ed: p\u0159echod z Puppet Enterprise na Ansible Tower. \u010c\u00e1st 1\" src=\"\/wp-content\/uploads\/2020\/05\/f3bd3b26cf20225b6e1800e09dbcfe43.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPod\u00edvejme se na v\u011bci, kter\u00e9 je pot\u0159eba ud\u011blat p\u0159edem, abychom usnadnili p\u0159echod na Ansible Tower. P\u0159edev\u0161\u00edm je nutn\u00e9 p\u0159ipravit va\u0161e vybaven\u00ed. Pokud n\u011bkter\u00e9 prvky va\u0161\u00ed infrastruktury chyb\u00ed v datab\u00e1zi, je t\u0159eba je tam p\u0159idat. Existuj\u00ed syst\u00e9my, kter\u00e9 nem\u011bn\u00ed sv\u00e9 charakteristiky a proto chyb\u00ed v datab\u00e1zi Puppet, ale pokud je tam p\u0159ed p\u0159echodem na Tower nep\u0159id\u00e1te, p\u0159ijdete o \u0159adu v\u00fdhod. M\u016f\u017ee to b\u00fdt \u201e\u0161pinav\u00e1\u201c p\u0159edb\u011b\u017en\u00e1 datab\u00e1ze, ale m\u011bla by obsahovat informace o ve\u0161ker\u00e9m va\u0161em vybaven\u00ed. M\u011bli byste proto napsat dynamick\u00fd skript vybaven\u00ed, kter\u00fd automaticky zapracov\u00e1v\u00e1 v\u0161echny zm\u011bny infrastruktury do datab\u00e1ze, aby Ansible v\u011bd\u011bl, jak\u00e9 hosty m\u00e1 m\u00edt v nov\u00e9m syst\u00e9mu. Nebudete muset t\u00e9to SCM oznamovat, jak\u00e9 hosty jste p\u0159idali a kter\u00e9 hosty ji\u017e neexistuj\u00ed, proto\u017ee to zjist\u00ed automaticky. \u010c\u00edm v\u00edce dat bude v datab\u00e1zi, t\u00edm u\u017eite\u010dn\u011bj\u0161\u00ed a flexibiln\u011bj\u0161\u00ed bude Ansible. Funguje tak, jako by jednodu\u0161e na\u010d\u00edtal z datab\u00e1ze \u010d\u00e1rov\u00fd k\u00f3d stavu vybaven\u00ed.<\/p>\n<p>V\u011bnujte n\u011bjak\u00fd \u010das sezn\u00e1men\u00ed se s p\u0159\u00edkazov\u00fdm \u0159\u00e1dkem Ansible. Spus\u0165te n\u011bjak\u00e9 speci\u00e1ln\u00ed p\u0159\u00edkazy, abyste otestovali fungov\u00e1n\u00ed skriptu vybaven\u00ed, napi\u0161te a spus\u0165te n\u011bjak\u00e9 jednoduch\u00e9, ale u\u017eite\u010dn\u00e9 playbooky, vyu\u017eijte \u0161ablony Jinja2 tam, kde je to vhodn\u00e9. Zkuste napsat roli a skript pro slo\u017eit\u00fd v\u00edcestup\u0148ov\u00fd proces, pou\u017e\u00edvaj\u00edc\u00ed standardn\u00ed, \u010dasto pou\u017e\u00edvanou konfiguraci za\u0159\u00edzen\u00ed. Hrajte si s t\u011bmito v\u011bcmi, otestujte, jak to funguje. Tak se nau\u010d\u00edte pracovat s n\u00e1stroji pro vytv\u00e1\u0159en\u00ed knihoven pou\u017e\u00edvan\u00fdch v Tower. U\u017e jsem \u0159\u00edkal, \u017ee p\u0159\u00edprava na p\u0159echod mi trvala asi 3 m\u011bs\u00edce. Domn\u00edv\u00e1m se, \u017ee na z\u00e1klad\u011b m\u00fdch zku\u0161enost\u00ed to zvl\u00e1dnete rychleji. Nepova\u017eujte tento \u010das za ztracen\u00fd, proto\u017ee pozd\u011bji poc\u00edt\u00edte v\u0161echny v\u00fdhody vykonan\u00e9 pr\u00e1ce. <\/p>\n<p>D\u00e1le je pot\u0159eba rozhodnout, co o\u010dek\u00e1v\u00e1te od Ansible Tower, co konkr\u00e9tn\u011b by m\u011bl tento syst\u00e9m pro v\u00e1s ud\u011blat. <\/p>\n<p><img decoding=\"async\" alt=\"St\u0159ih\u00e1n\u00ed nit\u00ed: p\u0159echod z Puppet Enterprise na Ansible Tower. \u010c\u00e1st 1\" src=\"\/wp-content\/uploads\/2020\/05\/4511b3f34d57e489be1103c3b77fc98f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPot\u0159ebujete nasazen\u00ed syst\u00e9mu na pr\u00e1zdn\u00e9m hardwaru nebo na pr\u00e1zdn\u00fdch virtu\u00e1ln\u00edch stroj\u00edch? Nebo si chcete zachovat p\u016fvodn\u00ed pracovn\u00ed podm\u00ednky a nastaven\u00ed st\u00e1vaj\u00edc\u00edho vybaven\u00ed? To je velmi d\u016fle\u017eit\u00fd aspekt pro fungov\u00e1n\u00ed st\u00e1tn\u00edch spole\u010dnost\u00ed, proto si mus\u00edte b\u00fdt jisti, \u017ee se v\u00e1m poda\u0159\u00ed migrovat a nasadit Ansible na existuj\u00edc\u00ed konfiguraci. Ur\u010dete rutinn\u00ed administrativn\u00ed procesy, kter\u00e9 chcete automatizovat. Zjist\u011bte, zda pot\u0159ebujete nasadit specifick\u00e9 aplikace a slu\u017eby na nov\u00e9m syst\u00e9mu. Sestavte seznam toho, co chcete ud\u011blat, a ur\u010dete priority. <\/p>\n<p>Pak za\u010dn\u011bte ps\u00e1t k\u00f3d skript\u016f a rol\u00ed, kter\u00e9 zabezpe\u010d\u00ed proveden\u00ed v\u00e1mi napl\u00e1novan\u00fdch \u00fakol\u016f. Spojte je do projekt\u016f, logick\u00e9 kolekce p\u0159\u00edslu\u0161n\u00fdch skript\u016f playbook\u016f. Ka\u017ed\u00fd projekt se bude vztahovat na samostatn\u00e9 \u00falo\u017ei\u0161t\u011b Git nebo jin\u00e9 \u00falo\u017ei\u0161t\u011b v z\u00e1vislosti na tom, jak\u00fd spr\u00e1vce k\u00f3du pou\u017e\u00edv\u00e1te. M\u016f\u017eete spravovat skripty playbooku a slo\u017eky playbooku tak, \u017ee je ru\u010dn\u011b um\u00edst\u00edte do Project Base Path na serveru Tower, nebo um\u00edst\u00edte playbook do jak\u00e9hokoli syst\u00e9mu \u0159\u00edzen\u00ed verz\u00ed (SCM) podporovan\u00e9ho Towerem, v\u010detn\u011b Git, Subversion, Mercurial a Red Hat Insights. Uvnit\u0159 jednoho projektu m\u016f\u017eete m\u00edt tolik skript\u016f, kolik chcete. Nap\u0159\u00edklad jsem vytvo\u0159il jeden z\u00e1kladn\u00ed projekt, ve kter\u00e9m jsem um\u00edstil skript pro z\u00e1kladn\u00ed prvky RedHat, skript pro z\u00e1klad Linuxu, skripty pro ostatn\u00ed z\u00e1kladn\u00ed metriky. Tak\u017ee v jednom projektu byly r\u016fzn\u00e9 role a skripty, kter\u00e9 byly spravov\u00e1ny z jednoho Git \u00falo\u017ei\u0161t\u011b. <\/p>\n<p>Spou\u0161t\u011bjte v\u0161echny tyto prvky p\u0159es p\u0159\u00edkazov\u00fd \u0159\u00e1dek, je to dobr\u00fd zp\u016fsob, jak ov\u011b\u0159it jejich funk\u010dnost. T\u00edmto zp\u016fsobem se p\u0159iprav\u00edte na instalaci Tower.<\/p>\n<p>Poj\u010fme si promluvit o transk\u00f3dov\u00e1n\u00ed manifestu Puppet, proto\u017ee jsem na to str\u00e1vil hodn\u011b \u010dasu, ne\u017e jsem si uv\u011bdomil, co skute\u010dn\u011b je t\u0159eba ud\u011blat. <\/p>\n<p><img decoding=\"async\" alt=\"St\u0159ih\u00e1n\u00ed nit\u00ed: p\u0159echod z Puppet Enterprise na Ansible Tower. \u010c\u00e1st 1\" src=\"\/wp-content\/uploads\/2020\/05\/abbc9ffb10b623dc29bcd975dca3bb80.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nJak jsem ji\u017e zm\u00ednil, Puppet uchov\u00e1v\u00e1 v\u0161echna nastaven\u00ed a parametry za\u0159\u00edzen\u00ed v jednom dlouh\u00e9m manifestu, a v tomto manifestu je ulo\u017eeno v\u0161e, co by tento SCM m\u011bl d\u011blat. P\u0159i p\u0159echodu nen\u00ed t\u0159eba v\u0161echny \u00fakoly shrom\u00e1\u017edit do jednoho seznamu; m\u00edsto toho zva\u017ete strukturu nov\u00e9ho syst\u00e9mu: role, sc\u00e9n\u00e1\u0159e, \u0161t\u00edtky, skupiny a co by do nich m\u011blo pat\u0159it. N\u011bkter\u00e9 samostatn\u00e9 prvky s\u00edt\u011b by m\u011bly b\u00fdt slou\u010deny do skupin, pro kter\u00e9 lze vytvo\u0159it sc\u00e9n\u00e1\u0159e. Slo\u017eit\u011bj\u0161\u00ed prvky infrastruktury, kter\u00e9 vy\u017eaduj\u00ed zna\u010dn\u00e9 mno\u017estv\u00ed zdroj\u016f, v\u010detn\u011b samostatn\u00fdch t\u0159\u00edd, mohou b\u00fdt slou\u010deny do rol\u00ed. P\u0159ed migrac\u00ed si s t\u00edm mus\u00edte ujasnit. Pokud vytv\u00e1\u0159\u00edte objemn\u00e9 role nebo sc\u00e9n\u00e1\u0159e, kter\u00e9 se na jednom displeji nevejdou, m\u011bli byste pou\u017e\u00edvat \u0161t\u00edtky, abyste byli schopni zachytit jednotliv\u00e9 \u010d\u00e1sti infrastruktury. <\/p>\n<p>18:00<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ua-hosting\/blog\/500588\/\"> O\u0159\u00edznut\u00ed nit\u00ed: p\u0159echod z Puppet Enterprise na Ansible Tower. \u010c\u00e1st 2 <\/a><\/noindex><\/p>\n<h3>Mal\u00e1 reklama \ud83d\ude42<\/h3>\n<p>\nD\u011bkujeme, \u017ee s n\u00e1mi z\u016fst\u00e1v\u00e1te. L\u00edb\u00ed se v\u00e1m na\u0161e \u010dl\u00e1nky? Chcete vid\u011bt v\u00edce zaj\u00edmav\u00fdch materi\u00e1l\u016f? Podpo\u0159te n\u00e1s objedn\u00e1vkou nebo doporu\u010den\u00edm zn\u00e1m\u00fdm, <noindex><a rel=\"nofollow\" href=\"https:\/\/ua-hosting.company\/cloudvps\/nl\">cloudov\u00e9 VPS pro v\u00fdvoj\u00e1\u0159e od 4,99 $<\/a><\/noindex>, <b>unik\u00e1tn\u00ed alternativa entry-level server\u016f, kterou jsme pro v\u00e1s vymysleli:<\/b> <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/ua-hosting\/blog\/347386\/\">V\u0161echny pravdy o VPS (KVM) E5-2697 v3 (6 jader) 10GB DDR4 480GB SSD 1Gbps od 19 $ nebo jak spr\u00e1vn\u011b rozd\u011blit server?<\/a><\/noindex> (k dispozici varianty s RAID1 a RAID10, a\u017e 24 jader a a\u017e 40GB DDR4).<\/p>\n<p><b>Dell R730xd je dvakr\u00e1t levn\u011bj\u0161\u00ed v datov\u00e9m centru Equinix Tier IV v Amsterdamu?<\/b> Jen 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 $<\/a><\/noindex> v Nizozemsku! <b>Dell R420 \u2014 2x E5-2430 2.2GHz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 od 99 $!<\/b><\/b> \u010ct\u011bte o tom <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/ua-hosting\/blog\/329618\/\">Jak postavit infrastrukturu podnikov\u00e9 t\u0159\u00eddy s pou\u017eit\u00edm server\u016f Dell R730xd E5-2650 v4 v hodnot\u011b 9000 eur za pakatel?<\/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.3 - 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\/cs\/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.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\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\/cs\/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\udd47O\u0159\u00edznut\u00ed nit\u00ed: p\u0159echod z Puppet Enterprise na Ansible Tower. \u010c\u00e1st 1 | ProHoster","description":"N\u00e1rodn\u00ed informa\u010dn\u00ed slu\u017eba satelitn\u00edch dat o \u017eivotn\u00edm prost\u0159ed\u00ed (NESDIS) sn\u00ed\u017eila sv\u00e9 n\u00e1klady na spr\u00e1vu konfigurace Red Hat Enterprise Linux (RHEL) o 35 % p\u0159echodem z Puppet Enterprise na Ansible Tower.","canonical_url":"https:\/\/prohoster.info\/cs\/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":"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\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\/cs\/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\/cs\/wp-json\/wp\/v2\/posts\/80491","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=80491"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/80491\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media\/80492"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=80491"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=80491"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=80491"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}