Supporting development with Rancher Server
Download as PPTX, PDF0 likes301 views
This document discusses using Rancher Server to support software development. It provides an overview of Rancher Server features like high availability, access controls, rolling updates, and native services. It also includes assembly instructions for running Rancher Server with Docker and tips on externalizing the database early. Several demos are described to showcase using the Rancher catalog and backing services like setting up Jenkins on EFS and spinning up a Kubernetes environment.
Supporting development with Rancher Server
- 1. Supporting development with Rancher Server Tom Bamford 24 Jan, 2017
- 2. Hello! Tom Bamford ???? @rocketeer125 Site Reliability Engineer Platforms Engineer DevOps Engineer Software Engineer Release Engineer Developer Advocate Distributed Systems Engineer Infrastructure Engineer Cloud Engineer Development Architect Systems Administrator Middleware Engineer Solutions Architect
- 3. Container adoption in software development Never used Played with it Using locally Built a local environment using compose Looked it up on StackOverflow
- 5. Explaining Docker to senior management is like...
- 6. Container Cluster Managers (“Container Distributions?”) Orchestration and Scheduling Frameworks
- 8. Rancher Server Features 100% OpenSource - https://github.com/rancher/rancher + Enterprise support options available from RancherLabs ● High Availability configuration ● Access controls - Active Directory/LDAP/Shibboleh/Github-OAuth ● Rancher Catalog (community + private) ● Rolling Updates (blue/green) and Rollback ● Native Services (DNS, Load Balancers, LetsEncrypt)
- 9. Assembly instructions docker run -d -p 8080:8080 rancher/server Installation…
- 10. Assembly instructions docker run -d --restart=unless-stopped -p 8080:8080 -p 9345:9345 --name rancher_server rancher/server:v1.3.1 --db-host mydb.xxx.eu-west- 1.rds.amazonaws.com --db-port 3306 --db-name mydb --db-user rancher_user --db-pass rancher_pass --advertise-address rancher.mydom.com Installation… Tip: Externalise the DB early so you don’t have to export/import!
- 11. Demos... Walkthrough Infrastructure Demo 1: Hello-World
- 12. Rancher Catalogue P Demo 2: Community -WordPress
- 13. Demos... Walkthrough Infra Catalogue Backing Services Demo 3: Jenkins on EFS
- 14. Demos... Demo 4: Spin up Kubernetes Environment
Editor's Notes
- #3: Ops identity crisis I find it easier to describe what I am doing, rather than what I am. (Doesn’t work so well LinkedIn) Help dev teams deliver projects by creating - shared resources - tooling - providing the environments = in which to build, test and deploy their code. With that, dev teams are effectively my customers, so what I am doing is selling dev experience. Docker is one such tool, which i have tried to promote.
- #4: Spectrum of people at various levels of expertise. - never used Docker - those who have developed some level of mastery. I’m not excluded from this. Fit somewhere in the middle - I first started using Docker about 18M ago. REQUIREMENT: Useful tool for users at any level of expertise
- #5: Common theme in Software Dev is RBACs - users are limited to a strict set of permissions. - Usually good reason, though Unfortunately there exists level of distrust. In the more traditional Operations-led environments are nervous about giving developers operational-level access to their build environments and tooling. I often try to make the case that the Dev is the Product Owner of the Dev Env. - Not going away anytime soon; new tooling needs to keep the security folks happy. REQUIREMENT: Access Control Next, Have you ever had to explain Docker to someone non-technical? It’s painful!
- #6: Never underestimate the value of good UI. Humans - accustomed to visual learning. If trying to “sell” docker, no buy-in by demoing on the command line! - Glazed face REQUIREMENT: Visual Experience
- #7: Unopinionated platforms Analogy: Today people rarely use Linux by downloading the kernel and starting from scratch. - Most people start with a Linux distro; I've seen opinions that we are seeing the same pattern emerge with Container Orchestration where developers intent of (eg Kubernetes) is something to build upon - rather than an out-of-the-box experience. It’s predominantly about building agreement on the primitives and APIs of distributed systems. Selected RANCHER
- #8: Rancher Labs - 2 tools Rancher Server - as described prev RancherOS is a lightweight distro built on Docker, similar to CoreOS.
- #9: 100% OpenSource + Enterprise support options available HA config Access controls Rancher Catalog (community + private) Rolling Updates (blue/green) and Rollback Native Backing Services (DNS, Load Balancers, TLS Certs) Storage: Rancher-EBS,Rancher-EFS Registry Service: ECR
- #10: ---- Assembly instructions At its most basic, starting a new instance of Rancher Server simply involves running the image from dockerhub
- #11: ---- Assembly instructions Externalise the DB early so you don’t have to export/import!
- #12: ---WALKTHROUGH: INFRASTRUCTURE--- ---DEMO 1: HELLO-WORLD --- Use the UI to build a basic container Image: dockercloud/hello-world
- #13: ---WALKTHROUGH: CATALOGUE--- ---DEMO 2: CATALOGUE--- Create a wordpress stack using the default catalog Scale out +2 Show access to logs Show access to SSH Custom Catalogue entries
- #14: ---DEMO 3: INFRA CATALOGUE BACKING SERVICES--- DNS - Amazon R53 Storage - Amazon EFS
- #15: ---DEMO 4--- Create environment 'test' (kubernetes)
- #16: Demo 5 - Show some Rancher eye candy. Spin up Prometheus and go to graphical view *END*