{"id":33050,"date":"2019-10-31T21:50:27","date_gmt":"2019-10-31T18:50:27","guid":{"rendered":"https:\/\/prohoster.info\/blog\/application-centric-infrastructure-arhitektura-seti-budushhego-ot-rassuzhdenij-k-delu\/"},"modified":"2019-10-31T21:50:27","modified_gmt":"2019-10-31T18:50:27","slug":"application-centric-infrastructure-arhitektura-seti-budushhego-ot-rassuzhdenij-k-delu","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/application-centric-infrastructure-arhitektura-seti-budushhego-ot-rassuzhdenij-k-delu","title":{"rendered":"Infrastruktura e P\u00ebrqendruar n\u00eb Aplikacione. Arkitektura e rrjetit t\u00eb ardhsh\u00ebm \u2014 nga reflektimi n\u00eb veprim","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

N\u00eb vitet e fundit, Cisco ka promovuar me force nj\u00eb arkitektur\u00eb t\u00eb re p\u00ebr nd\u00ebrtimin e rrjeteve t\u00eb transmetimit t\u00eb t\u00eb dh\u00ebnave n\u00eb QDC - Application Centric Infrastructure (apo ACI)<\/b>. Disa tashm\u00eb jan\u00eb t\u00eb njohur me t\u00eb. Disa madje e kan\u00eb implementuar at\u00eb n\u00eb kompanit\u00eb e tyre, p\u00ebrfshir\u00eb edhe n\u00eb Rusi. Megjithat\u00eb, p\u00ebr shumic\u00ebn e specialist\u00ebve dhe drejtor\u00ebve t\u00eb IT, ACI mbetet ose nj\u00eb akronim i panjohur, ose thjesht nj\u00eb diskutim p\u00ebr t\u00eb ardhmen.
\nN\u00eb k\u00ebt\u00eb artikull, do t\u00eb p\u00ebrpiqemi ta afrojm\u00eb k\u00ebt\u00eb t\u00eb ardhme. P\u00ebr k\u00ebt\u00eb, do t\u00eb flasim p\u00ebr komponent\u00ebt kryesor\u00eb arkitektonik\u00eb t\u00eb ACI, si dhe do t\u00eb ilustrojm\u00eb m\u00ebnyr\u00ebn se si aplikohet n\u00eb praktik\u00eb. P\u00ebr m\u00eb tep\u00ebr, n\u00eb nj\u00eb t\u00eb ardhme t\u00eb af\u00ebrt, do t\u00eb organizojm\u00eb nj\u00eb demonstrim t\u00eb qart\u00eb t\u00eb pun\u00ebs s\u00eb ACI, n\u00eb t\u00eb cilin mund t\u00eb regjistrohet \u00e7do specialist IT t\u00eb interesuar.
\n<\/a><\/noindex>
\nT\u00eb dh\u00ebnat m\u00eb t\u00eb plota mbi k\u00ebt\u00eb arkitektur\u00eb t\u00eb re t\u00eb nd\u00ebrtimit t\u00eb rrjetit do t\u00eb jen\u00eb n\u00eb Sh\u00ebn Petersburg n\u00eb maj 2019. T\u00eb gjitha detajet \u2013 n\u00eb linkun<\/a><\/noindex>. Regjistrohuni!<\/p>\n

Historia e m\u00ebparshme<\/b>
\nModeli tradicional dhe m\u00eb popullor i nd\u00ebrtimit t\u00eb rrjetit \u00ebsht\u00eb modeli hierarkik me tre nivele: b\u00ebrthama -> shp\u00ebrndarja (agregimi) -> akses. Gjat\u00eb shum\u00eb viteve, ky model ka qen\u00eb standarti, dhe p\u00ebr t\u00eb prodhuesit kan\u00eb nxjerr\u00eb pajisje rrjetesh me funksionalitetin p\u00ebrkat\u00ebs.
\nM\u00eb par\u00eb, kur teknologjit\u00eb informative ishin nj\u00eb lloj aneksi t\u00eb nevojsh\u00ebm (dhe, sinqerisht, jo gjithmon\u00eb t\u00eb d\u00ebshiruesh\u00ebm) p\u00ebr biznesin, ky model ishte i p\u00ebrshtatsh\u00ebm, relativisht static dhe i besuesh\u00ebm. Megjithat\u00eb, tani, kur IT \u00ebsht\u00eb nj\u00eb nga drejtuesit e zhvillimit t\u00eb biznesit, dhe n\u00eb shum\u00eb raste edhe vet\u00eb biznesi, staticiteti i k\u00ebtij modeli ka filluar t\u00eb shkaktoj\u00eb probleme t\u00eb m\u00ebdha.<\/p>\n

Biznesi modern gjeneron nj\u00eb sasi t\u00eb madhe k\u00ebrkesash komplekse p\u00ebr infrastruktur\u00ebn e rrjetit. Suksesi i biznesit varet drejtp\u00ebrdrejt nga afatet e realizimit t\u00eb k\u00ebtyre k\u00ebrkesave. Shtyrja n\u00eb k\u00ebto kushte \u00ebsht\u00eb e papranueshme, dhe modeli tradicional i nd\u00ebrtimit t\u00eb rrjetit shpesh nuk lejon t\u00eb plot\u00ebsohen n\u00eb koh\u00eb t\u00eb gjitha nevojat e biznesit. <\/p>\n

P\u00ebr shembull, shfaqja e nj\u00eb aplikacioni t\u00eb ri kompleks t\u00eb biznesit implicon realizimin e nj\u00eb numri t\u00eb madh operacioneve rutin\u00eb t\u00eb nj\u00ebjta nga administrator\u00ebt e rrjetit n\u00eb nj\u00eb shum\u00ebllojshm\u00ebri pajisjesh rrjeti n\u00eb nivele t\u00eb ndryshme. P\u00ebrve\u00e7 se kjo merr shum\u00eb koh\u00eb, ajo gjithashtu rrit rrezikun e gabimeve q\u00eb mund t\u00eb \u00e7ojn\u00eb n\u00eb nd\u00ebrprerje serioze t\u00eb sh\u00ebrbimeve IT dhe, si rezultat, d\u00ebme financiare.<\/p>\n

Nuk jan\u00eb as afatet as kompleksiteti i k\u00ebrkesave q\u00eb jan\u00eb shkaku i problemit. Problemi \u00ebsht\u00eb se k\u00ebto k\u00ebrkesa duhet \"t\u00eb p\u00ebrkthehen\" nga gjuha e aplikacioneve t\u00eb biznesit n\u00eb gjuh\u00ebn e infrastruktur\u00ebs rrjetore. Si\u00e7 dihet, \u00e7do p\u00ebrkthim \u00ebsht\u00eb gjithmon\u00eb nj\u00eb humbje e pjesshme e kuptimit. Kur pronari i aplikacionit flet p\u00ebr logjik\u00ebn e funksionimit t\u00eb aplikacionit t\u00eb tij, administrator\u00ebt e rrjetit kuptojn\u00eb nj\u00eb grup VLAN-ash, lista aksesi n\u00eb dhjet\u00ebra pajisje q\u00eb duhet t\u00eb mbahen, azhurnohen dhe dokumentohen.<\/p>\n

Eksperienca e akumuluar dhe komunikimi i vazhduesh\u00ebm me klient\u00ebt i ka lejuar Cisco t\u00eb projektoj\u00eb dhe implementoj\u00eb parime t\u00eb reja p\u00ebr nd\u00ebrtimin e rrjetit t\u00eb transmetimit t\u00eb t\u00eb dh\u00ebnave p\u00ebr qendrat e p\u00ebrpunimit t\u00eb t\u00eb dh\u00ebnave, t\u00eb cilat p\u00ebrmbushin tendencat moderne dhe jan\u00eb t\u00eb bazuara, n\u00eb radh\u00eb t\u00eb par\u00eb, n\u00eb logjik\u00ebn e aplikacioneve t\u00eb biznesit. Nga k\u00ebtu vjen dhe emri \u2013 Infrastruktur\u00eb e Orientuar ndaj Aplikacioneve.<\/p>\n

Arkitektura ACI.<\/b>
\nDuhet ta shqyrtojm\u00eb arhitektura ACI jo vet\u00ebm nga ana fizike, por edhe nga ana logjike. Ajo \u00ebsht\u00eb e bazuar n\u00eb nj\u00eb model politikash t\u00eb automatizuara, objektet e t\u00eb cilave n\u00eb nivel t\u00eb sip\u00ebrm mund t\u00eb ndahen n\u00eb komponent\u00ebt e m\u00ebposht\u00ebm:<\/p>\n

    \n
  1. Rrjeti i bazuar n\u00eb nd\u00ebrruesit Nexus.<\/li>\n
  2. Klusteri i kontrollor\u00ebve APIC;<\/li>\n
  3. Profili i aplikacioneve;<\/li>\n<\/ol>\n

    \n\"Infrastruktura
    \nT\u00eb shohim secilin nivel m\u00eb n\u00eb detaje \u2013 duke kaluar nga t\u00eb thjeshtat te m\u00eb t\u00eb komplikuarat.<\/p>\n

    Rrjeti i bazuar n\u00eb nd\u00ebrruesit Nexus<\/b>
    \nRrjeti n\u00eb fabrik\u00ebn ACI \u00ebsht\u00eb i ngjash\u00ebm me modelin tradicional hierarkik, por nd\u00ebrtimi \u00ebsht\u00eb shum\u00eb m\u00eb i thjesht\u00eb. P\u00ebrdoret modelin Leaf-Spine p\u00ebr organizimin e rrjetit, i cili \u00ebsht\u00eb b\u00ebr\u00eb nj\u00eb qasje e pranuar gjer\u00ebsisht p\u00ebr implementimin e rrjeteve t\u00eb brezit t\u00eb ri. Ky model p\u00ebrb\u00ebhet nga dy nivele: Spine dhe Leaf, p\u00ebrkat\u00ebsisht.
    \n \"Infrastruktura
    \nNiveli Spine \u00ebsht\u00eb p\u00ebrgjegj\u00ebs vet\u00ebm p\u00ebr performanc\u00ebn. Performanca e p\u00ebrmbledhur e switch-\u00ebve Spine \u00ebsht\u00eb e barabart\u00eb me performanc\u00ebn e gjitha fabrik\u00ebs, prandaj n\u00eb k\u00ebt\u00eb nivel duhet t\u00eb p\u00ebrdoren switch-e me porte 40G ose m\u00eb lart.
    \nSwitch-\u00ebt Spine lidhen me t\u00eb gjitha switch-et e nivelit t\u00eb ardhsh\u00ebm: switch-et Leaf, t\u00eb cilat jan\u00eb lidhur me hostet e fundit. Roli kryesor i switch-eve Leaf \u00ebsht\u00eb kapaciteti i portave. <\/p>\n

    K\u00ebshtu, \u00e7\u00ebshtjet e zgjerimit zgjidhen leht\u00ebsisht: n\u00ebse na nevojitet t\u00eb rrisim kapacitetin e fabrik\u00ebs, ne shtojm\u00eb switch-e Spine, dhe n\u00ebse duam t\u00eb rrisim kapacitetin e portave \u2013 Leaf.
    \nP\u00ebr t\u00eb dy nivelet p\u00ebrdoren switch-et e seris\u00eb Cisco Nexus 9000, t\u00eb cil\u00ebt jan\u00eb mjeti kryesor p\u00ebr Cisco p\u00ebr nd\u00ebrtimin e rrjeteve t\u00eb Qendrave t\u00eb t\u00eb Dh\u00ebnave pavar\u00ebsisht nga arkitektura e tyre. P\u00ebr nivelin Spine p\u00ebrdoren switch-et Nexus 9300 ose Nexus 9500, nd\u00ebrsa p\u00ebr Leaf vet\u00ebm Nexus 9300.
    \nSeria e modeleve t\u00eb switch-eve Nexus, t\u00eb cilat p\u00ebrdoren n\u00eb fabrik\u00ebn ACI, paraqitet n\u00eb figur\u00ebn m\u00eb posht\u00eb.
    \n \"Infrastruktura<\/p>\n

    Klastri i kontrolle APIC (Controller i Politikave t\u00eb Infrastruktur\u00ebs s\u00eb Aplikacioneve) <\/b>
    \nKontroller\u00ebt APIC jan\u00eb server\u00eb fizik\u00eb t\u00eb specializuar, nd\u00ebrsa p\u00ebr implementime t\u00eb vogla lejohet p\u00ebrdorimi i nj\u00eb klastri me nj\u00eb kontroller fizik APIC dhe dy virtual\u00eb.
    \nKontroller\u00ebt APIC kryejn\u00eb funksione menaxhimi dhe monitorimi. \u00cbsht\u00eb e r\u00ebnd\u00ebsishme t\u00eb theksohet se kontrollet nuk marrin pjes\u00eb kurr\u00eb n\u00eb transmetimin e t\u00eb dh\u00ebnave, dmth, edhe n\u00ebse t\u00eb gjith\u00eb kontrollet e klastri d\u00ebshtojn\u00eb, stabiliteti i rrjetit nuk do t\u00eb preket n\u00eb asnj\u00eb m\u00ebnyr\u00eb. Gjithashtu, duhet t\u00eb theksohet se me ndihm\u00ebn e APIC-ve, administrator\u00ebt menaxhojn\u00eb t\u00eb gjith\u00eb burimet fizike dhe logjike t\u00eb fabrik\u00ebs, dhe p\u00ebr t\u00eb b\u00ebr\u00eb \u00e7do ndryshim nuk \u00ebsht\u00eb e nevojshme t\u00eb lidhen me ndonj\u00eb pajisje, pasi n\u00eb ACI p\u00ebrdoret nj\u00eb pik\u00eb e vetme menaxhimi.
    \n \"Infrastruktura<\/p>\n

    Tani, le t\u00eb kalojm\u00eb n\u00eb nj\u00eb nga komponent\u00ebt kryesor\u00eb t\u00eb ACI \u2013 profilin e aplikacioneve.<\/b>
    \nProfili i aplikacionit (Profil i Rrjetit t\u00eb Aplikacioneve)<\/b> \u00ebsht\u00eb baza logjike e ACI. Pik\u00ebrisht profilet e aplikacioneve p\u00ebrcaktojn\u00eb politikat e nd\u00ebrveprimit midis t\u00eb gjitha segmenteve rrjet dhe p\u00ebrshkruajn\u00eb vet\u00eb segmentet rrjet. ANP lejon abstraktimin nga niveli fizik dhe, n\u00eb thelb, p\u00ebrfaq\u00ebson se si duhet t\u00eb organizohet nd\u00ebrveprimi midis segmenteve t\u00eb ndryshme t\u00eb rrjetit nga k\u00ebndv\u00ebshtrimi i aplikacionit. <\/p>\n

    Profil i aplikacionit p\u00ebrb\u00ebhet nga grupe lidhjesh (End-point groups \u2013 EPG). Nj\u00eb grup lidhjesh \u00ebsht\u00eb nj\u00eb grup logjik hostesh (makinash virtuale, serverash fizik\u00eb, konteineresh, etj.), t\u00eb cilat ndodhen n\u00eb nj\u00eb segment sigurie (jo rrjet, por pik\u00ebrisht siguri). Hostet p\u00ebrfundimtar\u00eb, t\u00eb cilat i p\u00ebrkasin nj\u00eb EPG, mund t\u00eb p\u00ebrcaktohen nga nj\u00eb num\u00ebr i madh kriteresh. Zakonisht p\u00ebrdoren kriteret e m\u00ebposhtme: <\/p>\n