Yi-shi-kanka Bare-Metal Provisioning, ko Shirya sabar ta atomatik daga karce

Sannu, Ni Denis ne kuma ɗayan wuraren aiki na shine haɓaka hanyoyin samar da ababen more rayuwa a X5. A yau zan so in raba tare da ku yadda zaku iya tura tsarin shirye-shiryen uwar garken atomatik bisa ga kayan aikin da ake samu a bainar jama'a. A ganina, wannan bayani ne mai ban sha'awa, mai sauƙi da sauƙi.

Ta hanyar shiri muna nufin: juya sabon uwar garken daga cikin akwatin zuwa cikakkiyar uwar garken da aka tsara tare da OS. Linux ko tare da ESXi hypervisor (ba a tattauna jigilar sabar Windows ba a cikin wannan labarin).

Sharuɗɗa:

• sabobin – sabar da ake buƙatar saita su.
• uwar garken shigarwa shine babban uwar garken da ke ba da duk tsarin shirye-shiryen akan hanyar sadarwa.

Me yasa ake buƙatar aiki da kai?

Bari mu ce akwai ɗawainiya: don shirya sabobin da yawa daga karce, a mafi girma - 30 kowace rana. Sabar na masana'anta da ƙira daban-daban, tsarin aiki daban-daban na iya shigar dasu, kuma ƙila ko ƙila suna da hypervisor.

Waɗanne ayyuka ne aka haɗa a cikin tsarin saitin (ba tare da sarrafa kansa ba):

• haɗa keyboard, linzamin kwamfuta, saka idanu zuwa uwar garken;
• saita BIOS, RAID, IPMI;
• sabunta bangaren firmware;
• tura hoton tsarin fayil (ko shigar da hypervisor da kwafin injunan kama-da-wane);

Lura. A madadin, ƙaddamar da OS yana yiwuwa ta hanyar shigarwa tare da fayil ɗin amsawa ta atomatik. Amma ba za a tattauna wannan a cikin labarin ba. Ko da yake za ku ga a ƙasa cewa ƙara wannan aikin ba shi da wahala.

• saita sigogin OS (sunan mai masauki, IP, da sauransu).

Tare da wannan hanyar, saituna iri ɗaya ana yin su akai-akai akan kowace uwar garken. Ingancin irin wannan aikin yana da ƙasa sosai.

Mahimmancin aiki da kai shine kawar da sa hannun ɗan adam daga tsarin shirye-shiryen uwar garken. Kamar yadda zai yiwu.

Automation yana rage raguwa tsakanin ayyuka kuma yana ba da damar samar da sabar da yawa a lokaci guda. Yiwuwar kurakurai saboda abubuwan ɗan adam kuma yana raguwa sosai.

Ta yaya ake saita sabobin ta atomatik?

Bari mu bincika dukkan matakai daki-daki.

Kuna da uwar garken Linux wanda kuke amfani dashi azaman uwar garken shigarwa na PXE. An shigar da kuma saita ayyuka akansa: DHCP, TFTP.

Don haka, muna taya uwar garken (wanda ke buƙatar daidaitawa) ta hanyar PXE. Bari mu tuna yadda yake aiki:

• An zaɓi boot ɗin cibiyar sadarwa akan sabar.
• Sabar tana loda PXE-ROM na katin cibiyar sadarwa kuma tana tuntuɓar uwar garken shigarwa ta DHCP don samun adireshin cibiyar sadarwa.
• Sabar shigarwa ta DHCP tana ba da adireshi, da kuma umarni don ƙarin saukewa ta PXE.
• Sabar tana loda bootloader na cibiyar sadarwa daga uwar garken shigarwa ta hanyar PXE, ƙarin lodi yana faruwa bisa ga fayil ɗin daidaitawa na PXE.
• Boot ɗin yana faruwa ne dangane da sigogin da aka karɓa (kwaya, initramfs, wuraren tsaunuka, hoton squashfs, da sauransu).

