Openshift: The power of kubernetes for engineers - Riga Dev Days 18
•
5 gefällt mir•466 views
Workshop material for OpenShift training at Riga Dev Days 2018
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie Openshift: The power of kubernetes for engineers - Riga Dev Days 18
Ähnlich wie Openshift: The power of kubernetes for engineers - Riga Dev Days 18 (20)
Mehr von Jorge Morales
Mehr von Jorge Morales (8)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Openshift: The power of kubernetes for engineers - Riga Dev Days 18
- 1. OpenShift: The power of Kubernetes for engineers Jorge Morales OpenShift Developer Advocate @jorgemoralespou Riga Dev Days 18
- 2. Me (aka Jorge) ● Spanish by nature and by language ● Work at Red Hat ● OpenShift Developer Advocate ● Mostly Java developer ● Obsessed with improving development experience @jorgemoralespou github.com/jorgemoralespou http://jorgemoral.es
- 3. 09:30 – 11:00 Introduction to OpenShift 11:00 – 11:30 Refreshment/Bio Break 11:30 – 13:00 Hands on labs - part 1 13:00 – 14:00 Lunch 14:00 – 15:30 Hands on labs - part 2 15:30 – 16:00 Refreshment/Bio Break 16:00 – 17:00 Hands on labs - part 3 17:00 – 17:30 Recap Agenda
- 5. Goals 1. Quick Introduction to Containers, Kubernetes, and OpenShift 2. Show You the Power of it All in Action!
- 6. What is it for?
- 7. QUICK DEMO
- 8. CrunchyData GitLab Iron.io Couchbase Sonatype EnterpriseDB and many more 8 ...and virtually any docker image out there! TRUE POLYGLOT PLATFORM PHPPythonJava NodeJS Perl Ruby .NET Core Apache HTTP Server MySQL Redis nginx TomcatVarnish JBoss EAP JBoss A-MQ JBoss Fuse JBoss BRMS JBoss BPMS JBoss Data Grid JBoss Data Virt RH Mobile RH SSO 3SCALE API mgmt JBoss Web Server Spring Boot Wildfly Swarm Vert.x PostgreSQL MongoDB Phusion Passenger Third-party Language Runtimes Third-party Databases Third-party App Runtimes Third-party Middleware Third-party Middleware
- 9. But why?
- 13. 13 A DRIVER CONTAINERS Adopting a container-based strategy helps applications to be easily shared and deployed.
- 14. 14 APPLICATIONS REQUIRE MANY CONTAINERS. HOW DO YOU DELIVER AND MANAGE THEM AT SCALE?
- 15. The industry’s most secure and comprehensive enterprise-grade container platform based on industry standards, Docker and Kubernetes. BUILD, DEPLOY, AND MANAGE AT SCALE WITH RED HAT OPENSHIFT CONTAINER PLATFORM 15
- 16. What is it built from?
- 17. How you get it
- 18. Why containers?
- 19. WHAT ARE CONTAINERS? It Depends Who You Ask ● Sandboxed application processes on a shared Linux OS kernel ● Simpler, lighter, and denser than virtual machines ● Portable across different environments ● Package my application and all of its dependencies ● Deploy to any environment in seconds and enable CI/CD ● Easily access and share containerized components INFRASTRUCTURE APPLICATIONS
- 20. VMs vs Containers VIRTUAL MACHINES CONTAINERS virtual machines are isolated apps are not containers are isolated so are the apps VM OS Dependencies Kernel Hypervisor Hardware App App App App Hardware Container Host (Kernel) Container App OS deps Container App OS deps Container App OS deps Container App OS deps
- 21. https://github.com/openshift-evangelists/workshop-summit/blob/master/nginx/Dockerfile FROM centos ADD nginx.repo /etc/yum.repos.d/ RUN yum update -y && yum install -y nginx RUN mkdir -p /nginx ADD nginx.sh /nginx/ RUN chmod 777 -R /nginx EXPOSE 8080 WORKDIR /nginx VOLUME ["/nginx/html"] VOLUME ["/nginx/logs"] CMD ["./nginx.sh"]
- 22. $ docker build -t app:v1 . $ docker run app:v1
- 23. Orchestration, Scheduling, Clustering, Shared Storage are All Still Needed
- 24. Kubernetes is an open-source platform designed to automate deploying, scaling, and operating application containers.
- 25. With Kubernetes, you are able to quickly and efficiently respond to customer demand: ● Deploy your applications quickly and predictably. ● Scale your applications on the fly. ● Roll out new features seamlessly. ● Limit hardware usage to required resources only.
- 26. Need to provide a good experience for developers and not just IT operations
- 29. Atomic Host Container Runtime & Packaging (Docker) Red Hat Enterprise Linux Infrastructure Automation & Mg Networking Storage Registry Logs & Metrics Security Container Orchestration & Cluster Management (kubernetes) OpenShift Application Lifecycle Management (CI/CD) Build Automation Deployment Automation Service Catalog (Language Runtimes, Middleware, Databases) Self-Service Container Business Automation Container Integration Container Data & Storage Container Web & Mobile
- 31. So, why OpenShift 1. You want more out of containers 2. You want more out of Kubernetes 3. You are smart, focusing on the things you enjoy doing
- 32. How it works
- 41. Nodes
- 42. Master nodes
- 44. Users and Groups USER & GROUPS ● USER ● GROUPS ● SERVICEACCOUNTS types: ● system:authenticated ● system:admin ● system:serviceaccounts:myproject ● jorge ● john ● admin ● system:serviceaccount:myproject:default ● system:serviceaccount:myproject:builder ● system:serviceaccount:myproject:deployer
- 45. Scopes / Multitenancy projectB projectC projectA PROJECT (a.k.a namespace) PROJECT SCOPED CLUSTER SCOPED Constrains: ● Resources ● Visibility View all View project
- 46. Authn & Authz API Server
- 49. Workload placement dev test prod dc1 dc2 API Server etcd Scheduler
- 50. Workloads ● Stateless ○ ReplicaSet (also known as ReplicationController) ● Stateful ○ StatefulSet (previously known as PetSet) ● Batch ○ Jobs ○ CronJobs ● Daemon ○ DaemonSet
- 51. Workload execution guarantees API Server etcd Scheduler Repl. Ctrlr
- 52. Workload execution guarantees API Server etcd Scheduler Repl. Ctrlr
- 53. Workload execution guarantees API Server etcd Scheduler Repl. Ctrlr
- 58. PersistentVolume and PersistentVolumeClaim API Server etcd Scheduler Repl. Ctrlr DNS PV 5GB NFS
- 59. Configuring apps API Server etcd Scheduler Repl. Ctrlr DNS PV 5GB NFS username=XYZ password=XYZ databasename=XYZ
- 60. Linking services API Server etcd Scheduler Repl. Ctrlr DNS username=XYZ password=XYZ databasename=XYZ username=XYZ password=XYZ databasename=XYZ
- 61. Linking services API Server etcd Scheduler Repl. Ctrlr DNS service=database
- 63. Source 2 Image Walk Through Code Build Deploy Container Image Registry
- 64. Source 2 Image Walk Through Code Developers can leverage existing development tools and then access the OpenShift Web, CLI or IDE interfaces to create new application services and push source code via GIT. OpenShift can also accept binary deployments or be fully integrated with a customer’s existing CI/CD environment.
- 65. Source 2 Image Walk Through Build OpenShift automates the Docker image build process with Source-to-Image (S2I). S2I combines source code with a corresponding Builder image from the integrated Docker registry. Builds can also be triggered manually or automatically by setting a Git webhook. Add in Build pipelines Container Image Registry
- 66. Source 2 Image Walk Through Deploy OpenShift automates the deployment of application containers across multiple Node hosts via the Kubernetes scheduler. Users can automatically trigger deployments on application changes and do rollbacks, configure A/B deployments & other custom deployment types. Container Image Registry
- 67. Image distribution API Server etcd Scheduler Repl. Ctrlr DNS Registry Docker hub
- 68. Time to try it out
- 69. Hands on! bit.ly/openshift-rigadevdays18 NOTE: The platform is shared. Don’t abuse it
- 71. 7 1 A container is the smallest compute unit CONTAINER
- 72. 7 2 containers are created from container images CONTAINER CONTAINER IMAGE BINARY RUNTIME
- 73. 7 3 IMAGE REGISTRY container images are stored in an image registry CONTAINER CONTAINER IMAGE CONTAINER IMAGE CONTAINER IMAGE CONTAINER IMAGE CONTAINER IMAGE CONTAINER IMAGE
- 74. an image repository contains all versions of an image in the image registry 7 4 IMAGE REGISTRY frontend:latest frontend:2.0 frontend:1.1 frontend:1.0 CONTAINER IMAGE mongo:latest mongo:3.7 mongo:3.6 mongo:3.4 CONTAINER IMAGE myregistry/frontend myregistry/mongo
- 75. PODPOD containers are wrapped in pods which are units of deployment and management 7 5 CONTAINER CONTAINERCONTAINER IP: 10.1.0.11 IP: 10.1.0.55
- 76. pods configuration is defined in a deployment 7 6 image name replicas labels cpu memory storage POD CONTAINER POD CONTAINER POD CONTAINER DEPLOYMENT
- 77. POD services provide internal load-balancing and service discovery across pods 7 7 CONTAINER POD CONTAINER POD CONTAINER BACKEND SERVICE POD CONTAINER role: backend role: backendrole: backendrole: backendrole: frontend
- 78. POD apps can talk to each other via services 7 8 CONTAINER POD CONTAINER POD CONTAINER BACKEND SERVICE POD CONTAINER role: backend role: backendrole: backendrole: backendrole: frontend Invoke Backend API
- 79. POD routes add services to the external load-balancer and provide readable urls for the app 7 9 CONTAINER POD CONTAINER POD CONTAINER BACKEND SERVICE ROUTE app-prod.mycompany.com > curl http://app-prod.mycompany.com
- 80. projects allow managing apps in isolation from other environments, teams, groups and departments 8 0 POD C POD C POD C PAYMENT DEV POD C POD C POD C PAYMENT PROD POD C POD C POD C CATALOG POD C POD C POD C INVENTORY ❌ ❌❌
- 81. Where to next
- 82. Self Paced Tutorials - https://learn.openshift.com/
- 83. Developer Resources ● eBook (O’Reilly): DevOps with OpenShift https://www.openshift.com/promotions/devops-with-openshift.html ● eBook (O'Reilly): OpenShift for Developers: https://www.openshift.com/promotions/for-developers.html ● eBook (O'Reilly): Deploying to OpenShift: https://www.openshift.com/deploying-to-openshift/
- 85. The code for this labs ● Source code for the examples: ○ https://github.com/openshift-roadshow ● Source code for instructions: ○ https://github.com/openshift-labs/starter-guides
- 86. THANK YOU 86