Virtual Machines: Difference between revisions

From The Munich Maker Lab's Wiki
Jump to navigation Jump to search
No edit summary
 
Line 4: Line 4:
{| class="wikitable" width="100%"
{| class="wikitable" width="100%"
! Name !! IP address !! Owner !! Description  
! Name !! IP address !! Owner !! Description  
|-
| localhorst || 10.10.20.63 || Heiko || Heikos Test VM
|-
|-
| broker || 10.10.20.64 || Jan, Heiko || MQTT Broker
| broker || 10.10.20.64 || Jan, Heiko || MQTT Broker

Latest revision as of 15:47, 9 December 2016

We are running two KVM hosts to run virtual machines on in the space.

Running VMs

vmhost01

Name IP address Owner Description
broker 10.10.20.64 Jan, Heiko MQTT Broker
vpn-access 10.10.20.90, 10.20.20.90 (DMZ) JanS OpenVPN Gateway
backup 10.10.20.91 Severin Backup operator
coreos10 10.10.20.66 Matthias, Severin Docker Host

vmhost02

Name IP address Owner Description

Access

URL: vmhost01 vmhost02

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 (SW 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 (HW RAID1) boot drives
  • 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.

Fixes