You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@vcl.apache.org by jf...@apache.org on 2013/01/08 17:37:56 UTC
svn commit: r1430372 [4/11] - /vcl/site/trunk/content/confluence_export/
Added: vcl/site/trunk/content/confluence_export/configuring-a-standalone-vcl-environment-using-vmware-server-1.x.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/configuring-a-standalone-vcl-environment-using-vmware-server-1.x.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/configuring-a-standalone-vcl-environment-using-vmware-server-1.x.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/configuring-a-standalone-vcl-environment-using-vmware-server-1.x.mdtext Tue Jan 8 16:37:53 2013
@@ -0,0 +1,442 @@
+Title: Configuring a Standalone VCL Environment using VMware Server 1.x
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer1.x-{color:#ff0000}DISCLAIMER\!{color}"></a>
+## {color:#ff0000}DISCLAIMER\!{color}
+
+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.
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer1.x-InstallVCLComponents"></a>
+## Install VCL Components
+
+Begin by completing the installation instructions for the VCL components:
+
+* [Database](database-configuration.html)
+* [Web server](web-code-installation.html)
+* [Management node](management-node-installation.html)
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer1.x-GatherRequiredFiles&Information"></a>
+## Gather Required Files & Information
+
+You will need the following:
+* VMware Server 1.x RPM installation file
+* VMWare Server 1.x serial number
+
+The following instructions assume the following locations on the management
+node:
+* VMWare Server RPM: /install/VMware-server-1.0.8-126538.i386.rpm
+
+These instructions assume you have root access and are using a bash shell:
+{panel}
+sudo bash
+{panel}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer1.x-Configure theVCLDatabasefortheVMGuestandHost "></a>
+## 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
+
+* 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](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](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
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer1.x-RemoveExistingVirtualizationComponents"></a>
+## Remove Existing Virtualization Components
+
+{panel}
+yum groupremove "Virtualization" \-y
+{panel}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer1.x-MakeSureTheHostComputerIsNotRunningAXenKernel"></a>
+## 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:
+{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}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer1.x-InstallVMwareServer"></a>
+## Install VMware Server
+
+Download the latest VMware Server 1.x RPM from [http://www.vmware.com](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
+* vmnet0 is bridged to eth1
+* vmnet1 is a host-only network on private subnet 192.168.0.0
+
+The following lists the sequence of answers to be entered after issuing the
+vmware-config.pl command:
+1. Press *ENTER* to view the license agreement, scroll to the bottom, type
+*yes* and press *ENTER*
+1. In which directory do you want to install the mime type icons?
+\[/usr/share/icons\](/usr/share/icons\.html)
+ *ENTER*
+1. What directory contains your desktop menu entry files?
+These files have a .desktop file extension. \[/usr/share/applications\](/usr/share/applications\.html)
+ *ENTER*
+1. In which directory do you want to install the application's icon?
+\[/usr/share/pixmaps\](/usr/share/pixmaps\.html)
+ *ENTER*
+1. None of the pre-built vmmon modules for VMware Server is suitable for
+your
+running kernel. Do you want this program to try to build the vmmon
+module for
+your system (you need to have a C compiler installed on your system)? \[yes\](yes\.html)
+ *ENTER*
+1. What is the location of the directory of C header files that match your
+running
+kernel? \[/lib/modules/2.6.18-128.1.14.el5/build/include\](/lib/modules/2.6.18-128.1.14.el5/build/include\.html)
+ *ENTER*
+1. Do you want networking for your virtual machines? (yes/no/help) \[yes\](yes\.html)
+ *ENTER*
+1. Your computer has multiple ethernet network interfaces available: eth0,
+eth1,
+virbr0. Which one do you want to bridge to vmnet0? \[eth0\](eth0\.html)
+ *eth1*
+1. Do you wish to configure another bridged network? (yes/no) \[no\](no\.html)
+ *ENTER*
+1. Do you want to be able to use NAT networking in your virtual machines?
+(yes/no)
+\[yes\](yes\.html)
+ *no*
+1. Do you want to be able to use host-only networking in your virtual
+machines?
+\[no\](no\.html)
+ *yes*
+1. Do you want this program to probe for an unused private subnet?
+(yes/no/help)
+\[yes\](yes\.html)
+ *no*
+1. What will be the IP address of your host on the private
+network? *192.168.0.1*
+1. What will be the netmask of your private network? *255.255.0.0*
+1. DHCP information is displayed, press *ENTER*
+1. Do you wish to configure another host-only network? (yes/no) \[no\](no\.html)
+ *ENTER*
+1. The default port : 902 is not free. We have selected a suitable
+alternative
+port for VMware Server use. You may override this value now.
+Remember to use this port when connecting to this server.
+Please specify a port for remote console connections to use \[904\](904\.html)
+ *ENTER*
+1. In which directory do you want to keep your virtual machine files?
+\[/var/lib/vmware/Virtual Machines\](/var/lib/vmware/virtual-machines\.html)
+ *ENTER*
+1. 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\](yes\.html)
+ *ENTER*
+1. Please enter your 20-character serial number
+Type XXXXX-XXXXX-XXXXX-XXXXX or 'Enter' to cancel: *enter the serial
+number*
+
+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}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer1.x-Configure/etc/hosts"></a>
+## Configure /etc/hosts
+
+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}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer1.x-ConfigureTheVMHostToBeAbleToSSHToItself"></a>
+## Configure The VM Host To Be Able To SSH To Itself
+
+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}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer1.x-Configurevcldtousevcl.key"></a>
+## Configure vcld to use vcl.key
+
+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*
+
+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}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer1.x-ConfigureThe DHCPService "></a>
+## Configure The DHCP Service
+
+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}
Added: vcl/site/trunk/content/confluence_export/configuring-a-standalone-vcl-environment-using-vmware-server-2.0.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/configuring-a-standalone-vcl-environment-using-vmware-server-2.0.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/configuring-a-standalone-vcl-environment-using-vmware-server-2.0.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/configuring-a-standalone-vcl-environment-using-vmware-server-2.0.mdtext Tue Jan 8 16:37:53 2013
@@ -0,0 +1,647 @@
+Title: Configuring a Standalone VCL Environment using VMware Server 2.0
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-{color:#ff0000}DISCLAIMER\!{color}"></a>
+## {color:#ff0000}DISCLAIMER\!{color}
+
+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.
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-GatherRequiredFiles&Information"></a>
+## Gather Required Files & Information
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-Requirements"></a>
+### 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-2.0.2-203138.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.
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-Assumptions"></a>
+### Assumptions
+
+* These instructions assume you are logged in to the management node as
+*root*
+* These instructions assume you are using a *bash* shell.
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-Networking"></a>
+### 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
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-VMwareServer2.0Configuration"></a>
+## VMware Server 2.0 Configuration
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-RemoveExistingVirtualizationComponents"></a>
+#### Remove Existing Virtualization Components
+
+{tip}
+yum groupremove "Virtualization" \-y
+{tip}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-MakeSureTheHostComputerIsNotRunningAXenKernel"></a>
+#### 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:
+{tip}
+uname \-a
+{tip}
+
+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:
+{tip}
+yum update ecryptfs-utils \-y
+yum install kernel kernel-devel \-y
+yum remove xen kernel-xen \-y
+{tip}
+
+Check the grub.conf file to make sure it is not configured to boot using
+the Xen Kernel
+{tip}
+less /boot/grub/grub.conf
+{tip}
+
+The grub.conf file should {color:#cc0000}{*}NOT{*}{color} look like this:
+{panel}
+title CentOS (2.6.18-92.el5{color:#cc0000}{*}xen{*}{color})
+module /vmlinuz-2.6.18-92.el5{color:#cc0000}{*}xen{*}{color} ro
+root=LABEL=/ pci=nommconf
+{panel}
+
+After removing the Xen kernel, reboot the computer:
+{tip}
+reboot
+{tip}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-DownloadVMwareServer2.0"></a>
+#### Download VMware Server 2.0
+
+Download the latest VMware Server 2.0 RPM from [http://www.vmware.com](http://www.vmware.com)
+{info}
+These instructions assume you saved the RPM into */root*
+{info}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-InstallVMwareServer2.0"></a>
+#### Install VMware Server 2.0
+{tip}
+rpm \-ivh /root/VMware-server-2.0.2-203138.x86_64.rpm
+{tip}Configure VMware Server:
+{tip}
+vmware-config.pl
+{tip}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?
+{color:#ff0000}{*}eth1{*}{color} {color:#000000}*(this should be set to the
+public interface)*{color}
+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? {color:#ff0000}{*}yes{*}{color}
+** Configuring a host-only network for vmnet1. Please specify a name for
+this network. {color:#ff0000}{*}HostOnly{*}{color}
+** Do you want this program to probe for an unused private subnet?
+(yes/no/help) {color:#ff0000}{*}no{*}{color}
+** What will be the IP address of your host on the private network?
+{color:#ff0000}{*}192.168.0.1{*}{color}
+** What will be the netmask of your private network?
+{color:#ff0000}{*}255.255.0.0{*}{color}
+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*
+
+{info}
+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:
+
+{tip}
+yum install glibc-devel \-y
+yum install glibc \-y
+yum install libXtst-devel \-y
+{tip}
+{info}
+Verify the host-only network was configured correctly:
+{tip}
+/sbin/ifconfig
+{tip}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:
+
+{tip}/sbin/service vmware restart
+{tip}
+
+You should see the following:
+{panel}
+Starting VMware services:
+Virtual machine monitor \[{color:#339966}OK{color} \]({color:#339966}ok{color}-\.html)
+Virtual ethernet \[{color:#339966}OK{color} \]({color:#339966}ok{color}-\.html)
+Bridged networking on /dev/vmnet0 \[{color:#339966}OK{color} \]({color:#339966}ok{color}-\.html)
+Host-only networking on /dev/vmnet1 (background) \[{color:#339966}OK{color} \]({color:#339966}ok{color}-\.html)
+Starting VMware virtual machines... \[{color:#339966}OK{color} \]({color:#339966}ok{color}-\.html)
+{panel}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-FixVMwareServer2.0glibcProblem"></a>
+#### 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 *2.5-34*. 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:
+
+{tip}
+yum list installed glibc
+{tip}
+
+You will need to configure VMware to use *glibc 2.5-34* if the version
+installed on the host is newer than *2.5-34*:
+
+
+ Installed Packages
+ glibc.i686 2.5-42 installed
+ glibc.x86_64 2.5-42 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: [http://vault.centos.org/5.3/updates/i386/RPMS/glibc-2.5-34.el5_3.1.i686.rpm](http://vault.centos.org/5.3/updates/i386/RPMS/glibc-2.5-34.el5_3.1.i686.rpm)
+* For 64-bit CentOS installations: [http://vault.centos.org/5.3/updates/x86_64/RPMS/glibc-2.5-34.el5_3.1.x86_64.rpm](http://vault.centos.org/5.3/updates/x86_64/RPMS/glibc-2.5-34.el5_3.1.x86_64.rpm)
+
+Create a temp directory and cd to it:
+{tip}
+mkdir /tmp/glibc ; cd /tmp/glibc
+{tip}
+
+Download the glibc RPM (change the URL accordingly):
+{tip}
+wget [http://vault.centos.org/5.3/updates/x86_64/RPMS/glibc-2.5-34.el5_3.1.x86_64.rpm](http://vault.centos.org/5.3/updates/x86_64/RPMS/glibc-2.5-34.el5_3.1.x86_64.rpm)
+{tip}
+
+Extract the cpio archive from the glibc RPM:
+{tip}
+rpm2cpio glibc-2.5-34.el5_3.1.x86_64.rpm \| cpio \--extract
+\--make-directories
+{tip}
+
+Create the following directory:
+{tip}
+mkdir /usr/lib/vmware/lib/libc.so.6
+{tip}
+
+Copy the following file to the new directory:
+{tip}
+cp /tmp/glibc/lib64/libc-2.5.so /usr/lib/vmware/lib/libc.so.6/libc.so.6
+{tip}
+
+Make a backup of the original vmware-hostd file:
+{tip}
+cp /usr/sbin/vmware-hostd /root/vmware-hostd.orig
+{tip}
+
+Edit vmware-hostd:
+{tip}
+vi /usr/sbin/vmware-hostd
+{tip}
+
+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:
+{tip}
+{note}
+Do not both manually edit *vmware-hostd* and run the following *sed*
+command
+{note}
+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/vmware-hostd
+{tip}
+
+Restart the *vmware* service:
+{tip}
+/sbin/service vmware restart
+{tip}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-LogintoVMware"></a>
+#### Login to VMware
+
+At this point you should be able to log in as *root* to the VMware
+Infrastructure Web Access page:
+\*{nolink:https://<IP address or hostname>:8333}\*
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-InstallVCLComponents"></a>
+## Install VCL Components
+
+Begin by completing the VCL installation instructions. Install
+all of the components on the same computer:
+1. [VCL:VCL 2.2.1 Database Installation](vcl:vcl-2.2.1-database-installation.html)
+1. [VCL:VCL 2.2.1 Web Code Installation](vcl:vcl-2.2.1-web-code-installation.html)
+{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.{note}
+1. [VCL:VCL 2.2.1 Management Node Installation](vcl:vcl-2.2.1-management-node-installation.html)
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-Add theManagementNodetotheDatabase"></a>
+#### Add the Management Node to the Database
+
+* Click *Management Nodes* > *Edit Management Node Information*
+* Click *Add*
+** Hostname: *localhost*
+** IP Address: *127.0.0.1*
+** 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*
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-AddtheVMwareHostComputertotheVCLdatabase"></a>
+#### Add the VMware Host Computer to the VCL database
+
+* Click *Manage Computers* > *Add Single Computer* > *Submit*
+** Hosthame: *localvmhost*
+** IP Address: *192.168.0.1*
+** 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*
+{info}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{info}
+** 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*
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-AddtheVirtualMachineComputerstotheVCLDatabase"></a>
+#### Add the Virtual Machine Computers to the VCL Database
+
+* Click *Manage Computers* > *Edit Computer Information* > *Submit*
+* Click the *Add Multiple* checkbox
+* Click *Add*
+** Hosthame: *vmguest-%*
+** Start value: *1*
+** End value: *10*
+** Start IP Address: *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*
+** 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: *127.0.0.1*
+* Click: *Download Data*, you should automatically generated dhcpd.conf
+file entries. Keep this web page open and continue with the following
+instructions.
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-Install&ConfiguretheDHCPService"></a>
+## 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.
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-Disablevmnet-dhcpd"></a>
+#### Disable vmnet-dhcpd
+
+Stop the *vmware* service:
+{tip}
+/sbin/service vmware stop
+{tip}
+
+Edit the following file:
+{tip}
+/etc/vmware/locations
+{tip}
+
+Find all lines beginning with *answer VNET_1_DHCP yes* and change *yes* to
+*no*:
+{panel}
+answer VNET_1_DHCP *no*
+{panel}
+
+Start the *vmware* service:
+{tip}
+/sbin/service vmware start
+{tip}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-InstalltheDHCPService"></a>
+#### Install the DHCP Service
+
+Install *dhcp* if it is not already installed:
+{tip}
+yum install dhcp \-y
+{tip}
+
+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:
+{tip}
+vi /etc/sysconfig/dhcpd
+{tip}
+
+Add *vmnet1* the to the *DHCPDARGS* line:
+
+ # Command line options here
+ DHCPDARGS=vmnet1
+
+
+Configure the dhcpd service to automatically start at runlevels 3-5:
+{tip}
+/sbin/chkconfig \--level 345 dhcpd on
+{tip}Start the dhcpd service:
+{tip}
+/sbin/service dhcpd start
+{tip}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-Configuredhcpd.conf"></a>
+#### Configure dhcpd.conf
+
+* Edit the */etc/dhcpd.conf* file on the computer:
+{tip}
+vi /etc/dhcpd.conf
+{tip}
+* Paste the following into the *dhcpd.conf* file and save the file:
+{info}The host sections below should be identical the the output displayed
+on the VCL website after you added the VM computers.{info}
+
+ 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 127.0.0.1;
+ next-server 127.0.0.1;
+ }
+
+ host vmguest-2 {
+ option host-name "vmguest-2";
+ hardware ethernet 00:50:56:1a:01:03;
+ fixed-address 192.168.1.2;
+ filename "/tftpboot/pxelinux.0";
+ option dhcp-server-identifier 127.0.0.1;
+ next-server 127.0.0.1;
+ }
+
+ host vmguest-3 {
+ option host-name "vmguest-3";
+ hardware ethernet 00:50:56:1a:01:05;
+ fixed-address 192.168.1.3;
+ filename "/tftpboot/pxelinux.0";
+ option dhcp-server-identifier 127.0.0.1;
+ next-server 127.0.0.1;
+ }
+
+ host vmguest-4 {
+ option host-name "vmguest-4";
+ hardware ethernet 00:50:56:1a:01:07;
+ fixed-address 192.168.1.4;
+ filename "/tftpboot/pxelinux.0";
+ option dhcp-server-identifier 127.0.0.1;
+ next-server 127.0.0.1;
+ }
+
+ host vmguest-5 {
+ option host-name "vmguest-5";
+ hardware ethernet 00:50:56:1a:01:09;
+ fixed-address 192.168.1.5;
+ filename "/tftpboot/pxelinux.0";
+ option dhcp-server-identifier 127.0.0.1;
+ next-server 127.0.0.1;
+ }
+
+ host vmguest-6 {
+ option host-name "vmguest-6";
+ hardware ethernet 00:50:56:1a:01:0b;
+ fixed-address 192.168.1.6;
+ filename "/tftpboot/pxelinux.0";
+ option dhcp-server-identifier 127.0.0.1;
+ next-server 127.0.0.1;
+ }
+
+ host vmguest-7 {
+ option host-name "vmguest-7";
+ hardware ethernet 00:50:56:1a:01:0d;
+ fixed-address 192.168.1.7;
+ filename "/tftpboot/pxelinux.0";
+ option dhcp-server-identifier 127.0.0.1;
+ next-server 127.0.0.1;
+ }
+
+ host vmguest-8 {
+ option host-name "vmguest-8";
+ hardware ethernet 00:50:56:1a:01:0f;
+ fixed-address 192.168.1.8;
+ filename "/tftpboot/pxelinux.0";
+ option dhcp-server-identifier 127.0.0.1;
+ next-server 127.0.0.1;
+ }
+
+ host vmguest-9 {
+ option host-name "vmguest-9";
+ hardware ethernet 00:50:56:1a:01:11;
+ fixed-address 192.168.1.9;
+ filename "/tftpboot/pxelinux.0";
+ option dhcp-server-identifier 127.0.0.1;
+ next-server 127.0.0.1;
+ }
+
+ host vmguest-10 {
+ option host-name "vmguest-10";
+ hardware ethernet 00:50:56:1a:01:13;
+ fixed-address 192.168.1.10;
+ filename "/tftpboot/pxelinux.0";
+ option dhcp-server-identifier 127.0.0.1;
+ next-server 127.0.0.1;
+ }
+
+* Restart the dhcpd service:
+{tip}/sbin/service dhcpd restart{tip}
+
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-Configure/etc/hosts"></a>
+#### Configure /etc/hosts
+
+* Modify the /etc/hosts file to include entries for the VM host and VM
+computers:
+{tip}
+vi /etc/hosts
+{tip}
+* Add the following entries:
+{panel}
+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
+{panel}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-ConfigurethesshdServicetoListenontheVirtualPrivateNetwork"></a>
+## Configure the sshd Service to Listen on the Virtual Private Network
+
+{tip}
+vi /etc/ssh/sshd_config
+{tip}Add the following line to the end of the file:
+{tip}
+ListenAddress 192.168.0.1
+{tip}Restart the sshd service on the management node:
+{tip}
+/sbin/service sshd restart
+{tip}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-ConfigureTheVMHostToBeAbleToSSHToItself"></a>
+## 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:
+
+{tip}
+mkdir /etc/vcl ; ssh-keygen \-t rsa \-f "/etc/vcl/vcl.key" \-N '' \-b 1024
+\-C "VCL root account on $HOSTNAME"
+{tip}
+
+Add the VM host's public key to its own authorized_keys file to allow it to
+SSH to itself without a password prompt:
+{tip}
+cat /etc/vcl/vcl.key.pub >> /root/.ssh/authorized_keys
+{tip}The following command should execute without having to enter a
+password:
+{tip}
+ssh \-i /etc/vcl/vcl.key localvmhost 'ls /'
+{tip}
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-ConfiguretheVMHostProfile"></a>
+## 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*
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-Assign theVM Computers totheVMHost"></a>
+## 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*
+
+<a name="ConfiguringaStandaloneVCLEnvironmentusingVMwareServer2.0-CreateaBaseImage"></a>
+## Create a Base Image
+
+Proceed to follow the instructions to create a [Windows ](vcl:create-a-windows-base-image.html)
+or [Linux |VCL:Create a Linux Base Image]
+base image.
Added: vcl/site/trunk/content/confluence_export/copy-administator-profile-with-bat-scripts.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/copy-administator-profile-with-bat-scripts.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/copy-administator-profile-with-bat-scripts.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/copy-administator-profile-with-bat-scripts.mdtext Tue Jan 8 16:37:53 2013
@@ -0,0 +1,41 @@
+Title: Copy Administator Profile With Bat Scripts
+Copy Administrator Windows XP Profile to Default User Profile Via Bat
+Scripts. Once you have your Administrator profile and shortcuts and
+programs in Windows XP perfect. All users will want to see the same
+environments. Doing a profile copy to the Default user lets all new users
+get the same profile as the Administrator that was just setup.
+
+1. Now as Administrator we need to create a new COPY profile.
+Please download these 3 VCL scripts that will do everything for you.
+
+http://db.tt/maf1PK2 Bat 1
+
+http://db.tt/BYRV6DL Bat 2
+
+http://db.tt/8Y6Epg0 Bat 3
+
+Download these files onto the VCL C Drive of the current Image environment
+
+
+2. From the VCL Local Disk Drive C: Click on the 1.bat script. This
+will create a cloning account called profile with the password profile. It
+will ask you do you wish to run this file. Please click on Run. A Black
+screen will open and the VCL will log you off automatically.
+
+3. Go back into the VCL web page. Click on current Reservations. Click
+on Connect then download and open your RDP file of your current create
+image. When you are prompted with a Log On to Windows Screen. Input your
+newly created profile from the downloaded bat file information *For
+Example* (User Name âprofileâ and password âprofileâ) * See steps 2
+4. Once you log into the profile copy account. Go to the VCL Local
+Disk Drive C: Click on the 2.bat Script. This will copy the Administrator
+profile to Default users. Click on Run when prompted. You will see the
+profile being copied this can take more than a few seconds to complete.
+Wait for the cmd.exe to finish working, the script will automatically log
+you off this is normal.
+5. Go back into the VCL web page and click on current reservations
+connect into the Administrator account for the current image Go to the VCL
+Local Disk Drive C: Click on the 3.bat Script
+6. Click on Run when 3.bat prompts you to do this. This will clean up
+the copy profile automatically. When you are prompted with a ###Done###
+information. You are finished with the profile copy and delete.
Added: vcl/site/trunk/content/confluence_export/create-a-linux-base-image.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/create-a-linux-base-image.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/create-a-linux-base-image.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/create-a-linux-base-image.mdtext Tue Jan 8 16:37:53 2013
@@ -0,0 +1,68 @@
+Title: Create a Linux Base Image
+{excerpt}This page describes how to create a Linux base image.{excerpt}
+
+
+<a name="CreateaLinuxBaseImage-Requirements"></a>
+## Requirements
+
+* Computer being captured has been added to the VCL database
+* Computer has been installed with Linux
+* Two network adapters are enabled on the computer:
+** eth0 - connected to the private network
+** eth1 - connected to the public network
+* The ability to log in as root via SSH using an identity key on the
+private network from management node
+
+<a name="CreateaLinuxBaseImage-ConfigureSSHIdentityKeyAuthentication"></a>
+### Configure SSH Identity Key Authentication
+
+1. On the Linux computer being captured, create a /root/.ssh directory:
+{tip}mkdir /root/.ssh{tip}
+1. On the management node, copy the public SSH identity key to the
+authorized_keys file on the Linux computer being captured:
+{tip}scp /etc/vcl/vcl.key.pub <hostname or IP
+address>:/root/.ssh/authorized_keys{tip}
+1. Or replace the above two steps with the following on the management node:
+{tip}ssh-copy-id \-i /etc/vcl/vcl.key <hostname or IP address>{tip}
+1. Make sure you can login from the management node to the Linux computer
+being captured using the identity key:
+{tip}ssh \-i /etc/vcl/vcl.key <hostname or IP address>{tip}
+
+<a name="CreateaLinuxBaseImage-Configuretheifcfg-\*Files"></a>
+### Configure the ifcfg-\* Files
+
+1. Navigate to the network-scripts directory:
+{tip}cd /etc/sysconfig/network-scripts{tip}
+1. Delete any ifcfg-*.bak files:
+{tip}rm \-f /etc/sysconfig/network-scripts/ifcfg-*.bak{tip}
+1. Edit every ifcfg-eth\* file in the network-scripts directory. Remove the
+*HWADDRESS=* line:
+{tip}vi ifcfg-eth0{tip}
+{tip}vi ifcfg-eth1{tip}
+The ifcfg-eth0 file should contain the following:
+
+ DEVICE=eth0
+ BOOTPROTO=dhcp
+ ONBOOT=yes
+
+The ifcfg-eth1 file should contain the following:
+
+ DEVICE=eth1
+ BOOTPROTO=dhcp
+ ONBOOT=yes
+
+1. Reboot the computer:
+{tip}shutdown \-r now{tip}
+1. Check the ifcfg-eth\* files to make sure there are no ifcfg-eth\* files
+and that the HWADDRESS= lines have not been automatically added back:
+{tip}
+ls /etc/sysconfig/network-scripts
+{tip}
+{tip}
+cat /etc/sysconfig/network-scripts/ifcfg-eth0
+{tip}
+{tip}
+cat /etc/sysconfig/network-scripts/ifcfg-eth1
+{tip}
+
+{include:Capture A Base Image}
Added: vcl/site/trunk/content/confluence_export/create-a-windows-base-image.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/create-a-windows-base-image.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/create-a-windows-base-image.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/create-a-windows-base-image.mdtext Tue Jan 8 16:37:53 2013
@@ -0,0 +1,171 @@
+Title: Create a Windows Base Image
+{excerpt}This page describes how to create a Windows base
+image.{excerpt}These instructions should work regardless of the
+provisioning engine being used (xCAT, VMware, etc.). Ignore the
+{color:#0000ff}{*}VMware Only{*}{color} sections if you are attempting
+to create an image using xCAT or some other bare metal provisioning
+engine.
+
+
+
+
+<a name="CreateaWindowsBaseImage-Requirements"></a>
+### Requirements
+
+You will need the following:
+* Windows installation ISO file
+* Windows product key or KMS server address
+
+ The following must be done before an image can be captured:
+* A computer for the machine being captured has already been added to
+the VCL database
+* {color:#0000ff}{*}VMware Only{*}{color}:
+** A VM host computer on which the guest is running as been added to
+the VCL database
+** The guest VM has been assigned to the VM host via the *Virtual Hosts*
+link on the VCL website
+
+These instructions assume you have root access and are using a *bash*
+shell.
+
+<a name="CreateaWindowsBaseImage-{color:#0000ff}VMwareOnly:{color}CreateaVirtualMachine"></a>
+## {color:#0000ff}VMware Only:{color} Create a Virtual Machine
+
+
+<a name="CreateaWindowsBaseImage-CreateaVirtualMachine"></a>
+### Create a Virtual Machine
+
+<a name="CreateaWindowsBaseImage-VMwareESXi4.x"></a>
+#### VMware ESXi 4.x
+
+The instructions assume that VMware has been configured with the following
+bridged networks:
+* *Private*: bridged to private interface: eth0
+* *Public*: bridged to public interface: eth1
+
+* Launch the vSphere Client, connect to the ESXi host and login
+* Click File > New > Virtual Machine
+* Configuration: *Custom*
+* Name: _(doesn't matter)_
+* Select a datastore where the VM will reside
+* Virtual Machine Version: *7*
+* Select the appropriate guest OS
+* Number of virtual processors: 1
+* Memory: 1GB
+* How many NICs: 2
+** NIC 1: *Private*, E1000
+** NIC 2: *Public*, E1000
+* SCSI controller: LSI Logic Parallel
+* Create a new virtual disk
+** Disk Size: at least 30 GB
+** Allocate and commit space on demand (Thin Provisioning): *Yes*
+** Location: Store with the virtual machine
+** Virtual Device Node: SCSI (0:0)
+** Mode: Independent, Persistent
+* Edit the virtual machine settings before completion: *Yes*
+* Select the CD/DVD device
+** Device Type: *Datastore ISO File*
+** Click Browse and browse to an ISO file that has previously been copied
+to the datastore
+** Connect at power on: *Yes*
+* Click Finish
+
+<a name="CreateaWindowsBaseImage-VMwareServer1.x"></a>
+#### VMware Server 1.x
+
+The instructions assume that VMware has been configured with the following
+bridged networks:
+* VMnet0: bridged to private interface: eth0
+* VMnet2: bridged to public interface: eth1
+
+* Launch the VMware Server console and connect to the local VMware host:
+{tip}
+vmware &
+{tip}
+* Virtual Machine Configuration: *Typical*
+* Guest Operating System: *Microsoft Windows*
+* Version: *Windows XP Professional* (select the appropriate version if you
+are not installing XP)
+* Name: *vmwarewinxp-base7-v1*
+* Network connection: *Custom*
+** /dev/vmnet0\*
+* Disk size: *8.0 GB*
+** Allocate all disk space now: *no*
+** Split disk into 2GB files: *yes*
+* Edit virtual machine settings
+** Configure the VM CD-ROM drive to use the Windows XP ISO image
+** Connection: *Use ISO image*: browse to path of Windows XP ISO image
+copied to the VMware host
+* Add: Ethernet Adapter
+** Network Connection: *Custom*
+** \*/dev/vmnet2\*
+
+<a name="CreateaWindowsBaseImage-VMwareServer2.x"></a>
+#### VMware Server 2.x
+
+* Open the VMware Infrastructure Web Access page:
+{info:icon=false}https://<IP address or hostname>:8333{info}
+* Click the *Virtual Machine* menu
+* Select *Create Virtual Machine*
+* Name and Location
+** Name: *Windows XP Base*
+** Datastore: *standard* (This causes the VM to be created under
+/var/lib/vmware/Virtual Machines)
+* Guest Operating System
+** Operating System: *Windows operating system*
+** Version: *Microsoft Windows XP Professional (32-bit)*
+** Product Compatibility: *4* (Optional - the hardware version can be set
+to the default value of *7* if you do not have any older VMware Server 1.x
+hosts in your environment)
+* Memory and Processors
+** Memory Size: *1024 MB*
+** Processor Count: *1*
+* Hard Disk
+** Click *Create a New Virtual*
+*** Capacity: at least *20 GB* (This value can be adjusted to suit the size
+of the VMware host's disk. It is best to create the base image with a large
+enough hard drive to accomodate your largest image. The hard drive of a VM
+can be expanded but it is a manual, time-consuming process.)
+*** File Options
+**** Allocate all disk space now: no
+**** Split disk into 2 GB files: yes
+*** Disk Mode: *Independent/Persistent*
+* Network Adapter
+** Click *Add a Network Adapter*
+*** Network Connection: select the name of your *private* network
+* CD/DVD Drive
+** Click *Use an ISO*
+*** Select the Windows ISO image you copied to the host. The ISO file must
+reside in */var/lib/vmware/Virtual Machines* in order to be able to select
+it from this interface.
+* Don't Add a Floppy Drive
+* Don't Add a USB
+* Click *Finish*
+* Select the VM from the Inventory pane
+* Click *Add Hardware* on the right side of the page
+* Select *Network Adapter*
+** Network Connection: select the name of your *public* network
+* Click *Next* > *Finish*
+
+<a name="CreateaWindowsBaseImage-InstallWindows"></a>
+## Install Windows
+
+[Install Windows for a Base Image](install-windows-for-a-base-image.html)
+
+<a name="CreateaWindowsBaseImage-{color:#0000ff}VMwareOnly:{color}InstallVMwareTools"></a>
+## {color:#0000ff}VMware Only:{color} Install VMware Tools
+
+1. Power on the VM if it is not already powered on
+1. Install VMWare Tools (Note: you must have a CD-ROM drive configured
+for the VM in order to install VMware Tools)
+1. # Click on the VM menu and select "Install VMWare Tools"
+1. # Select Typical and proceed through the setup pages accepting the
+defaults
+1. # Reboot the VM when installation is complete
+
+<a name="CreateaWindowsBaseImage-InstallCygwinSSHD"></a>
+## Install Cygwin SSHD
+
+Follow the steps: [Install & Configure Cygwin SSHD](install-&-configure-cygwin-sshd.html)
+
+{include:Capture A Base Image}
Added: vcl/site/trunk/content/confluence_export/creating-a-cluster-enviroment.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/creating-a-cluster-enviroment.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/creating-a-cluster-enviroment.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/creating-a-cluster-enviroment.mdtext Tue Jan 8 16:37:53 2013
@@ -0,0 +1,21 @@
+Title: Creating a Cluster enviroment
+Cluster environments are created from existing VCL images.
+
+The terms *parent* and *child* are used in this document and with the VCL
+provisioning:
+
+*parent* = the primary image or selectable image through the VCL New
+Reservation menu
+
+*child* = the second image or images that are also loaded and are the sub
+images associated with the parent image
+
+
+*To Create a cluster image*
+* Select Manage Images \-> Edit Image Profiles
+* Select edit beside the parent image
+* Click on Advanced Options
+* Select Manage Subimages
+* In the window select a child image
+** The child image can be the same as the parent image or another.
+* Repeat adding as many subimages as needed (or have nodes for).
Added: vcl/site/trunk/content/confluence_export/creating-a-new-image-from-a-base-image.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/creating-a-new-image-from-a-base-image.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/creating-a-new-image-from-a-base-image.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/creating-a-new-image-from-a-base-image.mdtext Tue Jan 8 16:37:53 2013
@@ -0,0 +1,18 @@
+Title: Creating a New Image from a Base Image
+!createimage.png!
+
+1. Select *Manage Images* from the left navigation menu
+1. Select the *Create / Update an Image* radio button and click *Submit*
+1. Select the base environment from which you would like to build your new
+image
+1. If you would like to start making the new image immediately, select Now.
+Otherwise, select Later and select a time in the future.
+1. The duration of the imaging reservation will be 8 hours and cannot be
+extended.
+1. If you selected *Now* and the environment is available, the estimated
+wait time will be displayed.
+1. Click *Create Imaging Reservation* to start
+1. Once the *Connect!* button is displayed on the *Current Reservations*
+page, click it to view connection information
+1. [Additional Steps for Windows Images](additional-steps-for-windows-images.html)
+1. [Additional Steps for Linux Images](additional-steps-for-linux-images.html)
Added: vcl/site/trunk/content/confluence_export/creating-a-virtual-machine-for-the-vcl-server.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/creating-a-virtual-machine-for-the-vcl-server.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/creating-a-virtual-machine-for-the-vcl-server.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/creating-a-virtual-machine-for-the-vcl-server.mdtext Tue Jan 8 16:37:53 2013
@@ -0,0 +1,110 @@
+Title: Creating a Virtual Machine for the VCL Server
+1. {color:#000000}Create a reservation for the vSphere client image{color}##
+{color:#000000}Log into{color} [https://vcl.ncsu.edu](https://vcl.ncsu.edu/)
+1. # {color:#000000}Click{color} {color:#000000}New Reservation{color}
+1. # {color:#000000}Select{color} {color:#000000}VMware vSphere Client
+Bootcamp 2011{color}
+1. # {color:#000000}Click Create Reservation{color}{color:#000000}Wait for
+the reservation to be ready, Connect button appears{color}
+1. # {color:#000000}Click{color} {color:#000000}Connect{color}
+1. # {color:#000000}Connect to the reservation via RDP and login{color}
+1. {color:#000000}Log into the ESXi host{color}## {color:#000000}Launch
+the{color} {color:#000000}VMware vSphere Client{color}
+{color:#000000}application{color}### {color:#000000}IP Address:{color}
+{color:#000000}enter the IP address you were given{color}
+1. ## {color:#000000}Username:{color} {color:#000000}root{color}
+1. ## {color:#000000}Password:{color}
+{color:#000000}{*}_<password>_{*}{color}
+1. # {color:#000000}Click Login{color}
+1. # {color:#000000}If presented with a Security Warning box, click the
+âInstall this certificate...â checkbox and then click Ignore{color}
+1. {color:#000000}Create a virtual machine for your VCL server{color}##
+{color:#000000}Click File > New > Virtual Machine{color}
+1. # {color:#000000}Configuration:{color} {color:#000000}Custom{color}
+1. # {color:#000000}Name:{color} {color:#000000}vcl-server{color}
+1. # {color:#000000}Datastore:{color} {color:#000000}local{color}
+1. # {color:#000000}Virtual Machine Version:{color} {color:#000000}7{color}
+1. # {color:#000000}Guest Operating System:{color}
+{color:#000000}Linux{color}### {color:#000000}Version:{color}
+{color:#000000}CentOS 4/5 (32-bit){color}
+1. # {color:#000000}Number of virutal processors: 1{color}
+1. # {color:#000000}Memory Size: 1 GB{color}
+1. # {color:#000000}How many Nics: 2{color}### {color:#000000}NIC 1:{color}
+{color:#000000}Private{color}{color:#000000}, Adapter: E1000, Connect at
+Power On: Yes{color}
+1. ## {color:#000000}NIC 2:{color}
+{color:#000000}Public{color}{color:#000000}, Adapter: E1000, Connect at
+Power On: Yes{color}
+1. # {color:#000000}SCSI controller: LSI Logic Parallel{color}
+1. # {color:#000000}Disk: Create a new virtual disk{color}###
+{color:#000000}Disk Size: 8 GB{color}
+1. ## {color:#000000}Allocate and commit space on demand (Thin
+Provisioning):{color} {color:#000000}Yes{color}
+1. ## {color:#000000}Support clustering: No{color}
+1. ## {color:#000000}Location: Store with the virtual machine{color}
+1. # {color:#000000}Virtual Device Node: SCSI (0:0){color}###
+{color:#000000}Mode:{color}
+{color:#000000}Independent{color}{color:#000000},{color}
+{color:#000000}Persistent{color}
+1. # {color:#000000}Edit the virtual machine settings before
+completion:{color} {color:#000000}Yes{color}
+1. # {color:#000000}Select the CD/DVD device{color}### {color:#000000}Change
+Device Type to:{color} {color:#000000}Datastore ISO File{color}
+1. ## {color:#000000}Click Browse{color}#### {color:#000000}Navigate
+to{color} {color:#000000}local/iso{color}
+1. ### {color:#000000}Select:{color}
+{color:#000000}CentOS-5.6-i386-bin-DVD.iso{color}
+1. ## {color:#000000}Connect at power on:{color} {color:#000000}Yes{color}
+1. # {color:#000000}Click{color} {color:#000000}Finish{color}
+1. {color:#000000}Install the VCL Server OS{color}## {color:#000000}Click
+the plus sign in the left pane to display the VM{color}
+1. # {color:#000000}Select the{color} {color:#000000}VCL Server{color}
+{color:#000000}VM{color}
+1. # {color:#000000}Click the{color} {color:#000000}Console{color}
+{color:#000000}tab{color}
+1. # {color:#000000}Click the play button to start the VM{color}
+1. # {color:#000000}To install in or upgrade in graphical mode: press
+Enter{color}
+1. # {color:#000000}Choose{color} {color:#000000}Skip{color}
+{color:#000000}to skip the media testthe GUI installation begins...{color}
+1. # {color:#000000}Click Next{color}
+1. # {color:#000000}Select English{color}
+1. # {color:#000000}Would you like to initialize this drive:{color}
+{color:#000000}Yes{color}
+1. # {color:#000000}Click Next to use the default partitioning scheme{color}
+1. # {color:#000000}Network Devices:{color}### {color:#000000}Select{color}
+{color:#000000}eth0{color} {color:#000000}and click Edit{color}####
+{color:#000000}Enable IPv4 support: Yes{color}##### {color:#000000}Manual
+configuration{color}###### {color:#000000}IP Address:{color}
+{color:#000000}10.100.0.1{color}
+1. ##### {color:#000000}Prefix (Netmask):{color}
+{color:#000000}255.255.255.0{color}
+1. ### {color:#000000}Enable IPv6 support:{color} {color:#000000}No{color}
+1. ## {color:#000000}Select{color} {color:#000000}eth1{color}
+{color:#000000}and click Edit{color}#### {color:#000000}Enable IPv4
+support: Yes{color}##### {color:#000000}Dynamic IP configuration
+(DHCP){color}
+1. ### {color:#000000}Enable IPv6 support:{color} {color:#000000}No{color}
+1. ## {color:#000000}eth1 - Activate on Boot:{color}
+{color:#000000}Yes{color}
+1. # {color:#000000}Select a timezone{color}
+1. # {color:#000000}Root Password:{color} {color:#000000}_<password>_{color}
+1. # {color:#000000}Software packages - uncheck{color} {color:#000000}Desktop
+- Gnome{color}
+1. # {color:#000000}Reboot the VM when the installation is complete{color}
+1. # {color:#000000}Select the item that you wish to modify: click
+Exit{color}
+1. # {color:#000000}Login as root{color}
+1. # {color:#000000}Verify the networking: ifconfig{color}###
+{color:#000000}eth0 should be assigned 10.100.0.1{color}
+1. ## {color:#000000}eth1 should be assigned a public IP address:
+152.46.x.x{color}
+1. {color:#000000}Log in via SSH{color}## {color:#000000}Launch PuTTY from
+the computer you connected to via RDP{color}### {color:#000000}Host Name:
+Enter the public IP address of the VCL server which is displayed in the
+ifconfig output{color}
+1. ## {color:#000000}Saved Sessions: enter âvcl-serverâ{color}
+1. ## {color:#000000}Click Save{color}
+1. # {color:#000000}Connect to vcl-server{color}
+1. # {color:#000000}Login as root{color}
+1. {color:#000000}Install the VCL components:{color}[https://cwiki.apache.org/confluence/display/VCL/VCL+2.2.1+Installation](https://cwiki.apache.org/display/VCL/VCL+2.2.1+Installation)
Added: vcl/site/trunk/content/confluence_export/database-configuration.mdtext
URL: http://svn.apache.org/viewvc/vcl/site/trunk/content/confluence_export/database-configuration.mdtext?rev=1430372&view=auto
==============================================================================
--- vcl/site/trunk/content/confluence_export/database-configuration.mdtext (added)
+++ vcl/site/trunk/content/confluence_export/database-configuration.mdtext Tue Jan 8 16:37:53 2013
@@ -0,0 +1,41 @@
+Title: Database Configuration
+{excerpt}This page describes how to create the VCL MySQL database and
+import the VCL database schema.{excerpt}
+
+
+<a name="DatabaseConfiguration-*Prerequisites*"></a>
+## *Prerequisites*
+
+1. You should have mysql server 5.x installed. If mysql server is not
+installed:
+
+ yum install mysql-server -y
+ /sbin/chkconfig --level 345 mysqld on
+ /sbin/service mysqld start
+
+1. Your host based firewall (IPTables) should be configured to allow traffic
+from the web server and management server to connect to TCP port 3306
+(mysqld).
+
+
+<a name="DatabaseConfiguration-*SettingUptheDatabaseforVCL*"></a>
+## *Setting Up the Database for VCL*
+
+1. create a database in mysql named for use with VCL
+
+ CREATE DATABASE vcl;
+
+1. create a user with SELECT, INSERT, UPDATE, and DELETE privileges on the
+database you just created
+*NOTE*: Replace vcluserpassword with your own password\!
+
+ GRANT SELECT,INSERT,UPDATE,DELETE ON vcl.* TO 'vcluser'@'localhost'
+IDENTIFIED BY 'vcluserpassword';
+
+1. locate vcl.sql file
+The vcl.sql file should be contained in the release artifact you should
+have downloaded already. After extracting it, look in the mysql directory.
+1. import vcl.sql file into database
+
+ mysql vcl < vcl.sql
+