Pre-setup preparations are required to create and manage RHEL-KVM virtual machines as L-Servers of Resource Orchestrator.
For details on pre-setup preparations for RHEL-KVM environment, refer to the RHEL-KVM manual.
Red Hat Enterprise Linux 6 Virtualization Administration Guide
URL: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/index.html (As of February 2012) |
Red Hat Enterprise Linux 6 Virtualization Getting Started Guide
URL: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Getting_Started_Guide/index.html (As of February 2012) |
Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide
URL: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/index.html (As of February 2012) |
Preparations for Servers
In addition to the operations in "4.1.1.1 Preparations for Server Environments", the following operations are necessary.
Installation and configuration of the host OS
Storage Preparations
Check the following:
Volumes (LUNs) to assign to the admin OS have already been created
LUNs are used for virtual L-Server disks. Create the same number of LUNs as the number of necessary disks. The size of each LUN must be larger than the size of each disk.
Volumes (LUN) to allocate to cloning images have been already created
Cloning images are stored on LUNs. Create LUNs based on the number of cloning images to be created. The size of each LUN must be larger than the size of each cloning image.
Zoning and affinity have been set
When migrating VM guests for Virtual L-Servers, configure zoning and affinity, and set LUNs as shared disks.
Network Preparations
Check the following:
The configuration for the admin and public LANs has been designed
The network environment for the admin LAN is configured
The VLAN ID to allocate to the network resource has been configured
The virtual bridge has been configured beforehand
The MAC address range for the virtual network interface (VNIF) has been decided
Perform the following configuration:
In order to enable the use of virtual bridges, disable the NetworkManager service of the OS.
On the managed server, enable the NetworkManager service and then enable the network service.
Execute the following commands:
# service NetworkManager stop <RETURN> |
Edit the /etc/sysconfig/network-scripts/ifcfg-NIC_name file to change the value for NM_CONTROLLED to "no".
Example
Before editing
DEVICE="eth0" |
After editing
DEVICE="eth0" |
Restart the managed server.
Execute the following command:
# shutdown -r now <RETURN> |
Perform configuration to allow the managed server to use the VLAN.
Add "VLAN=yes" in the /etc/sysconfig/network file on the managed server using a text editor.
Example
Before editing
NETWORKING=yes |
After editing
NETWORKING=yes |
Restart the managed server.
Execute the following command:
# shutdown -r now <RETURN> |
When using GLS for automatic network configuration, configure GLS.
For details, refer to the PRIMECLUSTER Global Link Services manual.
Creating a virtual bridge
Create a virtual bridge beforehand.
When Using IBP
When using virtual L-Servers, connect the IBP uplink sets used for the public LAN and admin LAN to the VM host regardless of VIOM, after creating each IBP uplink set.
It is not necessary to use the same name for the uplink set and the name of the network resource.
Creating a Virtual Bridge
The virtual bridge is required on the admin OS, in order to connect the L-Server to the network.
For details on how to configure virtual bridges, refer to the manual for RHEL-KVM and "Manual Network Configuration" in "E.6.4 Setup".
