oVirt a cikin awanni 2. Sashe na 2. Shigar da manajan da runduna

Wannan labarin shine na gaba a cikin jerin akan oVirt, farkon a nan.

Articles

  1. Gabatarwar
  2. Shigar da mai sarrafa (ovirt-engine) da hypervisors (runduna) - Muna nan
  3. Ƙarin saituna

Don haka, bari mu yi la'akari da al'amurran da suka shafi farkon shigarwa na ovirt-engine da ovirt-host aka gyara.

Ana iya samun ƙarin cikakkun hanyoyin shigarwa koyaushe a ciki takardun.

Abubuwa

  1. Shigar da injin-ovirt
  2. Shigar da ovirt-host
  3. Ƙara node zuwa oVirtN
  4. Saita hanyar sadarwa ta hanyar sadarwa
  5. Saitin FC
  6. Saita FCoE
  7. ISO image ajiya
  8. Farkon VM

Shigar da injin-ovirt

Don Injiniya, mafi ƙarancin buƙatun shine 2 cores/4 GiB RAM/25 GiB ajiya. An ba da shawarar - daga 4 cores/16 GiB na RAM/50 GiB na ajiya. Muna amfani da zaɓin Mai sarrafa Standalone, lokacin da injin ke aiki akan keɓaɓɓen na'ura na zahiri ko kama-da-wane a wajen gungu mai sarrafawa. Don shigarwar mu, za mu ɗauki injin kama-da-wane, alal misali, akan ESXi* mai zaman kansa. Ya dace don amfani da tura kayan aikin sarrafa kansa ko cloning daga samfurin da aka shirya a baya ko shigarwa kickstart.

* Lura: Don tsarin samarwa wannan mummunan ra'ayi ne saboda ... manajan yana aiki ba tare da ajiyar kuɗi ba kuma ya zama kwalban kwalba. A wannan yanayin, yana da kyau a yi la'akari da zaɓin Injin mai sarrafa kansa.

Idan ya cancanta, ana bayanin hanyar juyar da Standalone zuwa Hosted Self Hosted dalla-dalla a ciki takardun. Musamman ma, mai watsa shiri yana buƙatar a ba da umarnin sake shigar da shi tare da tallafin Injin Hosted.

Mun shigar da CentOS 7 akan VM a cikin ƙaramin tsari, sannan sabunta kuma sake kunna tsarin:

$ sudo yum update -y && sudo reboot

Yana da amfani don shigar da wakilin baƙo don injin kama-da-wane:

$ sudo yum install open-vm-tools

don VMware ESXi runduna, ko na oVirt:

$ sudo yum install ovirt-guest-agent

Haɗa ma'ajiyar kuma shigar da manajan:

$ sudo yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm
$ sudo yum install ovirt-engine

Saitin asali:

$ sudo engine-setup

A mafi yawan lokuta, saitunan tsoho sun isa; don amfani da su ta atomatik, zaku iya gudanar da tsarin tare da maɓalli:

$ sudo engine-setup --accept-defaults

Yanzu za mu iya haɗawa da sabon injin mu a ovirt.lab.example.com. Har yanzu babu komai a nan, don haka bari mu matsa zuwa shigar da hypervisors.

Shigar da ovirt-host

Mun shigar da CentOS 7 a cikin ƙaramin tsari akan mai masaukin baki, sannan mu haɗa ma'ajiyar, sabuntawa da sake kunna tsarin:

$ sudo yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release43.rpm
$ sudo yum update -y && sudo reboot

Lura: Ya dace don amfani da tura kayan aikin sarrafa kansa ko shigarwa na kickstart don shigarwa.

Misali fayil kickstart
Tsanaki Ana share sassan da suka wanzu ta atomatik! Yi hankali!

# System authorization information
auth --enableshadow --passalgo=sha512
# Use CDROM installation media
cdrom
# Use graphical install
graphical
# Run the Setup Agent on first boot
firstboot --enable
ignoredisk --only-use=sda
# Keyboard layouts
keyboard --vckeymap=us --xlayouts='us','ru' --switch='grp:alt_shift_toggle'
# System language
lang ru_RU.UTF-8

# Network information
network  --bootproto=dhcp --device=ens192 --ipv6=auto --activate
network  --hostname=kvm01.lab.example.com

