welcome: please sign in

Diff for "Hardware"

Differences between revisions 3 and 80 (spanning 77 versions)
⇤ ← Revision 3 as of 2006-06-24 21:09:04 →
Size: 1770
Editor: JustinLeitgeb
Comment:
← Revision 80 as of 2008-03-02 21:40:23 → ⇥
Size: 5225
Editor: NathanKennedy
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= New System Hardware = #pragma section-numbers off
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: This page collects information on the hardware that we have installed or plan to install at Peer1 as part of our hosting infrastructure.
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.		 [[TableOfContents()]]
Line 9: Line 7:
Also, it was mentioned that we should research hardware support contracts from any vendor that will be selling us equipment. = Peer1 =
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. This is a list of the stuff that is colocated at Peer1.
Line 13: Line 11:
This page will serve as a forum for collaborative research on the pieces of hardware that we need. == 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 15: Line 23:
== Servers == == 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 17: Line 30:
We will be purchasing two servers, which will be configured and sent to he.net for colocation. == mire: dynamic web content ==
http://docs.sun.com/source/817-5248-20/index.html
http://www.sun.com/servers/entry/v20z/images/gallery/full/img_3.jpg
 * Donated by: Ray Racine
 * Model: Sun Fire v20z
 * Processor: 1 x 1.6GHz AMD64 (Opteron)
 * RAM: 5 GB (initial 2x512MB and additional 2x2GB)
 * Disks: 2 x 36 GB Ultra320 SCSI (hot swap)
 * 1U
 * Ultra 320 SCSI controller embedded in mainboard
 * [http://onesearch.sun.com/search/docs/index.jsp?col=docs_en&locale=en&qt=Sun+Fire+v20z Search Sun for Product Documentation, including Maintenance and Troubleshooting Manuals for Sun Fire v20z]
Line 19: Line 42:
=== Server Hardware Specifications === '''Intended use: dynamic web content and any other Internet services that involve running arbitrary code from members (including custom daemons, etc.)'''
Line 21: Line 44:
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: == Xanadu: shell server? ==
 * Donated by: NathanKennedy
 * Model: Dell PowerEdge 1650
 * Dual P3 1.4GHz
 * 2G RAM
 * 18GB SCSI HDD
Line 23: Line 51:
 * Redundant power supplies.
 * Hardware RAID.
 * Dual CPU's, AMD seems to be a stronger option than Intel		 == krunk: secondary KDC and AFS server ==
 * KrunkInfoz
 * 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 61:
=== Server Hardware Vendors === == Other components ==
Line 29: Line 63:
== 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 66:
=== Switch Hardware Specifications === 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 68:
=== Switch Hardware Vendors === VLAN Configuration Proposal:
Line 35: Line 70:
== 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 91:
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
Line 39: Line 96:
=== Serial Port Specifications === === 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 41: Line 99:
=== Serial Port Vendors === 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 43: Line 101:
[http://www.cyclades.com/ Cyclades] was mentioned as one vendor of serial port devices which are linux-friendly. === 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].

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

= Tech.Coop =

This is a listing of the (virtual) machines colocated at Tech.Coop.

This page collects information on the hardware that we have installed or plan to install at Peer1 as part of our hosting infrastructure.

TableOfContents()

Peer1

This is a list of the stuff that is colocated at Peer1.

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.

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.

mire: dynamic web content

http://docs.sun.com/source/817-5248-20/index.html http://www.sun.com/servers/entry/v20z/images/gallery/full/img_3.jpg

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

Xanadu: shell server?

krunk: secondary KDC and AFS server

  • KrunkInfoz

  • 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

Other components

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

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]

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].

Standard KVM

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

Tech.Coop

This is a listing of the (virtual) machines colocated at Tech.Coop.

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