Lura. Labarin yana bayyana booting ta hanyar PXE ta yanayin BIOS. A halin yanzu, masana'antun suna aiwatar da UEFI bootmode. Don PXE, bambancin zai kasance cikin daidaitawar uwar garken DHCP da kasancewar ƙarin bootloader.

Bari mu kalli misali na daidaitawar uwar garken PXE (menu na pxelinux).

Fayil pxelinux.cfg/default:

default menu.c32
prompt 0
timeout 100
menu title X5 PXE Boot Menu
LABEL InstallServer Menu
	MENU LABEL InstallServer
	KERNEL menu.c32
	APPEND pxelinux.cfg/installserver
LABEL VMware Menu
	MENU LABEL VMware ESXi Install
	KERNEL menu.c32
	APPEND pxelinux.cfg/vmware
LABEL toolkit // меню по умолчанию
	MENU LABEL Linux Scripting Toolkits
	MENU default
	KERNEL menu.c32
	APPEND pxelinux.cfg/toolkit // переход на следующее меню

Fayil pxelinux.cfg/toolkit:

prompt 0
timeout 100
menu title X5 PXE Boot Menu
label mainmenu
    menu label ^Return to Main Menu
    kernel menu.c32
    append pxelinux.cfg/default
label x5toolkit-auto // по умолчанию — автоматический режим
        menu label x5 toolkit autoinstall
        menu default
        kernel toolkit/tkcustom-kernel
        append initrd=toolkit/tk-initramfs.gz quiet net.ifnames=0 biosdevname=0 nfs_toolkit_ip=192.168.200.1 nfs_toolkit_path=tftpboot/toolkit nfs_toolkit_script=scripts/mount.sh script_cmd=master-install.sh CMDIS2=”…”
label x5toolkit-shell // для отладки - консоль
        menu label x5 toolkit shell
        kernel toolkit/tkcustom-kernel
        append initrd=toolkit/tkcustom-initramfs.gz quiet net.ifnames=0 biosdevname=0 nfs_toolkit_ip=192.168.200.1 nfs_toolkit_path=tftpboot/toolkit nfs_toolkit_script=scripts/mount.sh script_cmd=/bin/bash CMDIS2=”…”

Kwaya da initramfs a wannan mataki shine matsakaicin hoton Linux, tare da taimakon abin da babban shiri da daidaitawar uwar garken zai faru.

Kamar yadda kake gani, bootloader yana wuce sigogi da yawa zuwa kernel. Wasu daga cikin waɗannan sigogi ana amfani da su ta kernel kanta. Kuma za mu iya amfani da wasu don manufar mu. Za a tattauna wannan daga baya, amma a yanzu za ku iya tuna cewa duk sigogin da aka wuce za su kasance a cikin matsakaicin hoton Linux ta /proc/cmdline.

A ina zan iya samun su, kernel da initramfs?
A matsayin tushe, zaku iya zaɓar kowane rarraba Linux. Abin da muke kula da shi lokacin zabar:

• hoton taya dole ne ya zama na duniya (samuwar direbobi, ikon shigar da ƙarin kayan aiki);
• Mafi mahimmanci, kuna buƙatar keɓance initramfs.

Ta yaya ake yin wannan a cikin maganinmu don X5? An zaɓi CentOS 7 a matsayin tushe. Bari mu gwada dabara mai zuwa: shirya tsarin hoto na gaba, shirya shi a cikin ma'ajiyar bayanai kuma ƙirƙirar intramfs, wanda a ciki za a sami tsarin tsarin fayil ɗin mu. Lokacin loda hoton, za a faɗaɗa ma'ajiyar zuwa cikin ɓangaren tmpfs da aka ƙirƙira. Ta wannan hanyar za mu sami ɗan ƙaramin hoto, duk da haka cikakken cikakken hoto na Linux tare da duk abubuwan da ake buƙata, wanda ya ƙunshi fayiloli guda biyu kawai: vmkernel da initramfs.

