Difference between revisions of "Phoenix"

From CSLabsWiki
(Created page with "{{services |contact_person = CoreMaintainers |last_update = ''Spring 2015'' |services = Various |category = Machines |handoff = no }} {{Machine | screenshot = | maintain...")
 
 
(23 intermediate revisions by 4 users not shown)
Line 1: Line 1:
  +
{{Archived}}
−
{{services
  
−
|contact_person = [[CoreMaintainers]]
  
−
|last_update = ''Spring 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 = Unknown?
  
−
| operating_system = Debian 8.0 Jessie
  
−
| cpuspecs = 2x Intel Xeon E5410 @ 2.33GHz
 
−
| ramspecs = 16 GB DDR2
  
−
| IP Address = 128.153.145.40
  
−
}}
  
   
  +
'''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]].
  +
  +
== Setup ==
  +
Generally, we followed the [https://wiki.debian.org/KVM 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:
  +
<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
  +
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
  +
  +
  +
</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>
  +
  +
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
  +
  +
* [[bouncer]]
  +
* [[talks]]
  +
* [[fsuvius]]
  +
* [[frux]]
  +
* [[print]]

Latest revision as of 21:47, 14 January 2017

Emblem-important.png This is an archived article or section.
This page is a legacy practice, project, or tutorial, and the information may not be up to date. See the talk page for more information about the page's status.


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

Retrieved from "http://docs.cslabs.clarkson.edu/mediawiki/index.php?title=Phoenix&oldid=8317"