welcome: please sign in

The following 164 words could not be found in the dictionary of 7 words (including 7 LocalSpellingWords) and are highlighted below:
able   about   add   Administration   allow   also   an   and   architecture   Architecture   architeture   are   as   at   back   Based   based   be   blueprint   break   build   by   can   capacity   Category   cluster   colocated   Colocation   connections   constructing   Contents   Coop   current   currently   daemon   deployment   describes   Description   deserves   Design   Details   develop   development   Diagram   diagram   divided   doesn   doing   edit   effort   end   eventually   expanded   file   files   for   from   future   Gigabit   goal   Goals   grow   have   hcoop   here   High   Historical   in   increased   information   initially   inter   into   involves   is   items   layout   Layout   Level   little   logins   looking   mail   main   manner   may   modify   My   needs   net   network   Network   new   next   node   now   Of   of   on   one   our   Our   out   Overview   page   Pages   Peer   physical   Physical   Plans   plug   Postgre   present   primary   processes   Providers   providers   provides   public   related   Related   right   same   section   separate   serve   server   servers   serves   Service   service   services   shell   should   sites   Software   software   switch   System   systems   Table   that   The   the   their   thing   think   This   this   three   to   us   used   user   users   want   We   we   web   well   which   will   with   written  

Clear message
Edit

SystemArchitecturePlans

1. Details about the next HCoop Architecture

This page will serve as the blueprint for the architecture that HCoop is constructing right now, to be colocated at Peer 1.

1.1. Network Overview

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

1.2. High-Level Architecture Description

The new HCoop architecture initially involves three servers; one for user shell logins, one for back-end services, and one for web service. Our goal is to build an architecture that serves us well based on our current needs, and can be expanded for increased capacity in the future with little effort.

Based on this, we should have one shell server that users edit and develop their web sites from. This will allow users to modify files on one web server in the present, and a cluster as we grow.

1.3. Design Goals

We should be able to plug new web servers into our architeture in the future in a manner that doesn't break our software systems. We may also want to think about doing the same thing with shell and file services.

1.4. Physical Network Layout

This section describes the HCoop physical network layout.

1.4.1. Physical Network Description

Gigabit switch, divided into VLAN for server inter-connections. LAN out to Peer 1.

1.4.2. Physical Network Diagram(s)

XXX add diagram here.

1.5. Software/System Layout

This deserves the separate page SoftwareArchitecturePlans.

1.5.1. Software/System Description

1.5.2. Software/System Diagram(s)

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


CategorySystemAdministration CategoryHistorical

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