VMLabs System: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
VMLAB | <H2> VMLAB Overview </H2> | ||
<br> | |||
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. | 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. | ||
<br> | |||
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 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. | ||
| Line 7: | Line 9: | ||
Here's a link of just the interface: https://raw.githubusercontent.com/kimchi-project/kimchi/master/docs/kimchi-templates.png | Here's a link of just the interface: https://raw.githubusercontent.com/kimchi-project/kimchi/master/docs/kimchi-templates.png | ||
<br> | |||
From the web interface, users can create vm's (guests) from template (Pre-made / provisioned VM's), monitor usage, and access the console. | |||
<H2>Login Info </H2> | |||
These credentials are suitable for anyone looking to use the vmlab as a sandbox | |||
[http://10.0.1.110:8000 Kimchi] | |||
<br>uname: vmlab | |||
<br>pw: uas | |||
<br><br><br> | |||
<h2>VMLABS physical Specs</h2> | |||
<br> | |||
OS:Ubuntu 14.04 LTS (Sorry, I built it right before the new release) | OS:Ubuntu 14.04 LTS (Sorry, I built it right before the new release) | ||
RAM: 64 Gb | <br>RAM: 64 Gb | ||
CPU: 4 dual core AMD Opterons (3GHZ) | <br>CPU: 4 dual core AMD Opterons (3GHZ) | ||
HDD: 660Gb | <br>HDD: 660Gb | ||
<h2> System Architecture </h2> | |||
TODO: Finalize plan, write this | |||
<h3>Links</h3> | |||
[https://github.com/kimchi-project/kimchi : Kimchi] | |||
<br>[https://github.com/kimchi-project/wok : Wok] | |||
<br>[https://www.linux.com/news/kvm-or-xen-choosing-virtualization-platform : kvm or xen] | |||
<h3> TODO </h3> | |||
# Document KVM architecture | |||
# Document Kimchi startup procedure | |||
# Create vmlab architecture diagram | |||
# Set agenda for individual boxes & services plan | |||
<h1> If you want a vm talk to flay! </h1> | |||
Revision as of 19:46, 16 July 2016
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.
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
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, write this
Links
TODO
- Document KVM architecture
- Document Kimchi startup procedure
- Create vmlab architecture diagram
- Set agenda for individual boxes & services plan