1. Red Hat partner event The evolution of Linux – From containers to OpenShift PaaS & how to get started
Kristijan Walter,
Presales engineer
Veracomp d.o.o.
Opatija,

2. Agenda Containers are Linux –The evolution of RHEL
The value of OpenShift
OpenShift – Choose your flavor with demo (Minishift)

3. When has it all began?
BACK TO

4. Containers are Linux –The evolution of RHEL
Historical overview - The evolution of Linux that made containers possible
1979: Unix V7 – introducing CHROOT 
confined environment
chroot = an operation that changes the apparent root directory for the current running process and its children
A program that is run in such a modified environment cannot access files outside the designated directory tree

5. Containers are Linux –The evolution of RHEL
Historical overview - The evolution of Linux that made containers possible
1991: chroot jail - term "jail" introduced by computer security researcher Bill Cheswick creating a honeypot to monitor a hacker
2000: FreeBSD Jails - partition a FreeBSD computer system into several independent, smaller systems – called “jails” – with the ability to assign an IP address for each system and configuration.

6. Containers are Linux –The evolution of RHEL
Historical overview - The evolution of Linux that made containers possible
2000: NSA released SELinux – the first SELinux version released to the open source community under the GNU GPL (later added to RHEL 4)
SELinux = is a set of patches to the Linux kernel and utilities to provide a strong, flexible, mandatory access control (MAC) that confine user programs and services access to files & system resources
Container security is Linux security !!! + + =
RED HAT = biggest contributor

7. Containers are Linux –The evolution of RHEL
Historical overview - The evolution of Linux that made containers possible
2001: Linux Vserver project - jails with kernel-level isolation (patched Linux kernel) – separated environments called “Virtual Private Servers”
2004: Solaris Containers – “Zones” (not real containers)
2005: OpenVZ – similar to Solaris Containers
Drawbacks:
lack of process migration and clustering
patched kernel (headache fir linux distis & sysadmins)
Allows running several general purpose Linux servers on a single box with a high degree of independence and security

8. Containers are Linux –The evolution of RHEL
Historical overview - The evolution of Linux that made containers possible
2006: adding Generic process containers to Linux kernel (later renamed to control groups or cgroups)
Started by Google engineers
Cgroups provide:
Resource limiting (e.g. set memory limit)
Prioritization (e.g. some cgroups get larger share of resources than others, like CPU, memory, etc.)
Accounting (measuring how much resources certain systems use, e.g. for billing purposes)
Control (e.g. freezing, checkpointing or restarting)
Cgroups allow processes to be grouped together, and ensure that each group gets a share of memory, CPU and disk I/O; preventing any one container from monopolizing any of these resources.

9. Containers are Linux –The evolution of RHEL
Historical overview - The evolution of Linux that made containers possible
2008: adding User namespaces to Linux kernel
(patches added by Red Hatter Eric W. Biederman)
allow a process to have it’s own set of users
A process’ UID and GID can be different
Users (UID) and groups (GID) may have privileges for certain operations inside a user namespace without having those privileges outside a user namespace
isolates an application's view of the operating environment
Isolation: Enable a process (or several processes) to have
different views of the system than other processes.
2010: Red Hat Enterprise Linux 6
launches with cgroups and
namespaces

10. Containers are Linux –The evolution of RHEL
Historical overview - The evolution of Linux that made containers possible
2008: The Linux Containers project (LXC)
= operating-system-level virtualization method for running multiple isolated Linux systems on a control host using a single Linux kernel
The Good:
Improved user experience (added userspace tools on top of cgroups and namespaces)
No need for kernel patches
The Bad:
- Security concerns (solved later in 2014; added SELinux)
2011: Red Hat launches OpenShift
as first enterprise PaaS
based on Linux containers

11. Containers are Linux –The evolution of RHEL
Historical overview - The evolution of Linux that made containers possible
2013: Docker – built on top of LXC, cgroups & namespaces
Formerly PaaS company dotCloud – renamed to Docker, Inc.
LXC later replaced by Docker’s own library: libcontainer
Entire ecosystem for managing containers (container image, registries, REST API, CLI…) – additional layer of abstraction
Open Source project: Docker – Red Hat is the 2nd largest contributor (after Docker, Inc.)
Docker is included in RHEL 7 ( )
# yum install docker device-mapper-libs device-mapper-event-lib
# systemctl start docker.service
# systemctl enable docker.service

