Successfully reported this slideshow.
Your SlideShare is downloading. ×

From Zero Docker to Hackathon Winner - Marcos Lilljedahl and Jimena Tapia

From Zero Docker to Hackathon Winner - Marcos Lilljedahl and Jimena Tapia

Download to read offline

This is my story about how I got involved in the Docker hackathon (and won) without knowing Docker at all. I'll share what technological limitations I had before using Docker and how I managed to solve them, and also some tips to getting started. As a closing, I'll talk about the Whaleprint project and some key features that we would love to see in docker today.

This is my story about how I got involved in the Docker hackathon (and won) without knowing Docker at all. I'll share what technological limitations I had before using Docker and how I managed to solve them, and also some tips to getting started. As a closing, I'll talk about the Whaleprint project and some key features that we would love to see in docker today.

Advertisement
Advertisement

More Related Content

Advertisement

From Zero Docker to Hackathon Winner - Marcos Lilljedahl and Jimena Tapia

  1. 1. Marcos Nils @marcosnils Jimena Tapia @tapiajimena
  2. 2. From Zero Docker to Hackathon Winner
  3. 3. As many young projects do, I faced these most common problems: • Consistent development environments. • On boarding team members. • Shipping code from development to production. Before Docker and I met
  4. 4. • Docker Documentation - [ https://docs.docker.com/ ] • Docker Training - [ https://training.docker.com/ ] • PWD: Interactive tutorials - [ http://training.play-with-docker.com/ ] Leveling up my zero Docker There is a lot of information on the web, but do not panic! Just start with the official documentation and grow from there. Watch out for third-party content as it might contain outdated or hacky workarounds for things that are clearly explained in the official docs.
  5. 5. Willing to participate in Docker hackathon but no project to do so. Aha moment! Messing around with Docker Training examples about Docker Swarm. Me Jonathan & Marcos
  6. 6. Allow users to manage DAB files as service blueprints, in order to understand what will happen with incoming changes. The idea
  7. 7. OMG… here I go!
  8. 8. Hacking process • Usability / UX. • Testing. • Docker source code. • Coding. We distributed tasks among the team:
  9. 9. Whaleprint Sketch
  10. 10. Other features • Export current Swarm configuration. • Output service’s public ports. • Destroy swarm services as needed. • Manage multiple stacks at once.
  11. 11. ~ docker-compose_memcached .TaskTemplate.ContainerSpec.Image: "memcached:3.1" => "memcached" .Mode.Replicated.Replicas: "1" => "2" + docker-compose_nginx .Annotations.Name: "docker-compose_nginx" .TaskTemplate.ContainerSpec.Image: "nginx:1.11.6-alpine" .Mode.Replicated.Replicas: "1" .EndpointSpec.Mode: "vip" We’ve got our MVP !
  12. 12. And so results arrived YOU WON !
  13. 13. - Focus on MVP. - Take into account who the users of your product will be. - Keep it understandable, easily configurable, self-explained and well documented. - Docker source code does not bite! - Keep calm and have fun while hacking! Hackathon - Lessons learned
  14. 14. Short Demo
  15. 15. Thank You! https://github.com/mantika/whaleprint @docker #dockercon @xetorthio @tapiajimena @marcosnils

×