VMLab
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.
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 the wok webserver (Interacts with nginx). 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
Kimchi
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.
Links
: Kimchi
: Wok
: kvm or xen
Ovirt
TODO
- Document KVM architecture
- Document Kimchi startup procedure
- Create vmlab architecture diagram
- Set agenda for individual boxes & services plan
- Set up/demo Ovirt