4 Annual Review OOI CI 1015 03 09 ver 1 02

June 22, 2021

Ocean Observatories Initiative

OOI Construction Completion and Transition to Operations Review Arlington VA

OOI Review March 9-10, 2015

Ocean Observatories Initiative

CyberInfrastructure (CI) Build

OOI Review March 9-10, 2015

Review of the Development Process • Concept of Operations (CONOPS) – Describes how system should function at a high level

• Use Cases – Flows from CONOPS, describes how users interact with system

• Requirements Development – Derived from Use Cases and CONOPS; list of “Shalls” that describe the functionality of the system

• Software Development – Implementation of requirements into software

• Software Testing – Verification that the software performs as specified by requirements

• Validation – Validation that the system performs a desired by the user, and provides valid output data products

2

OOI Review March 9-10, 2015

uFrame OOI • uFrame CI focused on: – – – –

Leveraging existing Raytheon uFrame SOA technology Improved User Interface Simplified hardware and network architecture Collocated Data Management organization

• Incremental Build Schedule – Allows for identification and resolution of integration issues – Permits feedback into later builds

• Systems Engineering Management Plan (SEMP) – OOINet Build schedule is linked with new SEMP, which defines commissioning plan, specific deliverables, and is represented in schedule 3

OOI Review March 9-10, 2015

uFrame OOI Architecture

OOI Review March 9-10, 2015

uFrame OOI Architecture Notes • Plug-in Development – The uFrame team is developing or extending plug-ins to meet some of OOI CI capabilities. – Other capabilities will be implemented via hardware or network infrastructure and via graphical user interface development by other OOI CI development teams.

• Database – Postgress database implemented to hold metadata about ingested data files and to hold the information about the physical assets that collect the data.

• Streaming Ingest – Data ingest performed using Cassandra engine. Cassandra provides for better performance than original (PyPies) technology, and includes support for clustering (allowing scalability), and replication. 5

OOI Review March 9-10, 2015

Data Ingestion Processing • Data Streams ingested via Sensor Integration extension • Python parsers used to parse incoming data – L0 Data stored within Cassandra – Meta data stored within Postgress • Profilers & Profilers and Moorings Moorings – Input through Java Messages to Apache Qpid queue

Sensors 1 Sensors 2 Sensors 1:n

Data Stream 1 Data Stream 2 Data Streams 1:n

• Streaming Data – Instrument Agent driver translates data stream into a Qpid queue 6

OOI Review March 9-10, 2015

uFrame Core Cassandra Cassandra Database Cassandra Database Database Cluster Sensor Integration

Streaming Gliders Level 1 Product Parameters Data Streams

Sensors

Postgres (metadata)

Algorithm Processing • Data arriving via streams is converted to usable data products through application of algorithms which apply calibration constants, perform quality control functions, and merge data from co-located sensors to generate data products •