# Root password 'monteV1DE0'
rootpw --iscrypted $6$6oPcf0GW9VdmJe5w$6WBucrUPRdCAP.aBVnUfvaEu9ozkXq9M1TXiwOm41Y58DEerG8b3Ulme2YtxAgNHr6DGIJ02eFgVuEmYsOo7./
# User password 'metroP0!is'
user --name=mgmt --groups=wheel --iscrypted --password=$6$883g2lyXdkDLbKYR$B3yWx1aQZmYYi.aO10W2Bvw0Jpkl1upzgjhZr6lmITTrGaPupa5iC3kZAOvwDonZ/6ogNJe/59GN5U8Okp.qx.
# System services
services --enabled="chronyd"
# System timezone
timezone Europe/Moscow --isUtc
# System bootloader configuration
bootloader --append=" crashkernel=auto" --location=mbr --boot-drive=sda
# Partition clearing information
clearpart --all
# Disk partitioning information
part /boot --fstype xfs --size=1024 --ondisk=sda  --label=boot
part pv.01 --size=45056 --grow
volgroup HostVG pv.01 --reserved-percent=20
logvol swap --vgname=HostVG --name=lv_swap --fstype=swap --recommended
logvol none --vgname=HostVG --name=HostPool --thinpool --size=40960 --grow
logvol / --vgname=HostVG --name=lv_root --thin --fstype=ext4 --label="root" --poolname=HostPool --fsoptions="defaults,discard" --size=6144 --grow
logvol /var --vgname=HostVG --name=lv_var --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=16536
logvol /var/crash --vgname=HostVG --name=lv_var_crash --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=10240
logvol /var/log --vgname=HostVG --name=lv_var_log --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=8192
logvol /var/log/audit --vgname=HostVG --name=lv_var_audit --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=2048
logvol /home --vgname=HostVG --name=lv_home --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=1024
logvol /tmp --vgname=HostVG --name=lv_tmp --thin --fstype=ext4 --poolname=HostPool --fsoptions="defaults,discard" --size=1024

%packages
@^minimal
@core
chrony
kexec-tools

%end

%addon com_redhat_kdump --enable --reserve-mb='auto'

%end

%anaconda
pwpolicy root --minlen=6 --minquality=1 --notstrict --nochanges --notempty
pwpolicy user --minlen=6 --minquality=1 --notstrict --nochanges --emptyok
pwpolicy luks --minlen=6 --minquality=1 --notstrict --nochanges --notempty
%end
# Reboot when the install is finished.
reboot --eject

Ajiye wannan fayil ɗin, misali. ftp.example.com/pub/labkvm.cfg. Don amfani da rubutun lokacin fara shigarwar OS, zaɓi 'Shigar da CentOS 7', kunna yanayin gyara siga (maɓallin Tab) kuma ƙara a ƙarshen (tare da sarari, ba tare da ƙima ba)

' inst.ks=ftp://ftp.example.com/pub/labkvm.cfg'

.
Rubutun shigarwa yana share ɓangarori na yanzu akan /dev/sda, yana ƙirƙirar sababbi shawarwarin masu haɓakawa (yana da dacewa don duba su bayan shigarwa ta amfani da umarnin lsblk). An saita sunan mai watsa shiri azaman kvm01.lab.example.com (bayan shigarwa, zaku iya canza shi tare da umarnin hostnamectl set-hostname kvm03.lab.example.com), ana samun adireshin IP ta atomatik, yankin lokaci shine Moscow, An ƙara tallafin harshen Rashanci.

Tushen kalmar sirrin mai amfani: monteV1DE0, kalmar sirrin mai amfani mgmt: metroP0!is.
Hankali! Ana share sassan da suka wanzu ta atomatik! Yi hankali!

Muna maimaita (ko aiwatar da a layi daya) akan duk runduna. Daga kunna uwar garken "ba komai" zuwa shirye-shiryen yanayi, la'akari da dogon zazzagewar 2, yana ɗaukar kusan mintuna 20.

Ƙara node zuwa oVirt

Yana da sauqi qwarai:

Ƙirƙiri → Runduna → Sabbo →…

Filayen da ake buƙata a cikin maye sune Suna (sunan nuni, misali kvm03), Sunan mai watsa shiri (FQDN, misali kvm03.lab.example.com) da sashin Tabbatarwa - tushen mai amfani (mai canzawa) - kalmar sirri ko SSH Public Key.

Bayan danna maɓallin Ok Za ku karɓi saƙo “Ba ku saita Gudanar da Wuta don wannan Mai watsa shiri ba. Kun tabbata kuna son ci gaba?”. Wannan al'ada ce - za mu kalli sarrafa wutar lantarki daga baya, bayan an sami nasarar haɗa mai watsa shiri. Koyaya, idan injunan da aka shigar da runduna ba su goyan bayan gudanarwa (IPMI, iLO, DRAC, da sauransu), Ina ba da shawarar kashe shi: Lissafi → Clusters → Default → Shirya → Wasan wasa → Kunna shinge, cire alamar akwatin.

