{"id":39302,"date":"2019-10-31T22:29:40","date_gmt":"2019-10-31T19:29:40","guid":{"rendered":"https:\/\/prohoster.info\/blog\/kak-aws-varit-svoi-elastichnye-servisy-masshtabirovanie-serverov-i-bazy-dannyh\/"},"modified":"2019-10-31T22:29:40","modified_gmt":"2019-10-31T19:29:40","slug":"kak-aws-varit-svoi-elastichnye-servisy-masshtabirovanie-serverov-i-bazy-dannyh","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/kak-aws-varit-svoi-elastichnye-servisy-masshtabirovanie-serverov-i-bazy-dannyh","title":{"rendered":"Si i \u201cgatuan\u201d AWS sh\u00ebrbimet e veta elastike. Shkall\u00ebzimi i server\u00ebve dhe i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Rekujt e ngjajn\u00eb me nj\u00eb kuti magjike \u2014 k\u00ebrkon at\u00eb q\u00eb t\u00eb nevojitet, dhe burimet thjesht shfaqen nga askund. Makinat virtuale, databazat, rrjeti \u2014 gjith\u00e7ka \u00ebsht\u00eb vet\u00ebm p\u00ebr ty. Ekzistojn\u00eb dhe tenanta t\u00eb tjer\u00eb t\u00eb reve, por n\u00eb universin t\u00ebnd je qeveritari i vet\u00ebm. Je i sigurt se gjithmon\u00eb do t\u00eb marr\u00ebsh burimet e nevojshme, nuk ke nevoj\u00eb t\u00eb n\u00ebnshtrohesh ndaj askujt dhe p\u00ebrcakton vet\u00eb se si do t\u00eb jet\u00eb rrjeti. Si funksionon kjo magji q\u00eb b\u00ebn q\u00eb reja t\u00eb alokoj\u00eb burimet elastike dhe t\u00eb izoloj\u00eb plot\u00ebsisht tenant\u00ebt nga nj\u00ebri-tjetri?<\/p>\n

\"Si
\n
\nReva AWS \u00ebsht\u00eb nj\u00eb sistem megasuperkomplikuar, i cili evoluon q\u00eb nga viti 2006. Nj\u00eb pjes\u00eb e k\u00ebtij zhvillimi ka p\u00ebrfituar Vasiliy Pantyukhin<\/strong> \u2014 arkitekti i Amazon Web Services. Si arkitekt, ai sheh nga brenda jo vet\u00ebm rezultatin p\u00ebrfundimtar, por edhe sfidat q\u00eb ekalon AWS. Sa m\u00eb shum\u00eb kuptim t\u00eb ket\u00eb p\u00ebr funksionimin e sistemit, aq m\u00eb shum\u00eb besim krijohet. Prandaj, Vasili do t\u00eb ndaj\u00eb sekretet e sh\u00ebrbimeve t\u00eb reves AWS. Posht\u00eb, do t\u00eb gjeni struktur\u00ebn e server\u00ebve fizik\u00eb t\u00eb AWS, elasticitetin e shkall\u00ebzueshm\u00ebris\u00eb s\u00eb DB, databaz\u00ebn e personalizuar Amazon dhe metodat p\u00ebr rritjen e performanc\u00ebs s\u00eb makinave virtuale p\u00ebrkrah uljes s\u00eb \u00e7mimit t\u00eb tyre. Njohja e qasjes arkitektonike t\u00eb Amazon do t\u00eb ndihmoj\u00eb n\u00eb p\u00ebrdorimin m\u00eb efektiv t\u00eb sh\u00ebrbimeve AWS dhe ndoshta do t\u00eb ofroj\u00eb ide t\u00eb reja p\u00ebr nd\u00ebrtimin e zgjidhjeve tuaja.
\n<\/a><\/noindex>
\nRreth fol\u00ebsit: Vasili Pantiukhin (Hen<\/a><\/noindex>) filloi si Unix admin n\u00eb kompanit\u00eb.ru, p\u00ebr 6 vjet u angazhua me pajisje t\u00eb m\u00ebdha Sun Microsystem, dhe p\u00ebr 11 vjet predikoi qendrueshm\u00ebrin\u00eb e t\u00eb dh\u00ebnave n\u00eb EMC. N\u00eb m\u00ebnyr\u00eb natyrale evolucionoi n\u00eb re private, dhe n\u00eb vitin 2017 kaloi n\u00eb ato publike. Tani, me k\u00ebshilla teknike ndihmon p\u00ebr t\u00eb jetuar dhe zhvilluar n\u00eb re AWS.<\/p>\n

Disclaim\u00ebr: gjith\u00e7ka m\u00eb posht\u00eb \u00ebsht\u00eb mendimi personal i Vasilit dhe mund t\u00eb mos p\u00ebrputhet me pozitat e Amazon Web Services. Regjistrimi i videos<\/a><\/noindex> i referatit, mbi t\u00eb cilin \u00ebsht\u00eb krijuar ky artikull, \u00ebsht\u00eb i disponuesh\u00ebm n\u00eb kanalin ton\u00eb YouTube.<\/i><\/p>\n

Pse po flas p\u00ebr thelbin e Amazon<\/h2>\n

\nMakina ime e par\u00eb kishte \"dor\u00eb\" \u2014 me transmetim mekanik. Ishte e shk\u00eblqyer p\u00ebr ndjesin\u00eb se mund ta kontrolloja makin\u00ebn dhe ta menaxhoja plot\u00ebsisht. M\u00eb p\u00eblqente gjithashtu se t\u00eb pakt\u00ebn e kuptoja n\u00eb nj\u00eb far\u00eb m\u00ebnyre principin e funksionimit t\u00eb saj. Sigurisht, e p\u00ebrfytyroja funksionimin e kutis\u00eb mjaft primitivisht \u2014 diku si nj\u00eb kuti shpejt\u00ebsie n\u00eb bi\u00e7iklet\u00eb.<\/p>\n

\"Si
\n
\nE gjitha ishte e shk\u00eblqyer, p\u00ebrve\u00e7 nj\u00eb gj\u00ebje \u2014 q\u00ebndrimit n\u00eb trafik. Si\u00e7 duket, ulur dhe nuk b\u00ebj asgj\u00eb, por vazhdimisht kaloj n\u00eb ingranazhe, shtyp frik\u00ebn, gazin, frenin \u2014 nga kjo, ndiej v\u00ebrtet lodhje. Problemi i trafikut u zgjidh pjes\u00ebrisht kur n\u00eb familje erdhi nj\u00eb makin\u00eb automatike. Pas timonit, pati koh\u00eb t\u00eb mendoj p\u00ebr di\u00e7ka, t\u00eb d\u00ebgjoj nj\u00eb audioklib\u00ebr.<\/p>\n

Nj\u00eb mister tjet\u00ebr u shfaq n\u00eb jet\u00ebn time, sepse un\u00eb sapo ndalova s\u00eb kuptuari si funksionon makina ime. Nj\u00eb makin\u00eb moderne \u2014 \u00ebsht\u00eb nj\u00eb pajisje e nd\u00ebrlikuar. Ajo adaptohet n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb ndaj dhjetra parametrave t\u00eb ndrysh\u00ebm: shtypi mbi gaz, fren, stili i vozitjes, cil\u00ebsia e rrug\u00ebs. Un\u00eb s'po e kuptoj m\u00eb se si funksionon kjo.<\/p>\n

Kur fillova t\u00eb merrem me Amazon Cloud, kjo ishte gjithashtu nj\u00eb mister p\u00ebr mua. Por ky mister \u00ebsht\u00eb nj\u00eb shkall\u00eb m\u00eb i lart\u00eb, sepse n\u00eb makin\u00eb ka nj\u00eb shofer, nd\u00ebrsa n\u00eb AWS jan\u00eb miliona. T\u00eb gjith\u00eb p\u00ebrdoruesit drejtojn\u00eb n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, shtypin gazin dhe frenin. \u00cbsht\u00eb e mrekullueshme q\u00eb ata arrijn\u00eb atje ku duan \u2014 p\u00ebr mua, kjo \u00ebsht\u00eb nj\u00eb mrekulli! Sistemi adaptohet automatikisht, shkall\u00ebzohet dhe p\u00ebrshtatet elastikisht me secilin p\u00ebrdorues, aq sa ai mendon se \u00ebsht\u00eb vet\u00ebm n\u00eb k\u00ebt\u00eb Univers.<\/p>\n

Magjia paksa u shp\u00ebrb\u00eb kur m\u00eb von\u00eb erdha t\u00eb punoj si arkitekt n\u00eb Amazon. Pash\u00eb p\u00ebrballjet q\u00eb kishim, si i zgjidhim ato, si zhvillojm\u00eb sh\u00ebrbimet. Me rritjen e kuptimit t\u00eb funksionimit t\u00eb sistemit, rritet besimi n\u00eb sh\u00ebrbim. Prandaj, d\u00ebshiroj t\u00eb ndaj pamjen e asaj q\u00eb ndodhet n\u00ebn kapak\u00ebt e AWS Cloud.<\/p>\n

P\u00ebr \u00e7far\u00eb do t\u00eb flasim<\/h2>\n

\nKam zgjedhur nj\u00eb qasje diversifikuar \u2014 kam p\u00ebrzgjedhur 4 sh\u00ebrbime interesante, p\u00ebr t\u00eb cilat ia vlen t\u00eb flasim.<\/p>\n

Optimizimi i server\u00ebve<\/strong>. Cloud-et efemer me p\u00ebrmasat fizike: qendrat e t\u00eb dh\u00ebnave fizike, ku jan\u00eb server\u00eb fizik\u00eb, q\u00eb zhurmojn\u00eb, ngrohen dhe ndri\u00e7ohen me ndri\u00e7im.<\/p>\n

Funksionet Serverless <\/strong>(Lambda) \u2014 ndoshta sh\u00ebrbimi m\u00eb i shkall\u00ebzuar n\u00eb cloud.<\/p>\n

Shk\u00ebmbimi i baz\u00ebs s\u00eb t\u00eb dh\u00ebnave<\/strong>. Do t\u00eb flas p\u00ebr m\u00ebnyr\u00ebn se si nd\u00ebrtuam bazat tona t\u00eb dh\u00ebnash t\u00eb shkall\u00ebzuara.<\/p>\n

Shkall\u00ebzimi i rrjetit<\/strong>. Pjesa e fundit, ku do t\u00eb zbuloj nd\u00ebrtimin e rrjetit ton\u00eb. Kjo \u00ebsht\u00eb nj\u00eb gj\u00eb e mrekullueshme \u2014 \u00e7do p\u00ebrdorues i cloud mendon se \u00ebsht\u00eb vet\u00ebm n\u00eb cloud dhe nuk e sheh fare t\u00eb tjer\u00ebt.<\/p>\n

Sh\u00ebnim. N\u00eb k\u00ebt\u00eb artikull do t\u00eb flasim p\u00ebr optimizimin e server\u00ebve dhe zgjerimin e bazave t\u00eb dh\u00ebnash. Zgjerimi i rrjetit do t\u00eb shqyrtohet n\u00eb artikullin tjet\u00ebr. Ku jan\u00eb funksionet serverless? P\u00ebr to \u00ebsht\u00eb publikuar nj\u00eb shpjegim i ve\u00e7ant\u00eb \"I vog\u00ebl, por i fuqish\u00ebm. Unboxing mikrovirtualizuesi Firecracker<\/a><\/noindex>'. N\u00eb t\u00eb ndodhen disa metoda t\u00eb ndryshme t\u00eb zgjerimit, dhe zgjidhja Firecracker \u00ebsht\u00eb shqyrtuar n\u00eb detaje - nj\u00eb simbioz\u00eb e cil\u00ebsive m\u00eb t\u00eb mira t\u00eb makinave virtuale dhe konteiner\u00ebve.<\/i><\/p><\/blockquote>\n

<\/p>\n

Server\u00ebt<\/h2>\n

\nRevolucioni i cloud-it \u00ebsht\u00eb efemer. Por kjo efemeritet ka nj\u00eb manifestim fizik - server\u00ebt. Fillimisht, arkitektura e tyre ishte klasike. \u00c7ipseti standard x86, kartat e rrjetit, Linux, hipervizori Xen, mbi t\u00eb cilin funksiononin makinat virtuale.<\/p>\n

\"Si
\n
\nN\u00eb vitin 2012, nj\u00eb arkitektur\u00eb e till\u00eb arrinte t\u00eb p\u00ebrballonte detyrat e saj. Xen \u00ebsht\u00eb nj\u00eb hipervizor i shk\u00eblqyer, por ka nj\u00eb disavantazh t\u00eb r\u00ebnd\u00ebsish\u00ebm. Ai ka shpenzime t\u00eb larta p\u00ebr emulimin e pajisjeve<\/strong>. Me daljen n\u00eb treg t\u00eb kartave t\u00eb reja rrjeti m\u00eb t\u00eb shpejta ose disk\u00ebve SSD, k\u00ebto shpenzime b\u00ebhen tep\u00ebr t\u00eb larta. Si mund ta zgjidhim k\u00ebt\u00eb problem? Vendos\u00ebm t\u00eb punojm\u00eb n\u00eb dy fronte - optimizimin e harduerit dhe hipervizorit<\/strong>. Kjo \u00ebsht\u00eb nj\u00eb detyr\u00eb shum\u00eb e r\u00ebnd\u00ebsishme.<\/p>\n

Optimizimi i harduerit dhe hipervizorit<\/h3>\n

\nT\u00eb b\u00ebsh gjith\u00e7ka nj\u00ebher\u00ebsh dhe mir\u00eb nuk do t\u00eb funksionoj\u00eb. \u00c7far\u00eb \u00ebsht\u00eb \"mir\u00eb\", fillimisht gjithashtu ishte e paqart\u00eb.<\/p>\n

Vendos\u00ebm t\u00eb p\u00ebrdorim nj\u00eb qasje evolucionare - t\u00eb ndryshojm\u00eb nj\u00eb element t\u00eb r\u00ebnd\u00ebsish\u00ebm t\u00eb arkitektur\u00ebs dhe ta hedhim at\u00eb n\u00eb prodhim.<\/p><\/blockquote>\n

K\u00ebrkojm\u00eb t\u00eb p\u00ebrballojm\u00eb \u00e7do penges\u00eb, d\u00ebgjojm\u00eb ankesat dhe sugjerimet. Pastaj ndryshojm\u00eb nj\u00eb tjet\u00ebr komponent. K\u00ebshtu, me inkrementime t\u00eb vogla, transformojm\u00eb t\u00ebr\u00eb arkitektur\u00ebn bazuar n\u00eb reagimet nga p\u00ebrdoruesit dhe mb\u00ebshtetjen.<\/p>\n

Transformimet filluan n\u00eb vitin 2013 me m\u00eb t\u00eb v\u00ebshtir\u00ebn - rrjetin. N\u00eb C3<\/strong> instancat, karta standarde e rrjetit u shtua me nj\u00eb kart\u00eb speciale Network Accelerator. Ajo u lidh literalisht me nj\u00eb kabllo loopback n\u00eb panelin e p\u00ebrparm\u00eb. E sh\u00ebmtuar, por n\u00eb cloud nuk duket. Megjithat\u00eb, nd\u00ebrveprimi direkt me harduerin p\u00ebrmir\u00ebsoi ndjesh\u00ebm jitter-in dhe kapacitetin e rrjetit.<\/p>\n

M\u00eb pas u vendos t\u00eb p\u00ebrmir\u00ebsojm\u00eb qasjen n\u00eb ruajtjen e dh\u00ebnave EBS - Elastic Block Storage. Kjo \u00ebsht\u00eb nj\u00eb kombinim i rrjetit dhe magazinimit. Sfid\u00eb \u00ebsht\u00eb se n\u00ebse n\u00eb treg ekzistonin karta Network Accelerator, mund\u00ebsia p\u00ebr t\u00eb bler\u00eb harduerin Storage Accelerator nuk kishte. Prandaj, ne iu drejtua nj\u00eb startup-i Annapurna Labs<\/strong>, e cila zhvilloi p\u00ebr ne \u00e7ipa t\u00eb specializuar ASIC. K\u00ebta lejuan lidhjen e volumeve t\u00eb larg\u00ebta EBS si pajisje NVMe.<\/p>\n

N\u00eb instancat C4<\/strong> ne zgjodh\u00ebm dy sfida. E para \u2014 realizuam nj\u00eb plan t\u00eb ardhsh\u00ebm p\u00ebr teknologjin\u00eb e re NVMe. E dyta \u2014 ndjesh\u00ebm ngarkuam procesorin qendror duke transferuar p\u00ebrpunimin e k\u00ebrkesave p\u00ebr EBS n\u00eb nj\u00eb kart\u00eb t\u00eb re. Doli mir\u00eb, prandaj tani Annapurna Labs \u2014 \u00ebsht\u00eb pjes\u00eb e Amazon.<\/p>\n

N\u00eb n\u00ebntor t\u00eb vitit 2017, ne kuptuam se erdhi koha p\u00ebr t\u00eb ndryshuar edhe hipervizorin.<\/p>\n

Hipervizori i ri u zhvillua mbi baz\u00ebn e moduleve t\u00eb p\u00ebrmir\u00ebsuara t\u00eb b\u00ebrtham\u00ebs KVM.<\/p><\/blockquote>\n

Ai lejon t\u00eb reduktohen ndjesh\u00ebm kostot p\u00ebr emulimin e pajisjeve dhe t\u00eb punoj\u00eb direkt me ASIC-t\u00eb e rinj. Instancat C5<\/strong> isht\u00eb virtualizimi i par\u00eb, n\u00ebn kapu\u00e7in e t\u00eb cilit punon hipervizori i ri. Ne e quajt\u00ebm at\u00eb Nitro<\/strong>.<\/p>\n

\"SiEvolucioni i instancave n\u00eb nj\u00eb shkall\u00eb kohore.<\/em><\/p>\n

T\u00eb gjitha llojet e reja t\u00eb makinave virtuale q\u00eb u shfaq\u00ebn q\u00eb nga n\u00ebntori 2017, punojn\u00eb mbi k\u00ebt\u00eb hipervizor. Makinat Bare Metal nuk kan\u00eb hipervizor<\/strong>, por ato gjithashtu quhen Nitro, pasi ato p\u00ebrdorin karta t\u00eb specializuara Nitro.<\/p>\n

N\u00eb dy vitet e ardhshme, numri i llojeve t\u00eb instancave Nitro tejkaloi disa dhjet\u00ebra: A1, C5, M5, T3 dhe t\u00eb tjera.<\/p>\n

\"Si
\nLlojet e instancave.<\/em><\/p>\n

Si jan\u00eb t\u00eb organizuara makinat Nitro moderne<\/h3>\n

\nAto kan\u00eb tre komponent\u00eb kryesor\u00eb: hipervizorin Nitro (p\u00ebr t\u00eb cilin u diskutua m\u00eb lart), \u00e7ipin e siguris\u00eb dhe kartat Nitro.<\/p>\n

\u00c7ipi i siguris\u00eb<\/strong> \u00ebsht\u00eb i integruar pik\u00ebrisht n\u00eb bord. Ai kontrollon shum\u00eb funksione t\u00eb r\u00ebnd\u00ebsishme, p\u00ebr shembull, kontrollin e ngarkes\u00ebs s\u00eb OS-s\u00eb s\u00eb hostit.<\/p>\n

Kartat Nitro<\/strong> - ato ekzistojn\u00eb n\u00eb kat\u00ebr lloje. T\u00eb gjitha jan\u00eb zhvilluar nga Annapurna Labs dhe bazohen n\u00eb ASIC t\u00eb zakonsh\u00ebm. Nj\u00eb pjes\u00eb e firmware-t t\u00eb tyre gjithashtu \u00ebsht\u00eb e p\u00ebrbashk\u00ebt.<\/p>\n

\"Si
\nKat\u00ebr lloje kartash Nitro.<\/em><\/p>\n

Nj\u00eb nga kartat \u00ebsht\u00eb e destinuar p\u00ebr t\u00eb punuar me rrjetin<\/strong>VPC<\/strong>. Ajo \u00ebsht\u00eb e dukshme n\u00eb virtualizime si karta rrjetit ENA \u2014 Adaptori i Rrjetit Elastik<\/strong>. Ajo gjithashtu inkapsulon trafikun gjat\u00eb transmetimit p\u00ebrmes rrjetit fizik (p\u00ebr k\u00ebt\u00eb do flasim n\u00eb pjes\u00ebn e dyt\u00eb t\u00eb artikullit), kontrollon Firewall grupet e Siguris\u00eb, p\u00ebrgjigjet p\u00ebr ruterimin dhe gj\u00ebra t\u00eb tjera rrjetore.<\/p>\n

Kartat e ve\u00e7anta punojn\u00eb me ruajtjen bllokuese EBS<\/strong> dhe disk\u00ebt, t\u00eb cil\u00ebt jan\u00eb t\u00eb integruar n\u00eb server. P\u00ebr makin\u00ebn virtuale t\u00eb pritjes ato paraqiten si adaptues NVMe<\/strong>. Ato gjithashtu p\u00ebrgjigjen p\u00ebr enkriptimin e t\u00eb dh\u00ebnave dhe monitorimin e disqeve.<\/p>\n

Sistemi i kartave Nitro, hipervizorit dhe \u00e7ipit t\u00eb siguris\u00eb \u00ebsht\u00eb i bashkuar n\u00eb nj\u00eb rrjet SDN ose Rrjeti i Definimit t\u00eb Softuerit<\/strong>. P\u00ebr menaxhimin e k\u00ebtij rrjeti (Control Plane) p\u00ebrgjigjet kontrolluesi i hart\u00ebs<\/strong>.<\/p>\n

Sigurisht, ne vazhdojm\u00eb zhvillimin e ASIC-ve t\u00eb rinj. P\u00ebr shembull, n\u00eb fund t\u00eb vitit 2018, \u00e7release \u00e7ipi Inferentia, i cili lejon nj\u00eb funksionim m\u00eb efikas me detyrat e m\u00ebsimit t\u00eb makinerive.<\/p>\n

\"Si
\n\u00c7ipi Inferentia Procesori i M\u00ebsimit t\u00eb Makinerive.<\/em><\/p>\n

Baza e dh\u00ebnash e shkall\u00ebzuar<\/h2>\n

\nNj\u00eb baz\u00eb e dh\u00ebnash tradicionale ka nj\u00eb struktur\u00eb t\u00eb stratifikuar. N\u00ebse e thjeshtojm\u00eb shum\u00eb, mund t\u00eb identifikojm\u00eb nivelet e m\u00ebposhtme.<\/p>\n