Difference between revisions of "NPG Layout"

From Nuclear Physics Group Documentation Pages
Jump to navigationJump to search
m (Our Layout moved to NPG Layout)
 
(35 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
=Systems and Services=
+
This page provides some diagrams and information about how our server systems and [[VMWare|virtual machines]] are organized. For detailed information about our network layout, see the [[Network|network]] page.
 +
 
 +
= Systems Diagram =
  
 
Here is a diagram of our current system layout.  
 
Here is a diagram of our current system layout.  
 +
 +
[[Image:System layout current.png]]
  
 
'''Black''' Systems represent physical hardware.
 
'''Black''' Systems represent physical hardware.
Line 9: Line 13:
 
'''Arrows''' indicate which system a Virtual Machine is running on. Other hosts with VMWare capability can be used to fill in for the main Virtualization server during downtime.
 
'''Arrows''' indicate which system a Virtual Machine is running on. Other hosts with VMWare capability can be used to fill in for the main Virtualization server during downtime.
  
−
'''Services''' are listed beneath each system's name, followed by the specific software used to provide that service.
+
'''Operating System''' is listed in italics beneath each system's name
−
 
 
−
[[Image:system_layout_current.png]]
 
−
 
 
−
=System Redesign=
 
−
 
 
−
This area features the current working diagrams for the proposed system redesign that will occur with the replacement of the current [[Einstein]] hardware. Working copies of the Dia files for these diagrams are located in my Public folder ( /net/home/aduston/Public/Diagrams ) If they need to be changed or updated.
 
−
<br/>
 
−
<br/>
 
−
 
 
−
== First Revised design ==
 
−
 
 
−
This updated diagram incorporates Maurik's suggested changes:
 
  
−
[[Image:proposed_redesign_01.png]]
+
'''Services''' are listed in the second row of the diagram, followed by the name of the software used to provide that service.
  
 +
=System Descriptions=
  
−
=== Questions / Concerns ===
+
Brief descriptions of our computing systems. For more detailed information see the [[Servers_and_Workstations|servers and workstations]] page.
  
−
This design attempts to minimize the number of virtual machines which frees up a couple of host names. I made Corn a backup DNS server that would run on Taro because this is the best way to failover in case something happens with Jalapeno. Even if Einstein goes down entirely we'll at least have one DNS server still running.
+
==Server Hardware==
  
−
Corn is running Debian and is designed to be a standalone Bugzilla appliance. It is not known whether this will make it difficult to add the DNS functionality ( it should be as simple as installing the service and copying the configuration from Jalapeno ). This needs to be investigated. An alternative is leaving Corn as a standalone and using the Okra virtual machine to provide printing as well as acting as a backup DNS.
+
'''[[Endeavour]]''' is a 26-node beowulf cluster.
  
−
It is not known yet whether the old Einstein will be usable as a mirror / failover for the new Einstein. This should be investigated. If it is, we should also investigate whether it will need a Red Hat license, or if CentOS will be sufficient.  
+
'''[[Gourd]]''' is a 2U rackmount server from [http://www.microway.com/ Microway] with two Quad-Core AMD Opteron processors and 32 GB of memory. It is the workhorse of the NPG server farm, hosting user's home folders as well as acting as the primary host for [[kvm]] virtual machines.
  
−
== Initial Proposed Design ==
+
'''[[Lentil]]''' is our backup server, and it is a custom built Dual-Core Pentium D machine with 2 GB of memory.
  
−
This design is deprecated, but left here for reference purposes.
+
'''[[Pumpkin]]''' is a Microway 5U rackmount server with four Dual-Core AMD Opteron processors and 32 GB of memory. It is used primarily for data storage and computation.
  
 +
'''[[Taro]]''' is a computation and data storage server with two Quad-Core Intel Xenon processors and 24 GB of memory. It also serves as a secondary host for virtual machines.
  
−
[[Image:system_layout_future.png]]
+
'''[[Tomato]]''' was previously Einstein, and now is a secondary [[DNS]] server and [[kvm]] host.

Latest revision as of 15:57, 15 August 2013

This page provides some diagrams and information about how our server systems and virtual machines are organized. For detailed information about our network layout, see the network page.

Systems Diagram

Here is a diagram of our current system layout.

System layout current.png

Black Systems represent physical hardware.

Blue Systems represent Virtual Machines

Arrows indicate which system a Virtual Machine is running on. Other hosts with VMWare capability can be used to fill in for the main Virtualization server during downtime.

Operating System is listed in italics beneath each system's name

Services are listed in the second row of the diagram, followed by the name of the software used to provide that service.

System Descriptions

Brief descriptions of our computing systems. For more detailed information see the servers and workstations page.

Server Hardware

Endeavour is a 26-node beowulf cluster.

Gourd is a 2U rackmount server from Microway with two Quad-Core AMD Opteron processors and 32 GB of memory. It is the workhorse of the NPG server farm, hosting user's home folders as well as acting as the primary host for kvm virtual machines.

Lentil is our backup server, and it is a custom built Dual-Core Pentium D machine with 2 GB of memory.

Pumpkin is a Microway 5U rackmount server with four Dual-Core AMD Opteron processors and 32 GB of memory. It is used primarily for data storage and computation.

Taro is a computation and data storage server with two Quad-Core Intel Xenon processors and 24 GB of memory. It also serves as a secondary host for virtual machines.

Tomato was previously Einstein, and now is a secondary DNS server and kvm host.

Retrieved from "https://nuclear.unh.edu/wiki/index.php?title=NPG_Layout&oldid=5567"