VMLab: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
<H2> VMLAB Overview </H2> | <H2> VMLAB Overview </H2> | ||
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. | ||
A secondary goal was to add | |||
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 17: | Line 18: | ||
<br> If you want a specialized machine/template, ask flay</br> | <br> If you want a specialized machine/template, ask flay</br> | ||
[ | [https://10.0.0.20:8001 Kimchi] | ||
<br>uname: vmlab | <br>uname: vmlab | ||
<br>pw: uas | <br>pw: uas | ||
| Line 25: | Line 26: | ||
<h2>VMLABS physical Specs</h2> | <h2>VMLABS physical Specs</h2> | ||
<br> | <br> | ||
MODEL:Dell Poweredge R710 | |||
OS:Ubuntu CentOS 7 LTS: 3.10.0-327.el7.x86_64 | OS:Ubuntu CentOS 7 LTS: 3.10.0-327.el7.x86_64 | ||
<br>RAM: | <br>RAM: 190GB | ||
<br>CPU: | <br>CPU: 2 x Intel Xeon x5560 (2.8GHZ) [https://ark.intel.com/products/37109/Intel-Xeon-Processor-X5560-8M-Cache-2_80-GHz-6_40-GTs-Intel-QPI] | ||
<br>HDD: | <br>HDD: 1.4TB | ||
RAID: 6 | |||
<h2> System Architecture </h2> | <h2> System Architecture </h2> | ||
Every student Guest (VM) will be set up via administrator-created template. | |||
<H2> Setup Info </H2> | <H2> Setup Info </H2> | ||
Disable SELinux | |||
Grab kimchi via packages | |||
<h3> Administrator Notes </h3> | |||
When creating a new Guest requiring internet access you'll have to add the "phybridge" device (located in kimchi under the admin account) you MUST do this after creating the guest. Create the guest, power it off, edit it, add the bridged adapter, restart. Then you can modify the device to assign a static ip. In the centOS minimal boxes this can be done via the respective /etc/sysconfig/network-scripts/ifcfg-eth file | |||
Don't give Guests names which contain spaces. You'll get insane errors. | |||
<h3> TODO </h3> | <h3> TODO </h3> | ||
# Document KVM architecture | # Document KVM architecture | ||
# Configure Firewalld | |||
# Document Kimchi startup procedure | # Document Kimchi startup procedure | ||
# Create vmlab architecture diagram | # Create vmlab architecture diagram | ||
# Set agenda for individual boxes & services plan | # Set agenda for individual boxes & services plan | ||
# Set up/demo Ovirt | # Set up/demo Ovirt | ||
<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] | |||
<br>[[Ovirt]] | |||
Revision as of 17:08, 5 February 2017
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.
A secondary goal was to add 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
EXPERIMENTATION IS ENCOURAGED!
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 machine/template, ask flay
Kimchi
uname: vmlab
pw: uas
VMLABS physical Specs
MODEL:Dell Poweredge R710
OS:Ubuntu CentOS 7 LTS: 3.10.0-327.el7.x86_64
RAM: 190GB
CPU: 2 x Intel Xeon x5560 (2.8GHZ) [1]
HDD: 1.4TB
RAID: 6
System Architecture
Every student Guest (VM) will be set up via administrator-created template.
Setup Info
Disable SELinux Grab kimchi via packages
Administrator Notes
When creating a new Guest requiring internet access you'll have to add the "phybridge" device (located in kimchi under the admin account) you MUST do this after creating the guest. Create the guest, power it off, edit it, add the bridged adapter, restart. Then you can modify the device to assign a static ip. In the centOS minimal boxes this can be done via the respective /etc/sysconfig/network-scripts/ifcfg-eth file
Don't give Guests names which contain spaces. You'll get insane errors.
TODO
- Document KVM architecture
- Configure Firewalld
- Document Kimchi startup procedure
- Create vmlab architecture diagram
- Set agenda for individual boxes & services plan
- Set up/demo Ovirt