block<\/code> etj. Sa m\u00eb mir\u00eb ta njihni ansible, aq m\u00eb shum\u00eb nuanca do t\u00eb jeni n\u00eb gjendje t\u00eb p\u00ebrmendni p\u00ebr nj\u00eb zgjidhje \"t\u00eb zgjuar\". Dhe nj\u00eb zgjidhje e thjesht\u00eb - p\u00ebrdorimi i ndarjes natyrore midis pre\/roles\/post - nuk shkakton nuanca.<\/p>\n<\/p>\n
Dhe, kthehemi te 'foo' yn\u00eb. Ku duhet ta vendosim? N\u00eb pre, post apo n\u00eb roles? \u00cbsht\u00eb e qart\u00eb, kjo varet nga n\u00ebse na nevojiten rezultatet e pun\u00ebs s\u00eb handlerit p\u00ebr foo. N\u00ebse jo, at\u00ebher\u00eb foo nuk ka nevoj\u00eb t\u00eb vendoset as n\u00eb pre, as n\u00eb post - k\u00ebto seksione kan\u00eb nj\u00eb kuptim t\u00eb ve\u00e7ant\u00eb - ekzekutimi i detyrave para dhe pas mas\u00ebs kryesore t\u00eb kodit.<\/p>\n
<\/p>\n
Tani, p\u00ebrgjigjja p\u00ebr pyetjen \"rol apo detyr\u00eb\" p\u00ebrfshin at\u00eb q\u00eb tashm\u00eb ekziston n\u00eb play - n\u00ebse atje ka tasks, at\u00ebher\u00eb duhet ta shkruani n\u00eb tasks. N\u00ebse ka roles, duhet t\u00eb krijoni nj\u00eb rol (edhe n\u00ebse \u00ebsht\u00eb nga nj\u00eb detyr\u00eb). Ju kujtoj, tasks dhe roles nuk p\u00ebrdoren nj\u00ebkoh\u00ebsisht.<\/p>\n
<\/p>\n
Kuptimi i bazave t\u00eb Ansible ofron p\u00ebrgjigje t\u00eb arsyeshme p\u00ebr, duksh\u00ebm, pyetje me shije.<\/p>\n
<\/p>\n
Detyrat dhe rolet (pjesa e dyt\u00eb)<\/h1>\n <\/p>\n
Tani, le t\u00eb diskutojm\u00eb situat\u00ebn kur vet\u00ebm filloni t\u00eb shkruani nj\u00eb playbook. Ju nevojitet t\u00eb b\u00ebni foo, bar dhe baz. A jan\u00eb k\u00ebto tri detyra, nj\u00eb rol apo tri role? P\u00ebr t\u00eb p\u00ebrmbledhur pyetjen: n\u00eb \u00e7far\u00eb momenti duhet t\u00eb filloni t\u00eb shkruani role? \u00c7far\u00eb ka kuptim t\u00eb shkruani role, kur mund t\u00eb shkruani detyra?\u2026 \u00c7far\u00eb \u00ebsht\u00eb nj\u00eb rol?<\/p>\n
<\/p>\n
Nj\u00eb nga gabimet m\u00eb t\u00eb m\u00ebdha (k\u00ebt\u00eb kam p\u00ebrmendur tashm\u00eb) \u00ebsht\u00eb t\u00eb mendosh se roli \u00ebsht\u00eb si nj\u00eb funksion n\u00eb bibliotek\u00ebn e nj\u00eb programi. Si duket p\u00ebrshkrimi i p\u00ebrgjithsh\u00ebm i nj\u00eb funksioni? Ai merr argumente si input, nd\u00ebrvepron me side causes, b\u00ebn side effects, kthen nj\u00eb vler\u00eb.<\/p>\n
<\/p>\n
Tani, duhet t'i kushtoni v\u00ebmendje. \u00c7far\u00eb nga kjo mund t\u00eb b\u00ebhet n\u00eb rol? T\u00eb therras\u00eb efekte an\u00ebsore - gjithmon\u00eb, kjo \u00ebsht\u00eb thelbi i gjitha Ansible - t\u00eb b\u00ebni efekte an\u00ebsore. T\u00eb keni shkaqe an\u00ebsore? Elementar. Por me \"t\u00eb kaloni nj\u00eb vler\u00eb dhe t'i ktheni at\u00eb\" - k\u00ebtu nuk \u00ebsht\u00eb k\u00ebshtu. S\u00eb pari, nuk mund t\u00eb kaloni nj\u00eb vler\u00eb n\u00eb rol. Mund t\u00eb vendosni nj\u00eb variab\u00ebl globale me nj\u00eb jet\u00ebgjat\u00ebsi t\u00eb barabart\u00eb me play n\u00eb seksionin vars p\u00ebr rolin. Mund t\u00eb vendosni nj\u00eb variab\u00ebl globale me nj\u00eb jet\u00ebgjat\u00ebsi n\u00eb play brenda rolit. Ose madje me nj\u00eb jet\u00ebgjat\u00ebsi t\u00eb playbook (set_fact<\/code>\/register<\/code>). Por nuk mund t\u00eb keni \"variab\u00ebl lokale\". Nuk mund t\u00eb \"pranoni nj\u00eb vler\u00eb\" dhe \"ta ktheni at\u00eb\".<\/p>\n<\/p>\n
Nga kjo p\u00ebrfundon se: nuk mund t\u00eb shkruash di\u00e7ka n\u00eb ansible dhe t\u00eb mos e th\u00ebrras\u00ebsh side effects. Ndryshimi i variablave globale \u00ebsht\u00eb gjithmon\u00eb nj\u00eb side effect p\u00ebr funksionin. N\u00eb Rust, p\u00ebr shembull, ndryshimi i nj\u00eb varianti global \u00ebsht\u00eb unsafe<\/code>. N\u00eb Ansible, metoda e vetme p\u00ebr t\u00eb ndikuar n\u00eb vlerat p\u00ebr rolin \u00ebsht\u00eb. Vini re fjal\u00ebt e p\u00ebrdorura: jo \"t\u00eb kaloni vler\u00ebn n\u00eb rol\", por \"t\u00eb ndryshoni vlerat q\u00eb p\u00ebrdor roli\". Nuk ka izolim midis rolieve. Nuk ka izolim midis detyrave dhe rolieve.<\/p>\n<\/p>\n
Pra, n\u00eb p\u00ebrfundim: roli \u00ebsht\u00eb jo nj\u00eb funksion<\/strong>.<\/p>\n<\/p>\n
\u00c7far\u00eb \u00ebsht\u00eb e mir\u00eb n\u00eb rolin? S\u00eb pari, roli ka vlera t\u00eb paracaktuara (\/default\/main.yaml<\/code>), s\u00eb dyti, roli ka katalog\u00eb shtes\u00eb p\u00ebr ruajtjen e skedave.<\/p>\n<\/p>\n
\u00c7far\u00eb \u00ebsht\u00eb e mir\u00eb n\u00eb vlerat e paracaktuara? Ato jan\u00eb, q\u00eb n\u00eb piramid\u00ebn e Maslow-it, nj\u00eb tabel\u00eb shum\u00eb t\u00eb \u00e7uditshme t\u00eb prioriteteve t\u00eb variablave n\u00eb Ansible, defaultet e rolit jan\u00eb m\u00eb pak t\u00eb prioritizuara (p\u00ebrve\u00e7 parametrave t\u00eb linj\u00ebs s\u00eb komand\u00ebs s\u00eb Ansible). Kjo do t\u00eb thot\u00eb se, n\u00ebse duhet t'i ofroni vlera t\u00eb paracaktuara dhe t\u00eb mos shqet\u00ebsoheni se ato do t\u00eb z\u00ebvend\u00ebsojn\u00eb vlerat nga inventari ose variablat grupor, at\u00ebher\u00eb defaultet e rolit jan\u00eb vendi i vet\u00ebm i duhur p\u00ebr ju. (Po, pak po g\u00ebnjej \u2014 ka edhe |d(your_default_here)<\/code>, por n\u00ebse flasim p\u00ebr vendet statike \u2014 at\u00ebher\u00eb vet\u00ebm defaultet e rolit).<\/p>\n<\/p>\n
\u00c7far\u00eb tjet\u00ebr \u00ebsht\u00eb e mir\u00eb n\u00eb role? Ato kan\u00eb katalog\u00ebt e tyre. K\u00ebto jan\u00eb katalog\u00eb p\u00ebr variablat, si konstant\u00eb (pra, t\u00eb llogaritur p\u00ebr rolin), ashtu dhe p\u00ebr dinamik\u00eb (ka nj\u00eb model ose anti-model t\u00eb till\u00eb \u2014 include_vars<\/code> m\u00eb bashk\u00eb me {{ ansible_distribution }}-{{ ansible_distribution_major_version }}.yml<\/code>.). K\u00ebto jan\u00eb katalog\u00eb p\u00ebr files\/<\/code>, templates\/<\/code>. Gjithashtu, ato lejojn\u00eb q\u00eb rolet t\u00eb ken\u00eb modulat dhe plug-in-at e tyre (library\/<\/code>). Por, n\u00eb krahasim me detyrat n\u00eb playbook (e cila gjithashtu mund t\u00eb ket\u00eb t\u00eb gjitha k\u00ebto), p\u00ebrfitimi k\u00ebtu \u00ebsht\u00eb vet\u00ebm se skedar\u00ebt nuk jan\u00eb mbledhur n\u00eb nj\u00eb grumbull, por n\u00eb disa grumbuj t\u00eb ve\u00e7ant\u00eb.<\/p>\n<\/p>\n
Nj\u00eb detaj tjet\u00ebr: mund t\u00eb p\u00ebrpiqeni t\u00eb b\u00ebni role q\u00eb do t\u00eb jen\u00eb t\u00eb disponueshme p\u00ebr rip\u00ebrdorim (p\u00ebrmes galaxy). Pas shfaqjes s\u00eb koleksioneve, shp\u00ebrndarja e rol\u00ebve mund t\u00eb konsiderohet pothuajse e harxhuar.<\/p>\n
<\/p>\n
K\u00ebshtu, rolet kan\u00eb dy ve\u00e7ori t\u00eb r\u00ebnd\u00ebsishme: ato kan\u00eb defaultet (nj\u00eb ve\u00e7ori unike) dhe lejojn\u00eb strukturimin e kodit.<\/p>\n
<\/p>\n
Duke u kthyer n\u00eb pyetjen fillestare: kur t\u00eb b\u00ebni detyra dhe kur t\u00eb b\u00ebni role? Detyrat n\u00eb playbook zakonisht p\u00ebrdoren ose si \"ngjis\u00eb\" para\/pas rolieve, ose si nj\u00eb element ndihm\u00ebs (at\u00ebher\u00eb n\u00eb kod nuk duhet t\u00eb ket\u00eb rol). Nj\u00eb grumbull detyrash t\u00eb zakonshme t\u00eb p\u00ebrziera me role \u00ebsht\u00eb padyshim nj\u00eb papast\u00ebrti. Duhet t\u00eb ndiqni nj\u00eb stil t\u00eb caktuar \u2014 ose detyra, ose role. Role ofrojn\u00eb ndarje entitetesh dhe default, detyrat lejojn\u00eb leximin m\u00eb t\u00eb shpejt\u00eb t\u00eb kodit. Zakonisht, n\u00eb rol d\u00ebrgohen kod m\u00eb \"stacionar\" (t\u00eb r\u00ebnd\u00ebsish\u00ebm dhe t\u00eb nd\u00ebrlikuar), dhe n\u00eb stilin e detyrave shkruhen skenar\u00eb ndihm\u00ebs.<\/p>\n
<\/p>\n
Ka ekziston mund\u00ebsia p\u00ebr t\u00eb b\u00ebr\u00eb import_role si detyr\u00eb, por n\u00ebse e shkruani k\u00ebt\u00eb, b\u00ebhuni gati p\u00ebr nj\u00eb shpjegim p\u00ebr ndjenj\u00ebn tuaj estetike, pse d\u00ebshironi ta b\u00ebni k\u00ebt\u00eb.<\/p>\n
<\/p>\n
Nj\u00eb lexues i bezdissh\u00ebm mund t\u00eb thot\u00eb se rolet mund t\u00eb importojn\u00eb role, dhe rolet mund t\u00eb ken\u00eb var\u00ebsi p\u00ebrmes galaxy.yml, dhe ka gjithashtu di\u00e7ka t\u00eb frikshme dhe t\u00eb tmerrshme include_role<\/code> \u2014 ju kujtoj, ne po p\u00ebrmir\u00ebsojm\u00eb aft\u00ebsit\u00eb n\u00eb Ansible-n themelor, e jo n\u00eb gimnasitik\u00ebn ritmike.<\/p>\n<\/p>\n
Handlerat dhe detyrat<\/h1>\n <\/p>\n
Le t\u00eb diskutojm\u00eb p\u00ebr nj\u00eb tjet\u00ebr gj\u00eb t\u00eb dukshme: handlerat. Aft\u00ebsia p\u00ebr t'i p\u00ebrdorur ato si\u00e7 duhet \u00ebsht\u00eb thuajse nj\u00eb art. Cila \u00ebsht\u00eb diferenca midis nj\u00eb handleri dhe nj\u00eb detyr\u00eb?<\/p>\n
<\/p>\n
Ata q\u00eb po e kujtojm\u00eb themelin, ja nj\u00eb shembull:<\/p>\n
<\/p>\n
- hosts: group1\n tasks:\n - foo:\n notify: handler1\n handlers:\n - name: handler1\n bar:<\/code><\/pre>\n<\/p>\n
N\u00eb rol, handler\u00ebt q\u00ebndrojn\u00eb n\u00eb rolename\/handlers\/main.yaml. Handler\u00ebt ndahen midis t\u00eb gjith\u00eb pjes\u00ebmarr\u00ebsve n\u00eb play: pre\/post_tasks mund t\u00eb th\u00ebrrasin handler\u00ebt e rolieve, dhe roli mund t\u00eb th\u00ebrras\u00eb handler\u00ebt nga play. Megjithat\u00eb, thirrjet \"me kalim nd\u00ebrmjet rolieve\" t\u00eb handler\u00ebve shkaktojn\u00eb nj\u00eb \"wtf\" shum\u00eb m\u00eb t\u00eb madh se sa p\u00ebrs\u00ebritja e nj\u00eb handleri trivial. (Nj\u00eb tjet\u00ebr element i praktikave m\u00eb t\u00eb mira \u00ebsht\u00eb t\u00eb p\u00ebrpiqeni t\u00eb mos b\u00ebni p\u00ebrs\u00ebritje t\u00eb emrave t\u00eb handler\u00ebve).<\/p>\n
<\/p>\n
Dallimi kryesor \u00ebsht\u00eb se nj\u00eb detyr\u00eb ekzekutohet (ideompatentisht) gjithmon\u00eb (plus\/minus etiketat dhe when<\/code>), kurse handleri ekzekutohet sipas ndryshimit t\u00eb gjendjes (notify vepron vet\u00ebm n\u00ebse ka pasur ndryshim). \u00c7far\u00eb do t'i sjell\u00eb kjo? P.sh., se n\u00eb nj\u00eb ekzekutim t\u00eb ri, n\u00ebse nuk ka qen\u00eb ndryshimi, at\u00ebher\u00eb nuk do t\u00eb ndodhi as handleri. Dhe pse mund t\u00eb ndodh\u00eb q\u00eb na nevojitet t\u00eb ekzekutojm\u00eb handlerin kur s\u2019ka pasur nj\u00eb ndryshim n\u00eb detyr\u00ebn ndihmuese? P.sh., sepse di\u00e7ka ka marr\u00eb fund t\u00ebjk dhe ka pasur ndryshim, por ekzekutimi nuk arriti n\u00eb handler. P.sh., sepse rrjeti ishte temporalisht i nd\u00ebrprer\u00eb. Konfigurimi u ndryshua, sh\u00ebrbimi nuk u rilansua. N\u00eb ekzekutimin e ardhsh\u00ebm, konfigurimi tashm\u00eb nuk ndryshon, dhe sh\u00ebrbimi mbetet me versionin e vjet\u00ebr t\u00eb konfigurimit.<\/p>\n<\/p>\n
Situata me konfigurimin nuk \u00ebsht\u00eb e zgjidhshme (m\u00eb sakt\u00eb, mund t\u00eb shpikni nj\u00eb protokoll t\u00eb ve\u00e7ant\u00eb p\u00ebr rinisje me bandera skedari etj., por kjo nuk \u00ebsht\u00eb m\u00eb 'ansible temel' n\u00eb asnj\u00eb form\u00eb). Megjithat\u00eb, ka nj\u00eb histori tjet\u00ebr t\u00eb zakonshme: ne kemi instaluar nj\u00eb aplikacion, e kemi regjistruar at\u00eb .service<\/code>-sked\u00ebn, dhe tani duam ta daemon_reload<\/code> dhe state=started<\/code>. Dhe vendi natyror p\u00ebr k\u00ebt\u00eb duket si handler. Por n\u00ebse e b\u00ebni at\u00eb nj\u00eb detyr\u00eb n\u00eb fund t\u00eb list\u00ebs s\u00eb detyrave apo nj\u00eb rol, at\u00ebher\u00eb ai do t\u00eb ekzekutohet idempotentisht \u00e7do her\u00eb. Edhe n\u00ebse playbook-u d\u00ebshton n\u00eb mes. Kjo nuk zgjidh problemin e restarted (nuk mund t\u00eb b\u00ebni nj\u00eb detyr\u00eb me atributin restarted, pasi do t\u00eb humbas\u00eb idempotent\u00ebsin\u00eb), por me siguri duhet t\u00eb b\u00ebni state=started, stabiliteti i p\u00ebrgjithsh\u00ebm i playbook-\u00ebve rritet, pasi zvog\u00eblohet numri i lidhjeve dhe gjendjes dinamike.<\/p>\n<\/p>\n
Nj\u00eb tjet\u00ebr pron\u00eb pozitive e handlerit \u00ebsht\u00eb se ai nuk e mbush output-in. Nuk kishte ndryshime \u2014 nuk ka skip ose ok n\u00eb output \u2014 m\u00eb e leht\u00eb p\u00ebr t'u lexuar. Po ashtu, \u00ebsht\u00eb nj\u00eb pron\u00eb negative \u2014 n\u00ebse gjeni nj\u00eb gabim n\u00eb nj\u00eb task q\u00eb ekzekutohet linear n\u00eb kalimin e par\u00eb, handler\u00ebt do t\u00eb ekzekutohen vet\u00ebm kur ka ndryshime, pra n\u00eb disa kushte \u2014 shum\u00eb rrall\u00eb. P\u00ebr shembull, hera e par\u00eb n\u00eb jet\u00ebn time pas pes\u00eb vjet\u00ebsh. Dhe, sigurisht, atje do t\u00eb ket\u00eb nj\u00eb gabim n\u00eb em\u00ebr dhe gjith\u00e7ka do t\u00eb prishen. Dhe her\u00ebn e dyt\u00eb nuk mund t'i nisni \u2014 nuk ka ndryshime.<\/p>\n
<\/p>\n
P\u00ebrve\u00e7 k\u00ebsaj, duhet t\u00eb flasim p\u00ebr arritshm\u00ebrin\u00eb e variablave. P\u00ebr shembull, n\u00ebse b\u00ebni notify p\u00ebr nj\u00eb detyr\u00eb me cik\u00ebl, \u00e7far\u00eb do t\u00eb ket\u00eb n\u00eb variabla? Mund t\u00eb arrini t\u00eb kuptoni n\u00eb m\u00ebnyr\u00eb analitike, por nuk \u00ebsht\u00eb gjithmon\u00eb triviale, sidomos n\u00ebse variablat vijn\u00eb nga vende t\u00eb ndryshme.<\/p>\n
<\/p>\n
K\u00ebshtu q\u00eb handler-\u00ebt jan\u00eb shum\u00eb m\u00eb pak t\u00eb dobish\u00ebm dhe shum\u00eb m\u00eb problematik\u00eb se sa duket. N\u00ebse mund t\u00eb shkruhet di\u00e7ka bukur (pa truke) pa handler-a, \u00ebsht\u00eb m\u00eb mir\u00eb ta b\u00ebni pa ta. N\u00ebse nuk ia del dot bukur \u2014 \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb keni me ta.<\/p>\n
<\/p>\n
Lexuesi i k\u00ebndsh\u00ebm e v\u00ebren drejt se nuk e kemi diskutuar listen<\/code>, q\u00eb handler mund t\u00eb th\u00ebrras\u00eb notify p\u00ebr nj\u00eb handler tjet\u00ebr, q\u00eb handler mund t\u00eb p\u00ebrmbaj\u00eb import_tasks (i cili mund t\u00eb b\u00ebj\u00eb include_role me with_items), q\u00eb sistemi i handler-\u00ebve n\u00eb Ansible \u00ebsht\u00eb Turing-p\u00ebrmbush\u00ebs, q\u00eb handler-\u00ebt nga include_role merren me kuriozitet me handler-\u00ebt nga play etj. \u2014 e gjith\u00eb kjo sigurisht nuk \u00ebsht\u00eb \"themelore\").<\/p>\n<\/p>\n
Megjithat\u00eb, ka nj\u00eb \u00e7\u00ebshtje t\u00eb caktuar WTF, q\u00eb n\u00eb fakt \u00ebsht\u00eb nj\u00eb ve\u00e7ori, dhe q\u00eb duhet mbajtur mend. N\u00ebse keni nj\u00eb detyr\u00eb q\u00eb ekzekutohet me delegate_to<\/code> dhe ka notify, at\u00ebher\u00eb handler-i p\u00ebrkat\u00ebs ekzekutohet pa delegate_to<\/code>, dometh\u00ebn\u00eb n\u00eb hostin ku \u00ebsht\u00eb caktuar play. (Megjith\u00ebse handler-i, natyrisht, mund t\u00eb ket\u00eb delegate_to<\/code> po ashtu).<\/p>\n<\/p>\n
Ve\u00e7an\u00ebrisht, dua t\u00eb them disa fjal\u00eb p\u00ebr rolet e rip\u00ebrdorshme. Para se t\u00eb shfaqeshin koleksionet, kishte iden\u00eb se mund t\u00eb b\u00ebhen role universale q\u00eb mund t\u00eb ansible-galaxy install<\/code> Dhe shkoi. Funksionon n\u00eb t\u00eb gjitha OS-t\u00eb p\u00ebr t\u00eb gjitha rastet n\u00eb \u00e7do situat\u00eb. K\u00ebshtu, mendimi im \u00ebsht\u00eb: kjo nuk funksionon. \u00c7do rol me mb\u00ebshtetje p\u00ebr 100500 raste \u00ebsht\u00eb e d\u00ebnuar t\u00eb p\u00ebrballet me thell\u00ebsit\u00eb e problemeve t\u00eb skenar\u00ebve t\u00eb raritetit. Ato mund t\u00eb mbyllen me testime masive, por si me \u00e7do testim, ose keni nj\u00eb produkt t\u00eb dekartuar t\u00eb vlerave hyr\u00ebse dhe nj\u00eb funksion total, ose keni \"mbuluar skenare t\u00eb ve\u00e7ant\u00eb\". Mendimi im \u00ebsht\u00eb se \u00ebsht\u00eb shum\u00eb m\u00eb mir\u00eb n\u00ebse roli \u00ebsht\u00eb linear (kompleksiteti ciklomatk 1). include_vars<\/code>, mb\u00ebshtetja p\u00ebr 100500 rast\u00eb \u00ebsht\u00eb e destinuar p\u00ebr humnera bug-esh corner case. Mund t\u00eb mbyllen p\u00ebrmes testimeve masive, por si p\u00ebr \u00e7do testim, ose keni nj\u00eb produkt t\u00eb produktit dekartian t\u00eb vlerave hyr\u00ebse dhe nj\u00eb funksion total, ose keni \"mbuluar skenar\u00eb t\u00eb ve\u00e7ant\u00eb\". Mendimi im \u2014 \u00ebsht\u00eb m\u00eb mir\u00eb n\u00ebse roli \u00ebsht\u00eb linear (kompleksiteti ciklomatik 1).<\/p>\n<\/p>\n
Sa m\u00eb pak if-\u00eb (t\u00eb dukshme ose deklaruese \u2014 n\u00eb form\u00ebn when<\/code> p\u00ebr grupin e variablave), aq m\u00eb mir\u00eb \u00ebsht\u00eb roli. Ndonj\u00ebher\u00eb duhet t\u00eb b\u00ebni ndarjen, por, do ta p\u00ebrs\u00ebris, sa m\u00eb pak t\u00eb jen\u00eb, aq m\u00eb mir\u00eb. Pra, duket se nj\u00eb rol i mir\u00eb me galaxy (funksionon!) me shum\u00eb include_vars<\/code> mund t\u00eb jet\u00eb m\u00eb pak i preferuar se \"rolin tuaj\" me pes\u00eb detyra. Momenti kur roli me galaxy \u00ebsht\u00eb m\u00eb mir\u00eb - kur filloni t\u00eb shkruani di\u00e7ka. Momenti kur b\u00ebhet m\u00eb keq - kur di\u00e7ka prishet, dhe keni dyshimin se \u00ebsht\u00eb p\u00ebr shkak t\u00eb \"rolit me galaxy\". E hapni, dhe atje jan\u00eb pes\u00eb p\u00ebrfshirje, tet\u00eb lista detyrash dhe nj\u00eb grumbull when<\/code> mund t\u00eb jet\u00eb m\u00eb pak e preferuar se nj\u00eb rol \"i vet\u00eb\" me pes\u00eb detyra. Momentin kur roli me galaxy \u00ebsht\u00eb m\u00eb i mir\u00eb \u2014 kur filloni t\u00eb shkruani di\u00e7ka. Momentin kur ai b\u00ebhet m\u00eb i keq \u2014 kur di\u00e7ka prishet, dhe keni dyshimin se \u00ebsht\u00eb p\u00ebr shkak t\u00eb \"rolit me galaxy\". E hapni at\u00eb, dhe atje ka pes\u00eb inkluziones, tet\u00eb lista detyrash dhe nj\u00eb grumbull when<\/code>\u2018\u2026 Dhe duhet t\u00eb kuptohet. N\u00eb vend t\u00eb 5 detyrave n\u00eb nj\u00eb list\u00eb linear, ku nuk ka asgj\u00eb p\u00ebr t'u prishur.<\/p>\n<\/p>\n
Pak p\u00ebr inventarin, variablat grupore, plugin-in host_group_vars, hostvars. Si t\u00eb lidhni spaghetti n\u00eb nj\u00eb nyje Gordiane. Shkala dhe prioriteti i variablave, modeli i memories Ansible. \"At\u00ebher\u00eb ku duhet t\u00eb ruhet emri i p\u00ebrdoruesit p\u00ebr baz\u00ebn e t\u00eb dh\u00ebnave?\".<\/h1>\n <\/p>\n
\nPak p\u00ebr inventarin, variablat grupore, plugin host_group_vars, hostvars. Si t\u00eb lidhni spaghetti me nyj\u00ebn Gordiane. Scope dhe precedence e variablave, modeli i memories n\u00eb Ansible. \"Por ku duhet ta ruaj emrin e p\u00ebrdoruesit p\u00ebr baz\u00ebn e t\u00eb dh\u00ebnave?\".<\/li>\n \u2014 nosql notype nosense plastelin\u00eb t\u00eb but\u00eb. \u00cbsht\u00eb kudo, madje aty ku nuk e prisni. Pak p\u00ebr<\/code> !!unsafe dhe yaml t\u00eb shijsh\u00ebm.<\/code> Un\u00eb b\u00ebj shum\u00eb rishikime p\u00ebr kodin e t\u00eb tjer\u00ebve n\u00eb Ansible dhe shkruaj shum\u00eb vet\u00eb.<\/li>\n<\/ul>\nBurimi: habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"\u042f \u0434\u0435\u043b\u0430\u044e \u043c\u043d\u043e\u0433\u043e \u0440\u0435\u0432\u044c\u044e \u0434\u043b\u044f \u0447\u0443\u0436\u043e\u0433\u043e \u043a\u043e\u0434\u0430 \u043d\u0430 \u0410\u043d\u0441\u0438\u0431\u043b \u0438 \u043c\u043d\u043e\u0433\u043e \u043f\u0438\u0448\u0443 \u0441\u0430\u043c. \u0412 \u0445\u043e\u0434\u0435 \u0430\u043d\u0430\u043b\u0438\u0437\u0430 \u043e\u0448\u0438\u0431\u043e\u043a (\u043a\u0430\u043a \u0447\u0443\u0436\u0438\u0445, \u0442\u0430\u043a \u0438 \u0441\u0432\u043e\u0438\u0445), \u0430 \u0442\u0430\u043a \u0436\u0435 \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u043e\u0433\u043e \u043a\u043e\u043b\u0438\u0447\u0435\u0441\u0442\u0432\u0430 \u0441\u043e\u0431\u0435\u0441\u0435\u0434\u043e\u0432\u0430\u043d\u0438\u0439, \u044f \u043f\u043e\u043d\u044f\u043b \u043e\u0441\u043d\u043e\u0432\u043d\u0443\u044e \u043e\u0448\u0438\u0431\u043a\u0443, \u043a\u043e\u0442\u043e\u0440\u0443\u044e \u0434\u043e\u043f\u0443\u0441\u043a\u0430\u044e\u0442 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u0438 \u0410\u043d\u0441\u0438\u0431\u043b\u0430 \u2014 \u043e\u043d\u0438 \u043b\u0435\u0437\u0443\u0442 \u0432 \u0441\u043b\u043e\u0436\u043d\u043e\u0435, \u043d\u0435 \u043e\u0441\u0432\u043e\u0438\u0432 \u0431\u0430\u0437\u043e\u0432\u043e\u0433\u043e. \u0414\u043b\u044f \u0438\u0441\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044f \u044d\u0442\u043e\u0439 \u0432\u0441\u0435\u043b\u0435\u043d\u0441\u043a\u043e\u0439 \u043d\u0435\u0441\u043f\u0440\u0430\u0432\u0435\u0434\u043b\u0438\u0432\u043e\u0441\u0442\u0438 \u044f \u0440\u0435\u0448\u0438\u043b \u043d\u0430\u043f\u0438\u0441\u0430\u0442\u044c \u0432\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0432 \u0410\u043d\u0441\u0438\u0431\u043b […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-87084","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t