mark interrante openstack design summit
TRANSCRIPT
OpenStack Design Summit: November 2010
Meet Mark Interrante
Finance, News, Sports
[email protected] Twitter: @Interrante Facebook: /Interrante
HP Ecommerce Cloud
Three start ups
Agenda
Cloud Today / Trends
Partnership with the
OpenStack Community
Rackspace Directions
1. Thank you!
2. We are proud to be a part of this community!
4
Cloud Drives Innovation
Corporate Website Test and Development eCommerce Social Media site Marketing / Advertising /
Campaign site SaaS offerings Rich Media Site Collaboration Platform Gaming
6
Why Pursue Open Source?
Not a software company
Standards are major barrier to adoption
Unique position to launch
7
Our Cloud as Test Bed for You
• Support and service is what we sell
• Intend to help customers with:
• Traditional hosting
• Dedicated OpenStack
• Multi-tenant OpenStack
• Federation (with above and on premise)
8
How Does Our Business Model Fit?
* 2008 vs. 2009 Net Revenue
118,000+ Customers in 120 Countries
80% are Cloud Customers
125% Growth in 2009
9
It’s Happening Today
CLOUDSITES CLOUDSERVERS CLOUDFILES
• Seemless cloud deployments where customers want it – dedicated, multitenant, federation
• Common API
• Standardize interfaces to drive modularity
• Scale, scale and more scale
• Interoperability ���between OpenStack ���clouds
10
Where Are We Going?
• Cloud Servers to OpenStack Compute
• Development in progress
• Blueprints of needed features submitted
• Expected in mid-2011
• Our Cloud Files offer IS ���OpenStack Object Storage today
• Commitment to run both ���projects in production going forward
11
Our Plans with OpenStack
• VM specific
• Basic functionality
• Rescue functionality
• Provider functionality
• Snapshot specific
• On demand
• Scheduled
• To object storage
• To local storage
• Tools/Infrastructure – Administrative API – Monitoring
– Logging
12
To Get There, We Need…
13
Example Blueprints
• Configure NIC: allows for the reorder of the network cards in the hypervisor.
• Dedicated Hosts: provides customers ‘private-like’ capabilities inside a public cloud.
• Flavors: packages of VCPU, disk space, and RAM to meet requirements of different workloads.
• Package update change: provides ability to alter the default location for package updates.
• Metrics: make RRD graphs for virtual machine interfaces available.
These have not been submitted yet
14
Rackspace Future Needs
• Complete portfolio: block storage, load balancing
• Web+ scale
• Dedicated Host Machines
• Authentication, Authorization, & Accounting
• Support more Hybrid scenarios
• Federation
• XaaS
• Auto: scaling, deploying, monitoring, configuring
15
Rackspace Future Needs
• Development resources
• Dozens of developers
• Multiple QA / testing
• Operations
• Reference deployment
• Help where we can
16
Summary: Commitment to OpenStack