{"id":35513,"date":"2019-10-31T22:04:46","date_gmt":"2019-10-31T19:04:46","guid":{"rendered":"https:\/\/prohoster.info\/blog\/ansible-obnovleniya-v-klyuchevyh-resheniyah-dlya-avtomatizatsii-vashego-mira\/"},"modified":"2019-10-31T22:04:46","modified_gmt":"2019-10-31T19:04:46","slug":"ansible-obnovleniya-v-klyuchevyh-resheniyah-dlya-avtomatizatsii-vashego-mira","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/ansible-obnovleniya-v-klyuchevyh-resheniyah-dlya-avtomatizatsii-vashego-mira","title":{"rendered":"Ansible: p\u00ebrdit\u00ebsime n\u00eb zgjidhjet ky\u00e7e p\u00ebr automatizimin e bot\u00ebs tuaj","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Komuniteti Ansible vazhdon t\u00eb surprizoj\u00eb me p\u00ebrmbajtje t\u00eb reja \u2013 plugina dhe module \u2013 duke krijuar gjithashtu shum\u00eb pun\u00eb t\u00eb re p\u00ebr ata q\u00eb jan\u00eb t\u00eb angazhuar n\u00eb mb\u00ebshtetje t\u00eb Ansible, pasi kodi i ri duhet t\u00eb integrohet sa m\u00eb shpejt n\u00eb repozitat. Nuk \u00ebsht\u00eb gjithmon\u00eb e leht\u00eb t\u00eb p\u00ebrfundohet n\u00eb koh\u00eb dhe l\u00ebshimi i disa produkteve q\u00eb jan\u00eb plot\u00ebsisht t\u00eb gatshme mund t\u00eb shtyhet deri n\u00eb versionin e ardhsh\u00ebm zyrtar t\u00eb Ansible Engine. Deri s\u00eb fundmi, p\u00ebrdoruesit p\u00ebrfundimtar\u00eb kishin vet\u00ebm nj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb marr\u00eb p\u00ebrmbajtje t\u00eb re Ansible \u2013 s\u00eb bashku me versionin e ri t\u00eb Ansible Engine.<\/p>\n

\"Ansible:
\n
\nP\u00ebr t\u00eb leht\u00ebsuar k\u00ebt\u00eb situat\u00eb, komuniteti Ansible ka filluar t\u00eb punoj\u00eb mbi variante m\u00eb fleksibile p\u00ebr krijimin dhe marrjen e p\u00ebrmbajtjes.
\n<\/a><\/noindex><\/p>\n

Red Hat Ansible Engine 2.8: n\u00eb rrug\u00ebn drejt metodave t\u00eb reja t\u00eb p\u00ebrpunimit t\u00eb p\u00ebrmbajtjes Ansible<\/h3>\n

\nN\u00eb p\u00ebrgjigje t\u00eb k\u00ebrkesave t\u00eb p\u00ebrdoruesve, Ansible Engine 2.8 sjell ndryshime n\u00eb trajtimin e p\u00ebrmbajtjes, q\u00eb nuk \u00ebsht\u00eb pjes\u00eb e l\u00ebshimit zyrtar.<\/b>K\u00ebto ndryshime do t\u00eb lejojn\u00eb realizimin e nj\u00eb m\u00ebnyre t\u00eb re p\u00ebr t'u ofruar p\u00ebrmbajtje p\u00ebrdoruesve, e cila nuk do t\u00eb varet nga mb\u00ebshtet\u00ebsit e Ansible n\u00eb menaxhimin e p\u00ebrmbajtjes dhe kodit t\u00eb platform\u00ebs vet\u00eb.<\/p>\n

Pritet q\u00eb n\u00eb l\u00ebshimet e ardhshme, Krijuesit (Creators) e p\u00ebrmbajtjes do t\u00eb jen\u00eb n\u00eb gjendje ta ofrojn\u00eb at\u00eb n\u00eb form\u00ebn e pakove speciale, t\u00eb njohura si Koleksione (Collection), t\u00eb cilat do t\u00eb instalohen n\u00eb vendin p\u00ebrkat\u00ebs p\u00ebr ekzekutim n\u00eb nodin kryesor Ansible (control node) ose n\u00eb nodin e menaxhuar (managed node). Krijuesi i koleksioneve do t\u00eb specifikoj\u00eb detajet e ekzekutimit brenda paket\u00ebs duke p\u00ebrdorur role dhe playbook-e. Fal\u00eb k\u00ebtyre ndryshimeve t\u00eb p\u00ebrmendura n\u00eb Ansible Engine, koleksionet do t\u00eb b\u00ebhen nj\u00eb nga mjetet q\u00eb do t\u00eb ndihmojn\u00eb p\u00ebr t\u00eb lidhur l\u00ebshimin e p\u00ebrmbajtjes me l\u00ebshimin e versioneve zyrtare t\u00eb Ansible Engine.<\/b>.<\/p>\n

Struktura e re Become<\/h4>\n

\nStruktura Become \u00ebsht\u00eb shfaqur q\u00eb prej nj\u00eb koh\u00eb, por duke filluar nga versioni 2.8, fjala BECOME p\u00ebrdoret si standard n\u00eb Ansible Engine p\u00ebr t\u00eb k\u00ebrkuar fjal\u00ebkalimin gjat\u00eb rritjes s\u00eb privilegjeve (privilegje sudo n\u00eb sistemet *nix ose modalitetin enable n\u00eb pajisjet rrjet\u00eb). Me fjal\u00eb t\u00eb tjera, tani BECOME \u00ebsht\u00eb nj\u00eb mjet standard p\u00ebr rritjen e fuqis\u00eb q\u00eb merret vet\u00eb me sistemin e synuar.<\/p>\n

Ja si duket nj\u00eb shembull i p\u00ebrdorimit t\u00eb tij:<\/p>\n

ansible-playbook --become --ask-become-pass site.yml\nBECOME password:\n<\/code><\/pre>\n
\nP\u00ebr m\u00eb tep\u00ebr, Ansible Engine 2.8 ka sjell\u00eb nj\u00eb plugin BECOME, i cili punon si doas n\u00eb Linux dhe si runas n\u00eb Windows dhe lejon kryerjen e veprimeve n\u00eb em\u00ebr t\u00eb nj\u00eb p\u00ebrdoruesi t\u00eb caktuar. P\u00ebr rritjen e privilegjeve n\u00eb pajisjet rrjet, p\u00ebrdoret plugin-i become enable.<\/p>\n
K\u00ebrkimi i interpretuesit Python<\/h4>\n
\nNdoshta keni hasur nj\u00eb gabim t\u00eb till\u00eb:<\/p>\n
\/usr\/bin\/python: bad interpreter: No such file or directory\n<\/code><\/pre>\n
\nKjo \u00ebsht\u00eb p\u00ebr shkak se n\u00eb versionet e m\u00ebparshme t\u00eb Ansible Engine, supozohej se interpretuesi kryesor (ai q\u00eb p\u00ebrdoret si standard) ndodhej n\u00eb dosjen \/usr\/bin\/python. Duke filluar nga versioni 2.8, Ansible k\u00ebrkon interpretuesin n\u00eb \u00e7do sistem t\u00eb synuar, duke filluar nga p\u00ebrputhja me tabel\u00ebn e rrug\u00ebve dhe emrave t\u00eb skedar\u00ebve ekzekutues t\u00eb interpretuesit kryesor Python n\u00eb shp\u00ebrndarje t\u00eb ndryshme, dhe m\u00eb pas duke p\u00ebrdorur lista t\u00eb renditura t\u00eb interpretuesve rezerv\u00eb (fallback list), detajet m\u00eb t\u00eb plota gjenden n\u00eb Udh\u00ebzimet p\u00ebr portimin n\u00eb Ansible 2.8.<\/a><\/noindex>.<\/p>\n
Skedar\u00ebt e Retry nuk krijohen m\u00eb si standard.<\/h4>\n
\nKeni k\u00ebrkuar me koh\u00eb skedar\u00ebt .retry n\u00eb disk? N\u00ebse e keni p\u00ebrdorur Ansible p\u00ebr nj\u00eb koh\u00eb t\u00eb gjat\u00eb, ata patjet\u00ebr jan\u00eb shum\u00eb dhe vet\u00ebm z\u00ebn\u00eb hap\u00ebsir\u00eb t\u00eb vlefshme. Duke filluar nga versioni 2.8, Ansible Engine nuk krijon m\u00eb k\u00ebta skedar\u00eb si standard (\u00e7ka mund t\u00eb anulohet duke redaktuar skedarin ansible.cfg).<\/p>\n
Rimarrja e Play e p\u00ebrmir\u00ebsuar<\/h4>\n
\nNxjerrje nga Udh\u00ebzimet p\u00ebr portimin n\u00eb Ansible 2.8<\/a><\/noindex>:<\/p>\n
Rimarrja e Play tani llogarit detyrat (tasks) me statusin ignored dhe rescued, si dhe ok, changed, unreachable, failed dhe skipped, fal\u00eb dy num\u00ebruesve t\u00eb rinj t\u00eb statistik\u00ebs n\u00eb callback plugin-in default. Detyrat q\u00eb d\u00ebshtuan, p\u00ebr t\u00eb cilat \u00ebsht\u00eb vendosur flagu ignore_errors: yes, llogariten si ignored. Detyrat q\u00eb d\u00ebshtuan, p\u00ebr t\u00eb cilat m\u00eb pas \u00ebsht\u00eb punuar seksioni rescue, llogariten si rescued. Vini re se, ndryshe nga versionet e m\u00ebparshme t\u00eb Ansible, detyrat rescued tani nuk llogariten m\u00eb si d\u00ebshtim.<\/p><\/blockquote>\n
\nDhe n\u00eb tabel\u00ebn e Rimarrjes s\u00eb Play pas p\u00ebrfundimit t\u00eb playbook, p\u00ebr host\u00ebt jan\u00eb shtuar kolona t\u00eb reja skipped, rescued dhe ignored:<\/p>\n
\"Ansible:<\/p>\n
Re dhe kontejner\u00eb<\/h4>\n
\nN\u00eb versionin 2.8 jan\u00eb implementuar p\u00ebrmir\u00ebsime dhe shtesa n\u00eb modulet e nubeve dhe kontejner\u00ebve p\u00ebr pun\u00ebn me Amazon Web Services, Microsoft Azure, Google Cloud, Digital Ocean, podman<\/a><\/noindex> dhe kubevirt.<\/a><\/noindex>Vlen t\u00eb theksohet gjithashtu se skedar\u00ebt TOML tani mund t\u00eb p\u00ebrdoren si burim inventari.<\/p>\n
Paramiko<\/h4>\n
\nA po p\u00ebrdorni Red Hat Ansible Network Automation? Ansible Engine 2.8 nuk p\u00ebrmban m\u00eb paramiko dhe nuk varet nga ai. Si standard, Ansible Engine p\u00ebrdor ssh. N\u00ebse ju nevojitet paramiko, mund ta instaloni me komand\u00ebn pip install paramiko.<\/p>\n
N\u00ebse ju nevojitet mb\u00ebshtetje p\u00ebr p\u00ebrdorimin e paramiko n\u00eb kuad\u00ebr t\u00eb abonimit Red Hat, ju lutemi referojuni artikullit n\u00eb baz\u00ebn e njohurive. Paketa Paramiko mungon pas instalimeve t\u00eb reja t\u00eb Ansible Engine.<\/a><\/noindex>.<\/p>\n
K\u00ebshtu, versioni i ri i Red Hat Ansible Engine u pasurua me nj\u00eb list\u00eb t\u00eb r\u00ebnd\u00ebsishme p\u00ebrmir\u00ebsimesh dhe ndryshimesh, me t\u00eb cilat mund t\u00eb njiheni m\u00eb n\u00eb detaje. k\u00ebtu<\/a><\/noindex>.<\/b><\/p>\n
Red Hat Ansible Tower 3.5: m\u00eb shum\u00eb automatizim<\/h3>\n
\nQ\u00eb nga fundi i majit, versioni i ri Red Hat Ansible Tower 3.5 \u00ebsht\u00eb n\u00eb dispozicion, duke ofruar disa p\u00ebrmir\u00ebsime t\u00eb r\u00ebnd\u00ebsishme p\u00ebr automatizim, p\u00ebr t\u00eb cilat do t\u00eb flasim, n\u00ebse ende nuk keni pasur mund\u00ebsin\u00eb t'i provoni vet\u00eb.<\/p>\n
Pra, fillimisht ky\u00e7et kryesore:<\/p>\n