Cloudstack at Spotify

Feb 2013

Cloudstackat Spotify

About SpotifyStreaming music serviceBare metal, babyEngineering offices in Stockholm, Gothenburg, NYCHundreds of engineersLots of servicesHighly managed configuration

Challenges

Let developers be developersBuild awesome tools

Geographically distributed teamsSupport different use cases

Develop, test, integrate with external parties

spvirtenvKVM hypervisors

DNS as database

Warning: Bad idea!

Everything in the client

Access everywhere

No error handling

SpoticloudBuilt on top of cloudstack

Command line tools

API Server

Async task execution

Integration with puppet, DNS

Not highly available

Something we can grow with

ssh key authenticationssh-agent

Challenge/Response over http

Token gives access

LDAP key & group

Grow your storageHigh level of integration with guest os

Creates local storage backed block device

Script that checks for new devices

Logical volume grows

Triggers ext4 resize

Seamless configPuppet class set on createDNS generated on createUser created early

Cloudstack lessonsKiller feature: add hypervisors, provision guests

Moving fast

Lots of features you don’t use

Still an appliance mindset

Feedback could be improved

What we want to focus onImprove the basic use cases

Ever added a hypervisor with wrong pod id?

Setting up a new cluster, what is secondary storage VM doing?

Building, packaging, system administration

Work around maven transitive dependency problems

Make less assumptions about netfilter configuration

Looking aheadLarge scale integration testing

Unified interface for private and public cloudspcloud in production

Storage

Feb 2013

Noa Resarenoa@spotify.com@blippie

Thank you!

Feb 2013

spoti.fi/cloudstack

Yes, we’re hiring