OpenShift. Marek Jelen, OpenShift, Red Hat

Transcription

1 OpenShift Marek Jelen, OpenShift, Red Hat

2 The problem Ever growing pressure on IT IT becoming the most integral part of most organizations The budgets do not grow as the requirements do Engineers demanding new technologies Business demands quick answers & solutions Operations asked to provide 9s Micro-services = many moving parts

3 Are there answers? DevOps to the rescue Give engineering the right tools they need Keep operations in charge Containers to the rescue Higher density, lower overhead Security through application isolation Automation to the rescues Let technology work for you Eliminate human error

4 PaaS has answers Self-provisioning of resources Automation of deployment process QA & Dev & Prod with same environment It s Easy. Work the way you want. Developers works in their IDE, browser, or command-line Java, Ruby, PHP, Python, Perl, Node.js Continuous Integration tools included JBoss included, full JavaEE capabilities No lock-in

5 Why PaaS? Quickly build the Application that YOU need for Your Group, your Enterprise, your next great idea! Big data, mobile, social You code the application, PaaS runs it for you Leverage the ease, scale and power of the Cloud

6

7

8

9 Peek into the (close) future OpenShift v3

10 Move beyond Applications Make non-web applications first-class citizens Big-data, databases, custom servers, HTTP frontends, you name it! Focus on services that talk to each other (SOA, microservices) Deploy components with relationships among them Allow isolated evolution of components rather than monoliths Image based deployment rather than application based Single image contains complete dependency chain Declarative deployment of components You say what is needed and how it should be linked, we deliver Trigger based deployments

11 Buzzwords Microservices Treat your servers as cattle not as pets

12 Containers Containers ship software Containers are self contained Container is a unit of packaging Containers are reusable Containers are universal

13 Docker Manage set of containers Move containers Load containers

14 Kubernetes Manage Docker fleet Ensure coordination Provide resiliency Provide high availability

15 OpenShift (operations) Abstract Kubernetes Hide complexities Manage lifecycles

16 OpenShift (engineers) Provide user experience Simplify workflows Abstract operational tasks

17 Pieces - recap Docker container management on single machine distribution of containers through marketplace (registry) Kubernetes manage containers on scale open-sourcing Google s container deployment know-how OpenShift application lifecycle - build, deploy, manage, promote user interface and user experience

18 Networking Make it simple for components to talk to each other provide every component with it s own address provide facilities to publish addresses of components Ensure that communication is private among friends SDN virtual networks Management has to be in the hands of operators developers do not need to know and care Provide pluggable mechanisms for implementation

19 Storage Make stateful applications first class citizens 12-factor apps are nice, but not always feasible component can be any service, including databases Applications define what they need (space, IO, etc.) Implementation is hidden from engineers Virtual storage to the rescue (SDS) operationally simpler than local storage provides ways to grow and expand in time IaaS-lie, NFS, SAN, Cepth, Gluster,... Fast storage for special cases (local) virtual storage is not always good-enough

20