Input Data streams (L0) from Mooring/ Node/ Sensors are transformed to output Product Derived (L1 & L2) via algorithms Algorithms require that calibration information be stored and managed (as calibration data may change over time

Platform: AUV/Glider or Mooring Mooring

location

PFID

Sen 1 CC

Node

Node

Node

Sen 2 CC Sen 3 CC

. . .

Sen Class Sen Class Stream

PFID PFID L0 or L1 PFIDs

PFID Stream

PFID

PD

. . .

PD CC = Calibration Constant PD = Product Derived PFID = Product Function ID – algorithm

7

Algorithm Asset id/location

OOI Review March 9-10, 2015

PD – Density Derived Product

Data Management/Processing • Asset Data can be ingested by bulk upload (for operators) and via Web based GUI • GUI will provide for entering individual data records, including editing and viewing existing records •

8

OOI Review March 9-10, 2015

Asset file copy to Rutgers

Users

Upload Asset Data

Asset Mgmt GUI

REST requests/ response

Spreadsheet XLSX formatted file

uFrame Core Web Services Asset Web Service

Service Bus

Asset data is retrieved from OOINet uFrame via REST services hosted by the Web Services plug-in to Request Asset uFrame. Data The REST request from the Asset Management GUI is handled by the Asset Web Service which translates the REST request to a database query.

OOINet Repository

Asset Management Asset Spreadsheet Parser File scanner

File Endpoint

CyberInfrastructure Deliveries Delivery Group

Driver Delivery to Omaha

Delivery to Integration

CI Validation at Rutgers

1A

2-Sep-14

30-Sep-14

14-Nov-14

1. 2.

uFrame CI – (16 Drivers) L0/1 Data Management

Support Pioneer II/Endurance Profiler Mooring and Coastal Glider Conditional Acceptance

1B

22-Sep-14

20-Oct-14

18-Mar-15

1. 2.

uFrame CI – (7 Drivers) L0/1 Data Management

RSN Risk Reduction

2A

22-Oct-14

12-Nov-14

24-Mar-15

1. 2. 3.

uFrame CI – (21 Drivers) Asset & Data Management User Interface

Support Pioneer Coastal Surface Mooring Conditional Acceptance

2B

26-Nov-14

19-Dec-14

16-Mar-15

1. 2. 3.

uFrame CI – (14 Drivers) Asset & Data Management User Interface

Support Station Papa/Irminger Sea Commissioning

3

23-Dec-14

20-Feb-15

27-Mar-15

1. 2. 3.

uFrame CI – (12 Drivers) Asset & Data Management User Interface

Support RSN/Endurance Cabled Commissioning

4

20-Mar-15

3-Apr-15

1-May-15

1. 2. 3.

uFrame CI – (31 Drivers) Data Management User Interface

Support RSN/Endurance Cabled Commissioning

5

23-Apr-15

1-May-15 (UI) 29-May-15

19-Jun-15

1. 2.

uFrame CI – (31 Drivers) User Interface

CI Ready for All Commissionings

*All dates are plan dates

complete

late

OOI Review March 9-10, 2015

CI Capability Level at Integration

Associated Event / Deployment

expected late

9

Build 1B Composition • Components: – Drivers (OL: Dan Mergens) – 6 Instrument Agent Drivers

– uFrame Capabilities (Omaha: Scott Risch) – L0 & L1 Data Products for the 6 Instrument Agent Drives – L1 Data Products

– Web Services: Proof of Concept

– UI Capabilities (ASA: Dan Maher) – None

– Install/Deployment (Rutgers: Ivan Rodero) – Website – ERDDAP Database OOI Review March 9-10, 2015

10

Build 2A Composition • Components: – Drivers (OL: Dan Mergens)

– 23 Dataset Agent Drivers (each has a “telemetered” and

“recovered” driver) – 3 Instrument Agent Drivers – uFrame Capabilities (Omaha: Scott Risch) – L0, L1, L2 Data Products – Asset Management:

– Record and manage mooring/platform data, expose UI interface

– Web Services: – Test harness UI for plotting/charting, provide UI with access to data in Asset Management

– UI Capabilities (ASA: Dan Maher) – Search & download science data – Graph science time-series data – Landing page (OOI Banner, navigational links)

OOI Review March 9-10, 2015

11

Build 2B Composition • Components: – Drivers (OL: Dan Mergens)

– 14 Dataset Agent Drivers (each has a “telemetered” and

“recovered” driver) – 0 Instrument Agent Drivers – uFrame Capabilities (Omaha: Scott Risch) – All L0, L1, L2 Data Products for all drivers previously delivered – Asset Management: – Extended support for mooring/platform data that have not yet been

deployed

– Web Services: – Expose UI interface for query and data retrieval UI Capabilites (ASA: Dan Maher) – Download support data – Query telemetered data from instruments – Landing page for Pioneer Array – Science UI

OOI Review March 9-10, 2015

12

Build 3 Composition • Components: – Drivers (OL: Dan Mergens) – 6 Dataset Agent Drivers – 4 Instrument Agent Drivers

– uFrame Capabilities (Omaha: Scott Risch) – All L0, L1, L2 Data Products for all drivers previously delivered – Data/Asset Management: – Framework complete, including provenance tracking calibration and QC – Asset Management complete with full lifecycle management – Web Services: – Web framework complete: query/retrieval/application services – Integrate ASA user account management services

– UI Capabilities (ASA: Dan Maher) – Manage User Accounts – Update Metadata – Operator Turnover

OOI Review March 9-10, 2015

– Annotate Data – Trouble Ticket Integration – Health/Status

13

Build 4 Composition • Components: – Drivers (OL: Dan Mergens) – 14 Dataset Agent Drivers – 15 Instrument Agent Drivers

– 6 Platform Agent Drivers – uFrame Capabilities (Omaha: Scott Risch) – All L0, L1, L2 Data Products for all drivers previously delivered – Alerts/Alarms/Notifications – User specified Annotations – UI Capabilities (ASA: Dan Maher) – Initial Command/Control functionality – QA/QC functionality; Alerts & Alarms – Help/Glossary/How-to – Initial Asset Management

OOI Review March 9-10, 2015

14

Build 5 Composition • Components: – Drivers (OL: Dan Mergens) – 29 Dataset Agent Drivers

– Includes telemetered and recovered variants

– 15 Instrument Agent Drivers

– uFrame Capabilities (Omaha: Scott Risch) – Mission Execution – Non-Time Series Plotting – Updates/Fixes

– Bug fixes will be worked by priority – UI Capabilities (ASA: Dan Maher) – Final User Management – CI Status Metrics

OOI Review March 9-10, 2015

15

Earned Value Definitions • CPI = Cost Performance Index – Work Performed/Cost of work Performed, 1.0 = Spending as planned

• SPI = Schedule Performance Index – Work Performed/Work Scheduled, 1.0 = Completing work as planned

• Cur. = Current Period Performance – Status of most current 2 weeks of work

• Cum. = Cumulative Performance – Status of work since beginning of task

• Plot = Historical data – Plot is bi-weekly graph of cumulative Plan Costs/Actual Costs/Performance Costs

OOI Review March 9-10, 2015

16

uFrame CI Plan vs. Actuals

OOI Review March 9-10, 2015

17

Cabled Plug-ins Plan vs. Actuals

OOI Review March 9-10, 2015 –

Uncabled Plug-ins Plan vs. Actuals

OOI Review March 9-10, 2015 –

UI Plan vs. Actuals

OOI Review March 9-10, 2015 –

Status Summary • Driver Development Stages: – IDD, Code/Unit Test, Software Integration Testing

• Summary of Driver Development Progress – Uncabled: 181 Dataset Agent Drivers / 16 remaining – Cabled: 32 Instrument Agent Drivers / 2 remaining

• Driver Integration Stages – uFrame OOI Integration, Verification, Validation

21

OOI Review March 9-10, 2015

Instrument Driver Overall Status

OOI Review March 9-10, 2015

22

Dataset Parser Plug-in Progress

Source: Unified Status Tracking – DAD Status

OOI Review March 9-10, 2015

OOI-CI Testing • Driver Development Unit / Integration Test – –

Verify that drivers function per IDD Performed by Driver Development Teams (Raytheon, OSU, UW)

• Framework Development Unit / Integration Test – –

Verify that software functions as expected in the development environment Performed by Raytheon Omaha team

• Verification / Acceptance Test – – –

Verify that software supports defined use cases and meets documented requirements This is done by running through test cases which are created from use cases Perform by Rutgers Software Test team

• Data Validation Test – –

Verify that data transformation algorithm is correct via output data validation Perform by Rutgers Data Management team

• Science Test – –

Verify that software meets science needs Perform by wider science community

24

OOI Review March 9-10, 2015

Test Artifacts Test Procedures

Test Reports

Test Planning

25

Test Scheduling

OOI Review March 9-10, 2015

Data Management Cabled/Platforms Instruments

Drivers/Parsers

Science/Engineering Data

Parser to data stream association

Asset Management:

Creation of L1, L2 Data Products

Uframe QC on L1, L2 Data Products Alerts/Alarms, Health Status monitoring

26

L0 Data

Data Ingestion

Command and Control

Mission Execution

Data Management

OOI Review March 9-10, 2015

eg. Location, Depth, Calibration Coefficients, startup config, telemetry

Algorithms

QC look up tables Alarm, Alert, Health/Status flags and thresholds

Glider Schedules Profiler Mission Plans

Asset Management Database Schema for storage of all Metadata related to assets and their associated events

27

OOI Review March 9-10, 2015

User Interface Demonstration

• Video of walkthrough of UI screens

28

OOI Review March 9-10, 2015

Ocean Observatories Initiative

CyberInfrastructure (CI) Network and Hardware Architecture

OOI Review March 9-10, 2015

OOI CI – Scope • Different activities at RU (October 2014 – Today) – – – – – – – –

Transition of services to Rutgers OOI infrastructure Network and hardware architecture Software stack Configuration and data lifecycle management Integration and testing infrastructure Data validation/verification and outreach activities Etc.

30

OOI Review March 9-10, 2015

Overall OOI CI Architecture Institutional VPN VPN/NGFW

West‐Coast CI (Pittock)

VPN/NGFW

PNWGP/MAPGI (Internet2/AL2S)

VPN/NGFW

PNWGP Dedicated  circuit

East‐Coast CI (RU)

VPN/NGFW

– Decentralized network architecture with 4 P2P connected sites (OMCWHOI, OMC-OSU, OMCSIO, CI-RU) – Independent administrative domains (e.g., IP spaces) – Supports both VPN and non-VPN configurations

VPN/NGFW Institutional VPN

VPN/NGFW

RSN Pacific City Cabled Instruments

Institutional VPN

Final users  (Portal)

Commercial  Internet

Flexible network architecture

VPN/NGFW VPN/NGFW

OMC‐OSU

OMC‐WHOI

– Short-term: traditional firewall system (iptables) – Long-term: Latest generation firewall appliances to consolidate security layers

VPN/NGFW Institutional VPN

VPN/NGFW

Un‐cabled  Instruments Highly available  latest generation  firewall  appliances

Un‐cabled  Instruments

VPN/NGFW VPN/NGFW

OMC‐SIO

Un‐cabled  Instruments

Remote  dial‐in users

OOI Review March 9-10, 2015

External connections – Leverages institutional VPN infrastructure

Institutional VPN

31

Security

OOI CI Architecture – Functional View Cabled array data, incl.  hydrophones, seismometers,  HD video, [data mirror]

Data  storage Compute  Servers  (mirror)

Data  storage

Wireframes command & control

West Coast CI

Cabled array  data, incl.  hydrophones,  seismometers,  HD video

Cabled array  data

Network  mgnt., load  balancing

Storage Group Tape‐library  storage/backup

Compute servers  (tools, UFrame,  test/backup) East Coast CI (RU)

Wireframes command & control

Wireframes  command &  control

Pacific City Data  acquisition

RSN

Data  Exchange

OMC‐WHOI

Data buffer  and backup

OMC‐OSU Data buffer  and backup OMC‐SIO

Data  acquisition

Data  acquisition

Data buffer  and backup

32

OOI Review March 9-10, 2015

Data  acquisition

CI portal  access point

OOI CI Architecture – Functional View Cabled array data, incl.  hydrophones, seismometers,  HD video, [data mirror]

Data  storage Compute  Servers  (mirror)

Data  storage

Wireframes command & control

West Coast CI

Cabled array  data, incl.  hydrophones,  seismometers,  HD video

Cabled array  data

Network  mgnt., load  balancing

Storage Group Tape‐library  storage/backup

Compute servers  (tools, UFrame,  test/backup) East Coast CI (RU)

Wireframes Estimated datacommand & control rates

Wireframes  command &  control

Pacific City Data  acquisition

RSN

Data  Exchange

OMC‐WHOI

Data buffer  and backup

OMC‐OSU Data buffer  and backup OMC‐SIO

Data  acquisition

Data  acquisition

Data buffer  and backup

33

OOI Review March 9-10, 2015

Data  acquisition

CI portal  access point

Information Lifecycle Management in OOI • Solution integrates two paradigms – Disk-based: Enterprise SAN • Deduplication – reduces data footprint • Redundancy – maintains data integrity • Management – increases administrative leverage

– Tape-based: Robotic Library • Acts as “Last Tier” of SAN hierarchy • Delivers no-power, no-cooling, long-life storage target • Suitable for backup, disaster recovery, data transport

• Data distribution (replication) – East Coast CI (Rutgers): main site/access point – West Coast CI (currently Pittock): mirror, data locality

• Highly available, 24/7-4hrs response support

34

OOI Review March 9-10, 2015

CI Implementation. ILM infrastructure West Coast CI (currently at Pittock)

East Coast CI (RU) Vmware ESXI Hypervisor

Vmware ESXI Hypervisor

PNWGP

Internet2

Latest Generation Latest Generation Network Switch,

Network Switch Firewall Appliances RSN

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

Vmware ESXI Hypervisor Vmware ESXI Hypervisor

Internet

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

Latest Generation Firewall Appliances,

Network Switch

Food Science (RU  Telecommunications hub)

Load Balancer

Vmware ESXI Hypervisor

10G over Internet 2

Vmware ESXI Hypervisor

Internet

VM

Vmware ESXI Hypervisor

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

Vmware ESXI Hypervisor

Vmware ESXI Hypervisor VM

VM

VM

VM

VM

Vmware ESXI Hypervisor

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM Bare‐Metal Server

Vmware ESXI Hypervisor VM

Backup/Testing  server strings  (existing HW)

VM

VM

VM

Wreless Router (Administrative Network)

VM

Latest Generation Network Switch,

Hill Center (RU  Telecommunications hub)

Internet2

VM

VM

VM

Bare‐Metal Server

4G Wireless Router (Administrative Network)

VM

VM

VM

VM

VM

VM

VM

VM

VM

Bare‐Metal Server Bare‐Metal Server Bare‐Metal Server

Backup/Testing  server strings  (existing HW)

UFrame Server (Bare‐Metal)

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

UFrame Server (Bare‐Metal) UFrame Server (Bare‐Metal) UFrame Server (Bare‐Metal)

Bare‐Metal Server

UFrame Server (Bare‐Metal)

Bare‐Metal Server

UFrame Server (Bare‐Metal)

Bare‐Metal Server

UFrame Server (Bare‐Metal)

Bare‐Metal Server Bare‐Metal Server

2 PB SAN

Bare‐Metal Server Bare‐Metal Server

Storage Area Network (SAN)

Up to 10 PB … Tape Library

UFrame Server (Bare‐Metal)

OOI Review March 9-10, 2015

2 PB SAN

UFrame Server (Bare‐Metal)

UFrame Server (Bare‐Metal)

Scalable Tape Library

UFrame Server (Bare‐Metal)

Storage Area Network (SAN)

Direct Fibre Channel Connection

36

UFrame Server (Bare‐Metal) UFrame Server (Bare‐Metal)

Bare‐Metal Server Bare‐Metal Server

Bare‐Metal Server

UFrame Server (Bare‐Metal)

UFrame Server (Bare‐Metal)

Bare‐Metal Server

(e.g., NODC)

Uframe Server (Bare‐Metal) Vmware ESXI Hypervisor

VM

VM

External National Archive

CI Implementation. ILM infrastructure West Coast CI (currently at Pittock)

East Coast CI (RU) Vmware ESXI Hypervisor

Vmware ESXI Hypervisor

PNWGP

Internet2

Latest Generation Latest Generation Network Switch,

Network Switch Firewall Appliances RSN

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

Vmware ESXI Hypervisor Vmware ESXI Hypervisor

Internet

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

Latest Generation Firewall Appliances,

Mirroring

Network Switch

Food Science (RU  Telecommunications hub)

Load Balancer

Vmware ESXI Hypervisor

10G over Internet 2

Vmware ESXI Hypervisor

Internet

VM

Vmware ESXI Hypervisor

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

Vmware ESXI Hypervisor

Vmware ESXI Hypervisor VM

VM

VM

VM

VM

Vmware ESXI Hypervisor

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM Bare‐Metal Server

Vmware ESXI Hypervisor VM

Backup/Testing  server strings  (existing HW)

VM

VM

VM

Wreless Router (Administrative Network)

VM

Latest Generation Network Switch,

Hill Center (RU  Telecommunications hub)

Internet2

VM

VM

VM

Bare‐Metal Server

4G Wireless Router (Administrative Network)

VM

VM

VM

VM

VM

VM

VM

VM

VM

Bare‐Metal Server Bare‐Metal Server Bare‐Metal Server

Backup/Testing  server strings  (existing HW)

UFrame Server (Bare‐Metal)

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

VM

UFrame Server (Bare‐Metal)

UFrame Server (Bare‐Metal) UFrame Server (Bare‐Metal) UFrame Server (Bare‐Metal)

Bare‐Metal Server

UFrame Server (Bare‐Metal)

Bare‐Metal Server

UFrame Server (Bare‐Metal)

Bare‐Metal Server

UFrame Server (Bare‐Metal)

Bare‐Metal Server Bare‐Metal Server

2 PB SAN

Bare‐Metal Server

Bare‐Metal Server

Bare‐Metal Server

Storage Area Network (SAN)

Up to 10 PB … Tape Library

UFrame Server (Bare‐Metal)

2 PB SAN

UFrame Server (Bare‐Metal)

UFrame Server (Bare‐Metal)

UFrame Server (Bare‐Metal)

Last-tier /Backup

Scalable Tape Library

Storage Area Network (SAN)

Direct Fibre Channel Connection

Storage solution (distributed, multi-tiered, resilient) 37

Archive

UFrame Server (Bare‐Metal)

Bare‐Metal Server Bare‐Metal Server

UFrame Server (Bare‐Metal)

UFrame Server (Bare‐Metal)

Bare‐Metal Server

Mirroring

(e.g., NODC)

Uframe Server (Bare‐Metal) Vmware ESXI Hypervisor

VM

VM

External National Archive

OOI Review March 9-10, 2015

uFrame SOA

38

OOI Review March 9-10, 2015

CI Architecture – Data Flow within OOInet Uframe

From Iridium downlink or recovery

Post Recovery

Cassandra

Meta

Glider

Glider

Platform

Separate Data Files

Temp Press. Lat./Lon Etc.

OMC

Cable data Data

Asset Management

data

Meta HDF5, NetCDF

Algorithms

EDEX

Uframe Web Services

MIO File Server qpidd

rsync Local Storage

data

CI File Server

data

39

OOI Review March 9-10, 2015

Local Storage

Meta

GUI data

Instrument data is stored in Cassandra DB. Metadata is stored in a Postgress DB

CI Deployment Plan Phase 1 – Minimal CI hardware (Current status) – Essential compute, storage, networking, software to support construction, testing, commissioning – Leveraging existing capabilities – End-to-end high-bandwidth network connection operational – Ramping up personnel – 5 positions on interviews

Phase 2 – Immediate O&M CI (Target*: 03/31) – Functional compute, software; intermediate storage solution – Expect to hire 3-4 systems/software personnel – Need to address reliability, quality of service

Phase 3 – Commissioning O&M CI (Target*: 05/31) – – – –

Full compute, software; redundant/reliable storage with backup solution; Full datacenter capability; west coast re-deployed and operational OOINet in production Security solution deployed * Contingent on funding 40

OOI Review March 9-10, 2015

Other CI Issues • Long-term data archival – Working with NODC

• Federated CI identity management – Leverage existing XSEDE/NCSA infrastructure

• Security audits – Working with Center for Trustworthy Scientific Cyberinfrastructure (CTSC) – http://trustedci.org

• Monitoring capabilities – Performance, availability and communications pathways

• CI evaluation – Quality of service (exclusive of scheduled downtime) – Network bandwidth utilization (e.g., prioritize non-user facing functionality when bandwidth utilization reaches >85%)

41

OOI Review March 9-10, 2015

Cost (CI Construction) Category

Servers

$297,813

Network $1,140,040

Storage and Backup (ILM)

$1,806,906

Item

Pice

8x Dell R730 servers for Uframe

$118,013

6x Dell R720 servers disk and 10G update

$6,900

Servers for West Coast CI (14x Dell R730)

$172,900

Latest Generation Security appliances: 4 x 10Gbps + 8 x 1Gbps (with 3 years service) – list price

$635,040

Latest Generation Security Appliance Management Console – (1 instance to manage 12 appliances) Latest generation switches for East/West Coast (based on list price)

$430,000

Load balancer/firewall, with 3 years service

$43,550

2 x Management network

$12,850

Rutgers Compellent support refresh (3 years)

$24,538

Pittock Compellent support refresh (3 years)

$39,334

2 Dell Compellent (160TB) upgrades – Rutgers and Pittock

$424,798

2x Dell Compellent expansion (333TB) – East Coast

$199,971

Backup media servers x 5 – Dell R720 (special configuration)

$60,000

Netvault DR6000 disk backup appliance x 4

$280,000

Quantum StorNext AEL6000 LTO-6 tape library, 1 PB frame

$502,640

LTO-6 media (tape) pack – 400 tapes + 2 cleaning tapes

$74,124

NetVault backup software

Infrastructure $213,300

$108,500

Quantum StorNext software

$93,000

Raritan 60A input, 6 x L6-30R output x 3 (for reusing existing UCSD PDUs)

$11,100

Liebert DS/3 22-ton precision cooling unit

$75,000

Liebert DS/3 installation cost

$35,000

UPS

$80,000

Network reconditioning

$12,200 Total CI construction cost

42

$18,600

OOI Review March 9-10, 2015

$3,458,059

Risks • • • •

Timelines Production readiness Beyond functionality Community acceptance

43

OOI Review March 9-10, 2015

Operation – Systems Team

44

OOI Review March 9-10, 2015

Source