{"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 rrjet\u00ebsore. Kapi i kat\u00ebrt. Automatizimi. Shabllonat","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ky kjo artikull \u00ebsht\u00eb e gjashta n\u00eb ciklin e artikujve \"Si ta merrni n\u00ebn kontroll infrastruktur\u00ebn rrjetore\". Mund t\u00eb gjeni p\u00ebrmbajtjen e t\u00eb gjith\u00eb artikujve t\u00eb ciklit dhe lidhjet. k\u00ebtu<\/a><\/noindex><\/i>.<\/p>\n

Duke l\u00ebn\u00eb disa tema pas, vendosa t\u00eb filloj nj\u00eb kapitull t\u00eb ri.<\/p>\n

Do t\u00eb kthehem te siguria pak m\u00eb von\u00eb. K\u00ebtu dua t\u00eb diskutoj nj\u00eb qasje t\u00eb thjesht\u00eb, por efektive, e cila, sigurisht, n\u00eb nj\u00eb form\u00eb apo n\u00eb nj\u00eb tjet\u00ebr, mund t\u00eb jet\u00eb e dobishme p\u00ebr shum\u00eb. Kjo \u00ebsht\u00eb m\u00eb shum\u00eb nj\u00eb histori e shkurt\u00ebr se si automatizimi mund t\u00eb ndryshoj\u00eb jet\u00ebn e inxhinierit. Do t\u00eb flas p\u00ebr p\u00ebrdorimin e templat\u00ebve. N\u00eb fund ka 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 konfiguracionit me skript, 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 mendoni p\u00ebr realizimin teknik t\u00eb qasjes DevOps. Avantazhet jan\u00eb t\u00eb dukshme. Por fatkeq\u00ebsisht, ka edhe disavantazhe.<\/p>\n

Kur m\u00eb shum\u00eb se 5 vjet m\u00eb par\u00eb, zhvilluesit tan\u00eb erdh\u00ebn te ne, tek rrjetar\u00ebt, me k\u00ebto propozime, ne nuk ishim shum\u00eb entuziast\u00eb.
\n<\/a><\/noindex>
\nDuhet t\u00eb them se trash\u00ebgova nj\u00eb rrjet t\u00eb ngjash\u00ebm, q\u00eb p\u00ebrb\u00ebhej nga pajisje t\u00eb rreth 10 ofruesve t\u00eb ndrysh\u00ebm. Disa gj\u00ebra ishin t\u00eb lehta p\u00ebr t'u konfiguruar p\u00ebrmes CLI-s\u00eb ton\u00eb t\u00eb preferuar, por ndonj\u00ebher\u00eb ne preferonim t\u00eb p\u00ebrdornim GUI-n\u00eb. P\u00ebr m\u00eb tep\u00ebr, puna e gjat\u00eb me pajisje \"n\u00eb jet\u00eb\" na ka m\u00ebsuar p\u00ebr kontrollin n\u00eb koh\u00eb reale. Un\u00eb, p\u00ebr shembull, duke b\u00ebr\u00eb ndryshime, ndjehem shum\u00eb m\u00eb rehat duke punuar drejtp\u00ebrdrejt p\u00ebrmes CLI. K\u00ebshtu mund t\u00eb shoh shpejt n\u00ebse di\u00e7ka shkoi keq dhe ta \"kthej\" ndryshimin. T\u00eb gjitha k\u00ebto ishin n\u00eb nj\u00ebfar\u00eb m\u00ebnyre n\u00eb kontradikt\u00eb me idet\u00eb e tyre.<\/p>\n

Shfaqen edhe pyetje t\u00eb tjera, p\u00ebr shembull, nga versioni n\u00eb version t\u00eb softuerit, nd\u00ebrfaqja mund t\u00eb ndryshoj\u00eb pak. Kjo, p\u00ebrfundimisht, do t\u00eb \u00e7oj\u00eb n\u00eb faktin q\u00eb 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 \"testimin\". <\/p>\n

Ose, si ta kuptoj se komandat e konfigurimit u aplikuan sakt\u00eb dhe \u00e7far\u00eb t\u00eb b\u00ebj n\u00eb rast gabimi?<\/p>\n

Nuk dua t\u00eb them se t\u00eb gjitha k\u00ebto pyetje jan\u00eb t\u00eb pazgjidhshme. Thjesht 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, at\u00ebher\u00eb duhet t\u00eb kesh p\u00ebrve\u00e7 prodhimit, gjithashtu mjedise dev dhe staging. At\u00ebher\u00eb, ky qasje duket e plot\u00eb. Por sa do t\u00eb kushtoj\u00eb?<\/p>\n

Por nj\u00eb situat\u00eb ku disavantazhet pothuajse anulohet, dhe mbeten vet\u00ebm avantazhet. Po flas p\u00ebr pun\u00ebt projektimore.<\/p>\n

Projekti<\/h2>\n

\nDy vitet e fundit, kam marr\u00eb pjes\u00eb n\u00eb nj\u00eb projekt p\u00ebr nd\u00ebrtimin e nj\u00eb qendre t\u00eb t\u00eb dh\u00ebnave p\u00ebr nj\u00eb provajder t\u00eb madh. Un\u00eb jam p\u00ebrgjegj\u00ebs p\u00ebr F5 dhe Palo Alto n\u00eb k\u00ebt\u00eb projekt. Nga k\u00ebndv\u00ebshtrimi i Cisco, kjo \u00ebsht\u00eb '3rd party equipment'.<\/p>\n

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

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

\nViti i par\u00eb kam qen\u00eb pafund\u00ebsisht i angazhuar, kam punuar nat\u00ebn dhe gjat\u00eb fundjavave. Nuk isha n\u00eb gjendje t\u00eb ngrihem kok\u00ebn. Presioni nga menaxhmenti dhe klienti ishte i fort\u00eb dhe i vazhduesh\u00ebm. N\u00eb rutin\u00ebn e p\u00ebrhershme nuk mund t\u00eb p\u00ebrpiqesha as t\u00eb optimizoja procesin. Nuk ishte vet\u00ebm konfigurimi i pajisjeve, por edhe p\u00ebrgatitja e dokumentacionit projektues. <\/p>\n

K\u00ebtu filluan testet e para, dhe isha i befasuar nga sa shum\u00eb gabime dhe pasakt\u00ebsi 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... Testet vazhdonin pa ndalur, dhe un\u00eb isha n\u00eb nj\u00eb luft\u00eb t\u00eb p\u00ebrhershme, t\u00eb p\u00ebrditshme me gabimet, testet dhe dokumentacionin. <\/p>\n

K\u00ebshtu vazhdoi p\u00ebr nj\u00eb vit. Projekti, sa kuptoj, ishte i v\u00ebshtir\u00eb p\u00ebr t\u00eb gjith\u00eb, por gradualisht klienti filloi t\u00eb ishte gjithnj\u00eb e m\u00eb i k\u00ebnaqur, dhe kjo dha mund\u00ebsin\u00eb p\u00ebr t\u00eb marr\u00eb inxhinier\u00eb t\u00eb tjer\u00eb q\u00eb mund t\u00eb merrnin nj\u00eb pjes\u00eb t\u00eb rutin\u00ebs mbi vete.<\/p>\n

Tani ishte koh\u00eb p\u00ebr t\u00eb filluar t\u00eb shihja pak rreth meje.
\nDhe kjo ishte fillimi i faz\u00ebs s\u00eb dyt\u00eb. <\/p>\n

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

\nVendosa t\u00eb automatizoj procesin.<\/p>\n

\u00c7far\u00eb kuptova nga bisedat e asaj kohe me zhvilluesit (dhe duhen kujtuar, kishim nj\u00eb ekip t\u00eb fort\u00eb), \u00ebsht\u00eb se formati tekstual, edhe pse duket n\u00eb shikim t\u00eb par\u00eb si di\u00e7ka nga bota e sistemit operativ DOS, ka nj\u00eb s\u00ebr\u00eb pronash t\u00eb vlefshme.
\nPra, p\u00ebr shembull, formati tekstual do t\u00eb jet\u00eb i dobish\u00ebm n\u00ebse d\u00ebshironi t\u00eb shfryt\u00ebzoni plotsisht p\u00ebrfitimet e GIT dhe t\u00eb gjith\u00eb pasardh\u00ebsve t\u00eb tij. Dhe un\u00eb e doja k\u00ebt\u00eb. <\/p>\n

Mir\u00eb, duket se mund t\u00eb ruajm\u00eb thjesht konfigurimin ose list\u00ebn e komandave, por t\u00eb b\u00ebsh ndryshime \u00ebsht\u00eb mjaft e bezdisshme. P\u00ebrve\u00e7 k\u00ebsaj, gjat\u00eb projektimit ka nj\u00eb detyr\u00eb t\u00eb r\u00ebnd\u00ebsishme tjet\u00ebr. Duhet t\u00eb keni dokumentacion q\u00eb p\u00ebrshkruan dizajnin tuaj n\u00eb t\u00ebr\u00ebsi (Low Level Design) dhe implementimin specifik (Network Implementation Plan). Dhe n\u00eb k\u00ebt\u00eb rast, p\u00ebrdorimi i shablloneve duket t\u00eb jet\u00eb nj\u00eb variant shum\u00eb i p\u00ebrshtatsh\u00ebm.<\/p>\n

Pra p\u00ebrdorimin e YAML dhe Jinja2, skedari YAML me parametrat e konfigurimit, si adresat IP, numrat BGP AS,\u2026 luan shk\u00eblqyesh\u00ebm rolin e NIP, nd\u00ebrsa shablon\u00ebt Jinja2 p\u00ebrfshijn\u00eb sintaks\u00ebn p\u00ebrkat\u00ebse t\u00eb dizajnit, dometh\u00ebn\u00eb p\u00ebrb\u00ebjn\u00eb n\u00eb thelb nj\u00eb pasqyr\u00eb t\u00eb LLD. <\/p>\n

Studimi i gjuh\u00ebve YAML dhe Jinja2 zgjati dy dit\u00eb. P\u00ebr t\u00eb kuptuar se si funksionon mjaftojn\u00eb disa shembuj t\u00eb mir\u00eb. Pastaj, rreth dy jav\u00eb kaluan p\u00ebr krijimin e t\u00eb gjith\u00eb shabloneve q\u00eb p\u00ebrputhen me dizajnin ton\u00eb: nj\u00eb jav\u00eb p\u00ebr Palo Alto dhe nj\u00eb jav\u00eb tjet\u00ebr \u2014 p\u00ebr F5. T\u00eb gjitha kjo u publikua n\u00eb GitHub-in ton\u00eb t\u00eb korporat\u00ebs.<\/p>\n

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