Red Hat Virtualization (RHV) 4.3 is at the forefront of proverbial presses, takinghas just been releasedA few days ago, and if you’re anxious to start exploring Red Hat Virtualization in your environment, then this blog post is for you!We’re going to walk through a quick start scenario with the new version so you can start working so you can start creating andmigrating their virtual machines as soon as possible.
The amount of time to deploy Red Hat Virtualization and starting to host virtual machines can vary a lot depending on how complex your environment is, if you have all the information ready before you start, how many machines are working, and even the speed of the hardware.On average, the implementation of your first hypervisor and the execution of Red Hat Virtualization Manager will take between 1 and 2 hours. Remember, most of the hard work and decisions are made in the planning phase so that this part is much easier!
It is a good idea to review the Planning guide and prerequisites before starting but, if you decide not to see the entire document, at a minimum,Chapter 4and the content below is a great start.
If you are not familiar withRed Hat Virtualization, there are two main software components:
- Red Hat Virtualization Manager (RHV-M), also called simply “administrator” and / or “engine” in the documentation.In this quick start we will use thethe host engine implementation model, where RHV-M is implemented in the same hypervisors that it manages, however, RHV-M can also be implemented in a separate physical (or virtual) host, if desired.
- Red Hat Virtualization Hypervisors. There are two hypervisor options available withRed Hat Virtualization: Red Hat Enterprise Linux or Host RHV (RHV-H). Both have the same functionality, however, it is intended that RHV-H be implemented as a device, and most of the administration is done through RHV-M and / or Cockpit.
Both are available in the Red Hats Virtualization sotware page in portal .
As expected, we also need hardware to host the virtual machines.There are three things we will need:
- Compute, a.k.a. servers:
Although it is technically possible to implement a single physical server that hosts RHV-M and other virtual machines, it should only do so in non-production, testing and validation environments.This configuration is not compatible but, with the right amount of resources, it is a good way to experience and become familiar with Red Hat virtualization. Two physical hosts is the minimum recommended for Red Hat Virtualization for a number of reasons. It could be said that the most important thing is that it provides the ability to migrate live virtual machines, allowing high availability for workloads if one of the servers needs to be restarted or removed for updates, maintenance or any other reason. For most situations, three or more nodes should be used per group. This gives you the greatest flexibility and gives you a great capacity for recovery and availability. Red Hat Virtualization supports up to 400 hosts in a single cluster, without a maximum number of virtual machines, A) Yes Do everything you want to get the resources you need!As a general rule, the minimum minimum hardware requirements for a hypervisor host are a dual-core CPU, 4 GB of RAM, 25 GB of local storage, and a single 1 GbE NIC.This can only be used as proof of concept or to become familiar with Red Hat virtualization. If you are going to host production virtual machines, you will want to evaluate the resource requirements of your workloads and size the servers accordingly.For example, the configuration minimum hardware it’s 2x quad-core CPU (or more), 32GB of RAM, 25GB of local storage and 2x 10GbE NICs.The planning guide provides various recommendations for computing resources.
Red Hat Virtualization : It can operate with a single network connection. However, as expected, this limits the performance and availability of the virtual machines that are hosted.At a minimum, two physical network connections configured in a mode 1 link (active / passive failover) for a production workload are highly recommended, and more than two network connections are recommended in a mode 4 link ( link aggregation 802.3ad / LACP).Optionally, but recommended, traffic types can be logically separated by VLAN, if desired.10GbE is highly recommended, especially if only two network connections are used.A more robust implementation would have multiple redundant and isolated connections for the management, storage, migration and network traffic of virtual machines, all distributed in more than one network switch.For example, two linked links of 1GbE mode 1 for administration, two linked links of + 10GbE + mode 4 for IP storage, and two linked links mode + 10GbE + for virtual machines and migration.Ultimately, the amount of network performance you will need will depend on a large number of factors and there are almost infinite different ways to configure network resources.The planning guide describes some considerations.here Y here , but you can also work with Red Hat to help identify the optimal way to configure the network if you wish.
- Storage :
Shared storage is a requirement when you want to be able to migrate your virtual machines live betweenRed Hat VirtualizationHypervisors in your groupings.Storage domains can be provided from NFS storage, iSCSI or FCP, giving you the freedom to use what meets your needs. It is important to note that all hosts in the same center logical data They must be able to access all storage domains.Be sure to use storage that is capable of delivering the capacity (GB), IOPS, and latency required for your virtual workloads.Storage considerations in the planning guide can be found here .
Step One: Deployment of the hypervisor operating system
The first thing we must do is implement the operating system for our hypervisor hosts.The complete steps for RHV-H can be found in the documentation here , but an overview of the process is:
- Download the ISO and create a boot device.
- Connect the boot device to the physical host, turn it on and boot to the RHV-H installation disk.
- Follow the installation instructions, providing the host name, the configuration of the administration network and the local storage configuration.Once the installation begins, be sure to set a secure root password !
- Once the installation is finished, restart the server and log in (locally on the terminal, using SSH or through the Cockpit) to register the system and subscribe to the necessary repositories. If you use the terminal or SSH, this command will register and attach the host:
# register and attach the host subscription-manager register —auto-attach # enable the RHV-H repo subscription-manager repos —enable=rhel-7-server-rhvh-4-rpms
If you are using RHEL as your hypervisor’s operating system, the process is very similar (complete documentation here ).We recommend that you choose the minimum implementation option, but you can choose the one that best suits your needs.After installing the operating system, you must perform two additional steps:
- After registering the system, enable these repositories:
subscription-manager repos —disable='*' \ —enable=rhel-7-server-rpms \ —enable=rhel-7-server-rhv-4-mgmt-agent-rpms \ —enable=rhel-7-server-ansible-2-rpms
- Install the cockpit:
# install using yum yum install cockpit- ovirt- dashboard # enable and start the service enable systemctl - now cockpit.socket # open the firewall for Cockpit firewall- cmd -Permanent -add-service = cockpit
Finally, if you have a complex network environment, it may be easier to manually configure the network before continuing. This is particularly true when performing additional configuration remotely can cause the management network to disconnect, or if you need additional network configuration for storage connectivity on the host where RHV-M will be deployed in the next He passed. The documentation highlights some common practices and makes some recommendations for configuration.
Step Two: Installing Red Hat Virtualization Manager
Now that we have the hypervisor hosts ready, we can continue with the implementation of RHV-M.The self-hosted RHV-M can be implemented using CLI or Cockpit, according to your preferences.We will cover the Cockpit-based implementation below, but be sure to verify the documentation for the CLI instructions if that is your methodIf you do not want to use the self-hosted RHV-M, you can find the requirements for the physical (or virtual) machine and the implementation instructions in the documentation here .
Before you start, if you have not already done so, make sure that at least one storage domain, with at least 100 GB of free capacity, has been provisioned and can be accessed by the host. If there is a firewall between the network where RHV-M will be implemented and the hypervisor administration interfaces, make sure that The correct ports have been openedas well.
With those two checks out of the way, we can implement RHV-M.For reference, you can find the complete documentation here. If, at any time, you encounter problems, be sure to check the problem solving section of the documentation.
- Log in to the Cockpit interface on the host that you want to deploy RHV-M using the URLhttps: // FQDNorIP: 9090 . After logging in, go to Virtualization and select Hosted Engine.Choose the option to deploy the hosted engine.
- Complete the RHV-M virtual machine information on the following screen, including the fully qualified domain name (make sure the direct and reverse DNS works for the name you use), the network configuration, the root password and the amount of CPU and RAM resources you need! desire to assign.Once you are satisfied with the configuration, press the next button.
- Provide a secure default administrator user password on the next screen, along with information on where to send notifications.When finished, press next.
- This screen is a review of the information you have entered at this point.Press the “Prepare VM” button to create the RHV-M virtual machine. This process will take a few minutes, so if your coffee cup is empty, now is a good time to recharge it.
- Once the VM has been created, press next and the installer will request information about the first storage domain.Select your type of storage, complete fields, including specifying thesize of the disk image of the virtual machine, and click Next.Review the data you just provided, then click “Finish implementation.”
- The installer will complete the implementation and configuration process, most likely to take a few more minutes.Take a walk around the office to do some exercise while you wait! When all the tasks have finished, click “Close” to exit the installation wizard.
If you want to use an external authentication / authorization provider, such as an LDAP server, you can do so now by following This part of the documentation .
At this point, we want to log in to RHV-M (using internal @ admin and the password you specified earlier).Notice that the installer has created a center data and a cluster, with the hypervisor where RHV-M was already added, and the storage domain has been attached.
The last tasks we must do before continuing is to add the remaining resources and configure them.This means, among other things:
- Check thedata center Y cluster configurationTo make sure it meets your needs, Create new clusters If it is desired
- Add additional hosts to clusters , remember that you need at least two hosts in a cluster for high availability.When adding hosts, be sure to select the option for at least one additional hypervisor to host RHV-Mas well!
- Additional configuration physicalY logical networks
- Attach any additional storage domains
- Creation of policies of QoS forstorage ,VMY host network, and CPU resources
- Assigning permissions and roles to additional users
- And, last but not least, check to make sure that RHV-Mand the Hosters Are updated
Step three: Start creating virtual machines!
That’s! Red Hat Virtualization is ready for your applications!You can start with creating some templatesto quickly implement virtual machines or customize each of your virtual machines using The creation assistant .Or, automate your environment using ansible ,the REST API, or the Java/Piton/RubySDKs
Are you tired of creating virtual machines?Deliver the work to the owners of applications and virtual machines using The portal of virtual machines, which allows users to self-serve, create virtual machines, perform energy operations, create / revert / destroy snapshots, connect to the console, view the use of resources and much more.The virtual machine portal is automatically deployed together with the RHV-M administrators portal; Once your resources are ready, you must assign permissions to the resources you want users to have access to, and they’re ready to go!
If you want detailed metrics for your virtual machines, hosts, storage domains, etc., you must deploy the metric store and configure your Red Hat Virtualization display for it. For more information about the metric store, including system requirements and implementation details, seethe documentation.
Support forand disaster recovery for your virtual machines are important parts of a business continuity plan, so be sure to work with your virtual machine and application administrators to identify Virtual machines Y hosters You need to have high availability enabled and review The disaster recovery guidelines .
Last but not least, if you want to know more technical details about Red Hat Virtualization, theTechnical reference guideIt’s a great start and it is immersed in many aspects of Red Hat Virtualization, from storage and network, to virtual machine capabilities.
Reliable, reliable, scalable
Red Hat Virtualization 4.3 provides a robust platform to host your virtual machines and the applications within them .This publication has gone through the process of getting started with Red Hat Virtualization 4.3 and provides a large number of links to relevant documentation and other considerations. We love listening to your comments, concerns and problems! If you are interested in contacting us or sharing, please open a support caseor get through the customer portal discussions !