Idan ba a haɗa ma'ajiyar oVirt da mai watsa shiri ba, shigarwar zai gaza, amma hakan ba daidai ba - kuna buƙatar ƙara shi, sannan danna Shigar -> Sake sakawa.

Haɗin mai watsa shiri yana ɗaukar ba fiye da mintuna 5-10 ba.

Saita hanyar sadarwa ta hanyar sadarwa

Tun da muna gina tsarin da bai dace ba, haɗin yanar gizon dole ne ya samar da haɗin kai marar amfani, wanda aka yi a cikin Compute → Hosts → tab. HOST → Hanyoyin Sadarwar Sadarwa - Saita Cibiyar Sadarwar Mai watsa shiri.

Dangane da iyawar kayan aikin cibiyar sadarwar ku da hanyoyin gine-gine, zaɓuɓɓukan suna yiwuwa. Yana da kyau a haɗa zuwa tarin manyan maɓalli na sama-sama ta yadda idan mutum ya gaza, kasancewar cibiyar sadarwa ba ta katsewa. Bari mu kalli misalin tashan LACP mai tarawa. Don daidaita tashar da aka tara, "ɗauka" adaftar na 2 da ba a yi amfani da ita tare da linzamin kwamfuta ba kuma "ɗauka" zuwa na 1st. Taga zai bude Ƙirƙiri Sabon Bond, inda LACP (Yanayin 4, Dynamic link aggregation, 802.3ad) aka zaɓi ta tsohuwa. A gefen sauya sheka, ana yin tsari na ƙungiyar LACP da aka saba. Idan ba zai yiwu a gina tarin maɓalli ba, kuna iya amfani da yanayin Active-Backup (Yanayin 1). Za mu kalli saitunan VLAN a cikin labarin na gaba, kuma za mu shiga ƙarin dalla-dalla tare da shawarwarin kafa hanyar sadarwa a cikin takaddar. Jagoran Tsare-tsare da Abubuwan Bukatu.

Saitin FC

Fiber Channel (FC) ana tallafawa daga cikin akwatin kuma yana da sauƙin amfani. Ba za mu kafa hanyar sadarwa ta ajiya ba, gami da kafa tsarin ajiya da masu canza masana'anta a matsayin wani ɓangare na kafa oVirt.

Saita FCoE

FCoE, a ganina, bai zama tartsatsi a cikin cibiyoyin sadarwa na ajiya ba, amma ana amfani dashi akai-akai akan sabobin a matsayin "mile na ƙarshe", misali, a cikin HPE Virtual Connect.

Saita FCoE yana buƙatar ƙarin matakai masu sauƙi.

Saita Injin FCoE

Labari akan gidan yanar gizon Red Hat B.3. Yadda ake saita Manajan Haɓaka Hat don Amfani da FCoE
Akan Manager
, tare da umarni mai zuwa muna ƙara maɓalli ga manajan kuma sake kunna shi:


$ sudo engine-config -s UserDefinedNetworkCustomProperties='fcoe=^((enable|dcb|auto_vlan)=(yes|no),?)*$'
$ sudo systemctl restart ovirt-engine.service

Saita Node FCoE

A kan oVirt-Hosts kuna buƙatar shigarwa

$ sudo yum install vdsm-hook-fcoe

Na gaba shine saitin FCoE na yau da kullun, labarin akan Red Hat: 25.5. Saita tashar Fiber akan Interface na Ethernet.

Don Broadcom CNA, duba ƙari Jagorar Mai amfani FCoE Kanfigareshan don Masu Adawa na tushen Broadcom.

Tabbatar cewa an shigar da fakitin (riga a ɗan ƙaranci):

$ sudo yum install fcoe-utils lldpad

Na gaba shine saitin kanta (maimakon ens3f2 da ens3f3 muna maye gurbin sunayen CNAs da aka haɗa a cikin hanyar sadarwar ajiya):

$ sudo cp /etc/fcoe/cfg-ethx /etc/fcoe/cfg-ens3f2
$ sudo cp /etc/fcoe/cfg-ethx /etc/fcoe/cfg-ens3f3
$ sudo vim /etc/fcoe/cfg-ens3f2
$ sudo vim /etc/fcoe/cfg-ens3f3

Muhimmanci: Idan cibiyar sadarwa tana goyan bayan DCB/DCBX a cikin kayan masarufi, dole ne a saita ma'aunin DCB_REQUIRED zuwa a'a.

DCB_REQUIRED="e" → #DCB_REQUIRED="e"

Na gaba, yakamata ku tabbatar cewa an kashe adminStatus akan duk hanyoyin sadarwa, gami da. ba tare da kunna FCoE ba:

