注意都要获取当前大版本对应的最新部署安装包,尤其是Node ISO要和Engine RPM对应起来,都用最新的就没问题,Virt-Viewer及Virtio-Win是辅助。
(注:可以使用本站提供的离线版本,在安装包下载页面下载。)
oVirt Node ISO:
https://resources.ovirt.org/pub/ovirt-4.4/iso/ovirt-node-ng-installer/4.4.3-2020111016/el8/ovirt-node-ng-installer-4.4.3-2020111016.el8.iso
oVirt Engine Appliance RPM:
https://resources.ovirt.org/pub/ovirt-4.4/rpm/el8/x86_64/ovirt-engine-appliance-4.4-20201110154142.1.el8.x86_64.rpm
Virt-Viewer:
https://virt-manager.org/download/sources/virt-viewer/virt-viewer-x64-9.0.msi
Virtio-Win ISO:
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.189-1/virtio-win-0.1.189.iso
备用下载地址:
http://mirror.isoc.org.il/pub/ovirt/ovirt-4.4
http://mirror.massclouds.com/ovirt/ovirt-4.4
https://mirrors.bfsu.edu.cn/ovirt/ovirt-4.4/
规划网络
根据你的网络实际情况为Node和Engin规划网络信息,如下:
Engine:
域名:engine240.com;
IP:192.168.105.240;
Netmask:255.255.255.0;
Gateway:192.168.105.254
Node:
域名:node241.com;
IP:192.168.105.241;
Netmask:255.255.255.0;
Gateway:192.168.105.254
注意:
应确保所规划的域名不能够在外网解析,即安装部署前域名不能ping通;
安装Node
分别使用Node ISO通过CD引导安装用于Node的主机;
1、语言选择中文即可;
2、键盘选择“汉语”;
3、安装目的地选中本地磁盘,选中“自动”分区,注意如果磁盘上有其它数据的话要执行回收空间操作;
4、时间和日期选择“亚洲/上海”时区;
5、网络和主机名处要根据上面我们规划的网络信息配置,包括主机名(这个地方直接用域名做主机名了)和IP信息;
6、安装过程中配置root密码;
7、安装完成后重启主机;
(注意:如果采用本站的离线版本部署,则不需要执行下面针对软件源的操作。)
通过ssh登录到该主机上,将/etc/yum.repos.d/下的文件删除掉(可以备份到其它目录下),如下:
mkdir /root/repos_bak
mv /etc/yum.repos.d/* /root/repos_bak
部署HostedEngine
添加域名解析
修改Node主机的/etc/hosts文件,增加Node主机和Engine的域名解析,如下:
192.168.105.241 node241.com
192.168.105.240 engine240.com
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
安装Engine Appliance RPM包
将上面下载的Engine RPM包上传到Node主机上的任意目录,例如/root目录下,执行以下命令安装:
rpm -ivh ovirt-engine-appliance-4.4-20201110154142.1.el8.x86_64.rpm
(注意:如果采用本站的离线版本部署,则不需要执行安装engine rpm包这步。)
创建NFS存储
执行命令在/data/images下新建一个nfs目录,并将其权属修改为vdsm:kvm,如下:
mkdir /data/images/nfs
chown vdsm:kvm /data/images/nfs
编辑/etc/exports文件
vi /etc/exports
增加如下内容:
/data/images/nfs *(rw,sync,no_wdelay,insecure_locks,no_root_squash)
重启nfs服务并设置为开机自启动
systemctl restart nfs-server
systemctl enable nfs-server
通过Cockpit执行部署过程
然后打开浏览器,输入上面Node主机的Cockpit Web管理台的地址(端口号是9090),如https://192.168.105.241:9090,使用root帐号登录
报错
如下图所示,安装hosted engine的过程中出现了一个ERROR:
hostname ‘xxx’ doesn’t uniquely match the interface ‘ens33’ selected for the management bridge; it matches also interface with IP [u’fe80::fc16:3eff:fe4e:fdc0’, u’xxx.xxx.xxx.xxx’, u’192.168.222.1’]. Please make sure that the hostname got from the interface for the management network resolves only there
————————————————
版权声明:本文为CSDN博主「前方一片光明」的原创文章,遵循CC 4.0 BY-SA版权协议,转载请附上原文出处链接及本声明。
原文链接:https://blog.csdn.net/qq_26230421/article/details/110524573
,要求需要关闭virbr0的网卡,网上查了一下virbr0是kvm虚拟机使用的网卡,是libvirtd服务安装后,自动生成的,virbr0的配置文件位置/etc/libvirt/qemu/networks/default.xml ,libvirtd服务的配置文件位置/etc/libvirt/libvirtd.conf
手动关闭virbr0网卡
示例:
ifconfig virbr0 down
将virbr0的配置文件删除
示例:
mv /etc/libvirt/qemu/networks/default.xml
/etc/libvirt/qemu/networks/default.xml.bak
————————————————
`[root@node2013 network-scripts]# vi ifcfg-ens33
[root@node2013 network-scripts]# systemctl restart network
[root@node2013 network-scripts]# ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.20.13 netmask 255.255.255.0 broadcast 192.168.20.255
inet6 fe80::4bfa:853b:e353:e084 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:45:b9:dc txqueuelen 1000 (Ethernet)
RX packets 4167878 bytes 5946438023 (5.5 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 378065 bytes 54133809 (51.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 697 bytes 3238966 (3.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 697 bytes 3238966 (3.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:54:00:8e:01:20 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[root@node2013 network-scripts]# vi ifcfg-ens33
[root@node2013 network-scripts]# vi /etc/hostname
[root@node2013 network-scripts]# virsh net-destroy default
setlocale: No such file or directory
Network default destroyed
[root@node2013 network-scripts]#
[root@node2013 network-scripts]# ifconfig virbr0 down
virbr0: ERROR while getting interface flags: No such device
[root@node2013 network-scripts]# ifconfig virbro down
virbro: ERROR while getting interface flags: No such device
[root@node2013 network-scripts]# ifconfig virbr0 down
virbr0: ERROR while getting interface flags: No such device
[root@node2013 network-scripts]# mv /etc/libvirt/qemu/networks/default.xml /etc/libvirt/qemu/networks/default.xml.bak
[root@node2013 network-scripts]# ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.20.13 netmask 255.255.255.0 broadcast 192.168.20.255
inet6 fe80::4bfa:853b:e353:e084 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:45:b9:dc txqueuelen 1000 (Ethernet)
RX packets 4169192 bytes 5946587496 (5.5 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 379484 bytes 55190586 (52.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 697 bytes 3238966 (3.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 697 bytes 3238966 (3.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0