Configuring a Standalone VCL Environment using VMware Server 2.0

Size: px

Start display at page:

Download "Configuring a Standalone VCL Environment using VMware Server 2.0"

Melvin Charles Grant
5 years ago
Views:

1 Configuring a Standalone VCL Environment using VMware Server 2.0 DISCLAIMER! This document provides instuctions for configuring a standalone VCL environment running on a single computer which is able to provision VCL reservations using VMware. It is only provided to help you understand how the various components of VCL operate. This document DOES NOT describe how to configure a production VCL environment. The environment described in this document can however be used to learn, test, and help develop VCL. Gather Required Files & Information Requirements VMware Server 2.x RPM Installer - These instructions assume the VMware Server RPM has been downloaded to the following location on the management node: /root/vmware-server x86_64.rpm VMware Server 2.x serial number - A serial number can be obtained when you download VMware Server 2.0 from vmware.com. You will need to register. Assumptions These instructions assume you are logged in to the management node as root These instructions assume you are using a bash shell. Networking The computer used to host the standalone VCL environment described in these instructions only needs a single network interface. These instructions will also work if it has multiple interfaces. The computer used to create these instructions had the following interfaces: eth0 - connected to the private VCL network (not used or referenced in these instructions) eth1 - connected to the public network VMware Server 2.0 Configuration Remove Existing Virtualization Components yum groupremove "Virtualization" -y Make Sure The Host Computer Is Not Running A Xen Kernel VMWare Server cannot be installed on a computer running a Xen kernel. To determine if a Xen kernel is being used: uname -a The following output indicates a Xen kernel is being used: Linux blade1g el5 xen #1 SMP Tue Jun 10 19:20:18 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux If "xen" appears in the output of the previous command, replace the Xen kernel: yum update ecryptfs-utils -y yum install kernel kernel-devel -y yum remove xen kernel-xen -y

2 Check the grub.conf file to make sure it is not configured to boot using the Xen Kernel less /boot/grub/grub.conf The grub.conf file should NOT look like this: title CentOS ( el5 xen) module /vmlinuz el5 xen ro root=label=/ pci=nommconf After removing the Xen kernel, reboot the computer: reboot Download VMware Server 2.0 Download the latest VMware Server 2.0 RPM from These instructions assume you saved the RPM into /root Install VMware Server 2.0 rpm -ivh /root/vmware-server x86_64.rpm Configure VMware Server: vmware-config.pl Answer the questions asked by vmware-config.pl as follows: Do you accept? (yes/no) yes Do you want networking for your virtual machines? (yes/no/help) yes Configuring a bridged network for vmnet0. Please specify a name for this network. Bridged Your computer has multiple ethernet network interfaces available: eth0, eth1. Which one do you want to bridge to vmnet0? eth1 ( this should be set to the public interface) The following bridged networks have been defined:. vmnet0 is bridged to eth1 Do you wish to configure another bridged network? (yes/no) no Do you want to be able to use NAT networking in your virtual machines? (yes/no) no Do you want to be able to use host-only networking in your virtual machines? yes Configuring a host-only network for vmnet1. Please specify a name for this network. HostOnly Do you want this program to probe for an unused private subnet? (yes/no/help) no What will be the IP address of your host on the private network? What will be the netmask of your private network? The following host-only networks have been defined:. vmnet1 is a host-only network on private subnet Do you wish to configure another host-only network? (yes/no) no Please specify a port for remote connections to use: 902 Please specify a port for standard http connections to use: 8222 Please specify a port for secure http (https) connections to use: 8333 The current administrative user for VMware Server is ''. Would you like to specify a different administrator? no Using root as the VMware Server administrator. In which directory do you want to keep your virtual machine files? /var/lib/vmware/virtual Machines The path "/var/lib/vmware/virtual Machines" does not exist currently. This program is going to create it, including needed parent directories. Is this what you want? yes Please enter your 20-character serial number. <Enter the serial number you received from VMware> In which directory do you want to install the VMware VIX API binary files? /usr/bin In which directory do you want to install the VMware VIX API library files? /usr/lib/vmware-vix/lib The path "/usr/lib/vmware-vix/lib" does not exist currently. This program is going to create it, including needed parent directories. Is this what you want? yes In which directory do you want to install the VMware VIX API document pages? /usr/share/doc/vmware-vix

