{"id":35973,"date":"2019-10-31T22:08:54","date_gmt":"2019-10-31T19:08:54","guid":{"rendered":"https:\/\/prohoster.info\/blog\/avtomatizatsiya-dlya-samyh-malenkih-chast-pervaya-kotoraya-posle-nulevoj-virtualizatsiya-seti\/"},"modified":"2019-10-31T22:08:54","modified_gmt":"2019-10-31T19:08:54","slug":"avtomatizatsiya-dlya-samyh-malenkih-chast-pervaya-kotoraya-posle-nulevoj-virtualizatsiya-seti","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/avtomatizatsiya-dlya-samyh-malenkih-chast-pervaya-kotoraya-posle-nulevoj-virtualizatsiya-seti","title":{"rendered":"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>N\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/453516\/\">versionin e kaluar,<\/a><\/noindex> Kam e p\u00ebrshkruar nj\u00eb korniz\u00eb p\u00ebr automatizimin e rrjetit. Nga komentet, disa njer\u00ebz besojn\u00eb se ky qasje fillestare ndaj problemit tashm\u00eb ka ndihmuar p\u00ebr t\u00eb sqaruar disa \u00e7\u00ebshtje. Kjo m\u00eb g\u00ebzon shum\u00eb, sepse q\u00ebllimi yn\u00eb n\u00eb k\u00ebt\u00eb proces nuk \u00ebsht\u00eb t\u00eb mbulojm\u00eb Ansible me skenar\u00eb Python, por t\u00eb ndihmojm\u00eb p\u00ebr t\u00eb nd\u00ebrtuar nj\u00eb sistem.<\/p>\n<p>Kjo korniz\u00eb p\u00ebrcakton rendin n\u00eb t\u00eb cilin do t\u00eb merremi me \u00e7\u00ebshtjen.<br \/>\nDhe virtualizimi i rrjetit, p\u00ebr t\u00eb cilin \u00ebsht\u00eb dedikuar ky edicion, nuk p\u00ebrshtatet shum\u00eb n\u00eb tematik\u00ebn e ADSM-s\u00eb, ku flasim p\u00ebr automatizimin. <\/p>\n<p>Por le t\u00eb shikojm\u00eb at\u00eb nga nj\u00eb k\u00ebndv\u00ebshtrim tjet\u00ebr.<\/p>\n<p>Shum\u00eb sh\u00ebrbime tani p\u00ebrdorin t\u00eb nj\u00ebjtin rrjet. N\u00eb rastin e operatorit t\u00eb komunikimit, kjo \u00ebsht\u00eb 2G, 3G, LTE, SHPD dhe B2B, p\u00ebr shembull. N\u00eb rastin e Qendrave t\u00eb t\u00eb Dh\u00ebnave: lidhshm\u00ebria p\u00ebr klient\u00eb t\u00eb ndrysh\u00ebm, Interneti, ruajtja bllokuese, ruajtja objektesh.<\/p>\n<p>Dhe t\u00eb gjitha sh\u00ebrbimet k\u00ebrkojn\u00eb izolim nga nj\u00ebra-tjetra. K\u00ebshtu u krijuan rrjetet e mbivendosura.<\/p>\n<p>Dhe t\u00eb gjitha sh\u00ebrbimet nuk duan t\u00eb presin derisa nj\u00eb person t'i konfiguroj\u00eb ato manualisht. K\u00ebshtu u krijuan orkestrator\u00ebt dhe SDN.<\/p>\n<p>Qasja e par\u00eb ndaj automatizimit sistematik t\u00eb rrjetit, m\u00eb sakt\u00eb t\u00eb nj\u00eb pjese t\u00eb tij, \u00ebsht\u00eb marr\u00eb prej koh\u00ebsh dhe \u00ebsht\u00eb zbatuar n\u00eb shum\u00eb vende: VMWare, OpenStack, Google Compute Cloud, AWS, Facebook.<\/p>\n<p>Me t\u00eb do t\u00eb merremi sot. <\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/fs.linkmeup.ru\/images\/adsm\/1\/kdpv.jpg\"><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/e0bf73b7b71c383c5526da48a6f6b776.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h1>P\u00ebrmbajtja<\/h1>\n<p><\/p>\n<ul>\n<li><b>Arsyet<\/b><\/li>\n<li><b>Terminologjia<\/b><\/li>\n<li><b>Underlay \u2014 rrjeti fizik<\/b><\/li>\n<li><b>Overlay \u2014 rrjeti virtual<\/b>\n<ul>\n<li>Overlay me ToR-s\u00eb<\/li>\n<li>Overlay nga hosti<\/li>\n<li>N\u00eb shembullin e Tungsten Fabric\n<ul>\n<li>Komunikimi brenda nj\u00eb makine fizike<\/li>\n<li>Komunikimi nd\u00ebrmjet VM-ve t\u00eb vendosura n\u00eb makina fizike t\u00eb ndryshme<\/li>\n<li>Dalja n\u00eb bot\u00ebn e jashtme<\/li>\n<\/ul>\n<p>\n <\/li>\n<\/ul>\n<p>\n <\/li>\n<li><b>FAQ<\/b><\/li>\n<li><b>P\u00ebrfundim<\/b><\/li>\n<li><b>Useful links<\/b><\/li>\n<\/ul>\n<p><\/p>\n<h1>Arsyet<\/h1>\n<p>\nDhe pasi e p\u00ebrmendem k\u00ebt\u00eb, \u00ebsht\u00eb mir\u00eb t\u00eb p\u00ebrmendim edhe parakushtet p\u00ebr virtualizimin e rrjetit. N\u00eb t\u00eb v\u00ebrtet\u00eb, ky proces ka filluar prej koh\u00ebsh. <\/p>\n<p>Ndoshta keni d\u00ebgjuar shum\u00eb her\u00eb se rrjeti gjithmon\u00eb ka qen\u00eb pjesa m\u00eb inerte e \u00e7do sistemi. Dhe kjo \u00ebsht\u00eb e v\u00ebrtet\u00eb n\u00eb t\u00eb gjitha aspektet. Rrjeti \u00ebsht\u00eb baza mbi t\u00eb cil\u00ebn mb\u00ebshtetet gjith\u00e7ka, dhe t\u00eb b\u00ebsh ndryshime n\u00eb t\u00eb \u00ebsht\u00eb mjaft e v\u00ebshtir\u00eb \u2014 sh\u00ebrbimet nuk tolerojn\u00eb kur rrjeti bie. Shpesh, nxjerrja e nj\u00eb nyje nga sh\u00ebrbimi mund t\u00eb d\u00ebmtoj\u00eb shumic\u00ebn e aplikacioneve dhe t\u00eb ndikoj\u00eb n\u00eb shum\u00eb klient\u00eb. Pjes\u00ebrisht p\u00ebr k\u00ebt\u00eb arsye, ekipi i rrjetit mund t\u00eb kund\u00ebrshtoj\u00eb \u00e7do ndryshim \u2014 sepse tani ndonj\u00ebher\u00eb funksionon si\u00e7 duhet (<i>ndoshta madje nuk e dim\u00eb si<\/i>), dhe tani duhet t\u00eb konfigurojm\u00eb di\u00e7ka t\u00eb re, dhe nuk dihet se si do t\u00eb ndikoj\u00eb n\u00eb rrjet.<\/p>\n<p>P\u00ebr t\u00eb mos pritur q\u00eb rrjetar\u00ebt t\u00eb ngrohin VLAN-in dhe t\u00eb mos keni nevoj\u00eb t\u00eb regjistroni \u00e7do sh\u00ebrbim n\u00eb \u00e7do nyje rrjeti, njer\u00ebzit shpik\u00ebn p\u00ebrdorimin e overlay-ve \u2014 rrjete t\u00eb mbuluara \u2014 t\u00eb cilat ofrojn\u00eb nj\u00eb shum\u00ebllojshm\u00ebri t\u00eb madhe: GRE, IPinIP, MPLS, MPLS L2\/L3VPN, VXLAN, GENEVE, MPLSoverUDP, MPLSoverGRE etj.<\/p>\n<p>T\u00ebrheqja e tyre q\u00ebndron n\u00eb dy aspekte t\u00eb thjeshta:<\/p>\n<ul>\n<li>Konfigurohen vet\u00ebm nyjet p\u00ebrfundimtare \u2014 nuk \u00ebsht\u00eb nevoja t\u00eb prekni t\u00eb kaluara. Kjo e p\u00ebrshpejton procesin ndjesh\u00ebm dhe ndonj\u00ebher\u00eb lejon p\u00ebrjashtimin e departamentit t\u00eb infrastruktur\u00ebs rrjet\u00ebsore nga procesi i hyrjes s\u00eb sh\u00ebrbimeve t\u00eb reja.<\/li>\n<li>Ngarkesa \u00ebsht\u00eb e fshehur thell\u00eb brenda titujve \u2014 nyjat kaluese nuk kan\u00eb nevoj\u00eb t\u00eb din\u00eb asgj\u00eb rreth saj, rreth adresave n\u00eb hoste, rrug\u00ebve t\u00eb rrjetit t\u00eb mbuluar. Kjo do t\u00eb thot\u00eb se nevojitet t\u00eb ruajm\u00eb m\u00eb pak informacione n\u00eb tabela, dhe k\u00ebshtu t\u00eb p\u00ebrdorim pajisje m\u00eb t\u00eb thjeshta dhe m\u00eb t\u00eb lira.<\/li>\n<\/ul>\n<p>\nN\u00eb k\u00ebt\u00eb botim jo t\u00eb plot\u00eb nuk kam planifikuar t\u00eb shqyrtoj t\u00eb gjitha teknologjit\u00eb e mundshme, por m\u00eb tep\u00ebr t\u00eb p\u00ebrshkruaj korniz\u00ebn e pun\u00ebs s\u00eb rrjeteve t\u00eb mbuluara n\u00eb QK.<\/p>\n<p>E gjith\u00eb seria do t\u00eb p\u00ebrshkruaj\u00eb nj\u00eb qend\u00ebr t\u00eb t\u00eb dh\u00ebnave, e p\u00ebrb\u00ebr\u00eb nga radh\u00eb stendash homogjene, ku \u00ebsht\u00eb instaluar pajisje serverike t\u00eb nj\u00ebjt\u00eb. <\/p>\n<p>N\u00eb k\u00ebt\u00eb pajisje fillojn\u00eb t\u00eb funksionojn\u00eb makina virtuale\/kontejner\u00eb\/serverless q\u00eb realizojn\u00eb sh\u00ebrbime.<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/a6863eb2804a298304d1e93daecf90d9.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<h1>Terminologjia<\/h1>\n<p>\nN\u00eb cik\u00ebl <b>server<\/b> do ta quaj programin q\u00eb realizon an\u00ebn server t\u00eb komunikat\u00ebs klient-server.<\/p>\n<p>Makinat fizike n\u00eb stenda do t'i quajm\u00eb servera <b>jo<\/b> do t\u00eb jemi.<\/p>\n<p><b>Makin\u00eb fizike<\/b> \u2014 nj\u00eb kompjuter x86 i instaluar n\u00eb nj\u00eb stend\u00eb. Termi m\u00eb i p\u00ebrdorur \u00ebsht\u00eb <b>server<\/b>. K\u00ebshtu do ta quajm\u00eb \"<b>makin\u00eb<\/b>\" ose <b>server<\/b>.<\/p>\n<p><b>Hipervizori<\/b> \u2014 nj\u00eb aplikacion i ekzekutuar n\u00eb makin\u00ebn fizike q\u00eb imiton burimet fizike, mbi t\u00eb cilat ekzekutohet Makina Virtuale. Ndonj\u00ebher\u00eb n\u00eb literatur\u00eb dhe n\u00eb rrjet, fjala \"hipervizor\" p\u00ebrdoret si sinonim p\u00ebr \"host\".<\/p>\n<p><b>Makin\u00eb virtuale<\/b> \u2014 sistemi operativ q\u00eb funksionon mbi makinen fizike p\u00ebr t\u00eb sip\u00ebrm t\u00eb hipervizorit. P\u00ebr ne n\u00eb k\u00ebt\u00eb cik\u00ebl nuk ka shum\u00eb r\u00ebnd\u00ebsi n\u00ebse \u00ebsht\u00eb me t\u00eb v\u00ebrtet\u00eb nj\u00eb makin\u00eb virtuale apo thjesht nj\u00eb konteiner. Do ta quajm\u00eb \"<b>VM<\/b>&#171;<\/p>\n<p><b>Tenant<\/b> \u2014 nj\u00eb term i gjer\u00eb, t\u00eb cilin do ta p\u00ebrcaktoj n\u00eb k\u00ebt\u00eb artikull si nj\u00eb sh\u00ebrbim t\u00eb ve\u00e7ant\u00eb ose nj\u00eb klient t\u00eb ve\u00e7ant\u00eb.<\/p>\n<p><b>Multi-tenancy<\/b> ose multi-qiraja \u2014 p\u00ebrdorimi i s\u00eb nj\u00ebjt\u00ebs aplikacion nga klient\u00eb\/sh\u00ebrbime t\u00eb ndryshme. N\u00eb k\u00ebt\u00eb rast, izolimi i klient\u00ebve nga nj\u00ebri-tjetri arrihet p\u00ebrmes arkitektur\u00ebs s\u00eb aplikacionit, e jo p\u00ebrmes instancave t\u00eb ve\u00e7anta t\u00eb drejtuara ndaras.<\/p>\n<p><b>ToR \u2014 Nd\u00ebrruesi n\u00eb Maj\u00eb t\u00eb Stend\u00ebs<\/b> \u2014 switch mounted in a rack to which all physical machines are connected.<\/p>\n<blockquote><p> In addition to ToR topology, various providers practice End of Row (EoR) or Middle of Row (although the latter is a rare exception, and I have not encountered the abbreviation MoR).\n<\/p><\/blockquote>\n<p> <b>Underlay network<\/b> or underlay network \u2014 the physical network infrastructure: switches, routers, cables.<\/p>\n<p><b>Overlay network<\/b> or overlay network \u2014 a virtual tunnel network operating over the physical network.<\/p>\n<p><b>L3 fabric or IP fabric<\/b> \u2014 a remarkable invention of mankind that allows interviews without repeating STP and learning TRILL. A concept in which the entire network up to the access level is exclusively L3, without VLANs and, consequently, vast broadcast domains. We will address the term \"fabric\" in the next part.<\/p>\n<p><b>SDN<\/b> \u2014 Software Defined Network. It hardly needs an introduction. A network management approach where changes in the network are implemented by a program rather than by a person. Usually means moving the Control Plane outside of the end network devices to a controller.<\/p>\n<p><b>NFV<\/b> \u2014 Network Function Virtualization \u2014 virtualization of network devices, suggesting that some network functions can be run as virtual machines or containers to accelerate the deployment of new services, organize Service Chaining, and enable easier horizontal scalability.<\/p>\n<p><b>VNF<\/b> \u2014 Virtual Network Function. A specific virtual device: router, switch, firewall, NAT, IPS\/IDS, etc.<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/971b6a28a9caab5f3a7067ce4d25749c.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<blockquote><p> I am intentionally simplifying the description to a specific implementation so as not to confuse the reader. For a more thoughtful read, I refer him to the section <noindex><a rel=\"nofollow\" href=\"#LINKS\">Linket<\/a><\/noindex>. In addition, Roma Gorg\u00e9, who criticizes this article for inaccuracies, promises to write a separate issue about server and network virtualization technologies, with more depth and attention to detail.<\/p><\/blockquote>\n<p>Most networks today can clearly be divided into two parts: <\/p>\n<p><b>Underlay<\/b> \u2014 a physical network with a stable configuration.<br \/>\n<b>Overlay<\/b> \u2014 abstraction over Underlay for tenant isolation. <\/p>\n<p>This is true for the case of DC (which we will discuss in this article), as well as for ISP (which we will not address because it has already been covered in <noindex><a rel=\"nofollow\" href=\"https:\/\/linkmeup.ru\/sdsm\">SDN<\/a><\/noindex>). With enterprise networks, of course, the situation is somewhat different. <\/p>\n<p>A picture focused on the network:<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/7b7dabc6d9f3b87c598346bf9195d568.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<p><\/p>\n<h1>Underlay<\/h1>\n<p>\nUnderlay \u2014 \u00ebsht\u00eb nj\u00eb rrjet fizik: \u00e7switch-e dhe kabllo hardware. Pajisjet n\u00eb underlay din\u00eb si t\u00eb arrijn\u00eb n\u00eb makinat fizike.<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/776a77a3821fe79a7323947e0bdf67e8.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nAi mb\u00ebshtetet n\u00eb protokollet dhe teknologjit\u00eb standarde. Jo n\u00eb m\u00ebnyr\u00eb t\u00eb fundit, sepse pajisjet hardware vazhdojn\u00eb t\u00eb funksionojn\u00eb me softuer t\u00eb pron\u00ebsish\u00ebm, q\u00eb nuk lejon as programimin e \u00e7ipave, as implementimin e protokolleve t\u00eb tij, p\u00ebrkat\u00ebsisht \u00ebsht\u00eb e nevojshme t\u00eb ket\u00eb p\u00ebrputhshm\u00ebri me furnizues t\u00eb tjer\u00eb dhe standardizim.<\/p>\n<blockquote><p>Por dikush si Google mund t\u00eb krijoj\u00eb \u00e7switch-e t\u00eb tij dhe t\u00eb heq\u00eb dor\u00eb nga protokollet e pranuara. Por LAN_DC nuk \u00ebsht\u00eb Google.\n<\/p><\/blockquote>\n<p> Underlay rrall\u00eb ndryshohet, sepse detyra e tij \u00ebsht\u00eb \u2014 lidhja baz\u00eb IP mes makinave fizike. Underlay nuk di asgj\u00eb p\u00ebr sh\u00ebrbimet, klient\u00ebt, dhe tenant\u00ebt q\u00eb funksionojn\u00eb mbi t\u00eb \u2014 ai ka vet\u00ebm nevoj\u00eb t\u00eb dor\u00ebzoj\u00eb paketat nga nj\u00eb makin\u00eb n\u00eb tjetr\u00ebn.<br \/>\nUnderlay mund t\u00eb duket k\u00ebshtu: <\/p>\n<ul>\n<li>IPv4+OSPF<\/li>\n<li>IPv6+ISIS+BGP+L3VPN<\/li>\n<li>L2+TRILL<\/li>\n<li>L2+STP<\/li>\n<\/ul>\n<p>\nRrjeti Underlay konfigurohet n\u00eb m\u00ebnyr\u00eb tradicionale: CLI\/GUI\/NETCONF.<\/p>\n<p>Duar, skenar\u00eb, mjete pron\u00ebsore.<\/p>\n<p>Nj\u00eb artikull m\u00eb i detajuar do t'i kushtohet underlay n\u00eb ciklin e ardhsh\u00ebm.<\/p>\n<p><\/p>\n<h1>Overlay<\/h1>\n<p>\nOverlay \u2014 nj\u00eb rrjet virtual tunelesh, i tendosur mbi Underlay, ai lejon q\u00eb VM-t\u00eb e nj\u00eb klienti t\u00eb komunikojn\u00eb mes tyre, duke siguruar izolim nga klient\u00ebt e tjer\u00eb.<\/p>\n<p>T\u00eb dh\u00ebnat e klient\u00ebve inkapsulohen n\u00eb ndonj\u00eb titull tunelimi p\u00ebr t'u d\u00ebrguar p\u00ebrmes rrjetit t\u00eb p\u00ebrbashk\u00ebt.<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/3060bc4913c55c21b785083fbe0b603b.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nK\u00ebshtu, VM-t\u00eb e nj\u00eb klienti (nj\u00eb sh\u00ebrbimi) mund t\u00eb komunikojn\u00eb mes tyre p\u00ebrmes Overlay, madje pa e ditur se cila \u00ebsht\u00eb rruga reale q\u00eb ndjek paketa. <\/p>\n<p>Overlay mund t\u00eb duket k\u00ebshtu, si\u00e7 e p\u00ebrmenda m\u00eb lart:<\/p>\n<ul>\n<li>Tuneli GRE<\/li>\n<li>VXLAN<\/li>\n<li>EVPN<\/li>\n<li>L3VPN<\/li>\n<li>GENEVE<\/li>\n<\/ul>\n<p>\nRrjeti Overlay zakonisht konfigurohet dhe mb\u00ebshtetet p\u00ebrmes nj\u00eb kontrolluesi qendror. Nga aty, konfigurimi, Control Plane dhe Data Plane d\u00ebrgohen n\u00eb pajisjet q\u00eb merret me ruterimin dhe kapsulimin e trafikut t\u00eb klient\u00ebve. Pak <noindex><a rel=\"nofollow\" href=\"#TF\">m\u00eb posht\u00eb<\/a><\/noindex> do ta analizojm\u00eb k\u00ebt\u00eb me shembuj.<\/p>\n<p><b>Po, kjo \u00ebsht\u00eb SDN n\u00eb form\u00ebn e saj t\u00eb past\u00ebr. <\/b><\/p>\n<p>Ekzistojn\u00eb dy qasje q\u00eb ndryshojn\u00eb n\u00eb m\u00ebnyr\u00eb thelb\u00ebsore p\u00ebr organizimin e rrjetit Overlay:<\/p>\n<ol>\n<li>Overlay me ToR-s\u00eb<\/li>\n<li>Overlay nga hosti<\/li>\n<\/ol>\n<h2>Overlay me ToR-s\u00eb<\/h2>\n<p>\nOverlay mund t\u00eb filloj\u00eb n\u00eb \u00e7switch-in e qasjes (ToR), q\u00eb ndodhet n\u00eb raft, si\u00e7 ndodh, p\u00ebr shembull, n\u00eb rastin e fabrik\u00ebs VXLAN. <\/p>\n<p>Ky \u00ebsht\u00eb nj\u00eb mekaniz\u00ebm i v\u00ebrtetuar me kalimin e koh\u00ebs n\u00eb rrjetet ISP dhe t\u00eb gjith\u00eb furnizuesit e pajisjeve rrjetore e mb\u00ebshtesin.<\/p>\n<p>Megjithat\u00eb, n\u00eb k\u00ebt\u00eb rast, kall\u00ebpi ToR duhet t\u00eb jet\u00eb n\u00eb gjendje t\u00eb ndaj\u00eb sh\u00ebrbimet e ndryshme, prandaj administratori i rrjetit duhet t\u00eb bashk\u00ebpunoj\u00eb n\u00eb nj\u00ebfar\u00eb mase me administrator\u00ebt e makinave virtuale dhe t\u00eb b\u00ebj\u00eb ndryshimet (ndon\u00ebse automatikisht) n\u00eb konfigurimin e pajisjeve.<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/9a5fe4d4a0cbb7e5c3bbac82527c6a6a.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nK\u00ebtu dua t\u00eb rekomandoj lexuesin n\u00eb artikullin mbi <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/344326\/\">VxLAN n\u00eb Habr<\/a><\/noindex> miqt\u00eb tan\u00eb t\u00eb vjet\u00ebr <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/users\/bormoglotx\/\">@bormoglotx<\/a><\/noindex>.<br \/>\nN\u00eb k\u00ebt\u00eb <noindex><a rel=\"nofollow\" href=\"https:\/\/www.enog.org\/wp-content\/uploads\/presentations\/enog-16\/18-Scaleway-P14-fabric-ENOG16.pdf\">prezantimet nga ENOG<\/a><\/noindex> p\u00ebrshkruhen n\u00eb detaje qasjet p\u00ebr nd\u00ebrtimin e rrjetit t\u00eb DC me fabrik\u00ebn EVPN VXLAN. <\/p>\n<p>Dhe p\u00ebr nj\u00eb zhytje m\u00eb t\u00eb plot\u00eb n\u00eb realitet, mund t\u00eb lexoni librin e Cisco <noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/dam\/en\/us\/td\/docs\/switches\/datacenter\/nexus9000\/sw\/vxlan_evpn\/VXLAN_EVPN.pdf\">A Modern, Open, and Scalable Fabric: VXLAN EVPN<\/a><\/noindex>.<\/p>\n<blockquote><p> V\u00ebrej se VXLAN \u00ebsht\u00eb vet\u00ebm nj\u00eb metod\u00eb kapsulimi dhe terminimi i tuneleve mund t\u00eb ndodh\u00eb jo te ToR, por te host-i, si\u00e7 ndodh n\u00eb rastin e OpenStack, p\u00ebr shembull.<\/p>\n<p>Megjithat\u00eb, VXLAN-fabrika, ku overlay fillon te ToR \u00ebsht\u00eb nj\u00eb nga dizajnet tradicionale t\u00eb rrjetit overlay.\n<\/p><\/blockquote>\n<p><\/p>\n<h2>Overlay nga hosti<\/h2>\n<p>\nQasja tjet\u00ebr \u00ebsht\u00eb t\u00eb filloni dhe t\u00eb terminoni tunelet n\u00eb hostet p\u00ebrfundimtare.<br \/>\nN\u00eb k\u00ebt\u00eb rast, rrjeti (Underlay) mbetet sa m\u00eb i thjesht\u00eb dhe statik.<br \/>\nDhe hosti vet\u00eb b\u00ebn t\u00eb gjitha enkapsulimet e nevojshme.<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/c9c2971369d1b3e5f026d6844afeb67f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nP\u00ebr k\u00ebt\u00eb, pa dyshim, do t\u00eb nevojitet t\u00eb ekzistoj\u00eb nj\u00eb aplikacion i ve\u00e7ant\u00eb n\u00eb hoste, por ia vlen. <\/p>\n<p>S\u00eb pari, t\u00eb fillosh klientin n\u00eb nj\u00eb makin\u00eb Linux \u00ebsht\u00eb m\u00eb e thjesht\u00eb ose, t\u00eb themi, e mundur \u2014 nd\u00ebrsa n\u00eb ndSwitch, ndoshta, do t\u00eb duhet t\u00eb p\u00ebrdor\u00ebsh ende zgjidhje SDN pron\u00ebsore, q\u00eb shkat\u00ebrron iden\u00eb e multi-marr\u00ebsis\u00eb.<\/p>\n<p>S\u00eb dyti, switch-i ToR n\u00eb k\u00ebt\u00eb rast mund t\u00eb mbetet sa m\u00eb i thjesht\u00eb, si nga perspektiva e Control Plane, ashtu edhe nga ai i Data Plane. N\u00eb t\u00eb v\u00ebrtet\u00eb \u2014 me kontrolluesin SDN, ai nuk ka nevoj\u00eb t\u00eb komunikoj\u00eb dhe t\u00eb ruaj\u00eb rrjetet\/ARP-t\u00eb e t\u00eb gjith\u00eb klient\u00ebve t\u00eb lidhur \u2014 \u00ebsht\u00eb e mjaftueshme t\u00eb dihet adresa IP e makines fizike, gj\u00eb q\u00eb e leht\u00ebson shum\u00eb tabelat e kalimit\/ruterimit.<\/p>\n<p>\nN\u00eb serin\u00eb ADSM zgjedh qasjen e overlay nga hosti - m\u00eb tej ne do t\u00eb flasim vet\u00ebm p\u00ebr t\u00eb dhe nuk do t\u00eb kthehemi m\u00eb n\u00eb fabrik\u00ebn VXLAN.<\/p>\n<p>\nM\u00eb s\u00eb lehti mund ta shqyrtojm\u00eb me shembuj. Dhe si subjekt do t\u00eb marrim platform\u00ebn SDN me burim t\u00eb hapur OpenContrail, tani e njohur si <noindex><a rel=\"nofollow\" href=\"https:\/\/tungsten.io\">Tungsten Fabric<\/a><\/noindex>.<\/p>\n<blockquote><p> N\u00eb fund t\u00eb artikullit do t\u00eb jap disa mendime mbi analogjin\u00eb me OpenFlow dhe OpenvSwitch.\n<\/p><\/blockquote>\n<p><\/p>\n<h2>N\u00eb shembullin e Tungsten Fabric<\/h2>\n<p>\nN\u00eb \u00e7do makin\u00eb fizike ka <b>vRouter<\/b> \u2014 ruter virtual, i cili di p\u00ebr rrjetet e lidhura me t\u00eb dhe se cilit klient i p\u00ebrkasin ato \u2014 n\u00eb thelb \u2014 ruter PE. P\u00ebr \u00e7do klient, ai mb\u00ebshtet nj\u00eb tabel\u00eb ruterimi t\u00eb izoluar (lexo VRF). Dhe v\u00ebrtet\u00eb ruter v b\u00ebn tunelimin Overlay.<\/p>\n<p>Pak m\u00eb n\u00eb detaje p\u00ebr rrug\u00ebzuesin \u2014 n\u00eb fund t\u00eb artikullit.<\/p>\n<p>\u00c7do VM e vendosur mbi hipervizorin \u00ebsht\u00eb e lidhur me vRouter-in e k\u00ebsaj makine p\u00ebrmes <noindex><a rel=\"nofollow\" href=\"https:\/\/en.wikipedia.org\/wiki\/TUN\/TAP\">TAP-interfejsi<\/a><\/noindex>.<\/p>\n<p><b>TAP<\/b> \u2014 Terminal Access Point \u2014 nj\u00eb interfejs virtual n\u00eb kernelin Linux, i cili lejon nd\u00ebrveprimin rrjetor.<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/a6fa1b4370ba4e787303ae647a28f5ed.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nN\u00ebse pas vRouter-it jan\u00eb disa rrjete, p\u00ebr secil\u00ebn prej tyre krijohet nj\u00eb nd\u00ebrfaqe virtuale, n\u00eb t\u00eb cil\u00ebn i caktohet nj\u00eb adres\u00eb IP \u2014 ajo do t\u00eb jet\u00eb adresa e der\u00ebs p\u00ebr default.<br \/>\nT\u00eb gjitha rrjetet e nj\u00eb klienti vendosen n\u00eb nj\u00eb <b>VRF<\/b> (nj\u00eb tav\u00eb), ato t\u00eb ndryshme \u2014 n\u00eb t\u00eb ndryshme.<br \/>\n<i>K\u00ebtu do t\u00eb b\u00ebj nj\u00eb sqarim, q\u00eb nuk \u00ebsht\u00eb gjith\u00e7ka kaq e thjesht\u00eb, dhe do ta d\u00ebrgoj lexuesin kureshtar n\u00eb fund t\u00eb artikullit.<\/i>.<\/p>\n<p>Q\u00eb vRouter-at t\u00eb mund t\u00eb komunikojn\u00eb me nj\u00ebri-tjetrin, dhe p\u00ebr rrjedhoj\u00eb edhe VM-t\u00eb q\u00eb ndodhen pas tyre, ata ndajn\u00eb informacionin e rrug\u00ebs p\u00ebrmes <b>SDN-kontrollerit.<\/b>.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/fs.linkmeup.ru\/images\/adsm\/1\/sdn-controller.png\"><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/8b133e10582dbde9c0670ad98c1840de.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p>P\u00ebr t'u zb\u00ebrthyer n\u00eb bot\u00ebn e jashtme, ekziston nj\u00eb pik\u00ebdalje nga matrica \u2014 porti i rrjetit virtual <b>VNGW<\/b> \u2014 Virtual Network GateWay (<i>termi im<\/i>).<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/fs.linkmeup.ru\/images\/adsm\/1\/vngw.png\"><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/9ac4d084d9b58b7ed1bc2c0ed6d06059.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p>\nTani le t\u00eb shqyrtojm\u00eb shembujt e komunikimeve \u2014 dhe do t\u00eb jet\u00eb e qart\u00eb.<\/p>\n<p><\/p>\n<h3>Komunikimi brenda nj\u00eb makine fizike<\/h3>\n<p>\nVM0 d\u00ebshiron t\u00eb d\u00ebrgoj\u00eb nj\u00eb paket\u00eb n\u00eb VM2. Supozojm\u00eb p\u00ebr tani, se k\u00ebto jan\u00eb VM t\u00eb nj\u00eb klienti.<\/p>\n<h4>Data Plane<\/h4>\n<p><\/p>\n<ol>\n<li>VM0 ka nj\u00eb rrug\u00eb t\u00eb parazgjedhur n\u00eb interfejsin e tij eth0. Paketa d\u00ebrgohet atje.<br \/>\n Ky interfejs eth0 n\u00eb t\u00eb v\u00ebrtet\u00eb \u00ebsht\u00eb virtualisht i lidhur me rrug\u00ebzuesin virtual vRouter p\u00ebrmes TAP-interfejsit tap0.<\/li>\n<li>Rrug\u00ebzuesi analizon se n\u00eb cilin interfejs ka ardhur paketa, pra p\u00ebr cilin klient (VRF) i takon, dhe krahason adres\u00ebn e marr\u00ebsit me tav\u00ebn e rrug\u00ebzimit t\u00eb k\u00ebtij klienti.<\/li>\n<li>Duke zbuluar se marr\u00ebsi \u00ebsht\u00eb n\u00eb k\u00ebt\u00eb makin\u00eb n\u00eb nj\u00eb port tjet\u00ebr, vRouter-i thjesht d\u00ebrgon paket\u00ebn n\u00eb t\u00eb pa asnj\u00eb titull shtes\u00eb \u2014 p\u00ebr k\u00ebt\u00eb rast vRouter-i ka nj\u00eb regjistrim ARP. <\/li>\n<\/ol>\n<p>\n<img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/a42da3f48a3f538eb92c1908d9d66921.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPaketa n\u00eb k\u00ebt\u00eb rast nuk hyn n\u00eb rrjetin fizik - ai \u00ebsht\u00eb ruterizuar brenda vRouter-it.<\/p>\n<p><\/p>\n<h4>Control Plane<\/h4>\n<p>\nHipervizori, gjat\u00eb ndezjes s\u00eb makin\u00ebs virtuale, i komunikon asaj:<\/p>\n<ul>\n<li>Adres\u00ebn e saj IP.<\/li>\n<li>Rruga e paracaktuar - p\u00ebrmes adres\u00ebs IP t\u00eb vRouter-it n\u00eb k\u00ebt\u00eb rrjet.<\/li>\n<\/ul>\n<p>\nvRouter-i p\u00ebrmes nj\u00eb API t\u00eb ve\u00e7ant\u00eb i komunikon hipervizorit:<\/p>\n<ul>\n<li>\u00c7far\u00eb duhet t\u00eb krijohet si nj\u00eb interfejs virtual.<\/li>\n<li>\u00c7far\u00eb Virtual Network duhet t\u00eb krijohet p\u00ebr t\u00eb.<\/li>\n<li>Me cilin VRF duhet t\u00eb lidhet (VN).<\/li>\n<li>Regjistrimi ARP statik p\u00ebr k\u00ebt\u00eb VM \u2014 cilit nd\u00ebrfaqe i p\u00ebrket adresa e saj IP dhe n\u00eb cilit MAC adresa \u00ebsht\u00eb e lidhur.<\/li>\n<\/ul>\n<p><\/p>\n<blockquote><p> S\u00ebrish, procedura reale e nd\u00ebrveprimit \u00ebsht\u00eb thjeshtuar n\u00eb funksion t\u00eb kuptimit t\u00eb konceptit.\n<\/p><\/blockquote>\n<p> <img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/593d7ad41782e882a88732b475bf91cb.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nK\u00ebshtu, t\u00eb gjitha VM-t\u00eb e nj\u00eb klienti n\u00eb k\u00ebt\u00eb makin\u00eb vRouter i sheh si rrjete t\u00eb drejtp\u00ebrdrejta t\u00eb lidhura dhe mund t\u00eb rutesh vet\u00eb mes tyre.<\/p>\n<p>\nVM0 dhe VM1 i p\u00ebrkasin klient\u00ebve t\u00eb ndrysh\u00ebm, prandaj jan\u00eb n\u00eb tabela t\u00eb ndryshme t\u00eb vRouter-it.<\/p>\n<p>A do t\u00eb mund t\u00eb komunikojn\u00eb drejtp\u00ebrdrejt me nj\u00ebri-tjetrin varet nga konfigurimet e vRouter dhe dizajni i rrjetit.<br \/>\nP\u00ebr shembull, n\u00ebse VM-t\u00eb e t\u00eb dy klient\u00ebve p\u00ebrdorin adresa publike, ose NAT ndodh n\u00eb vRouter-in e vet, at\u00ebher\u00eb mund t\u00eb b\u00ebhet edhe ruterizimi i drejtp\u00ebrdrejt\u00eb n\u00eb vRouter.<\/p>\n<p>N\u00eb situata t\u00eb tjera, mund t\u00eb ndodhin kryq\u00ebzime t\u00eb hap\u00ebsirave adresave \u2014 duhet t\u00eb kaloni p\u00ebrmes nj\u00eb serveri NAT q\u00eb t\u00eb merrni nj\u00eb adres\u00eb publike \u2014 kjo duket si nj\u00eb dalje n\u00eb rrjetet e jashtme, p\u00ebr t\u00eb cilat do t\u00eb flasim m\u00eb posht\u00eb.<\/p>\n<h3>Komunikimi nd\u00ebrmjet VM-ve t\u00eb vendosura n\u00eb makina fizike t\u00eb ndryshme<\/h3>\n<p><\/p>\n<h4>Data Plane<\/h4>\n<p><\/p>\n<ol>\n<li>Fillimi \u00ebsht\u00eb plot\u00ebsisht i nj\u00ebjt\u00eb: VM-0 d\u00ebrgon nj\u00eb paket\u00eb me adres\u00ebn e VM-7 (172.17.3.2) sipas parazgjedhjes s\u00eb saj.<\/li>\n<li>vRouter e merr at\u00eb dhe k\u00ebt\u00eb her\u00eb sheh q\u00eb adresati ndodhet n\u00eb nj\u00eb makin\u00eb tjet\u00ebr dhe \u00ebsht\u00eb i aksesuesh\u00ebm p\u00ebrmes tunelit Tunnel0.<\/li>\n<li>Fillimisht, ai vendos nj\u00eb etiket\u00eb MPLS, q\u00eb identifikon nd\u00ebrfaqen e larg\u00ebt, n\u00eb m\u00ebnyr\u00eb q\u00eb nga ana tjet\u00ebr vRouter t\u00eb mund t\u00eb p\u00ebrcaktoj\u00eb se ku duhet t\u00eb vendoset kjo paket\u00eb pa nevoj\u00ebn p\u00ebr l\u00ebvizje shtes\u00eb.\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/fs.linkmeup.ru\/images\/adsm\/1\/inter-hv-dp.png\"><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/1e159049376e2bf458b8c6cb5878cc17.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex>\n <\/li>\n<li>Tunnel0 ka burim 10.0.0.2, marr\u00ebs: 10.0.1.2.<br \/>\n vRouter shton kokat GRE (ose UDP) dhe nj\u00eb IP t\u00eb re n\u00eb paket\u00ebn origjinale.<\/li>\n<li>N\u00eb tabel\u00ebn e rrug\u00ebs vRouter ka nj\u00eb rrug\u00eb p\u00ebrfundimtare p\u00ebrmes adres\u00ebs ToR1 10.0.0.1. Aty e d\u00ebrgon.\n<p> <img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/8cb98a8ec43d202259acf6a1fcaeb3ee.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n \n <\/li>\n<li>ToR1 si pjes\u00eb e rrjetit Underlay e di (p\u00ebr shembull, p\u00ebrmes OSPF) se si t\u00eb arrij\u00eb n\u00eb 10.0.1.2, dhe d\u00ebrgon paket\u00ebn p\u00ebrmes rrug\u00ebs. Vini re se k\u00ebtu aktivizohet ECMP. N\u00eb ilustro, ka dy next-hop dhe fluxet e ndryshme do t\u00eb shp\u00ebrndahen n\u00eb to sipas hash-it. N\u00eb rastin e nj\u00eb fabrike reale, do t\u00eb kishte me shum\u00eb se 4 next-hop.\n<p>N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, ai nuk ka nevoj\u00eb t\u00eb dij\u00eb se \u00e7far\u00eb ndodhet n\u00ebn kok\u00ebn e jashtme IP. Pra, faktikisht n\u00ebn IP mund t\u00eb jet\u00eb nj\u00eb sandui\u00e7 nga IPv6 mbi MPLS mbi Ethernet mbi MPLS mbi GRE mbi mbi mbi Grek.<\/li>\n<li>P\u00ebr pasoj\u00eb, n\u00eb an\u00ebn e pranimit vRouter heq GRE-n\u00eb dhe p\u00ebrmes etiket\u00ebs MPLS kupton n\u00eb cilin nd\u00ebrfaqe duhet t\u00eb dor\u00ebzoj\u00eb k\u00ebt\u00eb paket\u00eb, e ndan at\u00eb dhe e d\u00ebrgon n\u00eb form\u00ebn e saj origjinale te marr\u00ebsi.<\/li>\n<\/ol>\n<h4>Control Plane<\/h4>\n<p>\nKur \u00ebsht\u00eb aktivizuar makina, ndodhin t\u00eb gjitha ato q\u00eb jan\u00eb p\u00ebrshkruar m\u00eb lart.<\/p>\n<p>Dhe plus edhe kjo:<\/p>\n<ul>\n<li>P\u00ebr \u00e7do klient, vRouter i dedikon nj\u00eb etiket\u00eb MPLS. Kjo \u00ebsht\u00eb nj\u00eb etiket\u00eb sh\u00ebrbimi L3VPN, sipas s\u00eb cil\u00ebs klient\u00ebt do t\u00eb ndahen brenda nj\u00eb makine fizike.<br \/>\n<blockquote><p> N\u00eb t\u00eb v\u00ebrtet\u00eb, MPLS-etiketa p\u00ebrshkruhet nga vRouter-i gjithmon\u00eb pa p\u00ebrjashtime - sepse nuk dihet paraprakisht n\u00ebse makina do t\u00eb interaktoj\u00eb vet\u00ebm me makinat e tjera n\u00ebn t\u00eb nj\u00ebjtin vRouter dhe ndoshta nuk \u00ebsht\u00eb k\u00ebshtu. \n <\/p><\/blockquote>\n<\/li>\n<li>vRouter krijon nj\u00eb lidhje me SDN-kontrollorin n\u00ebp\u00ebrmjet protokollit BGP (ose nj\u00eb protokolli t\u00eb ngjash\u00ebm \u2014 n\u00eb rastin e TF, \u00ebsht\u00eb XMPP 0_o).<\/li>\n<li>P\u00ebrmes k\u00ebsaj seance, vRouter i komunikon SDN-kontrollorit rrug\u00ebt drejt rrjeteve t\u00eb lidhura:\n<ul>\n<li>Adresa e rrjetit<\/li>\n<li>Metoda e kapjes (MPLSoGRE, MPLSoUDP, VXLAN)<\/li>\n<li>Etiketa MPLS e klientit<\/li>\n<li>IP-adresa e tij si nexthop<\/li>\n<\/ul>\n<p>\n <\/li>\n<li>SDN-kontrolleri merr k\u00ebto rrug\u00eb nga t\u00eb gjitha vRouter-at e lidhur dhe i reflekton ato tek t\u00eb tjer\u00ebt. Pra, ai funksionon si Route Reflector.<\/li>\n<\/ul>\n<p>\nE nj\u00ebjta gj\u00eb ndodh edhe n\u00eb an\u00ebn tjet\u00ebr.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/fs.linkmeup.ru\/images\/adsm\/1\/inter-hv-cp.png\"><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/feef9181133f3a50a5cb21aa7ba16dc0.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p>Overlay mund t\u00eb ndryshoj\u00eb \u00e7do minut\u00eb. Af\u00ebrsisht ashtu ndodh n\u00eb re publike, kur klient\u00ebt rregullisht nisin dhe ndalin makinat e tyre virtuale.<\/p>\n<p>Kontrollori qendror merr p\u00ebrsip\u00ebr t\u00eb gjitha v\u00ebshtir\u00ebsit\u00eb me mb\u00ebshtetje t\u00eb konfigurimit dhe kontrollin e tabelave t\u00eb komutimit\/rutimit n\u00eb vRouter.<\/p>\n<p>N\u00ebse flasim p\u00ebr t\u00eb thjesht\u00eb, at\u00ebher\u00eb kontrolluesi lidh\u00ebt me t\u00eb gjith\u00eb vRouter-at p\u00ebrmes BGP (ose nj\u00eb protokolli t\u00eb ngjash\u00ebm) dhe thjesht transmeton informacionin e rrug\u00ebs. BGP, p\u00ebr shembull, tashm\u00eb ka Address-Family p\u00ebr t\u00eb transmetuar metod\u00ebn e inkapsulimit. <noindex><a rel=\"nofollow\" href=\"https:\/\/tools.ietf.org\/html\/rfc4023\">MPLS-in-GRE<\/a><\/noindex> ose <noindex><a rel=\"nofollow\" href=\"https:\/\/tools.ietf.org\/html\/rfc7510\">MPLS-in-UDP<\/a><\/noindex>.<\/p>\n<p>N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, konfiguracioni i Underlay-rete nuk ndryshon n\u00eb asnj\u00eb m\u00ebnyr\u00eb, q\u00eb p\u00ebr m\u00eb tep\u00ebr, \u00ebsht\u00eb shum\u00eb m\u00eb e nd\u00ebrlikuar p\u00ebr t'u automatizuar, nd\u00ebrsa shkat\u00ebrrimi i saj me nj\u00eb l\u00ebvizje t\u00eb pakujdesshme \u00ebsht\u00eb m\u00eb i leht\u00eb.<\/p>\n<h3>Dalja n\u00eb bot\u00ebn e jashtme<\/h3>\n<p>\nDiku simulimi duhet t\u00eb p\u00ebrfundoj\u00eb, dhe nga bota virtuale duhet t\u00eb dilet n\u00eb t\u00eb v\u00ebrtet\u00eb. Dhe nevojitet nj\u00eb taksifon kalimi.<\/p>\n<p>Praktikohen dy qasje:<\/p>\n<ol>\n<li>Instalohet nj\u00eb router hardware.<\/li>\n<li>Nis nj\u00eb ndonj\u00eb aparat q\u00eb realizon funksionet e router-it (po, pas SDN-s\u00eb, ne u p\u00ebrball\u00ebm edhe me VNF). Ta quajm\u00eb at\u00eb kalimi virtual.<\/li>\n<\/ol>\n<p><\/p>\n<blockquote><p> Avantazhi i qasjes s\u00eb dyt\u00eb \u00ebsht\u00eb n\u00eb shkall\u00ebzimin horizontal t\u00eb lir\u00eb \u2014 n\u00ebse fuqia nuk mjafton \u2014 nisni nj\u00eb tjet\u00ebr virtual me kalimin. N\u00eb \u00e7do makin\u00eb fizike, pa nevoj\u00ebn p\u00ebr t\u00eb k\u00ebrkuar rafte t\u00eb lira, nj\u00ebsit\u00eb, linjat e energjis\u00eb, blerjen e pajisjeve, transportimin e saj, instalimin, lidhjen, konfiguroj dhe pastaj edhe z\u00ebvend\u00ebsimin e komponenteve t\u00eb d\u00ebmshme.<\/p>\n<p>Megjithat\u00eb, disavantazhet e nj\u00eb kalimi virtual jan\u00eb se nj\u00eb nj\u00ebsi fizike routeri \u00ebsht\u00eb shum\u00eb m\u00eb e fuqishme se nj\u00eb virtual shum\u00eb-b\u00ebrthamore dhe softueri i saj, i p\u00ebrshtatur p\u00ebr baz\u00ebn e saj harduerike, punon ndjesh\u00ebm m\u00eb stabilisht (<i>jo<\/i>). \u00cbsht\u00eb e v\u00ebshtir\u00eb t\u00eb mohohet edhe fakti se kompleksiteti softuerik-harduerik thjesht funksionon, duke k\u00ebrkuar vet\u00ebm konfigurimin, nd\u00ebrsa nisja dhe mbajtja e kalimit virtual \u00ebsht\u00eb nj\u00eb aktivitet p\u00ebr inxhinier\u00eb t\u00eb fort\u00eb.\n<\/p><\/blockquote>\n<p> Nj\u00eb k\u00ebmb\u00eb e kalimit shikon n\u00eb rrjetin virtual Overlay, si nj\u00eb Makin\u00eb Virtuale e zakonshme, dhe mund t\u00eb interaktoj\u00eb me t\u00eb gjitha VM tjera. N\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, ajo mund t\u00eb p\u00ebrfundoj\u00eb n\u00eb vetvete rrjetet e t\u00eb gjith\u00eb klient\u00ebve dhe, p\u00ebr pasoj\u00eb, t\u00eb realizoj\u00eb rrug\u00ebzimin midis tyre.<\/p>\n<p>K\u00ebmb\u00eb e tij tjet\u00ebr shikon n\u00eb rrjetin kryesor dhe e di se si t\u00eb dal\u00eb n\u00eb Internet.<\/p>\n<p><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/552fa0428ff8dd3aed76091a86a72109.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/p>\n<h4>Data Plane<\/h4>\n<p>\nPra, procesi duket k\u00ebshtu: <\/p>\n<ol>\n<li>VM-0, duke pasur default n\u00eb t\u00eb nj\u00ebjtin vRouter, d\u00ebrgon nj\u00eb paket\u00eb me adresat n\u00eb bot\u00ebn e jashtme (185.147.83.177) n\u00eb nd\u00ebrfaqen eth0.<\/li>\n<li>vRouter merr k\u00ebt\u00eb paket\u00eb dhe b\u00ebn nj\u00eb lookup t\u00eb adres\u00ebs s\u00eb destinacionit n\u00eb tabel\u00ebn e rrug\u00ebzimit \u2014 gjen rrug\u00ebn standarde p\u00ebrmes kalimit VNGW1 p\u00ebrmes Tunnel 1. <br \/>\n Ai gjithashtu sheh se ky \u00ebsht\u00eb nj\u00eb tunel GRE me SIP 10.0.0.2 dhe DIP 10.0.255.2, dhe gjithashtu duhet t\u00eb vendos\u00eb fillimisht etiket\u00ebn MPLS t\u00eb k\u00ebtij klienti, e cila pritet nga VNGW1.\n <\/li>\n<li>vRouter paketizon paket\u00ebn fillestare n\u00eb kokat MPLS, GRE dhe IP t\u00eb re dhe e d\u00ebrgon n\u00eb adres\u00ebn ToR1 10.0.0.1 si default.<\/li>\n<li>Rrjeti Underlay d\u00ebrgon paket\u00ebn te kalimi VNGW1.<\/li>\n<li>Kalimi VNGW1 heq kokat tuneluese GRE dhe MPLS, sheh adres\u00ebn e destinacionit, konsulton tabel\u00ebn e tij t\u00eb rrug\u00ebzimit dhe kupton se ajo \u00ebsht\u00eb drejtuar p\u00ebr n\u00eb Internet \u2014 dometh\u00ebn\u00eb p\u00ebrmes Full View ose Default. N\u00ebse \u00ebsht\u00eb e nevojshme, realizon NAT-translacion.<\/li>\n<li>Nga VNGW deri te bordi mund t\u00eb ket\u00eb nj\u00eb rrjet IP t\u00eb zakonsh\u00ebm, q\u00eb \u00ebsht\u00eb e pap\u00ebrfillshme.<br \/>\n Mund t\u00eb jet\u00eb nj\u00eb rrjet klasik MPLS (IGP+LDP\/RSVP TE), mund t\u00eb jet\u00eb nj\u00eb fabrik\u00eb e kund\u00ebrt me BGP LU ose nj\u00eb tunel GRE nga VNGW deri te bordi p\u00ebrmes rrjetit IP.<br \/>\n \u00c7far\u00ebdo q\u00eb t\u00eb ndodh\u00eb, VNGW1 realizon inkapsulimet e nevojshme dhe d\u00ebrgon paket\u00ebn fillestare n\u00eb drejtim t\u00eb bordit.<\/li>\n<\/ol>\n<p>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/fs.linkmeup.ru\/images\/adsm\/1\/outside-dp.png\"><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/a66e490c75f8220349398af814d4ebf2.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p>Trafiku n\u00eb drejtimin e kund\u00ebrt kalon t\u00eb nj\u00ebjtat hapa n\u00eb rendin e kund\u00ebrt. <\/p>\n<ol>\n<li>Bordi d\u00ebrgon paket\u00ebn deri te VNGW1.<\/li>\n<li>Ai e heq, shikon adres\u00ebn e marr\u00ebsit dhe sheh se ai \u00ebsht\u00eb i aksesuesh\u00ebm p\u00ebrmes tunelit Tunnel1 (MPLSoGRE ose MPLSoUDP).<\/li>\n<li>P\u00ebr rrjedhoj\u00eb, vendos etiket\u00ebn MPLS, kok\u00ebn GRE\/UDP dhe IP t\u00eb ri dhe e d\u00ebrgon n\u00eb ToR3 10.0.255.1.<br \/>\n Adresa e destinacionit t\u00eb tunelit - adresa IP e vRouter-it, pas s\u00eb cil\u00ebs q\u00ebndron VM e synuar - 10.0.0.2.<\/li>\n<li>Rrjeti n\u00ebnd\u00ebrlyes d\u00ebrgon paket\u00ebn n\u00eb vRouter-in e duhur. <\/li>\n<li>vRouter-i i synuar nxjerr GRE\/UDP, p\u00ebrcakton interfacin n\u00ebp\u00ebrmjet MPLS-it dhe d\u00ebrgon paket\u00ebn e past\u00ebr IP n\u00eb interfacin e tij TAP, t\u00eb lidhur me eth0 VM-s\u00eb.<\/li>\n<\/ol>\n<p>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/fs.linkmeup.ru\/images\/adsm\/1\/outside-dp-reverse.png\"><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/ba6748694a822fc04f4e872658d1fbbb.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<h4>Control Plane<\/h4>\n<p>\nVNGW1 vendos nj\u00eb fqinj\u00ebsi BGP me SDN-kontrollerin, nga i cili merr t\u00eb gjith\u00eb informacionin e rrug\u00ebs p\u00ebr klient\u00ebt: pas cil\u00ebs adrese IP (vRouter-i) q\u00ebndron cili klient, dhe me cil\u00ebn MPLS-etiket\u00eb identifikohet.<\/p>\n<p>N\u00eb m\u00ebnyr\u00eb t\u00eb ngjashme, ai vet\u00eb i komunikon SDN-kontrollerit rrug\u00ebn e paracaktuar me etiket\u00ebn e k\u00ebtij klienti, duke sh\u00ebnuar veten si nexthop. M\u00eb pas, ky defolt arrin n\u00eb vRouter-at.<\/p>\n<p>N\u00eb VNGW zakonisht ndodh agregimi i rrug\u00ebve ose p\u00ebrkthimi NAT.<\/p>\n<p>Dhe n\u00eb an\u00ebn tjet\u00ebr n\u00eb seanc\u00ebn me kufijt\u00eb ose Route Reflector-at ai jep pik\u00ebrisht k\u00ebt\u00eb rrug\u00eb t\u00eb agreguar. Dhe prej tyre merr rrug\u00ebn e paracaktuar ose Full-View, ose di\u00e7ka tjet\u00ebr.<\/p>\n<p>N\u00eb planin e inkapsulimit dhe shk\u00ebmbimit t\u00eb trafikut, VNGW nuk ndryshon nga vRouter. <br \/>\nN\u00ebse zgjeroni pak fush\u00ebn, t\u00eb VNGW dhe vRouter-at mund t\u00eb shtohen pajisje t\u00eb tjera rrjetit, si firewall-e, ferm\u00eb pastrimi ose pasurimi trafiku, IPS e k\u00ebshtu me radh\u00eb.<\/p>\n<p>Dhe me ndihm\u00ebn e krijimit t\u00eb nj\u00ebpasnj\u00ebsh\u00ebm t\u00eb VRF dhe njoftimit t\u00eb duhur t\u00eb rrug\u00ebve, mund t\u00eb b\u00ebni q\u00eb trafik t\u00eb ndjek\u00eb cikle ashtu si\u00e7 d\u00ebshironi, q\u00eb quhet Service Chaining.<\/p>\n<p>Pra, edhe k\u00ebtu SDN-kontrolleri funksionon si Route Reflector nd\u00ebrmjet VNGW, vRouter-ave dhe pajisjeve t\u00eb tjera rrjetore.<\/p>\n<p>Por n\u00eb fakt, kontrolleri jep gjithashtu informacion mbi ACL dhe PBR (Rruga e Bazuar n\u00eb Politika), duke e detyruar rrjedhjen e ve\u00e7ant\u00eb t\u00eb trafikut t\u00eb mos ndiqte rrug\u00ebn si\u00e7 e thot\u00eb rruga.<\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/fs.linkmeup.ru\/images\/adsm\/1\/outside-cp.png\"><img decoding=\"async\" alt=\"Automatizimi p\u00ebr t\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit\" src=\"\/wp-content\/uploads\/2019\/07\/dbba5a93d64edf56dc9c2b82311c5a11.jpg\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<h1>FAQ<\/h1>\n<p><b>Pse gjithmon\u00eb b\u00ebn k\u00ebt\u00eb sh\u00ebnim GRE\/UDP?<\/b><\/p>\n<p>Epo, n\u00eb t\u00eb v\u00ebrtet\u00eb, kjo \u00ebsht\u00eb specifike p\u00ebr Tungsten Fabric \u2014 mund t\u00eb mos e konsiderosh fare.<\/p>\n<p>Por megjithat\u00eb, vet\u00eb TF, edhe kur ishte OpenContrail, mb\u00ebshteste t\u00eb dy encapsulimet: MPLS n\u00eb GRE dhe MPLS n\u00eb UDP. <\/p>\n<p>UDP \u00ebsht\u00eb i mir\u00eb sepse n\u00eb Portin e Burimit n\u00eb titullin e tij \u00ebsht\u00eb shum\u00eb e leht\u00eb t\u00eb kodosh nj\u00eb funksion hash nga IP+Proto+Port fillestar, gj\u00eb q\u00eb do t\u00eb lejoj\u00eb balancimin. <\/p>\n<p>N\u00eb rastin e GRE, fatkeq\u00ebsisht, ka vet\u00ebm titujt e jasht\u00ebm IP dhe GRE, t\u00eb cil\u00ebt jan\u00eb t\u00eb nj\u00ebjt\u00eb p\u00ebr t\u00eb gjith\u00eb trafikun e inkapsuluar dhe flet p\u00ebr balancimin nuk \u00ebsht\u00eb \u00e7\u00ebshtje \u2014 pak kush mund t\u00eb shikoj\u00eb aq thell\u00eb brenda paket\u00ebs.<\/p>\n<p>Derisa mb\u00ebrritshme, ruter\u00ebt, edhe n\u00ebse dinin p\u00ebr tunel\u00eb dinamik\u00eb, e b\u00ebnin k\u00ebt\u00eb vet\u00ebm me MPLSoGRE, dhe vet\u00ebm s\u00eb fundi m\u00ebsuan p\u00ebr MPLSoUDP. Prandaj, gjithmon\u00eb duhet t\u00eb theksoj mund\u00ebsin\u00eb e dy enkapsulimeve t\u00eb ndryshme.<\/p>\n<p>P\u00ebr t\u00eb qen\u00eb t\u00eb drejt\u00eb, merret parasysh se TF e p\u00ebrkrah plot\u00ebsisht edhe lidhshm\u00ebrin\u00eb L2 me ndihm\u00ebn e VXLAN.<\/p>\n<p>\n<b>Ti e premtove t\u00eb b\u00ebsh paralela me OpenFlow.<\/b><br \/>\nAta v\u00ebrtet b\u00ebjn\u00eb kuptim. vSwitch n\u00eb t\u00eb nj\u00ebjt\u00ebn OpenStack b\u00ebn gj\u00ebra shum\u00eb t\u00eb ngjashme, duke p\u00ebrdorur VXLAN, i cili, p\u00ebr t\u00eb th\u00ebn\u00eb t\u00eb drejt\u00ebn, ka gjithashtu nj\u00eb header UDP.<\/p>\n<p>N\u00eb Data Plane ata punojn\u00eb p\u00ebraf\u00ebrsisht t\u00eb nj\u00ebjt\u00eb, por Control Plane \u00ebsht\u00eb shum\u00eb m\u00eb i ndrysh\u00ebm. Tungsten Fabric p\u00ebrdor XMPP p\u00ebr t\u00eb dor\u00ebzuar informacionin mbi rrug\u00ebt n\u00eb vRouter, nd\u00ebrsa n\u00eb OpenStack funksionon Openflow.<\/p>\n<p>\n<b>A mund t\u00eb flasim pak m\u00eb shum\u00eb p\u00ebr vRouter-in?<\/b><br \/>\nAi ndahet n\u00eb dy pjes\u00eb: vRouter Agent dhe vRouter Forwarder.<\/p>\n<p>E para aktivizohet n\u00eb User Space t\u00eb sistemit operativ prit\u00ebs dhe komunikon me SDN-controller-in, duke shk\u00ebmbyer informacion mbi rrug\u00ebt, VRF dhe ACL.<\/p>\n<p>E dyta implementon Data Plane\u2014zakonisht n\u00eb Kernel Space, por mund t\u00eb ekzekutohet edhe n\u00eb SmartNIC, karta t\u00eb rrjetit me CPU dhe nj\u00eb \u00e7ip t\u00eb dedikuar t\u00eb programuesh\u00ebm p\u00ebr nd\u00ebrlidhje, gj\u00eb q\u00eb lejon q\u00eb ngarkesa t\u00eb hiqet nga CPU e makin\u00ebs prit\u00ebse, duke e b\u00ebr\u00eb rrjetin m\u00eb t\u00eb shpejt\u00eb dhe m\u00eb t\u00eb parashikuesh\u00ebm. <\/p>\n<p>Gjithashtu \u00ebsht\u00eb e mundshme nj\u00eb skenar ku vRouter \u00ebsht\u00eb nj\u00eb aplikacion DPDK n\u00eb User Space. <\/p>\n<p>vRouter Agent d\u00ebrgon konfigurimet tek vRouter Forwarder.<\/p>\n<p>\n<b>\u00c7far\u00eb \u00ebsht\u00eb Rrjeti Virtual?<\/b><br \/>\nE p\u00ebrmenda n\u00eb fillim t\u00eb artikullit p\u00ebr VRF, se \u00e7do tenant lidhet me VRF-n\u00eb e tij. Dhe n\u00ebse p\u00ebr nj\u00eb kuptim t\u00eb sip\u00ebrfaqsh\u00ebm t\u00eb funksionit t\u00eb rrjet\u00ebs ovrlyed ishte e mjaftueshme, n\u00eb iterat\u00ebn tjet\u00ebr duhet b\u00ebr\u00eb sqarimet.<\/p>\n<p>Zakonisht n\u00eb mekanizmat e virtualizimit, entiteti Virtual Network (mund ta konsideroni si nj\u00eb em\u00ebr t\u00eb ve\u00e7ant\u00eb) merret ve\u00e7mas nga klient\u00ebt\/tenant\u00ebt\/makinat virtuale\u2014p\u00ebr nj\u00eb gj\u00eb t\u00eb pavarur n\u00eb vetvete. Ky Virtual Network mund t\u00eb lidhet p\u00ebrmes nd\u00ebrfaqeve n\u00eb nj\u00eb tenant, n\u00eb nj\u00eb tjet\u00ebr, n\u00eb dy, madje kudo. K\u00ebshtu, p\u00ebr shembull, realizohet Service Chaining, kur trafiku duhet t\u00eb kaloj\u00eb p\u00ebrmes disa node-ve n\u00eb rendin e duhur, duke krijuar thjesht dhe lidhur Virtual Network-et n\u00eb rendin e sakt\u00eb.<\/p>\n<p>Prandaj, si\u00e7 q\u00ebndron, nuk ka ndonj\u00eb p\u00ebrputhje t\u00eb drejtp\u00ebrdrejt\u00eb midis Rrjetit Virtual dhe tenantit.<\/p>\n<h1>P\u00ebrfundim<\/h1>\n<p>\nKy \u00ebsht\u00eb nj\u00eb p\u00ebrshkrim shum\u00eb sip\u00ebrfaq\u00ebsor i funksionimit t\u00eb rrjetit virtual me overlay nga nj\u00eb host dhe kontrolluesi SDN. Por cila do qoft\u00eb platforma e virtualizimit q\u00eb merrni sot, do t\u00eb funksionoj\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb ngjashme, qoft\u00eb VMWare, ACI, OpenStack, CloudStack, Tungsten Fabric apo Juniper Contrail. Ato do t\u00eb ndryshojn\u00eb n\u00eb llojet e enkapsulimeve dhe kryer\u00ebsave, protokolleve t\u00eb shp\u00ebrndarjes s\u00eb informacionit n\u00eb pajisjet finale t\u00eb rrjetit, por principi i rrjetit me overlay t\u00eb programuar mbi nj\u00eb rrjet t\u00eb thjesht\u00eb dhe statik t\u00eb mbulimit do t\u00eb mbetet i nj\u00ebjt\u00eb.<br \/>\nMund t\u00eb thuhet se n\u00eb fush\u00ebn e krijimit t\u00eb nj\u00eb Cloud t\u00eb privatizuar, sot SDN e bazuar n\u00eb rrjetin overlay ka fituar. Megjithat\u00eb, kjo nuk do t\u00eb thot\u00eb se Openflow nuk ka vend n\u00eb bot\u00ebn moderne \u2014 ai p\u00ebrdoret n\u00eb OpenStack dhe po ashtu n\u00eb VMWare NSX, dhe sa kam dijeni, Google e p\u00ebrdor at\u00eb p\u00ebr t\u00eb konfiguruar rrjetin e mbulimit.<\/p>\n<p>Pak m\u00eb posht\u00eb kam p\u00ebrfshir\u00eb lidhjet n\u00eb materiale m\u00eb t\u00eb detajuara, n\u00ebse d\u00ebshiron t\u00eb hulumtosh m\u00eb thell\u00eb. <\/p>\n<p>Por \u00e7far\u00eb ndodh me Underlay-n ton\u00eb? <\/p>\n<p>E n\u00eb p\u00ebrgjith\u00ebsi nuk ka asgj\u00eb t\u00eb re. Ai ka q\u00ebndruar i pandryshuar n\u00eb \u00e7do rast. \u00c7far\u00ebdo q\u00eb ka nevoj\u00eb t\u00eb b\u00ebj\u00eb n\u00eb rastin e overlay nga hosti\u2014\u00ebsht\u00eb t\u00eb p\u00ebrdit\u00ebsoj\u00eb rrug\u00ebt dhe ARP-t\u00eb p\u00ebr sa her\u00eb q\u00eb shfaqen dhe zhduken vRouter\/VNGW dhe t\u00eb transportoj\u00eb paketat midis tyre.<\/p>\n<p>Le t\u00eb formulojm\u00eb nj\u00eb list\u00eb k\u00ebrkesash p\u00ebr rrjetin Underlay.<\/p>\n<ol>\n<li>T\u00eb jet\u00eb i aft\u00eb n\u00eb nj\u00eb protokoll rrug\u00ebtimi, n\u00eb situat\u00ebn ton\u00eb \u2014 BGP.<\/li>\n<li>T\u00eb ket\u00eb nj\u00eb gjer\u00ebsi t\u00eb madhe, preferohet pa shfryt\u00ebzim t\u00eb tepruar, p\u00ebr t\u00eb mos humbur paketat p\u00ebr shkak t\u00eb mbingarkesave.<\/li>\n<li>T\u00eb mb\u00ebshtes\u00eb ECMP \u2014 nj\u00eb pjes\u00eb e pandashme e fabrik\u00ebs.<\/li>\n<li>T\u00eb jet\u00eb n\u00eb gjendje t\u00eb siguroj\u00eb QoS, duke p\u00ebrfshir\u00eb gj\u00ebra t\u00eb komplikuara, si\u00e7 \u00ebsht\u00eb ECN.<\/li>\n<li>T\u00eb mb\u00ebshtes\u00eb NETCONF \u2014 nj\u00eb hap n\u00eb t\u00eb ardhmen.<\/li>\n<\/ol>\n<p>\nKam kushtuar pak koh\u00eb funksionimit t\u00eb vet\u00eb rrjetit Underlay. Kjo \u00ebsht\u00eb sepse n\u00eb vazhdim t\u00eb seris\u00eb, un\u00eb do t\u00eb p\u00ebrqendrohem pik\u00ebrisht aty, nd\u00ebrsa Overlay do ta prekim vet\u00ebm n\u00eb m\u00ebnyr\u00eb t\u00eb sip\u00ebrme.<\/p>\n<p>Padyshim, po e kufizoj shum\u00eb vet\u00eb duke p\u00ebrdorur si shembull rrjetin e Qendr\u00ebs s\u00eb Dh\u00ebnave, i nd\u00ebrtuar mbi fabrik\u00ebn Clos me rrug\u00ebtim t\u00eb pastruar IP dhe overlay nga hosti.<\/p>\n<p>Megjithat\u00eb, jam i sigurt se \u00e7do rrjet me dizajn mund t\u00eb p\u00ebrshkruhet n\u00eb terma formale dhe t\u00eb automatizohet. Thjesht k\u00ebtu po ndjek synimin p\u00ebr t\u00eb kuptuar qasjet ndaj automatizimit, dhe jo p\u00ebr t\u00eb ngat\u00ebrruar t\u00eb gjith\u00eb duke zgjidhur problemin n\u00eb nj\u00eb form\u00eb t\u00eb p\u00ebrgjithshme.<\/p>\n<p>N\u00eb kuad\u00ebr t\u00eb ADSN, ne dhe Roman Gorga planifikojm\u00eb t\u00eb publikojm\u00eb nj\u00eb edicion t\u00eb ve\u00e7ant\u00eb mbi virtualizimin e kapaciteteve kompjuterike dhe nd\u00ebrveprimin e saj me virtualizimin e rrjetit. Q\u00ebndroni t\u00eb lidhur.<\/p>\n<p><\/p>\n<h1>Useful links<\/h1>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/tungstenfabric.github.io\/website\/\">Arkitektura Tungsten Fabric<\/a><\/noindex>.<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/youtu.be\/Kr6WIYPts8I?t=3157\">rreth:cloud<\/a><\/noindex>. 6 or\u00eb p\u00ebr Yandex.Cloud, ku p\u00ebrfshihet gjithashtu rrjeti virtual n\u00eb TF.<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/docs.openvswitch.org\/en\/latest\/intro\/what-is-ovs\/\">\u00c7far\u00eb \u00ebsht\u00eb Open vSwitch?<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/344326\/\">Hyrje n\u00eb VxLAN<\/a><\/noindex>.<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/tools.ietf.org\/html\/rfc7348\">RFC 7348. Rrjeti Virtual eXtensible Local Area Network (VXLAN): Nj\u00eb Korniz\u00eb p\u00ebr Mbivendosjen e Rrjeteve Virtuale t\u00eb Shtres\u00ebs 2 mbi Rrjetet e Shtres\u00ebs 3.<br \/>\n <\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.enog.org\/wp-content\/uploads\/presentations\/enog-16\/18-Scaleway-P14-fabric-ENOG16.pdf\">Qasja e Scaleway n\u00eb VXLAN EVPN Fabric<\/a><\/noindex>. K\u00ebtu p\u00ebrshkruhet e gjith\u00eb rrjeti i DC, duke p\u00ebrfshir\u00eb Underlay, Overlay, qasjet p\u00ebr multi-homing dhe menaxhimin.<\/li>\n<\/ul>\n<p><\/p>\n<h5>Faleminderit<\/h5>\n<p><\/p>\n<ul>\n<li><noindex>Roman Gorgh\u00eb<\/noindex> \u2014 ish-aspirant i podkastit linkmeup, tani ekspert n\u00eb fush\u00ebn e platformave cloud. Fal\u00ebnderime p\u00ebr komentet dhe korrigjimet. Dhe presim n\u00eb t\u00eb ardhmen nj\u00eb artikull m\u00eb t\u00eb thell\u00eb mbi virtualizimin.<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.alexander-shalimov.com\">Aleksand\u00ebr Shalimov<\/a><\/noindex> \u2014 kolegu im dhe ekspert n\u00eb fush\u00ebn e zhvillimit t\u00eb rrjeteve virtuale. Fal\u00ebnderime p\u00ebr komentet dhe korrigjimet.<\/li>\n<li><noindex>Valentin Sinitsin<\/noindex> \u2014 kolegu im dhe ekspert n\u00eb fush\u00ebn e Tungsten Fabric. Fal\u00ebnderime p\u00ebr komentet dhe korrigjimet.<\/li>\n<li><noindex>Artyom Chernobai<\/noindex> \u2014 ilustrator i linkmeup. Fal\u00ebnderime p\u00ebr KDPV.<\/li>\n<li>Aleksand\u00ebr Limonov. Fal\u00ebnderime p\u00ebr memin \u00abautomato\u00bb.<\/li>\n<\/ul>\n<p>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/458622\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u043c \u0432\u044b\u043f\u0443\u0441\u043a\u0435 \u044f \u043e\u043f\u0438\u0441\u0430\u043b \u0444\u0440\u0435\u0439\u043c\u0432\u043e\u0440\u043a \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0437\u0430\u0446\u0438\u0438. \u041f\u043e \u043e\u0442\u0437\u044b\u0432\u0430\u043c \u0443 \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u043b\u044e\u0434\u0435\u0439 \u0434\u0430\u0436\u0435 \u044d\u0442\u043e\u0442 \u043f\u0435\u0440\u0432\u044b\u0439 \u043f\u043e\u0434\u0445\u043e\u0434 \u043a \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u0435 \u0443\u0436\u0435 \u0440\u0430\u0437\u043b\u043e\u0436\u0438\u043b \u043d\u0435\u043a\u043e\u0442\u043e\u0440\u044b\u0435 \u0432\u043e\u043f\u0440\u043e\u0441\u044b \u043f\u043e \u043f\u043e\u043b\u043e\u0447\u043a\u0430\u043c. \u0418 \u044d\u0442\u043e \u043e\u0447\u0435\u043d\u044c \u043c\u0435\u043d\u044f \u0440\u0430\u0434\u0443\u0435\u0442, \u043f\u043e\u0442\u043e\u043c\u0443 \u0447\u0442\u043e \u043d\u0430\u0448\u0430 \u0446\u0435\u043b\u044c \u0432 \u0446\u0438\u043a\u043b\u0435 \u2014 \u043d\u0435 \u043e\u0431\u043c\u0430\u0437\u0430\u0442\u044c \u043f\u0438\u0442\u043e\u043d\u043e\u0432\u0441\u043a\u0438\u043c\u0438 \u0441\u043a\u0440\u0438\u043f\u0442\u0430\u043c\u0438 \u0430\u043d\u0437\u0438\u0431\u043b\u044c, \u0430 \u0432\u044b\u0441\u0442\u0440\u043e\u0438\u0442\u044c \u0441\u0438\u0441\u0442\u0435\u043c\u0443. \u042d\u0442\u043e\u0442 \u0436\u0435 \u0444\u0440\u0435\u0439\u043c\u0432\u043e\u0440\u043a \u0437\u0430\u0434\u0430\u0451\u0442 \u043f\u043e\u0440\u044f\u0434\u043e\u043a, \u0432 \u043a\u043e\u0442\u043e\u0440\u043e\u043c \u043c\u044b \u0431\u0443\u0434\u0435\u043c \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0442\u044c\u0441\u044f [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":26892,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-35973","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.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u043c \u0432\u044b\u043f\u0443\u0441\u043a\u0435 \u044f \u043e\u043f\u0438\u0441\u0430\u043b \u0444\u0440\u0435\u0439\u043c\u0432\u043e\u0440\u043a \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0437\u0430\u0446\u0438\u0438.\" \/>\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-pervaya-kotoraya-posle-nulevoj-virtualizatsiya-seti\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\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 \u0414\u043b\u044f \u0421\u0430\u043c\u044b\u0445 \u041c\u0430\u043b\u0435\u043d\u044c\u043a\u0438\u0445. \u0427\u0430\u0441\u0442\u044c \u043f\u0435\u0440\u0432\u0430\u044f (\u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043f\u043e\u0441\u043b\u0435 \u043d\u0443\u043b\u0435\u0432\u043e\u0439). \u0412\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u044f \u0441\u0435\u0442\u0438 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u043c \u0432\u044b\u043f\u0443\u0441\u043a\u0435 \u044f \u043e\u043f\u0438\u0441\u0430\u043b \u0444\u0440\u0435\u0439\u043c\u0432\u043e\u0440\u043a \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0437\u0430\u0446\u0438\u0438.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/avtomatizatsiya-dlya-samyh-malenkih-chast-pervaya-kotoraya-posle-nulevoj-virtualizatsiya-seti\" \/>\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\u00eb Vegjlit. Pjesa e par\u00eb (e cila vjen pas asaj zero). Virtualizimi i rrjetit | ProHoster","description":"N\u00eb numrin e kaluar, p\u00ebrshkrova korniz\u00ebn e automatizimit t\u00eb rrjetit.","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/avtomatizatsiya-dlya-samyh-malenkih-chast-pervaya-kotoraya-posle-nulevoj-virtualizatsiya-seti","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 \u0414\u043b\u044f \u0421\u0430\u043c\u044b\u0445 \u041c\u0430\u043b\u0435\u043d\u044c\u043a\u0438\u0445. \u0427\u0430\u0441\u0442\u044c \u043f\u0435\u0440\u0432\u0430\u044f (\u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043f\u043e\u0441\u043b\u0435 \u043d\u0443\u043b\u0435\u0432\u043e\u0439). \u0412\u0438\u0440\u0442\u0443\u0430\u043b\u0438\u0437\u0430\u0446\u0438\u044f \u0441\u0435\u0442\u0438 | ProHoster","og:description":"\u0412 \u043f\u0440\u0435\u0434\u044b\u0434\u0443\u0449\u0435\u043c \u0432\u044b\u043f\u0443\u0441\u043a\u0435 \u044f \u043e\u043f\u0438\u0441\u0430\u043b \u0444\u0440\u0435\u0439\u043c\u0432\u043e\u0440\u043a \u0441\u0435\u0442\u0435\u0432\u043e\u0439 \u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0437\u0430\u0446\u0438\u0438.","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/avtomatizatsiya-dlya-samyh-malenkih-chast-pervaya-kotoraya-posle-nulevoj-virtualizatsiya-seti","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":"35973","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-03-01 01:53:30","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\/35973","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=35973"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/35973\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/26892"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=35973"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=35973"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=35973"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}