Versions Compared

Key

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

...

Requirements

  • VMware Server 2.x RPM installation fileInstaller - These instructions assume the VMware Server RPM has been downloaded to the following location on the management node:
    /root/VMware-server-2.0.2-203138.x86_64.rpm
  • VMware Server 2.x serial number - A serial number can be obtained by registering at 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 instructions assume the management node has 2 network interfaces:

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
  • eth0 - connected to the private VCL network
  • eth1 - connected to the public network

Install VCL Components

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

  1. VCL 2.

...

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

Remove Remove Existing Virtualization Components

...

  • 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? 192.168.0.1
    • What will be the netmask of your private network? 255.255.0.0
      The following host-only networks have been defined:
      . vmnet1 is a host-only network on private subnet 192.168.0.0.
    • 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
  • 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 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:

Tip

mkdir /etc/vcl ; ssh-keygen -t rsa -f "/etc/vcl/vcl.key" -N '' -b 1024 -C "VCL root account on $HOSTNAME" 

...

Tip

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

Configure

...

The DHCP Service

Install dhcp if it is not already installed:

Tip

yum install dhcp -y

Configure the keys column in the managementnode table in the VCL database

  • Edit the managementnode table in the database: set the keys column to /etc/vcl/vcl.key

...

 


Save a copy of the original dhcpd.conf file:

...

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:

Tip

vi /etc/init.dsysconfig/dhcpd

Add vmnet1 the to the daemon $dhcpd DHCPDARGS line as shown:

No Format
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
}# Command line options here
DHCPDARGS=vmnet1

Configure the dhcpd service to automatically start at runlevels 3-5:

...