{"id":96767,"date":"2020-10-14T14:43:02","date_gmt":"2020-10-14T12:43:02","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/hystax-cloud-migration-skachem-po-oblakam"},"modified":"2020-10-14T14:43:02","modified_gmt":"2020-10-14T12:43:02","slug":"hystax-cloud-migration-skachem-po-oblakam","status":"publish","type":"post","link":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/hystax-cloud-migration-skachem-po-oblakam","title":{"rendered":"Hystax Cloud Migration: lecam pa m\u0101ko\u0146iem","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Viena no jaunaj\u0101m sp\u0113l\u0113t\u0101j\u0101m katastrofu atjauno\u0161anas risin\u0101jumu tirg\u016b ir uz\u0146\u0113mums Hystax \u2013 Krievijas startaps, kas dibin\u0101ts 2016. gad\u0101. \u0145emot v\u0113r\u0101, ka katastrofu atjauno\u0161anas t\u0113ma ir \u013coti popul\u0101ra un tirg\u016b ir \u0101rk\u0101rt\u012bgi augsta konkurence, startaps nol\u0113ma koncentr\u0113ties uz migr\u0101ciju starp da\u017e\u0101d\u0101m m\u0101ko\u0146infrastrukt\u016br\u0101m. Produkts, kas \u013cauj organiz\u0113t vienk\u0101r\u0161u un \u0101tru migr\u0101ciju m\u0101ko\u0146os, b\u016btu \u013coti noder\u012bgs ar\u012b uz\u0146\u0113muma \u00abOnlanta\u00bb klientiem\u00a0\u2014\u00a0lietot\u0101jiem. Oncloud.ru<\/a><\/noindex>. T\u0101 es iepazinos ar Hystax un s\u0101ku test\u0113t t\u0101 iesp\u0113jas. Par to, kas no t\u0101 izn\u0101ca, past\u0101st\u012b\u0161u \u0161aj\u0101 rakst\u0101.<\/p>\n

\"Hystax<\/a><\/noindex>
\nHystax galven\u0101 priek\u0161roc\u012bba ir t\u0101 pla\u0161\u0101 funkcionalit\u0101te attiec\u012bb\u0101 uz da\u017e\u0101du virtualiz\u0101cijas platformu, viesoper\u0113t\u0101jsist\u0113mu un m\u0101ko\u0146u pakalpojumu atbalstu, kas \u013cauj p\u0101rvietot j\u016bsu slodzes no jebkuras vietas uz jebkuru vietu.<\/p>\n

Tas \u013cauj izveidot ne tikai DR risin\u0101jumus, lai uzlabotu pakalpojumu notur\u012bbu, bet ar\u012b operat\u012bvi, elast\u012bgi migr\u0113t resursus starp da\u017e\u0101d\u0101m platform\u0101m un hiperskalariem, lai palielin\u0101tu izmaksu efektivit\u0101ti un izv\u0113l\u0113tos vislab\u0101ko risin\u0101jumu konkr\u0113tam pakalpojumam \u0161aj\u0101 br\u012bd\u012b. Papildus platform\u0101m, kas uzskait\u012btas virsraksta att\u0113l\u0101, uz\u0146\u0113mums akt\u012bvi sadarbojas ar\u012b ar Krievu m\u0101ko\u0146u pakalpojumu sniedz\u0113jiem: Yandex.Cloud, KROK \"M\u0101ko\u0146u pakalpojumi\", Mail.ru un daudziem citiem. T\u0101pat ir v\u0113rts piemin\u0113t, ka 2020. gad\u0101 uz\u0146\u0113mumam tika izveidots R&D centrs, kas atrodas Skolkovo.\u00a0<\/p>\n

L\u0113mums par viena risin\u0101juma izv\u0113li daudz\u0101m tirgus sp\u0113l\u0113t\u0101jiem liecina par labu cenu politiku un augstu produkta pielietojam\u012bbu, ko m\u0113s nol\u0113m\u0101m p\u0101rbaud\u012bt praks\u0113.<\/p>\n

