Rancher is an open-source platform for running containers on any infrastructure. It provides teams with authentication, networking, load-balancing, and service discovery capabilities, while leveraging Kubernetes, Mesos, and Docker Swarm for orchestration and scheduling.
In this talk, we'll briefly discuss some of the considerations your organization needs to consider when adopting containers, before introducing and demonstrating the Rancher platform.
During this Habitat presentation/workshop, we will do a deep dive into the components that make up Habitat and learn all about what it takes to create a Habitat Artifact that lives inside a Docker container. You will then be exposed to a few demos showing off some of Habitat's awesome features.
Afterward, you will build your own Habitat Artifact and post-process it to live inside a Docker container!
Join us as we go from Zero to Habitat in a Containerized World!
** NOTE : It's strongly recommended that you come with a working Docker environment and WiFi. If you are on Windows, please come with a Linux workstation inside a VM which has a Docker environment installed. After the presentation and demo part of this session, there will be a short break.
Rancher is an open-source platform for running containers on any infrastructure. It provides teams with authentication, networking, load-balancing, and service discovery capabilities, while leveraging Kubernetes, Mesos, and Docker Swarm for orchestration and scheduling.
In this hands-on workshop, you'll learn how to deploy a fully-containerized application with Rancher. We'll cover setting up access control, choosing an orchestrator, connecting registries, provisioning infrastructure, and ultimately launching and monitoring your application.
Pre-reqs:
1. A linux VM with Docker. (For this workshop we do not recommend Docker for Mac, Windows, etc)
2. Docker 1.11.3 or greater.
3. Git
4. Docker/Linux command line familiarity.
Docker containers are all the rage with developers, and it's clear why...with Docker it is easy to create consistent environments to build and test apps. But what happens post-development?
To optimally support DevOps pipelines, the Docker image must be the new artifact; from development through build, test, and deployment.
In this presentation, Chris Ciborowski will cover how teams can use Docker in an end-to-end pipeline, using images as an artifact and obtaining "git push; deployed."
The presentation can be found here:
http://nebulaworks.slides.com/chrisciborowski/containerizethis-2016-docker-containers-devops-adoption/fullscreen?token=44onzZQq
At times it seems that the whole world has jumped on the container bandwagon, with little consideration given to what running microservices and containers in production actually requires. In selecting the best possible container orchestration and management platform, you must take into consideration everything from developer enablement to CI/CD pipeline automation to scaling of your infrastructure, among others.
In this keynote, we will examine this issue and explain how Kontena addresses them and makes running containers and microservices simple and easy, even after the initial excitement and novelty wears off.
Historically, CI/CD pipelines produced software artifacts that needed to be deployed into specially configured run environments. Problems often occur because environments are different or configuration is missing. Docker is a containerization technology that addresses this challenge.
Tom Adams leads a hands-on tutorial that walks you through transforming a build pipeline from creating a software artifacts to building Docker images - that includes both the software and environment configuration.
You’ll learn about basic build pipelines, CI Servers and building Docker containers.
Knowledge / Materials Needed In Advance
In this workshop, you'll learn how to install and scale the Kontena container and microservices platform. Once the Kontena platform is up and running, we'll move on to installing Neo4j & Twitter graph analyzer, enabling the audience to analyze their own respective Twitter graphs.
Take homes:
