Tutorials for installing rhev-m in Linux

First, yum source configuration

Install rhev-m need to configure RHEV-M, Rhev-h, supplementary, JBoss four source, this experiment, I integrate it into a configuration. and save it to the/etc/yum.repos.d/directory. As follows:

[ROOT@RHEVM ~]# wget Http://classroom.example.com/materials/rhevm.repo-P/etc/yum.repos.d/
# Cat/etc/yum.repos.d/rhevm.repo
[Rhevmgr]
name=red Hat Enterprise Virtualization Manager for RHEL 6
baseurl=http://content.example.com/rhev3.5/x86_64/dvd/rhel-6-server-rhevm-3.5-rpms/
Enabled=1
Gpgcheck=0
[RHEVHYP6]
name=red Hat Enterprise Virtualization Hypervisor for RHEL 6
baseurl=http://content.example.com/rhev3.5/x86_64/dvd/rhel-6-server-rhevh-rpms/
Enabled=1
Gpgcheck=0
[RHEVHYP7]
name=red Hat Enterprise Virtualization Hypervisor for RHEL 7
baseurl=http://content.example.com/rhev3.5/x86_64/dvd/rhel-7-server-rhevh-rpms/
Enabled=1
Gpgcheck=0
[Rhelsupp]
name=red Hat Enterprise Linux Server 6 supplementary
Baseurl=http://content.example.com/rhel6.6/x86_64/supplementary
Enabled=1
Gpgcheck=0
[Rhevjboss]
name=red Hat Enterprise Virtualization JBoss EAP 6.2
baseurl=http://content.example.com/rhev3.5/x86_64/dvd/jb-eap-6-for-rhel-6-server-rpms/
Enabled=1
Gpgcheck=0
Upgrade the current package

[Root@rhevm ~]# Yum update-y
Second, RHEV-M package installation and configuration

1, installation of related packages

[ROOT@RHEVM ~]# yum-y Install RHEVM RHEVM-DWH
The following two packages are the related packages used by the RHEVM report pages.

2, using the Engine-setup command to configure RHEVM

This uses--generate-answer to generate an automated answer file that can be quickly installed through the RHEVM host if problems occur.

