So when you run the engine setup command, the program will automatically configure the firewall ports on the host. A proper firewall configuration is very much crucial for ensuring that the OLVM engine operates efficiently and securely.
So we need to configure these ports and enable services inside the firewall, which is done automatically by using the engine setup command. But if you want to do the setups manually, we have got a list of firewall services and ports that should be enabled as the manual configurations inside your firewall.
So let’s see, what are the available services that should be enabled? that is the basic services that should be enabled inside your firewall. So in the table, it is showing you all the basic services that should be enabled. And let’s try to discuss on each of these services, like the SSH access to the manager.
So you should enable the SSH port so that you can have passwordless authentication access to your host and your engine machine by using your Linux environment. So for passwordless access, you can use SSH access to be enabled on your manager. So port number 22 should be enabled on the system.
The next important ports and the service that you need to enable is your web interface API access. Now web interface API access requires you to enable the access to the web interface, that is using your portal to access your environment. Administration portal should be enabled and accessed by using these web interface or API access.
The ports which are used here is port number 443 for TCP and port number 80 of TCP. That will be used for defining your web interface and REST APIs. It’s crucial for accessing the management interface securely. And these should be enabled inside your firewall.
The next thing is database communication components. So in database communication components, port number 5432, which is the default port for PostgreSQL which OLVM uses as a database backend. This is where the OLVM stores its configurations and operational data. So to allow the access to this database, I need to enable port number 5432 for the database.
Then we have got the VDSM, which is Virtual Desktop and Server Manager communication. So in VDSM communication, the ports that should be enabled for facilitating communication between the OLVM engine and the host is 54321, which is the default port. And also 54322, which is the secondary VDSM import that should be enabled on your firewall.
Then we have got the Simple Protocol for Independent Computing Environment, which is called as a SPICE. So SPICE protocol, they are ports that can be used for remote desktop connections to virtual machines using SPICE protocol, which provides high-quality remote display capabilities.
And the range of ports is 5900 to 6923. These are the different set of ports that can be enabled on your firewall. We have also got the storage domain ports that will be specific to the storage domains, like NFS storage domain will have ports that will be enabled for accessing your TCP/IP over NFS server port, NFS mounted device ports.
So you have got different set of port numbers that should be enabled, that is basically port number 111, which is the– it should be enabled on TCP and UDP, which is used by the port manager service, which maps your RPC program numbers to your network addresses. You have got 32803, which is used by the nfs-mountd service. So there are multiple ports that should be enabled for your storage access.
Then we have got also for iSCSI storage domains, that is 3260 TCP/IP port that should be enabled for iSCSI target access. So these are some of the ports that should be enabled.
And you can do that by specifying the commands manually on your firewall command line utility, or you can enable that on your firewall daemon by using the firewall-cmd and specify the add ports to enable these ports and permanently store these ports inside your firewall.
So add these ports and permanently store these ports by using your firewall CMD command, which is used for adding these ports inside your firewall daemon. And store these ports permanently inside your environment.
Enable the PKI dependencies and PostgreSQL:13 appstream modules. So these two modules should be enabled on your Linux environment prior to installing your OLVM engine on the host machine.
So basically, the PKI is a system used for managing digital certificates like public key encryptions, security related elements. It typically involves components of certificate authority, certificate signing request, revocation list of certificates, public and private keys.
So PKI dependencies or pki-deps, what you see over there in OLVM is generally referring to the necessary packages or libraries which are required to support PKI operations. The PostgreSQL:13 is a version of PostgreSQL Relational Database Management system, and is an open-source database system that can be installed on your environments.
So these are the two modules that should be enabled inside your Virtualization Manager. The next set is the related modules that should be enabled and the modules that should be disabled for installing your Oracle Linux Virtualization engine, like you need to disable the virt:ol package and you need to install or enable the virt:kvm_utils version 2.
The KVM utils is the component or utility package related to your kernel-based virtual machine, which is a virtualization module in the Linux kernel that allows the kernel to function as a hypervisor. So you’re not working with virt:ol, because from version 4.4, you could say like the new versions are working with kvm_utils2. So you need to install the kvm_utils2.
The other component is enabling ol8_baseos_latest repository. So this basically gives you the options related to the base operating system latest packages and references to the latest packages inside your environment.
Then we have got the ovirt release 8. So I need to install the ovirt module, which is the oracle_ovirt_release_el8, Enterprise Linux 8, is a package for Oracle Linux 8 that provides access to ovirt, a free open-source virtualization management platform. So Oracle version of ovirt includes enhancements and integration specific to Oracle Linux.
So these are the components you should enable or disable inside your Linux node, which will be acting like a Linux Virtualization Manager node. Now the next step will be to make sure that the repositories that should be enabled.
The following repositories should be enabled inside your system. Make sure that these repositories are enabled by enabling these Virtualization Manager repositories which are essential for setting up and managing your virtualization environment.
They provide the necessary packages, updates for virtualization platform like libvirt, qemu, or ovirts. So repositories for Linux managers host packages that facilitate the installation and management of virtualization platforms and tools.
And if a required repository is not enabled, you can do that by using the dnf config-manager command. And you can use the set command or set option and you can enable or disable a repository.
So –set with dnf config-manager enable and the repository name that you want to enable, Or if extra repositories are enabled, you can disable those repositories by using the dnf config-manager command.
Once you have done all these requirements inside your host machine, the next step will be to go ahead and install your manager. So let’s try to see, how will we do it? So install the Oracle Linux Virtualization Manager.
So install the manager using the ovirt engine command by using the dnf install ovirt-engine. The command dnf install ovirt-engine is used to install the ovirt engine on a system running a DNF-based package manager.
So the ovirt engine is a central component of the Ovirt Virtualization Management platform, which provides a web-based interface for managing your virtual machines, storage, and your network resources.
So once you run this command and once the configurations are done, once you have accepted the installation of the packages, then after the installation, you will be requiring to configure your ovirt-engine. So after you have done these installations, the next step will be to configure the Oracle Linux Virtualization Manager engine. We’ll be seeing that in the upcoming posts.
Recent Comments