{"id":34742,"date":"2019-10-31T22:00:10","date_gmt":"2019-10-31T19:00:10","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-chetvertaya-avtomatizatsiya-templejty\/"},"modified":"2019-10-31T22:00:10","modified_gmt":"2019-10-31T19:00:10","slug":"kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-chetvertaya-avtomatizatsiya-templejty","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-vzyat-setevuyu-infrastrukturu-pod-svoj-kontrol-glava-chetvertaya-avtomatizatsiya-templejty","title":{"rendered":"Si t\u00eb merrni kontrollin mbi infrastruktur\u00ebn tuaj rrjet\u00eb. Kapingta e kat\u00ebrt. Automatizimi. Shabllonet.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ky artikull \u00ebsht\u00eb i gjashti n\u00eb ciklin e artikujve \"Si t\u00eb kontrolloni infrastruktur\u00ebn tuaj rrjet\u00eb.\" P\u00ebrmbajtja e t\u00eb gjith\u00eb artikujve t\u00eb ciklit dhe lidhjet e tyre mund t\u00eb gjenden k\u00ebtu<\/a><\/noindex><\/i>.<\/p>\n

Dhe, pasi lan\u00eb disa tema pas, vendosa t\u00eb filloj nj\u00eb kapitull t\u00eb ri.<\/p>\n

Do t\u00eb kthehem te siguria m\u00eb von\u00eb. K\u00ebtu dua t\u00eb diskutoj nj\u00eb qasje t\u00eb thjesht\u00eb, por efektive, q\u00eb jam i sigurt se do t'i sh\u00ebrbej\u00eb shum\u00ebkujt n\u00eb nj\u00eb form\u00eb apo nj\u00eb tjet\u00ebr. Ky \u00ebsht\u00eb m\u00eb shum\u00eb nj\u00eb histori e shkurt\u00ebr se si automatizimi mund t\u00eb ndryshoj\u00eb jet\u00ebn e nj\u00eb inxhinieri. Do t\u00eb flasim p\u00ebr p\u00ebrdorimin e template-ve. N\u00eb fund do t\u00eb gjeni nj\u00eb list\u00eb t\u00eb projekteve t\u00eb mia, ku mund t\u00eb shihni se si funksionon gjith\u00e7ka e p\u00ebrshkruar k\u00ebtu.<\/p>\n

DevOps p\u00ebr rrjetin<\/h2>\n

\nKrijimi i konfigurimeve me skripta, p\u00ebrdorimi i GIT p\u00ebr kontrollin e ndryshimeve n\u00eb infrastruktur\u00ebn IT, ngarkimi i larg\u00ebt \u2014 k\u00ebto ide vijn\u00eb menj\u00ebher\u00eb n\u00eb mendje kur mendojm\u00eb p\u00ebr implementimin teknik t\u00eb qasjes DevOps. Avantazhet jan\u00eb t\u00eb dukshme. Por, fatkeq\u00ebsisht, ka edhe disavantazhe.<\/p>\n

Kur mbi 5 vjet m\u00eb par\u00eb, zhvilluesit tan\u00eb erdh\u00ebn te ne, te specialist\u00ebt e rrjetit, me k\u00ebto propozime, ne nuk ishim t\u00eb entuziazmuar.
\n<\/a><\/noindex>
\nDuhet th\u00ebn\u00eb se trash\u00ebguam nj\u00eb rrjet mjaft t\u00eb ngjash\u00ebm, i p\u00ebrb\u00ebr\u00eb nga pajisje t\u00eb rreth 10 prodhuesve t\u00eb ndrysh\u00ebm. Disa ishin t\u00eb lehta p\u00ebr t'u konfiguruar p\u00ebrmes CLI-s\u00eb son\u00eb t\u00eb preferuar, por diku preferonim t\u00eb p\u00ebrdornim GUI. P\u00ebr m\u00eb tep\u00ebr, puna e gjat\u00eb me pajisje \"n\u00eb jet\" na kishte m\u00ebsuar p\u00ebr kontrollin n\u00eb koh\u00eb reale. P\u00ebr shembull, kur b\u00ebj ndryshime, ndihem shum\u00eb m\u00eb komod duke punuar direkt p\u00ebrmes CLI-s\u00eb. K\u00ebshtu, mund t\u00eb shoh shpejt n\u00ebse di\u00e7ka ka shkuar n\u00eb m\u00ebnyr\u00eb t\u00eb gabuar dhe ta \"rikthej\" ndryshimin. E gjith\u00eb kjo ishte disi n\u00eb kontradikt\u00eb me idet\u00eb e tyre.<\/p>\n

K\u00ebtu lindin edhe pyetje t\u00eb tjera, p\u00ebr shembull, nd\u00ebrmjet versioneve t\u00eb softuerit, nd\u00ebrfaqja mund t\u00eb ndryshoj\u00eb pak. Kjo, n\u00eb fund t\u00eb fundit, do t\u00eb \u00e7oj\u00eb n\u00eb faktin se skripti juaj do t\u00eb krijoj\u00eb nj\u00eb \"konfig\" t\u00eb gabuar. Nuk do t\u00eb doja t\u00eb p\u00ebrdorja prodhimin p\u00ebr \"testim\". <\/p>\n

Ose, si t\u00eb kuptohet q\u00eb komandat konfiguruese jan\u00eb aplikuar sakt\u00eb dhe \u00e7far\u00eb t\u00eb b\u00ebsh n\u00eb rast t\u00eb gabimit?<\/p>\n

Nuk d\u00ebshiroj t\u00eb them se t\u00eb gjitha k\u00ebto pyetje jan\u00eb t\u00eb pazgjidhshme. Duke th\u00ebn\u00eb \"A\", ndoshta \u00ebsht\u00eb e arsyeshme t\u00eb thuash edhe \"B\" dhe, n\u00ebse d\u00ebshiron t\u00eb p\u00ebrdor\u00ebsh t\u00eb nj\u00ebjtat procese p\u00ebr kontrollin e ndryshimeve si n\u00eb zhvillim, duhet t\u00eb kesh p\u00ebrve\u00e7 production edhe dev dhe staging mjedise. At\u00ebher\u00eb ky qasje duket e plot\u00eb. Por sa do t\u00eb kushtoj\u00eb kjo?<\/p>\n

Por ka nj\u00eb situat\u00eb kur disavantazhet praktikisht neutralizohen dhe mbeten vet\u00ebm avantazhet. Po flas p\u00ebr pun\u00ebt projektore.<\/p>\n

Projekt<\/h2>\n

\nDy vitet e fundit kam marr\u00eb pjes\u00eb n\u00eb nj\u00eb projekt p\u00ebr nd\u00ebrtimin e nj\u00eb data center-i p\u00ebr nj\u00eb ofrues t\u00eb madh sh\u00ebrbimi. Un\u00eb jam p\u00ebrgjegj\u00ebs n\u00eb k\u00ebt\u00eb projekt p\u00ebr F5 dhe Palo Alto. Nga k\u00ebndv\u00ebshtrimi i Cisco-s, kjo \u00ebsht\u00eb \"3rd party equipment\".<\/p>\n

Personalish, p\u00ebr mua kan\u00eb dy faza t\u00eb qarta n\u00eb k\u00ebt\u00eb projekt. <\/p>\n

Faza e par\u00eb<\/h3>\n

\nViti i par\u00eb isha pa fund i z\u00ebn\u00eb, punoja nat\u00ebn dhe n\u00eb fundjav\u00eb. Nuk mund t\u00eb ngrija kok\u00ebn. T\u00eb presionit nga menaxhimi dhe klienti ishte e fort\u00eb dhe e vazhdueshme. N\u00eb rutin\u00ebn e p\u00ebrhershme nuk mund t\u00eb p\u00ebrpiqesha t\u00eb optimizoja procesin. Kjo nuk ishte vet\u00ebm dhe as aq shum\u00eb konfigurimi i pajisjeve, por p\u00ebrgatitja e dokumentacionit t\u00eb projektit. <\/p>\n

K\u00ebtu filluan provat e para, dhe isha i habitur nga numri i vog\u00ebl i gabimeve dhe pasakt\u00ebsive q\u00eb ishin b\u00ebr\u00eb. Sigurisht, gjith\u00e7ka funksiononte, por aty mungonte nj\u00eb shkronj\u00eb n\u00eb emrin, k\u00ebtu mungonte nj\u00eb rresht n\u00eb komand\u00eb\u2026 Provat vazhduan dhe vazhduan, dhe un\u00eb isha n\u00eb nj\u00eb luft\u00eb t\u00eb vazhdueshme, \u00e7do dit\u00eb me gabime, prova dhe dokumentacion. <\/p>\n

K\u00ebshtu vazhdoi p\u00ebr nj\u00eb vit. Projekti, sa e kuptoj, nuk ishte i leht\u00eb p\u00ebr ask\u00ebnd, por gradualisht klienti filloi t\u00eb b\u00ebhej gjithnj\u00eb e m\u00eb i k\u00ebnaqur, dhe kjo krijoi mund\u00ebsin\u00eb p\u00ebr t\u00eb pun\u00ebsuar inxhinier\u00eb t\u00eb tjer\u00eb, t\u00eb cil\u00ebt mund t\u00eb merrnin pjes\u00eb nga rutina.<\/p>\n

Tani mund t\u00eb shikoja pak rreth meje.
\nDhe kjo ishte fillimi i faz\u00ebs s\u00eb dyt\u00eb. <\/p>\n

Faza e Dyt\u00eb<\/h3>\n

\nDecidova ta automatizoj procesin.<\/p>\n

Ajo q\u00eb kuptova nga bisedat e atyre koh\u00ebve me zhvilluesit (dhe duhet ta pranoj, kishim nj\u00eb ekip t\u00eb fort\u00eb) \u00ebsht\u00eb se formati tekstual, ndon\u00ebse duket si di\u00e7ka nga bota e sistemit operativ DOS, ka disa ve\u00e7ori t\u00eb \u00e7muara.
\nP\u00ebr shembull, formati tekstual do t\u00eb ishte i dobish\u00ebm n\u00ebse d\u00ebshiron t\u00eb shfryt\u00ebzosh plot\u00ebsisht p\u00ebrfitimet e GIT dhe t\u00eb gjitha derivatet e tij. Dhe un\u00eb e doja k\u00ebt\u00eb. <\/p>\n

Duket sikur mund t\u00eb ruajm\u00eb vet\u00ebm konfigurimin ose nj\u00eb list\u00eb komandash, por ndryshimet jan\u00eb mjaft t\u00eb pak\u00ebndshme p\u00ebr t'u b\u00ebr\u00eb. P\u00ebr m\u00eb tep\u00ebr, gjat\u00eb projektimit, ka nj\u00eb detyr\u00eb tjet\u00ebr t\u00eb r\u00ebnd\u00ebsishme. Ju duhet t\u00eb keni dokumentacionin q\u00eb p\u00ebrshkruan dizajnin tuaj n\u00eb m\u00ebnyr\u00eb t\u00eb p\u00ebrgjithshme (Dizajni n\u00eb Nivel t\u00eb Ul\u00ebt) dhe implementimin specifik (Plani i Implementimit t\u00eb Rrjetit). N\u00eb k\u00ebt\u00eb rast, p\u00ebrdorimi i shablloneve duket si nj\u00eb opsion shum\u00eb i p\u00ebrshtatsh\u00ebm.<\/p>\n

K\u00ebshtu, kur p\u00ebrdoren YAML dhe Jinja2, skedari YAML me parametrat e konfigurimit, si adresat IP, numrat BGP AS, etj., luan perfekt rolin e NIP, nd\u00ebrsa shabllonet Jinja2 p\u00ebrfshijn\u00eb sintaks\u00ebn p\u00ebrkat\u00ebse t\u00eb dizajnit, pra n\u00eb thelb jan\u00eb reflektim i LLD. <\/p>\n

Disa dit\u00eb m\u00eb jan\u00eb dashur p\u00ebr t\u00eb m\u00ebsuar gjuh\u00ebt YAML dhe Jinja2. P\u00ebr t\u00eb kuptuar se si funksionon, mjaftojn\u00eb disa shembuj t\u00eb mir\u00eb. M\u00eb pas, rreth dy jav\u00eb m\u00eb jan\u00eb dashur p\u00ebr t\u00eb krijuar t\u00eb gjitha shabllonet p\u00ebrkat\u00ebse me dizajnin ton\u00eb: nj\u00eb jav\u00eb p\u00ebr Palo Alto dhe nj\u00eb jav\u00eb tjet\u00ebr p\u00ebr F5. T\u00eb gjitha k\u00ebto jan\u00eb ngarkuar n\u00eb GitHub-in e korporat\u00ebs.<\/p>\n

Tani procesi i ndryshimeve dukej si m\u00eb posht\u00eb:<\/p>\n