{"id":82495,"date":"2020-05-22T01:42:27","date_gmt":"2020-05-21T23:42:27","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/ovirt-za-2-chasa-chast-1-otkrytaya-otkazoustojchivaya-platforma-virtualizaczii"},"modified":"2020-05-22T01:42:27","modified_gmt":"2020-05-21T23:42:27","slug":"ovirt-za-2-chasa-chast-1-otkrytaya-otkazoustojchivaya-platforma-virtualizaczii","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/ovirt-za-2-chasa-chast-1-otkrytaya-otkazoustojchivaya-platforma-virtualizaczii","title":{"rendered":"oVirt za 2 hodiny. \u010cas\u0165 1. Otvoren\u00e1 platforma pre odoln\u00fa virtualiz\u00e1ciu","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\u00davod<\/h2>\n

\nOpen source projekt oVirt<\/a><\/noindex> \u2014 vo\u013en\u00e1 platforma virtualiz\u00e1cie podnikovej \u00farovne. Prehliadan\u00edm habr som zistil, \u017ee oVirt<\/a><\/noindex> nie je tu tak \u0161iroko osvetlen\u00fd, ako si zasl\u00fa\u017ei.
\noVirt je vlastne upstream pre komer\u010dn\u00fd syst\u00e9m Red Hat Virtualization (RHV, predt\u00fdm RHEV), ktor\u00fd rastie pod kr\u00eddlami Red Hat. Aby nedo\u0161lo k zm\u00e4tku, je to nie<\/b> rovnak\u00e9 ako CentOS vs RHEL, model je bli\u017e\u0161\u00ed k Fedora vs RHEL.
\nPod kapotou \u2014 KVM<\/a><\/noindex>, na spr\u00e1vu sa pou\u017e\u00edva webov\u00e9 rozhranie. Z\u00e1kladom je OS RHEL\/CentOS 7.
\noVirt m\u00f4\u017ee by\u0165 pou\u017eit\u00fd na \u201etradi\u010dn\u00fa\u201c serverov\u00fa aj desktopov\u00fa virtualiz\u00e1ciu (VDI), na rozdiel od rie\u0161enia VMware, obe syst\u00e9my m\u00f4\u017eu spolu koexistova\u0165 v jednom komplexe.
\nProjekt je dobre dokumentovan\u00fd<\/a><\/noindex>, u\u017e dlh\u0161\u00ed \u010das dosiahol zrelos\u0165 pre produkt\u00edvne nasadenie a je pripraven\u00fd na vysok\u00e9 za\u0165a\u017eenia.
\nTento \u010dl\u00e1nok je prv\u00fd v cykle o tom, ako postavi\u0165 funguj\u00faci syst\u00e9m odoln\u00fd vo\u010di zlyhaniu. Prejden\u00edm cez ne, za kr\u00e1tky \u010das (pribli\u017ene 2 hodiny) z\u00edskame \u00faplne funk\u010dn\u00fd syst\u00e9m, aj ke\u010f nieko\u013eko ot\u00e1zok samozrejme nebude mo\u017en\u00e9 osvieti\u0165, pok\u00fasim sa ich rozobra\u0165 v nasleduj\u00facich \u010dl\u00e1nkoch.<\/a><\/noindex>
\nPou\u017e\u00edvame ho u\u017e nieko\u013eko rokov, za\u010d\u00ednali sme s verziou 4.1. Na\u0161a priemyseln\u00e1 s\u00fastava teraz be\u017e\u00ed na v\u00fdpo\u010dtov\u00fdch jednotk\u00e1ch HPE Synergy 480 a ProLiant BL460c 10. gener\u00e1cie s procesorom Xeon Gold.
\nV \u010dase p\u00edsania platn\u00e1 verzia 4.3. <\/p>\n

\u010cl\u00e1nky<\/h2>\n

<\/p>\n

    \n
  1. \u00davod (sme tu)<\/li>\n
  2. In\u0161tal\u00e1cia mana\u017e\u00e9ra (ovirt-engine) a hyperv\u00edzorov (hosts)<\/a><\/noindex><\/li>\n
  3. \u010eal\u0161ie nastavenia<\/a><\/noindex><\/li>\n<\/ol>\n

    Funk\u010dn\u00e9 vlastnosti<\/h2>\n

    \nV oVirt existuj\u00fa 2 hlavn\u00e9 entity: ovirt-engine a ovirt-host(s). Pre t\u00fdch, ktor\u00ed s\u00fa dobre obozn\u00e1men\u00ed s produktom VMware, oVirt ako platforma je v podstate vSphere, ovirt-engine \u2013 riadiaca vrstva \u2013 vykon\u00e1va rovnak\u00e9 funkcie ako vCenter, a ovirt-host \u2013 hyperv\u00edzor ako ESX(i). Ke\u010f\u017ee vSphere je ve\u013emi popul\u00e1rne rie\u0161enie, ob\u010das budem porovn\u00e1va\u0165 s n\u00edm.
    \n\"oVirt
    \nObr\u00e1zok 1 \u2013 ovl\u00e1dac\u00ed panel oVirt.<\/p>\n

    Ako hos\u0165ovsk\u00e9 stroje s\u00fa podporovan\u00e9 v\u00e4\u010d\u0161ina distrib\u00faci\u00ed Linuxu a verzi\u00ed Windows. Pre hos\u0165ovsk\u00e9 stroje s\u00fa k dispoz\u00edcii agenti a optimalizovan\u00e9 virtu\u00e1lne zariadenia a ovl\u00e1da\u010de virtio, predov\u0161etk\u00fdm diskov\u00fd ovl\u00e1da\u010d a sie\u0165ov\u00e9 rozhranie.
    \nNa implement\u00e1ciu rie\u0161enia odoln\u00e9ho vo\u010di zlyhaniu a v\u0161etk\u00fdch zauj\u00edmav\u00fdch funkci\u00ed bude potrebn\u00e9 zdie\u013ean\u00e9 \u00falo\u017eisko. Podporuj\u00fa sa ako blokov\u00e9 FC, FCoE, iSCSI, tak aj s\u00faborov\u00e9 NFS \u00falo\u017eisk\u00e1 a in\u00e9. Na implement\u00e1ciu rie\u0161enia odoln\u00e9ho vo\u010di zlyhaniu mus\u00ed by\u0165 \u00falo\u017en\u00fd syst\u00e9m tie\u017e odoln\u00fd vo\u010di zlyhaniu (minim\u00e1lne 2 kontrol\u00e9ry, multipathing).
    \nPou\u017e\u00edvanie lok\u00e1lnych \u00falo\u017e\u00edsk je mo\u017en\u00e9, av\u0161ak predvolen\u00fd klaster akceptuje len zdie\u013ean\u00e9 \u00falo\u017eisk\u00e1. Lok\u00e1lne \u00falo\u017eisk\u00e1 robia syst\u00e9m rozt\u0155hnut\u00fdm s\u00faborom hyperv\u00edzorov a dokonca aj pri existencii zdie\u013ean\u00e9ho \u00falo\u017eiska nie je mo\u017en\u00e9 zlo\u017ei\u0165 klaster. Najlep\u0161ou cestou s\u00fa bezdiskov\u00e9 stroje s boot from SAN alebo disky minim\u00e1lnej kapacity. Je pravdepodobn\u00e9, \u017ee prostredn\u00edctvom vdsm hook je mo\u017en\u00fd variant zlo\u017eenia z lok\u00e1lnych diskov Software Defined Storage (napr. Ceph) a ich prezent\u00e1cie VM, av\u0161ak nikdy som to seri\u00f3zne neuva\u017eoval.<\/p>\n

    Architekt\u00fara<\/h4>\n

    \n\"oVirt
    \nObr. 2 \u2014 architekt\u00fara oVirt.
    \nPodrobnej\u0161ie s architekt\u00farou sa m\u00f4\u017eete obozn\u00e1mi\u0165 v     dokumen\u00e1cie<\/a><\/noindex> v\u00fdvoj\u00e1rskej dokument\u00e1cii.<\/p>\n

    \"oVirt
    \nObr. 3 \u2014 objekty oVirt.<\/p>\n

    Horn\u00fd prvok v hierarchii \u2014 D\u00e1tov\u00e9 centrum<\/b>. Ur\u010duje, \u010di s\u00fa pou\u017eit\u00e9 zdie\u013ean\u00e9 alebo lok\u00e1lne \u00falo\u017eisk\u00e1, ako aj funkcie, ktor\u00e9 sa maj\u00fa pou\u017e\u00edva\u0165 (kompatibilita, od 4.1 do 4.3). M\u00f4\u017ee ich by\u0165 jeden alebo viac. Pre mnoh\u00e9 varianty je mo\u017en\u00e9 pou\u017ei\u0165 predvolen\u00e9 Data Center \u2014 Default.
    \nData Center pozost\u00e1va z jedn\u00e9ho alebo viacer\u00fdch Clusterov.<\/b>Klaster ur\u010duje typ procesora, migra\u010dn\u00e9 politiky a in\u00e9. Pre men\u0161ie in\u0161tal\u00e1cie je mo\u017en\u00e9 obmedzi\u0165 sa na klaster Default.
    \nKlaster sa obsiahne z Host<\/b>hosts, performing the core work \u2014 they carry the virtual machines and are connected to storage. The cluster is expected to have 2 or more hosts. Although it is technically possible to create a cluster with 1 host, it has no practical benefit.<\/p>\n

    V oVirt je podporovan\u00fdch mnoho funkci\u00ed, vr\u00e1tane \u017eivej migr\u00e1cie virtu\u00e1lnych strojov medzi hyperv\u00edzormi (live migration) a \u00falo\u017eiskami (storage migration), desktopovej virtualiz\u00e1cie (virtual desktop infrastructure) s poolmi VM, stateful a stateless VM, podpory NVidia Grid vGPU, importu z vSphere, KVM, a je tu aj siln\u00e9 API<\/a><\/noindex> a mnoh\u00e9 \u010fal\u0161ie. V\u0161etky tieto funkcie s\u00fa dostupn\u00e9 bez licen\u010dn\u00fdch poplatkov, a ak potrebujete podporu, m\u00f4\u017eete ju zak\u00fapi\u0165 od spolo\u010dnosti Red Hat prostredn\u00edctvom region\u00e1lnych partnerov.<\/p>\n

    O cen\u00e1ch na RHV<\/h4>\n

    \nCena je n\u00edzka v porovnan\u00ed s VMware, kupuje sa iba podpora \u2014 bez po\u017eiadavky na zak\u00fapenie samotnej licencie. Podpora sa nakupuje iba na hyperv\u00edzoroch, ovirt-engine, na rozdiel od vCenter Server, nevy\u017eaduje v\u00fddavky.<\/p>\n

    Pr\u00edklad kalkul\u00e1cie na 1. rok vlastn\u00edctva<\/h4>\n

    \nZv\u00e1\u017eme klaster z 4 dvojsocketov\u00fdch strojov a maloobchodn\u00e9 ceny (bez projektov\u00fdch zliav).
    \n\u0160tandardn\u00e9 predplatn\u00e9 RHV     stoj\u00ed $999<\/a><\/noindex> za socket\/rok (premium 365\/24\/7 \u2014 $1499), celkovo 4*2*$999=$7992<\/b>.
    \n    Cena vSphere<\/a><\/noindex>:<\/p>\n