[ROOT@RHEVM ~]# Engine-setup--help
Usage:/usr/bin/engine-setup
--log=file
Write log to this file.
--config=file
Load configuration files.
--config-append=file
Load Extra configuration files or answer file.
--offline
Offline mode.
--generate-answer=file
Generate answer file.
--jboss-home=dir
Use this jboss.
[ROOT@RHEVM ~]# Engine-setup--generate-answer=answer.txt
[INFO] Stage:initializing
[INFO] Stage:environment Setup
--== PRODUCT OPTIONS ==--
Configure Engine on this host (yes, No) [Yes]://Enter
Configure Data Warehouse on this host (yes, No) [Yes]://Enter
Configure Reports on this host (Yes, No) [yes]://carriage return
Configure WebSocket Proxy on this host (yes, No) [Yes]://Enter
Do you want Setup to configure the firewall? (Yes, No) [Yes]: No
Host fully qualified DNS name of this server [rhevm.pod0.example.com]://Enter
--== DATABASE CONFIGURATION ==--
Where is the Reports database located? (Local, Remote) [Local]:
Setup can configure the local PostgreSQL server automatically for the Reports to run. This may conflict with existing applications.
Would you like the Setup to automatically configure PostgreSQL and create Reports database, or prefer to perform that manually ? (Automatic, Manual) [Automatic]:
Where is the DWH database located? (Local, Remote) [Local]:
Setup can configure the local PostgreSQL server automatically for the DWH to run. This may conflict with existing applications.
Would you like the Setup to automatically configure PostgreSQL and create DWH database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
Where is the Engine database located? (Local, Remote) [Local]:
Setup can configure the local PostgreSQL server automatically for the engine to run. This may conflict with existing applications.
Would you like the Setup to automatically configure PostgreSQL and create Engine database, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
--== ovirt ENGINE CONFIGURATION ==--
Engine Admin Password://The password I use here is redhat, so this hint is a weak password. There is also a password configuration at the back.
Confirm Engine Admin Password:
[WARNING] Password is Weak:it are based on a dictionary word
Use weak password? (Yes, No) [No]: Yes
Application Mode (Virt, Gluster, Both) [Both]:
.................. Omitted
--== SYSTEM CONFIGURATION ==--
Configure an NFS share on this server to is used as an ISO Domain? (Yes, No) [Yes]://iso domain configuration, where RHEVM is used as the ISO domain
Local ISO domain path [/var/lib/exports/iso]:/exports/rhevisos
Local ISO domain Acl-note This default would restrict access to rhevm.pod0.example.com only, for security reasons [RH Evm.pod0.example.com (rw)]:
Local ISO domain name [iso_domain]: Iso0
When the above interactive completes, will jump out the configuration confirmation information, after confirming completes, will install.
Http://rhevm.pod0.example.com:80/ovirt-engine//web Admin Interface Address
Https://rhevm.pod0.example.com:443/ovirt-engine
Please use the user ' Admin ' and password specified in order to login
The following network ports should be opened:
tcp:111
tcp:2049
tcp:32803
tcp:443
tcp:5432
tcp:6100
tcp:662
Tcp:80
tcp:875
tcp:892
udp:111
udp:32769
udp:662
udp:7410
udp:875
udp:892
An example of the required configuration for iptables can is found at:
/etc/ovirt-engine/iptables.example
--== End of SUMMARY ==--
[INFO] Starting engine service
[INFO] Restarting httpd
[INFO] Starting DWH Service
[INFO] Starting reports Service
[INFO] Generating answer file ' answer.txt '
[INFO] Stage:pre-termination
[INFO] Stage:termination
[INFO] Execution of Setup completed successfully
The contents of the Answer.txt automatic answer file are as follows:

