Dennis Gannon Cloud Computing Futures extreme Computing Group Microsoft Research
2 Cloud Concepts Data Center Architecture The cloud flavors: IaaS, PaaS, SaaS Our world of client devices plus the cloud Science in the Cloud How to transform research.
3 A model of computation and data storage based on pay as you go access to unlimited remote data center capabilities. A cloud infrastructure provides a framework to manage scalable, reliable, on-demand access to applications. Examples: Search, email, social networks File storage (Live Mesh, Mobile Me, Flicker, ) Just about any large-scale web service is a cloud service.
4 The current driver: how do you Support email for 375 million users? Store and index 6.75 trillion photos? Support 10 billion web search queries/month? And deliver deliver a quality response in 0.15 seconds to millions of simultaneous users? never go down. The future applications of the cloud go well beyond web search The data explosion The merger of the client (phone, laptop, your personal sensors) with the cloud. A major implication for data center architecture
Range in size from edge facilities to megascale. Economies of scale Approximate costs for a small size center (1000 servers) and a larger, 100K server center. Technology Cost in small-sized Data Center Cost in Large Data Center Ratio 6 Network Storage Administration $95 per Mbps/ month $2.20 per GB/ month ~140 servers/ Administrator $13 permbps/ month $0.40 per GB/ month >1000 Servers/ Administrator 7.1 5.7 7.1 Each data center is 11.5 times the size of a football field
7 The impact on the environment In 2006 data centers used 61 Terawatt-hours of power 1.5 to 3% of US electrical energy consumption today Great advances are underway in power reduction With 100K+ servers and apps that must run 24x7 constant failure must be an axiom of hardware and software design. Huge implication for the application design model. How can hardware be designed to degrade gracefully? Two dimensions of parallelism Scaling apps from 1 to 1,000,000 simultaneous users Some apps require massive parallelism to satisfy a single request in less than a second.
Conquering complexity. Building racks of servers & complex cooling systems all separately is not efficient. Package and deploy into bigger units: 8 Generation 4 data center video
Chicago center has 7.5 miles of chiller tubes for conventional racks. The vision for Gen 4. No building. Ambient Air Shift load on hot days. 9
10 Scale Blue Waters = 40K 8-core servers Road Runner = 13K cell + 6K AMD servers MS Chicago Data Center = 50 containers = 100K 8-core servers. Network Architecture Supercomputers: CLOS Fat Tree infiniband Low latency high bandwidth protocols Data Center: IP based Optimized for Internet Access Data Storage Supers: separate data farm GPFS or other parallel file system DCs: use disk on node + memcache Fat tree network Standard Data Center Network
11 Monsoon Work by Albert Greenberg, ParantapLahiri, David A. Maltz, Parveen Patel, SudiptaSengupta. Designed to scale to 100K+ server data centers. Flat server address space instead of dozens of VLANS. Valiant Load Balancing. Allows a mix of apps and dynamic scaling. Strong fault tolerance characteristics.
13 Infrastructure as a Service (IaaS) Provide a data center and a way to host client VMs and data. Platform as a Service (PaaS) Provide a programming environment to build a cloud application The cloud deploys and manages the app for the client Software as a Service (SaaS) Delivery of software from the cloud to the desktop
Infrastructure as a Service Platform as a Service Software as a Service 14
Roles are a mostly stateless process running on a core. Web Roles provide web service access to the app by the users. Web roles generate tasks for worker roles Worker Roles do heavy lifting and manage data in tables/blobs Communication is through queues. The number of role instances should dynamically scale with load. 15
Experiments Simulations Archives Literature Instruments The Challenge: Enable Discovery. Deliver the capability to mine, search and analyze this data in near real time. Enhance our Lives Participate in our own heath care. Augment experience with deeper understanding. Petabytes Doubling every 2 years 16
17 The NSF Ocean Observing Initiative Hundreds of cabled sensors and robots exploring the sea floor Data to be collected, curated, mined
18 Ed Lazowska, Bill Howe, Keith Grachow, Mark Stroermer (University of Washington) Roger Barga, Nelson Araujo, Jared Jackson, Wei Lu (Microsoft Research)
19 Satellite image land use analysis Two MODIS satellites Terra, launched 12/1999 Aqua, launched 05/2002 Near polar orbits Global coverage every one to two days Sensitive in 36 spectral bands ranging in wavelength from 0.4 µm to 14.4 µm
20 Work by 3 Stanford student in a class project, Catherine Van Ingen, and Keith Jackson. Data Integration Problem ~35 different science data products Atmospheric and land products are in different projections Need to re-project one to work with both Different products: Spatial resolution Temporal resolution Must integrate data from different swaths, different days Data volume and processing requirements exceed desktop capacity ç
Statistical tool used to analyze DNA of HIV from large studies of infected patients PhyloD was developed by Microsoft Research and has been highly impactful Small but important group of researchers 100 s of HIV and HepC researchers actively use it 1000 s of research communities rely on results Cover of PLoS Biology November 2008 Typical job: 10 20 CPU hours; Extreme jobs: 1K 2K CPU hours Large number of test runs for a given job (1 10M tests) Highly compressed data per job ( ~100 KB per job) 21
selects DBs and input sequence Azure Blob Storage Genom e DB 1 BLAST DB Configuratio n Genom e DB K Web Role BLAST Execution Worker Role #1 Input Splitter Worker Role. Combiner Worker Role BLAST Execution Worker Role #n Using Azure cloud to host standard sequence data Run BLAST in parallel map reduce style for a large collection input Use Excel-based tool to search databases. Performance: speedup 45x with 50 roles; 94x with 100 roles; with 300 roles computation time is reduced to 4 hours! 22
23 At one time the client was a PC + browser. Now The Phone The laptop/tablet The TV/Surface/Media wall And the future The instrumented room Aware and active surfaces Voice and gesture recognition Knowledge of where we are Knowledge of our health
24 Challenges Going beyond the browser More than one device in a session Hide the cloud Make it work off-line using cached data if appropriate The cloud is an extension of the multi-client app. Adapt To client power, network resource, data center load. Programming models Agent based? Stateless processes + transactions?
A study of virtual worlds with real content Combination of PhotoSynth + telepresence Avatars represented by live video/audio streams Real people in real places. Scalable to 1000s of users in a single scene Architectural challenge An n-body problem with real-time bodies. Server scalability to make an entire city of people interacting regardless of location. Segmented geographically Each client AV is distributed by one server Store For persistent Avatar data Segmented geographically Architecture Overview Avatar Server address (config) Geography server Geography server Audio-Video Server Audio-Video Server Audio-Video Server Audio-Video Server addresses (config) Avatar server Avatar server Primarily Server to Client Primarily Client to Server Heavy traffic both ways client client client client This diagram does not show data interaction details. However, it does indicate the presence of every interaction between the major components shown. Hundreds of avatar servers each handling hundreds of avatars and exchanging data as avatars move 25
The Branscomb Pyramid The Rest of Us Use laptops. Our data collections are not as big as we wished. Our tools are limited. Paradigm shifts for research Google & others proved the power of the cloud with search. email demonstrated the power of global electronic collaboration Supercomputer Users Have own small cluster or servers The Rest of Us. The cloud is designed to support very large numbers of users or communities Data collections are the first step. 26
27