Versions Compared

Old Version 6

changes.mady.by.user Andy Kurth

Saved on

compared with

New Version 7

changes.mady.by.user Andy Kurth

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • eth0 - connected to the private VCL network (not used or referenced in these instructions)
  • eth1 - connected to the public network

Install VCL Components

Begin by completing the VCL installation instructions. Install all of the components on the same computer:

  1. VCL 2.2.1 Database Installation
  2. VCL 2.2.1 Web Code Installation
  3. VCL 2.2.1 Management Node Installation

VMware Server 2.0 Configuration

Remove Existing Virtualization Components

Tip

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:

...

After removing the Xen kernel, reboot the computer:

Tip

reboot

...

Download VMware Server 2.0

Download the latest VMware Server 2.0 RPM from http://www.vmware.com

Info

These instructions assume you saved the RPM into /root

Install VMware Server

...

2.0

Tip

rpm -ivh /root/VMware-server-2.0.2-203138.x86_64.rpm

...

Tip

/sbin/service vmware restart

Configure

...

the sshd Service to Listen on the Virtual Private Network

Tip

vi /etc/ssh/hostssshd_config

Add the entries in boldfollowing line to the end of the file:

Tip

ListenAddress

Panel

127.0.0.1 localhost
192.168.0.1 localvmhost
192.168.1.1 vmguest-1

Configure the sshd Service to Listen on the Virtual Private Network

Tip

vi /etc/ssh/sshd_config

Add the following line to the end of the file:

Tip

ListenAddress 192.168.0.1

Restart the sshd service on the Restart the sshd service on the management node:

Tip

/sbin/service sshd restart

...

Tip

ssh -i /etc/vcl/vcl.key localvmhost 'ls /'

Configure

...

the DHCP Service

Install dhcp if it is not already installed:

...

Tip

/sbin/service dhcpd start

Configure the VCL Database for the VM Guest and Host

  • 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

Install VCL Components

Begin by completing the VCL installation instructions. Install all of the components on the same computer:

  1. VCL 2.2.1 Database Installation
  2. VCL 2.2.1 Web Code Installation
    Note

    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 2.2.1 Management Node Installation

Add the Management Node to the Database

  • Click Management Nodes > Edit Management Node Information
  • Click 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 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 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
    • State: vmhostinuse
      Owner: admin
    • Platform: i386
    • Schedule: VCL 24x7
    • RAM: 1024
      Info

      The hardware settings have no effect for a VM host computer

    • No Processors: 1
    • Processor Speed: 2000
    • Network Speed: 1000Network Speed: 100
    • Type: blade
    • Provisioning engine: xCAT 12.x
      Note: the
      Info

      The computer Type and Provisioning engine values don't matter for the localvmhost computer in this test environment because vcld isn't provisioning

      it

      or reloading it

    • Computer Groups: all vm host computers 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 Add VM guest computer: Manage Computers - > Edit Computer Information - > Submit
  • Click the Add Multiple checkbox
  • Click -> Add
    • Hosthame: vmguest-%
    • Start value: 1
    • End value: 10
    • Start IP Address: current public ip address used by Windows XP VM
    • State: available
    • Owner: admin
    • Platform: i386
    • Schedule: VCL 24x7
      • 192.168.1.1
    • End IP Address: 192.168.1.10
    • Start private IP Address: 192.168.1.1
    • End private IP Address: 192.168.1.10
    • Start MAC Address: 00:50:56:1a:01:01
    • State: maintenance
    • Owner: admin
    • Platform: i386
    • Schedule: VCL 24x7
    • RAM: 4096
      Info

      The hardware settings have no effect for a VM host computer

      RAM: 1024

    • No Processors: 1
    • Processor Speed: 2000
    • Network Speed: 100 1000
    • Type: virtualmachine
    • Provisioning engine: VMWare VMware
    • 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
      • All VM Computers
      • allComputers
      • newvmimages
  • Click Confirm Compute
  • Click Submit
  • Enter the private address for the management node: 127.0.0.1
  • Click: Download Data, you should see the following output:
    No Format
    
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 127.0.0.1;
	next-server 127.0.0.1;
}
	host vmguest-2 {...

Configure dhcpd.conf

  • Edit the /etc/dhcpd.conf file on the computer:
    Tip

    vi /etc/dhcpd.conf

  • Paste the output generated by the website into the dhcpd.conf file under the option routers 192.168.0.1; line and save the file
  • Restart the dhcpd service:
    Tip

    /sbin/service dhcpd restart

Configure /etc/hosts

  • Modify the /etc/hosts file to include entries for the VM host and VM computers:
    Tip

    vi /etc/hosts

  • Add the entries in bold:
    Panel

    127.0.0.1 localhost
    192.168.0.1 localvmhost
    192.168.1.1 vmguest-1
    192.168.1.2 vmguest-2
    192.168.1.3 vmguest-3
    192.168.1.4 vmguest-4
    192.168.1.5 vmguest-5
    192.168.1.6 vmguest-6
    192.168.1.7 vmguest-7
    192.168.1.8 vmguest-8
    192.168.1.9 vmguest-9
    192.168.1.10 vmguest-10

Configure the VM Host Profile

  • Virtual Hosts > VM Host Profiles tab Configure the VM host profile: Virtual Hosts -> VM Host Profiles tab - > VMware Server 2.x - local storage - > configure 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
  • 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