[Root@rhevm ~]# Cat Answer.txt
# Action=setup
[Environment:default]
Ovesetup_dialog/confirmsettings=bool:true
Ovesetup_config/applicationmode=str:both
Ovesetup_config/remoteenginesetupstyle=none:none
Ovesetup_config/adminpassword=str:redhat
Ovesetup_config/storageislocal=bool:false
Ovesetup_config/firewallmanager=none:none
Ovesetup_config/remoteenginehostrootpassword=none:none
Ovesetup_config/updatefirewall=bool:false
Ovesetup_config/remoteenginehostsshport=none:none
Ovesetup_config/fqdn=str:rhevm.pod0.example.com
Ovesetup_config/storagetype=none:none
Osetup_rpmdistro/requirerollback=none:none
Osetup_rpmdistro/enableupgrade=none:none
Ovesetup_db/database=str:engine
Ovesetup_db/fixdbviolations=none:none
Ovesetup_db/secured=bool:false
Ovesetup_db/host=str:localhost
Ovesetup_db/user=str:engine
Ovesetup_db/securedhostvalidation=bool:false
ovesetup_db/port=int:5432
Ovesetup_engine_core/enable=bool:true
Ovesetup_core/enginestop=none:none
Ovesetup_system/memcheckenabled=bool:true
Ovesetup_system/nfsconfigenabled=bool:true
Ovesetup_pki/organization=str:pod0.example.com
Ovesetup_config/isodomainmountpoint=str:/exports/rhevisos
ovesetup_config/engineheapmax=str:1024m
Ovesetup_config/isodomainname=str:iso0
Ovesetup_config/isodomainacl=str:rhevm.pod0.example.com (rw)
ovesetup_config/engineheapmin=str:1024m
Ovesetup_aio/configure=none:none
Ovesetup_aio/storagedomainname=none:none
Ovesetup_aio/storagedomaindir=none:none
Ovesetup_provisioning/postgresprovisioningenabled=bool:true
Ovesetup_apache/configurerootredirection=bool:true
Ovesetup_apache/configuressl=bool:true
Ovesetup_dwh_core/enable=bool:true
Ovesetup_dwh_db/database=str:ovirt_engine_history
Ovesetup_dwh_db/secured=bool:false
Ovesetup_dwh_db/host=str:localhost
Ovesetup_dwh_db/disconnectexistingdwh=none:none
Ovesetup_dwh_db/restorebackuplate=bool:true
Ovesetup_dwh_db/user=str:ovirt_engine_history
Ovesetup_dwh_db/securedhostvalidation=bool:false
Ovesetup_dwh_db/performbackup=none:none
Ovesetup_dwh_db/password=str:tfnnxg7k0vvjb5j8uaqcyv
ovesetup_dwh_db/port=int:5432
Ovesetup_dwh_provisioning/postgresprovisioningenabled=bool:true
Ovesetup_db/password=str:pbyuilmt5nj41rey2qcdjb
Ovesetup_reports_core/enable=bool:true
ovesetup_reports_config/heapmin=str:1024m
Ovesetup_reports_config/adminpassword=str:redhat
ovesetup_reports_config/heapmax=str:1024m
Ovesetup_reports_db/database=str:ovirt_engine_reports
Ovesetup_reports_db/secured=bool:false
Ovesetup_reports_db/host=str:localhost
Ovesetup_reports_db/user=str:ovirt_engine_reports
Ovesetup_reports_db/securedhostvalidation=bool:false
Ovesetup_reports_db/password=str:mqjgjxh1n6vk781f4l3nhs
ovesetup_reports_db/port=int:5432
Ovesetup_reports_provisioning/postgresprovisioningenabled=bool:true
Ovesetup_engine_config/fqdn=str:rhevm.pod0.example.com
Ovesetup_rhevm_support/redhatsupportproxyport=none:none
Ovesetup_rhevm_support/redhatsupportproxy=none:none
Ovesetup_rhevm_support/redhatsupportproxyuser=none:none
Ovesetup_rhevm_support/configureredhatsupportplugin=bool:false
Ovesetup_rhevm_support/redhatsupportproxypassword=none:none
Ovesetup_rhevm_support/redhatsupportproxyenabled=bool:false
Ovesetup_rhevm_dialog/confirmupgrade=bool:true
Ovesetup_config/websocketproxyconfig=bool:true
3. View the default ISO domain file

[Root@rhevm ~]# showmount-e localhost
Export list for localhost:
/exports/rhevisos *
[ROOT@RHEVM ~]# tree/exports/rhevisos/
/exports/rhevisos/
└──8e63ca2a-b4ce-4506-a56c-aaede9fcccd2
├──dom_md
│├──ids
│├──inbox
│├──leases
│├──metadata
│└──outbox
└──images
└──11111111-1111-1111-1111-111111111111
├──rhev-tools-setup.iso
├──virtio-win_amd64.vfd
├──virtio-win.iso
└──virtio-win_x86.vfd
4 Directories, 9 files
Several files under the ISO domain images are used to install Windows, and note that the/exports/rhevisos directory's owner and group are VDSM:KVM, with a user ID and group ID of 36. These documents belong to the following two packages:

[ROOT@RHEVM ~]# Rpm-qf/usr/share/rhev-guest-tools-iso/rhev-tools-setup.iso
Rhev-guest-tools-iso-3.5-9.el6ev.noarch
[ROOT@RHEVM ~]# Rpm-qf/usr/share/virtio-win/virtio-win.iso
Virtio-win-1.7.2-2.el6.noarch
4, RHEVM Web Landing

After the installation configuration is complete, the RHEVM Web interface is as follows:

The rhev3.5 version of the Web interface is in support of Chinese, but because rh318 's official textbooks do not provide Chinese version, I also recognize the choice of English interface.

Third, rhev-m personalized configuration related

1, check version upgrade

[ROOT@RHEVM ~]# Engine-upgrade-check
2. Configure external authentication

At this time, the use of external IPA certification, configuration completed after the need to restart the Ovirt-engine service

