I. Configuration of RHEV-H
Rhev-h the installation process is nothing to do, it is the default next step. When the installation is complete, using the default Admin user login will appear as follows GUI interface-----Log on using the root account will enter the interface similar to the Linux terminal landing.
1, IP address configuration
Host name can be configured separately, if the intranet has DNS, configuration good DNS and IP address, can also automatically resolve the host name. After the IP address configuration is complete, it will appear as read-only, and after the IP configuration is complete, you can also test and RHEV-M network connectivity through the following Ping tool. More than a block of cards, can be configured in the Rhev-m management interface. Here also need to note that once the IP address has been modified, through the use of Root/password login, modified/ETC/SYSCONFIG/NETWORK-SCRIPTS/IFCFG-ETHX after the restart of the host after the restart IP is still old. This compact version of the Rhev has done a lot of security tuning, the host system is quite secure.
Here the main settings are remote admin account SSH login settings, here Select and set the password, you can through remote SSH connection into the current GUI interface configuration.
Several of the above SNMP, logging, kdump, Remote Storage are used as remote monitoring and physical host failure analysis. This is based on the actual need to open and configure.
Performance, Redhat preset several use scenarios, for different scenes Red Hat itself has made corresponding preferences. Here we are using it as virtualization, so choose the default virtual-host here. The Virtual-guest option can be easier to mix, which is typically set for virtual machines running within a physical machine.
This tuned-related instruction, introduced after Rhel 6.3, can be viewed as follows:
# TUNED-ADM List
Available Profiles:
-Virtual-guest
-Desktop-powersave
-Server-powersave
-Virtual-host
-Throughput-performance
-Enterprise-storage
-Spindown-disk
-Default
4, access to Rhev-m
Here input rhev-m corresponding host name (need intranet has DNS can resolve to this host) or host IP. The password set here is the password for the remote SSH root user, which is to be distinguished from the Admin user settings above. After configuring each item, remember save. Another need to pay attention to the access rhev-m is required "Two-way authentication", this point to rhev-m host, but also need to be confirmed on the rhev-m approve.
There is also an option to specify the path to the installed virtual machine image, which will be downloaded to the specified store. The method is also used by the authorities to install the rhev-h directly, with the built-in RHEV-M platform (that is, Rhev-m is a virtual machine in the data center). The good thing is that you can leave a physical machine, but also to avoid the outside to do ha, through the Rhev ha can achieve rhev-m virtual machine high availability.
The Rhev-m side confirmation interface is as follows:
When you join the appropriate data centers and clusters, be aware that when you create a cluster, you specify the CPU type of the host within that cluster. The actual physical CPU type of the rhev-h should be consistent with the setting of the cluster here, otherwise there will be an error. And the same cluster of physical machine CPU model to be the same, or internal can not migrate, so the different types, when added to the error.
Approve confirmation will be installed on the rhev-h host VDSM plug-ins, you can use the root account SSH login, and through the tail-f/var/log/message to view specific log information.
Second, the RHEV-H host upgrade
The corresponding host needs to be modified to maintenance mode before upgrading
View by Yum Source:
[Root@rhevm ~]# Yum List|grep hyperv
Rhev-hypervisor7.noarch 7.1-20150420.0.el7ev RHEVHYP7
hyperv-daemons.x86_64 0-0.15.20130826git.el6 Rhel-dvd
Hyperv-daemons-license.noarch 0-0.15.20130826git.el6 Rhel-dvd
hypervfcopyd.x86_64 0-0.15.20130826git.el6 Rhel-dvd
hypervkvpd.x86_64 0-0.15.20130826git.el6 Rhel-dvd
hypervvssd.x86_64 0-0.15.20130826git.el6 Rhel-dvd
Rhev-hypervisor-tools.noarch 2.3.0-15.el6_3.18 RHEVHYP6
Rhev-hypervisor6.noarch 6.6-20150421.0.el6ev RHEVHYP6
Rhev-hypervisor6-tools.noarch 6.3-20121012.0.el6_3 RHEVHYP6
[ROOT@RHEVM ~]# yum-y Install Rhev-hypervisor7
Install the latest RHEV-HYPERVISOR7, after the upgrade completes, will install the most recent rhev-h ISO image file on the RHEVM host, will be written to the corresponding version through the upgrade upgrade interface of the above image, the following is the version before and after the upgrade:
SPM is the abbreviation of Storage pool manager, in a data in the mind only a host as the SPM, all host data storage access through the host management. Once the physical host has an exception, a host is returned from the data center as a SPM host.
