Walking Through Cloud Serving at Yahoo!

Yahoo Cloud Serving
Surendra Reddy
Cloud Computing Conference & ExpoNovember 3, 2009

Imagining the Future of Cloud!

Cloud is a Promise, But …

Reference:
Tussle in Cyberspace: Deﬁning Tomorrow’s Internet
http://conferences.sigcomm.org/sigcomm/2002/papers/tussle.pdf

Customer Tussles:
Outages: 76% outages caused by change management
Unmet Needs: Rapidly changing needs

Management Tussles:
Growing Costs and Complexity
Long Deployment Cycles: Inflexible, peak-provisioned infrastructure

Operations Tussles:
Entangled in many day-to-day failures & troubleshooting
Crippled Infrastructure
Building on weak foundation

Developers Tussles:
Bloated Operating System, App Stacks
Staggering Complexities of Dependencies
No time for QA – Bugs Creeping in all over

Security Tussles:
Whose problem is it?
Auditability and Assurance
Governance
Compliance

As a Result:
More Friction, Waste, and Frustration
Less Innovation

So, What is Cloud?
C – Customer Driven
L – Lean
O – Optimized
U – Utility
D – Demand-Driven

Cloudis NOT about Cost cutting
It is about Value Creation enabling Innovation

Cloud is an opportunity to clean up the Infrastructure mess!

Yahoo! is Perfect for Cloud Computing
600M
UNIQUE USERS / MONTH
300M+
YAHOO! MAIL USERS / MONTH
HUNDREDS
OF PROPERTIES / PRODUCTS
BILLIONS
OF OBJECTS STORED
HUNDREDS
OF PETABYTES OF STORAGE
PETABYTES
OF TRAFFIC DAILY

Declarative language for specifying the full, end-to-end structure of a service
Includes multiple environments: Dev, QA, Staging, and production
Extreme Automation

Yahoo! Cloud Serving - Principles
Metastructure: Abstracts concerns of the underlying infrastructure and the network communication
Declarative application structure
Continuous Integration, Continuous Deployment, & Continuous Compliance*
End-to-End Security
* Rich Miller @RHM2K first coined “Continuous Compliance”

Virtualized hardware
Standardized software stacks and packaging
Integrated service management
Containers vs. Machines

Elastic serving of changing workloads
Controlled/Intelligent traffic direction
Controlled execution environment
Managed Communication
Service Associations, Bindings, and Access Controls

Yahoo! Cloud: Tiers without Tears
Entrypoint
Naming
Presentation
Tier
Application Logic
Tier
Bindings
Connections
Database Tier

Yahoo! Cloud: Tiers without Tears
Entrypoint
Naming
Load
Balancer
Presentation
Tier
Application Logic
Tier
node
node
node
Bindings
Connections
Database Tier

Yahoo! Cloud: Extreme Automation
Abstracting Services
Component AnswersCore {
Entry root;
Tier pres {
app = “answers_web_tier”;
Exit applogic;
nsize = small;
nnodes = 3;
};
Tier applogic {
app = “answers_al_tier”;
Exit data;
nsize = medium;
nnodes = 3;
};
Tier data;
Connections {
root -> pres;
pres.applogic -> applogic;
applogic.data -> data;
}
}
Presentation
Tier
Application Logic
Tier
Database Tier

QA Environment
Environment qa(ne1) {
TrafficDirector root {
name = “qa.answers.yahoo.com”;
access = testing;
};
AnswersCore core;
Connections {
root -> core;
}
}
Presentation
Tier
Presentation
Tier
Application Logic
Tier
Application Logic
Tier
Testing Testing
Environment production(ac4,sk1) {
TeeTrafficDirector root {
name = “answers.yahoo.com”;
access = public;
split_percent = 10;
split_destination = qa.root;
};
AnswersCore core;
Connections {
root -> core;
}
}
Database Tier
Database Tier

Apps written against rich stacks
Includes core infra and platforms
Infrastructure: Security, monitoring, metering, abuse prevention
Platforms: data, user info, ad systems, configuration bundles
All “auto configured”

Serving Cloud Serving for Y!’s Cloud

Infrastructure to Metastructure
Machines to Containers
Friction to Innovation
Tears to Tiers
Complexity to Simplexity
Costs to Revenue Streams

Cloud is a Promise, Service is the fulfillment!

OPEN CLOUD ACCESS PROTOCOL

OPEN CLOUD ACCESS PROTOCOL
Definition, Deployment, and Life Cycle Management of Cloud Resources
Allocation, Provisioning, and Metering of Cloud Resources
Metadata/Registry for Cloud Resources
Virtual Infrastructure Management

Yahoo! Submitted OpenCAP to IETF
Why IETF?
Specification behind Yahoo Implementation
Plan to open source implementation

Open Cloud Access Protocol
Resource Model
All Infrastructure and Functional Components are modeled as Resources
Nodes, Networks, Storage Devices, Databases, Load Balancers, Identities, Key Value Store, Object Stores, Caching Services
Resource Properties
Modeled as JSON objects
Standard Catalog of attributes, extensible
Resource Operations
Operation, Control, and Notification

Management Operation Services
CREATE - Create an instance of a managed resource
DELETE - Delete an instance of a managed resource
GET - Request managed resource properties (for one resource or a set of resource)
CANCEL - Cancel an outstanding request
SET - Set managed resource properties
ACTION - Request an action to be performed on a managed resource

Management Notification Services
EVENT- Send events occurring on managed resources (VM events, VM stats etc, SNMP events etc)
ALERT- Send alerts for resource failures and exceptions
Life Cycle Management Services
START- Starts the resource
TERMINATE – Stop the resource
SUSPEND – Suspend the resource
RESUME – Resume the resource
ARCHIVE – Archive the resource

Yahoo! Open Source & Research
Open Source
Cloud Serving Platform, Yahoo Implementation of OpenCAP
Traffic Server
Research Activities
Open Cloud Consortium
OpenCirrus & M45

THANK YOU
Surendra Reddy
@sureddy twitter
sureddy@yahoo-inc.com email
yCloudBlog.com blog

TUESDAY, 11/3
4:50pm – 5:35 pm
Hadoop @ Yahoo! – Internet
Scale Data Processing
Eric Baldeschwieler
VP, Hadoop Software Development
WEDNESDAY, 11/4
9:10 am - 9:55 am
Yahoo! Scalable Storage and
Delivery Services
Chuck Neerdaels
VP, Storage and Edge Services
VISIT BOOTH #103
TO TALK WITH YAHOO! ENGINEERS AND LEARN MORE ABOUT YAHOO!’S VISION FOR CLOUD COMPUTING.

Walking Through Cloud Serving at Yahoo!

by Yahoo! Developer Network

Accessibility

Categories

Upload Details

Usage Rights

2 Embeds 26

Statistics