#создаем директории: 

mkdir -p /tftpboot/toolkit/CustomTK/rootfs /tftpboot/toolkit/CustomTK/initramfs/bin

#подготавливаем структуру:

yum groups -y install "Minimal Install" --installroot=/tftpboot/toolkit/CustomTK/rootfs/
yum -y install nfs-utils mariadb ntpdate mtools syslinux mdadm tbb libgomp efibootmgr dosfstools net-tools pciutils openssl make ipmitool OpenIPMI-modalias rng-tools --installroot=/tftpboot/toolkit/CustomTK/rootfs/
yum -y remove biosdevname --installroot=/tftpboot/toolkit/CustomTK/rootfs/

# подготавливаем initramfs:

wget https://busybox.net/downloads/binaries/1.31.0-defconfig-multiarch-musl/busybox-x86_64 -O /tftpboot/toolkit/CustomTK/initramfs/bin/busybox
chmod a+x /tftpboot/toolkit/CustomTK/initramfs/bin/busybox
cp /tftpboot/toolkit/CustomTK/rootfs/boot/vmlinuz-3.10.0-957.el7.x86_64 /tftpboot/toolkit/tkcustom-kernel

# создаем /tftpboot/toolkit/CustomTK/initramfs/init (ниже содержание скрипта):

#!/bin/busybox sh
/bin/busybox --install /bin
mkdir -p /dev /proc /sys /var/run /newroot
mount -t proc proc /proc
mount -o mode=0755 -t devtmpfs devtmpfs /dev
mkdir -p /dev/pts /dev/shm /dev/mapper /dev/vc
mount -t devpts -o gid=5,mode=620 devpts /dev/pts
mount -t sysfs sysfs /sys
mount -t tmpfs -o size=4000m tmpfs /newroot
echo -n "Extracting rootfs... "
xz -d -c -f rootfs.tar.xz | tar -x -f - -C /newroot
echo "done"
mkdir -p /newroot/dev /newroot/proc /newroot/sys
mount --move /sys  /newroot/sys
mount --move /proc /newroot/proc
mount --move /dev  /newroot/dev
exec switch_root /newroot /sbin/init

# упаковываем rootfs и initramfs:

cd /tftpboot/toolkit/CustomTK/rootfs
tar cJf /tftpboot/toolkit/CustomTK/initramfs/rootfs.tar.xz --exclude ./proc --exclude ./sys --exclude ./dev .
cd /tftpboot/toolkit/CustomTK/initramfs
find . -print0 | cpio --null -ov --format=newc | gzip -9 > /tftpboot/toolkit/tkcustom-initramfs-new.gz

Don haka mun ƙayyade kernel da initramfs waɗanda yakamata a loda su. Sakamakon haka, a wannan matakin, ta hanyar loda madaidaicin hoton Linux ta hanyar PXE, za mu karɓi na'urar wasan bidiyo ta OS.

Mai girma, amma yanzu muna buƙatar canja wurin sarrafawa zuwa "aiki na atomatik".

Ana iya yin haka kamar haka.

Bari mu ɗauka cewa bayan loda hoton muna shirin canja wurin sarrafawa zuwa rubutun mount.sh.
Bari mu haɗa da rubutun mount.sh a cikin autorun. Don yin wannan, kuna buƙatar canza initramfs:

• cire initramfs (idan muka yi amfani da zaɓi na initramfs na sama, wannan ba a buƙata)
• sun haɗa da lamba a cikin farawa wanda zai bincika sigogi da aka wuce ta / proc / cmdline da kuma canja wurin sarrafawa gaba;
• shirya initramfs.

Lura. A cikin yanayin kayan aiki na X5, ana canja wurin sarrafa kaya zuwa rubutun /opt/x5/toolkit/bin/hook.sh с помощью override.conf в getty tty1 (ExecStart=…)