T\u0101tad, m\u016bsu test\u0113\u0161anas uzdevums sast\u0101v no migr\u0101cijas no manas test\u0113\u0161anas vides VMware un fiziskaj\u0101m ma\u0161\u012bn\u0101m uz pakalpojumu sniedz\u0113ja vidi, kas ar\u012b tiek p\u0101rvald\u012bta ar VMware. J\u0101, ir daudzi risin\u0101jumi, kas var veikt l\u012bdz\u012bgu migr\u0101ciju, ta\u010du m\u0113s uzskat\u0101m Hystax par univers\u0101lu r\u012bku, un izm\u0113\u0123in\u0101t migr\u0101ciju visos iesp\u0113jamos kombin\u0101cijas \u2014 ir vienk\u0101r\u0161i nere\u0101la uzdevums. Un m\u0101ko\u0146a Oncloud.ru ir balst\u012bts tie\u0161i uz VMware, t\u0101p\u0113c \u0161\u012b platforma k\u0101 m\u0113r\u0137is m\u016bs interes\u0113 vair\u0101k. T\u0101l\u0101k es aprakst\u012b\u0161u pamata darb\u012bbas principu, kas kopum\u0101 nav atkar\u012bgs no platformas, un VMware no jebkuras puses var tikt aizvietota ar citas pieg\u0101d\u0101t\u0101ja platformu.\u00a0<\/p>\n

Pirmaj\u0101 posm\u0101 j\u0101uzst\u0101da Hystax Acura, kas ir sist\u0113mas vad\u012bbas pane\u013ca r\u012bks.<\/p>\n

\"Hystax<\/a><\/noindex>
\nTas tiek uzst\u0101d\u012bts no veidnes. Kaut k\u0101d\u0101 veid\u0101 m\u016bsu gad\u012bjum\u0101 t\u0101 nebija piln\u012bgi pareiza, un viet\u0101, lai uzst\u0101d\u012btu ieteiktos 8CPU, 16Gb, t\u0101 tika uzst\u0101d\u012bta ar divreiz maz\u0101k resursiem. T\u0101p\u0113c ir j\u0101atceras tos main\u012bt, cit\u0101di ar konteineriem infrastrukt\u016bra iek\u0161 VM, uz kuras viss balst\u012bts, vienk\u0101r\u0161i nes\u0101ksies un port\u0101ls b\u016bs nepieejams. D Uzst\u0101d\u012b\u0161anas pras\u012bbas<\/a><\/noindex> detaliz\u0113ti aprakst\u012btas nepiecie\u0161am\u0101s resursu un visu sist\u0113mas komponentu porti.\u00a0<\/p>\n

Ar IP adreses iestat\u012b\u0161anu caur veidni ar\u012b rad\u0101s gr\u016bt\u012bbas, t\u0101p\u0113c to main\u012bj\u0101m no konsoles. P\u0113c tam var p\u0101riet uz administr\u0101cijas t\u012bmek\u013ca saskarni un aizpild\u012bt s\u0101kotn\u0113jo konfigur\u0101cijas vedni.\u00a0<\/p>\n

\"Hystax<\/a><\/noindex>
\n\"Hystax<\/a><\/noindex>
\nEndpoint \u2013 IP vai FQDN m\u016bsu vCenter.\u00a0
\nLietot\u0101jv\u0101rds un parole \u2013 \u0161eit viss skaidrs.\u00a0
\nTarget ESXi hostname \u2013 viens no m\u016bsu klastera hostiem, uz kuru notiks replik\u0101cija.\u00a0
\nTarget datastore \u2013 viens no m\u016bsu klastera datastoriem, uz kuru notiks replik\u0101cija.
\nHystax Acura kontrolpane\u013ca publiskais IP \u2013 adrese, caur kuru b\u016bs pieejams vad\u012bbas panelis.<\/p>\n

