welcome: please sign in

Diff for "SystemArchitecturePlans"

Differences between revisions 4 and 5
Revision 4 as of 2006-03-25 17:07:01
Size: 4789
Comment:
Revision 5 as of 2006-03-25 17:09:46
Size: 4917
Comment:
Deletions are marked like this. Additions are marked like this.
Line 41: Line 41:
Here we should talk about the specific networking equipment that we need. Ideas on vendors or models for the gigabit switch? Thoughts on if we should start with a hardware firewall device? Here we should talk about the specific networking equipment that we need. Ideas on vendors or models for the gigabit switch? Thoughts on if we should start with a hardware firewall device?  Also it was mentioned that we should invest in a serial console for remote access when a machine goes down. Thoughts on this?

1. Details about the next Hcoop Architecture

This page is intended to facilitate discussion of details relating to our next server architecture. Currently, the first draft of this page, written on Sat Mar 25 10:18:12 EST 2006 by JustinLeitgeb, is based upon discussions from the hcoop mailing list. Please feel free to contribute or change anything here!

1.1. Hcoop Future Network Overview

The architecture for the next hcoop.net network involves three physical servers:

  • A fileserver, running AFS which is accessible via ssh only for administrative purposes
  • A public login and http server, accessible by all members. User files are stored on the fileserver mentioned above. This will host all user pages, including dynamic content.
  • A server for hcoop needs that most users won't need direct shell access to. This will run Cyrus IMAP, exim, and Apache primarily for hcoop administrative purposes.

Additionally, we will need certain networking equipment:

  • A gigabit switch that will be the initial backbone of the hcoop LAN.
  • Perhaps (still not finalized in plans) a hardware firewall for the hcoop LAN. Ideas on this from members?

We should also remember that all of our servers will most likely have at least two NIC's. How can we utilize these best? Some sites have one NIC doing backups or logging, and another handling requests from the Internet. Perhaps we could segment our traffic to two local area networks, one for services to the Internet and another for local file access (i.e., traffic between the two "public" servers and the file server).

1.2. Hcoop Future Network Diagrams

The following are a preliminary version of a network plan that JustinLeitgeb created on March 25, 2006, after discussions on the hcoop.net mailing list. Included in the design is a hardware firewall, which was not finalized in previous discussions. Let's collect thoughts and alternate plans here as we work towards solidifying plans.

  • [attachment:network_diagram_20060325.dia Network planning diagram in "dia" format for editing]
  • [attachment:network_diagram_20060325.png Network planning diagram in PNG format for easier viewing]

1.3. Server Hardware

This may be a moot point as we are looking for a shop that can give us hardware support, and this may require that we buy their supported machines. However, it seems that many colocation providers will try to push us into a deal where their support consists in a "remote hands" plan where they will fix any reasonably standard hardware that we send to them for an hourly rate. If that is the case, our discussions on possible server hardware on the list may still be valid. Generally, we have decided that what we need in terms of hardware is more or less as follows:

  • Two web servers with at least 1GB of RAM each. Redundancy should include a RAID 1 configuration with two 73 GB drives, and dual power supplies.
  • One file server with more storage space and room to grow. It doesn't need to be exceptionally fast because of AFS's caching mechanisms. Perhaps a small RAID 5 configuration of 3 x 500 GB SATA devices would be a good place to start. It should certainly be hardware - based RAID so that main CPU power is not needed for read and write operations. JustinLeitgeb suggested a [http://www.3ware.com/products/serial_ata2-9000.asp 3Ware Escalade Controller] in this machine.

The list also discussed hardware vendors. If this isn't a moot point based on our decision of a colo provider with specific needs, the following list of possibilities may still be relevant:

1.4. Networking Hardware

Here we should talk about the specific networking equipment that we need. Ideas on vendors or models for the gigabit switch? Thoughts on if we should start with a hardware firewall device? Also it was mentioned that we should invest in a serial console for remote access when a machine goes down. Thoughts on this?

1.5. Page version history

Initial page created Sat Mar 25 11:52:03 EST 2006 JustinLeitgeb.

ColocationPlans is the main page for items related to the new architecture. ColocationPlansServiceProviders provides information about the service providers we are currently looking at.

SystemArchitecturePlans (last edited 2012-12-14 17:03:35 by ClintonEbadi)