12. Containers are Linux –The evolution of RHEL
Historical overview - The evolution of Linux that made containers possible
2014: Kubernetes – Open-Source project for Container Orchestration
Google: “everything at Google runs in a container” 
“...starting over 2 billion containers per week.”
Based on Google’s internal platform - Borg
clustering together groups of hosts running Linux containers
clusters can span hosts across public, private, or hybrid clouds
Introducing PODS = group of one or more containers deployed to a single node - all containers in a pod share an IP address, IPC, hostname, and other resources
Orchestrating containers via Kubernetes, even in a single master/node deployment with RHEL Atomic Host

13. Containers are Linux –The evolution of RHEL
OpenShift = LDK stack (Linux + Docker + Kubernetes)
“OpenShift is Enterprise Kubernetes and more”
OpenShift = User Experience
RHEL = foundation for OCP
“One cannot resist an idea whose time has come” (V. Hugo)

14. CONCLUSION - WHY RED HAT FOR CONTAINERS?
Red Hat’s contributions to containers go back to the creation of those core container primitives (cgroups, namespaces, SELinux…), since year 2000
Containers have been a core feature of RHEL over multiple major releases
RHEL is the foundation of Red Hat OpenShift since its initial release in 2011
Red Hat is #2 contributor to the Docker project (since 2013)
Red Hat packages and ships a fully supported binary version of the Docker container engine project as part of RHEL 7 and RHEL Atomic Host
Red Hat leverages the power of Kubernetes to move containers in multiple environments (Private / Public / Hybrid Cloud)
Red Hat is a leader in the upstream container communities and governance organizations
Red Hat is a leader in Linux over the past 15+ years 

15. The value of OpenShift Higher density Less overhead More efficiency
Application portability
Overhead
An IT manager in the early 2000s talking about virtualization: “Great for development, but I’ll never run it in production!”
CONTAINERS = “LIGHTWEIGHT VIRTUALIZATION”
“What if it wasn’t one cpu with multiple kernels, but one kernel with multiple userlands?”
Faster software and applications delivery – increased productivity (for developers)
Less overhead = less complexity for maintanence (for sys admins)

16. The value of OpenShift For Developers:
optimal platform for provisioning, building, and deploying applications
self-service provisioning
automated workflows (e.g. S2I for building images)
polyglot Language support (Java, PHP, Node.js, Perl, Python, Ruby… and latest… .NET core 2.0)
multiple choice of databases (MariaDB, MongoDB, MySQL, PostgreSQL, Redis)
integration with tools for Continuous Integration (CI) / Continuous Delivery (CD)
For System Admins (IT Operations):
enterprise grade Kubernetes for orchestration
policy-based control and automation for applications
cluster services & scheduling
load-balancing
auto-scaling
strong security (preventing tenants from compromising other apps or the underlying host)
ability to attach storage directly to Linux containers
running stateful and stateless apps on one platform

17. OpenShift – Choose your flavor
Open Source (Upstream, Community) Project
Innovation
Innovation
Stabilization
Stabilization
Innovation
Stabilization
On-Demand, Public Cloud Service, Operated by RedHat
Commercial Software to run your own Private PaaS on the Infrastructure of your Choice
Your own private, high availability OpenShift cluster, hosted on Amazon Web Services (AWS) or Google Cloud Platform (GCP) - operated as a cloud service by Red Hat
Application portability

18. OpenShift – Choose your flavor
FLEXIBILITY:
Running on bare-metal (RHEL/RHEL Atomic Host)
Running in virtualized datacenter (Vmware, KVM, RHEV)
Running in private cloud / hybrid cloud (Amazon EC2, OpenStack)
Running in Public Clouds (Azure, AWS, GCP)
PORTABILITY:
Low cost-of-entry, portability with low-cost-of-exit
No licences = No CAPEX
subscriptions = OPEX (“-as-a-Service model”)
No vendor lock-in
OpenShift – The CIO’s choice

19. OpenShift – getting started (demo)
1) Choose a priceplan:
2) Sign up:
3) Login and start:

20. OpenShift – getting started (demo)
Supported operating systems and hypervisors:
Apple macOS
GNU / Linux
Windows
Xhyve (default)
KVM (default)
Hyper-V (default)
VirtualBox
VirtualBox
VirtualBox
VMware Fusion

21. OpenShift – getting started (demo)
Installing Minishift on your laptop
Step-by-step guide:
Download from github:
Unzip to local folder and start…

22. OpenShift – getting started (demo)
Installing Minishift on your laptop…
Deploying a sample .NET core 2.0 application

23. Thank you! Q&A?