welcome: please sign in

Diff for "Hardware"

Differences between revisions 53 and 82 (spanning 29 versions)
⇤ ← Revision 53 as of 2006-07-06 20:55:24 →
Size: 4106
Editor: JustinLeitgeb
Comment: updated link to hardware config
← Revision 82 as of 2008-03-10 02:01:32 → ⇥
Size: 3731
Editor: DavorOcelic
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
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. #pragma section-numbers off
Line 3: Line 3:
= 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:		 This page collects information on the hardware that we have installed or plan to install as part of HCoop infrastructure.
Line 6: Line 5:
== Justin Leitgeb's donation: Dell PowerEdge 2850 ==
 * Processor: 2 x 2.8 GHz		 [[TableOfContents()]]

== deleuze ==
 * Location: Peer1
 * Model: Dell PowerEdge 2850
 * Processor: 2 x 2.8 GHz Intel Xeon
Line 13: Line 16:
'''Intended use: fileserver and host for all services that don't involve dynamic content provided by non-admins. No user logins.'''  * OS: Debian stable
 * User logins: no
 * Source: donation by Justin Leitgeb
Line 15: Line 20:
== HCoop's currently-underused machine Abulafia ==  * [https://dcse.dell.com/selfstudy/Associates_7_0/Enterprise/PowerEdge/PE2850/printer_friendly.asp Maintenance Manual for the PE 2850]

'''Use: fileserver, database server, email server, host for all services that don't involve dynamic content provided by non-admins.'''

== mire ==

 * Location: Peer1
 * 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
 * OS: Debian stable
 * User logins: yes
 * Source: donated by Ray Racine

 * [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]
 * http://docs.sun.com/source/817-5248-20/index.html
 * http://www.sun.com/servers/entry/v20z/images/gallery/full/img_3.jpg

'''Use: dynamic web content, services that involve running arbitrary code from members (including custom daemons, etc.)'''

== krunk ==

 * Location: Peer1
 * Model: Sun Netra
 * Processor:
 * RAM:
 * Disks:
  * 2 x 200GB Unknown RPM and Manufacturer
 * OS: Debian stable?
 * User logins: no
 * Source: donation by Adam Megacz

 * KrunkInfoz

'''Use: secondary KDC and AFS server'''

== baltar ==

 * Location: Peer1
 * Nortel Baystack 380 switch
 * 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

 * Source: donation by ShaunEmpie

 * [http://vpit.net/es380-guide.pdf ES380 Guide]

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

 * Location: Peer1
 * Source: Newegg?

 * [http://www.startech.com/Data/ProductManuals/SV1110IPEXT.pdf?c=US StarTech manual].

== Standard KVM ==

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


== outpost ==
 * Location: Tech.Coop (hosted at Bytemark, UK)
 * Model: Xen VM
 * Processor:
 * RAM: 512 MB
 * Disk: 40 GB RAID
 * OS: Debian stable
 * User logins: no

'''Use: secondary DNS on a different subnet, all tasks requiring remote location.'''


= Awaiting setup =

== xanadu ==

 * Model: Dell PowerEdge 1650
 * Dual P3 1.4GHz
 * 2G RAM
 * 18GB SCSI HDD
 * Source: donation by NathanKennedy

'''Use: '''



= Awaiting purchase =

There are currently no new systems awaiting purchase.

= Decommissioned =

== abulafia: shell server ==
Line 21: Line 124:

== New server, for which we need to come up with hardware specifications ==
 * Processor: Up for debate
 * RAM: 4 GB RAM (2 x 2 GB)
 * Disks: 2 x 120 GB SATA
 * 3 year, on-site hardware support (only adds $119)
 * Penguin Model: Altus 1300
 * List price: $3163.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_3.pdf (PDF)] [http://www.hcoop.net/~leitgebj/hcoop_servers/altus_1300_20060606_3.ps (PS)]

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

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

TableOfContents()

deleuze

Use: fileserver, database server, email server, host for all services that don't involve dynamic content provided by non-admins.

mire

Use: dynamic web content, services that involve running arbitrary code from members (including custom daemons, etc.)

krunk

  • Location: Peer1
  • Model: Sun Netra
  • Processor:
  • RAM:
  • Disks:
    • 2 x 200GB Unknown RPM and Manufacturer
  • OS: Debian stable?
  • User logins: no
  • Source: donation by Adam Megacz

  • KrunkInfoz

Use: secondary KDC and AFS server

baltar

  • Location: Peer1
  • Nortel Baystack 380 switch
  • 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

  • Source: donation by ShaunEmpie

  • [http://vpit.net/es380-guide.pdf ES380 Guide]

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.

Standard KVM

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

outpost

  • Location: Tech.Coop (hosted at Bytemark, UK)
  • Model: Xen VM
  • Processor:
  • RAM: 512 MB
  • Disk: 40 GB RAID
  • OS: Debian stable
  • User logins: no

Use: secondary DNS on a different subnet, all tasks requiring remote location.

Awaiting setup

xanadu

Use:

Awaiting purchase

There are currently no new systems awaiting purchase.

Decommissioned

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.

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