3 The path "/usr/share/doc/vmware-vix" does not exist currently. This program is going to create it, including needed parent directories. Is this what you want? yes If you receive an error message when you execute vmware-config.pl you may need to install or update the following libraries and then run vmware-config.pl again: yum install glibc-devel -y yum install glibc -y yum install libxtst-devel -y Verify the host-only network was configured correctly: /sbin/ifconfig You should see a vmnet1 interface using IP address : vmnet1 Link encap:ethernet HWaddr 00:50:56:C0:00:01 inet addr: Bcast: Mask: inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Restart the vmware service: /sbin/service vmware restart You should see the following: Starting VMware services: Virtual machine monitor [ OK ] Virtual ethernet [ OK ] Bridged networking on /dev/vmnet0 [ OK ] Host-only networking on /dev/vmnet1 (background) [ OK ] Starting VMware virtual machines... [ OK ] Fix VMware Server 2.0 glibc Problem VMware Server 2.0 will not run reliably if the version of glibc installed on the host is newer than This problem is known to affect recent versions of Red Hat Enterprise Linux and CentOS. If not corrected, VMware Server will crash intermittently and the VMware administration web pages will lock up or fail to load. Check the version of glib installed on the VMware host: yum list installed glibc You will need to configure VMware to use glibc if the version installed on the host is newer than : Installed Packages glibc.i installed glibc.x86_ installed For CentOS, you will need to download the glibc RPM included with CentOS 5.3. This is available from vault.centos.org: For 32-bit CentOS installations: For 64-bit CentOS installations:

4 Create a temp directory and cd to it: mkdir /tmp/glibc ; cd /tmp/glibc Download the glibc RPM (change the URL accordingly): wget Extract the cpio archive from the glibc RPM: rpm2cpio glibc el5_3.1.x86_64.rpm cpio --extract --make-directories Create the following directory: mkdir /usr/lib/vmware/lib/libc.so.6 Copy the following file to the new directory: cp /tmp/glibc/lib64/libc-2.5.so /usr/lib/vmware/lib/libc.so.6/libc.so.6 Make a backup of the original vmware-hostd file: cp /usr/sbin/vmware-hostd /root/vmware-hostd.orig Edit vmware-hostd: vi /usr/sbin/vmware-hostd Navigate to the bottom of the file. You should see the following as the last line: eval exec "$DEBUG_CMD" "$binary" "$@" Add the following export line immediately before the last eval line in vmware-hostd: export LD_LIBRARY_PATH=/usr/lib/vmware/lib/libc.so.6:$LD_LIBRARY_PATH eval exec "$DEBUG_CMD" "$binary" "$@" The following sed command can also be used to add the line to vmware-hostd: Do not both manually edit vmware-hostd and run the following sed command sed -i -r -e "s/(eval exec.*)/export LD_LIBRARY_PATH=\/usr\/lib\/vmware\/lib\/libc.so.6:\$LD_LIBRARY_PATH\n\1/" /usr/sbin/vmwarehostd Restart the vmware service:

5 /sbin/service vmware restart Login to VMware At this point you should be able to log in as root to the VMware Infrastructure Web Access page: * Install VCL Components Begin by completing the VCL installation instructions. Install all of the components on the same computer: VCL Database Installation VCL Web Code Installation Complete the Web Code Installation steps up to the Add a Management Node to the Database section. Use the instructions below to add the management node, VM host computer, and VM computers to the VCL database. 3. VCL Management Node Installation Add the Management Node to the Database Click Management Nodes > Edit Management Node Information Click Add Hostname: localhost IP Address: Owner: admin@local State: available Predictive Loading Module: Predictive Loading Level 0 Module Check-in Interval: 5 Install Path: /install End Node SSH Identitiy Key Files: /etc/vcl/vcl.key SSH Port for this node: 22 Enable Image Library: no Click Confirm Management Node Add the VMware Host Computer to the VCL database Click Manage Computers > Add Single Computer > Submit Hosthame: localvmhost IP Address: State: vmhostinuse Owner: admin Platform: i386 Schedule: VCL 24x7 RAM: 1024 No Processors: 1 Processor Speed: 2000 Network Speed: 1000 Type: blade Provisioning engine: xcat 2.x The computer Type and Provisioning engine values don't matter for the localvmhost computer in this test environment because vcld isn't provisioning or reloading it Computer Groups: allcomputers Click Confirm Computer Click Submit Select a VM Host Profile to be used on this computer: VMware Server 2.x - local storage Click Add Computer Add the Virtual Machine Computers to the VCL Database Click Manage Computers > Edit Computer Information > Submit Click the Add Multiple checkbox Click Add

