29.12.2014 Views

Magellan Final Report - Office of Science - U.S. Department of Energy

Magellan Final Report - Office of Science - U.S. Department of Energy

Magellan Final Report - Office of Science - U.S. Department of Energy

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 2<br />

Background<br />

The term “cloud computing” covers a range <strong>of</strong> delivery and service models. The common characteristic<br />

<strong>of</strong> these service models is an emphasis on pay-as-you-go and elasticity, the ability to quickly expand and<br />

collapse the utilized service as demand requires. Thus new approaches to distributed computing and data<br />

analysis have also emerged in conjunction with the growth <strong>of</strong> cloud computing. These include models like<br />

MapReduce and scalable key-value stores like Big Table [11].<br />

Cloud computing technologies and service models are attractive to scientific computing users due to the<br />

ability to get on-demand access to resources to replace or supplement existing systems, as well as the ability<br />

to control the s<strong>of</strong>tware environment. Scientific computing users and resource providers servicing these users<br />

are considering the impact <strong>of</strong> these new models and technologies. In this section, we briefly describe the<br />

cloud service models and technologies to provide some foundation for the discussion.<br />

2.1 Service Models<br />

Cloud <strong>of</strong>ferings are typically categorized as Infrastructure as a Service (IaaS), Platform as a Service (PaaS),<br />

and S<strong>of</strong>tware as a Service (SaaS). Each <strong>of</strong> these models can play a role in scientific computing.<br />

The distinction between the service models is based on the layer at which the service is abstracted to the<br />

end user (e.g., hardware, system s<strong>of</strong>tware, etc.). The end user then has complete control over the s<strong>of</strong>tware<br />

stack above the abstracted level. Thus, in IaaS, a virtual machine or hardware is provided to the end user<br />

and the user then controls the operating system and the entire s<strong>of</strong>tware stack. We describe each <strong>of</strong> these<br />

service models and visit existing examples in the commercial cloud space to understand their characteristics.<br />

2.1.1 Infrastructure as a Service<br />

In the Infrastructure as a Service provisioning model, an organization outsources equipment including storage,<br />

hardware, servers, and networking components. The service provider owns the equipment and is responsible<br />

for housing, running, and maintaining it. In the commercial space, the client typically pays on a per-use<br />

basis for use <strong>of</strong> the equipment.<br />

Amazon Web Services is the most widely used IaaS cloud computing platform today. Amazon provides<br />

a number <strong>of</strong> different levels <strong>of</strong> computational power for different pricing. The primary methods for data<br />

storage in Amazon EC2 are S3 and Elastic Block Storage (EBS). S3 is a highly scalable key-based storage<br />

system that transparently handles fault tolerance and data integrity. EBS provides a virtual storage device<br />

that can be associated with an elastic computing instance. S3 charges for space used per month, the volume<br />

<strong>of</strong> data transferred, and the number <strong>of</strong> metadata operations (in allotments <strong>of</strong> 1000). EBS charges for data<br />

stored per month. For both S3 and EBS, there is no charge for data transferred to and from EC2 within a<br />

domain (e.g., the U.S. or Europe).<br />

5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!