Difference between revisions of "Phoenix"
From CSLabsWiki
| Line 17: | Line 17: | ||
}} |
}} |
||
| − | '''Phoenix''' is our secondary VM host. It rose from the ashes of '''europa''' and '''xen2''' |
+ | '''Phoenix''' is our secondary VM host. It rose from the ashes of '''europa''' and '''xen2'''. |
'''Phoenix''' has older drives than eevee, but several of them have never been used prior to being installed in Phoenix. Additionally, all 4 drives, which are 1 TB each, have been configured in RAID6 to allow for up to 2 failed drives and provide a total of 2 TB of storage. This is twice the amount of storage as eevee currently has and also twice the tolerance for failure. |
'''Phoenix''' has older drives than eevee, but several of them have never been used prior to being installed in Phoenix. Additionally, all 4 drives, which are 1 TB each, have been configured in RAID6 to allow for up to 2 failed drives and provide a total of 2 TB of storage. This is twice the amount of storage as eevee currently has and also twice the tolerance for failure. |
||
| + | |||
| + | Each of Phoenix's CPUs are much older than, but roughly comparable in performance to [[Bennu]]'s CPU. Thus, Phoenix also has roughly twice the computing power as [[Bennu]]. |
||
== Setup == |
== Setup == |
||
| Line 25: | Line 27: | ||
=== Things to install === |
=== Things to install === |
||
| − | apt |
+ | apt install htop vim sudo qemu-kvm libvirt-bin virtinst screen rsync |
=== Network Bridge Setup === |
=== Network Bridge Setup === |
||
| Line 32: | Line 34: | ||
In /etc/network/interfaces: |
In /etc/network/interfaces: |
||
<pre> |
<pre> |
||
| + | # This file describes the network interfaces available on your system |
||
| + | # and how to activate them. For more information, see interfaces(5). |
||
| + | |||
| + | source /etc/network/interfaces.d/* |
||
| + | |||
# The loopback network interface |
# The loopback network interface |
||
auto lo |
auto lo |
||
iface lo inet loopback |
iface lo inet loopback |
||
| + | |||
| + | auto eth0 |
||
| + | auto eth1 |
||
| + | auto eth2 |
||
auto br0 |
auto br0 |
||
iface br0 inet static |
iface br0 inet static |
||
| + | address 128.153.145.40 |
||
| − | bridge_ports all # or just eth0, ... |
||
| + | netmask 255.255.254.0 |
||
| − | address 128.153.145.40 |
||
| + | gateway 128.153.144.1 |
||
| − | netmask 255.255.255.0 |
||
| + | bridge_ports all |
||
| − | gateway 128.153.145.1 |
||
| + | |||
| − | broadcast 128.153.145.255 |
||
| + | |||
| − | dns-nameservers 128.153.145.3 128.153.145.4 |
||
</pre> |
</pre> |
||
After making modifications to this file, you can either restart networking (<code>/etc/init.d/networking restart</code>, <code>systemctl restart networking</code>, etc.) or use <code>ifup br0</code> |
After making modifications to this file, you can either restart networking (<code>/etc/init.d/networking restart</code>, <code>systemctl restart networking</code>, etc.) or use <code>ifup br0</code> |
||
| − | |||
| − | Manual set up: |
||
| − | |||
| − | 1) Create new bridge iterface "brctl addbr <bridge_name>" |
||
| − | |||
| − | 2) Add existing interface to bridge "brctl addif <bridge_name> <iterface_name>" |
||
| − | |||
| − | 3) Bring bridge up "ifconfig <bridge_name> up" |
||
| − | |||
Bridging interfaces will cause the interfaces used to not have an ip address even if they are up. The bridge interface will contain an ip address. |
Bridging interfaces will cause the interfaces used to not have an ip address even if they are up. The bridge interface will contain an ip address. |
||
| − | === |
+ | === Automated backups === |
| + | Phoenix and [[Bennu]] will perform weekly backups of each others running VMs. This is a WIP. |
||
| − | To migrate a VM from eevee (in the case that it was created by kimchi): |
||
| − | |||
| − | Put iso in /var/lib/libvirt/isos |
||
| − | |||
| − | Put xml file from dump into /var/lib/libvirt/qemu |
||
| − | |||
| − | (The dump can be had by running virsh dumpxml > vm_name.xml on eevee |
||
| − | |||
| − | ==== XML Edits ==== |
||
| − | |||
| − | You will, at the least, need to make sure the network interface is running in bridge mode. In <devices/>, make sure that the <interface/> node resembles something of the following: |
||
| − | |||
| − | <code><pre> |
||
| − | <interface type='bridge'> |
||
| − | <mac address='00:16:36:15:a1:dd'/> <!-- Usually generated, can be omitted for a random one IIRC --> |
||
| − | <source bridge='br0'/> |
||
| − | <model type='virtio'/> <!-- Other models may work, but are untested --> |
||
| − | <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> <!-- Probably also safe to omit --> |
||
| − | </interface> |
||
| − | </pre></code> |
||
| − | |||
| − | If you're doing this to an already running VM, you will need to ''completely'' shut it down and restart it--a reboot will not suffice. When in doubt, <code>shutdown</code>, <code>destroy</code>, <code>start</code>. The network adapter for the VM should now show up as one of the <code>vnet#</code> devices, and will be automatically assigned to <code>br0</code> (as above). |
||
| − | |||
| − | Put disk image in /var/lib/libvirt/images |
||
| − | |||
| − | virsh define <Your VM Name>.xml |
||
Revision as of 14:59, 21 August 2015
| Phoenix | |
| Contact Person: | CoreMaintainers |
| Last Update: | Summer 2015 |
| Services: | Various |
| Hostname: | phoenix.cslabs.clarkson.edu |
| Operating system: | Debian 8.0 Jessie |
| NIC 1: | Clarkson Network MAC: ? IP: 128.153.145.40 |
| CPU: | 2x Intel Xeon E5410 @ 2.33GHz |
| RAM: | 16 GB DDR2 |
Phoenix is our secondary VM host. It rose from the ashes of europa and xen2.
Phoenix has older drives than eevee, but several of them have never been used prior to being installed in Phoenix. Additionally, all 4 drives, which are 1 TB each, have been configured in RAID6 to allow for up to 2 failed drives and provide a total of 2 TB of storage. This is twice the amount of storage as eevee currently has and also twice the tolerance for failure.
Each of Phoenix's CPUs are much older than, but roughly comparable in performance to Bennu's CPU. Thus, Phoenix also has roughly twice the computing power as Bennu.
Setup
Generally, we followed the instructions on the debian wiki.
Things to install
apt install htop vim sudo qemu-kvm libvirt-bin virtinst screen rsync
Network Bridge Setup
In order for the VMs to be on our LAN, a bridge must be set up as follows:
In /etc/network/interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
auto eth0
auto eth1
auto eth2
auto br0
iface br0 inet static
address 128.153.145.40
netmask 255.255.254.0
gateway 128.153.144.1
bridge_ports all
After making modifications to this file, you can either restart networking (/etc/init.d/networking restart, systemctl restart networking, etc.) or use ifup br0
Bridging interfaces will cause the interfaces used to not have an ip address even if they are up. The bridge interface will contain an ip address.
Automated backups
Phoenix and Bennu will perform weekly backups of each others running VMs. This is a WIP.
