Академический Документы
Профессиональный Документы
Культура Документы
2 Installation Guide
A guide to installing Red Hat Enterprise Virtualization for Servers
Installation Guide
Red Hat Enterprise Virtualization for Servers 2.2 Installation Guide A guide to installing Red Hat Enterprise Virtualization for Servers Edition 2
Author Author Author Copyright 2010 Red Hat, Inc Copyright 2010 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons AttributionShare Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the United States and other countries. Java is a registered trademark of Oracle and/or its affiliates. XFS is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. All other trademarks are the property of their respective owners. 1801 Varsity Drive Raleigh, NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 Susan Burgess Chris Curran David Jorm sburgess@redhat.com ccurran@redhat.com djorm@redhat.com
This document describes the installation of Red Hat Enterprise Virtualization for Servers.
Preface v 1. About this Guide ............................................................................................................. v 1.1. The Red Hat Enterprise Virtualization Documentation Suite ..................................... v 1.2. Audience .............................................................................................................. v 2. Document Conventions ................................................................................................... v 2.1. Typographic Conventions ..................................................................................... vi 2.2. Pull-quote Conventions ........................................................................................ vii 2.3. Notes and Warnings ........................................................................................... viii 3. We Need Feedback! ..................................................................................................... viii 1. Overview 1.1. System architecture ...................................................................................................... 1.2. How the management system works ............................................................................. 1.2.1. About the servers .............................................................................................. 1.2.2. About the virtual machines ................................................................................. 1.3. About the installation process ....................................................................................... 2. System Requirements 2.1. Prerequisites ................................................................................................................ 2.2. Hardware requirements ................................................................................................ 2.3. Software requirements .................................................................................................. 1 1 2 2 2 2 5 5 5 6
3. Installing the Red Hat Enterprise Virtualization Manager 7 3.1. Installing the Operating System ..................................................................................... 7 3.1.1. Configure DNS server ........................................................................................ 7 3.1.2. Connect to domain controller ............................................................................. 7 3.1.3. Installing Web Server (IIS) ................................................................................. 8 3.1.4. Add components .............................................................................................. 10 3.1.5. Firewall configuration ....................................................................................... 12 3.2. Installing Red Hat Enterprise Virtualization Manager ..................................................... 13 3.2.1. Run the installation wizard ............................................................................... 13 3.2.2. Accept license agreement ................................................................................ 14 3.2.3. Select features ................................................................................................ 14 3.2.4. Setup the database ......................................................................................... 16 3.2.5. Choose installation location .............................................................................. 16 3.2.6. Select website ................................................................................................. 17 3.2.7. Select Red Hat Enterprise Virtualization Manager domain and user ..................... 18 3.2.8. Enter certification details .................................................................................. 19 3.2.9. Enter net console port ..................................................................................... 20 3.2.10. Confirm settings ............................................................................................. 21 3.2.11. Login to the administrator portal ...................................................................... 24 4. Installing the Red Hat Enterprise Virtualization Hypervisor 4.1. Preparing an installation disc ...................................................................................... 4.2. Confirm hardware virtualization support ....................................................................... 4.3. Boot the Hypervisor .................................................................................................... 4.4. The Red Hat Enterprise Virtualization Hypervisor Configuration Menu ............................ 4.5. Remove existing Red Hat Enterprise Virtualization Hypervisor installations ..................... 4.6. Partitioning the disk .................................................................................................... 4.7. Set the administrator password ................................................................................... 4.8. Set the hostname ....................................................................................................... 4.9. Setup Networking ....................................................................................................... 4.10. Register to RHN ....................................................................................................... 4.11. Connect to the Red Hat Enterprise Virtualization Manager ........................................... 4.12. View logs ................................................................................................................. 4.13. Installation ................................................................................................................ 27 27 28 29 29 30 31 33 34 35 37 38 39 40 iii
Installation Guide 4.14. Using the hypervisor ................................................................................................. 40 5. Using Red Hat Enterprise Linux Hosts 5.1. Adding Red Hat Enterprise Linux Hosts ....................................................................... 5.1.1. Preparing Red Hat Enterprise Linux Hosts ........................................................ 5.1.2. To Add a Host ................................................................................................. 5.2. Activating a Host ........................................................................................................ 6. Setting Up Storage 6.1. Adding NFS Storage .................................................................................................. 6.2. Adding iSCSI Storage ................................................................................................. 6.3. Adding FCP Storage .................................................................................................. 7. Configuring the System A. Planning the System Architecture 43 43 43 47 51 53 53 55 61 65 67
B. Using Active Directory 69 B.1. Installing Active Directory ........................................................................................... 69 B.2. Creating the Red Hat Enterprise Virtualization admin user in Active Directory ................. 69 C. Remote Microsoft SQL Server configuration C.1. Enable Microsoft Distributed Transaction Coordinator (MSDTC) .............................. C.2. Modify Surface Area configuration .............................................................................. C.3. Modify firewall configuration ........................................................................................ D. Additional Reading E. Revision History 71 71 72 73 77 79
iv
Preface
The Red Hat Enterprise Virtualization platform is a richly featured virtualization management solution providing fully integrated management across virtual machines. It is based on the leading open source virtualization platform and provides superior technical capabilities. The platform offers scalability in the management of large numbers of virtual machines.
1.2. Audience
This documentation suite is intended for system administrators installing a virtual environment based on the specifications provided to them by their solution architect. An advanced level of system administration, preferably including familiarity with virtual machine data center operations, is assumed. This document is not intended for beginners.
2. Document Conventions
This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information. v
Preface In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.
1
https://fedorahosted.org/liberation-fonts/
vi
Pull-quote Conventions click this highlighted character to place it in the Text to copy field and then click the Copy button. Now switch back to your document and choose Edit Paste from the gedit menu bar. The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context. Mono-spaced Bold Italic or Proportional Bold Italic Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example: To connect to a remote machine using ssh, type ssh username@domain.name at a shell prompt. If the remote machine is example.com and your username on that machine is john, type ssh john@example.com. The mount -o remount file-system command remounts the named file system. For example, to remount the /home file system, the command is mount -o remount /home. To see the version of a currently installed package, use the rpm -q package command. It will return a result as follows: package-version-release. Note the words in bold italics above username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system. Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example: Publican is a DocBook publishing system.
Source-code listings are also set in mono-spaced roman but add syntax highlighting as follows:
package org.jboss.book.jca.ex1; import javax.naming.InitialContext; public class ExClient { public static void main(String args[]) throws Exception { InitialContext iniCtx = new InitialContext(); Object ref = iniCtx.lookup("EchoBean"); EchoHome home = (EchoHome) ref; Echo echo = home.create();
vii
Preface
Note
Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
Important
Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration.
Warning
Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
3. We Need Feedback!
If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report by email to the author of the manual, Susan Burgess (sburgess@redhat.com ). When submitting a bug report, be sure to mention the manual's identifier: Server_Install_Guide. If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, include the section number and some of the surrounding text so we can find it easily.
viii
Chapter 1.
Overview
This document describes how to install the Red Hat Enterprise Virtualization platform for the first time. It contains information on hardware and software prerequisites, installation procedures and initial configuration.
Chapter 1. Overview
About the installation process 3. Install the Red Hat Enterprise Virtualization Hypervisors and Red Hat Enterprise Linux hosts according to Chapter 4, Installing the Red Hat Enterprise Virtualization Hypervisor and Chapter 5, Using Red Hat Enterprise Linux Hosts. 4. Configure and attach storage, according to Chapter 6, Setting Up Storage. 5. Configure the Red Hat Enterprise Virtualization Manager for use, according to Chapter 7, Configuring the System.
Chapter 2.
System Requirements
This section describes the basic hardware and software prerequisites required for installing the Red Hat Enterprise Virtualization platform. It is assumed that the requirements for your specific implementation of the Red Hat Enterprise Virtualization system have been defined by your solution architect. Therefore, the solution planning stage is not covered by this document. However, be aware that the following must be considered when designing the system: total number of virtual machines to be used, storage requirements, network capacity, total CPU and memory requirements. Additional notes regarding system planning are provided in Appendix A, Planning the System Architecture. Ensure that the listed requirements are ready before attempting installation.
2.1. Prerequisites
Latest Red Hat Enterprise Virtualization Manager Release Notes. A client with Windows XP and .NET Framework 3.1 with Service Pack 1, or Windows 7, is required to access the web-based administration portal. The client must be running Internet Explorer 7 or 8. To connect to virtual machines with SPICE via the Red Hat Enterprise Virtualization administration portal, a SPICE browser plugin is used. The SPICE plugin for Internet Explorer is only compatible with 32-bit editions of Internet Explorer. When using a 64-bit Windows operating system, you must install a 32-bit edition of Internet Explorer to use the SPICE plugin. You must also make a global registry setting change to allow the WPF application to run as a 32-bit process. The process for 1 making this change is described in Microsoft kbase article 974396
Chapter 2. System Requirements Minimum 20 GB of local disk space. At least one network controller with a minimum bandwidth of 1 Gbps. Server to provide storage for virtual machine and ISO images.
Chapter 3.
Note
Only the English locale is supported when installing the Red Hat Enterprise Virtualization Manager on Windows Server 2008.
Chapter 3. Installing the Red Hat Enterprise Virtualization Manager 6. When prompted for the credentials of a user that can join machines to the domain, enter the Red Hat Enterprise Virtualization administrator user credentials created as per Section B.2, Creating the Red Hat Enterprise Virtualization admin user in Active Directory. Then click Ok. If successful, a message will be displayed confirming that the computer has been joined to the domain. Click Ok to continue. If a confirmation message was not received, this is likely to be due to one of the following: Domain specified is incorrect. User credentials specified are incorrect. User credentials provided do not have the necessary permissions to join a machine to the domain. Check your Active Directory configuration and credentials and try again. 8. Reboot the machine to complete the process.
7.
Figure 3.1. Roles Summary If Web Server (IIS) is listed then it is already installed and no further action is required. If Web Server (IIS) is not listed then it still needs to be installed. From Server Manager, click on Add Roles.
Installing Web Server (IIS) a. From the Add Roles Wizard, select the Web Server (IIS) checkbox and click Next.
Chapter 3. Installing the Red Hat Enterprise Virtualization Manager b. Enable any additional Web Server (IIS) Role Services required and click Next.
Figure 3.3. Web Server (IIS) Role Services c. Click Install to install the selected components.
10
Add components b. Verify that .NET Framework 3.5.1 is installed by going to Start > Control Panel > Turn Windows features on or off and checking that it is listed, as in Figure 3.4, Features Summary.
Figure 3.4. Features Summary 2. 3. From Server Manager, click on Add Features. From the Add Features Wizard, select the .NET Framework 3.5.1 Features checkbox and click Next.
Figure 3.5. Windows component wizard 4. 5. Click Install to install the selected components. Install Windows PowerShell 2.0
11
Chapter 3. Installing the Red Hat Enterprise Virtualization Manager 6. Verify PowerShell is installed successfully by going to Start > All Programs > Accessories > Windows PowerShell.
for /D %p in (80,443,25285,54321,22,8006,8007,8008,8009) do (netsh firewall add portopening protocol = TCP port = %p name = RHEVM%p)
4.
Type the below command and press Enter. This will allow the manager to respond to ICMP ping requests.
12
13
Figure 3.7. End User License Agreement To continue with the installation you must accept the terms of the License Agreement by clicking Yes. The wizard will proceed to the next step. If you do not agree to the License Agreement, click No. The installation process will be canceled.
Select features Red Hat Enterprise Virtualization Manager Scripting Library: PowerShell scripting library and documentation. Red Hat Enterprise Virtualization Manager Net Console: remote console service used for logging purposes.
Figure 3.8. Select components 1. Select the features to be installed. If a checkbox is gray, this indicates that the feature is required for installation.
2.
15
Figure 3.9. Red Hat Enterprise Virtualization Manager Database 2. Set the password for the database sa user. To change the default password for the SQLExpress sa user: Enter the preferred administrator password in the Password and Confirm Password fields.
Note
It is recommended that the default installation path is used.
16
Select website Procedure 3.5. Change the installation location 1. Click Browse... and select the required destination folder.
Figure 3.10. Set installation folder 2. Click Next to accept the installation location.
17
Chapter 3. Installing the Red Hat Enterprise Virtualization Manager 1. Either select the desired website from the drop-down menu or create a new site.
Figure 3.11. Select or create website To use the default website, keep the default values. To set a custom name: a. b. c. d. 2. Click Create a new site. Enter the desired site name in the New site name field. Enter the site port in the Port field. Leave the Force SSL checkbox selected.
Once the default or custom selection has been made, click Next to continue.
3.2.7. Select Red Hat Enterprise Virtualization Manager domain and user
Provide the Active Directory domain and user details to be used by Red Hat Enterprise Virtualization Manager. The User details section requires the Active Directory user details that were setup according to Section B.2, Creating the Red Hat Enterprise Virtualization admin user in Active Directory. These credentials will be used on the first run of template-created servers to associate users and groups with specific virtual servers within the system. Therefore, this user requires permissions to create computer objects within Active Directory. 18
Figure 3.12. Enter domain and user details The Red Hat Enterprise Virtualization Manager filters users that do not have a User Principal Name (UPN, e.g. user@domain) configured in Active Directory. Therefore, ensure that the user is correctly configured before proceeding. Domain details 1. From the Select Local or Domain drop-down menu, choose the Domain option. 2. Enter the domain name to be used in the Domain Name field. User details 1. Enter the Active Directory username in the User Name field. 2. Enter the Active Directory password in the Password field. Once it has been confirmed that the domain and user details have been correctly entered, click Next to continue.
19
Note
It is recommended that the fully qualified computer name is resolvable. If not, select the Do not validate fully qualified computer name checkbox. This option is useful during testing or when the Domain Name Server is not configured.
Figure 3.13. Certification Details 3. Confirm that the information entered is correct and click Next to proceed.
20
21
Chapter 3. Installing the Red Hat Enterprise Virtualization Manager 2. Once all details are correct, click Next to continue.
Figure 3.15. Confirm settings 3. The installation wizard will begin configuring the installation. If there are any running applications using files that require updating, you are notified to close these before proceeding. Once this is done, click Retry to continue.
22
Confirm settings
Figure 3.16. Close applications 4. The Red Hat Enterprise Virtualization Manager installation will continue and may take some time to complete. When finished, the installation wizard will confirm that it has completed the
23
Chapter 3. Installing the Red Hat Enterprise Virtualization Manager installation. The fingerprint for the Certificate Authority certificate created by the installation is also displayed. Save this string for future use.
Figure 3.17. Installshield Wizard Complete 5. Result: Installation has successfully been completed. Click Finish to exit.
1.
Open the administrator portal login screen by clicking on Start > All Programs > Red Hat > Red Hat Enterprise Virtualization Manager > RHEVManager. Alternatively, if the RHEVManager shortcut is not present, open a web browser and navigate to http:// localhost/RHEVmanager.
24
Login to the administrator portal 2. If you are connecting to the administrator portal for the first time, you will be prompted to install the certificate.
Figure 3.18. Certificate Installation Follow the prompts to install a certificate. Once complete, reload the administrator portal. The portal login screen will be displayed.
Figure 3.19. Administrator portal login 3. Enter the Red Hat Enterprise Virtualization Manager administrator credentials, as configured in Section 3.2.7, Select Red Hat Enterprise Virtualization Manager domain and user. Please wait while the application information is downloaded.
25
Chapter 3. Installing the Red Hat Enterprise Virtualization Manager 4. Once the installation process is complete, you will be presented with the Red Hat Enterprise Virtualization Manager interface.
26
Chapter 4.
Automated Installations
Red Hat Enterprise Virtualization Hypervisor installations can be automated or conducted without interaction. This type of installation is only recommended for advanced users. Refer to the Red Hat Enterprise Virtualization Hypervisor Deployment Guide for more information.
Note
Access to a working system with an optical recorder drive and optical disk recording software is required for creation of the installation disc. The instructions in this guide use the cdrecord package, which is installed by default on Red Hat Enterprise Linux.
Procedure 4.1. Confirm recording software is present on Red Hat Enterprise Linux 1. To verify that the cdrecord package is present on the system, perform a query using the rpm package manager by entering the command:
# rpm -q cdrecord
27
Chapter 4. Installing the Red Hat Enterprise Virtualization Hypervisor 2. If the cdrecord package is installed, the package name will be displayed in the system output. If notification is displayed that the cdrecord package is not installed, it can be installed using the command:
# yum install cdrecord
Once the cdrecord package is verified as being present, the installation media can be created. Procedure 4.2. Create an installation disc 1. Enable the Red Hat Enterprise Virtualization Hypervisor 5 channel on RHN. 2. Install the Red Hat Enterprise Virtualization Hypervisor ISO image package.
# yum -y install rhev-hypervisor
Alternatively, download the Red Hat Enterprise Virtualization Hypervisor CD-ROM image from 1 Red Hat Network . 3. 4. Insert a blank CD-ROM or DVD into your CD/DVD recorder drive. Record the ISO file to disc using the cdrecord command in the format:
# cdrecord dev=device [iso file path]
For example, if using the first CD-RW device (/dev/cdrw) available and the Hypervisor ISO file located at /usr/share/rhev-hypervisor/rhev-hypervisor.iso the command used is:
# cdrecord dev=/dev/cdrw /usr/share/rhev-hypervisor/rhev-hypervisor.iso
5.
If an error occurs during the recording process, try inserting a new writable disc and repeat the previous command. Once the record process has completed without any errors occurring, the installation media is ready to use. The Red Hat Enterprise Virtualization Hypervisor uses the isomd5sum to verify the integrity of the installation media each time the Hypervisor is booted. If media errors are reported during the boot sequence, a new installation disc will need to be created.
28
Boot the Hypervisor 4. To verify that your CPU contains the virtualization extensions, enter the command:
# grep -E 'svm|vmx' /proc/cpuinfo
The processor is hardware virtualization capable if output is displayed. 5. To verify that the virtualization extensions are enabled in the BIOS, check that the kvm modules are loaded in the kernel by entering:
# lsmod | grep kvm
If the output includes kvm_intel or kvm_amd then the kvm hardware virtualization modules are loaded and the system meets requirements.
Note
If hardware virtualization support is not present and enabled, it is not possible to install the Red Hat Enterprise Virtualization Hypervisor.
29
Configuration menu options Configure storage partitions: prepares the local storage device for installation. Refer to Section 4.6, Partitioning the disk. Configure authentication: sets the root password for administration and SSH access. Refer to Section 4.7, Set the administrator password. Set the hostname: sets the hostname manually instead of using DHCP. Refer to Section 4.8, Set the hostname. Networking setup: configures network settings and services including: DHCP, IPv4, NTP and DNS. Refer to Section 4.9, Setup Networking. Register Host to RHN: registers the host to the Red Hat Network (RHN). Refer to Section 4.10, Register to RHN. Configure the host for RHEV: enter IP address of the Red Hat Enterprise Virtualization Manager server. Refer to Section 4.11, Connect to the Red Hat Enterprise Virtualization Manager. View logs: view log files to debug the installation procedure. Refer to Section 4.12, View logs. Install locally and reboot: install the Hypervisor to the storage device and reboot. Refer to Section 4.13, Installation. Support Menu: contains options for continuing stateless boot and exiting to a shell prompt. This menu is not supported except when working with Red Hat support.
For further information on removing previous versions of the Red Hat Enterprise Virtualization Hypervisor, refer to the Red Hat Enterprise Virtualization Hypervisor Deployment Guide. 30
Warning
Running this procedure will destroy all data on the local storage device selected with the storage_init parameter.
Procedure 4.3. The Storage Configuration menu 1. Select the Configure storage partitions option from the main menu to open the Configure storage partitions menu. Example 4.2. The Configure storage partitions menu
Configure storage partitions 1) Configure 2) Review 3) Commit configuration 4) Return to the Hypervisor Configuration Menu Choose an option:
2.
Choose partition sizes Select Configure. You are prompted to set the size of boot, swap, root, config, logging and data partitions. The value is accepted in megabytes (MB). Setting a size value of -1 sets the partition to take up all remaining disk space. Note that this can only be used with the Data partition. Pressing Enter without any value sets the partition to the default size.
Important
Do not append units onto the end of the partition size values. Using MB or similar unit on the end of a value may have adverse effects. For example, use the value 5 instead of 5MB.
a.
The boot partition contains the boot loader, kernel and initramfs. The default and only supported size for the boot partition is 50MB.
b.
The swap partition is used for swapping underused memory to the hard drive to speed up memory performance. The default size of the swap partition is calculated from amount of RAM and overcommit ratio (default is 0.5). Red Hat Enterprise Virtualization Hypervisors must have a swap partition and the swap partition cannot be disabled by setting its size to 0. The minimum size for the swap partition is 5MB. Red Hat Knowledgebase has an article on determining the size of the swap partition. 31
2
Chapter 4. Installing the Red Hat Enterprise Virtualization Hypervisor Use the formula from the Red Hat Knowledgebase and add storage for the overcommit ratio (RAM multiplied by the overcommit ratio).
Recommended swap + (RAM * overcommit) = swap partition size
Pressing Enter during the installation sequence sets a recommended value for the swap partition. c. The root partition contains the core files for the Hypervisor and the LiveOS directory from the installation media. The default total size of the root file system partitions is 512MB. That is broken up into 256MB for one root partition and an additional 256MB for a backup root partition. The default and only supported size for the root partition is 256MB. The size entered is per partition, with the total size of the root partitions double what is entered. d. The config partition stores configuration files for the Hypervisor. The default and minimum size for the configuration partition is 5MB. e. The logging partition stores all logs for the Hypervisor. The default size for the logging partition is 2048MB, the minimum size is 256MB. f. The data partition stores core files and kdump files and acts as temporary storage for ISO files. The default size of the data partition is the remaining available disk space (labeled as -1). When ISO files are uploaded using the ISO Uploader tool, they are temporarily stored on the data partition of a Red Hat Enterprise Virtualization Hypervisor host, before being moved to the shared ISO Library. The data partition must include sufficient space to store these ISO files, which can be over 4GB in size for modern operating systems. The data partition must be large enough to hold core files for kvm. Core files depend on the RAM size for the guests. The data partition must also be large enough to store kernel dump files, also known as kdumps. A kdump file is usually the same size the host's system RAM. The data partition also stores the Red Hat Enterprise Virtualization Hypervisor ISO file for Red Hat Enterprise Virtualization Hypervisor upgrades. The data partition should be at least 1.5x as large as the RAM on the host system plus an additional 512MB in size. The minimum size is 256MB. 3. Review Select the Review menu option. The review menu output similar to the screenshot below:
The local disk will be repartitioned as follows: ================================================ Physical Hard Disk: /dev/hda (1024 MB) Disk Identifier: storage_serial_be_a8bb_1a222ce09dc6 Boot partition size: 50 MB Swap partition size: 5 MB Installation partition size: 256 * 2 MB Configuration partition size: 5 MB Logging partition size: 5 MB Data partition size: 447 MB
32
Set the administrator password 4. 5. Select Commit configuration to accept the partitions. The following warning displays:
!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!! !!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!! !!WARNING!! !!WARNING!! !!WARNING!! !!WARNING!! !!WARNING!! If you proceed, all data on your selected storage !!WARNING!! !!WARNING!! device will be destroyed and your hard disk !!WARNING!! !!WARNING!! will be irreversibly reconfigured. !!WARNING!! !!WARNING!! !!WARNING!! !!WARNING!! !!WARNING!! !!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!! !!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!!WARNING!! Do you wish to proceed([Y]es or [N]o)?
6.
Partitions are created and file systems are formatted. Once complete, the main menu reappears.
2. 3.
Enter the preferred password. You will be prompted to retype the password. 4.
Changing password for user root. passwd: all authentication tokens updated successfully. storing to /config : /etc/shadow File persisted
This message indicates that the password has been set and saved to local storage.
33
Press y to enable SSH password authentication. 3. If successful, the following message is displayed:
SSH remote access is currently enabled.
Enter the hostname for the Hypervisor and press Enter. 3. If the hostname setting procedure is successful, this message is displayed:
The hostname is set.
Resetting hostnames
To reset a hostname: 1. 2. Open the Set the hostname menu. The specify a hostname prompt appears:
What is this Hypervisor's hostname?
Press the Enter key without typing anything else to reset the hostname. 34
Multiple networks
For installation purposes only a single network can be configured for access to the Red Hat Enterprise Virtualization Manger. Once the Red Hat Enterprise Virtualization Hypervisor is installed, additional network interfaces can be configured with the Red Hat Enterprise Virtualization Manager user interface.
1. 2. 3.
Select the Networking setup option. The network devices attached to your system are listed.
Choose an interface or a configuration option:
Select the network interface on the same network as the Red Hat Enterprise Virtualization Manager. On systems with one network interface there is only eth0 to choose from.
Device support
Wireless and logical network devices are presently unsupported.
4.
Identifying the interface Hypervisors include a tool to assist in physically identifying which network interface was selected.
Help identify eth0 by blinking the lights for 10 seconds ([Y]es or [N]o)?
Press y to identify which socket eth0 is. This is useful for systems with multiple network interfaces. If assistance is not required, continue by pressing n. If the selected network interface does not support this feature, the system will display the following message:
Blinking is not supported by your network interface.
5.
Enter the VLAN ID number when prompted. 6. IPv4 The IPv4 prompt appears.
Enable IPv4 support ([S]tatic IP, [D]HCP, [N]o or [A]bort)?
Select DHCP or Static IP depending on your networking environment. To use DHCP, press D to enable IPv4 support with DHCP. It is required to statically map all IP addresses for each Red Hat Enterprise Virtualization Hypervisor on your DHCP server. Alternatively, assign a static IP address by pressing S. You are then prompted for the IP address, Netmask and gateway. Confirm your settings.
Is this correct ([Y]es, [N]o or [A]bort)?
Press Y if correct to continue. 7. DNS Configure DNS if using static network configuration or of your DHCP server is not assigning DNS servers. a. Enter the IP address of the first DNS gateway or press Enter to abort.
Enter the first DNS server (or press the Enter key to exit):
b.
Enter the IP address of the second DNS gateway or press Enter to skip.
Enter the second DNS server (or press the Enter key to exit):
c.
Press Y if correct to continue. 8. Network Time Protocol (NTP) The Network Time Protocol (NTP) keeps system clocks in time with the rest of the world. NTP is crucial for some host systems with inconsistent clocks. Inaccurate timekeeping prevents Hypervisors from migrating virtual machines. a.
Enter an NTP server:
Enter the IP address or hostname of an NTP server or press Enter to abort. b. You will be prompted to enter additional NTP servers. Enter as many as required and press Enter on a blank line to save your selection.
36
Register to RHN 9. Select Save And Return To Menu to save the configuration.
10. If the network is configured correctly, the output should be similar to Figure 4.1, Working network configuration.
Figure 4.1. Working network configuration You are now returned to the main menu.
Enter a profile name for this system. This parameter is optional. If a blank profile name is provided, the system hostname will be used by default. d.
Enter HTTP proxy in host:port format, e.g. proxy.example.com:3128 (leave blank if not required):
Enter your HTTP proxy address. This parameter is optional. If a blank proxy address is provided, no proxy server will be used. To register to an RHN Satellite, select 2) Register to RHN Satellite a.
Enter URL of RHN Satellite (ie. https://satellite.example.com)
37
Chapter 4. Installing the Red Hat Enterprise Virtualization Hypervisor Enter the URL of your satellite certificate, or press enter to select the default URL shown. c.
Enter RHN account username:
Enter a profile name for this system. This parameter is optional. If a blank profile name is provided, the system hostname will be used by default. f.
Enter HTTP proxy in host:port format, e.g. proxy.example.com:3128 (leave blank if not required):
Enter your HTTP proxy address. This parameter is optional. If a blank proxy address is provided, no proxy server will be used.
Table 4.1. Red Hat Enterprise Virtualization Manager addressing examples Type IP address Host Name 1. 2. Format IP[:port] host.name.domain[:port] Example 127.0.0.1:443 www.redhat.com:443
Select Configure the host for RHEV from the main menu. Connecting Red Hat Enterprise Virtualization Manager Once the Configure the host for RHEV menu item is selected the following output displays:
Enter the RHEV Manager's hostname or IP address.
38
View logs
Optionally: append a port after the hostname or IP address For example, 10.0.0.1:443 or rhev.example.com:443
a.
Enter the Red Hat Enterprise Virtualization Manager's hostname or IP address in the specified format. If the Red Hat Enterprise Virtualization Manager port is skipped the setup will use the default port, port 443. However, if a port has previously been assigned, the Red Hat Enterprise Virtualization Hypervisor uses that port as the default instead. For example, if port 12345 was specified during a previous installation then the default port for future installations is port 12345.
b.
If the Red Hat Enterprise Virtualization Manager is successfully located, the following output is displayed:
The RHEV Manager's address is set The RHEV Manager's port is set.
3.
NetConsole access
Enter the NetConsole manager's hostname or IP address. Optionally: append a port after the hostname or IP address For example, 10.0.0.1:25285 or rhev.redhat.com:25285 If you are unsure, use the Red Hat Enterprise Virtualization Manager's address, without a port.
a.
Enter the NetConsole server and port. In most cases, this server will be the Red Hat Enterprise Virtualization Manager. The NetConsole port is the same as the NetConsole port number specified during the installation of the Red Hat Enterprise Virtualization Manager in Section 3.2.9, Enter net console port. If the NetConsole server is successfully found, the following output is displayed before being returned to the configuration menu:
The NetConsole manager address is set. The NetConsole manager port is set.
b.
Chapter 4. Installing the Red Hat Enterprise Virtualization Hypervisor Contains detailed information about the hypervisor installation and configuration procedure. /var/log/messages Contains general messages from the system and core services. /var/log/secure Contains authentication and security messages, including failed login attempts.
4.13. Installation
Once all the previous steps are complete, the Red Hat Enterprise Virtualization Hypervisor can be installed to the local storage device. Storage, networking and the Red Hat Enterprise Virtualization Manager must be configured before continuing. 1. 2. Select Install locally and reboot from the Hypervisor Configuration Menu.
This option exits the menu and requires a reboot. Ensure local storage and networking is configured correctly on the previous menu before continuing. The current kernel boot parameters are crashkernel=128M@16M elevator=deadline processor.max_cstate=1 Enter additional kernel boot parameters (press Enter to use the present arguments):
Press Y to continue. The final installation sequence begins. Once the installation is complete the Red Hat Enterprise Virtualization Hypervisor will reboot. After rebooting, the Red Hat Enterprise Virtualization Hypervisor is installed and integrated with Red Hat Enterprise Virtualization Manager for Servers. You should have a new host available in the Red Hat Enterprise Virtualization Manager interface.
Note
You may need to remove the boot media and change the boot device order to prevent the installation sequence restarting after the system reboots.
Using the hypervisor 2. 3. 4. From the Hosts tab, click on the host to be approved. The host should currently be listed with the status of Pending Approval. Click the Approve button. The Edit and Approve dialog displays. You can use the dialog to make changes to the details Click Save. The status in the Hosts tab changes to Installing, after a brief delay the host status changes to Up.
41
42
Chapter 5.
Important
Only the AMD64/Intel 64 version of Red Hat Enterprise Linux is compatible for use with Red Hat Enterprise Virtualization.
Note
Red Hat Enterprise Linux 5.4 hosts can only be used with a Red Hat Enterprise Virtualization Manager which was upgraded from version 2.1 to 2.2. They can only be attached to data centers running in version 2.1 compatibility mode. New installations of Red Hat Enterprise Virtualization Manager 2.2 or data centers running in version 2.2 compatibility mode can only support Red Hat Enterprise Linux 5.5 hosts. Red Hat Enterprise Virtualization Manager 2.2 in version 2.1 compatibility mode can support Red Hat Enterprise Linux 5.5 hosts.
The following table shows which versions of Red Hat Enterprise Linux are supported as hosts for each version of Red Hat Enterprise Virtualization. Red Hat Enterprise Linux Version Red Hat Enterprise Virtualization 2.1 Red Hat Enterprise Virtualization 2.2 Red Hat Enterprise Virtualization 2.2 in 2.1 compatibility mode Supported Supported
5.4 5.5
Supported Unsupported
Unsupported Supported
Ensure that VLANs are configured for access to the Red Hat Enterprise Virtualization Manager. Ensure the host is correctly subscribed to the appropriate Red Hat Network channels. Red Hat Enterprise Virt Management Agent (v.5 for x86_64) RHEL Virtualization (v. 5 for 64-bit x86_64)
Note
If you do not have the appropriate subscription entitlements, contact Red Hat Customer Service.
Install the fence-agents, kvm-qemu-img bridge-utils packages required by Red Hat Enterprise Virtualization Manager to manage Red Hat Enterprise Linux hosts. During installation if the required additional packages are not found, they will be automatically installed by the Red Hat Enterprise Virtualization Manager. Install the required packages with yum:
# yum install bridge-utils fence-agents kvm-qemu-img
Warning
If you are using proprietary directory services or standard directory services with no access to authentication files for user management, the vdsm package will fail to create the required system user . The authentication files required by the useradd command must be accessible to the installer. Red Hat Directory Server (RHDS) recommends a security policy with a mixture of local files and LDAP. Following this recommendation will resolve this issue.
Uninstall incompatible packages. The Red Hat Enterprise Virtualization management daemon (vdsm) is currently incompatible with Xen. Therefore Xen, including all dependencies, should be removed.
44
Warning
The following steps will destroy data on all existing virtual machines. It is strongly recommended to back up or migrate existing virtual machines to other Red Hat Enterprise Linux servers before proceeding. This process is not reversible.
Remove the xen and kernel-xen packages with the yum command:
# yum remove xen kernel-xen
Reboot the system. The reboot effects a return to the default kernel if the Xen kernel was in use. Add a manual host entry to the /etc/hosts file (on the Red Hat Enterprise Linux 5.5 host) for the Red Hat Enterprise Virtualization Manager server to enable vdsm and other services to connect properly to the host. Because Active Directory uses layered domain names, the Active Directory instance takes the domain name usually used by a Linux host. For example, if the server running the Red Hat Enterprise Virtualization Manager has a hostname of server1.example.com, Active Directory uses that address and creates a sub-address named rhev-manager.server1.example.com. Edit the /etc/hosts file on the Red Hat Enterprise Linux Host. The following screen output sample resembles the contents of the file:
127.0.0.1 ::1 localhost.localdomain localhost localhost6.localdomain6 localhost6
Append a new line to /etc/hosts with the IP address and both variants of the Red Hat Enterprise Virtualization Manager domain names. The following screen output sample resembles the required contents of the file:
127.0.0.1 localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 10.0.0.1 server1.example.com rhev-manager.server1.example.com
Open firewall ports on the host. Red Hat Enterprise Virtualization platform uses a number of network ports for management and other virtualization features. The following steps configure iptables to open the required ports. Add the required ports as iptables rules. Advanced users can modify rules or use the iptables -i option instead of iptables -A in order to integrate with existing rules.
# # # # # # # # iptables iptables iptables iptables iptables iptables iptables iptables -A -A -A -A -A -A -A -A INPUT INPUT INPUT INPUT INPUT INPUT INPUT INPUT -m -p -i -p -p -p -p -j state --state ESTABLISHED,RELATED -j ACCEPT icmp -j ACCEPT lo -j ACCEPT tcp --dport 54321 -j ACCEPT tcp --dport 22 -j ACCEPT tcp -m multiport --dports 5634:6166 -j ACCEPT tcp -m multiport --dports 49152:49216 -j ACCEPT REJECT --reject-with icmp-host-prohibited
45
Configure sudo access The Red Hat Enterprise Virtualization Manager makes use of sudo to perform operations as root on the host. The default configuration stored in /etc/sudoers contains values to allow this. If this file has been modified since Red Had Enterprise Linux installation these values may have been removed. As root run visudo to ensure that the /etc/sudoers contains the default configuration values. Where it does not they must be added.
Enable SSH access for root The Red Hat Enterprise Virtualization management daemon accesses host machines via SSH. To do this it logs in as root with an encrypted key for authentication. To ensure that SSH is configured and root is able to use it to access the system follow these additional steps.
Warning
The first time the Red Hat Enterprise Virtualization Manager is connected to the host it will install an authentication key. In the process it will overwrite any existing keys which exist in / root/.ssh/authorized_keys.
These steps assume that the openssh-server package is installed on the system. Where the package is not present use yum to install it.
# yum install openssh-server
# chkconfig --list sshd sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
It is expected that the SSH daemon shows as on for run-levels 3, 4, and 5. This is the default configuration. If the configuration on the host differs use chkconfig to enable it for the required run-levels. The /etc/init.d/sshd script can then be used to ensure the service is currently started.
46
To Add a Host To verify this operation as successful run chkconfig --list sshd again and check the output. It should now show the daemon as on at run-level 3, 4, and 5. In Red Hat Enterprise Linux the default SSH daemon configuration allows remote login by the root user. This is also a requirement for the Red Hat Enterprise Virtualization Manager to successfully access the machine. In some cases administrator's may have disabled this ability. To check whether or not this is the case search the /etc/ssh/sshd_config for the value PermitRootLogin. This must be done while logged in as root.
Where PermitRootLogin is set to no the value must be changed to yes. To do this edit the configuration file.
# vi /etc/ssh/sshd_config
Once the updated configuration file has been saved the SSH daemon must be told to reload it.
OK
The root user should now be able to access the system via SSH. You can now add the correctly installed and configured Red Hat Enterprise Linux host to Red Hat Enterprise Virtualization platform.
47
Figure 5.1. List of Hosts 2. Click the New button. The New Host dialog displays.
48
To Add a Host
Figure 5.2. New Host Dialog Enter the details of the new host. 3. Name: a descriptive name for the host. 4. Address: the IP address, or resolvable hostname of the host (provided during installation). 5. Port: the port used for internal communication control between the hosts. A default port is displayed; change the default only if you are sure that another port can be used. 6. Host Cluster: the cluster to which the host belongs (select from the drop-down list). 7. Root password: the password of the designated host; used during installation of the host.
49
Chapter 5. Using Red Hat Enterprise Linux Hosts 8. Enable Power Management: Select this checkbox to turn out-of-band (OOB) power management on. If selected, the information for the following fields must also be provided. The Address of the host. This is usually the address of the remote access card (RAC) on the host. A valid User Name for the OOB management. A valid, robust Password for the OOB management. The Type of the OOB management device. Select the appropriate device from the drop down list. alom apc bladecenter drac5 eps ilo ipmilan rsa rsb wti The Port to connect to OOB management. Slot: The slot number in the blade chassis. This option is for blade systems only. Options: Extra command line options for the fence agent. Detailed documentation of the options available is provided in the man page for each fence agent. Secure: Some fence agents support both encrypted and unencrypted communications. Check this option to enable encrypted communications. Click the Test button to test the operation of the OOB management solution. Red Hat Enterprise Virtualization recommends power management. Power management enables the system to fence a troublesome host using an additional interface. Sun Integrated Lights Out Manager (ILOM) APC Master MasterSwitch network power switch IBM Bladecentre Remote Supervisor Adapter Dell Remote Access Controller for Dell computers ePowerSwitch 8M+ network power switch HP Integrated Lights Out standard Intelligent Platform Management Interface IBM Remote Supervisor Adaptor Fujitsu-Siemens RSB management interface WTI Network PowerSwitch
Note
If the host is required to be Highly Available, power management must be enabled and configured.
9. Click OK.
50
Activating a Host The new host displays in the list of hosts with a status of "Installing". Once installation is complete, the status will update to Reboot and then Awaiting. The host must be activated for the status to change to Up.
Note:
View the process of the host installation on the Details pane.
51
52
Chapter 6.
Setting Up Storage
This chapter provides a quick start guide to configuring storage for Red Hat Enterprise Virtualization. For information about managing storage, including maintenance and removal, refer to the Red Hat Enterprise Virtualization Administration Guide. Red Hat Enterprise Virtualization uses a centralized storage system for maintaining ISO files and virtual machine disk images, data and snapshots. Storage networking can be implemented using Network File System (NFS), Internet Small Computer System Interface (iSCSI) or Fibre Channel Protocol (FCP). Once storage has been configured, it must be attached to the Red Hat Enterprise Virtualization Manager in order to make it accessible to the system.
chkconfig nfs on
53
Chapter 6. Setting Up Storage Determine the NFS share directory. For example, if you intend to share /RHEV/Images, enter the following line into the /etc/exports file.
/RHEV/Images *(rw,no_root_squash)
Restart the NFS service. The NFS export directory must be configured for read write access and must be owned by vdsm:kvm. If these users do not exist on your external NFS server use the following command, assuming that /RHEV/Images is the NFS share.
chown -R 36:36 /RHEV/Images
To Add NFS Storage: 1. Click the Storage tab. The Storage list and toolbar display. 2. Click New Domain. The New Domain dialog box displays.
Figure 6.1. NFS Storage 3. Enter the Name of the storage. For example, depending on its function, either Images or ISO. A suitably descriptive name is recommended. 4. Select the appropriate Domain function: Data, ISO or Export. 54
Adding iSCSI Storage 5. Select NFS as the Storage type. 6. Select an active host in the Use host field. To attach a domain, the name of any active host must be selected from the list of existing hosts.
Note
All communication to the storage domain is via the configured host and not from the Red Hat Enterprise Virtualization Manager. At least one host must exist in the system before the storage can be configured.
7. Enter the Export path of the storage. The export path can be either an IP address or a resolvable hostname. For example, 192.168.0.10:/Images/ISO. 8. Click OK. 9. The name of the NFS storage domain is added to the Storage tab.
55
Figure 6.2. New Domain Dialog 3. Enter the Name of the storage. 4. Select the appropriate Domain function: Data, ISO or Export. 5. Select iSCSI as the storage Storage type. The dialog box displays a set of fields appropriate to the iSCSI type.
56
Figure 6.3. Adding iSCSI Storage 6. Select an active host in the Use host field. To attach a domain, the name of any active host must be selected from the list of existing hosts.
Note
All communication to the storage domain is via the configured host and not from the Red Hat Enterprise Virtualization Manager. At least one host must exist in the system before the storage can be configured.
7. Select either Build New Domain or Use Pre-Configured Domain. In this step you can either attach a set of LUNs (create a volume group) or attach an already existing Volume Group as your storage domain. 8. To Build New Domain: a. If necessary, to search for LUNs, click the Connect to Target button. b. The Connect to Targets dialog displays, enabling you to define a target on which to search for LUNs. Enter the requisite information in the fields.
57
Figure 6.4. Adding iSCSI Storage i. ii. Enter the IP Address of the iSCSI target. Enter the Port to connect to.
iii. If required, enter the details for User Authentication. iv. Click the Discover button to find the targets. v. The targets display in the list of Discovered Targets
vi. Click to either Login to All targets, or Add targets manually. If adding manually, select the LUNs from the list. vii. Click Close. The targets are now selected, and the LUNs display in the New Storage dialog.
58
Figure 6.5. Adding LUNs c. A list of LUNs (Logical Unit Numbers) display in the list of Discovered LUNs. Click the Add button to select the LUNs to add to the storage domain.
d. The LUNs selected in the previous step display in the Selected LUNs grid. The set of LUNs in this list will be assigned to the new storage domain. Use the Remove button to remove LUNs from the Selected LUNs if necessary.
59
Figure 6.6. Adding LUNs e. Click OK to attach the selected LUNs to the iSCSI storage domain. 9. To Use a Preconfigured Volume Group: a. In this step you use an existing volume group. Ensure that all tags and LVs have been removed from the VG before creating the new domain. The New Domain dialog changes to display the required fields for the preconfigured domain.
60
Figure 6.7. New Storage - Use Existing Volume group b. Use the Add a Target link to connect to an existing storage domain. The Connect to Targets dialog displays. See Figure 6.4, Adding iSCSI Storage. c. Select a Volume Group to connect to. The Name and Size are displayed. Click the Expand button to view the LUNs that comprise the VG.
10. Click OK. 11. The new storage domain displays in the Storage tab.
61
Chapter 6. Setting Up Storage Red Hat Enterprise Virtualization system administrators need a working knowledge of Storage Area Networks (SAN) concepts. SAN usually uses Fibre Channel Protocol (FCP) for traffic between hosts and shared external storage. For this reason, SAN may occasionally be referred to as FCP storage. For information regarding the setup and configuration of FCP or multipathing on Red Hat Enterprise Linux, please refer to the Online Storage Reconfiguration Guide and DM-Multipathing Guide. To Add FCP Storage: 1. Click the Storage tab. The Storage list and toolbar display. 2. Click New Domain. The New Domain dialog box displays. 3. Enter the Name of the storage. 4. Select FCP as the Storage type. The dialog box displays the appropriate fields.
Figure 6.8. Adding FCP Storage 5. Select a host in Use host. To attach a domain, any active host must be selected.
Note
All communication to the storage domain is via the configured host and not from the Red Hat Enterprise Virtualization Manager. At least one host must exist in the system before the storage can be configured.
62
Adding FCP Storage 6. Select either Build New Domain or Use Existing Volume Group. 7. To Build New Domain: a. A list of LUNs (Logical Unit Numbers) display in the list of Discovered LUNs. Click the Add button to select the LUNs to add to the storage domain. b. The LUNs selected in the previous step display in the Selected LUNs grid. The set of LUNs in this list will be assigned to the new storage domain. Use the Remove button to remove LUNs from the Selected LUNs if necessary. c. Click OK to attach the selected LUNs to the storage domain.
8. To Use Preconfigured Domain: a. In this step you use an existing volume group. The New Storage dialog changes to display the required fields for the preconfigured domain. This is similar to the fields for the iSCSI preconfigured domain shown here.
Figure 6.9. New Storage - Use Existing Volume group b. Use the Add a Target link to connect to an existing storage domain. The Connect to Targets dialog displays. See Figure 6.4, Adding iSCSI Storage. c. A list of targets display in the Target Manager. 63
Chapter 6. Setting Up Storage d. Select a Volume group to connect to. Ensure that all tags and LVs have been removed from the VG before creating the new domain. The Name and Size are displayed. Click the Expand button to view the LUNs that comprise the Volume group. 9. Click OK. 10. The new storage domain displays in the Storage list.
64
Chapter 7.
Important
Detailed instructions for performing the following procedures are provided in the Red Hat Enterprise Virtualization Administration Guide.
Procedure 7.1. Typical Red Hat Enterprise Virtualization configuration workflow: 1. Upload ISO files onto the defined Storage domains. This is essential for allowing efficient creation of new virtual machines, as required. 2. Define clusters. A cluster is a group of hosts. Grouping hosts into a cluster allows resources to be shared across the cluster. Grouping also allows segmentation between groups (for example, resources are not shared between HR and finance). Define logical networks for the data center, cluster and the hosts. For example, the default logical networks will need to be edited if a new network card is added to the data center. Define virtual machines by installing an operating system and applications using the Run Once function. Define templates from customized virtual servers. This enables creation of large numbers of identical virtual machines quickly and efficiently.
3. 4. 5.
65
66
CPU
CPU will have an average target utilization of 50%, allowing virtual machines to reach 100% utilization during high loads.
Memory
The Red Hat Enterprise Virtualization page sharing process overcommits up to 150% of physical memory for virtual machines. Therefore, allow for an approximately 30% overcommit.
Networking
When designing the network, it is important to ensure that the volume of traffic produced by storage, remote connections and virtual machines is taken into account. As a general rule, allow approximately 50 MBps per virtual machine. It is best practice to separate disk I/O traffic from end-user traffic, as this reduces the load on the ethernet connection and reduces security vulnerabilities by isolating data from the visual stream. For ethernet networks, it is suggested that bonds (802.3ad) are utilized to aggregate server traffic types.
Note
It is possible to connect both the storage and Hypervisors via a single high performance switch. For this configuration to be effective, the switch must be able to provide 30 GBps on the backplane.
High Availability
The system requires at least two Hypervisors to achieve high availability. This redundancy is useful when performing maintenance or repairs.
67
68
B.2. Creating the Red Hat Enterprise Virtualization admin user in Active Directory
The administrative user must be created prior to installation. The credentials of this user are required to complete Manager installation. It is the account used when logging into the Red Hat Enterprise Virtualization Administration Portal to manage the system. The Red Hat Enterprise Virtualization administrative user must have delegated control over the Domain to: Join a computer to the domain. Modify the membership of a group. For information on creation of user accounts refer to http://technet.microsoft.com/en-us/library/ cc732336.aspx. For information on delegation of control refer to http://technet.microsoft.com/en-us/library/ cc732524.aspx.
69
70
4.
5.
71
Figure C.1. Local DTC Properties 6. Apply Local DTC security configuration changes Click OK. A dialog box will appear indicating that the MSDTC service must be restarted for the configuration changes to be applied. Click Yes to restart the service.
7. Result: The MSDTC configuration has been updated to allow remote connections.
72
1.
Open SQL Server 2005 Surface Area Configuration Click Start All Programs Microsoft SQL Server 2005 Configuration Tools SQL Server Surface Area Configuration.
2. 3.
Open Surface Area Configuration for Services and Connections Click Surface Area Configuration for Services and Connections. Open Remote Connections configuration In the tree view on the left of the window which appears click the Remote Connections entry associated with the Database Engine that the Red Hat Enterprise Virtualization Manager is to use. Allow local and remote connections Ensure that both the Local and remote connections and Using both TCP/IP and named pipes options are selected. Open SQL Server Browser configuration In the tree view on the left of the window click the SQL Server Browser entry. Enable automatic start of the SQL Server Browser Ensure that the Startup type is set to Automatic. This ensures that the SQL Server Browser is run each time the system starts. Start the SQL Server Browser If the Service Status is not shown as Running then click the Start button. This action will start the service. Apply Surface Area configuration changes Click OK to apply the configuration changes. The SQL Server 2005 Surface Area Configuration window will return to focus. Close this window to exit.
4.
5. 6.
7.
8.
9. Result: The SQL Server 2005 Surface Area Configuration has been updated to allow remote connections.
Appendix C. Remote Microsoft SQL Server configuration Administrators must examine their Microsoft SQL Server 2005 configuration to further strengthen the given firewall rules where possible. Configuration of Microsoft SQL Server 2005 to use static port allocation or a specific range of ports in conjunction with dynamic port allocation allows for firewall rules which restrict communication to the specific ports in use. Consult the Microsoft SQL Server 2005 documentation for further information. Microsoft Distributed Transaction Coordinator The msdtc.exe executable is found in the system32 directory of the Windows Server 2008 R2 installation. Example C.1. Path to msdtc.exe
%SystemRoot%\system32\msdtc.exe
Microsoft SQL Server 2005 instance The sqlservr.exe executable is found in the Binn directory under the Microsoft SQL Server 2005 installation. Example C.2. Path to sqlservr.exe
%ProgramFiles(x86)%\Microsoft SQL Server\MSSQL.1\Binn\sqlservr.exe
Each Microsoft SQL Server 2005 database instance has an identifier associated with it. This instance identifier forms a component of the path to the relevant sqlservr.exe executable. In Example C.2, Path to sqlservr.exe the value MSSQL.1 in the path is the instance identifier. See Procedure C.1, Determine database instance identifier for instruction on determining the instance identifier to use. Microsoft SQL Server 2005 Server Browser The sqlbrowser.exe executable is found in the 90\Shared directory under the Microsoft SQL Server 2005 installation. Example C.3. Path to sqlservr.exe
%ProgramFiles(x86)%\Microsoft SQL Server\90\Shared\sqlbrowser.exe
Refer to Procedure C.2, Create firewall exception for a specific program for instructions on creation of a program specific exception in the Windows Firewall on Windows Server 2008 R2 systems. Administrators managing Windows Server 2003 systems should consult their operating system documentation.
74
Procedure C.1. Determine database instance identifier 1. Open SQL Server Configuration Manager Click Start All Programs Microsoft SQL Server 2005 Configuration Tools SQL Server Configuration Manager. 2. Select SQL Server 2005 Services Ensure that SQL Server 2005 Services is selected in the pane on the left hand side of the window that appears. Open SQL Server Browser properties In the pane on the right hand side of the SQL Server Configuration Manager right click on the SQL Server Browser entry. From the context menu that appears select Properties. Locate instance identifier Click the Advanced tab heading. On the resultant screen take note of the value listed for the Instance ID field.
3.
4.
5. Result: The instance identifier has been located. This value is required to configure the system's firewall to allow remote connections to the Microsoft SQL Server 2005 instance. Procedure C.2. Create firewall exception for a specific program 1. Open Windows Firewall with Advanced Security Click Start Administrative Tools Windows Firewall with Advanced Security. 2. View Inbound Rules or Outbound Rules Click Inbound Rules or Outbound Rules in the left hand pane of the Windows Firewall with Advanced Security window. The option selected determines which type of rule will be created in subsequent steps. Create New Rule Click New Rule in the right hand pane of the Windows Firewall with Advanced Security window. Select rule type Ensure that the selected rule type is Program and then click Next >. Program selection Select This program path to restrict the rule to a specific program executable. Click Browse... to select the executable the rule should apply to. Once the correct executable has been selected, click Next > to continue. 75
3.
4. 5.
Appendix C. Remote Microsoft SQL Server configuration 6. 7. Specify firewall action Select Allow the connection and click Next > to continue. Select profile Specify when the new rule should apply. At least one of Domain, Private or Public should be selected. If unsure which of these profiles is appropriate for your organization click Learn more about profiles for further information. Once the appropriate profiles have been selected click Next > to continue. 8. Name rule Enter a descriptive name for the new firewall rule in the Name field. Click Finish > to create the new rule.
9. Result: The Windows Firewall has been configured to allow inbound or outbound connections for the selected program.
76
77
78
79
80