Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Dev ops 2016 dockerizing the it


Published on

Deveo CEO Ilmari Kontulainen gave a speech about how Deveo has improved its release time from 90 minutes to 9 minutes and the ability to take into use new IT services within hours, while it earlier took days.

Published in: Software
  • We also wrote a blog post covering what was in the presentation. Read it in our blog:
    Are you sure you want to  Yes  No
    Your message goes here
  • You may watch the full talk in Youtube
    Are you sure you want to  Yes  No
    Your message goes here

Dev ops 2016 dockerizing the it

  1. 1. DOCKERIZING THE IT INFRASTRUCTURE Ilmari Kontulainen @deveoteam
  2. 2. Background
  3. 3. Technical background 10 years in IT industry Creating value Technology Coaching / self improvement Sports Personal background
  4. 4. Repository management Code reviews Access management Documentation Issue tracking All from the same platform with self service approach Features and Benefits
  5. 5. History and context 10 years of history 4 years of development Various technologies Cloud and on-premises Support for 4 different operating systems Three different deployment options
  6. 6. Delivery pipeline
  7. 7. Types of Deployment: Combo, HA, Cluster
  8. 8. Operating systems
  9. 9. Total installation combinations 3 * 6 = 18
  10. 10. Before 90 minute install for Deveo customers Compiling everything to everything with Chef Error prone Debugging sessions Unsatisfied customers Avoiding releases
  11. 11. Omnibus Easily create full-stack installers for your project across a variety of platforms.
  12. 12. Omnibus project scaffolder dependency recipes project configuration virtual machine system the project builder
  13. 13. Omnibus The omnibus project includes a project build caching mechanism that reduces the time it takes to rebuild a project when only a few components need to be rebuilt.
  14. 14. Why not virtual machines? Creating and destroying virtual machines is time consuming and resource-intensive. A clean state is needed for each build Easier to upgrade build tools in images Cleaning up VMs too error prone
  15. 15. How we did the transition Listing operating systems Listing software components Created dependency recipes for missing components Set up KitchenCI builds Added support for separate DB and web app packages Added support for addition operating systems
  16. 16. How does the pipeline work Building the packages Create cloud instances Deploy to test instances Test the installation of packages
  17. 17. Benefits Before: 90 minutes Now: 9 minutes Release times: 10 times faster Shorter installation and upgrade times Less problems during installations and upgrades No longer avoiding releases
  18. 18. Future and learnings SSD speeds docker up quite a lot Dockerize our test environments
  19. 19. Separately managed internal services
  20. 20. Problem “Office server” Typically the largest technical debt for the organisation from IT point of view Loss of such server is critical Adding new services takes time Data safety and backups are often forgotten
  21. 21. Docker for harmonising the IT infrastructure
  22. 22. Benefits Own namespace and storage for each app Linking applications together Building dependencies, e.g. Our CRM needs a DB Docker native volume and networking support Version controlled by Docker compose Convoy for backups and recovery
  23. 23. Convoy Create thin provisioned volumes Take snapshots of volumes Incrementally backup snapshots to object stores, such as Amazon S3 Restore volumes to any hosts Separation of host and storage
  24. 24. Process List components, what data do they store, what dependencies they have for each component: 1. create docker compose file 2. List ports, volumes/mount points 3. Create image that holds application
  25. 25. Results and findings Before: Deploying new IT services took 3 days After: Deployment of new services in 1-3 hours 
 Example: Internal Storage problem Before: Disaster After: Full recovery in hours
  26. 26. Conclusion
  27. 27. Conclusion Faster installations Less problems with installations More satisfied customers No longer avoiding releases Faster deployments of new IT services More fault tolerance and ability to recover from disasters
  28. 28. Q & A
  29. 29. Follow us on twitter @deveoteam