Difference between revisions of "Phoenix"

From CSLabsWiki
 
(14 intermediate revisions by 4 users not shown)
Line 1: Line 1:
  +
{{Archived}}
{{services
 
|contact_person = [[CoreMaintainers]]
 
|last_update = ''Summer 2015''
 
|services = Various
 
|category = Machines
 
|handoff = no
 
}}
 
   
  +
'''Phoenix''' was our secondary VM host. It rose from the ashes of '''europa''' and '''xen2'''. It has since been decommissioned because the computer was crashing too often, and from it's ashes rose '''[[Felix]]'''..
{{Machine
 
| screenshot =
 
| maintainer = [[CoreMaintainers]]
 
| hostname = phoenix.cslabs.clarkson.edu
 
| operating_system = Debian 8.0 Jessie
 
| interface1 = {{Network Interface | name=Clarkson Network | mac=? | ip=128.153.145.40}}
 
| cpuspecs = 2x Intel Xeon E5410 @ 2.33GHz
 
| ramspecs = 16 GB DDR2
 
}}
 
   
  +
'''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 is our secondary VM host. It rose from the ashes of [[europa]] and [[xen2]] It is currently in development.
 
   
  +
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]].
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.
 
   
 
== Setup ==
 
== Setup ==
Line 25: Line 11:
   
 
=== Things to install ===
 
=== Things to install ===
apt-get install htop vim sudo qemu-kvm libvirt-bin virtinst
+
apt install htop vim sudo qemu-kvm libvirt-bin virtinst screen rsync
   
 
=== Network Bridge Setup ===
 
=== Network Bridge Setup ===
Line 32: Line 18:
 
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 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>
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"
 
   
  +
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>
   
 
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.
   
=== Migration from eevee ===
+
=== Automated backups ===
  +
Phoenix and [[Bennu]] will perform weekly backups of each others running VMs. This is a WIP.
To migrate a VM from eevee:
 
 
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
 
 
(The xml file will need to be edited, see the debian wiki)
 
   
  +
== Current VMs ==
Put disk image in /var/lib/libvirt/images
 
  +
Main VMs that are currently on Phoenix include
   
  +
* [[bouncer]]
virsh define <Your VM Name>.xml
 
  +
* [[talks]]
  +
* [[fsuvius]]
  +
* [[frux]]
  +
* [[print]]

Latest revision as of 21:47, 14 January 2017


Phoenix was our secondary VM host. It rose from the ashes of europa and xen2. It has since been decommissioned because the computer was crashing too often, and from it's ashes rose Felix..

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.

Current VMs

Main VMs that are currently on Phoenix include