welcome: please sign in

Diff for "Hardware"

Differences between revisions 51 and 52
Revision 51 as of 2006-07-06 15:19:28
Size: 4531
Editor: ShaunEmpie
Comment: Added vlan proposal to switch section
Revision 52 as of 2006-07-06 16:48:20
Size: 4061
Comment: Changed Penguin model, formatting on Shaun's notes.
Deletions are marked like this. Additions are marked like this.
Line 23: Line 23:
 * Processor: Dual AMD 248
 * RAM: 2 GB RAM
 * Disks: 2 x 73 RAID 1 SCSI
 * Extra: Should be 1U. Goal is to make it processor intensive, and only disk-heavy enough to ensure a high level of uptime. Other considerations such as a preference for AMD and the vendor Penguin Computing that have been expressed on the list and in meetings should be followed here.
 * Processor: Single AMD 275 (Dual-core)
 * RAM: 4 GB RAM (2 x 2 GB)
 * Disks: 2 x 120 GB SATA
 * Penguin Model: Altus 1
300
 * List price: $3
163.00
 * Extra: Should be 1U. Goal is to make it processor intensive, and only disk-heavy enough to ensure a high level of uptime. Other considerations such as a preference for AMD and the vendor Penguin Computing that have been expressed on the list and in meetings should be followed here.  More information from online configuration: [http://www.hcoop.net/~leitgebj/hcoop_servers/altus_1300_20060606.pdf (PDF)] [http://www.hcoop.net/~leitgebj/hcoop_servers/altus_1300_20060606.ps (PS)]
Line 29: Line 32:
JustinLeitgeb says:

 . The model that I like best for this machine of the previous configurations is the Penguin Altus 1400. It is a 1U machine with hardware SCSI RAID listing for $3463 [http://www.hcoop.net/~leitgebj/hcoop_servers/penguin_web_server.ps (postscript)] [http://www.hcoop.net/~leitgebj/hcoop_servers/penguin_web_server.pdf (PDF)][[BR]]
 We could go with SATA, but I would only do this if we can do it with hot-swappable disks in a 1U case. I suppose that SATA could be a better choice even if it isn't hot-swappable once we get a cluster of web servers... maybe we can get SATA now and live with the consequences until we reach this point. Ideas?[[BR]] I think that we should also negotiate with Penguin on the phone over this configuration.
Line 48: Line 47:
Line 49: Line 49:
Line 50: Line 51:
Line 51: Line 53:
Line 52: Line 55:
Line 55: Line 59:
Line 58: Line 63:
Line 59: Line 65:
Line 65: Line 72:
Line 66: Line 74:

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.

System setup

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 to-be-donated server configuration. What we need to come up with, is the ideal setup for the third machine that we will have to buy. So, the machine configurations and intended uses follow:

Justin Leitgeb's donation: Dell PowerEdge 2850

  • Processor: 2 x 2.8 GHz
  • 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

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

HCoop's currently-underused machine Abulafia

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

New server, for which we need to come up with hardware specifications

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

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.

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