VCL Virtual Machine Appliance


Use the below instructions to bring the VCL virtual machine to a usable state on your infrastructure. Two install this virtual machine you will require a blade center with at least two blades available, one for the VCL virtual machine, and the other to provision virtual machines to. Before beginning the below installation, ensure your environment is ready by completing the pre-install checklist and review you have hardware similar to the recommended Blade Center configurations.

These packages have not been combined but only grouped. The code of all packages has not been modified, interwoven, or merged with each other in any way. Each package has its own license which operates independantly of the others. Use of the VCL grouping of this Virtual Machine does not in any way change or modify the licenses for each of the individual packages. Review the terms of the licenses below to determine appropriate use.

[plain english]: We have merely grouped these applications together, in a way that makes installation of the VCL easier, than going and getting each application independantly from its parent source. None of the applications have been modified in any way, nor combined to create any form of derivitave work, as defined by any of the different license groups. This Virtual Machine itself is not covered under any license as it is not a derivative work. A user who installs this virtual machine is advised to read and understand the terms of each individual license for each of the enclosed applications.

Of course, anyone can always build their own VCL from the source code below, and only be subject to its modified Eclipse 1.0 License.

VCL source code version 1.9.1

65cf571f12daafc2ef6c87c7773b8673

 

1) Install 3i on a blade in your environment. You can accomplish this by downloading the .iso, burning it to a disk, and installing 3i on a blade. Ensure your blade is online by performing a network self test from the console.

 

2) Install the VMware Infrastructure Client (VI Client) on a windows machine. Your 3i server will hand you the VI Client .exe installer through https at https://your_3i_servers_ip/

 

3) Connect to your 3i server using the VMware Virtual Infrastructure Client.

 

4) Display your 3i server's networking configuration. Use the below screen shot as a guide. Select your 3i server (top left circle). Select the 'Configuration' tab (top right circle). Then, select Networking from the tab's display (bottom circle).

 

 

5) Use the below diagram as a guide. Use the 'Add Networking' and 'Properties' buttons to get the networking to look like the below diagram. Specifically, create two 'Virtual Machine' network groups named "Public" and "Management". Connect the "Public" port group to the virtual switch uplinked to a physical interface with a public IP (look for a valid VMkernel Port). Similarly, connect the "Management" port group to the virtual switch uplinked to a physical interface connected to a a private, non-routable VLAN.

 

 

 

6) Download the Virtaul Machine below to your local Windows Desktop containing the VI client. Verify the md5 sum; you can use md5sum for windows to do this.

 

Download VCL VM version 1.6 [torrent][http]

d694e518e55ac2db0f22abd32daae830

 

7) Use winzip to extract the 'VCL-1.6.zip' file. After extracting, verify you now have a VCL directory containing the VCL.vmx

 

8) Use the below diagram as a guide. Connect to your 3i server through the VMware Virtual Infrastructure Client. Select your blade (leftmost circle). Select the configuration tab, and then the storage selection on the left to display your datastores. Double click on the datastore icon () to browse it.

 

 

6) Use the diagram below as a guide. Select the 'Upload Folder' icon () to upload the entire unzipped 'VCL' folder from your local windows machine.

 

 

 

7) Use the below image as a guide. After the VCL directory is on the datastore, select the VCL.vmx file and select the 'Add VM to Inventory' icon (). Name the VM (ie: VCL), and following the screens to complete this VM addition.

 

 

 

8) This virtual machine's eth0 (00:50:56:39:38:cc) is set to DHCP from the 'public' port group. Configure your LAN's DHCP services such that the eth0 interface of the VM receives a public IP address. This is the IP address (and its associated DNS) which you will later use to access the VCL web interface. The VMs eth1 (aka the management interface) will self-assing itself to the 10.10.0.1/24 address. It is through the eth1 interface where DHCP, pxe, tftp, and nfs services are offered to accomplish the provisioning.

 

 

9) Turn the VM on with the 'Power On' icon (). Watch the VM boot up with the 'Console' tab, and if DHCP is properly set for the eth0 interface, it should boot cleanly. It will boot showing its hostname below the fedora logo.

 

 

10) The VM has no X windows GUI, and only has a command line shell. SSH to the VM on port 22, using user 'root' and password 'Cl0udC0mputing'. This is the user/pass for the root account of the OS and the root mySQL account.

 

11) Ensure the networking has started properly using 'ifconfig'

  • eth0: a "public" IP address from your LAN's DHCP services.
  • eth1: 10.10.0.1/24

 

12) cd /root/configure_vcl/

 

13) When running Step 14 you will be prompted for several pieces of information. Prepare to be able to provide all the necessary information. NOTE: your management module's must be accessable from the public interface IP of your virtual machine, so the management node can reach the Management Modules via layer 3 (IP).

  • A 'Supervisor Profile' is created on each Blade Center Management Module scoped to the blades inside which VCL should manage. This single user/pass must be ubiquitious across all Blade Centers managed by VCL.
  • The password assigned by default to linux machines when they are loaded
  • The physical interface (eth0 or eth1) connected to the 'private' management VLAN of the blades you will provision
  • For each Blade Center, three things are required:
    1. The IP Address of the Management Module
    2. A name for that Blade Center
    3. The slot numbers of blades to add
  • The mySQL root password

 

14) ./configure_all.sh

 

 

15) Browse to the VCL web GUI by browsing to the location displayed as output at the end of the script in step 14. Typically, it is https://IP_OF_YOUR_VM/

 

 

16) Logon to your VCL installation using the following credentials

username: admin
password: adminVc1passw0rd

 

17) Goto Manage -> 'Edit Computer Information'. For each Blade entry in this computer list select 'Edit', and update its IP address to match the public IP address the blade's public interface entry in the DHCP services.

 

18) Verify the installation was successful by completing the post-install checklist.

hosted by ibiblio