{"id":38966,"date":"2019-10-31T22:27:03","date_gmt":"2019-10-31T19:27:03","guid":{"rendered":"https:\/\/prohoster.info\/blog\/admin-bez-ruk-giperkonvergentsiya\/"},"modified":"2019-10-31T22:27:03","modified_gmt":"2019-10-31T19:27:03","slug":"admin-bez-ruk-giperkonvergentsiya","status":"publish","type":"post","link":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/admin-bez-ruk-giperkonvergentsiya","title":{"rendered":"Administrators bez rok\u0101m = hiperkonver\u0123ence?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Administrators bez rok\u0101m = hiperkonver\u0123ence?\" src=\"\/wp-content\/uploads\/2019\/10\/ea1763132185c97bb4edf0e67640d58f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<img decoding=\"async\" alt=\"Administrators bez rok\u0101m = hiperkonver\u0123ence?\" src=\"\/wp-content\/uploads\/2019\/10\/b6355c444c310570e1f2619cd931e1ca.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTas ir m\u012bts, kas diezgan izplat\u012bts serveru aparat\u016bras jom\u0101. Tom\u0113r praks\u0113 hiperkonver\u0123ent\u0101s risin\u0101jumi (kad viss ir vien\u0101) ir nepiecie\u0161ami daudz\u0101m liet\u0101m. V\u0113sturiski pirm\u0101s arhitekt\u016bras izstr\u0101d\u0101ja Amazon un Google saviem pakalpojumiem. Toreiz ideja bija izveidot skait\u013co\u0161anas saimniec\u012bbu no vien\u0101diem mezgliem, katram no kuriem ir savi diski. Viss tika apvienots ar k\u0101du sist\u0113mas veidojo\u0161o programmat\u016bru (hiper-vizoru) un sadal\u012bts virtu\u0101laj\u0101s ma\u0161\u012bn\u0101s. Galvenais m\u0113r\u0137is ir minim\u0101ls darbs vienas mezglu apkalpo\u0161anai un minim\u0101las probl\u0113mas m\u0113rogojot: vienk\u0101r\u0161i ieg\u0101d\u0101j\u0101ties v\u0113l t\u016bkstoti vai divas t\u0101du pa\u0161u serveru un pievienojat tos blakus. Praks\u0113 tas ir vienreiz\u0113ji gad\u012bjumi, un daudz bie\u017e\u0101k runa ir par maz\u0101ku mezglu skaitu un nedaudz citu arhitekt\u016bru. <\/p>\n<p>Bet priek\u0161roc\u012bba paliek t\u0101 pati \u2014 neticama m\u0113rogo\u0161anas un p\u0101rvald\u012bbas vienk\u0101r\u0161\u012bba. M\u012bnuss ir t\u0101ds, ka da\u017e\u0101das uzdevumu veidi da\u017e\u0101di pat\u0113r\u0113 resursus, un kaut kur lok\u0101lo disku b\u016bs daudz, kaut kur ir maz RAM un t\u0101 t\u0101l\u0101k, t\u0101tad pie da\u017e\u0101diem uzdevumu veidiem samazin\u0101s resursu izmanto\u0161ana. <\/p>\n<p>Izr\u0101d\u012bj\u0101s, ka j\u016bs maks\u0101jat par 10\u201315% vair\u0101k par iestat\u012b\u0161anas \u0113rtumu. Tas ar\u012b izrais\u012bja m\u012btu no virsraksta. M\u0113s ilgi mekl\u0113j\u0101m, kur tehnolo\u0123ija b\u016btu optim\u0101li piem\u0113rojama, un atrad\u0101m. Probl\u0113ma bija t\u0101da, ka Cisco nebija savu uzglab\u0101\u0161anas risin\u0101jumu, bet vi\u0146i v\u0113l\u0113j\u0101s pilnu serveru tirgu. Un vi\u0146i izveidoja Cisco Hyperflex \u2014 risin\u0101jumu ar lok\u0101lajiem uzglab\u0101\u0161anas risin\u0101jumiem mezglos. <\/p>\n<p>Un no t\u0101 izn\u0101ca \u013coti labs risin\u0101jums rezerves datu centriem (Disaster Recovery). K\u0101p\u0113c un k\u0101 \u2014 tagad to izst\u0101st\u012b\u0161u. Un par\u0101d\u012b\u0161u klastera testus. <noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Kur nepiecie\u0161ams<\/h3>\n<p>\nHiperkonver\u0123ence \u2014 tas ir: <\/p>\n<ol>\n<li>Disku p\u0101rvieto\u0161ana skait\u013co\u0161anas mezglos.<\/li>\n<li>Pilnv\u0113rt\u012bga datu uzglab\u0101\u0161anas sist\u0113mas integr\u0101cija ar virtualiz\u0101cijas sist\u0113mu.<\/li>\n<li>P\u0101rvieto\u0161ana\/integr\u0101cija ar t\u012bkla sist\u0113mu.<\/li>\n<\/ol>\n<p>\n\u0160\u0101da saikne \u013cauj realiz\u0113t daudzas glab\u0101\u0161anas sist\u0113mas funkcijas virtualiz\u0101cijas l\u012bmen\u012b, un visu no viena vad\u012bbas loga.<\/p>\n<p>M\u016bsu uz\u0146\u0113mum\u0101 ir \u013coti piepras\u012bti rezerves datu centru projekt\u0113\u0161anas projekti, un bie\u017ei tiek izv\u0113l\u0113ts tie\u0161i hiperkonver\u0123ents risin\u0101jums daudz\u0101s replik\u0101cijas opcij\u0101s (l\u012bdz metroklasterim) no t\u016bl\u012bt\u0113jas pieejam\u012bbas. <\/p>\n<p>Datu centr\u0101 rezerv\u0101cijas gad\u012bjum\u0101 parasti runa ir par att\u0101lin\u0101tu objektu cit\u0101 pils\u0113tas mal\u0101 vai pat cit\u0101 pils\u0113t\u0101. Tas \u013cauj atjaunot kritiskas sist\u0113mas da\u013c\u0113ja vai piln\u012bga galven\u0101 datu centra (DC) atteikuma gad\u012bjum\u0101. Dati past\u0101v\u012bgi tiek replik\u0113ti no produkcijas, un \u0161\u012b replik\u0101cija var notikt gan lietojumprogrammas, gan blok\u0161\u0137iedras ier\u012bces l\u012bmen\u012b (SAS).<\/p>\n<p>T\u0101d\u0113\u013c tagad st\u0101st\u012b\u0161u par sist\u0113mas uzb\u016bvi un testiem, bet p\u0113c tam par da\u017eiem re\u0101la pielietojuma scen\u0101rijiem ar ietaup\u012bto datu inform\u0101ciju. <\/p>\n<h3>Testi<\/h3>\n<p>\nM\u016bsu instance sast\u0101v no \u010detriem serveriem, katr\u0101 no kuriem ir 10 SSD diski ar 960 GB ietilp\u012bbu. Ir atsevi\u0161\u0137s disks rakst\u012b\u0161anas oper\u0101ciju ke\u0161\u0113\u0161anai un pakalpojuma virtu\u0101l\u0101s ma\u0161\u012bnas glab\u0101\u0161anai. Pa\u0161reiz\u0113jais risin\u0101jums ir ceturt\u0101 versija. Pirmais bija ac\u012bmredzami neizstr\u0101d\u0101ts (saska\u0146\u0101 ar atsauksm\u0113m), otrais ir joproj\u0101m neizstr\u0101d\u0101ts, tre\u0161ais jau ir pietiekami stabils, bet \u0161o var uzskat\u012bt par versiju p\u0113c beta test\u0113\u0161anas pabeig\u0161anas pla\u0161ai auditorijai. Test\u0113\u0161anas laik\u0101 probl\u0113mu man nebija, viss str\u0101d\u0101 nevainojami.<\/p>\n<p><b class=\"spoiler_title\">Izmai\u0146as v4<\/b>Nov\u0113rsta vairums k\u013c\u016bdu. <\/p>\n<p>S\u0101kotn\u0113ji platforma var\u0113ja darboties tikai ar hipervizoru VMware ESXi un atbalst\u012bja nelielu skaitu mezglu. Turkl\u0101t izvieto\u0161anas process t\u0101lu ne vienm\u0113r beidz\u0101s veiksm\u012bgi, n\u0101c\u0101s restart\u0113t da\u017eus so\u013cus, bija probl\u0113mas atjauninot no vec\u0101k\u0101m versij\u0101m, dati GUI ne vienm\u0113r tika att\u0113loti pareizi (lai gan es joproj\u0101m neesmu apmierin\u0101ts ar veiktsp\u0113jas grafiku att\u0113lo\u0161anu), da\u017ereiz bija probl\u0113mas saskares viet\u0101s ar virtualiz\u0101ciju.<\/p>\n<p>Tagad visas b\u0113rnu slim\u012bbas ir nov\u0113rstas, HyperFlex atbalsta gan ESXi, gan Hyper-V, turkl\u0101t iesp\u0113jami:<\/p>\n<ol>\n<li>Izveidot izpletni klasteri. <\/li>\n<li>Izveidot klasteri birojiem, neizmantojot Fabric Interconnect, no diviem l\u012bdz \u010detriem mezgliem (ieg\u0101d\u0101jamies tikai serverus).<\/li>\n<li>Iesp\u0113ja str\u0101d\u0101t ar \u0101r\u0113jiem SAS.<\/li>\n<li>Atbalsts konteineriem un Kubernetes.<\/li>\n<li>Izveidot pieejam\u012bbas zonas.<\/li>\n<li>Integr\u0101cija ar VMware SRM, ja ieb\u016bv\u0113tais funkcionalit\u0101te neapmierina.<\/li>\n<\/ol>\n<p>Architekt\u016bra b\u016btiski neat\u0161\u0137iras no galveno konkurentu risin\u0101jumiem, un velosip\u0113du nav izstr\u0101d\u0101ju\u0161i. Tas viss darbojas uz VMware vai Hyper-V virtualiz\u0101cijas platformas. Aparat\u016bra ir izvietota uz Cisco UCS izstr\u0101d\u0101tajiem serveriem. Ir t\u0101di, kuri ien\u012bst platformu par relat\u012bvo sare\u017e\u0123\u012bt\u012bbu s\u0101kotn\u0113j\u0101 iestat\u012bjum\u0101, daudz\u0101m pog\u0101m, netrivi\u0101lo veid\u0146u un atkar\u012bbu sist\u0113mu, bet ir ar\u012b tie, kuri ir iepazinu\u0161ies ar zen, ieinteres\u0113ju\u0161ies par ideju un vairs nev\u0113las str\u0101d\u0101t ar citiem serveriem. <\/p>\n<p>M\u0113s apskat\u012bsim risin\u0101jumu tie\u0161i VMware, jo tas tika s\u0101kotn\u0113ji izstr\u0101d\u0101ts tie\u0161i tam un tam ir liel\u0101ka funkcionalit\u0101te, bet Hyper-V izstr\u0101d\u0101ta pa ce\u013cam, lai nes\u0101ktu atpalikt no konkurentiem un atbilstu tirgus cer\u012bb\u0101m.<\/p>\n<p>Ir klasteris no serveriem, kas piepild\u012bti ar diskiem. Ir diskus datu glab\u0101\u0161anai (SSD vai HDD \u2014 k\u0101 jums pat\u012bk un k\u0101das ir j\u016bsu vajadz\u012bbas), un ir viens SSD disks ke\u0161atmi\u0146ai. Ierakstot datus datu kr\u0101tuv\u0113, dati tiek saglab\u0101ti ke\u0161atmi\u0146as sl\u0101n\u012b (velt\u012bts SSD disks un RAM servisa VM). Paral\u0113li datu bloks tiek s\u016bt\u012bts uz klastera mezgliem (mezglu skaits atkar\u012bgs no klastera replik\u0101cijas faktora). P\u0113c apstiprin\u0101juma no visiem mezgliem par veiksm\u012bgu ierakstu apstiprin\u0101juma e-pasts tiek nos\u016bt\u012bts hipervizoram un t\u0101l\u0101k \u2014 VM. Ierakst\u012btie dati fon\u0101 tiek deduplic\u0113ti, saspie\u017eami un ierakst\u012bti glab\u0101\u0161anas diskos. Taj\u0101 pa\u0161\u0101 laik\u0101 uz glab\u0101\u0161anas diskiem vienm\u0113r tiek ierakst\u012bts liels bloks sec\u012bgi, kas samazina slodzi uz glab\u0101\u0161anas diskiem.<\/p>\n<p>Deduplication un kompresija ir past\u0101v\u012bgi iesl\u0113gti, un tos nevar izsl\u0113gt. Datu las\u012b\u0161ana notiek tie\u0161i no glab\u0101\u0161anas diskiem vai no RAM ke\u0161atmi\u0146as. Ja tiek izmantota hibr\u012bda konfigur\u0101cija, tad las\u012b\u0161ana ar\u012b tiek ke\u0161ota uz SSD diska.<\/p>\n<p>Dati nav piesaist\u012bti pa\u0161reiz\u0113jai virtu\u0101l\u0101s ma\u0161\u012bnas atra\u0161an\u0101s vietai un tiek sadal\u012bti starp mezgliem vienm\u0113r\u012bgi. \u0160\u0101da pieeja \u013cauj vienm\u0113r\u012bgi noslogot visus diskus un t\u012bkla interfeisus. V\u0113l viens ac\u012bmredzams tr\u016bkums ir: m\u0113s nevaram maksim\u0101li samazin\u0101t las\u012b\u0161anas aizkavi, jo nav garantijas par datu pieejam\u012bbu lok\u0101li. Bet es uzskatu, ka tas ir nenoz\u012bm\u012bgs upuris sal\u012bdzin\u0101jum\u0101 ar ieg\u016btajiem ieguvumiem. Turkl\u0101t t\u012bkla aizkaves ir sasniegu\u0161as t\u0101das v\u0113rt\u012bbas, ka praktiski neietekm\u0113 kop\u0113jo rezult\u0101tu.<\/p>\n<p>Par visu diskosist\u0113mas lo\u0123iku atbild \u012bpa\u0161a pakalpojumu VM Cisco HyperFlex Data Platform controller, kas tiek izveidota katr\u0101 glab\u0101\u0161anas mezgl\u0101. M\u016bsu konfigur\u0101cij\u0101 pakalpojumu VM tika pie\u0161\u0137irti asto\u0146i vCPU un 72 GB RAM, kas nav nemaz tik maz. Atg\u0101dinu, ka pa\u0161am hostam ir pieejami 28 fiziski kodoli un 512 GB RAM.<\/p>\n<p>Pakalpojumu VM piek\u013c\u016bst fiziskajiem diskam tie\u0161i, izmantojot SAS kontroliera p\u0101rb\u012bd\u012b\u0161anu uz VM. Sazi\u0146a ar hipervizoru notiek caur \u012bpa\u0161u IOVisor moduli, kas uztver I\/O oper\u0101cijas, un, izmantojot a\u0123entu, kas \u013cauj nos\u016bt\u012bt komandas hipervizora API. A\u0123ents atbild par darbu ar HyperFlex momentuz\u0146\u0113mumiem un kloniem.<\/p>\n<p>Hipervizor\u0101 diskresursi tiek mont\u0113ti k\u0101 NFS vai SMB koplieto\u0161anas (atkar\u012bb\u0101 no hipervizora veida, uzminiet, kur\u0161 kur). Bet zem v\u0101ka t\u0101 ir izklied\u0113ta failu sist\u0113ma, kas \u013cauj pievienot pieaugu\u0161iem piln\u012bg\u0101m SDD: pl\u0101na apjoma pie\u0161\u0137ir\u0161anu, saspi\u0161anu un deduplic\u0113\u0161anu, momentuz\u0146\u0113mumus ar Redirect-on-Write tehnolo\u0123iju, sinhrono\/asinhrono replik\u0101ciju.<\/p>\n<p>Pakalpojumu VM nodro\u0161ina piek\u013cuvi HyperFlex apak\u0161sist\u0113mas p\u0101rvald\u012bbas WEB interfeisam. Ir integr\u0101cija ar vCenter, un liel\u0101ko da\u013cu ikdienas uzdevumu var veikt no t\u0101, ta\u010du datu veikali, piem\u0113ram, \u0113rt\u0101k ir sagriezt no atsevi\u0161\u0137as t\u012bmek\u013ca lapas, ja esat jau p\u0101rg\u0101ju\u0161i uz \u0101tru HTML5 interfeisu, vai izmantot pilnv\u0113rt\u012bgu Flash klientu ar pilnu integr\u0101ciju. Pakalpojumu t\u012bmek\u013ca lap\u0101 var apskat\u012bt sist\u0113mas veiktsp\u0113ju un detaliz\u0113tu statusu.<\/p>\n<p><img decoding=\"async\" alt=\"Administrators bez rok\u0101m = hiperkonver\u0123ence?\" src=\"\/wp-content\/uploads\/2019\/10\/4f603b38d6489836892bebc76663eb2f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nIr ar\u012b cita veida mezgli klaster\u012b \u2014 skait\u013co\u0161anas mezgli. Tie var b\u016bt rack vai blade serveri bez ieb\u016bv\u0113tiem diskiem. \u0160ajos serveros var darbin\u0101t VM, kuru dati tiek glab\u0101ti serveros ar diskiem. Piek\u013cuves datiem zi\u0146\u0101 starp mezglu veidiem nav at\u0161\u0137ir\u012bbas, jo arhitekt\u016bra paredz abstrakciju no datu fizisk\u0101 izvietojuma. Maksim\u0101lais skait\u013co\u0161anas mezglu un glab\u0101\u0161anas mezglu attiec\u012bba ir 2:1.<\/p>\n<p>Skait\u013co\u0161anas mezglu izmanto\u0161ana palielina elast\u012bbu, papla\u0161inot klastera resursus: mums nav oblig\u0101ti j\u0101ieg\u0101d\u0101jas mezgli ar diskiem, ja mums ir vajadz\u012bbas tikai p\u0113c CPU\/RAM. Turkl\u0101t m\u0113s varam pievienot blade grozu un ieg\u016bt ietaup\u012bjumus serveru novieto\u0161an\u0101 skap\u012b.<\/p>\n<p>K\u0101 rezult\u0101t\u0101 mums ir hiperkonver\u0123enta platforma ar \u0161\u0101d\u0101m funkcij\u0101m:<\/p>\n<ul>\n<li>L\u012bdz 64 mezgliem klaster\u012b (l\u012bdz 32 uzglab\u0101\u0161anas mezgliem).<\/li>\n<li>Minim\u0101lais mezglu skaits klaster\u012b ir tr\u012bs (divi \u2014 Edge klasterim).<\/li>\n<li>Datu redundances meh\u0101nisms: mirroring ar replik\u0101cijas faktoru 2 un 3.<\/li>\n<li>Metro klasteris.<\/li>\n<li>Asinhron\u0101 VM replik\u0101cija cit\u0101 HyperFlex klaster\u012b.<\/li>\n<li>Orkestr\u0101cija VM p\u0101rl\u0113k\u0161anai uz att\u0101lo datu centru.<\/li>\n<li>Native snapshot, izmantojot Redirect-on-Write tehnolo\u0123iju.<\/li>\n<li>L\u012bdz 1 PB noder\u012bg\u0101 apjoma ar replik\u0101cijas faktoru 3 un ne\u0146emot v\u0113r\u0101 deduplik\u0101ciju. Replik\u0101cijas faktors 2 netiek \u0146emts v\u0113r\u0101, jo tas nav nopietns p\u0101rdo\u0161anas variants.<\/li>\n<\/ul>\n<p>\nV\u0113l viens liels ieguvums \u2014 vad\u012bbas un izvieto\u0161anas vienk\u0101r\u0161\u012bba. Visas UCS serveru konfigur\u0101cijas sare\u017e\u0123\u012bt\u012bbas uz\u0146emas specializ\u0113ta VM, ko sagatavoju\u0161i Cisco in\u017eenieri. <\/p>\n<h3>Test\u0113\u0161anas standarta konfigur\u0101cija:<\/h3>\n<p><\/p>\n<ul>\n<li>2 x Cisco UCS Fabric Interconnect 6248UP k\u0101 vad\u012bbas klasteris un t\u012bkla komponenti (48 porti, kas darbojas 10G Ethernet\/16G FC re\u017e\u012bm\u0101).<\/li>\n<li>\u010cetri Cisco UCS HXAF240 M4 serveri.<\/li>\n<\/ul>\n<p>\nServeru specifik\u0101cijas:<\/p>\n<p><\/p>\n<p>CPU<\/p>\n<p>2 x Intel \u00ae Xeon \u00ae E5-2690 v4<\/p>\n<p>RAM<\/p>\n<p>16 x 32GB DDR4-2400-MHz RDIMM\/PC4-19200\/dual rank\/x4\/1.2v<\/p>\n<p>T\u012bkls<\/p>\n<p>UCSC-MLOM-CSC-02 (VIC 1227). 2 10G Ethernet porti<\/p>\n<p>Glab\u0101tuves HBA<\/p>\n<p>Cisco 12G Modular SAS Pass Through Controller<\/p>\n<p>Glab\u0101tuves diski<\/p>\n<p>1 x SSD Intel S3520 120 GB, 1 x SSD Samsung MZ-IES800D, 10 x SSD Samsung PM863a 960 GB<\/p>\n<p>\n<b class=\"spoiler_title\">Vair\u0101k konfigur\u0101ciju iesp\u0113ju<\/b>Papildus izv\u0113l\u0113tajai aparat\u016brai pa\u0161laik ir pieejamas \u0161\u0101das iesp\u0113jas:<\/p>\n<ul>\n<li>HXAF240c M5.<\/li>\n<li>Viens vai divi CPU no Intel Silver 4110 l\u012bdz Intel Platinum I8260Y. Pieejams otrais paaudzes.<\/li>\n<li>24 atmi\u0146as slots, modulis no 16 GB RDIMM 2600 l\u012bdz 128 GB LRDIMM 2933.<\/li>\n<li>No 6 l\u012bdz 23 diskiem datiem, viens ke\u0161atmi\u0146as disks, viens sist\u0113mas un viens starta disks.<\/li>\n<\/ul>\n<p>\n<b>Jauda diski<\/b><\/p>\n<ul>\n<li>HX-SD960G61X-EV 960 GB 2.5 collu Enterprise Value 6G SATA SSD (1X iztur\u012bba) SAS 960 GB.<\/li>\n<li>HX-SD38T61X-EV 3.8 TB 2.5 collu Enterprise Value 6G SATA SSD (1X iztur\u012bba) SAS 3.8 TB.<\/li>\n<li>Ke\u0161atmi\u0146as diski<\/li>\n<li>HX-NVMEXPB-I375 375 GB 2.5 collu Intel Optane disks, augsta veiktsp\u0113ja un iztur\u012bba.<\/li>\n<li>HX-NVMEHW-H1600* 1.6 TB 2.5 collu Ent. Perf. NVMe SSD (3X iztur\u012bba) NVMe 1.6 TB.<\/li>\n<li>HX-SD400G12TX-EP 400 GB 2.5 collu Ent. Perf. 12G SAS SSD (10X iztur\u012bba) SAS 400 GB.<\/li>\n<li>HX-SD800GBENK9** 800 GB 2.5 collu Ent. Perf. 12G SAS SED SSD (10X iztur\u012bba) SAS 800 GB.<\/li>\n<li>HX-SD16T123X-EP 1.6 TB 2.5 collu Enterprise performance 12G SAS SSD (3X iztur\u012bba).<\/li>\n<\/ul>\n<p>\n<b>Sist\u0113mas \/ \u017eurn\u0101la diski<\/b><\/p>\n<ul>\n<li>HX-SD240GM1X-EV 240 GB 2.5 collu Enterprise Value 6G SATA SSD (prasa uzlabojumu).<\/li>\n<\/ul>\n<p>\n<b>Starta diski<\/b><\/p>\n<ul>\n<li>HX-M2-240GB 240 GB SATA M.2 SSD SATA 240 GB.<\/li>\n<\/ul>\n<p>T\u012bkla savienojums caur 40G, 25G vai 10G Ethernet portiem. <\/p>\n<p>K\u0101 FI var b\u016bt HX-FI-6332 (40G), HX-FI-6332-16UP (40G), HX-FI-6454 (40G\/100G).<\/p>\n<h3>Pats tests<\/h3>\n<p>\nDisku apak\u0161sist\u0113mas test\u0113\u0161anai es izmantoju HCIBench 2.2.1. Tas ir bezmaksas r\u012bks, kas \u013cauj autom\u0101tiski izveidot slodzi no vair\u0101k\u0101m virtu\u0101laj\u0101m ma\u0161\u012bn\u0101m. Pa\u0161a slodze tiek \u0123ener\u0113ta ar parasto fio. <\/p>\n<p>M\u016bsu klasteris sast\u0101v no \u010detriem mezgliem, replik\u0101cijas faktors 3, visi diski ir Flash.<\/p>\n<p>Test\u0113\u0161anai es izveidoju \u010detrus datu kr\u0101tuves un asto\u0146as virtu\u0101l\u0101s ma\u0161\u012bnas. Ierakstu testiem tiek pie\u0146emts variants, kad ke\u0161atmi\u0146as disks nenok\u013c\u016bst pilns.<\/p>\n<p>Testa rezult\u0101ti ir \u0161\u0101di:<\/p>\n<p>100 % Las\u012bt 100 % Nejau\u0161a<\/p>\n<p>0 % Las\u012bt 100% Nejau\u0161a<\/p>\n<p>Bloks\/izsist\u0101s dzi\u013cums<\/p>\n<p>128<\/p>\n<p>256<\/p>\n<p>512<\/p>\n<p>1024<\/p>\n<p>2048<\/p>\n<p>128<\/p>\n<p>256<\/p>\n<p>512<\/p>\n<p>1024<\/p>\n<p>2048<\/p>\n<p>4K<\/p>\n<p>0,59 ms 213804 IOPS<\/p>\n<p>0,84 ms 303540 IOPS<\/p>\n<p>1,36 ms 374348 IOPS<\/p>\n<p>2,47 ms 414116 IOPS<\/p>\n<p><b>4,86 ms 420180 IOPS<\/b><\/p>\n<p>2,22 ms 57408 IOPS<\/p>\n<p>3,09 ms 82744 IOPS<\/p>\n<p>5,02 ms 101824 IOPS<\/p>\n<p>8,75 ms 116912 IOPS<\/p>\n<p><b>17,2 ms 118592 IOPS<\/b><\/p>\n<p>8K<\/p>\n<p>0,67 ms 188416 IOPS<\/p>\n<p>0,93 ms 273280 IOPS<\/p>\n<p>1,7 ms 299932 IOPS<\/p>\n<p>2,72 ms 376484 IOPS<\/p>\n<p><b>5,47 ms 373176 IOPS<\/b><\/p>\n<p>3,1 ms 41148 IOPS<\/p>\n<p>4,7 ms 54396 IOPS<\/p>\n<p>7,09 ms 72192 IOPS<\/p>\n<p><b>12,77 ms 80132 IOPS<\/b><\/p>\n<p>16K<\/p>\n<p>0,77 ms 164116 IOPS<\/p>\n<p>1,12 ms 228328 IOPS<\/p>\n<p>1,9 ms 268140 IOPS<\/p>\n<p><b>3,96 ms 258480 IOPS<\/b><\/p>\n<p>3,8 ms 33640 IOPS<\/p>\n<p>6,97 ms 36696 IOPS<\/p>\n<p><b>11,35 ms 45060 IOPS<\/b><\/p>\n<p>32K<\/p>\n<p>1,07 ms 119292 IOPS<\/p>\n<p>1,79 ms 142888 IOPS<\/p>\n<p><b>3,56 ms 143760 IOPS<\/b><\/p>\n<p>7,17 ms 17810 IOPS<\/p>\n<p><b>11,96 ms 21396 IOPS<\/b><\/p>\n<p>64K<\/p>\n<p>1,84 ms 69440 IOPS<\/p>\n<p>3,6 ms 71008 IOPS<\/p>\n<p><b>7,26 ms 70404 IOPS<\/b><\/p>\n<p><b>11,37 ms 11248 IOPS<\/b><\/p>\n<p><i>Bold\u0101 izceltie skait\u013ci nor\u0101da uz v\u0113rt\u012bb\u0101m, p\u0113c kur\u0101m veiktsp\u0113ja vairs nepalielin\u0101s, da\u017ek\u0101rt pat var redz\u0113t degrad\u0101ciju. Tas saist\u012bts ar to, ka non\u0101kam l\u012bdz t\u012bkla\/kontroliera\/diska veiktsp\u0113jai.<\/i><\/p>\n<ul>\n<li>Secin\u0101jums lasot 4432 MB\/s.<\/li>\n<li>Secin\u0101jums rakstot 804 MB\/s.<\/li>\n<li>Ja viens kontrolieris neizdodas (k\u0101 kontroliera vai viesdatora atteice), veiktsp\u0113ja samazin\u0101s l\u012bdz pusei.<\/li>\n<li>Ja uzglab\u0101\u0161anas disks neizdodas \u2014 veiktsp\u0113ja samazin\u0101s par 1\/3. Disku p\u0101rb\u016bve aiz\u0146em 5% resursu katram kontrolierim.<\/li>\n<\/ul>\n<p>\nNeliel\u0101 blok\u0101 m\u0113s non\u0101kam pie kontroliera veiktsp\u0113jas (virtu\u0101l\u0101 ma\u0161\u012bna), t\u0101 CPU ir noslogots par 100%, palielinot bloku, m\u0113s sasniedzam p\u0101rs\u016bt\u012b\u0161anas jaudas pielaidumu. 10 Gbit\/s nav pietiekami, lai atkl\u0101tu AllFlash sist\u0113mas potenci\u0101lu. Diem\u017e\u0113l 40 Gbit\/s p\u0101rbaude nav iesp\u0113jama sniegto demo stenda parametru d\u0113\u013c.<\/p>\n<p>Mani iespaidi no testiem un arhitekt\u016bras izp\u0113tes r\u0101da, ka pateicoties algoritmam, kas izplata datus starp visiem hostiem, m\u0113s ieg\u016bstam skalojamu, paredzamu veiktsp\u0113ju, ta\u010du tas ir ierobe\u017eojums las\u012b\u0161anai, jo no lok\u0101lajiem diskiem var\u0113tu ieg\u016bt vair\u0101k, \u0161eit var\u0113tu pal\u012bdz\u0113t efekt\u012bv\u0101ka t\u012bkls, piem\u0113ram, pieejamie FI uz 40 Gbit\/s.<\/p>\n<p>T\u0101pat viens disks ke\u0161o\u0161anai un deduplication var b\u016bt ierobe\u017eojo\u0161s, faktiski \u0161aj\u0101 stend\u0101 m\u0113s varam rakst\u012bt uz \u010detriem SSD diskiem. B\u016btu lieliski, ja b\u016btu iesp\u0113ja palielin\u0101t ke\u0161ojo\u0161o disku skaitu un redz\u0113t at\u0161\u0137ir\u012bbu.<\/p>\n<h3>Re\u0101la izmanto\u0161ana<\/h3>\n<p>\nApak\u0161centr\u0101lo visu jomu rezerv\u0113\u0161anai var izmantot divus pieejas veidus (nenor\u0101d\u0101m rezerves kopijas izvietojumu att\u0101lin\u0101t\u0101 viet\u0101):<\/p>\n<ol>\n<li>Akt\u012bvs-Pas\u012bvs. Visas lietojumprogrammas tiek izvietotas galvenaj\u0101 datu centr\u0101. Replik\u0101cija ir sinhrona vai asinhrona. Galven\u0101 datu centra sabrukuma gad\u012bjum\u0101 mums j\u0101aktiviz\u0113 rezerv\u0113t\u0101. To var izdar\u012bt manu\u0101li\/skribentiem\/or\u0137estr\u0101cijas lietotn\u0113m. \u0160eit m\u0113s ieg\u016bsim RPO, kas ir sal\u012bdzin\u0101ms ar replik\u0101cijas bie\u017eumu, un RTO ir atkar\u012bgs no administratora reakcijas un prasm\u0113m, k\u0101 ar\u012b no pl\u0101na p\u0101rsl\u0113g\u0161anas izstr\u0101des\/uzlabo\u0161anas kvalit\u0101tes.<\/li>\n<li>Akt\u012bvs-Akt\u012bvs. \u0160aj\u0101 gad\u012bjum\u0101 ir pieejama tikai sinhrona replik\u0101cija, datu centru pieejam\u012bba tiek noteikta p\u0113c kvoruma\/arbitra, kas atrodas stingri tre\u0161aj\u0101 viet\u0101. RPO = 0, bet RTO var sasniegt 0 (ja lietojumprogramma to at\u013cauj) vai ir vien\u0101ds ar noda\u013ca izb\u0113g\u0161anas apstr\u0101des laiku virtualiz\u0101cijas klaster\u012b. Virtualiz\u0101cijas l\u012bmen\u012b tiek izveidots gar\u0161 (Metro) klasteris, kas prasa Akt\u012bvs-Akt\u012bvs datu uzglab\u0101\u0161anas sist\u0113mu.<\/li>\n<\/ol>\n<p>\nParasti m\u0113s redzam pie klientiem jau \u012bstenotu arhitekt\u016bru ar klasisku datu uzglab\u0101\u0161anas sist\u0113mu galvenaj\u0101 datu centr\u0101, t\u0101p\u0113c projekt\u0113jam v\u0113l vienu replik\u0101cijai. K\u0101 jau min\u0113ju, Cisco HyperFlex pied\u0101v\u0101 asimetrisku replik\u0101ciju un gar\u0101 klastera izveidi virtualiz\u0101cij\u0101. Taj\u0101 pa\u0161\u0101 laik\u0101 mums nav nepiecie\u0161ama atsevi\u0161\u0137a vid\u0113jo datu uzglab\u0101\u0161anas sist\u0113mu un augst\u0101kas klases ar d\u0101rg\u0101m replik\u0101cijas un Akt\u012bvs-Akt\u012bvs datu pieejam\u012bbas funkcij\u0101m uz div\u0101m datu uzglab\u0101\u0161anas sist\u0113m\u0101m.<\/p>\n<p><b>Scen\u0101rijs 1:<\/b> Mums ir galvenie un rezerves datu centri, VMware vSphere virtualiz\u0101cijas platforma. Visas ra\u017eo\u0161anas sist\u0113mas atrodas galvenaj\u0101 datu centr\u0101, un virtu\u0101lo ma\u0161\u012bnu replik\u0101cija notiek hipervizora l\u012bmen\u012b, kas \u013caus nezaud\u0113t VM rezerv\u0113taj\u0101 datu centr\u0101. Datu b\u0101zes un speci\u0101l\u0101s lietojumprogrammas tiek replik\u0113tas ar ieb\u016bv\u0113tiem l\u012bdzek\u013ciem, un m\u0113s turam VM iesl\u0113gtas. Galven\u0101 datu centra sabrukuma gad\u012bjum\u0101 aktiviz\u0113jam sist\u0113mas rezerves datu centr\u0101. M\u0113s uzskat\u0101m, ka mums ir apm\u0113ram 100 virtu\u0101lo ma\u0161\u012bnu. Kam\u0113r galvenais datu centrs darbojas, rezerves datu centr\u0101 var iesl\u0113gt test\u0113\u0161anas vid\u0113s un citas sist\u0113mas, kuras var atsl\u0113gt galven\u0101 datu centra p\u0101rsl\u0113g\u0161anas gad\u012bjum\u0101. T\u0101pat ir iesp\u0113jams variants, ka m\u0113s izmantojam divvirzienu replik\u0101ciju. No apr\u012bkojuma viedok\u013ca nekas nemain\u012bsies.<\/p>\n<p>Klasiskaj\u0101 arhitekt\u016br\u0101 m\u0113s katr\u0101 datu centr\u0101 uzst\u0101d\u012bsim hibr\u012bdo uzglab\u0101\u0161anas sist\u0113mu ar piek\u013cuvi, izmantojot FibreChannel, datu pl\u016bsmu, datu atdubl\u0113\u0161anu un kompresiju (bet ne tie\u0161saist\u0113), 8 serverus katr\u0101 viet\u0101, pa 2 FibreChannel un 10G Ethernet sl\u0113gviet\u0101m. Replik\u0101cijai un p\u0101rvaldei klasiskaj\u0101 arhitekt\u016br\u0101 varam izmantot VMware r\u012bkus (Replication + SRM) vai ar\u012b tre\u0161o pu\u0161u r\u012bkus, kas b\u016bs nedaudz l\u0113t\u0101ki un da\u017ereiz \u0113rt\u0101ki.<\/p>\n<p>Z\u012bm\u0113 ir par\u0101d\u012bta sh\u0113ma.<\/p>\n<p><img decoding=\"async\" alt=\"Administrators bez rok\u0101m = hiperkonver\u0123ence?\" src=\"\/wp-content\/uploads\/2019\/10\/e7a1ef66c0ae1a8cbb60d0411007d822.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nJa izmantojam Cisco HyperFlex, tad ieg\u016bstam sekojo\u0161o arhitekt\u016bru:<\/p>\n<p><img decoding=\"async\" alt=\"Administrators bez rok\u0101m = hiperkonver\u0123ence?\" src=\"\/wp-content\/uploads\/2019\/10\/71d58163728f37a163ec914b81dc73ab.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nHyperFlex esmu izmantojis serverus ar lieliem CPU\/RAM resursiem, jo da\u013ca resursu tiks izmantota HyperFlex kontroliera VM, CPU un atmi\u0146as konfigur\u0101cij\u0101 es pat nedaudz p\u0101rbaud\u012bju resursus, lai neizsniegtu priek\u0161roc\u012bbas Cisco un garant\u0113tu resursus p\u0101r\u0113jiem VM. T\u0101tad m\u0113s varam atteikties no FibreChannel sl\u0113gviet\u0101m, un mums nav nepiecie\u0161ami Ethernet porti katram serverim, lok\u0101l\u0101s datu pl\u016bsmas tiek p\u0101rsl\u0113gtas iek\u0161\u0113j\u0101 FI.<\/p>\n<p>Rezult\u0101t\u0101 san\u0101ca sekojo\u0161a konfigur\u0101cija katram datu centram:<\/p>\n<p>Serveri<\/p>\n<p>8 x 1U serveris (384 GB RAM, 2 x Intel Gold 6132, FC HBA)<\/p>\n<p>8 x HX240C-M5L (512 GB RAM, 2 x Intel Gold 6150, 3,2 GB SSD, 10 x 6 TB NL-SAS)<\/p>\n<p>Glab\u0101\u0161anas sist\u0113ma<\/p>\n<p>Hibr\u012bda uzglab\u0101\u0161anas sist\u0113ma ar FC Front-End (20 TB SSD, 130 TB NL-SAS)<\/p>\n<p>&#8212;<\/p>\n<p>LAN<\/p>\n<p>2 x 10G 12 portu Ethernet sl\u0113gvietas<\/p>\n<p>&#8212;<\/p>\n<p>SAN<\/p>\n<p>2 x 32\/16Gb 24 portu FC sl\u0113gvietas<\/p>\n<p>2 x Cisco UCS FI 6332<\/p>\n<p>Licences<\/p>\n<p>VMware Ent Plus<\/p>\n<p><\/p>\n<p>Replik\u0101cija un\/vai VM p\u0101rsl\u0113g\u0161anas or\u0137estr\u0101cija<\/p>\n<p>VMware Ent Plus<\/p>\n<p>Hyperflex esmu neiek\u013c\u0101vis licences replik\u0101ciju programmat\u016brai, jo mums tas ir pieejams k\u0101 standarts.<\/p>\n<p>Klasiskaj\u0101 arhitekt\u016br\u0101 izv\u0113l\u0113jos pieg\u0101d\u0101t\u0101ju, kur\u0161 sevi ir apliecin\u0101jis k\u0101 kvalitat\u012bvu un l\u0113tu ra\u017eot\u0101ju. Abiem variantiem pielietoju standarta atlaidi konkr\u0113tajam risin\u0101jumam, rezult\u0101t\u0101 guvu re\u0101las cenas. <\/p>\n<p>Risin\u0101jums uz Cisco HyperFlex izr\u0101d\u012bj\u0101s par 13% l\u0113t\u0101ks.<\/p>\n<p><b>Scen\u0101rijs 2:<\/b> divu akt\u012bvo datu centru izveide. \u0160aj\u0101 scen\u0101r\u012b projekt\u0113jam izplestu klasteri uz VMware. <\/p>\n<p>Klasisk\u0101 arhitekt\u016bra sast\u0101v no virtualiz\u0101cijas serveriem, SAN (FC protokols) un div\u0101m uzglab\u0101\u0161anas sist\u0113m\u0101m, kas prot nolas\u012bt un rakst\u012bt uz t\u0101, kas ir izple\u0161ams starp t\u0101m. Katr\u0101 uzglab\u0101\u0161anas sist\u0113m\u0101 iepl\u0101noj\u0101m noder\u012bgo kapacit\u0101ti lok\u0101lai izmanto\u0161anai.<\/p>\n<p><img decoding=\"async\" alt=\"Administrators bez rok\u0101m = hiperkonver\u0123ence?\" src=\"\/wp-content\/uploads\/2019\/10\/c3830f5bab128b724d94e727218b21b5.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nHyperFlex m\u0113s vienk\u0101r\u0161i izveidojam izple\u0161amo klasteri ar vien\u0101du nodu skaitu ab\u0101s viet\u0101s. \u0160aj\u0101 gad\u012bjum\u0101 tiek izmantots replik\u0101cijas faktors 2+2.<\/p>\n<p><img decoding=\"async\" alt=\"Administrators bez rok\u0101m = hiperkonver\u0123ence?\" src=\"\/wp-content\/uploads\/2019\/10\/6351c830c3fba60dc4e71a9a4245ec6f.jpg\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n <br \/>\nSan\u0101ca sekojo\u0161a konfigur\u0101cija:<\/p>\n<p>Klasisk\u0101 arhitekt\u016bra<\/p>\n<p>HyperFlex<\/p>\n<p>Serveri<\/p>\n<p>16 x 1U serveris (384 GB RAM, 2 x Intel Gold 6132, FC HBA, 2 x 10G NIC)<\/p>\n<p>16 x HX240C-M5L (512 GB RAM, 2 x Intel Gold 6132, 1,6 TB NVMe, 12 x 3,8 TB SSD, VIC 1387)<\/p>\n<p>Glab\u0101\u0161anas sist\u0113ma<\/p>\n<p>2 x AllFlash uzglab\u0101\u0161anas sist\u0113mas (150 TB SSD)<\/p>\n<p>&#8212;<\/p>\n<p>LAN<\/p>\n<p>4 x 10G 24 portu Ethernet sl\u0113gvietas<\/p>\n<p>&#8212;<\/p>\n<p>SAN<\/p>\n<p>4 x 32\/16Gb 24 portu FC sl\u0113gvietas<\/p>\n<p>4 x Cisco UCS FI 6332<\/p>\n<p>Licences<\/p>\n<p>VMware Ent Plus<\/p>\n<p>VMware Ent Plus<\/p>\n<p>Visos apr\u0113\u0137inos es neesmu \u0146\u0113mis v\u0113r\u0101 t\u012bkla infrastrukt\u016bru, datu centrus u.t.t.: tie b\u016bs vien\u0101di klasiskaj\u0101 arhitekt\u016br\u0101 un risin\u0101jum\u0101 uz HyperFlex.<\/p>\n<p>Attiec\u012bb\u0101 uz izmaks\u0101m HyperFlex izr\u0101d\u012bj\u0101s par 5% d\u0101rg\u0101ks. J\u0101atz\u012bm\u0113, ka attiec\u012bb\u0101 uz CPU\/RAM resursiem man Cisco rezult\u0101ts izn\u0101ca ne l\u012bdzsvarots, jo konfigur\u0101cij\u0101 es izl\u012bdzin\u0101ju atmi\u0146as kontrolieru kan\u0101lus. Cena nedaudz augst\u0101ka, bet ne par k\u0101rtu, kas skaidri nor\u0101da, ka hiper-konvergences risin\u0101jums nav oblig\u0101ti \u201ebag\u0101tnieku rota\u013clieta\u201d, bet var konkur\u0113t ar standarta pieeju datu centru izveidei. Tas var b\u016bt interesanti ar\u012b tiem, kam jau ir Cisco UCS serveri un atbilsto\u0161a infrastrukt\u016bra. <\/p>\n<p>Priek\u0161roc\u012bb\u0101s m\u0113s ieg\u016bstam to, ka nav izmaksu par SAN un STH administr\u0113\u0161anu, tie\u0161saistes kompresiju un deduplik\u0101ciju, vienotu atbalsta ieejas punktu (virtualiz\u0101cija, serveri, tie pa\u0161i \u2013 STH), vietas ekonomiju (bet ne visos scen\u0101rijos), ekspluat\u0101cijas vienk\u0101r\u0161o\u0161anu.<\/p>\n<p>Attiec\u012bb\u0101 uz atbalstu, j\u016bs to sa\u0146emat no viena pieg\u0101d\u0101t\u0101ja \u2014 Cisco. Balstoties uz pieredzi ar Cisco UCS serveriem, man t\u0101 patika, HyperFlex atv\u0113rt man nevajadz\u0113ja, viss str\u0101d\u0101ja. In\u017eenieri rea\u0123\u0113 \u0101tri un var risin\u0101t ne tikai tipiskas probl\u0113mas, bet ar\u012b sare\u017e\u0123\u012btus robe\u017egad\u012bjumus. Da\u017ereiz es vi\u0146iem uzdodu jaut\u0101jumus: \u201eVai t\u0101 var izdar\u012bt, pievienojot to?\u201d vai \u201eEs \u0161eit kaut ko konfigur\u0113ju un tas nev\u0113las darboties. Pal\u012bdziet!\u201d \u2014 vi\u0146i tur paciet\u012bgi atrad\u012bs nepiecie\u0161amo rokasgr\u0101matu un nor\u0101d\u012bs pareizas darb\u012bbas, atbild\u0113t: \u201eM\u0113s risin\u0101m tikai aparat\u016bras probl\u0113mas\u201d vi\u0146i neizdar\u012bs.<\/p>\n<h3>Saites<\/h3>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.cisco.com\/c\/dam\/en\/us\/products\/collateral\/hyperconverged-infrastructure\/hyperflex-hx-series\/hxaf-240c-m5-specsheet.pdf\">Specifik\u0101cijas<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/croc\/blog\/146536\/\">Virtu\u0101lais datu centrs<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/croc\/blog\/342820\/\">Datu centrs galda skap\u012b<\/a><\/noindex><\/li>\n<li>Mana e-pasta adrese \u2014 StGeneralov@croc.ru<\/li>\n<\/ul>\n<p>Avots: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/croc\/blog\/471508\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u042d\u0442\u043e \u043c\u0438\u0444, \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u0440\u0430\u0441\u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0451\u043d\u043d\u044b\u0439 \u0432 \u0441\u0444\u0435\u0440\u0435 \u0441\u0435\u0440\u0432\u0435\u0440\u043d\u043e\u0433\u043e \u0436\u0435\u043b\u0435\u0437\u0430. \u041d\u0430 \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0435 \u0436\u0435 \u0433\u0438\u043f\u0435\u0440\u043a\u043e\u043d\u0432\u0435\u0440\u0433\u0435\u043d\u0442\u043d\u044b\u0435 \u0440\u0435\u0448\u0435\u043d\u0438\u044f (\u043a\u043e\u0433\u0434\u0430 \u0432\u0441\u0451 \u0432 \u043e\u0434\u043d\u043e\u043c) \u043d\u0443\u0436\u043d\u044b \u043c\u043d\u043e\u0433\u043e \u0434\u043b\u044f \u0447\u0435\u0433\u043e. \u0418\u0441\u0442\u043e\u0440\u0438\u0447\u0435\u0441\u043a\u0438 \u0441\u043b\u043e\u0436\u0438\u043b\u043e\u0441\u044c, \u0447\u0442\u043e \u043f\u0435\u0440\u0432\u044b\u0435 \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u044b \u0431\u044b\u043b\u0438 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u0430\u043d\u044b Amazon \u0438 Google \u043f\u043e\u0434 \u0441\u0432\u043e\u0438 \u0441\u0435\u0440\u0432\u0438\u0441\u044b. \u0422\u043e\u0433\u0434\u0430 \u0438\u0434\u0435\u044f \u0431\u044b\u043b\u0430 \u0432 \u0442\u043e\u043c, \u0447\u0442\u043e\u0431\u044b \u0441\u0434\u0435\u043b\u0430\u0442\u044c \u0432\u044b\u0447\u0438\u0441\u043b\u0438\u0442\u0435\u043b\u044c\u043d\u0443\u044e \u0444\u0435\u0440\u043c\u0443 \u0438\u0437 \u043e\u0434\u0438\u043d\u0430\u043a\u043e\u0432\u044b\u0445 \u0443\u0437\u043b\u043e\u0432, \u0443 \u043a\u0430\u0436\u0434\u043e\u0433\u043e \u0438\u0437 \u043a\u043e\u0442\u043e\u0440\u044b\u0445 \u0435\u0441\u0442\u044c \u0441\u043e\u0431\u0441\u0442\u0432\u0435\u043d\u043d\u044b\u0435 \u0434\u0438\u0441\u043a\u0438. \u0412\u0441\u0451 \u044d\u0442\u043e [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":29233,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-38966","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.5 - aioseo.com -->\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\/lv\/blog\/administrirovanie\/admin-bez-ruk-giperkonvergentsiya\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5\" \/>\n\t\t<meta property=\"og:locale\" content=\"lv_LV\" \/>\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\u0434\u043c\u0438\u043d \u0431\u0435\u0437 \u0440\u0443\u043a = \u0433\u0438\u043f\u0435\u0440\u043a\u043e\u043d\u0432\u0435\u0440\u0433\u0435\u043d\u0446\u0438\u044f? | ProHoster\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/admin-bez-ruk-giperkonvergentsiya\" \/>\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:27:03+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:27:03+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\udd47Admins bez rok\u0101m = hiper-konvergence? | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/admin-bez-ruk-giperkonvergentsiya","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"lv_LV","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\u0434\u043c\u0438\u043d \u0431\u0435\u0437 \u0440\u0443\u043a = \u0433\u0438\u043f\u0435\u0440\u043a\u043e\u043d\u0432\u0435\u0440\u0433\u0435\u043d\u0446\u0438\u044f? | ProHoster","og:url":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/admin-bez-ruk-giperkonvergentsiya","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:27:03+00:00","article:modified_time":"2019-10-31T19:27:03+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"38966","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-24 00:12:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 00:59:27","updated":"2026-01-24 00:12:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/38966","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/comments?post=38966"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/posts\/38966\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media\/29233"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/media?parent=38966"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/categories?post=38966"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/lv\/wp-json\/wp\/v2\/tags?post=38966"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}