Nepiecie\u0161ams neliels preciz\u0113jums par hostu un datastoru. Proti, ka Hystax replik\u0101cija darbojas uz hosta un datastora l\u012bme\u0146a. T\u0101l\u0101k es past\u0101st\u012b\u0161u, k\u0101 tenants var nomain\u012bt hostu un datastoru, bet probl\u0113ma ir cita. Hystax neatbalsta darbu ar resursu grup\u0101m, tas ir, replik\u0101cija vienm\u0113r notiks klastera sakn\u0113 (rakstot \u0161o materi\u0101lu, Hystax komanda izlaida atjaunin\u0101jumu, kur\u0101 \u0101tri ieviesa manu funkciju piepras\u012bjumu attiec\u012bb\u0101 uz resursu grupu atbalstu). Tika ar\u012b neatbalst\u012bts vCloud Director, t\u0101tad, ja, k\u0101 man\u0101 gad\u012bjum\u0101, tenantam nav administratora ties\u012bbu visam klasterim, bet tikai uz konkr\u0113tu resursu grupu, un m\u0113s dev\u0101m piek\u013cuvi Hystax, vi\u0146\u0161 var\u0113s patst\u0101v\u012bgi replik\u0113t un palaist \u0161os VM, bet vi\u0146\u0161 tos nesp\u0113s redz\u0113t VMware infrastrukt\u016br\u0101, kurai vi\u0146am ir piek\u013cuve un, attiec\u012bgi, t\u0101l\u0101k p\u0101rvald\u012bt virtu\u0101l\u0101s ma\u0161\u012bnas. Ir nepiecie\u0161ams, lai klastera administrators p\u0101rvietotu VM uz pareizo resursu grupu vai import\u0113tu to vCloud Director.<\/p>\n

K\u0101p\u0113c es uzsveru \u0161os punktus? Jo, cik es saprotu produkta koncepciju, klientam vajadz\u0113tu sp\u0113t patst\u0101v\u012bgi veikt jebkuru migr\u0101ciju vai DR, izmantojot Acura paneli. Bet, kam\u0113r VMware atbalsts nedaudz atpaliek no t\u0101 pa\u0161a OpenStack, kur \u0161\u0101das meh\u0101nismes jau ir ieviesti.\u00a0<\/p>\n

Bet atgriez\u012bsimies pie izvieto\u0161anas. Pirmais solis, p\u0113c s\u0101kotn\u0113j\u0101s paneles iestat\u012b\u0161anas, mums ir j\u0101izveido pirmais tenants m\u016bsu sist\u0113m\u0101.<\/p>\n

\"Hystax<\/a><\/noindex>
\nVisi \u0161ie lauki ir skaidri, es izst\u0101st\u012b\u0161u tikai par lauku Cloud. Mums jau ir \u00abnoklus\u0113juma\u00bb m\u0101ko\u0146i, kurus m\u0113s izveidoj\u0101m, kad s\u0101kotn\u0113ji konfigur\u0113j\u0101m. Bet, ja m\u0113s v\u0113lamies, lai katrs tenants b\u016btu sav\u0101 datu kr\u0101tuv\u0113 un resursu grup\u0101, m\u0113s to varam \u012bstenot, izveidojot atsevi\u0161\u0137us m\u0101ko\u0146us katram no m\u016bsu klientiem.<\/p>\n

\"Hystax<\/a><\/noindex>
\nJaun\u0101 m\u0101ko\u0146a pievieno\u0161anas form\u0101 m\u0113s nor\u0101d\u0101m tos pa\u0161us parametrus, k\u0101 s\u0101kotn\u0113j\u0101 konfigur\u0113\u0161an\u0101 (m\u0113s varam pat izmantot to pa\u0161u hostu), nor\u0101dam konkr\u0113tajam klientam nepiecie\u0161amo datu kr\u0101tuvi, un tagad papildu parametros m\u0113s varam individu\u0101li nor\u0101d\u012bt nepiecie\u0161amo resursu grupu {\u00abresource_pool\u00bb: \u00abYOUR_POOL_NAME\u00bb}.\u00a0<\/p>\n

