welcome: please sign in

Diff for "Hardware"

Differences between revisions 57 and 209 (spanning 152 versions)
Revision 57 as of 2006-12-13 19:36:45
Size: 3584
Editor: MichaelOlson
Comment: Add names for machines and clean up page
Revision 209 as of 2019-04-20 00:32:27
Size: 2061
Editor: ClintonEbadi
Comment: upgraded outpost to stretch
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:
See also NewServersSetup for tasks remaining to be done to get these machcines ready for general use. This page collects information on the hardware that we have installed or plan to install as part of HCoop infrastructure.
Line 5: Line 5:
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>>
Line 7: Line 7:
[[TableOfContents()]] = Linode =
Line 9: Line 9:
= 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
'''Intended use: fileserver and host for all services that don't involve dynamic content provided by non-admins. No user logins.'''
== outpost ==
Line 20: Line 11:
= 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.'''
 Location:: Linode London
 Allocated Resources:: 1 vCPU, 2G RAM, 50G storage.
 Operating System:: Debian Stretch AMD64
 User Logins:: No
 Intended Use:: Secondar AndrewFileSystem server, DNS
 Details:: ServerOutpost
Line 27: Line 18:
= mire: dynamic web content =
 * Donated by: Ray Racine
 * Model: Sun Fire v20
 * Processor: 1 x 1.6GHz AMD64 (Opteron)
 * RAM: 1 GB
 * Disks: 2 x 36 GB Ultra320 SCSI (hot swap)
 * 1U
'''Use: secondary DNS on a different subnet, all tasks requiring remote location.'''
Line 35: Line 20:
'''Intended use: dynamic web content and any other Internet services that involve running arbitrary code from members (including custom daemons, etc.)''' = Digital Ocean =
Line 37: Line 22:
= Other components = == gibran ==
Line 39: Line 24:
== Switch ==
We are proceeding under the assumption that we'll use ShaunEmpie's donation (see HardwareDonations), a Nortel (Baystack) 380 switch. He says:
 Location:: DigitalOcean NYC3
 Allocated Resources:: 6 vCPU, 16G RAM, 320G storage. Additional block storage volume for OpenAFS `/vicepa`
 Operating System:: Debian Stretch AMD64
 User Logins:: No
 Intended Use:: Primary AndrewFileSystem fileserver and dbserver, primary MitKerberos KDC, SQL databases, [[ConfigurationManagent|Puppet Master]]
 Details:: ServerGibran
Line 42: Line 31:
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. == lovelace ==
Line 44: Line 33:
VLAN Configuration Proposal:  Location :: DigitalOcean NYC3
 Allocated Resources :: 2vCPU, 2G RAM, 60G storage.
 Operating System:: Debian Stretch AMD64
 User Logins:: No
 Intended Use:: Secondary AndrewFileSystem fileserver and dbserver, secondary MitKerberos KDC
 Details:: ServerLovelace
Line 46: Line 40:
{{{
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 67: Line 41:
 * 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.
== marsh ==

 Location:: DigitalOcean NYC3
 Allocated Resources:: 4vCPU, 8G RAM, 160G storage
 Operating System:: Debian Stretch AMD64
 User Logins:: Yes
 Intended Use:: Member logins
 Details:: ServerMarsh

== minsky ==

 Location:: DigitalOcean NYC3
 Allocated Resources:: 2vCPU, 4G RAM, 80G storage
 Operating System:: Debian Stretch AMD64
 User Logins:: No
 Intended Use:: Mail server and ejabberd server
 Details:: ServerMinsky

== shelob ==

 Location:: DigitalOcean NYC3
 Allocated Resources:: 4vCPU, 8G RAM, 160G storage
 Operating System:: Debian Stretch AMD64
 User Logins:: No
 Intended Use:: Web Server
 Details:: ServerShelob

= Awaiting setup =

None.

= Awaiting purchase =

None.

= Decommissioned =

See [[/Decommissioned]] for older machines

----
CategorySystemAdministration

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

Linode

outpost

Location
Linode London
Allocated Resources
1 vCPU, 2G RAM, 50G storage.
Operating System
Debian Stretch AMD64
User Logins
No
Intended Use

Secondar AndrewFileSystem server, DNS

Details

ServerOutpost

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

Digital Ocean

gibran

Location

DigitalOcean NYC3

Allocated Resources

6 vCPU, 16G RAM, 320G storage. Additional block storage volume for OpenAFS /vicepa

Operating System
Debian Stretch AMD64
User Logins
No
Intended Use

Primary AndrewFileSystem fileserver and dbserver, primary MitKerberos KDC, SQL databases, Puppet Master

Details

ServerGibran

lovelace

Location

DigitalOcean NYC3

Allocated Resources
2vCPU, 2G RAM, 60G storage.
Operating System
Debian Stretch AMD64
User Logins
No
Intended Use

Secondary AndrewFileSystem fileserver and dbserver, secondary MitKerberos KDC

Details

ServerLovelace

marsh

Location

DigitalOcean NYC3

Allocated Resources
4vCPU, 8G RAM, 160G storage
Operating System
Debian Stretch AMD64
User Logins
Yes
Intended Use
Member logins
Details

ServerMarsh

minsky

Location

DigitalOcean NYC3

Allocated Resources
2vCPU, 4G RAM, 80G storage
Operating System
Debian Stretch AMD64
User Logins
No
Intended Use
Mail server and ejabberd server
Details

ServerMinsky

shelob

Location

DigitalOcean NYC3

Allocated Resources
4vCPU, 8G RAM, 160G storage
Operating System
Debian Stretch AMD64
User Logins
No
Intended Use
Web Server
Details

ServerShelob

Awaiting setup

None.

Awaiting purchase

None.

Decommissioned

See /Decommissioned for older machines


CategorySystemAdministration

Hardware (last edited 2019-04-20 00:32:27 by ClintonEbadi)