$ sudo lldptool set-lldp -i ens3f0 adminStatus=disabled
...
$ sudo lldptool set-lldp -i ens3f3 adminStatus=disabled

Idan akwai wasu hanyoyin sadarwa na cibiyar sadarwa, zaku iya kunna LLDP:

$ sudo systemctl start lldpad
$ sudo systemctl enable lldpad

Kamar yadda aka fada a baya, idan aka yi amfani da kayan aikin DCB/DCBX, dole ne a kunna saitin DCB_REQUIRED a ciki. babu kuma ana iya tsallake wannan matakin.

$ sudo dcbtool sc ens3f2 dcb on
$ sudo dcbtool sc ens3f3 dcb on
$ sudo dcbtool sc ens3f2 app:fcoe e:1
$ sudo dcbtool sc ens3f3 app:fcoe e:1
$ sudo ip link set dev ens3f2 up
$ sudo ip link set dev ens3f3 up
$ sudo systemctl start fcoe
$ sudo systemctl enable fcoe

Don mu'amalar hanyar sadarwa, duba ko an kunna autostart:

$ sudo vim /etc/sysconfig/network-scripts/ifcfg-ens3f2
$ sudo vim /etc/sysconfig/network-scripts/ifcfg-ens3f3

ONBOOT=yes

Duba musaya na FCoE da aka saita, fitarwar umarni bai kamata ya zama fanko ba.

$ sudo fcoeadm -i

Ana yin saitin FCoE na gaba azaman na FC na yau da kullun.

Na gaba ya zo da daidaitawar tsarin ajiya da cibiyoyin sadarwa - zoning, SAN runduna, ƙirƙira da gabatar da kundin / LUNs, bayan haka za'a iya haɗa ajiya zuwa rundunonin ovirt: Storage → Domains → Sabon Domain.

Bar Ayyukan Domain azaman Bayanai, Nau'in Ajiya azaman Tashoshin Fiber, Mai watsa shiri kamar kowane, suna kamar misali storNN-volMM.

Tabbas tsarin ajiyar ku yana ba da damar haɗi ba kawai don ajiyar hanya ba, har ma don daidaitawa. Yawancin tsarin zamani suna da ikon watsa bayanai tare da dukkan hanyoyi daidai gwargwado (ALUA mai aiki/aiki).

Don kunna duk hanyoyi a cikin jihar mai aiki, kuna buƙatar saita multipasing, ƙari akan wannan a cikin labarai masu zuwa.

Kafa NFS da iSCSI ana yin su ta hanya iri ɗaya.

ISO image ajiya

Don shigar da OS, kuna buƙatar fayilolin shigarwa, galibi ana samun su ta hanyar hotunan ISO. Kuna iya amfani da hanyar da aka gina, amma don yin aiki tare da hotuna a cikin oVirt, an haɓaka nau'in ajiya na musamman - ISO, wanda za'a iya yin niyya ga uwar garken NFS. Ƙara shi:

Adana → Domains → Sabon Domain,
Ayyukan yanki → ISO,
Hanyar fitarwa - misali mynfs01.example.com:/exports/ovirt-iso (a lokacin haɗi, babban fayil ɗin dole ne ya zama fanko, dole ne mai sarrafa ya iya rubuta masa).
Suna - misali mynfs01-iso.

Manajan zai ƙirƙiri tsari don adana hotuna
/exports/ovirt-iso/<some UUID>/images/11111111-1111-1111-1111-111111111111/

Idan an riga an sami hotunan ISO akan sabar NFS ɗin mu, don adana sarari yana dacewa don haɗa su zuwa wannan babban fayil maimakon kwafin fayiloli.

Farkon VM

A wannan matakin, zaku iya ƙirƙirar injin kama-da-wane na farko, shigar da OS da software akan shi.

Ƙirƙiri → Injin Farko → Sabo

Don sabon injin, saka suna (Sunan), ƙirƙira faifai (Hotunan Misali → Ƙirƙiri) kuma haɗa hanyar sadarwa ta hanyar sadarwa (Instantiate VM network musaya ta hanyar ɗaukar bayanan vNIC → zaɓi kawai ovirtmgmt daga jerin a yanzu).

A gefen abokin ciniki kuna buƙatar mai bincike na zamani da abokin ciniki SPICE don yin hulɗa tare da na'ura mai kwakwalwa.

An yi nasarar harba injin na farko. Koyaya, don ƙarin cikakken aiki na tsarin, ana buƙatar ƙarin ƙarin saitunan, waɗanda za mu ci gaba a cikin labarai masu zuwa.

source: www.habr.com

Add a comment