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.
Begin by completing the installation instructions for the VCL components:
You will need the following:
The following instructions assume the following locations on the management node:
These instructions assume you have root access and are using a bash shell: {panel} sudo bash {panel}
Create the following computer groups: Go to Manage Groups -> Resource Groups -> Add ** all vm host computers ** all vm guest computers
Map all computer groups to management node group ** Management Nodes -> Edit Management Node Mapping
Configure the management node to check in with the database ** Management Nodes -> Edit Management Node Information -> Add *** Hostname: localhost *** IP Address: 127.0.0.1 *** Owner: admin *** 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
Add VM host computer: ** Manage Computers -> Edit Computer Information -> Submit -> Add *** Hosthame: localvmhost *** IP Address: 192.168.0.1 (NOTE: there is currently a bug restricting the size of the field, so hopefully one octet has less than 3 digits.) *** State: available {}Note: do not attempt to add the computer in the maintenance state because of the following issue: https://issues.apache.org/jira/browse/VCL-189 *** Owner: admin *** Platform: i386 *** Schedule: VCL 24x7 *** RAM: 1024 *** No Processors: 1 *** Processor Speed: 2000 *** Network Speed: 100 *** Type: blade *** Provisioning engine: xCAT 1.x {}Note: the Type and Provisioning engine values don‘t matter for the localvmhost computer in this test environment because vcld isn’t provisioning it *** Computer Groups: all vm host computers
Add VM guest computer: ** Manage Computers -> Edit Computer Information -> Submit -> Add *** Hosthame: vmguest-1 *** IP Address: current public ip address used by Windows XP VM *** State: available *** Owner: admin *** Platform: i386 *** Schedule: VCL 24x7 *** RAM: 1024 *** No Processors: 1 *** Processor Speed: 2000 *** Network Speed: 100 *** Type: virtualmachine *** Provisioning engine: VMWare Server Provisioning *** Computer Groups: all vm guest computers
Note the fix for the IP address bug is recorded here: https://issues.apache.org/jira/browse/VCL-193
Configure the VM guest's MAC address in the computer table in the database (as there currently does not seem to be a way to do this through the UI): ** eth0: 00:50:56:1a:01:01 ** eth1: 00:50:56:1a:01:02
Configure the VM host profile: ** Virtual Hosts -> VM Host Profiles tab -> VMware GSX standard -> configure Profile *** Virtual Switch 0: VMnet1 *** Virtual Switch 1: VMnet0
Change state of localvmhost to vmhostinuse (edit the database directly, do not use the Virtual Hosts utility on the website)
Assign vm guests to localvmhost
Create node in priviledge tree ** Name: VM image access ** Add resource groups: *** all vm guest computers *** all vm guest images
{panel} yum groupremove “Virtualization” -y {panel}
VMWare Server cannot be installed on a computer running a Xen kernel. To determine if a Xen kernel is being used: {panel} uname -a {panel}The following output indicates a Xen kernel is being used: {panel} Linux blade1g6-4 2.6.18-92.el5{color:#cc0000}{}xen{}{color} #1 SMP Tue Jun 10 19:20:18 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux {panel}If “xen” appears in the output of the previous command, replace the Xen Kernel with the following commands: {panel} yum update ecryptfs-utils -y yum install kernel kernel-devel -y yum remove xen kernel-xen -y {panel}Check the grub.conf file to make sure it is not configured to boot using the Xen Kernel {panel} less /boot/grub/grub.conf {panel}The grub.conf file should {color:#cc0000}{}NOT{}{color} look like this: {panel} # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/sda3 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-92.el5{color:#cc0000}{}xen{}{color}) root (hd0,0) kernel /xen.gz-2.6.18-92.el5 module /vmlinuz-2.6.18-92.el5{color:#cc0000}{}xen{}{color} ro root=LABEL=/ pci=nommconf module /initrd-2.6.18-92.el5xen.img {panel}The grub.conf file {color:#336600}{}SHOULD{}{color} look like this: {panel} # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/sda3 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-128.1.14.el5) root (hd0,0) kernel /vmlinuz-2.6.18-128.1.14.el5 ro root=LABEL=/1 pci=nommconf initrd /initrd-2.6.18-128.1.14.el5.img {panel}After removing the Xen kernel, reboot the computer: {panel} reboot {panel}
Download the latest VMware Server 1.x RPM from http://www.vmware.com (Note: these instructions assume you saved the RPM into /install)
Install the VMware Server RPM: {panel} rpm -ivh /install/VMware-server-1.0.8-126538.i386.rpm {panel}Configure VMware Server: {panel} vmware-config.pl {panel}{}Note: if you receive an error message you may need to install or update some libraries and then run vmware-config.pl again: {panel} yum install glibc-devel -y yum install glibc -y yum install libXtst-devel -y {panel}VMware networking should be configured as follows after answering the questions asked by vmware-config.pl
The following lists the sequence of answers to be entered after issuing the vmware-config.pl command:
Verify the host-only network was configured correctly: {panel} /sbin/ifconfig {panel}You should see a vmnet1 interface using IP address 192.168.0.1: {panel} vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01 inet addr:192.168.0.1 Bcast:192.168.255.255 Mask:255.255.0.0 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) {panel}Restart the vmware service (/sbin/service vmware restart), you should see the following: {panel} Starting VMware services: Virtual machine monitor [ OK ](-ok-.html) Virtual ethernet [ OK ](-ok-.html) Bridged networking on /dev/vmnet0 [ OK ](-ok-.html) Host-only networking on /dev/vmnet1 (background) [ OK ](-ok-.html) Starting VMware virtual machines... [ OK ](-ok-.html) {panel}
Modify the /etc/hosts file to include entries for the VM host and guest computers: {panel} vi /etc/hosts {panel}Add the entries in bold: {panel} 127.0.0.1 localhost 192.168.0.1 localvmhost 192.168.1.1 vmguest-1 {panel}
h2. Configure the sshd Service to Listen on the Virtual Private Network
{panel} vi /etc/ssh/sshd_config {panel}Add the following line to the end of the file: {panel} ListenAddress 192.168.0.1 {panel}Restart the sshd service on the management node: {panel} /sbin/service sshd restart {panel}
Add the VM host's public key to its own authorized_keys file to allow it to SSH to itself without a password prompt: {panel} cat /etc/vcl/vcl.key.pub >> /root/.ssh/authorized_keys {panel}The following command should execute without having to enter a password: {panel} ssh localvmhost ‘ls /’ {panel}
Configure the keys column in the managementnode table in the VCL database
Configure the vcld.conf file to use vcl.key: {panel} vi /etc/vcl/vcld.conf {panel}Modify all of the IDENTITY lines to specify the vcl.key file: {panel} IDENTITY_blade_linux=/etc/vcl/vcl.key IDENTITY_solaris_lab=/etc/vcl/vcl.key IDENTITY_linux_lab=/etc/vcl/vcl.key IDENTITY_blade_win=/etc/vcl/vcl.key {panel}
Save a copy of the original dhcpd.conf file: {panel} mv /etc/dhcpd.conf /etc/dhcpd.conf.orig {panel}Configure the dhcpd.conf file: {panel} vi /etc/dhcpd.conf {panel}The dhcpd.conf file should contain the following:
ddns-update-style none; shared-network vmnet1 {
������� subnet 192.168.0.0 netmask 255.255.0.0 {
��������������� ignore unknown-clients;
��������������� option routers 192.168.0.1;
��������������� host vmguest-1 {
����������������������� option host-name "vmguest-1";
����������������������� hardware ethernet 00:50:56:1a:01:01;
����������������������� fixed-address 192.168.1.1;
����������������������� filename "/tftpboot/pxelinux.0";
����������������������� option dhcp-server-identifier 192.168.0.1;
����������������������� next-server 192.168.0.1;
��������������� }
}
}
The DHCP daemon should only listen on the virtual private network (vmnet1) to avoid conflicts with other production VCL networks. Configure the dhcpd service startup script to only listen on the vmnet1 interface: {panel} vi /etc/init.d/dhcpd {panel}Add vmnet1 the to the daemon $dhcpd line as shown:
start() {
[ -x $dhcpd ]
|| return 5 [ -f $conf ] || return 6 pidofproc $prog >/dev/null 2>&1 RETVAL=$? [ $RETVAL -eq 0 ] && return $RETVAL echo -n $"Starting $prog: " daemon $dhcpd vmnet1 $DHCPDARGS 2>/dev/null RETVAL=$? echo [ $RETVAL = 0 ] && touch $lockfile return $RETVAL }
Configure the dhcpd service to automatically start at runlevels 3-5: {panel} /sbin/chkconfig --level 345 dhcpd on {panel}Start the dhcpd service: {panel} /sbin/service dhcpd start {panel}