{"id":35972,"date":"2019-10-31T22:08:54","date_gmt":"2019-10-31T19:08:54","guid":{"rendered":"https:\/\/prohoster.info\/blog\/avtomatizatsiya-dlya-samyh-malenkih-chast-nulevaya-planirovanie\/"},"modified":"2019-10-31T22:08:54","modified_gmt":"2019-10-31T19:08:54","slug":"avtomatizatsiya-dlya-samyh-malenkih-chast-nulevaya-planirovanie","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/avtomatizatsiya-dlya-samyh-malenkih-chast-nulevaya-planirovanie","title":{"rendered":"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>CDSM ka p\u00ebrfundoi, por d\u00ebshira e pakontrolluar p\u00ebr t\u00eb shkruar ka mbetur. <\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/fs.linkmeup.ru\/images\/adsm\/0\/kdpv.jpg\"><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/2da9a566e92a782cf1205a6da716d4c4.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p>P\u00ebr shum\u00eb vite, v\u00ebllai yn\u00eb vuante nga kryerja e pun\u00ebve rutin\u00eb, duke kaluar gishta p\u00ebrpara komitetit dhe duke mos fjetur p\u00ebr shkak t\u00eb rikthimeve t\u00eb nat\u00ebs.<br \/>\nPor er\u00ebrat e err\u00ebta po skadojn\u00eb.<\/p>\n<p>Me k\u00ebt\u00eb artikull do t\u00eb filloj nj\u00eb seri rreth asaj se si <i>mua<\/i> m\u00eb duket automatizimi. <br \/>\nGjat\u00eb rrug\u00ebs ne do t\u00eb shqyrtojm\u00eb fazat e automatizimit, ruajtjen e variablave, formalisimin e dizajnit, me RestAPI, NETCONF, YANG, YDK dhe do t\u00eb programojm\u00eb shum\u00eb. <br \/>\n<i>Mua<\/i> kjo do t\u00eb thot\u00eb se a) kjo nuk \u00ebsht\u00eb nj\u00eb e v\u00ebrtet\u00eb objektive, b) nuk \u00ebsht\u00eb qasje e pap\u00ebrs\u00ebritshme m\u00eb e mir\u00eb, c) mendimi im madje gjat\u00eb kalimit nga artikulli i par\u00eb tek ai i fundit mund t\u00eb ndryshoj\u00eb - sinqerisht, nga faza e skic\u00ebs deri n\u00eb publikim kam shkruar gjith\u00e7ka dy her\u00eb. <\/p>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h1>P\u00ebrmbajtja<\/h1>\n<p><\/p>\n<ol>\n<li> <b>Q\u00ebllimet<\/b>\n<ol>\n<li>Rrjeti \u00ebsht\u00eb si nj\u00eb organiz\u00ebm i vet\u00ebm<\/li>\n<li>Testimi i konfiguracionit<\/li>\n<li>Versionimi<\/li>\n<li>Monitorimi dhe rikuperimi automatik i sh\u00ebrbimeve<\/li>\n<\/ol>\n<p>\n <\/li>\n<li> <b>Mjetet<\/b>\n<ol>\n<li>Sistemi i inventarit<\/li>\n<li>Sistemi i menaxhimit t\u00eb hap\u00ebsir\u00ebs IP<\/li>\n<li>Sistemi i p\u00ebrshkrimit t\u00eb sh\u00ebrbimeve rrjet\u00ebsore<\/li>\n<li>Mekanizmi i inicializimit t\u00eb pajisjeve<\/li>\n<li>Modeli konfigurues i vendor-agnostik<\/li>\n<li>Drejtuesi specifik i vendor-interfejsit<\/li>\n<li>Mekanizmi i shp\u00ebrndarjes s\u00eb konfiguracionit n\u00eb pajisje<\/li>\n<li>CI\/CD<\/li>\n<li>Mekanizmi i kopjimit t\u00eb rezerv\u00ebs dhe t\u00eb gjetjes s\u00eb devijimeve<\/li>\n<li>Sistemi i monitorimit<\/li>\n<\/ol>\n<p>\n <\/li>\n<li> <b>P\u00ebrfundim<\/b>\n <\/li>\n<\/ol>\n<p>\nADSM do ta provoj t\u00eb udh\u00ebheq n\u00eb nj\u00eb format paksa t\u00eb ndrysh\u00ebm nga CDSML. Akoma do t\u00eb shfaqen artikuj t\u00eb m\u00ebdhenj dhe t\u00eb holl\u00ebsish\u00ebm numra, nd\u00ebrsa midis tyre do t\u00eb publikoj sh\u00ebnime t\u00eb vogla nga praktik\u00ebn e p\u00ebrditshme. Do t\u00eb p\u00ebrpiqem t\u00eb luftoj me perfeksionizmin dhe t\u00eb mos rregulloj \u00e7do prej tyre. <\/p>\n<blockquote><p> Sa qesharake \u00ebsht\u00eb q\u00eb p\u00ebr her\u00eb t\u00eb dyt\u00eb duhet t\u00eb kaloj t\u00eb nj\u00ebjt\u00ebn rrug\u00eb.<\/p>\n<p> Fillimisht, duhet t\u00eb shkruaja vet\u00eb artikuj p\u00ebr rrjetet p\u00ebr shkak se ata nuk ishin t\u00eb pranish\u00ebm n\u00eb runet.<\/p>\n<p> Tani nuk mund ta gjej nj\u00eb dokument gjith\u00ebp\u00ebrfshir\u00ebs q\u00eb t\u00eb sistematizoj\u00eb qasjet ndaj automatizimit dhe t\u00eb shqyrtoj\u00eb teknologjit\u00eb e p\u00ebrmendura m\u00eb sip\u00ebr me shembuj t\u00eb thjesht\u00eb praktik\u00eb.<\/p>\n<p> Ndoshta gaboj, prandaj, d\u00ebrgoni lidhje p\u00ebr burime t\u00eb vlefshme. Megjithat\u00eb, kjo nuk do t\u00eb ndryshoj\u00eb vendosm\u00ebrin\u00eb time p\u00ebr t\u00eb shkruar, sepse, q\u00ebllimi kryesor \u00ebsht\u00eb t\u00eb m\u00ebsoj di\u00e7ka p\u00ebr vete, nd\u00ebrsa leht\u00ebsimi i jet\u00ebs s\u00eb t\u00eb tjer\u00ebve \u00ebsht\u00eb nj\u00eb bonus i k\u00ebndsh\u00ebm q\u00eb p\u00ebrk\u00ebdheli gjenin e shp\u00ebrndarjes s\u00eb p\u00ebrvoj\u00ebs.\n<\/p><\/blockquote>\n<p>Ne do t\u00eb p\u00ebrpiqemi t\u00eb marrim nj\u00eb qend\u00ebr t\u00eb mesme t\u00eb t\u00eb dh\u00ebnave LAN DC dhe t\u00eb zhvillojm\u00eb t\u00ebr\u00eb skem\u00ebn e automatizimit. <br \/>\nDisa gj\u00ebra do t'i b\u00ebj praktikisht p\u00ebr her\u00eb t\u00eb par\u00eb me ju. <\/p>\n<blockquote><p> N\u00eb idet\u00eb dhe mjetet e p\u00ebrshkruara k\u00ebtu nuk do t\u00eb jem origjinal. Dmitry Figol ka nj\u00eb kanal t\u00eb shk\u00eblqyer <noindex><a rel=\"nofollow\" href=\"https:\/\/www.youtube.com\/watch?v=MLeiShwb7Qo&amp;list=PLSwGHYY8t8JiGI9powOXDHTAXDSs7FZqt\">me transmetime rreth k\u00ebsaj teme<\/a><\/noindex>. <br \/>\n Artikujt do t\u00eb kryq\u00ebzohen me ta n\u00eb shum\u00eb aspekte. \n<\/p><\/blockquote>\n<p>N\u00eb LAN DC ka 4 DC, rreth 250 switch-e, nj\u00eb duzin\u00eb router-a dhe disa firewalls. <br \/>\nNuk \u00ebsht\u00eb Facebook, por mjaftuesh\u00ebm p\u00ebr t\u00eb ndjer\u00eb thell\u00ebsisht nevoj\u00ebn p\u00ebr automatizim. <br \/>\nMegjithat\u00eb, ka nj\u00eb mendim se n\u00ebse keni m\u00eb shum\u00eb se 1 pajisje, automatizimi \u00ebsht\u00eb i nevojsh\u00ebm. <br \/>\nN\u00eb realitet, \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb imagjinohet se dikush mund t\u00eb jetoj\u00eb tani pa t\u00eb pakt\u00ebn nj\u00eb grusht skenari t\u00eb thjesht\u00eb. <br \/>\nMegjithat\u00eb, kam d\u00ebgjuar se ka kompani ku regjistrimi i adresave IP b\u00ebhet n\u00eb Excel, dhe \u00e7do nj\u00eb nga mij\u00ebra pajisjeve t\u00eb rrjetit konfigurrohet manualisht dhe ka konfigurimin e saj unik. Kjo, sigurisht, mund t\u00eb paraqitet si art modern, por ndjenjat e inxhinierit do t\u00eb ofendohen patjet\u00ebr. <\/p>\n<h1>Q\u00ebllimet<\/h1>\n<p>\nTani do t\u00eb vendosim q\u00ebllime sa m\u00eb abstrakte:<\/p>\n<ul>\n<li>Rrjeti \u00ebsht\u00eb si nj\u00eb organiz\u00ebm i vet\u00ebm<\/li>\n<li>Testimi i konfiguracionit<\/li>\n<li>Versionimi i gjendjes s\u00eb rrjetit<\/li>\n<li>Monitorimi dhe rikuperimi automatik i sh\u00ebrbimeve<\/li>\n<\/ul>\n<p>\nM\u00eb von\u00eb n\u00eb k\u00ebt\u00eb artikull do t\u00eb shqyrtojm\u00eb se cilat mjete do t\u00eb p\u00ebrdorim, dhe n\u00eb t\u00eb ardhshmet do t\u00eb diskutojm\u00eb dhe q\u00ebllimet dhe mjetet n\u00eb detaje.<\/p>\n<h2>Rrjeti \u00ebsht\u00eb si nj\u00eb organiz\u00ebm i vet\u00ebm<\/h2>\n<p>\nFraza p\u00ebrcaktuese e ciklit, edhe pse n\u00eb pamje t\u00eb par\u00eb mund t\u00eb duket e par\u00ebnd\u00ebsishme: <b>ne do t\u00eb konfigurojm\u00eb rrjetin, jo pajisjet e ve\u00e7anta<\/b>. <br \/>\nGjat\u00eb viteve t\u00eb fundit kemi par\u00eb nj\u00eb ndryshim fokusimi drejt trajtimit t\u00eb rrjetit si nj\u00eb entitet t\u00eb vet\u00ebm, dhe si rezultat kemi <i>Rrjet\u00ebzimi i P\u00ebrcaktuar nga Softueri<\/i>, <i>Rrjetet e Drejtuara nga Q\u00ebllimi<\/i> dhe <i>Rrjetet Autonomous<\/i>. <br \/>\nSepse \u00e7far\u00eb kan\u00eb nevoj\u00eb aplikacionet nga rrjeti n\u00eb m\u00ebnyr\u00eb globale: lidhshm\u00ebria midis pikave A dhe B (ndonj\u00ebher\u00eb +B-Y) dhe izolimi nga aplikacione dhe p\u00ebrdorues t\u00eb tjer\u00eb. <\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/f8b43928ccc6d487722ce7724f5c4829.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nDhe k\u00ebshtu, detyra jon\u00eb n\u00eb k\u00ebt\u00eb seri \u00ebsht\u00eb <b>nd\u00ebrtimi i nj\u00eb sistemi<\/b>, q\u00eb mb\u00ebshtet konfigurimin aktual <b>t\u00eb gjith\u00eb rrjetit<\/b>, q\u00eb tashm\u00eb dekompozohet n\u00eb konfigurimin aktual n\u00eb \u00e7do pajisje n\u00eb p\u00ebrputhje me rolin dhe vendndodhjen e saj. <br \/>\n<b>Sistemi<\/b> menaxhimi i rrjetit n\u00ebnkupton se p\u00ebr t\u00eb b\u00ebr\u00eb ndryshime ne lidhemi me t\u00eb, dhe ajo n\u00eb an\u00ebn e saj llogarit gjendjen e nevojshme p\u00ebr \u00e7do pajisje dhe e konfiguronte at\u00eb. <br \/>\nK\u00ebshtu ne minimizojm\u00eb pothuajse n\u00eb zero sh\u00ebtitjet n\u00eb CLI me duar - \u00e7do ndryshim n\u00eb konfigurimin e pajisjeve ose dizajnin e rrjetit duhet t\u00eb formizohet dhe dokumentohet - dhe vet\u00ebm pastaj t\u00eb aplikohet n\u00eb elementet e nevojshme t\u00eb rrjetit. <\/p>\n<blockquote><p> Praud, p\u00ebr shembull, n\u00ebse kemi vendosur q\u00eb q\u00eb nga ky moment, switch-et e kabinetit n\u00eb Kazan duhet t\u00eb shpallin dy rrjete n\u00eb vend t\u00eb nj\u00eb, ne<\/p>\n<ol>\n<li>S\u00eb pari, dokumentojm\u00eb ndryshimet n\u00eb sisteme<\/li>\n<li>Generojm\u00eb konfigurimin e q\u00ebllimsh\u00ebm p\u00ebr t\u00eb gjitha pajisjet e rrjetit<\/li>\n<li>Nisim programin e p\u00ebrdit\u00ebsimit t\u00eb konfigurimit t\u00eb rrjetit, i cili llogarit \u00e7far\u00eb duhet t\u00eb hiqet n\u00eb \u00e7do nod, \u00e7far\u00eb duhet t\u00eb shtohet dhe e \u00e7on nodin n\u00eb gjendjen e k\u00ebrkuar.<\/li>\n<\/ol>\n<p>\n N\u00eb k\u00ebt\u00eb rast, ne b\u00ebjm\u00eb ndryshime me dor\u00eb vet\u00ebm n\u00eb hapin e par\u00eb.\n<\/p><\/blockquote>\n<h2>Testimi i konfiguracionit<\/h2>\n<p>\n<noindex><a rel=\"nofollow\" href=\"http:\/\/www.wikisummaries.org\/wiki\/Visible_Ops\">Dihet<\/a><\/noindex>, se 80% e problemeve ndodhin gjat\u00eb ndryshimit t\u00eb konfiguracionit - nj\u00eb d\u00ebshmi indirekte \u00ebsht\u00eb se gjat\u00eb festave t\u00eb fundvitit zakonisht gjith\u00e7ka \u00ebsht\u00eb qet\u00eb. <br \/>\nPersonalish kam qen\u00eb d\u00ebshmitar i dhjetra nd\u00ebrprerjeve globale p\u00ebr shkak t\u00eb gabimeve njer\u00ebzore: komanda e gabuar, ekzekutimi n\u00eb deg\u00ebn e gabuar t\u00eb konfiguracionit, harrimi i komunitetit, fshira globale e MPLS n\u00eb router, konfigurohen pes\u00eb pajisje, nd\u00ebrsa n\u00eb t\u00eb gjashtin nuk e v\u00ebm\u00eb re gabimin, kemi komituar ndryshimet e vjetra, t\u00eb b\u00ebra nga nj\u00eb person tjet\u00ebr. Ka mij\u00ebra skenar\u00eb. <\/p>\n<p>Automatizimi do t\u00eb na lejoj\u00eb t\u00eb b\u00ebjm\u00eb m\u00eb pak gabime, por n\u00eb nj\u00eb shkall\u00eb m\u00eb t\u00eb madhe. K\u00ebshtu, mund t\u00eb bllokojm\u00eb jo nj\u00eb pajisje, por t\u00eb gjith\u00eb rrjetin nj\u00ebher\u00ebsh. <\/p>\n<p>Q\u00eb n\u00eb fillim t\u00eb koh\u00ebs, paraardh\u00ebsit tan\u00eb kontrollonin sakt\u00ebsin\u00eb e ndryshimeve t\u00eb b\u00ebra me nj\u00eb sy t\u00eb mpreht\u00eb, me nj\u00eb guxim t\u00eb fort\u00eb dhe funksionalitetin e rrjetit pas aplikimit t\u00eb tyre. <br \/>\nAta paraardh\u00ebs, puna e t\u00eb cil\u00ebve \u00e7onte n\u00eb ndalesa dhe humbje katastofike, linin m\u00eb pak pasardh\u00ebs dhe duhej t\u00eb zhdukeshin me kalimin e koh\u00ebs, por evolucioni \u00ebsht\u00eb nj\u00eb proces i ngadalt\u00eb, dhe prandaj nuk t\u00eb gjith\u00eb e kontrollojn\u00eb paraprakisht ndryshimin n\u00eb laborator. <br \/>\nMegjithat\u00eb, n\u00eb maj\u00eb t\u00eb progresit jan\u00eb ata q\u00eb kan\u00eb automatizuar procesin e testimit t\u00eb konfiguracionit dhe aplikimin e m\u00ebtejsh\u00ebm t\u00eb tij n\u00eb rrjet. Me fjal\u00eb t\u00eb tjera - kan\u00eb marr\u00eb hua procedur\u00ebn CI\/CD (<noindex><a rel=\"nofollow\" href=\"https:\/\/img.devrant.com\/devrant\/rant\/r_1535091_ErSUL.jpg\">Integrimi i P\u00ebrdoruesve, Dor\u00ebzimi i Vazhdimisht<\/a><\/noindex>) nga zhvilluesit.<br \/>\nN\u00eb nj\u00eb nga pjes\u00ebt, do t\u00eb shqyrtojm\u00eb si ta realizojm\u00eb k\u00ebt\u00eb me nj\u00eb sistem kontrolli versioni, ndoshta GitHub. <\/p>\n<blockquote><p> Sa her\u00eb q\u00eb t\u00eb merrni me mendimin p\u00ebr CI\/CD rrjetor, n\u00eb nj\u00eb moment, metoda e kontrollit t\u00eb konfiguracionit duke e aplikuar n\u00eb rrjetin e pun\u00ebs do t'ju duket si nj\u00eb injoranc\u00eb e mesjet\u00ebs s\u00eb hershme. Pothuajse si t\u00eb godas\u00ebsh me \u00e7eki\u00e7 mbi nj\u00eb kok\u00eb b\u00ebrthamor.\n<\/p><\/blockquote>\n<p>Nj\u00eb vazhdim organik i ideve p\u00ebr <b>sistemit<\/b> menaxhimin e rrjetit dhe CI\/CD \u00ebsht\u00eb versionimi i plot\u00eb i konfiguracionit. <\/p>\n<h2>Versionimi<\/h2>\n<p>\nNe do ta shohim se p\u00ebr \u00e7do ndryshim, madje edhe m\u00eb t\u00eb voglin, madje n\u00eb nj\u00eb pajisje t\u00eb padukshme, e gjith\u00eb rrjeti kalon nga nj\u00eb gjendje n\u00eb tjetr\u00ebn.<br \/>\nDhe ne gjithmon\u00eb nuk e realizojm\u00eb komand\u00ebn n\u00eb pajisje, ne ndryshojm\u00eb gjendjen e rrjetit. <br \/>\nLe t\u00eb quajm\u00eb k\u00ebto gjendje versione?<\/p>\n<p>Supozoni se versioni aktual \u00ebsht\u00eb 1.0.0.<br \/>\n\u00cbnd\u00ebrr nga nd\u00ebrrimi i IP-adres\u00ebs s\u00eb interfesit Loopback n\u00eb nj\u00eb nga ToR? Ky \u00ebsht\u00eb nj\u00eb version i vog\u00ebl \u2014 do t\u00eb marr\u00eb numrin 1.0.1.<br \/>\nKemi rishikuar politikat e importit t\u00eb rrug\u00ebve n\u00eb BGP \u2014 di\u00e7ka m\u00eb serioze \u2014 tashm\u00eb \u00ebsht\u00eb 1.1.0.<br \/>\nKemi vendosur t\u00eb heqim IGP-n\u00eb dhe t\u00eb kalojm\u00eb vet\u00ebm n\u00eb BGP \u2014 kjo \u00ebsht\u00eb nj\u00eb ndryshim radikal n\u00eb dizajn \u2014 2.0.0.<\/p>\n<p>N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, qendrat e t\u00eb dh\u00ebnave t\u00eb ndryshme mund t\u00eb ken\u00eb versione t\u00eb ndryshme \u2014 rrjeti zhvillohet, vendoset pajisje e re, diku shtohen nivele t\u00eb reja spina, diku \u2014 jo, etj.<\/p>\n<p>P\u00ebr <noindex><a rel=\"nofollow\" href=\"https:\/\/semver.org\">versionim semantik<\/a><\/noindex> ne do t\u00eb flasim n\u00eb nj\u00eb artikull t\u00eb ve\u00e7ant\u00eb.<\/p>\n<p>P\u00ebrs\u00ebris \u2014 \u00e7do ndryshim (p\u00ebrve\u00e7 komandave t\u00eb ndihm\u00ebs) \u00ebsht\u00eb nj\u00eb p\u00ebrdit\u00ebsim versioni. Administrator\u00ebt duhet t\u00eb njoftohen p\u00ebr \u00e7do devijim nga versioni aktual.<\/p>\n<p>E nj\u00ebjta gj\u00eb vlen edhe p\u00ebr kthimin e ndryshimeve \u2014 kjo nuk \u00ebsht\u00eb anulimi i komandave t\u00eb fundit, nuk \u00ebsht\u00eb rollback me forcat e sistemit operativ t\u00eb pajisjes \u2014 kjo \u00ebsht\u00eb sjellja e gjith\u00eb rrjetit n\u00eb nj\u00eb version t\u00eb ri (t\u00eb vjet\u00ebr). <\/p>\n<h2>Monitorimi dhe rikuperimi automatik i sh\u00ebrbimeve<\/h2>\n<p>\nKjo \u00ebsht\u00eb nj\u00eb detyr\u00eb e qart\u00eb n\u00eb rrjetet moderne, duke kaluar n\u00eb nj\u00eb nivel t\u00eb ri.<br \/>\nshpesh praktikohet nga ofruesit e m\u00ebdhenj t\u00eb sh\u00ebrbimeve se sh\u00ebrbimi i r\u00ebn\u00eb duhet t\u00eb rregullohet shum\u00eb shpejt dhe t\u00eb ngrihet nj\u00eb i ri, n\u00eb vend q\u00eb t\u00eb merret me at\u00eb q\u00eb ndodhi.<br \/>\n\u00abShum\u00eb\u00bb do t\u00eb thot\u00eb se nga t\u00eb gjitha an\u00ebt duhet t\u00eb mbushet me monitorime, q\u00eb brenda disa sekondave do t\u00eb zbulojn\u00eb m\u00eb t\u00eb voglin devijim nga norma.<br \/>\nDhe k\u00ebtu nuk mjafton t\u00eb kesh metrika t\u00eb njohura, si ngarkesa e intervist\u00ebs ose disponueshm\u00ebria e nyj\u00ebs. S\u00eb bashku nuk \u00ebsht\u00eb e mjaftueshme q\u00eb ruajt\u00ebsi t\u00eb ndjek\u00eb manualisht ato.<br \/>\nP\u00ebr shum\u00eb gj\u00ebra duhet t\u00eb ket\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/www.irisns.com\/self-healing-network-tomorrow-look-like\/\">Vet\u00eb-Sh\u00ebrim<\/a><\/noindex> \u2014 monitorimet u ndez\u00ebn n\u00eb t\u00eb kuqe dhe shkuan vet\u00eb t'i japin ndihm\u00ebn, ku dhemb.<\/p>\n<p>Dhe k\u00ebtu ne gjithashtu monitorojm\u00eb jo vet\u00ebm pajisje t\u00eb ve\u00e7anta, por edhe sh\u00ebndetin e rrjetit n\u00eb t\u00ebr\u00ebsi, dhe kjo si whitebox, q\u00eb \u00ebsht\u00eb relativisht e qart\u00eb, ashtu edhe blackbox, q\u00eb \u00ebsht\u00eb m\u00eb e komplikuar.<\/p>\n<p>\n\u00c7far\u00eb do na nevojitet p\u00ebr t\u00eb realizuar k\u00ebt\u00eb plane ambicioze?<\/p>\n<ul>\n<li>T\u00eb kemi nj\u00eb list\u00eb t\u00eb t\u00eb gjitha pajisjeve n\u00eb rrjet, vendndodhjet e tyre, rolet, modelet, versionet e softuerit. <br \/>\n <i>kazan-leaf-1.lmu.net, Kazan, leaf, Juniper QFX 5120, R18.3.<\/i>\n <\/li>\n<li>T\u00eb kemi nj\u00eb sistem p\u00ebr p\u00ebrshkrimin e sh\u00ebrbimeve rrjet\u00ebsore. <br \/>\n <i>IGP, BGP, L2\/3VPN, Politika, ACL, NTP, SSH.<\/i><\/li>\n<li>T\u00eb jesh n\u00eb gjendje t\u00eb inicializosh pajisjen. <br \/>\n <i>Hostname, Mgmt IP, Mgmt Route, Users, RSA-Keys, LLDP, NETCONF<\/i><\/li>\n<li>T\u00eb konfigurosh pajisjen dhe ta kesh konfigurimin n\u00eb versionin e duhur (p\u00ebrfshir\u00eb versionin e vjet\u00ebr).<\/li>\n<li>T\u00eb testosh konfigurimin<\/li>\n<li>T\u00eb kontrollosh rregullisht gjendjen e t\u00eb gjitha pajisjeve p\u00ebr devijime nga aktualja dhe t\u00eb njoftosh p\u00ebrkat\u00ebsin.<br \/>\n <i>Nat\u00ebn dikush qet\u00ebsisht shtoi nj\u00eb rregull n\u00eb ACL<\/i>.<\/li>\n<li>T\u00eb monitorosh funksionimin.<\/li>\n<\/ul>\n<p><\/p>\n<h1>Mjetet<\/h1>\n<p>\nD\u00ebgjohet mjaft e komplikuar p\u00ebr t\u00eb filluar t\u00eb dekompozosh projektin n\u00eb komponente.<\/p>\n<p>Dhe do t\u00eb jen\u00eb dhjet\u00eb:<\/p>\n<ol>\n<li>Sistemi i inventarit<\/li>\n<li>Sistemi i menaxhimit t\u00eb hap\u00ebsir\u00ebs IP<\/li>\n<li>Sistemi i p\u00ebrshkrimit t\u00eb sh\u00ebrbimeve rrjet\u00ebsore<\/li>\n<li>Mekanizmi i inicializimit t\u00eb pajisjeve<\/li>\n<li>Modeli konfigurues i vendor-agnostik<\/li>\n<li>Drejtuesi specifik i vendor-interfejsit<\/li>\n<li>Mekanizmi i shp\u00ebrndarjes s\u00eb konfiguracionit n\u00eb pajisje<\/li>\n<li>CI\/CD<\/li>\n<li>Mekanizmi i kopjimit t\u00eb rezerv\u00ebs dhe t\u00eb gjetjes s\u00eb devijimeve<\/li>\n<li>Sistemi i monitorimit<\/li>\n<\/ol>\n<blockquote><p> Kjo, ndryshe, \u00ebsht\u00eb nj\u00eb shembull se si ka ndryshuar v\u00ebshtrimi mbi q\u00ebllimet e ciklit \u2014 n\u00eb draftin e komponenteve ishin 4.\n<\/p><\/blockquote>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/91132e29d359a4042b213529511f6d7d.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nN\u00eb ilustrim kam nd\u00ebrtuar t\u00eb gjitha komponentet dhe vet\u00eb pajisjen. <br \/>\nKomponentet e nd\u00ebrthura bashk\u00ebpunojn\u00eb me nj\u00ebra-tjetr\u00ebn. <br \/>\nSa m\u00eb i madh t\u00eb jet\u00eb blloku, aq m\u00eb shum\u00eb v\u00ebmendje i duhet dedikuar k\u00ebtij komponenti. <\/p>\n<p><\/p>\n<h2>Komponenti 1. Sistemi i inventarizimit<\/h2>\n<p>\nSigurisht, d\u00ebshirojm\u00eb t\u00eb dim\u00eb se cili ekip, ku ndodhet, me \u00e7far\u00eb \u00ebsht\u00eb i lidhur. <br \/>\nSistemi i inventarizimit \u00ebsht\u00eb nj\u00eb pjes\u00eb e pandashme e \u00e7do nd\u00ebrrmarrjeje. <br \/>\nS\u00eb shumti, p\u00ebr pajisjet rrjet, nd\u00ebrmarrjet kan\u00eb nj\u00eb sistem t\u00eb ve\u00e7ant\u00eb inventarizimi q\u00eb zgjidh probleme m\u00eb specifike. <br \/>\nBrenda ciklit t\u00eb artikujve ne do ta quajm\u00eb k\u00ebt\u00eb DCIM \u2014 Menaxhimi i Infrastruktur\u00ebs s\u00eb Qendr\u00ebs s\u00eb T\u00eb Dh\u00ebnave. Megjithat\u00eb, termi DCIM, n\u00eb kuptimin e ngusht\u00eb, p\u00ebrfshin shum\u00eb m\u00eb tep\u00ebr.<\/p>\n<p>P\u00ebr ne, n\u00eb t\u00eb do t\u00eb ruajm\u00eb informacionin e m\u00ebposht\u00ebm p\u00ebr pajisjen:<\/p>\n<ul>\n<li>Numri i inventarit<\/li>\n<li>Emri\/p\u00ebrshkrimi <\/li>\n<li>Modeli (<i>Huawei CE12800, Juniper QFX5120 etj<\/i>)<\/li>\n<li>Parametrat karakteristik\u00eb (<i>platformat, nd\u00ebrfaqet etj<\/i>)<\/li>\n<li>Roli (<i>Leaf, Spine, Border Router etj<\/i>)<\/li>\n<li>Lokacioni (<i>rajoni, qyteti, qendra e t\u00eb dh\u00ebnave, rafti, uniti<\/i>)<\/li>\n<li>Interkonneksionet mes pajisjeve<\/li>\n<li>Topologjia e rrjetit<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/fac708b1bf3640a943f90247bff8216e.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nE qart\u00eb \u00ebsht\u00eb se edhe neve na intereson t\u00eb dim\u00eb t\u00eb gjitha k\u00ebto. <br \/>\nPor, a do t'i ndihmoj\u00eb kjo n\u00eb automatik\u00ebn? <br \/>\nPadyshim. <br \/>\nP\u00ebr shembull, ne e dim\u00eb q\u00eb n\u00eb k\u00ebt\u00eb qend\u00ebr t\u00eb t\u00eb dh\u00ebnave n\u00eb pajisjet Leaf, n\u00ebse \u00ebsht\u00eb Huawei, ACL p\u00ebr filtrimin e trafikut t\u00eb caktuar duhet t\u00eb aplikohet n\u00eb VLAN, dhe n\u00ebse \u00ebsht\u00eb Juniper \u2014 at\u00ebher\u00eb n\u00eb unitin 0 t\u00eb nd\u00ebrfaqes fizike. <br \/>\nOse duhet t\u00eb shp\u00ebrndajm\u00eb nj\u00eb server t\u00eb ri Syslog n\u00eb t\u00eb gjitha kufijt\u00eb e rajonit.<\/p>\n<p>Aty do t\u00eb ruajm\u00eb edhe pajisjet e rrjetit virtual, p\u00ebr shembuj ruter\u00eb virtual\u00eb ose reflektor\u00eb rrugor\u00eb. Mund t\u00eb shtojm\u00eb server\u00eb DNS, NTP, Syslog dhe n\u00eb p\u00ebrgjith\u00ebsi gjith\u00e7ka q\u00eb lidhet me rrjetin. <\/p>\n<h2>Komponenti 2. Sistemi i menaxhimit t\u00eb hap\u00ebsir\u00ebs IP<\/h2>\n<p>\nPo, dhe n\u00eb koh\u00ebt tona, akoma ka grupe njer\u00ebzish q\u00eb mbajn\u00eb nj\u00eb regjist\u00ebr t\u00eb prefikseve dhe IP-adresave n\u00eb nj\u00eb skedar Excel. Por qasja moderne \u2014 \u00ebsht\u00eb nj\u00eb baz\u00eb t\u00eb dh\u00ebnash, me frontend n\u00eb nginx\/apache, API dhe funksione t\u00eb gjera p\u00ebr regjistrimin e IP-adresave dhe rrjeteve me ndarje n\u00eb VRF.<br \/>\nIPAM \u2014 Menaxhimi i Adresave IP. <\/p>\n<p>P\u00ebr nevojat tona n\u00eb t\u00eb, ne do t\u00eb ruajm\u00eb informacionin e m\u00ebposht\u00ebm:<\/p>\n<ul>\n<li>VLAN<\/li>\n<li>VRF<\/li>\n<li>Rrjetet\/Podsetet<\/li>\n<li>Adresa IP<\/li>\n<li>Lidhja e adresave me pajisjet, rrjetet me lokacionet dhe numrat VLAN<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/6d476d48f95ed663d84cae052a86d129.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nNj\u00eb her\u00eb tjet\u00ebr, \u00ebsht\u00eb e qart\u00eb se ne duam t\u00eb sigurohemi q\u00eb, duke caktuar nj\u00eb IP t\u00eb re p\u00ebr lloopback-in e ToR, nuk do t\u00eb hasim faktin q\u00eb ajo tashm\u00eb \u00ebsht\u00eb caktuar ndokujt. Ose q\u00eb t\u00eb nj\u00ebjtin prefiks e kemi p\u00ebrdorur dy her\u00eb n\u00eb skajet e ndryshme t\u00eb rrjetit. <br \/>\nPor si do t\u00eb ndihmoj\u00eb kjo n\u00eb automatizim? <br \/>\nLeht\u00eb. <br \/>\nK\u00ebrkojm\u00eb n\u00eb sistem nj\u00eb prefiks me rolin Loopbacks, n\u00eb t\u00eb cilin ka adresa IP t\u00eb disponueshme p\u00ebr caktim \u2014 n\u00ebse gjendet, e cakoim adres\u00ebn, n\u00ebse jo, k\u00ebrkojm\u00eb krijimin e nj\u00eb prefiksi t\u00eb ri. <br \/>\nOse gjat\u00eb krijimit t\u00eb konfiguracionit t\u00eb pajisjes, ne mund t\u00eb zbulojm\u00eb nga i nj\u00ebjti sistem n\u00eb cilin VRF duhet t\u00eb ndodhet nd\u00ebrfaqja. <br \/>\nDhe gjat\u00eb aktivizimit t\u00eb nj\u00eb serveri t\u00eb ri, skripti shkon n\u00eb sistem, zbulohet n\u00eb cilin switch server, n\u00eb cilin port dhe cila podshet \u00ebsht\u00eb caktuar p\u00ebr nd\u00ebrfaqen \u2014 nga aty do t\u00eb caktohet adresa e serverit. <\/p>\n<p>\nD\u00ebshira p\u00ebr t\u00eb bashkuar DCIM dhe IPAM n\u00eb nj\u00eb sistem po lind, p\u00ebr t\u00eb shmangur funksionet e dyfishuara dhe p\u00ebr t\u00eb menaxhuar dy entitete t\u00eb ngjashme. <br \/>\nK\u00ebshtu do ta b\u00ebjm\u00eb. <\/p>\n<h2>Komponenti 3. Sistemi i p\u00ebrshkrimit t\u00eb sh\u00ebrbimeve rrjet\u00ebsore<\/h2>\n<p>\nN\u00ebse dy sistemet e para ruajn\u00eb variablat, t\u00eb cilat duhet t\u00eb p\u00ebrdoren ndryshe, at\u00ebher\u00eb e treta p\u00ebrshkruan p\u00ebr \u00e7do rol pajisjeje, se si duhet t\u00eb konfigurohet. <br \/>\nDuhet t\u00eb dallojm\u00eb dy lloje t\u00eb ndryshme t\u00eb sh\u00ebrbimeve rrjet\u00ebsore: <\/p>\n<ul>\n<li>Infrastrukturore<\/li>\n<li>Klientore.<\/li>\n<\/ul>\n<p>T\u00eb parat kan\u00eb p\u00ebr q\u00ebllim t\u00eb sigurojn\u00eb lidhshm\u00ebrin\u00eb dhe menaxhimin e pajisjes. K\u00ebtu p\u00ebrfshihen VTY, SNMP, NTP, Syslog, AAA, protokollet e rrug\u00ebzimit, CoPP, etj. <br \/>\nT\u00eb dytat organizojn\u00eb nj\u00eb sh\u00ebrbim p\u00ebr klientin: MPLS L2\/L3VPN, GRE, VXLAN, VLAN, L2TP, etj. <br \/>\nNatyrisht, ka edhe raste t\u00eb kufizuara \u2014 si do ta klasifikojm\u00eb MPLS LDP, BGP? Dhe protokollet e rrug\u00ebzimit mund t\u00eb p\u00ebrdoren p\u00ebr klient\u00ebt. Por kjo nuk \u00ebsht\u00eb thelb\u00ebsore. <\/p>\n<p>T\u00eb dyja llojet e sh\u00ebrbimeve ndahen n\u00eb primitive konfigurimi:<\/p>\n<ul>\n<li>nd\u00ebrfaqet fizike dhe logjike (tag\/anteg, mtu)<\/li>\n<li>IP-adresat dhe VRF (IP, IPv6, VRF)<\/li>\n<li>ACL dhe politikat e trajtimit t\u00eb trafik\u00ebve<\/li>\n<li>Protokollet (IGP, BGP, MPLS)<\/li>\n<li>Politikat e rrug\u00ebzimit (listat e prefikseve, komunitetet, filtrat ASN).<\/li>\n<li>Sh\u00ebrbimet operative (SSH, NTP, LLDP, Syslog\u2026)<\/li>\n<li>Etj.<\/li>\n<\/ul>\n<p>\nSi e b\u00ebjm\u00eb k\u00ebt\u00eb, nuk kam idea p\u00ebr momentin. Do ta shqyrtojm\u00eb n\u00eb nj\u00eb artikull t\u00eb ve\u00e7ant\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/092bc3a4b875f4a6422ee13fb580ba4f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nN\u00ebse e shohim nga nj\u00eb k\u00ebndv\u00ebshtrim m\u00eb t\u00eb af\u00ebrt me realitetin, mund t\u00eb p\u00ebrshkruajm\u00eb se<br \/>\nSwitch-i Leaf duhet t\u00eb ket\u00eb sesione BGP me t\u00eb gjith\u00eb switch-at Spine t\u00eb lidhur, t\u00eb importe themi n\u00eb proces rrjetet e lidhura, duke pranuar nga switch-at Spine vet\u00ebm rrjetet me nj\u00eb prefiks t\u00eb caktuar. T\u00eb kufizojm\u00eb CoPP IPv6 ND n\u00eb 10 pps etj. <br \/>\nNga ana e saj, spine-t mbajn\u00eb sesione me t\u00eb gjith\u00eb leaf-at e lidhur, duke vepruar si reflektor\u00eb rr\u00ebnj\u00ebsor\u00eb dhe pranojn\u00eb vet\u00ebm rrug\u00ebt me nj\u00eb gjat\u00ebsi t\u00eb caktuar dhe me nj\u00eb komunitet t\u00eb caktuar nga ata.<\/p>\n<h2>Komponenti 4. Mekanizmi i inicializimit t\u00eb pajisjes<\/h2>\n<p>\nN\u00ebn k\u00ebt\u00eb titull un\u00eb bashkoj shum\u00eb veprime q\u00eb duhet t\u00eb ndodhin n\u00eb m\u00ebnyr\u00eb q\u00eb pajisja t\u00eb shfaqet n\u00eb radar dhe t\u00eb jet\u00eb e mundur t\u00eb arrihet n\u00eb distanc\u00eb.<\/p>\n<ol>\n<li>T\u00eb regjistrosh pajisjen n\u00eb sistemin e inventarit.<\/li>\n<li>T\u00eb alokosh nj\u00eb adres\u00eb IP p\u00ebr menaxhim.<\/li>\n<li>T\u00eb konfigurosh aksesin baz\u00eb n\u00eb t\u00eb: <br \/>\nEmri i host-it, adresa IP p\u00ebr menaxhim, rruga n\u00eb rrjetin e menaxhimit, p\u00ebrdoruesit, \u00e7el\u00ebsat SSH, protokollet \u2014 telnet\/SSH\/NETCONF<\/li>\n<\/ol>\n<p>K\u00ebtu ekzistojn\u00eb tri qasje:<\/p>\n<ul>\n<li>Totali manual. Pajisja \u00ebsht\u00eb sjell\u00eb n\u00eb nj\u00eb stend\u00eb, ku nj\u00eb njeri normal do ta regjistroj\u00eb n\u00eb sistem, do t\u00eb lidhet me konsol\u00ebn dhe do ta konfiguroj\u00eb. Mund t\u00eb funksionoj\u00eb n\u00eb rrjete t\u00eb vogla statike.<\/li>\n<li>ZTP \u2014 Zero Touch Provisioning. Pajisja ka arritur, \u00ebsht\u00eb vendosur, ka marr\u00eb nj\u00eb adres\u00eb p\u00ebrmes DHCP, \u00ebsht\u00eb lidhur me nj\u00eb server t\u00eb ve\u00e7ant\u00eb dhe \u00ebsht\u00eb konfiguruar vet\u00eb. <\/li>\n<li>Infrastruktura e server\u00ebve t\u00eb konsol\u00ebs, ku konfigurimi fillestar ndodh n\u00eb m\u00ebnyr\u00eb automatike p\u00ebrmes portit t\u00eb konsol\u00ebs.<\/li>\n<\/ul>\n<p>P\u00ebr t\u00eb treja do flasim n\u00eb nj\u00eb artikull t\u00eb ve\u00e7ant\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/6d8d061e53b508edbbcbd98fe496ca91.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h2>Komponenti 5. Modeli i konfigurimit vendor-agnostik<\/h2>\n<p>\nDeri tani t\u00eb gjitha sistemet kan\u00eb qen\u00eb cop\u00ebza t\u00eb ndara, duke ofruar p\u00ebrshkrimin variab\u00ebl dhe deklarativ t\u00eb asaj q\u00eb do donim t\u00eb shihnim n\u00eb rrjet. Por, her\u00ebt ose von\u00eb, do t\u00eb duhet t\u00eb merremi me konkret\u00ebsin\u00eb. <br \/>\nN\u00eb k\u00ebt\u00eb etap\u00eb, p\u00ebr \u00e7do pajisje specifike, primitive, sh\u00ebrbimet dhe variablat kombinohen n\u00eb nj\u00eb model konfiguracioni, q\u00eb p\u00ebrshkruan n\u00eb fakt konfigurimin e plot\u00eb t\u00eb pajisjes specifike, vet\u00ebm n\u00eb nj\u00eb m\u00ebnyr\u00eb q\u00eb nuk varet nga shit\u00ebsi. <br \/>\n\u00c7far\u00eb sjell ky hap? Pse t\u00eb mos formohej menj\u00ebher\u00eb konfigurimi i pajisjes q\u00eb mund t\u00eb ngarkohej leht\u00eb? <br \/>\nN\u00eb t\u00eb v\u00ebrtet\u00eb, kjo lejon zgjidhjen e tri detyrave:<\/p>\n<ol>\n<li> Mos u akomodoni me nj\u00eb nd\u00ebrfaqe t\u00eb caktuar p\u00ebr t\u00eb bashk\u00ebvepruar me pajisjen. Qoft\u00eb CLI, NETCONF, RESTCONF, SNMP \u2014 modelit do t\u00eb mbetet i nj\u00ebjt\u00eb.<\/li>\n<li> Mos mbani numrin e shablloneve\/skripteve n\u00eb numrin e furnizuesve n\u00eb rrjet, dhe n\u00eb rast t\u00eb ndryshimit t\u00eb dizajnit, ndryshoni t\u00eb nj\u00ebjt\u00ebn gj\u00eb n\u00eb disa vende.<\/li>\n<li> Shkarkoni konfigurimin nga pajisja (rezerva), organizojeni n\u00eb nj\u00eb model t\u00eb sakt\u00eb dhe p\u00ebrpiquni t\u00eb krahasoni konfigurimin e synuar me at\u00eb ekzistues p\u00ebr t\u00eb llogaritur diferenc\u00ebn dhe p\u00ebr t\u00eb p\u00ebrgatitur nj\u00eb patch konfigurimi, i cili do t\u00eb ndryshoj\u00eb vet\u00ebm ato pjes\u00eb q\u00eb nevojiten ose p\u00ebr t\u00eb identifikuar devijimet.<\/li>\n<\/ol>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/a154c42ebe7978fcc5b2ce4f235516c9.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nSi rezultat i k\u00ebtij hapi, ne marrim nj\u00eb konfigurim t\u00eb pavarur nga furnizuesi.<\/p>\n<h2>Komponenti 6. Drejtues specifik p\u00ebr interfacing t\u00eb furnizuesit<\/h2>\n<p>\nNuk duhet t\u00eb g\u00ebnjejm\u00eb veten me shpresat se nj\u00eb dit\u00eb do t\u00eb mund ta konfigurojm\u00eb Cisco-n n\u00eb t\u00eb nj\u00ebjt\u00ebn m\u00ebnyr\u00eb si Juniper, thjesht duke d\u00ebrguar thirrje t\u00eb nj\u00ebjta tek ta. Pavar\u00ebsisht popullaritetit n\u00eb rritje t\u00eb whitebox-\u00ebve dhe shpalljes s\u00eb mb\u00ebshtetjes p\u00ebr NETCONF, RESTCONF, OpenConfig, p\u00ebrmbajtja specifike q\u00eb k\u00ebto protokolle ofrojn\u00eb ndryshon nga nj\u00eb ofrues te tjetri dhe kjo \u00ebsht\u00eb nj\u00eb nga ve\u00e7orit\u00eb e tyre konkurrente q\u00eb ata nuk do ta dor\u00ebzojn\u00eb leht\u00eb. <br \/>\nN\u00eb m\u00ebnyr\u00eb t\u00eb ngjashme, OpenContrail dhe OpenStack, t\u00eb cilat kan\u00eb RestAPI si nd\u00ebrfaqen e tyre NorthBound, presin thirrje krejt t\u00eb ndryshme. <\/p>\n<p>Pra, n\u00eb hapin e pest\u00eb modeli i pavarur nga furnizuesi duhet t\u00eb marr\u00eb form\u00ebn q\u00eb do t\u00eb shkoj\u00eb n\u00eb harduer. <br \/>\nDhe k\u00ebtu t\u00eb gjitha mjetet jan\u00eb t\u00eb mira (jo): CLI, NETCONF, RESTCONF, SNMP, nj\u00eb shpjegues i thjesht\u00eb.<\/p>\n<p>Prandaj, do t\u00eb na nevojitet nj\u00eb drejtues i cili do ta transformoj\u00eb rezultatin e hapit t\u00eb m\u00ebparsh\u00ebm n\u00eb formatin e nevojsh\u00ebm p\u00ebr nj\u00eb furnizues t\u00eb caktuar: nj\u00eb grup urdh\u00ebrash CLI, struktur\u00ebn XML.<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/6ed8e935183075fda60a209477f84937.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h2>Komponenti 7. Mekanizmi i paketimit t\u00eb konfigurimit n\u00eb pajisje<\/h2>\n<p>\nPra, ne e kemi krijuar konfigurimin, por duhet ta d\u00ebrgojm\u00eb at\u00eb n\u00eb pajisje \u2014 dhe, natyrisht, jo me duar. <br \/>\n<b>S\u00eb pari<\/b>, na del k\u00ebtu pyetja, \u00e7far\u00eb transporti do t\u00eb p\u00ebrdorim? Dhe zgjedhja sot nuk \u00ebsht\u00eb e vog\u00ebl:<\/p>\n<ul>\n<li>CLI (telnet, ssh)<\/li>\n<li>SNMP<\/li>\n<li>NETCONF<\/li>\n<li>RESTCONF<\/li>\n<li>REST API<\/li>\n<li>OpenFlow (edhe pse ai del nga lista, pasi \u00ebsht\u00eb nj\u00eb m\u00ebnyr\u00eb p\u00ebr t\u00eb d\u00ebrguar FIB, jo konfigurime)<\/li>\n<\/ul>\n<p>Le t\u00eb sqarojm\u00eb disa gj\u00ebra k\u00ebtu. CLI \u00ebsht\u00eb e vjet\u00ebr. SNMP\u2026 ahem.<br \/>\nRESTCONF \u2014 nj\u00eb krijes\u00eb ende e panjohur, REST API mb\u00ebshtetet nga gati askush. Prandaj, n\u00eb ciklin ton\u00eb do t\u00eb fokusohmi n\u00eb NETCONF.<\/p>\n<p>N\u00eb t\u00eb v\u00ebrtet\u00eb, si\u00e7 e kuptoi lexuesi, ne n\u00eb k\u00ebt\u00eb moment tashm\u00eb kemi vendosur p\u00ebr nd\u00ebrfaqen \u2014 rezultati i hapit t\u00eb m\u00ebparsh\u00ebm \u00ebsht\u00eb shfaqur n\u00eb formatin e asaj nd\u00ebrfaqe q\u00eb u zgjodh.<\/p>\n<p><b>S\u00eb dyti<\/b>, por me cilat mjete do ta b\u00ebjm\u00eb k\u00ebt\u00eb?<br \/>\nK\u00ebtu zgjedhja \u00ebsht\u00eb gjithashtu e madhe:<\/p>\n<ul>\n<li>Nj\u00eb skript i krijuar vet\u00eb ose nj\u00eb platform\u00eb. T\u00eb armatosim ncclient dhe asyncIO dhe ta b\u00ebjm\u00eb vet\u00eb. \u00c7far\u00eb na pengon t\u00eb nd\u00ebrtosh sistemin e deploy-it nga zero?<\/li>\n<li>Ansible me bibliotek\u00ebn e tij t\u00eb pasur t\u00eb moduleve rrjet\u00eb.<\/li>\n<li>Salt me pun\u00ebn e tij t\u00eb varf\u00ebr me rrjetin dhe lidhjen me Napalm.<\/li>\n<li>N\u00eb vet\u00eb Napalm, i cili njeh vet\u00ebm disa furnizues, dhe p\u00ebrfundon k\u00ebshtu.<\/li>\n<li>Nornir \u2014 nj\u00eb tjet\u00ebr kafsh\u00eb, t\u00eb cil\u00ebn ne do ta analizojm\u00eb n\u00eb t\u00eb ardhmen.<\/li>\n<\/ul>\n<p>K\u00ebtu ende nuk \u00ebsht\u00eb zgjedhur nj\u00eb favorit \u2014 do t\u00eb eksperimentojm\u00eb.<\/p>\n<p>\u00c7far\u00eb tjet\u00ebr \u00ebsht\u00eb e r\u00ebnd\u00ebsishme k\u00ebtu? Pasojat e aplikimit t\u00eb konfiguracionit. <br \/>\nMe sukses apo jo. A ka mbetur akses n\u00eb pajisje apo jo. <br \/>\nDuket se k\u00ebtu ndihmon commit-i me konfirmimin dhe verifikimin e asaj q\u00eb u ngarkua n\u00eb pajisje. <br \/>\nKjo s\u00eb bashku me realizimin e duhur t\u00eb NETCONF ngushton ndjesh\u00ebm grupin e pajisjeve t\u00eb p\u00ebrshtatshme \u2014 komitetet normale nuk mb\u00ebshteten nga shum\u00eb prodhues. Por kjo \u00ebsht\u00eb thjesht nj\u00eb nga kushtet e obligueshme n\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/ru.wikipedia.org\/wiki\/%D0%97%D0%B0%D0%BF%D1%80%D0%BE%D1%81_%D0%BF%D1%80%D0%B5%D0%B4%D0%BB%D0%BE%D0%B6%D0%B5%D0%BD%D0%B8%D1%8F\">RFP<\/a><\/noindex>. N\u00eb fund t\u00eb fundit, askush nuk shqet\u00ebsohet se asnj\u00eb furnizues rus nuk do t\u00eb plot\u00ebsoj\u00eb kushtin e 32*100GE nd\u00ebrfaqes. Apo njeri shqet\u00ebsohet?<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/59d8ad3b55b9c107642550bb06fc759a.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h2>Komponenti 8. CI\/CD<\/h2>\n<p>\nN\u00eb k\u00ebt\u00eb moment, ne tashm\u00eb kemi p\u00ebrfunduar konfigurimin p\u00ebr t\u00eb gjitha pajisjet e rrjetit.<br \/>\nPo shkruaj \u00abp\u00ebr t\u00eb gjitha\u00bb, sepse po flasim p\u00ebr versionimin e gjendjes s\u00eb rrjetit. Dhe edhe n\u00ebse duhet t\u00eb nd\u00ebrohet konfigurimi i nj\u00eb vet\u00ebm switch, ndryshimet p\u00ebr t\u00eb gjith\u00eb rrjetin llogariten. \u00cbsht\u00eb e qart\u00eb, ata mund t\u00eb jen\u00eb zero p\u00ebr shumic\u00ebn e nyjeve.<\/p>\n<p>Por, si\u00e7 u tha m\u00eb par\u00eb, ne nuk jemi barbar\u00eb q\u00eb t\u00eb hedhim gjith\u00e7ka menj\u00ebher\u00eb n\u00eb prodhim. <br \/>\nKonfigurimi i krijuar duhet s\u00eb pari t\u00eb kaloj\u00eb p\u00ebrmes Pipeline CI\/CD.<\/p>\n<blockquote><p>CI\/CD do t\u00eb thot\u00eb Integrim t\u00eb Vazhdimit, Deploy t\u00eb Vazhdimit. Ky \u00ebsht\u00eb nj\u00eb qasje, ku ekipi nuk publikonte nj\u00eb version t\u00eb ri kryesor \u00e7do gjasht\u00eb muaj, duke z\u00ebvend\u00ebsuar plot\u00ebsisht t\u00eb vjetrit, por implementon rregullisht inkuadrime t\u00eb reja (Deployment) n\u00eb m\u00ebnyr\u00eb t\u00eb vog\u00ebl, t\u00eb cilat testohen n\u00eb m\u00ebnyr\u00eb t\u00eb plot\u00eb p\u00ebr p\u00ebrputhshm\u00ebri, siguri dhe funksionalitet (Integration).\n<\/p><\/blockquote>\n<p>P\u00ebr k\u00ebt\u00eb, ne kemi nj\u00eb sistem kontrolli versioni q\u00eb monitoron ndryshimet n\u00eb konfigurim, nj\u00eb laborator ku kontrollohet n\u00ebse sh\u00ebrbimi i klientit nuk prishet, nj\u00eb sistem monitorimi q\u00eb verifikon k\u00ebt\u00eb fakt, dhe hapi p\u00ebrfundimtar \u2014 publikimi i ndryshimeve n\u00eb rrjetin aktiv.<\/p>\n<p>P\u00ebrve\u00e7 komandave t\u00eb dehjes, t\u00eb gjitha ndryshimet n\u00eb rrjet duhet t\u00eb kalojn\u00eb p\u00ebrmes CI\/CD Pipeline \u2014 kjo \u00ebsht\u00eb \u00e7el\u00ebsi yn\u00eb p\u00ebr nj\u00eb jet\u00eb t\u00eb qet\u00eb dhe nj\u00eb karrier\u00eb t\u00eb gjat\u00eb e t\u00eb lumtur.<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/101a5ff87c7a9c7b6776aca9daf762a4.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h2>Komponenti 9. Sistemi i kopjeve rezerv\u00eb dhe k\u00ebrkimit t\u00eb devijimeve<\/h2>\n<p>\nNuk ka nevoj\u00eb t\u00eb flasim edhe nj\u00ebher\u00eb p\u00ebr kopjet rezerv\u00eb. <br \/>\nNe do t\u2019i ruajm\u00eb ato n\u00ebp\u00ebrmjet cron-it ose me rastin e ndryshimit t\u00eb konfiguracionit n\u00eb git.<\/p>\n<p>Por pjesa e dyt\u00eb \u00ebsht\u00eb m\u00eb interesante \u2014 pas k\u00ebtyre kopjeve rezerv\u00eb dikush duhet t\u00eb q\u00ebndroj\u00eb n\u00eb qend\u00ebr. N\u00eb disa raste, ai dikush duhet t\u00eb shkoj\u00eb dhe t\u00eb kthej\u00eb gjith\u00e7ka si\u00e7 ishte, dhe n\u00eb disa t\u00eb tjera, duhet t\u00eb informoj\u00eb dik\u00eb se ndodhi nj\u00eb problem. <br \/>\nP\u00ebr shembull, n\u00ebse shfaqet ndonj\u00eb p\u00ebrdorues i ri q\u00eb nuk \u00ebsht\u00eb regjistruar n\u00eb variabla, duhet ta heqim at\u00eb nga haku. Po ashtu, n\u00ebse ka nj\u00eb rregull t\u00eb ri p\u00ebr firewall-in \u2014 \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb mos e prekim at\u00eb, ndoshta dikush thjesht aktivizoi dehjen, ose ndoshta nj\u00eb sh\u00ebrbim i ri, q\u00eb nuk \u00ebsht\u00eb regjistruar sipas rregullave, po p\u00ebrpiqet ta b\u00ebj\u00eb k\u00ebt\u00eb.<\/p>\n<p>Megjithat\u00eb, nga nj\u00eb delta e vog\u00ebl n\u00eb p\u00ebrmasat e rrjetit t\u00eb gjith\u00eb, ne nuk do t\u00eb ikim, pavar\u00ebsisht nga \u00e7do sistem automatizimi dhe dora e fort\u00eb e menaxhimit. P\u00ebr zgjidhjen e problemeve, askush nuk do ta vendos\u00eb konfigurimin n\u00eb sisteme. Sidomos pasi modeli i konfigurimit mund t\u00eb mos e parashikoj\u00eb k\u00ebt\u00eb. <\/p>\n<blockquote><p>P\u00ebr shembull, rregulli i firewall-it p\u00ebr llogaritjen e numrit t\u00eb paketave n\u00eb nj\u00eb IP t\u00eb caktuar, p\u00ebr lokalizimin e problemit \u2014 \u00ebsht\u00eb nj\u00eb konfigurim i p\u00ebrkohsh\u00ebm mjaft normal.\n<\/p><\/blockquote>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/390f78139d336f1fc2c60573bccfe76c.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h2>Komponenti 10. Sistemi i monitorimit<\/h2>\n<p>\nFillimisht, nuk kisha nd\u00ebrmend t\u00eb diskutoja tem\u00ebn e monitorimit \u2014 p\u00ebr shkak se \u00ebsht\u00eb nj\u00eb tem\u00eb e gjer\u00eb, e diskutueshme dhe e komplikuar. Por gjat\u00eb rrug\u00ebs, u shp\u00ebrb\u00eb se ajo \u00ebsht\u00eb nj\u00eb pjes\u00eb e patjet\u00ebrsueshme e automatizimit. Dhe nuk mund ta anashkalosh k\u00ebt\u00eb tem\u00eb edhe pa praktik\u00eb. <\/p>\n<p>Duke zhvilluar mendimin \u2014 ajo \u00ebsht\u00eb nj\u00eb pjes\u00eb organike e procesit CI\/CD. Pas publikimit t\u00eb konfigurimit n\u00eb rrjet, na nevojitet t\u00eb dim\u00eb t\u00eb p\u00ebrcaktojm\u00eb n\u00ebse gjith\u00e7ka \u00ebsht\u00eb n\u00eb rregull tani. <br \/>\nDhe nuk b\u00ebhet fjal\u00eb vet\u00ebm p\u00ebr grafik\u00ebt e p\u00ebrdorimit t\u00eb nd\u00ebrfaqeve ose p\u00ebrDisponibilitetin e nyjeve, por p\u00ebr gj\u00ebra m\u00eb t\u00eb ndjeshme \u2014 pranin\u00eb e rrug\u00ebve t\u00eb duhura, atributeve mbi to, numrin e seancave BGP, fqinj\u00ebve OSPF, funksionalitetin End-to-End t\u00eb sh\u00ebrbimeve m\u00eb t\u00eb larta.<br \/>\nMos ndalojn\u00eb s\u00eb grumbulluari log-et n\u00eb serverin e jasht\u00ebm, a nuk \u00ebsht\u00eb prishur agjenti SFlow, a nuk kan\u00eb filluar t\u00eb rriten drop-et n\u00eb radh\u00eb, a nuk \u00ebsht\u00eb nd\u00ebrlikuar lidhja mes ndonj\u00eb cifti prefix-esh?<\/p>\n<p>N\u00eb nj\u00eb artikull t\u00eb ve\u00e7ant\u00eb do t\u00eb mendojm\u00eb edhe mbi k\u00ebt\u00eb.<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/08aeee4939081abb21e61abadd0ce5de.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr m\u00eb t\u00eb vegjlit. Pjesa zero. Planifikimi\" src=\"\/wp-content\/uploads\/2019\/07\/13c186070c85fd00f7b6923df154f1b6.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h1>P\u00ebrfundim<\/h1>\n<p>\nSi baz\u00eb kam zgjedhur nj\u00eb nga dizajnet modern t\u00eb rrjetit t\u00eb qendr\u00ebs s\u00eb t\u00eb dh\u00ebnave \u2014 L3 Clos Fabric me BGP si protokoll rrug\u00ebzimi.<br \/>\nRrjetin do ta nd\u00ebrtojm\u00eb k\u00ebt\u00eb her\u00eb mbi Juniper, sepse tani nd\u00ebrfare JunOs \u00ebsht\u00eb nj\u00eb lal.<\/p>\n<p>Do ta v\u00ebshtir\u00ebsojm\u00eb jet\u00ebn duke p\u00ebrdorur vet\u00ebm mjete Open Source dhe nj\u00eb rrjet multivendor \u2014 k\u00ebshtu q\u00eb p\u00ebrve\u00e7 Juniper do t\u00eb zgjedh edhe nj\u00eb fatlum tjet\u00ebr n\u00eb proces.<\/p>\n<p>Plani p\u00ebr publikimet e af\u00ebrta \u00ebsht\u00eb rreth k\u00ebsaj:<br \/>\nS\u00eb pari, do t\u00eb flas p\u00ebr rrjetet virtuale. N\u00eb radh\u00eb t\u00eb par\u00eb, sepse m\u00eb p\u00eblqen, dhe n\u00eb t\u00eb dyt\u00eb, sepse pa k\u00ebt\u00eb dizajni i rrjetit infrastrukturor nuk do t\u00eb jet\u00eb shum\u00eb i kuptuesh\u00ebm.<br \/>\nM\u00eb pas, n\u00eb fakt do t\u00eb flas p\u00ebr dizajnin e rrjetit: topologjin\u00eb, rrug\u00ebzimin, politik\u00ebn.<br \/>\nDo t\u00eb grumbullojm\u00eb nj\u00eb laborator.<br \/>\nDo t\u00eb mendojm\u00eb dhe, ndoshta, do t\u00eb praktikojm\u00eb n\u00eb inicializimin e pajisjes n\u00eb rrjet.<br \/>\nDhe m\u00eb pas p\u00ebr \u00e7do komponent n\u00eb detaje intime.<\/p>\n<p>Po ashtu, nuk premtoj q\u00eb do ta p\u00ebrfundoj k\u00ebt\u00eb cik\u00ebl me nj\u00eb zgjidhje t\u00eb gatshme. \ud83d\ude42<\/p>\n<h5>Useful links<\/h5>\n<p><\/p>\n<ul>\n<li>Para se t\u00eb thellohemi n\u00eb k\u00ebt\u00eb seri, ia vlen t\u00eb lexoni librin e Natasha Samoylenko <noindex><a rel=\"nofollow\" href=\"https:\/\/natenka.gitbook.io\/pyneng\/\">Python p\u00ebr inxhinier\u00ebt e rrjetit<\/a><\/noindex>. Dhe, ndoshta, ta kaloni <noindex><a rel=\"nofollow\" href=\"https:\/\/natenka.github.io\/pyneng-online\/\">kursin<\/a><\/noindex>.<\/li>\n<li>Do t\u00eb jet\u00eb gjithashtu e dobishme t\u00eb lexoni <noindex><a rel=\"nofollow\" href=\"https:\/\/tools.ietf.org\/html\/rfc7938\">RFC<\/a><\/noindex> p\u00ebr dizajnin e fabrikave t\u00eb qendr\u00ebs s\u00eb t\u00eb dh\u00ebnave nga Facebook i shkruar nga Petr Lapukhov.<\/li>\n<li>Dokumentacioni mbi arkitektur\u00ebn do t'ju jap\u00eb nj\u00eb pasqyr\u00eb mbi m\u00ebnyr\u00ebn se si funksionon SDN me Overlay. <noindex><a rel=\"nofollow\" href=\"https:\/\/tungstenfabric.github.io\/website\/Tungsten-Fabric-Architecture.html\">Tungsten Fabric<\/a><\/noindex> (m\u00eb par\u00eb Open Contrail).<\/li>\n<\/ul>\n<h5>Faleminderit<\/h5>\n<p>\nRoman Gorge. P\u00ebr komentet dhe ndryshimet.<br \/>\nArtyom Chernobai. P\u00ebr KDPV.<br \/>\n<br \/>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/453516\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0421\u0414\u0421\u041c \u0437\u0430\u043a\u043e\u043d\u0447\u0438\u043b\u0441\u044f, \u0430 \u0431\u0435\u0441\u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u043d\u043e\u0435 \u0436\u0435\u043b\u0430\u043d\u0438\u0435 \u043f\u0438\u0441\u0430\u0442\u044c \u2014 \u043e\u0441\u0442\u0430\u043b\u043e\u0441\u044c. \u0414\u043e\u043b\u0433\u0438\u0435 \u0433\u043e\u0434\u044b \u043d\u0430\u0448 \u0431\u0440\u0430\u0442 \u0441\u0442\u0440\u0430\u0434\u0430\u043b \u043e\u0442 \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u0440\u0443\u0442\u0438\u043d\u043d\u043e\u0439 \u0440\u0430\u0431\u043e\u0442\u044b, \u0441\u043a\u0440\u0435\u0449\u0438\u0432\u0430\u043b \u043f\u0430\u043b\u044c\u0446\u044b \u043f\u0435\u0440\u0435\u0434 \u043a\u043e\u043c\u043c\u0438\u0442\u043e\u043c \u0438 \u043d\u0435\u0434\u043e\u0441\u044b\u043f\u0430\u043b \u0438\u0437-\u0437\u0430 \u043d\u043e\u0447\u043d\u044b\u0445 \u0440\u043e\u043b\u0431\u044d\u043a\u043e\u0432. \u041d\u043e \u0442\u0451\u043c\u043d\u044b\u043c \u0432\u0440\u0435\u043c\u0435\u043d\u0430\u043c \u043f\u0440\u0438\u0445\u043e\u0434\u0438\u0442 \u043a\u043e\u043d\u0435\u0446. \u042d\u0442\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0451\u0439 \u044f \u043d\u0430\u0447\u043d\u0443 \u0441\u0435\u0440\u0438\u044e \u043e \u0442\u043e\u043c, \u043a\u0430\u043a \u043c\u043d\u0435 \u0432\u0438\u0434\u0438\u0442\u0441\u044f \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0437\u0430\u0446\u0438\u044f. \u041f\u043e \u0445\u043e\u0434\u0443 \u0434\u0435\u043b\u0430 \u0440\u0430\u0437\u0431\u0435\u0440\u0451\u043c\u0441\u044f \u0441 \u044d\u0442\u0430\u043f\u0430\u043c\u0438 \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0437\u0430\u0446\u0438\u0438, \u0445\u0440\u0430\u043d\u0435\u043d\u0438\u0435\u043c \u043f\u0435\u0440\u0435\u043c\u0435\u043d\u043d\u044b\u0445, \u0444\u043e\u0440\u043c\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u0435\u0439 \u0434\u0438\u0437\u0430\u0439\u043d\u0430, \u0441 RestAPI, [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":26891,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-35972","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.2 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0421\u0414\u0421\u041c \u0437\u0430\u043a\u043e\u043d\u0447\u0438\u043b\u0441\u044f, \u0430 \u0431\u0435\u0441\u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u043d\u043e\u0435 \u0436\u0435\u043b\u0430\u043d\u0438\u0435 \u043f\u0438\u0441\u0430\u0442\u044c \u2014 \u043e\u0441\u0442\u0430\u043b\u043e\u0441\u044c.\" \/>\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\/sq\/blog\/administrirovanie\/avtomatizatsiya-dlya-samyh-malenkih-chast-nulevaya-planirovanie\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\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\u0410\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0437\u0430\u0446\u0438\u044f \u0434\u043b\u044f \u0441\u0430\u043c\u044b\u0445 \u043c\u0430\u043b\u0435\u043d\u044c\u043a\u0438\u0445. \u0427\u0430\u0441\u0442\u044c \u043d\u0443\u043b\u0435\u0432\u0430\u044f. \u041f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0421\u0414\u0421\u041c \u0437\u0430\u043a\u043e\u043d\u0447\u0438\u043b\u0441\u044f, \u0430 \u0431\u0435\u0441\u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u043d\u043e\u0435 \u0436\u0435\u043b\u0430\u043d\u0438\u0435 \u043f\u0438\u0441\u0430\u0442\u044c \u2014 \u043e\u0441\u0442\u0430\u043b\u043e\u0441\u044c.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/avtomatizatsiya-dlya-samyh-malenkih-chast-nulevaya-planirovanie\" \/>\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=\"2019-10-31T19:08:54+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:08:54+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\udd47Automatizimi p\u00ebr t\u00ebr\u00eb t\u00eb vegj\u00ebl. Pjesa zero. Planifikimi | ProHoster","description":"CDSM ka p\u00ebrfundoi, por d\u00ebshira e pakontrolluar p\u00ebr t\u00eb shkruar ka mbetur.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/avtomatizatsiya-dlya-samyh-malenkih-chast-nulevaya-planirovanie","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sq_AL","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\u0410\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0437\u0430\u0446\u0438\u044f \u0434\u043b\u044f \u0441\u0430\u043c\u044b\u0445 \u043c\u0430\u043b\u0435\u043d\u044c\u043a\u0438\u0445. \u0427\u0430\u0441\u0442\u044c \u043d\u0443\u043b\u0435\u0432\u0430\u044f. \u041f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 | ProHoster","og:description":"\u0421\u0414\u0421\u041c \u0437\u0430\u043a\u043e\u043d\u0447\u0438\u043b\u0441\u044f, \u0430 \u0431\u0435\u0441\u043a\u043e\u043d\u0442\u0440\u043e\u043b\u044c\u043d\u043e\u0435 \u0436\u0435\u043b\u0430\u043d\u0438\u0435 \u043f\u0438\u0441\u0430\u0442\u044c \u2014 \u043e\u0441\u0442\u0430\u043b\u043e\u0441\u044c.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/avtomatizatsiya-dlya-samyh-malenkih-chast-nulevaya-planirovanie","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":"2019-10-31T19:08:54+00:00","article:modified_time":"2019-10-31T19:08:54+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"35972","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":"2026-01-22 01:28:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 09:58:22","updated":"2026-01-22 01:28:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/35972","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=35972"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/35972\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/26891"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=35972"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=35972"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=35972"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}