Don haka, an ɗora hoton, wanda rubutun mount.sh ya fara a autorun. Na gaba, rubutun mount.sh yana nazarin sigogi da aka wuce (script_cmd =) yayin aiwatarwa kuma ya ƙaddamar da shirin / rubutun da ake bukata.

alamar kayan aiki -mota
kwaya...
append...nfs_toolkit_script=scripts/mount.sh script_cmd=master-install.sh

alamar kayan aiki -harsashi
kwaya...
append...nfs_toolkit_script=scripts/mount.sh script_cmd=/bin/bash

Anan a gefen hagu akwai menu na PXE, a dama shine zanen canja wurin sarrafawa.

Mun gano canja wurin sarrafawa. Ya danganta da zaɓi na menu na PXE, ko dai an ƙaddamar da rubutun daidaitawa ta atomatik ko na'ura mai gyara kuskure.

A cikin yanayin daidaitawa ta atomatik, ana ɗora kundayen adireshi masu mahimmanci daga uwar garken shigarwa, wanda ya ƙunshi:

• rubutun;
• saitunan BIOS/UEFI don sabar daban-daban;
• firmware;
• kayan aikin uwar garken;
• rajistan ayyukan

Na gaba, rubutun mount.sh yana canja wurin sarrafawa zuwa rubutun master-install.sh daga kundin rubutun.

Itacen rubutun (tsarin da aka kaddamar da su) yayi kama da haka:

• master-install
• Sharefunctions (ayyukan raba)
• bayanai (fitowar bayanai)
• model (saitin shigarwa sigogi dangane da uwar garken model)
• ready_utils (shigar da abubuwan da ake buƙata)
• fwupdate (sabuntawa na firmware)
• diag (ilimin farko)
• biosconf (BIOS/UEFI saitin)
• clockfix (saitin lokaci akan motherboard)
• srmconf (tsarin mu'amala mai nisa)
• raidconf (yana daidaita kundin ma'ana)

daya daga cikin:

• preinstall (canja wurin sarrafawa zuwa OS ko mai sakawa hypervisor, kamar ESXi)
• merged-install (farawa nan da nan na kwashe hoton)

Yanzu mun sani:

• yadda ake taya uwar garken ta hanyar PXE;
• yadda ake canja wurin sarrafawa zuwa rubutun ku.

Mu ci gaba. Tambayoyi masu zuwa sun zama masu dacewa:

• Yadda za a gane uwar garken da muke shiryawa?
• Wadanne kayan aiki da yadda ake saita uwar garken?
• Yadda ake samun saituna don takamaiman uwar garken?

Yadda za a gane uwar garken da muke shiryawa?

Yana da sauƙi - DMI:

dmidecode –s system-product-name
dmidecode –s system-manufacturer
dmidecode –s system-serial-number

Duk abin da kuke buƙata yana nan: mai siyarwa, samfuri, lambar serial. Idan ba ku da tabbacin cewa wannan bayanin yana nan a cikin duk sabar, zaku iya gane su ta adireshin MAC. Ko kuma a cikin hanyoyi guda biyu a lokaci guda, idan masu siyar da uwar garken sun bambanta kuma akan wasu samfuran kawai babu bayani game da lambar serial.

Dangane da bayanan da aka karɓa, ana ɗora manyan fayilolin cibiyar sadarwa daga uwar garken shigarwa kuma ana ɗora duk abin da ake buƙata (kayan aiki, firmware, da sauransu).

Wadanne kayan aiki da yadda ake saita uwar garken?

Zan samar da kayan aiki don Linux don wasu masana'antun. Ana samun duk abubuwan amfani akan gidan yanar gizon hukuma na masu siyarwa.

Tare da firmware, Ina tsammanin komai ya bayyana. Yawancin lokaci suna zuwa cikin nau'ikan fayilolin aiwatarwa. Fayil ɗin da za a iya aiwatarwa yana sarrafa tsarin sabunta firmware kuma yana ba da rahoton lambar dawowa.

BIOS da IPMI yawanci ana saita su ta hanyar samfuri. Idan ya cancanta, ana iya gyara samfurin kafin saukewa.

Hakanan ana iya daidaita kayan aikin RAID daga wasu dillalai ta amfani da samfuri. Idan ba haka lamarin yake ba, to dole ne ka rubuta rubutun daidaitawa.

Hanyar kafa RAID shine yawanci kamar haka:

• Muna buƙatar tsari na yanzu.
• Idan an riga an sami tsararraki masu ma'ana, muna share su.
• Bari mu kalli faifai na zahiri da kuma nawa suke.
• Ƙirƙiri sabon tsari mai ma'ana. Muna katse tsarin idan akwai kuskure.

Yadda ake samun saituna don takamaiman uwar garken?

Bari mu ɗauka cewa za a adana saitunan duk sabobin a kan uwar garken shigarwa. A wannan yanayin, don amsa tambayarmu, dole ne mu fara yanke shawarar yadda ake canja wurin saitunan zuwa uwar garken shigarwa.

Da farko, zaku iya samun ta tare da fayilolin rubutu. (A nan gaba, kuna iya amfani da fayil ɗin rubutu azaman hanyar faɗuwa don canja wurin saituna.)

Kuna iya “raba” fayil ɗin rubutu akan sabar shigarwa. Kuma ƙara hawansa zuwa rubutun mount.sh.

Layukan za, alal misali, suyi kama da haka:

<serial number> <hostname> <subnet>

Injiniya za a tura waɗannan layin zuwa fayil ɗin daga injin aikin sa. Sannan, lokacin kafa uwar garken, za a karanta sigogi na takamaiman uwar garken daga fayil ɗin.

Amma, a cikin dogon lokaci, yana da kyau a yi amfani da bayanai don adana saitunan, jihohi da kuma rajistan ayyukan shigarwar uwar garke.

Tabbas, bayanan bayanai kadai bai isa ba, kuma kuna buƙatar ƙirƙirar ɓangaren abokin ciniki tare da taimakon abin da za a canza saitunan zuwa bayanan. Wannan ya fi wahalar aiwatarwa idan aka kwatanta da fayil ɗin rubutu, amma a zahiri, komai ba shi da wahala kamar yadda ake gani. Yana da yuwuwa a rubuta ƙaramin sigar abokin ciniki wanda kawai zai canja wurin bayanai zuwa bayanan da kanku. Kuma a nan gaba zai yiwu a inganta shirin abokin ciniki a cikin yanayin kyauta (rahotanni, alamun bugu, aika sanarwar, da dai sauransu wanda ya zo a hankali).

Ta hanyar yin ƙayyadaddun buƙatu ga ma'ajin bayanai da ƙididdige lambar sabar uwar garken, za mu karɓi ma'auni masu mahimmanci don daidaita sabar.

Ƙari ga haka, ba za mu buƙaci samar da makullai don shiga lokaci guda ba, kamar yadda yake da fayil ɗin rubutu.

Za mu iya rubuta rubutun sanyi zuwa ga bayanai a duk matakai kuma sarrafa tsarin shigarwa ta hanyar abubuwan da suka faru da kuma tutoci na matakan shirye-shiryen.

Yanzu mun san yadda:

• kora sabar ta hanyar PXE;
• canja wurin sarrafawa zuwa rubutun mu;
• gano uwar garken da ke buƙatar shirya ta lambar serial ɗinsa;
• saita uwar garken ta amfani da abubuwan da suka dace;
• canja wurin saituna zuwa bayanan uwar garken shigarwa ta amfani da ɓangaren abokin ciniki.

Mun gano yadda:

• uwar garken da aka shigar yana karɓar saitunan da suka dace daga bayanan;
• Ana yin rikodin duk ci gaban shirye-shiryen a cikin ma'ajin bayanai ( rajistan ayyukan, abubuwan da suka faru, tutocin mataki).

Me game da nau'ikan software daban-daban da kuka girka? Yadda za a shigar da hypervisor, kwafi VM kuma saita shi duka?

A cikin yanayin tura hoton tsarin fayil (linux) zuwa kayan masarufi, komai yana da sauƙi:

• Bayan saita duk abubuwan haɗin uwar garken, muna tura hoton.
• Shigar da grub bootloader.
• Muna chroot kuma muna saita duk abin da ake buƙata.

Yadda ake canja wurin sarrafawa zuwa mai sakawa OS (ta amfani da ESXi a matsayin misali).

• Muna tsara canja wurin sarrafawa daga rubutun mu zuwa mai sakawa hypervisor ta amfani da fayil ɗin amsa ta atomatik (kickstart):
• Muna share sassan yanzu akan faifai.
• Ƙirƙiri bangare mai girman 500MB.
• Muna yi masa alama azaman bootable.
• Tsarin zuwa FAT32.
• Muna kwafi fayilolin shigarwa na ESXi zuwa tushen.
• Shigar da syslinux.
• Kwafi syslinux.cfg zuwa /syslinux/

default esxi
prompt 1
timeout 50
label esxi
kernel mboot.c32
append -c boot.cfg

• Kwafi boot.c32 zuwa /syslinux.
• Boot.cfg yakamata ya sami kernelopt=ks=ftp:// /ks_esxi.cfg
• Mun sake kunna uwar garken.

Bayan uwar garken ya sake yin aiki, mai sakawa na ESXi zai zazzage daga rumbun kwamfutar uwar garken. Duk fayilolin mai sakawa masu mahimmanci za a loda su cikin ƙwaƙwalwar ajiya sannan za a fara shigarwar ESXi, bisa ga ƙayyadadden fayil ɗin amsawa ta atomatik.

Anan ga ƴan layika daga fayil ɗin amsa kai tsaye ks_esxi.cfg:

%firstboot --interpreter=busybox
…
# получаем серийный номер

SYSSN=$(esxcli hardware platform get | grep Serial | awk -F " " '{print $3}')

# получаем IP

IPADDRT=$(esxcli network ip interface ipv4 get | grep vmk0 | awk -F " " '{print $2}')
LAST_OCTET=$(echo $IPADDRT | awk -F'.' '{print $4}')

# подключаем NFS инсталл-сервера

esxcli storage nfs add -H is -s /srv/nfs_share -v nfsshare1

# копируем временные настройки ssh, для использования ssh-клиента

mv /etc/ssh /etc/ssh.tmp
cp -R /vmfs/volumes/nfsshare1/ssh /etc/
chmod go-r /etc/ssh/ssh_host_rsa_key

# копируем ovftool, для развертывания ВМ сейчас, плюс возможно пригодится позже

cp -R /vmfs/volumes/nfsshare1/ovftool /vmfs/volumes/datastore1/

# развертываем ВМ

/vmfs/volumes/datastore1/ovftool/tools/ovftool --acceptAllEulas --noSSLVerify --datastore=datastore1 --name=VM1 /vmfs/volumes/nfsshare1/VM_T/VM1.ova vi://root:[email protected]
/vmfs/volumes/datastore1/ovftool/tools/ovftool --acceptAllEulas --noSSLVerify --datastore=datastore1 --name=VM2 /vmfs/volumes/nfsshare1/VM_T/VM2.ova vi://root:[email protected]

# получаем строку с настройками нашего сервера

ssh root@is "mysql -h'192.168.0.1' -D'servers' -u'user' -p'secretpassword' -e "SELECT ... WHERE servers.serial='$SYSSN'"" | grep -v ^$ | sed 's/NULL//g' > /tmp/servers
...
# генерируем скрипт настройки сети

echo '#!/bin/sh' > /vmfs/volumes/datastore1/netconf.sh
echo "esxcli network ip interface ipv4 set -i=vmk0 -t=static --ipv4=$IPADDR --netmask=$S_SUB || exit 1" >> /vmfs/volumes/datastore1/netconf.sh
echo "esxcli network ip route ipv4 add -g=$S_GW -n=default || exit 1" >> /vmfs/volumes/datastore1/netconf.sh
chmod a+x /vmfs/volumes/datastore1/netconf.sh

# задаем параметр guestinfo.esxihost.id, указываем в нем серийный номер

echo "guestinfo.esxihost.id = "$SYSSN"" >> /vmfs/volumes/datastore1/VM1/VM1.vmx
echo "guestinfo.esxihost.id = "$SYSSN"" >> /vmfs/volumes/datastore1/VM2/VM2.vmx
...
# обновляем информацию в базе

SYSNAME=$(esxcli hardware platform get | grep Product | sed 's/Product Name://' | sed 's/^ *//')
UUID=$(vim-cmd hostsvc/hostsummary | grep uuid | sed 's/ //g;s/,$//' | sed 's/^uuid="//;s/"$//')
ssh root@is "mysql -D'servers' -u'user' -p'secretpassword' -e "UPDATE servers ... SET ... WHERE servers.serial='$SYSSN'""
ssh root@is "mysql -D'servers' -u'user' -p'secretpassword' -e "INSERT INTO events ...""

# возвращаем настройки SSH

rm -rf /etc/ssh
mv /etc/ssh.tmp /etc/ssh

# настраиваем сеть и перезагружаемся

esxcli system hostname set --fqdn=esx-${G_NICK}.x5.ru
/vmfs/volumes/datastore1/netconf.sh
reboot

A wannan mataki, ana shigar da hypervisor kuma an daidaita shi, kuma ana kwafi na'urori masu kama da juna.

Yadda ake saita injunan kama-da-wane yanzu?

Mun ɗan yi ɗan zamba: yayin shigarwa mun saita ma'aunin guestinfo.esxihost.id = "$ SYSSN" a cikin fayil ɗin VM1.vmx kuma mun nuna lambar serial na uwar garken jiki a ciki.

Yanzu, bayan farawa, injin kama-da-wane (tare da kunshin kayan aikin vmware) na iya samun damar wannan siga:

ESXI_SN=$(vmtoolsd --cmd "info-get guestinfo.esxihost.id")

Wato, VM zai iya gane kansa (ya san lambar serial na runduna ta jiki), yin buƙatu zuwa bayanan uwar garken shigarwa kuma ya karɓi sigogin da ke buƙatar daidaitawa. Wannan duk an haɗa shi cikin rubutun, wanda yakamata a ƙaddamar da shi ta atomatik lokacin da gustos vm ya fara (amma sau ɗaya: RunOnce).

Yanzu mun san yadda:

• kora sabar ta hanyar PXE;
• canja wurin sarrafawa zuwa rubutun mu;
• gano uwar garken da ke buƙatar shirya ta lambar serial ɗinsa;
• saita uwar garken ta amfani da abubuwan da suka dace;
• canja wurin saituna zuwa bayanan uwar garken shigarwa ta amfani da ɓangaren abokin ciniki;
• saita nau'ikan software iri-iri, gami da tura esxi hypervisor da daidaita injunan kama-da-wane (duk ta atomatik).

Mun gano yadda:

• uwar garken da aka shigar yana karɓar saitunan da suka dace daga bayanan;
• Ana yin rikodin duk ci gaban shirye-shiryen a cikin ma'ajin bayanai ( rajistan ayyukan, abubuwan da suka faru, tutocin mataki).

Kasa line:

Na yi imani cewa bambancin wannan bayani ya ta'allaka ne a cikin sassauƙansa, sauƙi, iyawa da haɓakawa.

Da fatan za a rubuta a cikin sharhin abin da kuke tunani.

source: www.habr.com