K\u0101 j\u016bs var\u0113j\u0101t paman\u012bt, tenant izveido\u0161anas form\u0101 nav nek\u0101 par resursu pie\u0161\u0137ir\u0161anu vai kvot\u0101m \u2013 sist\u0113m\u0101 nav nek\u0101 t\u0101da. Ierobe\u017eot tenant skaitu l\u012bdzstr\u0101d\u0101jo\u0161o replik\u0101ciju skait\u0101, replik\u0101cijas ma\u0161\u012bnu skait\u0101 vai citos parametrus nav iesp\u0113jams. T\u0101tad, m\u0113s esam izveidoju\u0161i pirmo tenant. Tagad ir j\u0101veic ne glu\u017ei lo\u0123iska, bet oblig\u0101ta darb\u012bba \u2013 instal\u0113t Cloud a\u0123entu. T\u0101 nav lo\u0123iska, jo a\u0123ents tiek lejupiel\u0101d\u0113ts konkr\u0113t\u0101 klienta lap\u0101.<\/p>\n

\"Hystax<\/a><\/noindex>
\nTas nav piesaist\u012bts izveidotajam tenantam, un caur to darbosies visi m\u016bsu pas\u016bt\u012bt\u0101ji (vai caur vair\u0101kiem, ja m\u0113s tos izvietosim). Viens a\u0123ents atbalsta 10 vienlaic\u012bgas sesijas. Viena sesija tiek uzskat\u012bta par vienu ma\u0161\u012bnu. Nav svar\u012bgi, cik daudz diskus tai ir. Pa\u0161laik Acura iek\u0161\u0113jam meh\u0101nismam a\u0123entu m\u0113rogo\u0161anai VMware nav pieejams. Ir ar\u012b v\u0113l viens nepat\u012bkams moments \u2013 m\u0113s nevaram no Acura pane\u013ca apskat\u012bt \u0161\u012b a\u0123enta \u201cizmanto\u0161anu\u201d, lai spriestu, vai mums vajag izvietot v\u0113l vai pa\u0161reiz\u0113j\u0101 instal\u0101cija ir pietiekama. Rezult\u0101t\u0101 stends izskat\u0101s \u0161\u0101di:<\/p>\n

\"Hystax<\/a><\/noindex>
\nN\u0101kamais posms, lai piek\u013c\u016btu m\u016bsu klienta port\u0101lam, ir j\u0101izveido lietot\u0101ja konts (ieguldot ar\u012b lomu, kas tiks piem\u0113rota \u0161im lietot\u0101jam).<\/p>\n

\"Hystax<\/a><\/noindex>
\n\"Hystax<\/a><\/noindex>
\nTagad m\u016bsu klients var patst\u0101v\u012bgi izmantot port\u0101lu. Viss, kas vi\u0146am j\u0101dara, ir lejupiel\u0101d\u0113t a\u0123entus no port\u0101la un uzst\u0101d\u012bt tos sav\u0101 pus\u0113. Past\u0101v tr\u012bs veidu a\u0123enti: Linux, Windows un VMware.<\/p>\n

