Difference between revisions of "Cloud Computing Testbed Requirements"
From Earth Science Information Partners (ESIP)
| (8 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | ==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 | ||
| − | **References supporting other science-based orgs | + | *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 | ||
Latest revision as of 13: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
