Spotify's journey to GCP
-
Upload
alexey-lapitsky -
Category
Technology
-
view
78 -
download
0
Transcript of Spotify's journey to GCP
![Page 1: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/1.jpg)
Spotify’s journey to GCP
![Page 2: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/2.jpg)
~# whoami
Alexey Lapitsky / @[email protected]
Site Reliability Engineer @SpotifyPM for the service track of the GCP migration
![Page 3: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/3.jpg)
Agenda
● History● Why GCP?● The biggest mistake● Learnings● Questions!
![Page 4: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/4.jpg)
Spotify’s cloud history
2010Manual VM provisioning
2012Cloudstack, reached ~700 instances
2013Amazon EC2
2015Google Cloud Platform
![Page 5: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/5.jpg)
Current status
● 4 data centers, ~10k physical servers● Micro-service architecture, ~1k different services● Mostly commodity hardware (Dell)● Fully automated, self-service server provisioning
Moving everything to GCP
![Page 6: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/6.jpg)
Focus
![Page 7: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/7.jpg)
Why GCP?
![Page 8: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/8.jpg)
Why GCP?
● BigData● Culture● Timing● Partnership
![Page 9: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/9.jpg)
Our worst mistake
![Page 10: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/10.jpg)
Spoticloud
CLIREST
DBCloudstack
AWS
Puppet
DNS
Server
● CLI Tool + REST Server● User authentication with ssh agent: github.com/spotify/crtauth
SSH
Jumphost
![Page 11: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/11.jpg)
Looks awesome!
● No need to distribute AWS accounts● No need to manage ACLs● Extremely easy to use
~# spcloud create --name web --project alexey
![Page 12: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/12.jpg)
… or not really :(
● Testing environment, shamelessly misused for production● No accountability or a proper ownership tracking
○ 60% of instances were wasting money● Access only to the basic cloud primitives
○ Which are already available on-premise
Currently being deprecated.
![Page 13: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/13.jpg)
GCP Migration
![Page 14: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/14.jpg)
Cross-project networking (XPN)
![Page 15: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/15.jpg)
![Page 16: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/16.jpg)
Things we learned
● VPN is tricky● GCP network is great● Keep an eye on quotas ● Live VM migration!● Think about ACL mgmt in advance● BigTable, GCS, BigQuery are awesome
![Page 17: Spotify's journey to GCP](https://reader033.fdocuments.us/reader033/viewer/2022051300/58a69e431a28abbd568b685d/html5/thumbnails/17.jpg)
Questions?