VMLabs System: Difference between revisions

From Unallocated Space
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
Hyper-V 3.x (Server 2012 R2 release) or ESXi 5.1 (pending benchmarking of key resources such as CPU and I/O load distribution, last round of benchmarking Hyper-V trashed ESXi on our hardware for our specific usage scenarios due to how multipath I/O was handled and ram manipulation. Will test the latest update rollups of both.) managed by System Center Virtual Machine Manager 2012 R2 preview. (or RTM, if available upon launch).
VMLAB:
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.


Limited user accounts are provided for users to create/share VMs using specific resource allocations per user as well as a specific SAN share for their VM's disk files and ISO uploads.
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.


Private file shares as well will be provided for users with individualized accounts.
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 from template (locally hosted iso's), monitor usage, and run a console through the web browser
 
Login info:
10.0.1.110:8000
uname: vmlab
pw: uas
 
VMLab 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
 
 
Relevant links:
https://github.com/kimchi-project/kimchi
https://github.com/kimchi-project/wok
https://www.linux.com/news/kvm-or-xen-choosing-virtualization-platform

Revision as of 17:08, 16 July 2016

VMLAB: 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.

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 from template (locally hosted iso's), monitor usage, and run a console through the web browser

Login info: 10.0.1.110:8000 uname: vmlab pw: uas

VMLab 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


Relevant links: https://github.com/kimchi-project/kimchi https://github.com/kimchi-project/wok https://www.linux.com/news/kvm-or-xen-choosing-virtualization-platform