VMLabs System

From Unallocated Space
Jump to navigation Jump to search

VMLAB Overview

The rationale for this implementation was to reduce the barrier for project creation and facilitate ad hoc experimentation. It was my goal to make this minimally intimidating for inexperienced users.

Ovirt - The RHEL Virtualization Platform

I nuked all the other iterations and installed CentOS

The config

For users:

For Admins Invocation to upload iso's

engine-iso-uploader upload iso_library web_for_pentester_i386.iso

Old VMLab Info

I thought it easiest if those who were less confident had a familiar interface and I didn't suspect anyone regardless of experience will be offended by a GUI, so I opted for a browser based system.

I did this through a management interface called Kimchi, which is a plugin for wok the webserver. ginger is used as a plugin mgmt system. the whole thing is backed by KVM acting as a hypervisor. Here's a link of just the interface: https://raw.githubusercontent.com/kimchi-project/kimchi/master/docs/kimchi-templates.png

From the web interface, users can create VM's (guests) from template (Pre-made / provisioned VM's), monitor usage, and access the console.

Login Info

These credentials are suitable for anyone looking to use the vmlab as a sandbox.
If you want a specialized box, ask flay

uname: vmlab
pw: uas

VMLABS physical Specs

OS:Ubuntu 14.04 LTS (Sorry, I built it right before the new release)
RAM: 64 Gb
CPU: 4 dual core AMD Opterons (3GHZ)
HDD: 660Gb

System Architecture

TODO: Finalize plan.


: Kimchi
: Wok
: kvm or xen


  1. Document KVM architecture
  2. Document Kimchi startup procedure
  3. Create vmlab architecture diagram
  4. Set agenda for individual boxes & services plan