\"Hystax<\/a><\/noindex>
\nPirmie divi tiek uzst\u0101d\u012bti uz fiziskaj\u0101m ma\u0161\u012bn\u0101m vai virtu\u0101laj\u0101m ma\u0161\u012bn\u0101m uz jebkura hipervizora, iz\u0146emot VMware. \u0160eit nav nepiecie\u0161ams nekas papildu konfigur\u0113t, a\u0123ents tiek lejupiel\u0101d\u0113ts un jau zina, uz kuru adresi nepiecie\u0161ams piek\u013c\u016bt, un burtiski p\u0113c min\u016btes ma\u0161\u012bnu var\u0113s redz\u0113t Acura panel\u012b. Ar VMware a\u0123entu situ\u0101cija ir nedaudz sare\u017e\u0123\u012bt\u0101ka. Probl\u0113ma ir t\u0101da, ka a\u0123ents VMware tiek lejupiel\u0101d\u0113ts no port\u0101la jau sagatavots un ar nepiecie\u0161amo konfigur\u0101ciju. Bet, lai a\u0123ents VMware var\u0113tu piek\u013c\u016bt m\u016bsu Acura port\u0101lam, tam j\u0101zina ar\u012b par to virtualiz\u0101cijas sist\u0113mu, kur\u0101 tas tiks izvietots.<\/p>\n

\"Hystax<\/a><\/noindex>
\nFaktiski \u0161ie dati tiks pras\u012bti, kad pirmo reizi lejupiel\u0101d\u0113sim VMware a\u0123entu. Probl\u0113ma ir t\u0101da, ka m\u016bsu dro\u0161\u012bbas laikmet\u0101 t\u0101lu ne visi v\u0113l\u0113sies nor\u0101d\u012bt savu administratora paroli sve\u0161\u0101 port\u0101l\u0101, kas ir piln\u012bgi saprotams. Iek\u0161pus\u0113, p\u0113c izvieto\u0161anas, a\u0123entu vairs nevar\u0113s konfigur\u0113t (var\u0113s tikai main\u012bt t\u0101 t\u012bkla iestat\u012bjumus). \u0160eit es paredzu gr\u016bt\u012bbas ar \u012bpa\u0161i piesardz\u012bgiem klientiem.\u00a0<\/p>\n

T\u0101tad, p\u0113c a\u0123entu uzst\u0101d\u012b\u0161anas m\u0113s varam atgriezties Acura panel\u012b un redz\u0113t visas m\u016bsu ma\u0161\u012bnas.<\/p>\n

\"Hystax<\/a><\/noindex>
\nKop\u0161 esmu str\u0101d\u0101jis ar sist\u0113mu jau k\u0101du laiku, man ir ma\u0161\u012bnas da\u017e\u0101dos st\u0101vok\u013cos. Visas t\u0101s atrodas grup\u0101 Default, ta\u010du ir iesp\u0113ja izveidot atsevi\u0161\u0137as grupas un p\u0101rvietot taj\u0101s ma\u0161\u012bnas p\u0113c vajadz\u012bbas. Tas neietekm\u0113 neko \u2013 tas ir tikai lo\u0123isks datu att\u0113lojums un to grup\u0113\u0161ana \u0113rt\u0101kai darb\u012bbai. Pirmais un vissvar\u012bg\u0101kais, kas mums j\u0101dara p\u0113c tam, ir uzs\u0101kt migr\u0101cijas procesu. M\u0113s to varam izdar\u012bt gan piespiedu k\u0101rt\u0101 manu\u0101li, gan iestat\u012bt grafiku, tostarp ar\u012b masveida vis\u0101m ma\u0161\u012bn\u0101m uzreiz.<\/p>\n

\"Hystax<\/a><\/noindex>
\nAtg\u0101dinu, ka Hystax tika pozicion\u0113ts k\u0101 produkts migr\u0101cijai. T\u0101d\u0113\u013c nav nek\u0101 p\u0101rsteidzo\u0161a, ka, lai uzs\u0101ktu m\u016bsu replik\u0113t\u0101s ma\u0161\u012bnas, mums ir j\u0101izveido DR pl\u0101ns. Pl\u0101nu var sast\u0101d\u012bt ma\u0161\u012bn\u0101m, kuras jau atrodas st\u0101vokl\u012b Synced. Var \u0123ener\u0113t gan vienai konkr\u0113tai VM, gan vis\u0101m ma\u0161\u012bn\u0101m uzreiz.<\/p>\n

