8.7 KiB
- Agenda
- 1. Introduction to containers & kubernetes
- 2. Exploring openshift application platform
- 3. Setting up your development environment
Welcome to the OpenShift Ruby on Rails Workshop!
The workshop provides ruby developers an introduction to OpenShift and containers, and how these can be used to build fully automated end-to-end continuos integration and deployment pipelines for Ruby on Rails applications.
Agenda
| # | Topic | How | Time allocated | Section link |
|---|---|---|---|---|
| 1 | Introduction to containers & kubernetes | Facilitator led, group session | 10m | Link |
| 2 | Exploring openshift application platform | Facilitator led, group session | 10m | Link |
| 3 | Setting up your development environment | Individual, hands on excercise | 10m | Link |
| 4 | Deploying a ruby application | Individual, hands on excercise | 20m | Link |
| 5 | Creating a deployment pipeline | Individual, hands on excercise | 20m | Link |
| 6 | Developing & deploying a new feature | Individual, hands on excercise | 20m | Link |
1. Introduction to containers & kubernetes
Before we can get hands on with the workshop, let's make sure we have an understanding of both containers and kubernetes.
What are containers?
Containers are technologies that allow the packaging and isolation of applications with their entire runtime environment—all of the files necessary to run. This makes it easy to move the contained application between environments (dev, test, production, etc.) while retaining full functionality.
What does this mean? For starters, virtualization uses a hypervisor to emulate hardware, which allows multiple operating systems to run side by side. This isn’t as lightweight as using containers.
When you have finite resources with finite capabilities, you need lightweight apps that can be densely deployed. Linux containers run natively on the operating system, sharing it across all of your containers, so your apps and services stay lightweight and run swiftly in parallel.
Containers are also an important part of IT security. By building security into the container pipeline, containers stay reliable, scalable, and trusted.
You can also easily move the containerized application between public, private and hybrid cloud environments and data centers (or on-premises) with consistent behavior and functionality.
Why are containers important?
Containers help reduce conflicts between your development and operations teams by separating areas of responsibility. Developers can focus on their apps and operations teams can focus on the infrastructure. And, because containers are based on open source technology, you get the latest and greatest advancements as soon as they’re available.
Container technologies—including Podman, Skopeo, Buildah, CRI-O, Kubernetes, and Docker — help your team simplify, speed up, and orchestrate application development and deployment.
Containers share the same operating system kernel and isolate the application processes from the rest of the system so the whole thing can be moved, opened, and used across development, testing, and production configurations.
Because they are lightweight and portable, containers provide the opportunity for faster development and meeting business needs as they arise.
What is kubernetes?
Kubernetes (also known as k8s or "kube") is an open source container orchestration platform that automates many of the manual processes involved in deploying, managing, and scaling containerized applications.
You can cluster together groups of hosts running Linux® containers, and Kubernetes helps you easily and efficiently manage those clusters.
Kubernetes clusters can span hosts across on-premise, public, private, or hybrid clouds. For this reason, Kubernetes is an ideal platform for hosting cloud-native applications that require rapid scaling.
Kubernetes was originally developed and designed by engineers at Google. Google was one of the early contributors to Linux container technology.
Red Hat was one of the first companies to work with Google on Kubernetes, even prior to launch, and has become the 2nd leading contributor to the Kubernetes upstream project. Google donated the Kubernetes project to the newly formed Cloud Native Computing Foundation (CNCF) in 2015.
2. Exploring openshift application platform
Now that we have refreshed on containers and kubernetes, let's take a tour through the OpenShift application platform from the perspective of a developer.
Web console developer view
The first stop on our tour will be the Web console "Developer View". In order to move quickly with containers, developers need to be able to use the benefits of Kubernetes without being required to develop a platform engineering skillset. Taking time from development cycles to learn, install, and manage infrastructure tools is not helping get business applications to market.
Red Hat OpenShift has a specifically designed developer view so that you can make the most of the platform, without having to get bogged down learning kubernetes.
Within developer view you can see a graphical topology for your application, check application logs or observability metrics, scale applications, restart deployments, review pipelines and much more.
Web console terminal
Sometimes you just need to quickly drop into a terminal to get something done. With the OpenShift Web Terminal you don't need to leave your browser or worry about logging in at a local terminal!
Quick add for new applications
Want to quickly test a proof of concept or spin up a container? Awesome, within developer view in OpenShift you can quickly add a new application directly from git, from an existing image, from a Dockerfile, a yaml manifest, or a catalog of templated services.
3. Setting up your development environment
For our first hands on excercise let's get logged into the tools we'll be using today and get familar with each.
Log into bitbucket and fork codebase
For this workshop we will be using a Bitbucket server as our git source control management tooling. The server is running on the same OpenShift cluster we will be using for the hands on excercises and can be accessed with the link below:
https://bitbucket-bitbucket.apps.rosa-7lpn7.2pqm.p1.openshiftapps.com
Use the credentials provided on the workshop etherpad to login.
Once logged in you should be able to view and create a fork of the Rails Team/openstreetmap-website repository to your own user using this link: https://bitbucket-bitbucket.apps.rosa-7lpn7.2pqm.p1.openshiftapps.com/projects/MSD/repos/openstreetmap-website?fork
Log into openshift web console
Once we have our individual code fork created let's log into the OpenShift web console using the link https://console-openshift-console.apps.rosa-7lpn7.2pqm.p1.openshiftapps.com.
Use the credentials provided on the workshop etherpad to login.
Once logged in feel free to repeat the OpenShift tour we went through as a group in section two to get more comfortable with the user interface.