1. How DreamHost builds aPublic Cloud with OpenStackCarl Perry
twitter/github/slideshare:edolnx irc:carlp@freenode
2. Well Hello! Im the Cloud Architect at DreamHost Weve been
around since 1997 Were old enough to drive next year! Spun off
Inktank as a support company for Ceph last year Launched
DreamObjects, a Ceph based S3 alternative, in September This week
we Launched DreamCompute, our Public Cloud 3. To empower
entrepreneursand developers
Why?http://www.ickr.com/photos/toywhirl/8050771631/ 4. Design
Tenants Design for Reliability Maintenance is the norm not the
exception Isolate tenants from each other by default Modular
equipment design Easy to expand Easy to upgrade Automate Everything
5. Considerations Scalability Speed Monitoring Uptime Security Cost
6. Obstacleshttp://www.ickr.com/photos/brewbooks/4206976341/ 7.
Storage Must be shared, local storage prevents maintenance Has to
be cost effective Has to be massively scalable Must run on
commodity hardware Single solution for boot and additional volumes
Fully Automat-able 8. Networking Must support IPv6 Tenants must be
isolated from each other Cannot be limited to a physical location
within a data center 10Gb, lots of 10Gb No single point of failure
(core switches are so 1980) 9. Hypervisor Simpler is better Should
run on Linux Support for architectures that are not x86(_64) a huge
bonus Must not require guest operation system modications 10. 1998
called, they are disappointed We expect to operate this for more
than 6months, so IPv6 is a requirement. There are new and exciting
problem to solve,but its past time Its a great way to piss off
vendors Best Part: Everything is Internet Addressable! 11. Decision
Timehttp://www.ickr.com/photos/inafrenzy/5787848646/ 12. Hypervisor
Scalability: No changes needed for 2-2000 VMs Speed: Fast.
Especially when using virtio drivers Monitoring: Lots of support
for existingsystems, hooks for custom ones Uptime: Kernel module
and userspace app. Easyto patch. Supports live migration Security:
Built into kernel, lots of eyes. Cost: Free 13. Storage
Scalability: Works from gigabytes to exabytes Speed: Easy to
deploy, IOPS limited by hardware Monitoring: Userspace apps, easy
to monitorhealth of hardware. Software monitoring gettingbetter all
the time Uptime: Userspace apps. Designed for highavailability
Security: Provides isolation layers, not directlyaccessible to
tenants Cost: Free* 14. Physical Networking Hardware Scalability:
Pizza boxes, just buy more Speed: Based on Broadcom Trident
platform Monitoring: (software) Uptime: These guys make the
switches for toptier OEMs Security: (software) Cost: Extremely
Affordable (about the cost of aserver) 15. Physical Networking
Software Scalability: Designed for spine & leaf and
fat-treearchitectures. Runs Linux natively. Speed: Limited only by
hardware Monitoring: Its Linux! Uptime: Designed to meet our model
Security: Its Linux! Cost: Extremely Affordable (fraction
ofhardware) 16. Logical Networking Software Scalability: Scales out
with the rest of the cluster Speed: Low overhead Monitoring: SNMP
and SFLOW Uptime: No control plane has no single point offailure.
We designed around HV node beingfailure point. Security: Everyone
is on their own network.Shared NOTHING. Cost: Worth Every Penny 17.
Who needs spanning tree? North Pod West Pod East Pod QSFP+ Spine
QSFP+ Spine SFP+ Leaf SFP+ Leaf10/100/1000 Edge 10/100/1000 Edge
18. Automation Scalability: No Problem Speed: High speed, low drag
Monitoring: Easy Uptime: If the server goes down formaintenance, we
keep running just not changing Security: No open ports! Cost:
Depends 19. Internet & SAN Access Scalability: Scales out with
the rest of the cluster Speed: Blazing Monitoring: SNMP and SFLOW
Uptime: Using multiple switches each in its ownfailure domain to
allow for maintenance/upgrades Security: Proven in the harshest
environments Cost: Best in class 20. Wait...Did you just say SAN?
21. If only you had an Open Source Cloud Infrastructure
Orchestration Platform -Ron Pedde 22. HA Solution Scalability:
Somewhat Limited, but thats OK Speed: Impressive Monitoring:
Complicated Uptime: Trusting the vendors on this one Security: The
enterprise better not be wrong Cost: OUCH 23. Attention CTOs:Avert
your eyes now 24. HARDCORE HARDWARE 25. What Customers See 26. What
Power Users See 27. Questions? not in sessionsWill be at booth to
answer questions when(or leave a card - no SPAM I
promise)http://slideshare.net/edolnx/presentations
