Leanpub Header

Skip to main content

The Copenhagen Initiative

How we migrated the 6play VOD platform to The Cloud, on AWS & Kubernetes.

We have migrated our 6play VOD platform to The Cloud! We now run on Kubernetes and AWS managed services! Read our feedback, discover the challenges we faced and the solutions we retained.

Free With Membership
This book is a translation into English of Le Plan Copenhague which was originally written in French

With Membership

Free!

$24.99

You pay

$24.99

Author earns

$19.99

Packages

Details
$

...Or Buy With Credits!

You can get credits monthly with a Reader Membership
PDF
EPUB
WEB
330
Pages
About

About

About the Book

6play, the replay and VOD platform of M6 and other RTL Group channels, is hosted in The Cloud! Or rather, depending on when you read this, part of our platform is hosted in The Cloud.

Before 2018, our platform was hosted in a Parisian data center. There, we rented a room, racks, servers, network connections. When a disk broke or to add RAM to a server, a technician would drive to the data center...

In 2018, we started our migration to The Cloud: we switched most of our hosting to AWS. We now use managed services when we can and our applications are often deployed under Kubernetes.

This book tells the story of this migration: how did we transform our hosting? What impact did it have on our projects? How did we organize ourselves? What choices did we make throughout the process? What did we learn, what did we make evolve? And maybe even, one or two years later: what would we do differently if we had to do it all over again?

More than "this is our platform, it's perfect", we will focus on "why" and "how".

The first chapters have already been translated from French to English, you will get them right away when buying the book:

  • Introduction: why this book?
  • Our platform, our project: an overview of our platform and applications, our technical background and our migration project.
  • Discovering the Cloud and Kubernetes: why are we migrating to The Cloud and which provider are we choosing? How do we work with containers and what issues will an orchestrator solve? What was our first migration plan?
  • The Copenhagen Initiative: our YOLO idea to quickly gain experience on an application deployed in production.
  • Our AWS setup: accounts, regions and rights management. Infrastructure as Code with Terraform.
  • Our Kubernetes setup: how do we manage our clusters, with kops, and what additional components do we install to make them fully functional?
  • A first migration: we are finally migrating our first application, with a minimalist deployment chain and a safe approach.

The following chapters have been written, in French, and will be translated soon:

  • The beginning of the problems: with an application in production, we finally encounter a first set of problems and we will present the solutions we have developed.
  • A stabilization phase: what improvements have we made to our hosting, how do we manage monitoring, alerting and logging? In short, how have we evolved towards truly prod-ready hosting?
  • Cloud Native Cloud: what impact does The Cloud (Kubernetes, managed services...) have on our projects and our teams?
  • Migrating other applications: what choices have we made to migrate other more complex applications? What problems did we encounter and how did we solve them?

The last chapters have not been written yet (not even in French). They will be published when I'm done with them, which may be in many months:

  • A second stabilization phase: with almost all our applications deployed in The Cloud, we encountered another set of problems. And we made a lot of improvements to our new hosting!
  • CI, CDs and previews: how does continuous integration work for containers? How do we deploy our applications painlessly?
  • Consumption/cost tracking: the ability to launch any type of instance or service is very nice when we code... But after a while, let's look at the cost of our hosting and the optimizations we have put in place.
  • The development environment: we quickly saw that this point was not going to be simple, because we use managed services and deploy containers to Kubernetes...

The published version of the book will of course be updated, free of charge, when these chapters are added or in case of corrections.

This book is a translation into English of Le Plan Copenhague which was originally written in French

Packages

Pick Your Package

All packages include the ebook in the following formats: PDF, EPUB, and Web

The Book

Minimum price

Suggested price$24.99

