welcome: please sign in

Diff for "Hardware"

Differences between revisions 4 and 63 (spanning 59 versions)
⇤ ← Revision 4 as of 2006-06-24 21:13:44 →
Size: 1748
Editor: JustinLeitgeb
Comment: changed naming of sections
← Revision 63 as of 2007-09-14 07:38:22 → ⇥
Size: 5136
Editor: MichaelOlson
Comment: Migrate changes
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= New System Hardware = This page collects information on the hardware we plan to install at a colocation provider as part of our new hosting infrastructure. Some older discussion and similar stuff is on NewSystemHardwareArchive.
Line 3: Line 3:
During the HCoop IRC meeting on June 24, 2006, the group decided that it would based it's new system architecture on the following pieces of hardware: See also NewServersSetup for tasks remaining to be done to get these machcines ready for general use.
Line 5: Line 5:
 * Two robust servers, one that doesn't allow normal user logins, and one that does.
 * One switch to form a LAN between these servers.
 * One serial port device, to facilitate remote access to our servers.		 Currently, what we know are the uses for the three machines we will base our infrastructure on. We also know our Abulafia machine configuration, and Justin Leitgeb's donated server configuration. The machine configurations and intended uses follow:
Line 9: Line 7:
Also, it was mentioned that we should research hardware support contracts from any vendor that will be selling us equipment. [[TableOfContents()]]
Line 11: Line 9:
Additionally, group decided that the server that HCoop currently owns, Abulafia, will be brought to he.net for shell service. This will follow a necessary re-load of the OS software at a time to be determined later. = deleuze: fileserver, static HTML content =
 * Donated by: Justin Leitgeb
 * Model: Dell PowerEdge 2850
 * Processor: 2 x 2.8 GHz Intel Xeon
 * RAM: 4 GB
 * Disks:
  * 4 x 10K Seagate Cheetah SCSI drives, 73GB '''and'''
  * 2 x 10K Seagate Cheetah SCSI drives, 36GB
 * Extra: RAID kit, with battery, etc., 256 MB RAID cache, 2 power supplies
 * [https://dcse.dell.com/selfstudy/Associates_7_0/Enterprise/PowerEdge/PE2850/printer_friendly.asp Maintenance Manual for the PE 2850]
'''Intended use: fileserver and host for all services that don't involve dynamic content provided by non-admins. No user logins.'''
Line 13: Line 21:
This page will serve as a forum for collaborative research on the pieces of hardware that we need.
Line 15: Line 22:
== Servers ==
Line 17: Line 23:
We will be purchasing two servers, which will be configured and sent to he.net for colocation. = abulafia: shell server =
 * Processor: 1 x 900 MHz
 * RAM: 512 MB
 * Disks: 40 GB RAID 1 (2 x 40 GB 7200 RPM ATA drives)
 * Extra: 3Ware 6400 PCI ATA RAID controller
'''Intended use: refurbished slightly to serve as a generic shell server and the only machine where usage not strictly related to "Internet hosting" is permitted.'''
Line 19: Line 30:
=== Desired Features === = mire: dynamic web content =
 * Donated by: Ray Racine
 * Model: Sun Fire v20z
 * Processor: 1 x 1.6GHz AMD64 (Opteron)
 * RAM: 1 GB
 * Disks: 2 x 36 GB Ultra320 SCSI (hot swap)
 * 1U
 * Ultra 320 SCSI controller embedded in mainboard
 * [http://www.sun.com/products-n-solutions/hardware/docs/Servers/Workgroup_Servers/Sun_Fire_V20z/index.html Product Documentation, including Maintenance and Troubleshooting Manuals for Sun Fire v20z]
Line 21: Line 40:
These servers should be as redundant as possible. At this point, we cannot afford to have less than one point of failure in many areas, so we should look for the following features in our new servers: '''Intended use: dynamic web content and any other Internet services that involve running arbitrary code from members (including custom daemons, etc.)'''
Line 23: Line 42:
 * Redundant power supplies.
 * Hardware RAID.
 * Dual CPU's, AMD seems to be a stronger option than Intel		 = krunk: secondary KDC and AFS server =
 * Donated by: Adam Megacz
 * Model: Sun Netra
 * Processor:
 * RAM:
 * Disks:
  * 2 x 200GB Unknown RPM and Manufacturer
'''Intended use: secondary KDC and AFS server (backup) in event that the primary server (deleuze) goes down'''
Line 27: Line 51:
=== Proposed Models and Vendors === = Other components =
Line 29: Line 53:
== Ethernet Switch == == Switch ==
We are proceeding under the assumption that we'll use ShaunEmpie's donation (see HardwareDonations), a Nortel (Baystack) 380 switch. He says:
Line 31: Line 56:
=== Desired Features === It is not brand new but is working. Here is [http://vpit.net/es380-guide.pdf a guide] that I was able to find to give anyone interested a more in depth view of it.
Line 33: Line 58:
=== Proposed Models and Vendors === VLAN Configuration Proposal:
Line 35: Line 60:
== Serial Port == {{{
With our new setup, I think it would be best to setup a few different
VLANs for different uses. For anyone who is unfamiliar with the term, a
VLAN is a virtual lan. It allows you to have completely separate networks
on the same switch. This will allow us to setup a private network that
the public and peer1 would have no access to. This could be handy for
database systems, NAS, backup servers, etc which you'd want to keep off
the public network.
Proposed Configuration:
VLAN 1. Management VLAN - not used for normal traffic
VLAN 10. Public VLAN - public/Peer1's network
VLAN 20. Private VLAN - private subnet for inter-server traffic
For a starting point i think having ports 1-12 in VLAN 10 and ports 13-24
in VLAN 20 would be best. The VLAN membership of a port can be changed
easily so these would not be set in stone.
The switch allows for many more VLANs than we'll ever need so if anyone
has a suggestion or need for another VLAN it would be trivial to setup.
Any questions/comments, let me know.
-Shaun}}}
ES380 AC Power Specs:
Line 37: Line 81:
Docelic, or other users -- please update this section since I am entirely ignorant about these devices! :)  * Input current: 1.5A to 100 AC
 * Input voltage (rms): 100 to 240 VAC at 47 to 63 Hz
 * Power consumption: 150 W
 * Thermal rating: 1000 BTU/hr maximum
== Serial console ==
Some device to simulate local login over the Internet could be a life saver. JustinLeitgeb mentions a special card that Dell sells that would work with his donation.
Line 39: Line 88:
=== Desired Features === There are also some really good KVM-over-IP devices out there fairly cheap these days. My provider has one and it works very well, although on the client side you have to use this ugly Windows ActiveX control. I'm sure by now there are KVM-over-IP boxes that speak plain VNC. These should be well under $500. [AdamMegacz]
Line 41: Line 90:
=== Proposed Models and Vendors === == IP KVM ==
The StarTech Server Remote Control External KVM over IP provides access to systems that may have a degraded network. It allows us to monitor Power-On Self Test (POST), configure BIOS/CMOS, and even reinstall operating system software. It must be connected to another multiple port KVM in order to have access to more than one server. See [[http://www.startech.com/Data/ProductManuals/SV1110IPEXT.pdf?c=US manual]].
Line 43: Line 93:
[http://www.cyclades.com/ Cyclades] was mentioned as one vendor of serial port devices which are linux-friendly. == Standard KVM ==
We have a standard KVM to allow remote switching between servers as maintenance requires.

This page collects information on the hardware we plan to install at a colocation provider as part of our new hosting infrastructure. Some older discussion and similar stuff is on NewSystemHardwareArchive.

See also NewServersSetup for tasks remaining to be done to get these machcines ready for general use.

Currently, what we know are the uses for the three machines we will base our infrastructure on. We also know our Abulafia machine configuration, and Justin Leitgeb's donated server configuration. The machine configurations and intended uses follow:

TableOfContents()

1. deleuze: fileserver, static HTML content

Intended use: fileserver and host for all services that don't involve dynamic content provided by non-admins. No user logins.

2. abulafia: shell server

  • Processor: 1 x 900 MHz
  • RAM: 512 MB
  • Disks: 40 GB RAID 1 (2 x 40 GB 7200 RPM ATA drives)
  • Extra: 3Ware 6400 PCI ATA RAID controller

Intended use: refurbished slightly to serve as a generic shell server and the only machine where usage not strictly related to "Internet hosting" is permitted.

3. mire: dynamic web content

Intended use: dynamic web content and any other Internet services that involve running arbitrary code from members (including custom daemons, etc.)

4. krunk: secondary KDC and AFS server

  • Donated by: Adam Megacz
  • Model: Sun Netra
  • Processor:
  • RAM:
  • Disks:
    • 2 x 200GB Unknown RPM and Manufacturer

Intended use: secondary KDC and AFS server (backup) in event that the primary server (deleuze) goes down

5. Other components

5.1. Switch

We are proceeding under the assumption that we'll use ShaunEmpie's donation (see HardwareDonations), a Nortel (Baystack) 380 switch. He says:

It is not brand new but is working. Here is [http://vpit.net/es380-guide.pdf a guide] that I was able to find to give anyone interested a more in depth view of it.

VLAN Configuration Proposal: 

With our new setup, I think it would be best to setup a few different
VLANs for different uses.  For anyone who is unfamiliar with the term, a
VLAN is a virtual lan.  It allows you to have completely separate networks
on the same switch.  This will allow us to setup a private network that
the public and peer1 would have no access to.  This could be handy for
database systems, NAS, backup servers, etc which you'd want to keep off
the public network.
Proposed Configuration:
VLAN 1.     Management VLAN - not used for normal traffic
VLAN 10.    Public VLAN - public/Peer1's network
VLAN 20.    Private VLAN - private subnet for inter-server traffic
For a starting point i think having ports 1-12 in VLAN 10 and ports 13-24
in VLAN 20 would be best.  The VLAN membership of a port can be changed
easily so these would not be set in stone.
The switch allows for many more VLANs than we'll ever need so if anyone
has a suggestion or need for another VLAN it would be trivial to setup.
Any questions/comments, let me know.
-Shaun

ES380 AC Power Specs:

  • Input current: 1.5A to 100 AC
  • Input voltage (rms): 100 to 240 VAC at 47 to 63 Hz
  • Power consumption: 150 W
  • Thermal rating: 1000 BTU/hr maximum

5.2. Serial console

Some device to simulate local login over the Internet could be a life saver. JustinLeitgeb mentions a special card that Dell sells that would work with his donation.

There are also some really good KVM-over-IP devices out there fairly cheap these days. My provider has one and it works very well, although on the client side you have to use this ugly Windows ActiveX control. I'm sure by now there are KVM-over-IP boxes that speak plain VNC. These should be well under $500. [AdamMegacz]

5.3. IP KVM

The StarTech Server Remote Control External KVM over IP provides access to systems that may have a degraded network. It allows us to monitor Power-On Self Test (POST), configure BIOS/CMOS, and even reinstall operating system software. It must be connected to another multiple port KVM in order to have access to more than one server. See http://www.startech.com/Data/ProductManuals/SV1110IPEXT.pdf?c=US manual.

5.4. Standard KVM

We have a standard KVM to allow remote switching between servers as maintenance requires.

Hardware (last edited 2021-04-17 15:58:03 by ClintonEbadi)