Running Rancher and Docker on Dev Machines - Rancher Online Meetup - May 2016
•Descargar como PPTX, PDF•
3 recomendaciones•3,959 vistas
Rancher is a powerful platform for running large clusters and deploying complex apps into production. But a growing number of users are starting to run it locally on developer machines as a fully-contained DevOps platform. In our May meetup, we discussed some of the benefits to developers of running Rancher locally. In this meetup we demonstrated: Building a local implementation of Rancher Leveraging CI to run local builds Deploying complex applications locally for testing The benefits of isolating dev environments Our discussion and demonstration was led by Chris Urwin, Rancher's UK DevOps Lead. We were also joined by Mark Matthews, principal at ARKM Enterprise, who discussed how he has implemented Rancher on developer machines at one of the world's largest health care organizations.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (20)
Similar a Running Rancher and Docker on Dev Machines - Rancher Online Meetup - May 2016
Similar a Running Rancher and Docker on Dev Machines - Rancher Online Meetup - May 2016 (20)
Último
Último (20)
Running Rancher and Docker on Dev Machines - Rancher Online Meetup - May 2016
- 1. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Running Docker and Rancher Locally on Dev Machines May 26, 2016 #ranchermeetup
- 2. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Shannon Williams Co-Founder/VP Marketing @smw355 1 Darren Shepherd Co-Founder/Chief Architect @ibuildthecloud Freenode: darren0 #ranchermeetup
- 3. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Chris Urwin DevOps Lead - UK Rancher Labs @containerschris 2 Mark Matthews Principal ARKM Enterprise https://uk.linkedin.com/in/mark- matthews-2965501 #ranchermeetup
- 4. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . First things first… This is a not a ! 3 #ranchermeetup
- 5. © 2015 Rancher Labs, Inc.4 There are rules for a meetup! • We won’t be done on time • Questions are always welcome • There are no bad questions • Demo, then demo some more • Things will break, be patient #ranchermeetup
- 6. © 2015 Rancher Labs, Inc.5 Join the conversation on Twitter #ranchermeetup
- 7. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Agenda • From Dev to DevOps to Dev - Shannon • Running Docker and Rancher Locally on Dev Machines – Chris • Demo: Building a Micro DC - Chris • User Story: Rancher for our Dev Team – Mark • Latest Rancher Update – Darren 6 #ranchermeetup
- 8. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Rancher Labs 7 #ranchermeetup
- 9. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Building a Container Service 8 Container Service Linux Linux Linux Linux Linux Linux
- 10. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . How to deploy a container service 9 Container Service Linux Linux Linux Linux Linux Linux App Catalog Orchestration Scheduling Monitoring Access Control Network Storage Distributed DB Registry Engine Security Helm, … Compose, Kubernetes, Marathon, Swarm, Kubernetes, Mesos, … cAdvisor, Sysdig, Datadog, … LDAP, AD, GitHub, … DockerHub, Quay.io, … Docker, Rkt, … Notary, Vault, … VXLAN, IPSEC, HAProxy, … Ceph, Gluster, Swift, … Etcd, Consul, MongoDB, …
- 11. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Rancher Overview 10 Microservice Catalog AD/LDAP Leverage existing tools: - CI/CD - Code Repository - Monitoring Environment 1 Environment N … Network Services Storage Services Container Orchestration and Scheduling User Mgmt Ops Mgmt Environment 2
- 12. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc .#ranchermeetup Running Docker and Rancher Locally on Dev Machines My other data center is this laptop
- 13. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Problem Statement “I want my developers and testers to be able to build and test quality code independently; using the same toolset as production uses.”
- 14. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Some of the problems…. • Multiple developers all trying to update applications at the same time • Scheduling conflicts • No SSL or proxy server • Data quality/consistency issues • Network contention • Environment consistency
- 15. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . A potential solution • Running Docker in the datacentre…run it locally • Running Rancher in the datacentre…run it locally • On a local hypervisor (or natively) • Have a common data set • Useful for Developers and testers
- 16. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . What does it look like MirrorRancher Server Rancher Agent Jenkins Desktop Virtualisation Layer App Stack Development VM Shared Folders
- 17. © 2015 Rancher Labs, Inc.16 Demo
- 18. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . How can Rancher help? • Gives visibility of application stack • Can be utilised by less technical resources • Consistency • API and GUI • Load Balancing • Catalog
- 19. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Demo App Voting App Redis queue Java Worker Database Results App Voting App Voting App Load Balancer
- 20. © 2015 Rancher Labs, Inc.19 Demo
- 21. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . The flow
- 22. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Benefits of local dev • More representative of production • Distributed build system • Independent development • Moves Developers more to Devopers • Familiarity with tools • Consistency
- 23. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Limitations • Physical • The more memory the better • The fastest disks you can get • Your imagination…
- 24. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc .
- 25. © 2015 Rancher Labs, Inc. Rancher Dev In A Box
- 26. © 2015 Rancher Labs, Inc. Don't Bash it out, Compose it We all start with bash script building and running docker containers We nearly all then use docker-compose instead The iced cake is using Rancher Compose for scaling and interdependent service stack management More composition means more reliable scripting How to take full advantage of this?
- 27. © 2015 Rancher Labs, Inc. Mirror Mirror on the Laptop Reduces network contention Pull in the background today for your build tomorrow A great enabler for fast dev builds Faster dev builds for quicker feedback cycles Low overhead
- 28. © 2015 Rancher Labs, Inc. CI fingers in all the pies Gives a UI for testers - because most teams still have these Can talk to the host file system, dev box, rancher box Make sure you sidekick a data volume, thus direct code refresh from local git Easily switch between projects (stacks off, stacks on, no need to delete) Easy re-deploy from latest code
- 29. © 2015 Rancher Labs, Inc. Rancher++ Managing containers is a pain, rancher solves that, so give it to everyone Rancher lets everyone easily see memory, io, network traffic - early diagnosis More easily test multi-stack systems - don't leave that to PTL or Prod, solve the pain early Especially for less surprises on your [sticky] session handling Internal registry trick "localhost:5000/" Same deployment and management tools as PTL & Prod Low overhead
- 30. © 2015 Rancher Labs, Inc. Thanks! Enquiries to Mark Matthews markmatthews@arkmEnterprises.co.uk Chris Urwin chris@rancher.com Hand drawn images and the ARKM logo (c) ARKM Enterprises 2016.
- 31. © 2015 Rancher Labs, Inc. Latest Rancher Enhancements 30 1.0.1 • Rancher Multi-node Simplification #ranchermeetup 1.1-dev2 • Experimental Mesos support • F5 Load balancer integration • Customizable Docker Machine UI
- 32. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Getting Started Rancher and RancherOS are in GitHub – Get Involved! 31 #ranchermeetup http://github.com/rancher
- 33. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . New eBook: Building a CI/CD Pipeline with Docker & Rancher 32 http://info.rancher.com/cicd-with-docker-ebook
- 34. © 2015 Rancher Labs, Inc.© 2016 Rancher Labs, Inc . Thank you rancher.com #ranchermeetup
Notas del editor
- Delivery manager, devops lead Reliable Repeatable tested consistently minimal compromise
- Representative data is key. Dockerieze all for dev Apps as close as possible i.e. version
- 1- Desktop Machines 2- Virtualisation layer 3- 3 VM’s spinning 1, rancher Server, mirror and a Development VM 4- In the development VM we are going to run a rancher agent container and a Jenkins container 5- We are going to share some data through into the Jenkins server via the shared folders feature 6- We are going to run our app stack in here (this can be anything you like, limited only by resources)
- During Jenkins Build- make run-Jenkins 1m 10 This could be any CI, so longs as it can be run in a container and everyone can build in a consistent way then it doesn’t matter what its doing. As part of this build it could be executing unit tests etc I’ve mapped through the drive but you could just as easily have it git pull into the container, my instance monitors the remote git repo and then builds it from the mapped drive. There are pros and cons to both, I like this as I can make changes and run a manual build without needing to check in all the time. Jenkins git build – 5 mins Running multiple hosts locally causes pain as it means you need a repository or a means to get the built containers between the hosts. Overlay network also doesn’t currently work in boot2docker
- People like pictures Ba’s can demo even if not technical Can be scripted so all the same and easy to set up Catalog, easily give people access to a version of your app locally
- Docker voting app Front end – Python Redis queue Java worker Postrgres DB Restults App Nodejs
- Spin up demo app stack, edit a couple of files, watch Jenkins pick up and rebuild Perform an upgrade to voting app to show rolling upgrade Show roll back – discuss benefits Show upgrade to both voting and result app
- After check in to git, Jenkins and docker build automated Nothing stopping having rancher automated too
- Every laptop becomes a build system Representative data is key. Dockerieze all for dev Apps as close as possible i.e. version