6 Hosthame: vmguest-% Start value: 1 End value: 10 Start IP Address: End IP Address: Start private IP Address: End private IP Address: Start MAC Address: 00:50:56:1a:01:01 State: maintenance Owner: admin Platform: i386 Schedule: VCL 24x7 RAM: 4096 No Processors: 1 Processor Speed: 2000 Network Speed: 1000 Type: virtualmachine Provisioning engine: VMware Computer Groups: All VM Computers allcomputers newvmimages Click Confirm Compute Click Submit Enter the private address for the management node: Click: Download Data, you should automatically generated dhcpd.conf file entries. Keep this web page open and continue with the following instructions. Install & Configure the DHCP Service VMware Server installs its own DHCP service ( vmnet-dhcpd). This service starts automatically when the vmware service is running. Either the VMware vmnet-dhcpd service or the normal dhcpd service installed on the Linux operating system can be used to assign IP addresses to the VMs' private interfaces. The instructions below explain how to disable vmnet-dhcpd and configure dhcpd. Disable vmnet-dhcpd Stop the vmware service: /sbin/service vmware stop Edit the following file: /etc/vmware/locations Find all lines beginning with answer VNET_1_DHCP yes and change yes to no: answer VNET_1_DHCP no Start the vmware service: /sbin/service vmware start Install the DHCP Service Install dhcp if it is not already installed: yum install dhcp -y The DHCP daemon should only listen on the virtual private network (vmnet1) to avoid conflicts with other networks. Configure the dhcpd service startup script to only listen on the vmnet1 interface:

7 vi /etc/sysconfig/dhcpd Add vmnet1 the to the DHCPDARGS line: # Command line options here DHCPDARGS=vmnet1 Configure the dhcpd service to automatically start at runlevels 3-5: /sbin/chkconfig --level 345 dhcpd on Start the dhcpd service: /sbin/service dhcpd start Configure dhcpd.conf Edit the /etc/dhcpd.conf file on the computer: vi /etc/dhcpd.conf Paste the following into the dhcpd.conf file and save the file: The host sections below should be identical the the output displayed on the VCL website after you added the VM computers. ddns-update-style none; shared-network vmnet1 { subnet netmask { ignore unknown-clients; option routers ; host vmguest-1 { option host-name "vmguest-1"; hardware ethernet 00:50:56:1a:01:01; fixed-address ; host vmguest-2 { option host-name "vmguest-2"; hardware ethernet 00:50:56:1a:01:03; fixed-address ; host vmguest-3 { option host-name "vmguest-3";

8 hardware ethernet 00:50:56:1a:01:05; fixed-address ; host vmguest-4 { option host-name "vmguest-4"; hardware ethernet 00:50:56:1a:01:07; fixed-address ; host vmguest-5 { option host-name "vmguest-5"; hardware ethernet 00:50:56:1a:01:09; fixed-address ; host vmguest-6 { option host-name "vmguest-6"; hardware ethernet 00:50:56:1a:01:0b; fixed-address ; host vmguest-7 { option host-name "vmguest-7"; hardware ethernet 00:50:56:1a:01:0d; fixed-address ; host vmguest-8 { option host-name "vmguest-8"; hardware ethernet 00:50:56:1a:01:0f; fixed-address ; host vmguest-9 {

9 option host-name "vmguest-9"; hardware ethernet 00:50:56:1a:01:11; fixed-address ; host vmguest-10 { option host-name "vmguest-10"; hardware ethernet 00:50:56:1a:01:13; fixed-address ; Restart the dhcpd service: /sbin/service dhcpd restart Configure /etc/hosts Modify the /etc/hosts file to include entries for the VM host and VM computers: vi /etc/hosts Add the following entries: localvmhost vmguest vmguest vmguest vmguest vmguest vmguest vmguest vmguest vmguest vmguest-10 Configure the sshd Service to Listen on the Virtual Private Network vi /etc/ssh/sshd_config Add the following line to the end of the file: ListenAddress Restart the sshd service on the management node: /sbin/service sshd restart

10 Configure The VM Host To Be Able To SSH To Itself If you have not already generated an SSH identity key on the management node to be used to login to the computers the management node controls, run the following command to generate a new key: mkdir /etc/vcl ; ssh-keygen -t rsa -f "/etc/vcl/vcl.key" -N '' -b C "VCL root account on $HOSTNAME" Add the VM host's public key to its own authorized_keys file to allow it to SSH to itself without a password prompt: cat /etc/vcl/vcl.key.pub >> /root/.ssh/authorized_keys The following command should execute without having to enter a password: ssh -i /etc/vcl/vcl.key localvmhost 'ls /' Configure the VM Host Profile Virtual Hosts > VM Host Profiles tab > VMware Server 2.x - local storage > Configure Profile Virtual Switch 0: HostOnly Virtual Switch 1: Bridged Assign the VM Computers to the VM Host Virtual Hosts > VM Hosts tab Select localvmhost Click Configure Host Set VM limit to 10 Select vmguest-1...vmguest-10 under Unassigned VMs Click Add Create a Base Image Proceed to follow the instructions to create a Windows or Linux base image.

Network Configuration for Cisco UCS Director Baremetal Agent

Network Configuration for Cisco UCS Director Baremetal Agent This chapter contains the following sections: About the Network Configuration Options, page 1 Single Network for Management and PXE, page 1