1. Log on to Red Hat Network (http://rhn.redhat.com).
2. Click Systems at the top of the page.
3. Select the system to which you are adding channels from the list presented on the screen, by clicking the name of the system.
4. Click Alter Channel Subscriptions in the Subscribed Channels section of the screen.
5. Select the Red Hat Enterprise Virtualization Hypervisor (v.6 x86_64) channel from the list presented on the screen, then click the Change Subscription button to finalize the change.
6. Log in to the system on which the Red Hat Enterprise Virtualization Manager is installed. You must log in as the root user.
7. Use yum to install the rhev-hypervisor and rhev-hypervisor-tools packages.

   # yum install "rhev-hypervisor*"

1. Boot the hypervisor from removable media. For example, a USB stick or CD-ROM.
2. When the message Automatic boot in 30 seconds... is displayed, and begins counting down from thirty, press any key to skip the automatic boot process.
3. Ensure the Install or Upgrade option is selected and press Tab to edit the boot parameters.
4. Add the rescue parameter to the list of boot parameters shown on the screen, then press Enter. This action will boot the hypervisor in rescue mode.
5. Once the hypervisor boots, verify your CPU contains the virtualization extensions with the following command:

   # grep -E 'svm|vmx' /proc/cpuinfo
   

   Output displays if the processor has the hardware virtualization extensions.
6. Verify that the KVM modules load by default:

   # lsmod | grep kvm
   

Procedure 7.5. Hostname Configuration

1. To set or change the hostname select the Hostname field and enter the new hostname.
2. Select <Apply>, and press Enter to save changes to the hostname.

Procedure 7.6. DNS Configuration

1. To set or change the primary DNS server select the DNS Server 1 field and enter the IP address of the new primary DNS server to use.
2. To set or change the secondary DNS server select the DNS Server 2 field and enter the IP address of the new secondary DNS server to use.
3. Select <Apply>, and press Enter to save changes to the DNS configuration.

Procedure 7.7. NTP Configuration

1. To set or change the primary NTP server select the NTP Server 1 field and enter the IP address or hostname of the new primary NTP server to use.
2. To set or change the secondary NTP server select the NTP Server 2 field and enter the IP address or hostname of the new secondary NTP server to use.
3. Select <Apply>, and press Enter to save changes to the NTP configuration.

Procedure 7.8. Network Interface Configuration

1. Device Identification

   Select the network interface to be configured from the list and press Enter.
   In some cases it may be unclear which physical device an entry in the list refers to. Where this is the case the hypervisor is able to blink the physical device's network traffic lights to assist with identification. To make use of this facility select the entry from the list and, then select the <Flash Lights to Identify> button. Press Enter and, take note of which physical device's lights start blinking. The configuration screen for the selected device will be displayed.

2. IPv4 Settings

   The hypervisor supports both dynamic (DHCP), and static IPv4 network configuration.

   • Dynamic (DHCP) Network Configuration

     Dynamic network configuration allows the hypervisor to be dynamically assigned an IP address via DHCP. To enable dynamic IPv4 network configuration select the DHCP option under IPv4 Settings and press Space to toggle it to enabled.

   • Static Network Configuration

     Static network configuration allows the hypervisor to be manually assigned an IP address. To enable static IPv4 network configuration select the Static option under IPv4 Settings and press Space to toggle it to enabled.
     Selection of the Static option enables the IP Address, Netmask, and Gateway fields. The IP Address, Netmask, and Gateway fields must be populated to complete static network configuration.
     In particular it is necessary that:

     • the IP Address is not already in use on the network,
     • the Netmask matches that used by other machines on the network, and
     • the Gateway matches that used by other machines on the network.

     Where it is not clear what value should be used for the IP Address, Netmask, or Gateway field consult the network's administrator or consider a dynamic configuration.

     Example 7.11. Static IPv4 Networking Configuration

     IPv4 Settings
     [ ] Disabled [ ] DHCP [*] Static
     IP Address: 192.168.122.100_ Netmask: 255.255.255.0___
     Gateway     192.168.1.1_____
     

     
     

3. IPv6 Settings

   The Red Hat Enterprise Virtualization Manager does not currently support IPv6 networking. IPv6 networking must remain set to Disabled.

4. VLAN Configuration

   If VLAN support is required then populate the VLAN ID field with the VLAN identifier for the selected device.

5. Save Network Configuration

   Once all networking options for the selected device have been set the configuration must be saved.
   1. Select the <Apply> button and press Enter to save the network configuration.
   2. The Confirm Network Settings dialog box will appear. Ensure that the Ok button is selected and press Enter to confirm.

Procedure 7.9. Change Security Configuration

1. Enable SSH Password Authentication

   To enable SSH password authentication for remote access select the Enable ssh password authentication option and press Space to toggle it to enabled.

2. Change admin Password

   1. Enter the desired admin password in the Password field. You should use a strong password.
      Strong passwords contain a mix of uppercase, lowercase, numeric and punctuation characters. They are six or more characters long and do not contain dictionary words.
   2. Enter the desired admin password in the Confirm Password field. Ensure that the value entered in the Confirm Password field matches the value entered in the Password field exactly. Where this is not the case an error message will be displayed to indicate that the two values are different.
3. Select <Apply> and press Enter to save the security configuration.

Procedure 7.10. Change Logging Configuration

1. Logrotate Configuration

   The logrotate utility simplifies the administration of log files. The hypervisor uses logrotate to rotate logs when they reach a certain file size.
   Log rotation involves renaming the current log(s) and starting new ones in their place. The Logrotate Max Log Size value set on the Logging screen is used to determine when a log should be rotated.
   Enter the Logrotate Max Log Size in kilobytes. The default maximum log size is 1024 kilobytes.

2. Rsyslog Configuration

   The rsyslog utility is a multithreaded syslog daemon. The hypervisor is able to use rsyslog to transmit log files over the network to a remote syslog daemon. For information on setting up the remote syslog daemon consult the Red Hat Enterprise Linux — Deployment Guide.
   1. Enter the remote Rsyslog server address in the Server Address field.
   2. Enter the remote Rsyslog server port in the Server Port field. The default port is 514.

3. netconsole Configuration

   The netconsole module allows kernel messages to be sent to a remote machine. The hypervisor uses netconsole to transmit kernel messages over the network.
   1. Enter the Server Address.
   2. Enter the Server Port. The default port is 6666.

4. Save Configuration

   To save the logging configuration select <Apply> and press Enter.

Procedure 7.11. kdump Configuration

1. Kernel Configuration

   Crash dumps generated by kdump are exported over NFS or SSH. Select the desired transfer method and press Space to enable it.
   For the export method chosen a location to which the kdump files should be exported must also be specified.

   1. NFS location

      Set the NFS location to which crash logs should be exported in the NFS Location field. The NFS Location should be the full NFS path which includes fully qualified domain name and directory path.

      Example 7.12. NFS Location

      example.redhat.com:/var/crash
      
      

   2. SSH location

      Set the SSH location to which crash logs should be exported in the SSH Location field. The SSH Location should be the full SSH login which includes the fully qualified domain name and username.

      Example 7.13. SSH Location

      root@example.redhat.com
      
      

2. Save Configuration

   To save the configuration the user must select <Apply> and press Enter.

Procedure 7.12. Remote Storage Configuration

1. iSCSI Initiator Name

   Enter the initiator name in the iSCSI Initiator Name field.

   Example 7.14. iSCSI Initiator Name

   iqn.1994-05.com.redhat:5189835eeb40
   
   

2. Save Configuration

   To save the configuration the user must select <Apply> and press Enter.

Procedure 7.13. RHEV-M Configuration

1. • Configuration Using a Management Server Address

     1. Enter the IP address or fully qualified domain name of the manager in the Management Server field.
     2. Enter the management server port in the Management Server Port field. The default value is 8443. Where a different port was selected during Red Hat Enterprise Virtualization Manager installation then it should be specified here, replacing the default value.
     3. Enable the Verify RHEVM Certificate option if you wish to verify that the finger print of the certificate retrieved from the management server you specified is correct. The value that the certificate finger print should be compared against is returned at the end of Red Hat Enterprise Virtualization Manager installation.
     4. Leave the Password and Confirm Password fields blank, these fields are not required if the address of the management server is known.

   • Configuration Using a Password

     1. Enter a password in the Password field. It is recommended that you use a strong password. Strong passwords contain a mix of uppercase, lowercase, numeric and punctuation characters. They are six or more characters long and do not contain dictionary words.
     2. Re-enter the password in the Confirm Password field.
     3. Leave the Management Server and Management Server Port fields blank. As long as a password is set, allowing the hypervisor to be added to the manager later, these fields are not required.

2. Save Configuration

   To save the configuration select <Apply> and press Enter.

Procedure 7.14. Register with Red Hat Network

1. Authentication

   Enter your Red Hat Network username in the Login field.
   Enter your Red Hat Network password in the Password field.

2. Profile Name

   Enter the profile name to be used for the system in the Profile Name field. This is the name that the system will appear under when viewed via the Red Hat Network.

3. Update Source

   Guests running on the hypervisor may need to consume Red Hat Enterprise Linux virtualization entitlements. Where this is the case the hypervisor must be registered to Red Hat Network or, if available, either a Satellite installation or a Subscription Asset Manager. The hypervisor is able to connect to these services via a HTTP proxy where one is in use.
   Note that when new versions of the hypervisor itself become available they are installed from the Red Hat Enterprise Virtualization Manager, not Red Hat Network.

   • To Connect Directly to RHN

     Select the RHN option and press Space to toggle it to enabled. The URL and CA values do not need to be provided.

     Example 7.15. Red Hat Network Configuration

     [*] RHN [ ] Satellite [ ] Subscription Asset Manager           
     URL:  ________________________________________                 
     CA :  ________________________________________

     
     

   • To Connect via Satellite

     1. Select the Satellite option and press Space to toggle it to enabled.
     2. Enter the URL of the Satellite server in the URL field.
     3. Enter the URL of the Certificate Authority for the Satellite server in the CA field.

     Example 7.16. Satellite Configuration

     [ ] RHN [*] Satellite [ ] Subscription Asset Manager
     URL:   https://your-satellite.example.com
     CA :   https://your-satellite.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT

     
     

   • To Connect via Subscription Asset Manager

     1. Select the Subscription Asset Manager option and press Space to toggle it to enabled.
     2. Enter the URL of the Subscription Asset Manager server in the URL field.
     3. Enter the URL of the Certificate Authority for the Subscription Asset Manager server in the CA field.

     Example 7.17. Subscription Asset Manager Configuration

     [ ] RHN [ ] Satellite [*] Subscription Asset Manager           
     URL:  https://subscription-asset-manager.example.com                 
     CA :  https://subscription-asset-manager.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT

     
     

4. HTTP Proxy

   Where a HTTP proxy is in use the details to connect to it must be provided. To connect to the Red Hat Network or a Satellite server via a proxy you must enter:

   • the proxy Server's network address,
   • the Port to connect to the proxy on, and
   • optionally, the Username and Password to use to connect to the proxy.

   In environments where a HTTP proxy is not in use it is safe to ignore this step.

   Example 7.18. HTTP Proxy Configuration

   HTTP Proxy
   Server: proxy.example.com__ Port: 8080_
   Username: puser________ Password: ******_______
   

   
   

5. Save Configuration

   To save the configuration the user must select <Apply> and press Enter.

Procedure 8.1. Directions:

1. Install Red Hat Enterprise Linux

   Ensure that Red Hat Enterprise Linux is correctly installed and configured on the physical host. Refer to the Red Hat Enterprise Linux Installation Guide for more information. Only the Base package group is required. All other packages can be removed or not selected.

   Warning — DNS Configuration

   The Red Hat Enterprise Linux host must have a fully resolvable network address. Valid forward and reverse lookups for the address must be available in DNS. Virtual machine migration will not work in environments where this is not the case.

   Important — Provide Access to Authentication Files

   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.

2. Configure VLANs

   If you are using VLAN, ensure that VLANs are configured for access to the Red Hat Enterprise Virtualization Manager.

3. Check Red Hat Network Subscriptions

   Ensure the host is correctly subscribed to the Red Hat Enterprise Virt Management Agent (v 6 x86_64) channel in Red Hat Network, also referred to as rhel-x86_64-rhev-mgmt-agent-6, on Red Hat Network. If you do not have the appropriate subscription entitlements, contact Red Hat Customer Service.
   1. If the machine has not already been registered with Red Hat Network, run the rhn_register command as root to register it. To complete registration successfully you will need to supply your Red Hat Network username and password. Follow the onscreen prompts to complete registration of the system.

      # rhn_register

   2. You must now add a subscription to the Red Hat Enterprise Virt Management Agent (v 6 x86_64) channel to the machine. To add the channel subscription to the system from the Red Hat Network web interface:
      1. Log on to Red Hat Network (http://rhn.redhat.com).
      2. Click Systems at the top of the page.
      3. Select the system to which you are adding channels from the list presented on the screen, by clicking the name of the system.
      4. Click Alter Channel Subscriptions in the Subscribed Channels section of the screen.
      5. Select the Red Hat Enterprise Virt Management Agent (v 6 x86_64) channel from the list presented on the screen, then click the Change Subscription button to finalize the change.

4. Edit hosts file

   Add a manual host entry to the /etc/hosts file (on the Red Hat Enterprise Linux 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    localhost.localdomain localhost
   ::1          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
   

5. Open firewall ports

   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. These steps replace any existing firewall configuration with that required for Red Hat Enterprise Virtualization Manager. If you have existing firewall rules with which this configuration must be merged then you must manually edit the rules defined in the iptables configuration file, /etc/sysconfig/iptables.
   1. Remove and existing firewall rules.

      # iptables --flush

   2. Add the ports required by Red Hat Enterprise Virtualization Manager to the iptables rules.

      # iptables --append INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
      # iptables --append INPUT -p icmp -j ACCEPT
      # iptables --append INPUT -i lo -j ACCEPT
      # iptables --append INPUT -p tcp --dport 22 -j ACCEPT
      # iptables --append INPUT -p tcp --dport 16514 -j ACCEPT
      # iptables --append INPUT -p tcp --dport 54321 -j ACCEPT
      # iptables --append INPUT -p tcp -m multiport --dports 5634:6166 -j ACCEPT
      # iptables --append INPUT -p tcp -m multiport --dports 49152:49216 -j ACCEPT
      # iptables --append INPUT -j REJECT --reject-with icmp-host-prohibited
      # iptables --append FORWARD -m physdev ! --physdev-is-bridged -j REJECT --reject-with icmp-host-prohibited
      

      Note

      The provided iptables commands add firewall rules to accept network traffic on a number of ports. These include:

      • port 22 for SSH,
      • ports 5634 to 6166 for guest console connections,
      • port 16514 for libvirt virtual machine migration traffic,
      • ports 49152 to 49216 for VDSM virtual machine migration traffic, and
      • port 54321 for the Red Hat Enterprise Virtualization Manager.
   3. Save the modified rules.

      # service iptables save

   4. Ensure that the iptables service is configured to start on boot and has been restarted, or started for the first time if it wasn't already running.

      # chkconfig iptables on
      # service iptables restart
      

6. 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.

   # Allow root to run any commands anywhere 
   root    ALL=(ALL)   ALL
   

7. 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.
   1. 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

   2. Use chkconfig to verify which run-levels SSH is enabled at.

      # 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.

      # chkconfig --level 345 sshd on
      # /etc/init.d/sshd start
      

      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.
   3. 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.

      # grep PermitRootLogin /etc/ssh/sshd_config
      PermitRootLogin no
      

      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.

      # /etc/init.d/sshd reload
      Reloading sshd:                                            [  OK  ]
      

   The root user should now be able to access the system via SSH.

1. Click the Hosts tab. The Hosts tab displays a list of all hosts in the system.
   

   Figure 8.1. List of Hosts

   
   
2. Click the New button. The New Host dialog displays.
   

   Figure 8.2. New Host Dialog

   
   
   Enter the details of the new host.
   • Name: a descriptive name for the host.
   • Address: the IP address, or resolvable hostname of the host (provided during installation).
   • 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.
   • Host Cluster: the cluster to which the host belongs (select from the drop-down list).
   • Root password: the password of the designated host; used during installation of the host.
   • 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	Sun Integrated Lights Out Manager (ILOM)
       apc	APC Master MasterSwitch network power switch
       bladecenter	IBM Bladecentre Remote Supervisor Adapter
       drac5	Dell Remote Access Controller for Dell computers
       eps	ePowerSwitch 8M+ network power switch
       ilo	HP Integrated Lights Out standard
       ipmilan	Intelligent Platform Management Interface
       rsa	IBM Remote Supervisor Adaptor
       rsb	Fujitsu-Siemens RSB management interface
       wti	WTI Network PowerSwitch

     • 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. Select 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.

   Note

   If the host is required to be Highly Available, power management must be enabled and configured.
3. Click OK.

1. Click the New button on the Data Centers tab. The New Data Center dialog displays.
2. Enter the Name and Description of the data center.
3. Select the storage Type of the data center. Select the storage appropriate to your data center; one of the following:

   • NFS
   • iSCSI
   • FCP
   • Local Storage
4. Select the Compatibility Level of the data center, 2.2 or 3.0.
5. Click OK.
6. The Guide Me dialog displays a list of configuration tasks that must be completed before the data center can be activated. The data center configuration tasks can be done immediately or later.
   

   Figure 9.3. New Data Center Guide Me Dialog

   
   
   Click Configure Later to close the dialog.

Procedure 9.1. To create a new host cluster:

1. Click the Clusters tab. A list of clusters displays.
2. Click the New button on the Clusters tab.
   The New Cluster dialog displays.
3. On the General tab, Select an existing Data Center from the list, the cluster Name and Description. The name should not include spaces.
   Select the CPU Name for the Cluster. All hosts in the Cluster must have this model of CPU, or a newer model capable of exposing the same functionality. The CPU Name list displays all the CPU models supported by Red Hat Enterprise Virtualization. Finally on the General tab, select the Compatibility Level of the data center, from either 2.2 or 3.0.
4. Use the Memory Optimization tab to define how much of the host's memory can be used in excess of the permitted memory for a virtual machine in the cluster. For example, all virtual machines will not be using the full amount of allocated memory all the time. Memory sharing allows virtual machines that require additional memory at a certain time to use memory that is not being used at that time by other virtual machines. This feature allows you to fine tune how you wish to optimize the memory page sharing and large pages implementation on the hosts in the cluster.
   Select from None, that disables memory page sharing, Optimized for Server Load, that sets the memory page sharing threshold to 150% of the system memory on each host, or Optimized for Desktop Load, that sets the memory page sharing threshold to 200% of the system memory on each host.
5. Select the Resilience Policy tab to define if high availability is to be implemented for the virtual machines in the cluster. If a host shuts down unexpectedly or is put into maintenance, the virtual machines running on the host can be re-run on another host in the same cluster. This field allows you to configure the migration settings for virtual machines.
   Select from Migrate Virtual Machines, (migrates all machines); Migrate only Highly Available Virtual Machines or Do Not Migrate Virtual Machines.
6. Click OK to create the cluster. The new host cluster is added to the data center and displays on the Cluster tab.
   The New Cluster - Guide Me dialog displays.
7. The Guide Me tab prompts you to add hosts to the new cluster. Click the Configure Hosts button, the New Host dialog displays.
   Enter the details of the host to assign to the cluster. Click OK to close the New Host dialog. Now click Configure Later to close the New Cluster Guide Me dialog and return to the Clusters tab.

1. Install nfs-utils

   NFS functionality is provided by the nfs-utils package. Before file shares can be created, check that the package is installed by querying the RPM database for the system:

   $ rpm -qi nfs-utils

   If the nfs-utils package is installed then the package information will be displayed. If no output is displayed then the package is not currently installed. Install it using yum while logged in as the root user:

   # yum install nfs-utils

2. Configure Boot Scripts

   To ensure that NFS shares are always available when the system is operational both the nfs and rpcbind services must start at boot time. Use the chkconfig command while logged in as root to modify the boot scripts.

   # chkconfig --add rpcbind
   # chkconfig --add nfs
   # chkconfig rpcbind on
   # chkconfig nfs on

   Once the boot script configuration has been done, start the services for the first time.

   # service rpcbind start
   # service nfs start

3. Create Directory

   Create the directory you wish to share using NFS.

   # mkdir /exports/iso

   Replace /exports/iso with the name, and path of the directory you wish to use.

4. Export Directory

   To be accessible over the network using NFS the directory must be exported. NFS exports are controlled using the /etc/exports configuration file. Each export path appears on a separate line followed by a tab character and any additional NFS options. Exports to be attached to the Red Hat Enterprise Virtualization Manager must have the read, and write, options set.
   To grant read, and write access to /exports/iso using NFS for example you add the following line to the /etc/exports file.

   /exports/iso       *(rw)

   Again, replace /exports/iso with the name, and path of the directory you wish to use.

5. Reload NFS Configuration

   For the changes to the /etc/exports file to take effect the service must be told to reload the configuration. To force the service to reload the configuration run the following command as root:

   # service nfs reload

6. Set Permissions

   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 /exports/iso is the directory to be used as an NFS share.

   # chown -R 36:36 /exports/iso

   The permissions on the directory must be set to allow read and write access to both the owner and the group. The owner should also have execute access to the directory. The permissions are set using the chmod command. The following command arguments set the required permissions on the /exports/iso directory.

   # chmod 0755 /exports/iso

1. Click the Storage tab. The Storage list and toolbar display.
2. Click New Domain.
3. The New Storage dialog box displays.

   

   Figure 11.2. NFS Storage

   
   
4. Configure the following options:

   Name: Enter a suitably descriptive name.

   Data Center: Select the required Data Center from the drop-down list.

   Domain Function/ Storage Type: In the drop down menu, select Data → NFS. The storage domain types which are not compatible with the Default data center are grayed out. After you select your domain type, the Export Path field appears.

   Export path: Enter the IP address or a resolvable hostname of the chosen host. The export path should be in the format of 192.168.0.10:/Images/ISO or domain.example.com:/Images/ISO

   Use Host: Select any of the hosts from the drop down menu. Only hosts which belong in the pre-selected data center will display in this list.

   Active Host Required

   All communication to the storage domain is via the selected host and not directly from the Red Hat Enterprise Virtualization Manager. At least one active host must exist in the system, and be attached to the chosen data center, before the storage is configured.
5. Click OK.

1. On the tree pane, select the Tree tab. On System, click the + icon to display the available data centers.
2. Select the Data Center to which the domain is to be added. The storage type of the data center selected determines the type of storage domains that can be added to it. To add an iSCSI data, or export, storage domain you must select an iSCSI data center. iSCSI storage domains can not be used for ISO storage domains.
3. Click the New Domain button.
4. Click New Storage. The New Storage dialog box displays.
5. From the Domain Function / Storage Type drop-down menu, select the appropriate storage type for the storage domain. The storage domain types that are not compatible with the chosen data center are not available.
6. Select an active host in the Use host field. To attach a domain, the name of an active host must be selected from the list of existing hosts. Only hosts that are attached to the selected Data Center are listed.

   Active Host Required

   All communication to the storage domain is via the selected host and not directly from the Red Hat Enterprise Virtualization Manager. At least one active host must exist in the system, and be attached to the chosen data center, before the storage is configured.
7. The Red Hat Enterprise Virtualization Manager is able to map either iSCSI targets to LUNs, or LUNs to iSCSI targets. The New Domain dialog automatically displays known targets with unused LUNs when iSCSI is selected as the storage type. If the target that you are adding storage from is not listed then you can use target discovery to find it, otherwise proceed to the next step.
   

   Figure 11.3. New Domain Dialog

   
   

   iSCSI Target Discovery

   • Click Discover Targets to enable target discovery options. The New Domain dialog automatically displays targets with unused LUNs when iSCSI is selected as the storage type. If the target that you are adding is not listed, click Discover Targets to enable target discovery options.
   • Enter the fully qualified domain name or IP address of the iSCSI host in the Address field.
   • Enter the port to connect to the host on when browsing for targets in the Port field. The default is 3260.
   • If the Challenge Handshake Authentication Protocol (CHAP) is being used to secure the storage, select the User Authentication check box. Enter the CHAP user name and password.
   • Click the Discover button.
8. Click the + button next to the desired target. This will expand the entry and display all unused LUNs attached to the target.
   

   Figure 11.4. iSCSI LUN Selection

   
   
9. Select the check box for each LUN that you are using to create the storage domain.
10. Click OK to create the storage domain.

Procedure 11.1. To Add FCP Storage:

1. Click the Storage tab. The Storage list and toolbar display.
2. Click New Domain.
3. The New Domain dialog box displays.

   

   Figure 11.5. Adding FCP Storage

   
   
4. Configure the following options:

   1. Name: Enter a suitably descriptive name.
   2. Data Center: Select the required Data Center from the drop-down list.
   3. Domain Function/ Storage Type: Select FCP.
   4. Use Host: Select the IP address of either the hypervisor or Red Hat Enterprise Linux host.

      Active Host Required

      All communication to the storage domain is via the selected host and not directly from the Red Hat Enterprise Virtualization Manager. At least one active host must exist in the system, and be attached to the chosen data center, before the storage is configured.
   5. The list of existing LUNs display. On the selected LUN, select the Add LUN check box to use it as the FCP data domain.
5. Click OK.