Free!

    Team package (6 books)

    Minimum price

    Suggested price$80.00

    Get six copies of "The Copenhagen Initiative": one for each person on your team.

    $50.00

      This book is also available in the following packages:

      • Enterprise package (50 books)

        Get fifty copies of "The Copenhagen Initiative": one for each person at your company.

        Minimum price
        $300.00
        Suggested price
        $500.00

      Author

      About the Author

      Pascal MARTIN

      DevOps, développeur Web et PHP et conférencier, je publie des articles en rapport avec le développement Web, et principalement PHP, sur mon blog.

      Vous pouvez me suivre sur @pascal_martin.

      Contents

      Table of Contents

      1.Introduction

      1. 1.1Contents of this book
      2. 1.2Why?
      3. 1.3Our experience feedback
      4. 1.4Transparency and Confidentiality
      5. 1.5Writing Conventions
      6. 1.6About the author

      2.Our platform, our project

      1. 2.1Our applications
      2. 2.26play: frontend, back and videos
      3. 2.3An aging infrastructure
      4. 2.4The future is coming
      5. 2.5The DevOps team
      6. 2.6A public cloud, Kubernetes
      7. 2.7It was a bit fuzzy!
      8. 2.8In summary

      3.Discovering The Cloud and Kubernetes

      1. 3.1Why “The Cloud”?
      2. 3.2GCP, AWS, …
      3. 3.3Kubernetes
      4. 3.4Kubernetes on GCP and AWS?
      5. 3.5At what cost?
      6. 3.6First Migration Plan
      7. 3.7In summary

      4.The Copenhagen Initiative

      1. 4.1Achieving perfection?
      2. 4.2KubeCon 2018
      3. 4.3YOLO!
      4. 4.4Back down to Earth

      5.Our AWS setup

      1. 5.1Introduction
      2. 5.2Regions, zones, HA
      3. 5.3Separate AWS accounts
      4. 5.4Identification and AssumeRole
      5. 5.5The principle: SSO, identification and roles
      6. 5.6IaaS and IaC
      7. 5.7The network
      8. 5.8In summary

      6.Our Kubernetes setup

      1. 6.1Introduction
      2. 6.2EKS
      3. 6.3kops
      4. 6.4A first cluster
      5. 6.5Additional components
      6. 6.6Auto-scaling of pods
      7. 6.7System Metrics
      8. 6.8In summary

      7.A first migration

      1. 7.1Introduction
      2. 7.2The plan
      3. 7.3A simple application
      4. 7.4The poor’s man CI/CD
      5. 7.5Securing the switchover with haproxy
      6. 7.6Finish the switchover?
      7. 7.7In summary

      8.The beginning of the problems

      1. 8.1Introduction: in production, but…
      2. 8.2Our starting tools
      3. 8.3Logging, monitoring and alerting
      4. 8.4Some problems: real cases!
      5. 8.5Nodes that restart whenever
      6. 8.6A lack of audit
      7. 8.7Some “concerns”
      8. 8.8Working in / with The Cloud
      9. 8.9In summary

      9.A first phase of stabilization

      1. 9.1Introduction
      2. 9.2The AWS setup
      3. 9.3Tags for AWS resources
      4. 9.4Cluster Kubernetes (kops)
      5. 9.5Applications and their infrastructure
      6. 9.6Monitoring, alerting
      7. 9.7The documentation
      8. 9.8In summary

      10.Cloud Native projects

      1. 10.1Introduction
      2. 10.2Cloud Native?
      3. 10.3How is it really going?
      4. 10.4The .cloud directory
      5. 10.5Some examples
      6. 10.6What impacts?
      7. 10.7In summary

      11.Let’s migrate all our applications!

      1. 11.1Introduction
      2. 11.2Migrating applications?
      3. 11.3An API to know the time
      4. 11.4Image storage and thumbnail generation
      5. 11.5The Events Collector
      6. 11.6Our Catalog API
      7. 11.7User Preferences
      8. 11.8The Web Front
      9. 11.9Backoffices
      10. 11.10It’s a lot of work!
      11. 11.11In summary

      12.TODO - A second phase of stabilization

      13.TODO - CI, CD and previews

      14.Tracking consumption and costs

      1. 14.1Introduction
      2. 14.2Costs, in our context
      3. 14.3Some theory and first steps
      4. 14.4Improvements we made
      5. 14.5Any other ideas for the future?
      6. 14.6In summary

      15.The development environment

      1. 15.1Introduction
      2. 15.2What were we starting with
      3. 15.3During our migration…
      4. 15.4And then
      5. 15.5In summary

      Appendices

      1. Acknowledgements
      2. Help me!
      3. Timeline
      4. Some interesting reading
      5. Changelog

      Get the free sample chapters

      Click the buttons to get the free sample in PDF or EPUB, or read the sample online here

      The Leanpub 60 Day 100% Happiness Guarantee

      Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

      Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.

      You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!

      So, there's no reason not to click the Add to Cart button, is there?

      See full terms...

      Earn $8 on a $10 Purchase, and $16 on a $20 Purchase

      We pay 80% royalties on purchases of $7.99 or more, and 80% royalties minus a 50 cent flat fee on purchases between $0.99 and $7.98. You earn $8 on a $10 sale, and $16 on a $20 sale. So, if we sell 5000 non-refunded copies of your book for $20, you'll earn $80,000.

      (Yes, some authors have already earned much more than that on Leanpub.)

      In fact, authors have earned over $14 million writing, publishing and selling on Leanpub.

      Learn more about writing on Leanpub

      Free Updates. DRM Free.

      If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

      Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.

      Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

      Learn more about Leanpub's ebook formats and where to read them

      Write and Publish on Leanpub

      You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses!

      Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks.

      Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. (Or, if you are producing your ebook your own way, you can even upload your own PDF and/or EPUB files and then publish with one click!) It really is that easy.

      Learn more about writing on Leanpub