![\"Si](\"\/wp-content\/uploads\/2020\/02\/62b3d222c1911fb28a345defdd81135c.jpeg\")
<\/p>\nP\u00ebrsh\u00ebndetje, emri im \u00ebsht\u00eb Kostya Kramlih, un\u00eb jam zhvilluesi kryesor i divizionit Virtual Private Cloud n\u00eb Yandex.Cloud. Un\u00eb merrem me rrjetin virtual dhe, si\u00e7 mund t\u00eb kuptoni, n\u00eb k\u00ebt\u00eb artikull do t'ju tregoj p\u00ebr struktur\u00ebn e Virtual Private Cloud (VPC) n\u00eb p\u00ebrgjith\u00ebsi dhe t\u00eb rrjetit virtual n\u00eb ve\u00e7anti. Po ashtu do t\u00eb m\u00ebsoni se p\u00ebrse ne, zhvilluesit e sh\u00ebrbimit, e vler\u00ebsojm\u00eb shum\u00eb feedback-un nga p\u00ebrdoruesit tan\u00eb. Por le t\u00eb fillojm\u00eb me renditjen.<\/p>\n
<\/p>\n
<\/a><\/p>\n N\u00eb koh\u00ebt tona ka shum\u00eb mund\u00ebsi p\u00ebr zhvillimin e sh\u00ebrbimeve. Jam i sigurt se dikush ende mban nj\u00eb server n\u00ebn tryez\u00ebn e administratorit, megjithat\u00eb, shpresoj q\u00eb k\u00ebto histori t\u00eb b\u00ebhen gjithnj\u00eb e m\u00eb t\u00eb pakta.<\/p>\n Aktualisht sh\u00ebrbimet p\u00ebrpiqen t\u00eb kalojn\u00eb n\u00eb cloud publik, dhe pik\u00ebrisht k\u00ebtu ata p\u00ebrballen me VPC. VPC \u00ebsht\u00eb nj\u00eb pjes\u00eb e cloud-it publik q\u00eb lidh fuqit\u00eb e p\u00ebrdoruesve, infrastruktur\u00ebs, platformave dhe t\u00eb tjerave s\u00eb bashku, kudo q\u00eb ndodhen, n\u00eb Clouds ton\u00eb apo jasht\u00eb saj. Gjithashtu, VPC lejon q\u00eb t\u00eb mos ekspozoni k\u00ebto fuqi n\u00eb internet pa nevoj\u00eb, ato mbeten brenda rrjetit tuaj t\u00eb izoluar.<\/p>\n Me VPC, ne kuptojm\u00eb para se gjithash nj\u00eb rrjet mb\u00ebshtetje dhe sh\u00ebrbime rrjeti si VPNaaS, NATaas, LBaas etj. T\u00eb gjitha k\u00ebto funksionojn\u00eb mbi nj\u00eb infrastruktur\u00eb rrjeti t\u00eb q\u00ebndrueshme, p\u00ebr t\u00eb cil\u00ebn \u00ebsht\u00eb folur m\u00eb par\u00eb artikull i shk\u00eblqyer<\/a> k\u00ebtu, n\u00eb Habr.<\/p>\n Le t\u00eb shohim m\u00eb af\u00ebr rrjetin virtual dhe struktur\u00ebn e tij.<\/p>\n T\u00eb shqyrtojm\u00eb dy zona qasje. Ne ofrojm\u00eb nj\u00eb rrjet virtual - at\u00eb q\u00eb e quajm\u00eb VPC. N\u00eb fakt, ajo p\u00ebrcakton hap\u00ebsir\u00ebn e ve\u00e7antis\u00eb p\u00ebr adresat tuaja 't\u00eb gris\u00eb'. Brenda \u00e7do rrjeti virtual, ju keni kontroll t\u00eb plot\u00eb mbi hap\u00ebsir\u00ebn e adresave q\u00eb mund t\u00eb caktoni p\u00ebr burimet kompjuterike.<\/p>\n Rrjeti \u00ebsht\u00eb global. Ai projektohet n\u00eb \u00e7do zon\u00eb t\u00eb disponueshm\u00ebris\u00eb si nj\u00eb entitet i quajtur Subnet. P\u00ebr \u00e7do Subnet, duhet t\u00eb caktoni nj\u00eb CIDR me nj\u00eb madh\u00ebsi 16 ose m\u00eb t\u00eb vog\u00ebl. N\u00eb \u00e7do zon\u00eb t\u00eb disponueshm\u00ebris\u00eb mund t\u00eb ket\u00eb m\u00eb shum\u00eb se nj\u00eb t\u00eb till\u00eb, dhe midis tyre gjithmon\u00eb ka routing transparent. Kjo do t\u00eb thot\u00eb se t\u00eb gjitha burimet tuaja brenda nj\u00eb VPC mund t\u00eb \"komunikojn\u00eb\" me nj\u00ebra-tjetr\u00ebn, madje edhe n\u00ebse ndodhen n\u00eb zona t\u00eb ndryshme t\u00eb disponueshm\u00ebris\u00eb. \"T\u00eb komunikojn\u00eb\" pa dal\u00eb n\u00eb internet, n\u00ebp\u00ebrmjet kanaleve tona t\u00eb brendshme, t\u00eb \"mendoni\" se ndodhen brenda nj\u00eb rrjeti privat.<\/p>\n N\u00eb diagramin e m\u00ebsip\u00ebrm \u00ebsht\u00eb ilustruar nj\u00eb rast tipik: dy VPC-t\u00eb, t\u00eb cilat ndodhen diku q\u00eb p\u00ebrputhen n\u00eb adresat. T\u00eb dyja mund t\u00eb p\u00ebrkasin juve. P\u00ebr shembull, nj\u00eb p\u00ebr zhvillim, tjetra p\u00ebr testim. Mund t\u00eb jen\u00eb thjesht p\u00ebrdorues t\u00eb ndrysh\u00ebm \u2013 n\u00eb k\u00ebt\u00eb rast nuk ka r\u00ebnd\u00ebsi. Dhe n\u00eb \u00e7do VPC \u00ebsht\u00eb instaluar nj\u00eb makin\u00eb virtuale.<\/p>\n Ta p\u00ebrkeq\u00ebsojm\u00eb diagramin. Mund t\u00eb b\u00ebhet q\u00eb nj\u00eb makin\u00eb virtuale t\u00eb lidhet menj\u00ebher\u00eb me disa Subnet. Dhe jo thjesht ashtu, por n\u00eb rrjete t\u00eb ndryshme virtuale.<\/p>\n N\u00eb rast se keni nevoj\u00eb t\u00eb ekspozoni makinat n\u00eb internet, mund ta b\u00ebni k\u00ebt\u00eb p\u00ebrmes API-s\u00eb ose UI-s\u00eb. P\u00ebr k\u00ebt\u00eb, \u00ebsht\u00eb e nevojshme t\u00eb konfiguroni transmetimin NAT t\u00eb adres\u00ebs tuaj \"t\u00eb err\u00ebt\", brenda, n\u00eb nj\u00eb adres\u00eb \"t\u00eb bardh\u00eb\" \u2013 publike. Nuk mund t\u00eb zgjidhni adres\u00ebn \"t\u00eb bardh\u00eb\", ajo caktohet rast\u00ebsisht nga grupi yn\u00eb i adresave. Sapo t\u00eb pushoni s\u00eb p\u00ebrdoruri IP-n\u00eb e jashtme, ajo kthehet n\u00eb grup. Ju paguani vet\u00ebm p\u00ebr koh\u00ebn e p\u00ebrdorimit t\u00eb adres\u00ebs \"t\u00eb bardh\u00eb\".<\/p>\n Ka gjithashtu mund\u00ebsin\u00eb p\u00ebr t\u00eb dh\u00ebn\u00eb nj\u00eb makin\u00eb akses n\u00eb internet p\u00ebrmes nj\u00eb instanc\u00eb NAT. Trafici mund t\u00eb rrug\u00ebzohet n\u00eb instanc\u00eb p\u00ebrmes nj\u00eb tabele statike t\u00eb rrug\u00ebzimit. Ne kemi parashikuar nj\u00eb rast t\u00eb till\u00eb, sepse ndodh shpesh q\u00eb p\u00ebrdoruesit e kan\u00eb nevoj\u00eb, dhe ne e dim\u00eb k\u00ebt\u00eb. Prandaj, n\u00eb katalogun ton\u00eb t\u00eb imazheve ndodhet nj\u00eb imazh NAT i konfiguruar posa\u00e7\u00ebrisht.<\/p>\n Megjith\u00ebse ekziston nj\u00eb imazh NAT i gatsh\u00ebm, konfigurimi mund t\u00eb jet\u00eb i nd\u00ebrlikuar. Ne kuptuam se p\u00ebr disa p\u00ebrdorues ky nuk \u00ebsht\u00eb opsioni m\u00eb i p\u00ebrshtatsh\u00ebm, prandaj n\u00eb fund krijuam mund\u00ebsin\u00eb p\u00ebr t\u00eb aktivizuar NAT p\u00ebr subnet-in e nevojsh\u00ebm me nj\u00eb klik. Kjo ve\u00e7ori \u00ebsht\u00eb ende n\u00eb aksesin preview t\u00eb mbyllur, duke u testuar me ndihm\u00ebn e an\u00ebtar\u00ebve t\u00eb komunitetit.<\/p>\n Si ndikon p\u00ebrdoruesi n\u00eb rrjetin virtual? Rrjeti shikon jasht\u00eb p\u00ebrmes API-s\u00eb s\u00eb tij. P\u00ebrdoruesi hyn n\u00eb API dhe punon me gjendjen e synuar. P\u00ebrmes API-s\u00eb, p\u00ebrdoruesi sheh si duhet t\u00eb jet\u00eb strukturuar dhe konfiguruar gjith\u00e7ka, duke par\u00eb gjithashtu statusin e saj, sa shum\u00eb gjendja aktuale ndryshon nga ajo q\u00eb d\u00ebshirohet. Kjo \u00ebsht\u00eb pamja e p\u00ebrdoruesit. Po \u00e7far\u00eb ndodh brenda?<\/p>\n Ne regjistrojm\u00eb gjendjen e d\u00ebshiruar n\u00eb Yandex Database dhe shk\u00ebmbejm\u00eb konfigurimin e pjes\u00ebve t\u00eb ndryshme t\u00eb VPC-s\u00eb ton\u00eb. Rrjeti i mb\u00ebshtjelljes n\u00eb Yandex.Cloud \u00ebsht\u00eb nd\u00ebrtuar mbi komponent\u00ebt e zgjedhur t\u00eb OpenContrail, i cili koh\u00ebt e fundit ka marr\u00eb emrin Tungsten Fabric. Sh\u00ebrbimet rrjet\u00ebrore jan\u00eb t\u00eb implementuara n\u00eb nj\u00eb platform\u00eb t\u00eb vetme, CloudGate. N\u00eb CloudGate ne gjithashtu p\u00ebrdor\u00ebm nj\u00eb sasi t\u00eb caktuar komponent\u00ebsh open source: GoBGP \u2013 p\u00ebr aksesimin e informacionit t\u00eb kontrollit, si dhe VPP \u2013 p\u00ebr implementimin e nj\u00eb router-i programatik q\u00eb funksionon mbi DPDK p\u00ebr rrug\u00ebn e t\u00eb dh\u00ebnave.<\/p>\n Tungsten Fabric komunikon me CloudGate p\u00ebrmes GoBGP. Njofton se \u00e7far\u00eb ndodh n\u00eb rrjetin e mb\u00ebshtjelljes. CloudGate, nga ana tjet\u00ebr, lidh rrjetet e mb\u00ebshtjelljes me nj\u00ebra-tjetr\u00ebn dhe me internetin.<\/p>\n Tani le t\u00eb shohim se si rrjeti virtual zgjidh problemet e shkall\u00ebzueshm\u00ebris\u00eb dhe disponueshm\u00ebris\u00eb. Le t\u00eb marrim nj\u00eb rast t\u00eb thjesht\u00eb. Kemi nj\u00eb zon\u00eb aksesuese dhe n\u00eb t\u00eb jan\u00eb krijuar dy VPC. Ne kemi zhvilluar nj\u00eb instanc\u00eb Tungsten Fabric, e cila mbart disa dhjet\u00ebra mij\u00ebra rrjete. Rrjetet lidhen me CloudGate. CloudGate, si\u00e7 e kemi th\u00ebn\u00eb m\u00eb par\u00eb, siguron lidhshm\u00ebrin\u00eb midis tyre dhe me internetin.<\/p>\n Supozoni se shtohet nj\u00eb zon\u00eb e dyt\u00eb aksesuese. Ajo duhet t\u00eb funksionoj\u00eb plot\u00ebsisht e pavarur nga e para. Prandaj, n\u00eb zon\u00ebn e dyt\u00eb aksesuese ne duhet t\u00eb vendosim nj\u00eb instanc\u00eb t\u00eb ve\u00e7ant\u00eb Tungsten Fabric. Kjo do t\u00eb jet\u00eb nj\u00eb sistem i ve\u00e7ant\u00eb, i cili merret me overlay dhe di pak p\u00ebr sistemin e par\u00eb. Nd\u00ebrsa, vizibiliteti se rrjeti yn\u00eb virtual \u00ebsht\u00eb global, n\u00eb fakt, krijohet nga API-ja jon\u00eb VPC. Kjo \u00ebsht\u00eb detyra e tij.<\/p>\n VPC1 projektohet n\u00eb zon\u00ebn e aksesit B, n\u00ebse n\u00eb zon\u00ebn e aksesit B ka burime q\u00eb lidhen me VPC1. N\u00ebse nuk ka burime nga VPC2 n\u00eb zon\u00ebn e aksesit B, VPC2 n\u00eb k\u00ebt\u00eb zon\u00eb nuk materializohet. Nga ana tjet\u00ebr, p\u00ebr shkak se burimet nga VPC3 ekzistojn\u00eb vet\u00ebm n\u00eb zon\u00ebn B, VPC3 nuk \u00ebsht\u00eb n\u00eb zon\u00ebn A. E gjith\u00eb kjo \u00ebsht\u00eb e thjesht\u00eb dhe logjike.<\/p>\n Le t\u00eb shkojm\u00eb pak m\u00eb thell\u00eb dhe t\u00eb shohim se si funksionon nj\u00eb host specifik n\u00eb Y.Oblak. E vetmja gj\u00eb q\u00eb duhet theksuar \u00ebsht\u00eb se t\u00eb gjith\u00eb hostet funksionojn\u00eb nj\u00ebsoj. Ne sigurojm\u00eb q\u00eb vet\u00ebm minimumi i nevojsh\u00ebm i sh\u00ebrbimeve t\u00eb jet\u00eb aktiv n\u00eb \"harduer\", nd\u00ebrsa t\u00eb gjitha sh\u00ebrbimet e tjera funksionojn\u00eb mbi makinat virtuale<\/a>. Ne nd\u00ebrtuam sh\u00ebrbime m\u00eb t\u00eb avancuara mbi sh\u00ebrbimet bazike infrastrukturore dhe gjithashtu p\u00ebrdorim Cloud p\u00ebr t\u00eb zgjidhur disa detyra inxhinierike, si\u00e7 \u00ebsht\u00eb n\u00eb kuad\u00ebr t\u00eb Continuous Integration.<\/p>\n N\u00ebse shohim nj\u00eb host t\u00eb ve\u00e7ant\u00eb, do t\u00eb shohim se n\u00eb sistemin operativ t\u00eb hostit funksionojn\u00eb tre komponente:<\/p>\n P\u00ebrve\u00e7 k\u00ebsaj, n\u00eb makinat virtuale<\/a> jan\u00eb aktive sh\u00ebrbime: sh\u00ebrbimet infrastrukturore t\u00eb Cloud, sh\u00ebrbimet e platform\u00ebs dhe kapacitetet e klient\u00ebve. Kapacitetet e klient\u00ebve dhe sh\u00ebrbimet e platform\u00ebs gjithmon\u00eb kalojn\u00eb n\u00eb overlay p\u00ebrmes VRouter.<\/p>\n Sh\u00ebrbimet infrastrukturore mund t\u00eb integrohen n\u00eb overlay, por kryesisht duan t\u00eb punojn\u00eb n\u00eb underlay. N\u00eb underlay, ato integrohen p\u00ebrmes SR-IOV. Faktikisht, ne e ndajm\u00eb kart\u00ebn n\u00eb karta virtuale rrjetesh (funksione virtuale) dhe i futim ato n\u00eb makinat virtuale infrastrukturore, p\u00ebr t\u00eb mos humbur performanc\u00ebn. P\u00ebr shembull, CloudGate i famsh\u00ebm \u00ebsht\u00eb nisur si nj\u00ebra prej k\u00ebtyre makinave virtuale infrastrukturore.<\/p>\n Tani, kur kemi p\u00ebrshkruar detyrat globale t\u00eb rrjetit virtual dhe struktur\u00ebn e komponent\u00ebve baz\u00eb t\u00eb rethit, le t\u00eb shohim se si pjes\u00ebt e ndryshme t\u00eb rrjetit virtual nd\u00ebrveprojn\u00eb me nj\u00ebra-tjetr\u00ebn.<\/p>\n Ne kemi identifikuar n\u00eb sistemin ton\u00eb tre nivele:<\/p>\n Si\u00e7 e p\u00ebrmenda m\u00eb lart, gjith\u00e7ka fillon kur p\u00ebrdoruesi ose sh\u00ebrbimi i brendsh\u00ebm i platform\u00ebs hyn n\u00eb API dhe p\u00ebrshkruan nj\u00eb gjendje t\u00eb caktuar q\u00eb do t\u00eb arrihet.<\/p>\n Ky ky\u00e7 \u00ebsht\u00eb regjistruar menj\u00ebher\u00eb n\u00eb Yandex Database, kthen p\u00ebrmes API ID t\u00eb operacionit asinkron dhe niset mekanizmi yn\u00eb t\u00eb brendsh\u00ebm p\u00ebr t\u00eb dh\u00ebn\u00eb gjendjen q\u00eb d\u00ebshiron p\u00ebrdoruesi. Detyrat e konfigurimit shkojn\u00eb n\u00eb SDN-kontroller dhe tregojn\u00eb Tungsten Fabric se \u00e7far\u00eb duhet b\u00ebr\u00eb n\u00eb overlay. P\u00ebr shembull, ato rezervojn\u00eb porte, rrjeta virtuale dhe gj\u00ebra t\u00eb ngjashme.<\/p>\n Plani i Konfigurimit n\u00eb Tungsten Fabric d\u00ebrgon n\u00eb Planin e Kontrollit gjendjen e k\u00ebrkuar. P\u00ebrmes tij, Plani i Konfigurimit komunikon me hostet, duke th\u00ebn\u00eb se \u00e7far\u00eb do t\u00eb funksionoj\u00eb aty s\u00eb shpejti.<\/p>\n Tani le t\u00eb shohim se si duket sistemi n\u00eb hoste. N\u00eb makin\u00ebn virtuale<\/a> ka nj\u00eb adaptues rrjeti, i vendosur n\u00eb VRouter. VRouter \u00ebsht\u00eb moduli thelb\u00ebsor i Tungsten Fabric, i cili shqyrton paketat. N\u00ebse p\u00ebr ndonj\u00eb paket\u00eb ka tashm\u00eb nj\u00eb rrjedh\u00eb, moduli e p\u00ebrpunon at\u00eb. N\u00ebse s'ka rrjedh\u00eb, moduli b\u00ebn at\u00eb q\u00eb quhet punting, dmth d\u00ebrgon paket\u00ebn n\u00eb procesin e mod\u00ebs s\u00eb p\u00ebrdoruesit. Procesi analizon paket\u00ebn dhe ose p\u00ebrgjigjet vet\u00eb, si\u00e7 \u00ebsht\u00eb n\u00eb DHCP dhe DNS, ose i tregon VRouter se \u00e7far\u00eb t\u00eb b\u00ebj\u00eb me t\u00eb. Pas k\u00ebsaj, VRouter mund t\u00eb p\u00ebrpunoj\u00eb paket\u00ebn.<\/p>\n Trafiku midis makinave virtuale brenda nj\u00eb rrjeti virtual \u00ebsht\u00eb i kaluesh\u00ebm, ai nuk d\u00ebrgohet n\u00eb CloudGate. Hostet, mbi t\u00eb cilat jan\u00eb vendosur makinat virtuale, komunikojn\u00eb me nj\u00ebri-tjetrin p\u00ebrmes nj\u00eb lidhjeje direkte. Ata tunnelojn\u00eb trafikun dhe e kalojn\u00eb at\u00eb p\u00ebrmes rrjetit.<\/p>\n Control Plane komunikon me nj\u00ebri-tjetrin midis zonave t\u00eb disponueshm\u00ebris\u00eb p\u00ebrmes BGP, ashtu si me nj\u00eb router tjet\u00ebr. Ata tregojn\u00eb se cilat makina jan\u00eb ngritur dhe ku, n\u00eb m\u00ebnyr\u00eb q\u00eb makinat virtuale n\u00eb nj\u00eb zon\u00eb t\u00eb mund t\u00eb nd\u00ebrveprojn\u00eb drejtp\u00ebrdrejt me makinat virtuale t\u00eb tjera.<\/p>\n P\u00ebr m\u00eb tep\u00ebr, Control Plane komunikon me CloudGate. Ai njofton se ku dhe \u00e7far\u00eb makinash virtuale jan\u00eb ngritur dhe cilat jan\u00eb adresat e tyre. Kjo lejon d\u00ebrgimin e trafikut t\u00eb jasht\u00ebm dhe trafikut nga balancuesit.<\/p>\n Trafiku q\u00eb del nga VPC arrin n\u00eb CloudGate, n\u00eb rrug\u00ebn e t\u00eb dh\u00ebnave, ku p\u00ebrpunohen shpejt me VPP-n\u00eb ton\u00eb dhe pluginet. M\u00eb pas trafiku d\u00ebrgohet ose n\u00eb VPC t\u00eb tjera, ose jasht\u00eb, n\u00eb routerat kufitar\u00eb, t\u00eb cilat konfigurohen p\u00ebrmes Control Plane t\u00eb CloudGate.<\/p>\n N\u00ebse e p\u00ebrgjith\u00ebsojm\u00eb t\u00eb gjitha t\u00eb th\u00ebn\u00eb m\u00eb lart n\u00eb disa fraza, mund t\u00eb themi se VPC n\u00eb Yandex.Cloud p\u00ebrmbush dy detyra t\u00eb r\u00ebnd\u00ebsishme:<\/p>\n Dhe p\u00ebr t\u00eb zgjidhur k\u00ebto detyra mir\u00eb, nevojitet t\u00eb sigurojm\u00eb shkall\u00ebzueshm\u00ebri dhe q\u00ebndrueshm\u00ebri n\u00eb nivelin e arkitektur\u00ebs s\u00eb brendshme, gj\u00eb q\u00eb e b\u00ebn VPC.<\/p>\n Gradualisht, VPC shp\u00ebrfaq funksione, ne realizojm\u00eb mund\u00ebsi t\u00eb reja dhe p\u00ebrpiqemi t\u00eb p\u00ebrmir\u00ebsojm\u00eb di\u00e7ka n\u00eb aspektin e komoditetit p\u00ebr p\u00ebrdoruesit. Disa ide shprehen dhe p\u00ebrfshihen n\u00eb list\u00ebn e prioriteteve fal\u00eb pjes\u00ebmarr\u00ebsve n\u00eb komunitetin ton\u00eb.<\/p>\n Aktualisht, kemi nj\u00eb list\u00eb planesh p\u00ebr t\u00eb ardhmen e af\u00ebrt:<\/p>\n Balancuesi dhe mund\u00ebsia p\u00ebr t\u00eb nd\u00ebrruar adres\u00ebn IP p\u00ebr makinat virtuale q\u00eb jan\u00eb krijuar tashm\u00eb u p\u00ebrfshin\u00eb n\u00eb k\u00ebt\u00eb list\u00eb p\u00ebr k\u00ebrkes\u00ebn e p\u00ebrdoruesve. T\u00eb them sinqerisht, pa nj\u00eb kthim t\u00eb qart\u00eb, do t\u00eb merreshim me k\u00ebto funksione disa m\u00eb von\u00eb. Tani, ne po punojm\u00eb p\u00ebr detyr\u00ebn lidhur me adresat.<\/p>\n N\u00eb fillim, adresa IP \"e bardh\u00eb\" mund t\u00eb shtohej vet\u00ebm gjat\u00eb krijimit t\u00eb makin\u00ebs. N\u00ebse p\u00ebrdoruesi e harronte k\u00ebt\u00eb, makina virutale duhej t\u00eb rip\u00ebrt\u00ebrinte. E nj\u00ebjta gj\u00eb ndodhte dhe kur duhej hequr IP e jashtme. Shpejt do t\u00eb jet\u00eb e mundur t\u00eb aktivizohet dhe dezaktivizohet IP publik pa e rip\u00ebrt\u00ebrir\u00eb makin\u00ebn.<\/p>\n Mos hezitoni t\u00eb shprehni ide dhe t\u00eb mb\u00ebshtesni propozimet<\/a> e p\u00ebrdoruesve t\u00eb tjer\u00eb. Ju ndihmoni q\u00eb t\u00eb b\u00ebjm\u00eb Cloud m\u00eb t\u00eb mir\u00eb dhe t\u00eb merrni m\u00eb shpejt funksione t\u00eb r\u00ebnd\u00ebsishme dhe t\u00eb dobishme!<\/p>\n\u00c7far\u00eb \u00ebsht\u00eb VPC?<\/h2>\n
Si dhe duket nj\u00eb rrjet virtual nga jasht\u00eb<\/h2>\n
![\"Si](\"\/wp-content\/uploads\/2020\/02\/073a0cbac0e733decd8a4e6ffd9570ff.jpeg\")
<\/p>\n![\"Si](\"\/wp-content\/uploads\/2020\/02\/b1b7a15912f9c7995663ab9943d473f1.jpeg\")
<\/p>\n![\"Si](\"\/wp-content\/uploads\/2020\/02\/73e872a4f6c3e19576db4e4980d62a45.jpeg\")
<\/p>\n![\"Si](\"\/wp-content\/uploads\/2020\/02\/cc4ab2c7553d63ef2636924df1575479.jpeg\")
<\/p>\n![\"Si](\"\/wp-content\/uploads\/2020\/02\/c2375fd6d0fb7b55ca55787adf505229.jpeg\")
<\/p>\n![\"Si](\"\/wp-content\/uploads\/2020\/02\/744ac3bdd2f388bab2597d6fe1519d76.jpeg\")
<\/p>\nSi \u00ebsht\u00eb e organizuar nj\u00eb rrjet virtual nga brenda<\/h2>\n
![\"Si](\"\/wp-content\/uploads\/2020\/02\/71cab3ae7f067f165a87e30c60559794.jpeg\")
<\/p>\n![\"Si](\"\/wp-content\/uploads\/2020\/02\/222d68fff4b9577f316c8642e846172e.jpeg\")
<\/p>\n![\"Si](\"\/wp-content\/uploads\/2020\/02\/4da02ba041dcd886eee212dd8998718c.jpeg\")
<\/p>\n![\"Si](\"\/wp-content\/uploads\/2020\/02\/4664bd03793ba394ceda1f8214fa2c16.jpeg\")
<\/p>\n\n
\n
![\"Si](\"\/wp-content\/uploads\/2020\/02\/644cddfa8bce83a501bf4788a21f9588.jpeg\")
<\/p>\n![\"Si](\"\/wp-content\/uploads\/2020\/02\/c2c6e443c93f8dedc6a63e4bd3fd7042.jpeg\")
<\/p>\n![\"Si](\"\/wp-content\/uploads\/2020\/02\/2139361a9e1837c7bc7f156e8bc36d38.jpeg\")
<\/p>\n![\"Si](\"\/wp-content\/uploads\/2020\/02\/1247f20fa2a12f093d7f1d2361d48a02.jpeg\")
<\/p>\n![\"Si](\"\/wp-content\/uploads\/2020\/02\/f70cd562220c7367e29597d8e8b62f81.jpeg\")
<\/p>\nPlanet p\u00ebr t\u00eb ardhmen e af\u00ebrt<\/h2>\n
\n
\n