|
Size: 4106
Comment: Fixed price
|
Size: 2085
Comment: peer1 servers have all be removed
|
| 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 * 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.''' |
<<TableOfContents>> |
| Line 15: | Line 7: |
| == 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.''' |
= Linode = |
| Line 22: | Line 9: |
| == 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: $2702.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)] |
== outpost == |
| Line 31: | Line 11: |
| '''Intended use: dynamic web content and any other Internet services that involve running arbitrary code from members (including custom daemons, etc.)''' | * Location: Linode (hosted at UK data center) * Model: Xen VM * Processor: 8 cores (1x priority?) * RAM: 1024 MB * Disk: 40 GB * OS: Debian wheezy * User logins: no |
| Line 33: | Line 19: |
| == Switch == We are proceeding under the assumption that we'll use ShaunEmpie's donation (see HardwareDonations), a Nortel (Baystack) 380 switch. He says: |
'''Use: secondary DNS on a different subnet, all tasks requiring remote location.''' |
| Line 36: | Line 21: |
| 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. | = Digital Ocean = |
| Line 38: | Line 23: |
| VLAN Configuration Proposal: | == gibran == |
| Line 40: | Line 25: |
| {{{ 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. |
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 49: | Line 32: |
| Proposed Configuration: | == lovelace == |
| Line 51: | Line 34: |
| VLAN 1. Management VLAN - not used for normal traffic | 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 53: | Line 41: |
| VLAN 10. Public VLAN - public/Peer1's network | |
| Line 55: | Line 42: |
| VLAN 20. Private VLAN - private subnet for inter-server traffic | == marsh == |
| Line 57: | Line 44: |
| 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. |
Location:: DigitalOcean NYC3 Allocated Resources:: 4vCPU, 8G RAM, 160G storage Operating System:: Debian Stretch AMD64 User Logins:: Yes Intended Use:: Member logins Details:: ServerMarsh |
| Line 61: | Line 51: |
| 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. |
== minsky == |
| Line 65: | Line 53: |
| -Shaun}}} | 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 |
| Line 67: | Line 60: |
| ES380 AC Power Specs: | == shelob == |
| Line 69: | Line 62: |
| * 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 |
Location:: DigitalOcean NYC3 Allocated Resources:: 4vCPU, 8G RAM, 160G storage Operating System:: Debian Stretch AMD64 User Logins:: No Intended Use:: Web Server Details:: ServerShelob |
| Line 74: | Line 69: |
| == Serial console == | = Awaiting setup = |
| Line 76: | Line 71: |
| 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. | None. = Awaiting purchase = New virtual servers, see VirtualizedHosting2018 and ServerMigration2018. = 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.
Contents
Linode
outpost
- Location: Linode (hosted at UK data center)
- Model: Xen VM
- Processor: 8 cores (1x priority?)
- RAM: 1024 MB
- Disk: 40 GB
- OS: Debian wheezy
- User logins: no
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
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
marsh
- Location
DigitalOcean NYC3
- Allocated Resources
- 4vCPU, 8G RAM, 160G storage
- Operating System
- Debian Stretch AMD64
- User Logins
- Yes
- Intended Use
- Member logins
- Details
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
shelob
- Location
DigitalOcean NYC3
- Allocated Resources
- 4vCPU, 8G RAM, 160G storage
- Operating System
- Debian Stretch AMD64
- User Logins
- No
- Intended Use
- Web Server
- Details
Awaiting setup
None.
Awaiting purchase
New virtual servers, see VirtualizedHosting2018 and ServerMigration2018.
Decommissioned
See /Decommissioned for older machines