[ROOT@RHEVM ~]# engine-manage-domains add--domain=example.com--user=rhevadmin--provider=ipa
[ROOT@RHEVM ~]# engine-manage-domains List
Domain:example.com
User name:rhevadmin@example.com
Manage Domains completed successfully
[ROOT@RHEVM ~]#/etc/init.d/ovirt-engine Restart
Using the internal Admin user login, click on the Configure configuration entry in the upper right corner, select System permissions and click Add to add the corresponding user, as follows:

3. Reset Password

The password of the internal authenticated Admin user can be reset through the Engine-config command, as follows:

[ROOT@RHEVM ~]# engine-config-a|grep-i AdminPassword//-a parameter is to view all configuration items
Localadminpassword:set version:general
Adminpassword:set version:general
[ROOT@RHEVM ~]# engine-config-s adminpassword=interactive//-s parameter is the value that sets the related option
Please enter a password:
Please reenter password:
[ROOT@RHEVM ~]#/etc/init.d/ovirt-engine Restart
Stopping ovirt Engine: [OK]
Starting ovirt Engine: [OK]
4, Time related item setting

Where the session option is a web interface more than the operation on the automatic when the unit is minutes. Using the-a selection and-G selection are

[ROOT@RHEVM ~]# engine-config-a|grep-i session
Usersessiontimeoutinterval:30 version:general
[ROOT@RHEVM ~]# engine-config-g usersessiontimeoutinterval//When using the-G option, the following parameter section must use the full
Usersessiontimeoutinterval:30 version:general
[ROOT@RHEVM ~]# engine-config-a|grep-i Serverreboot
serverreboottimeout:300 version:general
Serverreboottimeout time is the time when the Ovirt-engine service restarts. For security considerations and to avoid waiting too long, we can set the session time to 2 minutes and set the serverreboottimeout time to 90 seconds:

[ROOT@RHEVM ~]# engine-config-s usersessiontimeoutinterval=2
[ROOT@RHEVM ~]# engine-config-s serverreboottimeout=90
[ROOT@RHEVM ~]#/etc/init.d/ovirt-engine Restart
5. Log Collection

The Engine-log-collector command allows you to collect related logs from a group or data center to facilitate problem analysis (the actual call is also the Sosreport Directive)

engine-log-collector [Options] list [all,clusters,datacenters]
engine-log-collector [Options] Collect
If you use list to view related information:

[ROOT@RHEVM ~]# engine-log-collector List
This command would collect system configuration and diagnostic
Information from this system.
The generated archive may contain data considered sensitive and its
Content should be reviewed by the originating organization before
Being passed to the third party.
No changes is made to system configuration.
Please provide the REST API password for the admin@internal ovirt Engine user (Ctrl+d to skip)://This will allow you to enter your password
Host list (Datacenter=none, Cluster=none, Host=none):
Data Center | Cluster | HOSTNAME/IP Address
Center0 | Cluster0 | 172.25.0.10
Note: The engine command needs to enter a password when performing a rest API call, which can be returned directly without having to enter a password when executing the related command, after being configured in the relevant configuration file in the/etc/ovirt-engine/directory.

Iv. unloading and reloading of rhev-m

1, rhev-m cleaning and unloading

# Engine-cleanup
# yum Remove rhevm* vdsm-bootstrap *jboss* postgresql-server
# echo "" >/etc/exports
# Service NFS Restart
2. Re-installation and recovery

Reinstall requires the installation of the relevant software package, and then through the Engine-config answer.txt file between the Yum before the installation configuration. After the installation is complete, use Postgresql-server database backup Recovery--all RHEV-M data centers, clusters, networks, hosts, virtual machines, external authentication, etc. are stored in the database.

# Engine-setup--config-append=answer.txt
Rhev-m in the use of physical machine, it is best to need two between the HA or the database to do a separate one. Of course rhev-m can also be a virtual machine within the rhev-h, in which a rhev-h physical machine clapping, you can through the Rhev of the HA mechanism drift to other hosts, continue to provide services.