{"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\/et\/blog\/administrirovanie\/obrezaem-niti-perehod-s-puppet-enterprise-na-ansible-tower-chast-1","title":{"rendered":"L\u00f5ikame niite: \u00fcleminek Puppet Enterprise'ilt Ansible Towerile. Osa 1","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Rahvuslik keskkonnaandmete satelliitide teabe s\u00fcsteem (NESDIS) v\u00e4hendas Red Hat Enterprise Linuxi (RHEL) konfiguratsioonihalduse kulusid 35%, liikudes Puppet Enterprise'ilt Ansible Towerile. Selles videos kategoorias \u201ekuidas me seda tegime\u201c selgitab s\u00fcsteemiinsener Michael Rau, miks see migratsioon tehti, jagab kasulikke n\u00f5uandeid ja kogemusi, mis saadud \u00fcleminekul \u00fchest SCM-ist teise. <\/p>\n<p>Selles videos \u00f5pite:<\/p>\n<ul>\n<li>kuidas p\u00f5hjendada juhtkonnale \u00fclemineku vajadust Puppet Enterprise'ilt Ansible Towerile;<\/li>\n<li>milliseid strateegiaid kasutada sujuvaks \u00fcleminekuks;<\/li>\n<li>n\u00f5uandeid PE manifestide translatsiooniks Ansible Playbookiks;<\/li>\n<li>soovitusi Ansible Toweri optimaalseks seadistamiseks.<\/li>\n<\/ul>\n<p>\n<img decoding=\"async\" alt=\"L\u00f5ikame niite: \u00fcleminek Puppet Enterprise&#039;ilt Ansible Towerile. Osa 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>Tere k\u00f5igile, mina olen Michael Rau, ActioNet'i vanem s\u00fcsteemiinsener, kes t\u00f6\u00f6tab Riikliku Ookean ja Atmosf\u00e4\u00e4ri Administratsiooni (NOAA) NESDIS'i teenistuseks. T\u00e4na r\u00e4\u00e4gime ridade k\u00e4rpimisest \u2013 minu isiklik kogemus \u00fcleminekust Puppet Enterprise'ilt Ansible Towerile. Selle esitluse eesm\u00e4rgiks on \u201evaadata mu arme\u201d, mis on j\u00e4\u00e4nud p\u00e4rast minu \u00fcleminekut aasta alguses. Soovin jagada, mida olen selle protsessi k\u00e4igus \u00f5ppinud. Nii et kui v\u00f5tate sarnase ette, saate kasutada minu kogemusi, et \u00fcleminek sujuks paremini.<\/p>\n<p>Te n\u00e4ete slaide, mis on sarnased sellele, iga esitluse alguses Ansible Festil. Sellel slaidil on v\u00e4lja toodud minu ettev\u00f5tte automatiseerimise lugu. Ma ei ole selles alles algaja, olen kasutanud Puppet\/Puppet Enterprise'i alates 2007. aastast. Alustasin Ansible'i kasutamist 2016. aastal ja mind, nagu ka paljusid teisi selle toote kasutajaid, t\u00f5mbas \u201etrikkide\u201d tegemise v\u00f5imalus k\u00e4surea ja lihtsate skriptide (playbookide) kaudu. 2017. aasta l\u00f5pus p\u00f6\u00f6rdusin oma juhtkonna poole t\u00f5siste p\u00f5hjustega, miks \u00fcle minna Ansible Towerile. M\u00f5ne hetke p\u00e4rast r\u00e4\u00e4gin, mis mind selle sammu astuma sundis. P\u00e4rast juhtkonna heakskiitu kulus veel paar kuud, et plaan ellu viia, ja ma tegin \u00fclemineku jaanuaris-veebruaris sel aastal. Nii et loobusime t\u00e4ielikult Puppetist Ansible'i kasuks, ja see on suurep\u00e4rane saavutus. <\/p>\n<p><img decoding=\"async\" alt=\"L\u00f5ikame niite: \u00fcleminek Puppet Enterprise&#039;ilt Ansible Towerile. Osa 1\" src=\"\/wp-content\/uploads\/2020\/05\/0e179ef00aa22edae72270e53d9787df.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAnsible's ability to write and use roles and playbooks is what I find most appealing. Roles are perfect for creating various but interrelated tasks and placing all relevant data for these tasks in one location. A playbook is a YAML syntax file that describes actions for one or several hosts. I primarily share these capabilities with software developers. Ansible Tower allows me to say, 'No, you do not have shell access, but I provide you the ability to run all Tower processes and restart the service whenever you need.' I will explain our working environment and the equipment we use. <\/p>\n<p><img decoding=\"async\" alt=\"L\u00f5ikame niite: \u00fcleminek Puppet Enterprise&#039;ilt Ansible Towerile. Osa 1\" src=\"\/wp-content\/uploads\/2020\/05\/1dd8f9d0025660a1f3c17a174681caec.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nThis is a federal LAN with 7 physical sites connected via a cloud MPLS, 140 RHEL servers, 99% of which are virtual (vSphere), SuperMicro hardware, NexentaStore network storage, a set of Cisco, Arista, and Cumulus switches, and Fortinet UTM unified threat management tools at each site. <\/p>\n<p>The federal network means that I must use all information protection measures required by legislation. You should bear in mind that Puppet Enterprise does not support most of the equipment we use. We are forced to use budget hardware as government bodies face funding issues for this expense. Therefore, we purchase SuperMicro class hardware and assemble our equipment from individual parts, the maintenance of which is guaranteed by government contracts. We use Linux, and this is one of the important reasons for switching to Ansible. <\/p>\n<p>Our history with Puppet is as follows.<\/p>\n<p><img decoding=\"async\" alt=\"L\u00f5ikame niite: \u00fcleminek Puppet Enterprise&#039;ilt Ansible Towerile. Osa 1\" src=\"\/wp-content\/uploads\/2020\/05\/a893499e8bbabf1223461f11d737e777.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\n2007. aastal oli meil v\u00e4ike v\u00f5rk, kus oli 20-25 s\u00f5lme, kuhu paigaldasime Puppet'i. Enamasti olid need s\u00f5lmed lihtsalt RedHat'i \"kastid\". 2010. aastal hakkasime kasutama Puppet Dashboard'i veebiliidest 45 s\u00f5lme jaoks. Kuna v\u00f5rk j\u00e4tkas laienemist, 2014. aastal \u00dcksikasjalik \u00fcleminek PE 3.3-le, t\u00e4ieliku \u00fcleminekuga 75 s\u00f5lme mansi arenguga. See tuli teha, kuna Puppet meeldib m\u00e4ngureegleid muuta ning sel juhul muutsid nad t\u00e4ielikult keelt. Aasta hiljem, kui 3. versiooni Puppet Enterprise'i tugi l\u00f5petati, pidime migreerima PE 2015.2-le. J\u00f5udis taas \u00fcmberehitus uusimate serverite jaoks ja ostsime litsentsi 100 s\u00f5lme jaoks, kuigi sel hetkel oli meil vaid 85 s\u00f5lme. <\/p>\n<p>Kaks aastat hiljem pidime taas l\u00e4bi viima suurt t\u00f6\u00f6d \u00fcleminekuks uuele versioonile PE 2016.4. Ostsime litsentsi 300 s\u00f5lme jaoks, kuid meil oli vaid 130. Me pidime j\u00e4lle t\u00f5siselt muutma mansi, kuna uuel keele versioonil oli s\u00fcntaks, mis erineb 2015. aasta versiooni keelest. L\u00f5puks kolis meie SCM versioonihalduss\u00fcsteemilt SVN Bitbucket'i (Git) peale. Sellised olid meie \"suhted\" Puppet'iga.<\/p>\n<p>Nii et pidin juhtkonnale selgitama, miks peame minema \u00fcle teisele SCM-le, kasutades j\u00e4rgmisi argumente. Esimene - teenuse k\u00f5rge hind. K\u00f5neldes RedHat'i poisiga \u00fctlesid nad, et 300 s\u00f5lme haldamise hind Ansible Toweriga on ainult Pool Puppet Enterprise'i \u00f5igusi. Kui ostate veel Ansible Engine'i, on hind ligikaudu sama, kuid saate palju rohkem funktsioone kui PE. Kuna oleme riigiettev\u00f5te, mille rahastamine toimub f\u00f6deraalse eelarve kaudu, on see \u00fcsna kaalukas argument. <\/p>\n<p><img decoding=\"async\" alt=\"L\u00f5ikame niite: \u00fcleminek Puppet Enterprise&#039;ilt Ansible Towerile. Osa 1\" src=\"\/wp-content\/uploads\/2020\/05\/8077b9a470286c795a13de3cd6470ce9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTeine argument - universaalsus. Puppet toetab ainult neid seadmeid, kus on Puppet'i agent. See t\u00e4hendab, et k\u00f5ikide l\u00fclitite jaoks peab olema agent paigaldatud, ja see peab olema viimase versiooniga. Kui osa teie l\u00fclititest toetab \u00fchte versiooni, kuid osa teist, peate nendel uut PE agenti versiooni paigaldama, et k\u00f5ik need saaksid \u00fches SCM s\u00fcsteemis t\u00f6\u00f6tada.<\/p>\n<p>Ansible Toweri s\u00fcsteem t\u00f6\u00f6tab erinevalt, kuna tal ei ole agente, vaid on moodulid, mis toetavad Cisco l\u00fclitid ja k\u00f5iki teisi l\u00fcliteid. See SCM toetab Qubes OS-i, Linuxit ja 4.NET UTM-i. Ansible Tower toetab ka NexentaStore'i, mis p\u00f5hineb Illumose tuumadel \u2013 Unix-p\u00f5hine avatud l\u00e4htekoodiga operatsioonis\u00fcsteem. Kuigi see tugi on v\u00e4ga v\u00e4ike, pakub Ansible Tower seda siiski. <\/p>\n<p>Kolmas argument, mis on mulle ja meie haldusele v\u00e4ga oluline, on lihtsus. Olen 10 aastat \u00f5ppinud Puppet'i mooduleid ja manifestide koodi, kuid Ansible'i \u00f5ppisin n\u00e4dalaga, kuna see SCM on palju lihtsam kasutada. Kui k\u00e4itate t\u00e4idetavaid faile, siis kui te ei tee seda p\u00f5hjendamatult, t\u00f6\u00f6tavad nende kallal m\u00f5istlikud ja vastutulelikud t\u00f6\u00f6tlejad. YAML-p\u00f5hised playbook'id on kergesti \u00f5pitavad ja kiiresti kasutatavad. Need, kes ei ole kunagi varem YAML-i kuulnud, saavad lihtsalt skripte lugeda ja kergesti m\u00f5ista, kuidas see t\u00f6\u00f6tab. <\/p>\n<p>Ausalt \u00f6eldes, Puppet muudab teie t\u00f6\u00f6 arendajana palju keerulisemaks, kuna see p\u00f5hineb Puppet Master'i kasutamisel. See on ainus masin, millel on \u00f5igus suhelda Puppet agentidega. Kui olete teinud mingeid muudatusi manifestis ja soovite oma koodi testida, peate koodi Puppet Master'ile \u00fcmber kirjutama, seadma Puppet Master'i faili \/etc\/hosts, et \u00fchendust saada k\u00f5ikide klientidega, ja k\u00e4ivitama Puppet Server'i teenuse. Alles p\u00e4rast seda saate testida v\u00f5rgu seadmeid \u00fchel hostil. See on \u00fcsna valutav protseduur. <br \/>\nAnsible'is on k\u00f5ik palju lihtsam. K\u00f5ik, mida peate tegema, on arendada kood masinale, millel on v\u00f5imalik testitava hostiga l\u00e4bi SSH protokolli suhelda. Sellega on palju lihtsam t\u00f6\u00f6tada.<\/p>\n<p>J\u00e4rgmine suur pluss Ansible Tower'is on v\u00f5imalus rakendada juba olemasolevat tugis\u00fcsteemi ja s\u00e4ilitada olemasolev riistvara konfiguratsioon. See SCM kasutab k\u00f5ik olemasolevat teavet teie infrastruktuuri ja seadmete, virtuaalmasinate, serverite jne kohta ilma igasuguste t\u00e4iendavate toiminguteta. See saab suhelda teie RH Satellite serveritega, kui need on olemas, ja pakub teile sellist integratsiooni, mida te kunagi ei saaks, t\u00f6\u00f6tades Puppetiga.<\/p>\n<p>Veel t\u00e4htsam on detailsed kontrollid. Te teate, et Puppet on modulaarne s\u00fcsteem, klient-serveri rakendus, seega peate m\u00e4\u00e4ratlema k\u00f5igi teie masinate t\u00f6\u00f6s eksisteerivad aspektid \u00fches pikas manifestis. Samuti tuleb testida iga s\u00fcsteemi elemendi seisundit iga poole tunni tagant \u2013 see on vaikimisi ajavahemik. Just nii t\u00f6\u00f6tab Puppet.<\/p>\n<p>Tower vabastab teid sellest. Saate piiramatult teostada erinevaid protsesse erinevates seadmetes, teha p\u00f5hitegevust, k\u00e4ivitada muid olulisi protsesse, seadistada turvas\u00fcsteemi, t\u00f6\u00f6tada andmebaasidega. K\u00f5ik see, millega Puppet Enterprise'is on seotud teatud raskused. Nii et kui teete seadistuse \u00fchel hostil, peab aega minema, enne kui muudatused j\u00f5ustuvad teistel hostidel. Ansible'is j\u00f5ustuvad k\u00f5ik muudatused samaaegselt.<\/p>\n<p>L\u00f5puks vaatame turvamoodulit. Ansible Toweris on see ellu viidud lihtsalt h\u00e4mmastavalt, suure t\u00e4psuse ja hoolikusega. Saate anda kasutajatele \u00f5iguse p\u00e4\u00e4seda teatud teenustele v\u00f5i teatud hostidele. Maakohas piirduvad mu t\u00f6\u00f6tajad, kes on harjunud Windowsiga, Linuxi shell'i juurdep\u00e4\u00e4suga. Ma hellitan neile juurdep\u00e4\u00e4su Towerisse, et nad saaksid teha ainult neid t\u00f6id ja k\u00e4ivitada ainult neid teenuseid, mis kuuluvad nende p\u00e4devusse.<\/p>\n<p><img decoding=\"async\" alt=\"L\u00f5ikame niite: \u00fcleminek Puppet Enterprise&#039;ilt Ansible Towerile. Osa 1\" src=\"\/wp-content\/uploads\/2020\/05\/f3bd3b26cf20225b6e1800e09dbcfe43.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nVaatame, mida on vaja ette valmistada, et \u00fcleminek Ansible Towerile sujuvam oleks. Esiteks peate valmistama ette oma seadmed. Kui m\u00f5ningad teie infrastruktuuri elemendid ei ole veel andmebaasis, tuleb need sinna lisada. On s\u00fcsteeme, mille omadused ei muutu ja seega ei ole need Puppet'i andmebaasis, kuid kui te ei lisa neid sinna enne Towerile \u00fcleminekut, kaotate mitmed eelised. See v\u00f5ib olla \"m\u00e4\u00e4rdunud\" eeldatav andmebaas, kuid see peab sisaldama teavet kogu teie olemasoleva varustuse kohta. Seet\u00f5ttu peaksite kirjutama d\u00fcnaamilise seadme skripti, mis automaatselt kannab infrastruktuuri muudatused andmebaasi, et Ansible saaks teada, millised hostid peavad uues s\u00fcsteemis olema. Te ei pea sellele SCM-ile teatama, milliseid hoste olete lisanud ja milliseid enam ei eksisteeri, kuna seda saab automaatselt teada. Mida rohkem andmeid andmebaasis on, seda kasulikum ja paindlikum on Ansible. Ta t\u00f6\u00f6tab nagu seade, mis lihtsalt loeb andmebaasist seadmete oleku triipkoodi.<\/p>\n<p>P\u00fchendage veidi aega Ansible'i k\u00e4surea t\u00f6\u00f6ga tutvumisele. K\u00e4ivitage m\u00f5ni spetsiaalne k\u00e4sk, et kontrollida seadme skripti t\u00f6\u00f6d, kirjutage ja k\u00e4ivitage m\u00f5ned lihtsad, kuid kasulikud playbook'i stsenaariumid, kasutage Jinja2 malli seal, kus see on asjakohane. Proovige kirjutada roll ja stsenaarium keerukaks mitmeastmeliseks protsessiks, kasutades tavalist, sageli esinevat seadmete konfiguratsiooni. Katsetage nendega, testige, kuidas see t\u00f6\u00f6tab. Nii \u00f5pite t\u00f6\u00f6riistu, mida kasutatakse Toweri raamatukogude loomisel. Olen juba \u00f6elnud, et minu ettevalmistus \u00fcleminekuks kestis umbes 3 kuud. Arvan, et minu kogemusele toetudes suudate seda kiiremini teha. \u00c4rge pidage seda aega raiskamiseks, sest hiljem tunnete k\u00f5iki tehtud t\u00f6\u00f6 eeliseid. <\/p>\n<p>Seej\u00e4rel tuleb otsustada, mida te Ansible Towerilt ootate, mida see s\u00fcsteem peaks teie jaoks tegema. <\/p>\n<p><img decoding=\"async\" alt=\"L\u00f5ikame niite: \u00fcleminek Puppet Enterprise&#039;ilt Ansible Towerile. Osa 1\" src=\"\/wp-content\/uploads\/2020\/05\/4511b3f34d57e489be1103c3b77fc98f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nKas vajate s\u00fcsteemi juurutamist t\u00fchjale riistvarale v\u00f5i t\u00fchjadesse virtuaalmasinatesse? V\u00f5i soovite hoida olemasolevaid t\u00f6\u00f6tingimusi ja seadistusi? See on v\u00e4ga oluline aspekt riigiasutuste t\u00f6\u00f6 jaoks, seega peate olema kindel, et suudate migratsiooni teostada ja Ansible'i olemasolevale konfiguratsioonile rakendada. M\u00e4\u00e4rake rutiinsed administratiivsed protsessid, mida soovite automatiseerida. Selgitage v\u00e4lja, kas peate juurutama uut s\u00fcsteemi spetsiifilisi rakendusi ja teenuseid. Koostage nimekiri selle kohta, mida soovite teha, ja seada prioriteedid. <\/p>\n<p>Seej\u00e4rel minge edasi koodiskripti ja rollide kirjutamisega, mis tagavad teie plaanitud \u00fclesannete t\u00e4itmise. Koguge need Projects'isse, loogilisse kogumisse vastavaid playbook'e. Iga Project kuulub eraldi Git-repositooriumisse v\u00f5i m\u00f5nda muusse repositoriumisse s\u00f5ltuvalt sellest, millist koodihaldurit kasutate. Saate hallata playbook'e ja playbook'i katalooge, paigutades need k\u00e4sitsi Serveri Tower'i Project Base Path'i v\u00f5i panedes playbook'i m\u00f5nda Tower'i toetatud l\u00e4htekoodihalduss\u00fcsteemi (SCM), sealhulgas Git, Subversion, Mercurial ja Red Hat Insights. \u00dches Project'is v\u00f5ite paigutada nii palju skripte, kui soovite. N\u00e4iteks l\u00f5in \u00fche p\u00f5hialuste Project'i, kuhu paigutasin skripti RedHat'i p\u00f5hielementide jaoks, skripti Linuxi baasi jaoks ja skripte teiste p\u00f5hin\u00e4itaja jaoks. Nii esines \u00fches projektis mitmesuguseid rolle ja skripte, mida haldati \u00fchest Git-repositooriumist. <\/p>\n<p>K\u00e4ivitage k\u00f5ik need asjad k\u00e4surealt, see on hea viis nende toimimise kontrollimiseks. Nii valmistute Toweri installimiseks.<\/p>\n<p>R\u00e4\u00e4gime veidi Puppet'i manifisti transkodeerimisest, sest kulutasin sellele palju aega, enne kui taipasin, mida t\u00f5eliselt teha tuleb. <\/p>\n<p><img decoding=\"async\" alt=\"L\u00f5ikame niite: \u00fcleminek Puppet Enterprise&#039;ilt Ansible Towerile. Osa 1\" src=\"\/wp-content\/uploads\/2020\/05\/abbc9ffb10b623dc29bcd975dca3bb80.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNagu ma juba \u00fctlesin, hoiab Puppet k\u00f5ik seadistused ja seadme parameetrid \u00fches pikemas manifestis, kus on kajastatud k\u00f5ik, mida see SCM tegema peab. \u00dcleminekul ei pea te k\u00f5iki oma \u00fclesandeid \u00fchte nimekirja suruma; m\u00f5elge pigem uue s\u00fcsteemi struktuurile: rollidele, stsenaariumitele, siltidele, r\u00fchmadele ja sellele, mida sinna peaks kuuluma. M\u00f5ned iseseisvad v\u00f5rguelemendid tuleks r\u00fchmitada gruppidesse, mille jaoks saab luua stsenaariume. T\u00e4iendavad infrastruktuuri elemendid, mis kasutavad suurt hulka ressursse, sealhulgas iseseisvad klassid, saab koondada rollidesse. Enne migreerimist peate seda v\u00e4lja selgitama. Kui loote mahukaid rolle v\u00f5i stsenaariume, mis ei mahdu \u00fchele ekraanile, peaksite kasutama silte, et saaksite h\u00f5lpsasti haarata erinevaid infrastruktuuri osi. <\/p>\n<p>18:00<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/ua-hosting\/blog\/500588\/\"> L\u00f5ikame niidid: \u00fcleminekut Puppet Enterprise'ist Ansible Tower'isse. Osa 2 <\/a><\/noindex><\/p>\n<h3>Veidi reklaami \ud83d\ude42<\/h3>\n<p>\nAit\u00e4h, et olete meiega. Kas teile meeldivad meie artiklid? Kas soovite n\u00e4ha rohkem huvitavat sisu? Toetage meid, tellides teenuse v\u00f5i soovitades meid tuttavatele. <noindex><a rel=\"nofollow\" href=\"https:\/\/ua-hosting.company\/cloudvps\/nl\">Pilve VPS arendajatele alates $4.99<\/a><\/noindex>, <b>ainulaadne entry-level serverite analoog, mille oleme teie jaoks v\u00e4lja m\u00f5elnud:<\/b> <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/ua-hosting\/blog\/347386\/\">Kogu t\u00f5de VPS (KVM) E5-2697 v3 (6 Cores) 10GB DDR4 480GB SSD 1Gbps alates $19 v\u00f5i kuidas jagada serverit \u00f5igesti?<\/a><\/noindex> (saadaval RAID1 ja RAID10 variandid, kuni 24 tuuma ja kuni 40GB DDR4).<\/p>\n<p><b>Dell R730xd on Equinixi Tier IV andmekeskuses Amsterdamis kaks korda odavam?<\/b> Ainult meie juures <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 alates $199<\/a><\/noindex> Hollandis! <b>Dell R420 \u2014 2x E5-2430 2.2Ghz 6C 128GB DDR3 2x960GB SSD 1Gbps 100TB \u2014 alates $99!<\/b><\/b> Lugege sellest <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/company\/ua-hosting\/blog\/329618\/\">Kuidas luua ettev\u00f5tte tasemel infrastruktuuri, kasutades Dell R730xd E5-2650 v4 servereid, mille hind on 9000 eurot, taskukohase hinna eest?<\/a><\/noindex><br \/>\n<br \/>Allikas: <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.1.1 - 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\/et\/blog\/administrirovanie\/obrezaem-niti-perehod-s-puppet-enterprise-na-ansible-tower-chast-1\" \/>\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\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\/et\/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\udd47L\u00f5ikame niidid: \u00fcleminekut Puppet Enterprise'ist Ansible Tower'isse. Osa 1 | ProHoster","description":"Riiklik keskkonnainformatsiooni satelliitandmete teenistus (NESDIS) v\u00e4hendas oma Red Hat Enterprise Linuxi (RHEL) konfiguratsiooni haldamise kulusid 35% Puppet Enterprise'ist Ansible Tower'isse \u00fcleminekul.","canonical_url":"https:\/\/prohoster.info\/et\/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":"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\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\/et\/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\/et\/wp-json\/wp\/v2\/posts\/80491","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=80491"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/posts\/80491\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media\/80492"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/media?parent=80491"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/categories?post=80491"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/et\/wp-json\/wp\/v2\/tags?post=80491"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}