Virtual Machines: Difference between revisions
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
== Hardware == | == Hardware == | ||
=== vmhost01 === | === vmhost01 === | ||
WebUI: https://10.10.20.62:8006/ | |||
* 2x Intel Xeon 2,0 Ghz | * 2x Intel Xeon 2,0 Ghz | ||
* 18 GB RAM | * 18 GB RAM | ||
| Line 14: | Line 16: | ||
=== vmhost02 === | === vmhost02 === | ||
WebUI: https://10.10.20.65:8006/ | |||
* 2x Intel Xeon 5130 (2,0Ghz) | * 2x Intel Xeon 5130 (2,0Ghz) | ||
* 16GB RAM | * 16GB RAM | ||
Revision as of 04:02, 12 March 2016
We are running a KVM host to run virtual machines on in the space.
Access
If you need a user, contact Severin
Hardware
vmhost01
WebUI: https://10.10.20.62:8006/
- 2x Intel Xeon 2,0 Ghz
- 18 GB RAM
- 2x 150GB (RAID1) Boot drives
- 8x 500GB data drives (in a ZFS RAIDZ2, leaving about 2.8 TB of space)
vmhost02
WebUI: https://10.10.20.65:8006/
- 2x Intel Xeon 5130 (2,0Ghz)
- 16GB RAM
- 2x 250GB (RAID1) boot drives (hw raid)
- 14x 143GB data drives in external SCSI shelf, not all of them working (in a ZFS RAIDZ2, leaving about 1.2 TB of space)
Software
We are running Proxmox on the machine. Installation was done manually on a Debian Jessie install roughly following Proxmox's guide, as their standard installer does not support software RAID for boot devices, and didn't recognise our additional SATA controller.
There are two working datastores, one called "internal" which points to the ZFS raid array, and another called "local" which is on the boot drives. Use the one on the bootdrives for ISO images, and the ZFS array for everything else. Ideally, ISO images will be pulled from the fileserver, but that just hasn't been successfully setup yet.