\"Hystax<\/a><\/noindex>
\nParametru kopums DR pl\u0101na \u0123ener\u0113\u0161anai b\u016bs at\u0161\u0137ir\u012bgs atkar\u012bb\u0101 no infrastrukt\u016bras, uz kuru migr\u0113siet. VMware vid\u0113 ir pieejams minim\u0101lais parametru kopums. T\u0101pat netiek atbalst\u012bta Re-IP ma\u0161\u012bn\u0101m. \u0160aj\u0101 pl\u0101n\u0101 m\u016bs interes\u0113 \u0161\u0101di aspekti: VM aprakst\u0101 parametrs \u201esubnet\u201d: \u201eVMNetwork\u201d, kur m\u0113s piesaist\u0101m VM konkr\u0113tai t\u012bklam klaster\u012b. Rank \u2013 ir svar\u012bgs, migr\u0113jot vair\u0101kas VM, nosaka to iedarbo\u0161an\u0101s sec\u012bbu. Flavor \u2013 apraksta VM konfigur\u0101ciju, \u0161aj\u0101 gad\u012bjum\u0101 \u2013 1CPU, 2GB RAM. Subnetu sekcij\u0101 m\u0113s nosak\u0101m, ka \u201esubnet\u201d: \u201eVMNetwork\u201d tiek asoci\u0113ts ar t\u012bklu \u201eVM Network\u201d VMware.\u00a0<\/p>\n

Izveidojot DR pl\u0101nu, nav iesp\u0113jas \u201esad repartir\u201d diskus pa da\u017e\u0101diem datastoriem. Tie atrad\u012bsies taj\u0101 pa\u0161\u0101 datastor\u0101, kas tika noteikts \u0161im klienta m\u0101ko\u0146a pakalpojumam, un, ja jums ir diski at\u0161\u0137ir\u012bg\u0101 klas\u0113, tas var rad\u012bt da\u017eas gr\u016bt\u012bbas ma\u0161\u012bnas palai\u0161an\u0101, bet p\u0113c palai\u0161anas un VM \u201eatvieno\u0161an\u0101s\u201d no Hystax, b\u016bs nepiecie\u0161ama ar\u012b atsevi\u0161\u0137a disku migr\u0101cija uz vajadz\u012bgajiem datastoriem. T\u0101l\u0101k mums atliks tikai uzs\u0101kt m\u016bsu DR pl\u0101nu un gaid\u012bt, kad tiks palaistas m\u016bsu ma\u0161\u012bnas. P2V\/V2V konversijas process ar\u012b aiz\u0146em laiku. Man\u0101 liel\u0101kaj\u0101 test\u0113\u0161anas ma\u0161\u012bn\u0101 ar 100GB un trim diskiem tas aiz\u0146\u0113ma maksimums 10 min\u016btes.<\/p>\n

\"Hystax<\/a><\/noindex>
\nP\u0113c tam ir j\u0101izp\u0113ta palaist\u0101 VM, t\u0101s pakalpojumi, datu sader\u012bba un j\u0101veic citas p\u0101rbaudes.\u00a0<\/p>\n

T\u0101l\u0101k mums ir divi ce\u013ci:\u00a0<\/p>\n

    \n
  1. Dz\u0113st \u2013 izdz\u0113st palaistu DR pl\u0101nu. \u0160\u012b darb\u012bba vienk\u0101r\u0161i izsl\u0113gs palaisto VM. Replik\u0101cijas dati nekur nepazud\u012bs.\u00a0<\/li>\n
  2. Atsiet \u2013 atvienot replik\u0101ciju ma\u0161\u012bnu no Acura, t.i., b\u016bt\u012bb\u0101 pabeigt migr\u0101cijas procesu.\u00a0<\/li>\n<\/ol>\n

    \nRisin\u0101juma priek\u0161roc\u012bbas:<\/strong>\u00a0<\/p>\n