Intranet Spawner Application using Docker, Ansible and the DigitalOcean API

The presentations gives a brief overview on how we implemented a spawner application that let's one of our customers "Joe" spawn instances of his Intranet application for his customers in an easy way.

Every deployment does a rollout of the Intranet application to a domain that is provided inside the spawner application.

Transcript

1. 1@bryantebeek Intranet Spawner Application
2. 1@bryantebeek The Backstory "Spawn an instance of the Intranet application with minimal effort" - Joe
3. 1@bryantebeek The Backstory The Intranet Application
4. 1@bryantebeek The Backstory The Intranet Application Build-in chat Timeline of updates Groups Events Articles Colleagues
5. 1@bryantebeek The Backstory The Intranet Application Mobile app Android / iOS Focus around chat Notifications, etc.
6. 1@bryantebeek The Backstory The Stack Meteor + Docker
7. 1@bryantebeek The Backstory The Stack DigitalOcean Meteor + Docker → Ansible →
8. 1@bryantebeek The Challenge Build an application that lets Joe spawn an instance of his intranet application with minimal effort
9. 1@bryantebeek The Challenge So what now? • We need to build an application for Joe to manage his instances • Every instance spawned will need • a url <domain>.intranet.io • a place to run • custom environment variables "I can do all of this for you, and more..." - mr. Kubernetes
10. 1@bryantebeek The Solution We stick to the existing solution and make an abstraction on top of it
11. 1@bryantebeek The Solution The Spawner Application
12. 1@bryantebeek The Solution The Spawner Application Build with Laravel
13. 1@bryantebeek The Solution The Spawner Application • Provisioning was originally done with Ansible • Integrating this in Laravel feels like reinventing the wheel
14. 1@bryantebeek The Solution We need something to run Ansible for us
15. 1@bryantebeek The Solution So I thought ... ... let's call one of our old friends
16. 1@bryantebeek The Implementation Putting everything together
17. 1@bryantebeek Spawning an instance
18. 1@bryantebeek Spawning an instance Contact details Application details e.g. slug, domain What happens now?
19. 1@bryantebeek Spawning an instance Request a droplet using the DigitalOcean API +
20. 1@bryantebeek Spawning an instance 1. Request a droplet Poll DigitalOcean API to see if droplet is ready +
21. 1@bryantebeek Spawning an instance + + Start droplet provisioning job in Jenkins Also create a DNS record for the application 1. Request a droplet 2. Poll; is droplet ready?
22. 1@bryantebeek Spawning an instance Poll the instance on the provided domain to see if it's ready 1. Request a droplet 2. Poll; is droplet ready? 3. Provision droplet + DNS
23. 1@bryantebeek Spawning an instance Email Joe that the application instance is ready 1. Request a droplet 2. Poll; is droplet ready? 3. Provision droplet + DNS 4. Poll; is application ready?
24. 1@bryantebeek "Bryan, I messed up the url, can I destroy this instance easily?" - Joe
25. 1@bryantebeek Destroying an instance Queue a snapshot of the droplet using the DigitalOcean API +
26. 1@bryantebeek 1. Queue snapshot Remove the DNS record, again using the DigitalOcean API + Destroying an instance
27. 1@bryantebeek 1. Queue snapshot 2. Remove DNS record Destroy the droplet using the in DigitalOcean API + Destroying an instance
28. 1@bryantebeek "One last thing.. what about backups?" - Joe
29. 1@bryantebeek A backup / restore can be started on demand + Backup / restoring an instance
30. 1@bryantebeek A backup / restore can be started on demand + Backup / restoring an instance
31. 1@bryantebeek Thank you