{"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\/sq\/blog\/administrirovanie\/ovirt-za-2-chasa-chast-1-otkrytaya-otkazoustojchivaya-platforma-virtualizaczii","title":{"rendered":"oVirt n\u00eb 2 or\u00eb. Pjesa 1. Platforma e hapur e virtualizimit me q\u00ebndrueshm\u00ebri t\u00eb lart\u00eb.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Hyrje<\/h2>\n

\nProjekti me burim t\u00eb hapur oVirt<\/a><\/noindex> \u2014 nj\u00eb platform\u00eb falas p\u00ebr virtualizimin e nivelit t\u00eb korporatave. Duke rishikuar habr, zbulova se oVirt<\/a><\/noindex> nuk ka marr\u00eb aq shum\u00eb v\u00ebmendje sa e meriton.
\noVirt n\u00eb fakt \u00ebsht\u00eb upstream p\u00ebr sistemin komercial Red Hat Virtualization (RHV, m\u00eb par\u00eb RHEV), q\u00eb rritet n\u00ebn mb\u00ebshtetje t\u00eb Red Hat. P\u00ebr t\u00eb shmangur ngat\u00ebrresat, kjo jo<\/b> \u00ebsht\u00eb e nj\u00ebjt\u00eb me CentOS vs RHEL, modeli \u00ebsht\u00eb m\u00eb af\u00ebr Fedora vs RHEL.
\nN\u00ebn kapak \u2014 KVM<\/a><\/noindex>, administrimi b\u00ebhet me an\u00eb t\u00eb nj\u00eb nd\u00ebrfaqeje web. Bazohet n\u00eb OS RHEL\/CentOS 7.
\noVirt mund t\u00eb p\u00ebrdoret p\u00ebr virtualizimin \"tradicional\" t\u00eb server\u00ebve, si dhe virtualizimin desktop (VDI), p\u00ebr dallim nga zgjidhja VMware, t\u00eb dy sistemet mund t\u00eb bashk\u00ebjetojn\u00eb n\u00eb nj\u00eb kompleks.
\nProjekti \u00ebsht\u00eb mir\u00eb dokumetuar<\/a><\/noindex>, ka arritur prej koh\u00ebsh nj\u00eb q\u00ebndrim t\u00eb fort\u00eb p\u00ebr aplikim produktiv dhe \u00ebsht\u00eb i gatsh\u00ebm p\u00ebr ngarkesa t\u00eb larta.
\nKy artikull \u00ebsht\u00eb i pari n\u00eb nj\u00eb cik\u00ebl mbi nd\u00ebrtimin e nj\u00eb klasteri t\u00eb q\u00ebndruesh\u00ebm. Duke kaluar p\u00ebrmes tyre, do t\u00eb kemi nj\u00eb sistem funksional plot\u00ebsisht brenda nj\u00eb kohe t\u00eb shkurt\u00ebr (rreth 2 or\u00eb), ndon\u00ebse disa \u00e7\u00ebshtje, sigurisht, nuk do t\u00eb mund t\u00eb trajtohen, do t\u00eb p\u00ebrpiqem t'i p\u00ebrfshij n\u00eb artikujt e ardhsh\u00ebm.<\/a><\/noindex>
\nE p\u00ebrdorim vet\u00eb p\u00ebr disa vite, kemi filluar me versionin 4.1. Sistemi yn\u00eb industrial tani operon n\u00eb serverat HPE Synergy 480 dhe ProLiant BL460c t\u00eb gjenerat\u00ebs s\u00eb 10-t\u00eb me CPU Xeon Gold.
\nN\u00eb momentin e shkrimit, versioni aktual \u00ebsht\u00eb 4.3. <\/p>\n

Artikuj<\/h2>\n

<\/p>\n

    \n
  1. Hyrje (Ne jemi k\u00ebtu)<\/li>\n
  2. Instalimi i menaxherit (ovirt-engine) dhe hiper-vizor\u00ebve (hosts)<\/a><\/noindex><\/li>\n
  3. Cil\u00ebsimet shtes\u00eb<\/a><\/noindex><\/li>\n<\/ol>\n

    Karakteristikat funksionale<\/h2>\n

    \nN\u00eb oVirt ka 2 entitete kryesore: ovirt-engine dhe ovirt-host(s). P\u00ebr ata q\u00eb jan\u00eb t\u00eb njohur mir\u00eb me produktet VMware, oVirt n\u00eb p\u00ebrgjith\u00ebsi si platform\u00eb \u00ebsht\u00eb si vSphere, ovirt-engine \u2014 shtresa menaxhuese \u2014 kryen t\u00eb nj\u00ebjtat funksione si vCenter, nd\u00ebrsa ovirt-host \u2014 hipervizori, si ESX(i). Duke qen\u00eb se vSphere \u00ebsht\u00eb nj\u00eb zgjidhje shum\u00eb e njohur, ndonj\u00ebher\u00eb do t\u00eb b\u00ebj krahasime me t\u00eb.
    \n\"oVirt
    \nFig. 1 \u2014 paneli i kontrollit oVirt.<\/p>\n

    Si makina mysafir, mb\u00ebshteten shumica e shp\u00ebrndarjeve t\u00eb Linux dhe versioneve t\u00eb Windows. P\u00ebr makinat mysafir ka agjent\u00eb dhe pajisje virtuale t\u00eb optimizuara dhe drejtor\u00eb virtio, kryesisht kontrolluesi i diskut dhe nd\u00ebrfaqja rrjet.
    \nP\u00ebr realizimin e nj\u00eb zgjidhjeje t\u00eb q\u00ebndrueshme dhe t\u00eb gjitha funksioneve interesante, do t\u00eb nevojitet nj\u00eb ruajtje e p\u00ebrbashk\u00ebt. Mb\u00ebshteten si ruajtjet bloqesh FC, FCoE, iSCSI, ashtu edhe ruajtjet NFS dhe t\u00eb tjera. P\u00ebr realizimin e nj\u00eb zgjidhjeje t\u00eb q\u00ebndrueshme, sistemi i ruajtjes gjithashtu duhet t\u00eb jet\u00eb i q\u00ebndruesh\u00ebm (minimum 2 kontrollues, multi-pathing).
    \nP\u00ebrdorimi i magazinave lokale \u00ebsht\u00eb i mundur, por p\u00ebr varsit\u00eb e saj, p\u00ebr klasterin aktual p\u00ebrdoren vet\u00ebm magazinat e ndara (shared storages). Magazinat lokale e b\u00ebjn\u00eb sistemin nj\u00eb grup t\u00eb shp\u00ebrndar\u00eb hipervizor\u00ebsh dhe madje edhe me nj\u00eb magazin\u00eb t\u00eb ndar\u00eb, klasteri nuk mund t\u00eb krijohet. Rruga m\u00eb e sakt\u00eb \u00ebsht\u00eb makinat pa disk me boot from SAN, ose disqe me kapacitet minimal. Ndoshta, p\u00ebrmes vdsm hook \u00ebsht\u00eb e mundur t\u00eb krijohet nj\u00eb variant me disqe lokale Software Defined Storage (p.sh., Ceph) dhe p\u00ebr t\u00eb prezantuar VM-t\u00eb, por nuk e kam shqyrtuar thell\u00ebsisht.<\/p>\n

    Arkitektura<\/h4>\n

    \n\"oVirt
    \nFig. 2 \u2014 arkitektura e oVirt.
    \nM\u00eb shum\u00eb p\u00ebr arkitektur\u00ebn mund t\u00eb gjeni n\u00eb     dokumentacionin<\/a><\/noindex> zhvilluesin.<\/p>\n

    \"oVirt
    \nFig. 3 \u2014 objektet e oVirt.<\/p>\n

    Elementi m\u00eb i lart\u00eb n\u00eb hierarki \u2014 Qendra e t\u00eb Dh\u00ebnave<\/b>. Ai p\u00ebrcakton n\u00ebse p\u00ebrdoren magazina t\u00eb ndara (shared) ose lokale, si dhe grupin e funksioneve t\u00eb p\u00ebrdorura (kompatibiliteti, nga 4.1 n\u00eb 4.3). Mund t\u00eb ket\u00eb nj\u00eb ose m\u00eb shum\u00eb. P\u00ebr shum\u00eb variante, p\u00ebrdorimi i Data Center si parazgjedhje \u2014 Default \u2014 \u00ebsht\u00eb i p\u00ebrshtatsh\u00ebm.
    \nData Center p\u00ebrb\u00ebhet nga nj\u00eb ose m\u00eb shum\u00eb Klastra<\/b>. Klasteri p\u00ebrcakton llojin e procesorit, politikat e migrimit etj. P\u00ebr instalime t\u00eb vogla gjithashtu mund t\u00eb mjaftohemi me klasterin Default.
    \nKlasteri, nga ana e tij, p\u00ebrb\u00ebhet nga Host<\/b>\u2018eve, q\u00eb realizojn\u00eb pun\u00ebn e k\u00ebrkuar \u2014 ato mbajn\u00eb makina virtuale, dhe jan\u00eb t\u00eb lidhura me magazina. N\u00eb klas\u00ebr pritet t\u00eb ket\u00eb 2 ose m\u00eb shum\u00eb hoste. Megjith\u00ebse \u00ebsht\u00eb teknikisht e mundur t\u00eb krijohet nj\u00eb klas\u00ebr me 1 host, kjo nuk ka asnj\u00eb p\u00ebrfitim praktik.<\/p>\n

    N\u00eb oVirt mb\u00ebshteten shum\u00eb funksione, duke p\u00ebrfshir\u00eb migronin e drejtp\u00ebrdrejt\u00eb t\u00eb makinave virtuale nd\u00ebrmjet hipervizor\u00ebve (live migration) dhe magazinave (storage migration), virtualizimi desktop (virtual desktop infrastructure) me grupe VM, VM me gjendje dhe pa gjendje, mb\u00ebshtetje p\u00ebr NVidia Grid vGPU, import nga vSphere, KVM, ka nj\u00eb API<\/a><\/noindex> dhe shum\u00eb t\u00eb tjera. T\u00eb gjitha k\u00ebto funksione jan\u00eb t\u00eb disponueshme pa tarifat e licenc\u00ebs, dhe n\u00ebse nevojitet mb\u00ebshtetje, mund t\u00eb blihen nga Red Hat p\u00ebrmes partner\u00ebve rajonal\u00eb.<\/p>\n

    P\u00ebr \u00e7mimet e RHV<\/h4>\n

    \n\u00c7mimi \u00ebsht\u00eb jo i lart\u00eb krahasuar me VMware, blihen vet\u00ebm mb\u00ebshtetje \u2014 pa k\u00ebrkes\u00eb p\u00ebr blerjen e vet\u00eb licenc\u00ebs. Mb\u00ebshtetje blihen vet\u00ebm p\u00ebr hipervizor\u00ebt, ovirt-engine, ndryshe nga vCenter Server, nuk k\u00ebrkon shpenzime.<\/p>\n

    Shembulli i llogaritjes p\u00ebr vitin e par\u00eb t\u00eb pron\u00ebsis\u00eb<\/h4>\n

    \nLe t\u00eb shqyrtojm\u00eb nj\u00eb klaster prej 4 makinash me 2 socket dhe \u00e7mimet me pakic\u00eb (pa zbritje projekti).
    \nAbonimi standard RHV     kushton $999<\/a><\/noindex> p\u00ebr socket\/vit (premium 365\/24\/7 \u2014 $1499), gjithsej 4*2*$999=$7992<\/b>.
    \n    \u00c7mimi i vSphere<\/a><\/noindex>:<\/p>\n