System Hardware*Draft* 08/09/2000

• What hardware will we need for:– Development of DSpace– Initial rollout of DSpace to customers– DSpace usage through ~06/2002.

Proposed HardwareFY’2000

De

velo

pmen

tE

nvi

ronm

ent

Pro

duct

ion

En

viro

nmen

t

Big BrotherN-Class

Production Server

- Mirrored Metadata- Unmirrored Data Siloon each of two partitions:- staging & regression- production

Little BrotherN-Class

Staging Server

RAID

AppServer

switch

Web Requests

AppServer

Little Brother upgradableto carry production loadif necessary, whileupgrades and/ormaintenance occurson Big Brother

AppServer

WS / App Server

WS / App Server

WS

WS

WS

TrailBlazerN-Class

Dev Server

Backup Server

Tape BackupSystem

WSNew FY2000 Existing

Legend:

Prod Capacity

Proposed HardwareFY’2001

De

velo

pmen

tE

nvi

ronm

ent

Pro

duct

ion

En

viro

nmen

t

Big BrotherN-Class

Production Server

Little BrotherN-Class

Staging Server

RAID

AppServer

switch

Web Requests

AppServer

Little Brother upgradableto carry production loadif necessary, whileupgrades and/ormaintenance occurson Big Brother

AppServer

WS / App Server

WS / App Server

WS

WS

WS Tra

ilBla

zer

N-C

lass

Dev

Ser

ver

Backup Server

Tape BackupSystem

WS

AppServer

switch VideoServer

Prod Capacity

xtra CPU / DRAMxtra CPU / DRAM

Tape BackupSystem

Prod Capacity

New FY2001 Existing

Legend:

Rationalization (1)

• Need distinct development and production environments– Must develop & improve DSpace while customers are using it.

– Set up this infrastructure sooner rather than later

• Need staging server distinct from production server– primary problem solved: regression before production installation

– secondary problem solved: prod/staging servers are switchable (no installation/upgrade induced

downtime)

• Need app server web front ends– for scaling traffic. Start with two to prove it works.

Rationalization (2)

• Need mirrored metadata (to avoid reconstructing a DB)

• Do NOT need mirrored data silo(tape backup, <24 hour latency will suffice)

• Buy only enough CPUs, Disk, Tape to get by in FY 2000.– Get entire server infrastructure in place, but…

– Price of CPUs, Disks will fall with time, so wait until FY 2001 to buy and install production capacity.

What to BuyFY2000

FY 2000• (1) Local Director IP Switch prod load balance• (1) N-Class, 2way, 4GB RAM, 200GB RAID Big Brother• (1) N-Class, 2way, 4GB RAM Little Brother• (3) LpR, 2way, 1GB RAM App Servers• (1) N-Class, 2way, 4GB RAM Dev Server• (1) A-Class, ?? 1way, 1GB RAM ?? Backup Server• (1) Tape System Backup Storage

What to BuyFY2001

FY 2001• +1 Local Director IP Switch Staging Load Balance• CPU/DRAM upgrades Big/Little Brother• +1 LpR App Server• Disk upgrades Prod Server• Prod Backup Latency Backup Server/Storage• (1) Streaming Video Server• Software Licenses