Difference between revisions of "Bennu"

From CSLabsWiki
Jump to: navigation, search
m (Updated maintainer & OS)
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{services
 
{{services
 
|ip_addr = 128.153.145.41
 
|ip_addr = 128.153.145.41
|contact_person = [[User:Bruskajp|James Bruska]] & [[User:Jared|Jared Dunbar]]
+
|contact_person = [[User:xperia64|xperia64]]  
|last_update = ''September 2016''
+
|last_update = ''Apirl 2017''
|services = most vital Virtual Machines
+
|services = fog
 
|category = Machines
 
|category = Machines
 
|handoff = no
 
|handoff = no
Line 10: Line 10:
 
{{Machine
 
{{Machine
 
| screenshot =  
 
| screenshot =  
| maintainer = [[User:Bruskajp|James Bruska]] & [[User:Jared|Jared Dunbar]]
+
| maintainer = [[User:xperia64|xperia64]]
 
| hostname = bennu.cslabs.clarkson.edu
 
| hostname = bennu.cslabs.clarkson.edu
| operating_system = Debian 8.3
+
| operating_system = Arch
 
| interface1 = {{Network Interface | name=Clarkson Network | mac=0c:c4:7a:04:3c:38  | ip=128.153.145.41}}
 
| interface1 = {{Network Interface | name=Clarkson Network | mac=0c:c4:7a:04:3c:38  | ip=128.153.145.41}}
 
| cpuspecs = Intel Xeon E5-2603 @ 1.80 GHz (4 cores)
 
| cpuspecs = Intel Xeon E5-2603 @ 1.80 GHz (4 cores)
 
| ramspecs = 16 GB
 
| ramspecs = 16 GB
 
}}
 
}}
Bennu is our primary VM host. It was formerly known as eevee. It has a pair of mirrored 1 TB drives, and so it can tolerate 1 disk failure and has 1 TB of storage.
+
Bennu is our primary VM host. It was formerly a vm host with the VMs:
 
 
The setup for Bennu was the same as for [[Phoenix]].
 
 
 
== Current VMs ==
 
VMs that are currently on Bennu include
 
  
 
* [[Docs]]
 
* [[Docs]]
Line 28: Line 23:
 
* [[odin]]
 
* [[odin]]
 
* [[Serenity]]
 
* [[Serenity]]
* [[dubsdot]]
+
* [[DubsDot]]
 +
 
 +
 
 +
It was known as eevee before that. It has a pair of mirrored 1 TB drives, and so it can tolerate 1 disk failure and has 1 TB of storage.
 +
 
 +
The setup for Bennu was the same as for [[Phoenix]] before i got my hands on it.
 +
 
 +
==Setup==
  
=Virtual Machine Core Allocation=
+
Bennu was purposed  for fog after the fog VM had some minor issues. These issues may have been related to me mounting an nfs share on bacon to a directory in the vm, then using FUSE file system (bindfs) to mount it to another location so that fog clients could upload images. This was done because there are kernel restrictions on sharing directories through NFS that are not physically present.
  
These are cores that are allocated to VM's for efficiency.
+
Bennu had a base setup of Ubuntu server, from which i downloaded the fog setup files, and the script that installed this as a promary fog server that does not offer DHCP services. Form there the server was set up and all of teh configuration was done withing the FOG application.
  
<pre style="background-color:#ffcccc">
 
virsh vcpupin <guestname> <local-core> <host core>
 
</pre>
 
  
Host cores are between 0 and 3
+
==Updates==
 +
Technology changes and things tend to break. When they do, try updating to the latest release candidate, and update to stable releases when the come out (to do so see http://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk). We are currently on version 1.4.0-RC-8 (as of 4/26/17) which has fixes to issues the prevent us from initializing the fog client properly when the first network interface is down.
  
You must run it for each core to each host core
+
Monitor https://forums.fogproject.org/category/22/announcements for new stable releases. I would suggest upgrading tho those, but i would avoid upgrading to a release candidate (beta) unless to fix a known issue or for an important feature.
  
{| class="wikitable"
+
==Maintenance and Troubleshooting==
! CPU CORE
+
So, looks like google-fu, updating fog, and the OS on bennu didn’t work. Congratulations, you either found a bug or broke something in an unusual way. Try making a post at https://forums.fogproject.org/ . They are a great community, very helpful and friendly. And senior developers frequent the forums, so finding a solution to your issue should be very simple.
! ALLOCATION
 
|-
 
|0
 
|System, [[Docs]]
 
|-
 
|1
 
|[[odin]]
 
|-
 
|2
 
|[[bouncer]],[[serenity]]
 
|-
 
|3
 
|[[dubsdot]]
 
|}
 

Latest revision as of 12:13, 24 August 2017

Bennu
IP Address(es): 128.153.145.41
Contact Person: xperia64
Last Update: Apirl 2017
Services: fog


Hostname: bennu.cslabs.clarkson.edu
Operating system: Arch
NIC 1: Clarkson Network
MAC: 0c:c4:7a:04:3c:38
IP: 128.153.145.41
CPU: Intel Xeon E5-2603 @ 1.80 GHz (4 cores)
RAM: 16 GB

Bennu is our primary VM host. It was formerly a vm host with the VMs:


It was known as eevee before that. It has a pair of mirrored 1 TB drives, and so it can tolerate 1 disk failure and has 1 TB of storage.

The setup for Bennu was the same as for Phoenix before i got my hands on it.

Setup

Bennu was purposed for fog after the fog VM had some minor issues. These issues may have been related to me mounting an nfs share on bacon to a directory in the vm, then using FUSE file system (bindfs) to mount it to another location so that fog clients could upload images. This was done because there are kernel restrictions on sharing directories through NFS that are not physically present.

Bennu had a base setup of Ubuntu server, from which i downloaded the fog setup files, and the script that installed this as a promary fog server that does not offer DHCP services. Form there the server was set up and all of teh configuration was done withing the FOG application.


Updates

Technology changes and things tend to break. When they do, try updating to the latest release candidate, and update to stable releases when the come out (to do so see http://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk). We are currently on version 1.4.0-RC-8 (as of 4/26/17) which has fixes to issues the prevent us from initializing the fog client properly when the first network interface is down.

Monitor https://forums.fogproject.org/category/22/announcements for new stable releases. I would suggest upgrading tho those, but i would avoid upgrading to a release candidate (beta) unless to fix a known issue or for an important feature.

Maintenance and Troubleshooting

So, looks like google-fu, updating fog, and the OS on bennu didn’t work. Congratulations, you either found a bug or broke something in an unusual way. Try making a post at https://forums.fogproject.org/ . They are a great community, very helpful and friendly. And senior developers frequent the forums, so finding a solution to your issue should be very simple.