Difference between revisions of "Cloud Computing Testbed Requirements"

Latest revision as of 12:22, January 5, 2012

Earth Science Information Requirements and Computational Characteristics

Data Intensive (Disk I/O, Network I/O)
Computing Intensive (Numerical Models)
Concurrent Intensive (Popular Services)
Cloud Virtual Hosting
Intensity Spikes
Scalability/Reliability (guarantee % of up time)

Vendor Capabilities

Scalability/Reliability (guarantee % of up time)

Maximum or Available Capacity
- Operation
- Spike
- CPU Core
- RAM
- Storage
- Network (In-bound, Out-bound)

Cost Model (how vendor charge the following aspects) and Cost
- Operation
- Spike
- CPU Core
- RAM
- Storage
- Network (In-bound, Out-bound)
- Other Facility (e.g., auto scaling, queue, logs, analyses, etc.)

Available User Interfaces
- Web Interface
- SSH Linux type of interface
- Or community open APIs

Supported Services
- SaaS, PaaS, IaaS, etc.
- Supported OS
- Apache Hadoop
- Persistent object store
- Intercloud

Usability and Manageability

Security and Auditability (FISMA supports)

References supporting other science-based orgs
- Successful Domain Projects
- Deployed science-domain projects using their platform

@@ Line 1: / Line 1: @@
-ESIP Cloud Computing Testbed Requirements Document
-Earth Science Information Requirements and Computational Characteristics
-Data Intensive (Disk I/O, Network I/O)
-Computing Intensive (Numerical Models)
-Concurrent Intensive (Popular Services)
-Intensity Spikes
-Scalability/Reliability (guarantee % of up time)
-Vendor Capabilities
+==Earth Science Information Requirements and Computational Characteristics==
-Scalability/Reliability (guarantee % of up time)
+*Data Intensive (Disk I/O, Network I/O)
+*Computing Intensive (Numerical Models)
+*Concurrent Intensive (Popular Services)
+*Cloud Virtual Hosting
+*Intensity Spikes
+*Scalability/Reliability (guarantee % of up time)
-Maximum or Available Capacity
+==Vendor Capabilities==
-Operation
+*Scalability/Reliability (guarantee % of up time)
-Spike
-CPU Core
-RAM
-Storage
-Network (In-bound, Out-bound)
-Cost Model (how vendor charge the following aspects) and Cost
+*Maximum or Available Capacity
-Operation
+**Operation
-Spike
+**Spike
-CPU Core
+**CPU Core
-RAM
+**RAM
-Storage
+**Storage
-Network (In-bound, Out-bound)
+**Network (In-bound, Out-bound)
-Other Facility (e.g., auto scaling, queue, logs, analyses, etc.)
-Available User Interfaces and Supported services, SaaS, PaaS, IaaS
+*Cost Model (how vendor charge the following aspects) and Cost
-Web Interface
+**Operation
-SSH Linux type of interface
+**Spike
-Or community open APIs
+**CPU Core
+**RAM
+**Storage
+**Network (In-bound, Out-bound)
+**Other Facility (e.g., auto scaling, queue, logs, analyses, etc.)
-Usability and Manageability
+*Available User Interfaces
+**Web Interface
+**SSH Linux type of interface
+**Or community open APIs
-Security and Auditability (FISMA supports)
+*Supported Services
+**SaaS, PaaS, IaaS, etc.
+**Supported OS
+**Apache Hadoop
+**Persistent object store
+**Intercloud
-References supporting other science-based orgs
+*Usability and Manageability
-•	Successful Domain Projects
-•	Deployed science-domain projects using their platform
+*Security and Auditability (FISMA supports)
+*References supporting other science-based orgs
+**Successful Domain Projects
+**Deployed science-domain projects using their platform