System Hardware Draft 08092000 What hardware will we

Proposed Hardware FY’ 2000 Development Environment Production Environment Web Requests App Server Little Brother

Proposed Hardware FY’ 2001 App Server switch App Server Little Brother N-Class Staging Server

Rationalization (1) • Need distinct development and production environments – Must develop & improve

Rationalization (2) • Need mirrored metadata (to avoid reconstructing a DB) • Do NOT

What to Buy FY 2000 • (1) Local Director IP Switch • (1) N-Class,

What to Buy FY 2001 • +1 Local Director IP Switch • CPU/DRAM upgrades

Slides: 7

Download presentation

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 Hardware FY’ 2000 Development Environment Production Environment Web Requests App Server Little Brother N-Class Staging Server WS / App Server WS WS Trail. Blazer N-Class Dev Server App Server Big Brother N-Class Production Server RAID WS / App Server switch - Mirrored Metadata - Unmirrored Data Silo on each of two partitions: - staging & regression - production Little Brother upgradable to carry production load if necessary, while upgrades and/or maintenance occurs on Big Brother Backup Server Tape Backup System Legend: New FY 2000 Existing

Proposed Hardware FY’ 2001 App Server switch App Server Little Brother N-Class Staging Server Big Brother N-Class Production Server xtra CPU / DRAM WS / App Server WS WS Video Server Little Brother upgradable to carry production load if necessary, while upgrades and/or maintenance occurs on Big Brother Backup Server Trail. Blazer N-Class Dev Server Development Environment Production Environment Web Requests RAID Prod Capacity Tape Backup System Prod Capacity Legend: New FY 2001 Existing

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 Buy FY 2000 • (1) Local Director IP Switch • (1) N-Class, 2 way, 4 GB RAM, 200 GB RAID • (1) N-Class, 2 way, 4 GB RAM • (3) Lp. R, 2 way, 1 GB RAM • (1) N-Class, 2 way, 4 GB RAM • (1) A-Class , ? ? 1 way, 1 GB RAM ? ? • (1) Tape System prod load balance Big Brother Little Brother App Servers Dev Server Backup Storage

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