DOCSLIB.ORG

Leveraging Containers and Openstack

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Leveraging Containers and Openstack Leveraging Containers and OpenStack A Comprehensive Review Introduction Imagine that you are tasked to build an entire private cloud infrastructure from the ground up. You have a limited budget, a small but dedicated team, and are asked to pull off a miracle. A few years ago, you’d build an infrastructure with applications running in virtual machines, with some bare-metal machines for legacy applications. As infrastructure has evolved, virtual machines (VMs) enabled greater levels of efficiency and agility, but VMs alone don’t completely meet the needs of an agile approach to application deployment. They continue to serve as a foundation for running many applications, but increasingly, developers are looking toward the emerging trend of containers for leading-edge application development and deployment because containers offer increased levels of agility and efficiency. Container technologies like Docker and Kubernetes are becoming the leading standards for building containerized applications. They help free organizations from complexity that limits development agility. Containers, container infrastructure, and container deployment technologies have proven themselves to be very powerful abstractions that can be applied to a number of different use cases. Using something like Kubernetes, an organization can deliver a cloud that solely uses containers for application delivery. But a leading-edge private cloud isn’t just about containers, and containers aren’t appropriate for all workloads and use cases. Today, most private cloud infrastructures need to encompass bare-metal machines for managing infrastructure, virtual machines for legacy applications, and containers for newer applications. The ability to support, manage and orchestrate all three approaches is the key to operational efficiency. OpenStack is currently the best available option for building private clouds, with the ability to manage networking, storage and compute infrastructure, with support for virtual machines, bare-metal, and containers from one control plane. While Kubernetes is arguably the most popular container orchestrator and has changed application delivery, it depends on the availability of a solid cloud infrastructure, and OpenStack offers the most comprehensive open source infrastructure for hosting applications. OpenStack’s multi-tenant cloud infrastructure is a natural fit for Kubernetes, with several integration points, deployment solutions, and ability to federate across multiple clouds. In this paper, we’re going to explore how containers work within OpenStack, examine various use cases, and provide an overview of open source projects, from OpenStack and elsewhere, that help make containers a technology that’s easily adopted and utilized. I. A High Level View of Containers in OpenStack There are three primary scenarios where containers and OpenStack intersect. The first scenario, called infrastructure containers, allows operators to leverage containers in a way that improves cloud infrastructure deployment, management, and operation. In this scenario, containers are set up on a bare-metal infrastructure, and are allowed privileged access to host resources. This access allows them to take direct advantage of compute, networking, and storage resources that container runtimes are typically trying to hide from users. The containers isolate the often complex set of dependencies that each application depends on, while still allowing the infrastructure applications to directly manage and manipulate the underlying system resources. When the time comes to upgrade an service, the upgrade can be handled without changes in dependencies disrupting co-located services. Modern versions of OpenStack have embraced this infrastructure container model, and it’s now normal to manage an entire lifecycle of an OpenStack deployment with a combination of orchestration tooling and containerized services. Infrastructure containers enable operators to use container orchestration technologies to solve many issues, particularly around rapidly iterating/upgrading existing software including OpenStack. Running OpenStack within containers helps operators to solve Day 2 challenges, including adding new components for services, upgrading versions of software quickly, and rapidly rolling updates across machines and data centers. This approach brings the agility of containers to the problem of OpenStack deployment and upgrades. The second scenario is concerned with hosting containerized application frameworks on cloud infrastructure. These can include Container Orchestration Engines (COEs) like Docker Swarm and Kubernetes, or lighter-weight container-focused services and serverless application programming interfaces (APIs). Whether on bare-metal or VMs, the OpenStack community has worked to ensure that it’s possible to deliver containerized applications on a secure, tenant-isolated cloud host. This scenario is facilitated by drivers that allow projects like Kubernetes to directly take advantage of OpenStack APIs for storage, load-balancing, and identity. It also includes APIs for provisioning managed Kubernetes clusters and application containers on demand. With these capabilities, development teams can write new containerized applications and quickly provision Kubernetes clusters on OpenStack clouds. It’s a complete application lifecycle solution that gives them the resources needed to develop, test, and debug their code, with robust automation to deploy their applications into production. In the final scenario, we consider the interactions between independent OpenStack and COE deployments, and in this paper particularly Kubernetes clusters. Consistency and interoperability of APIs across both OpenStack and Kubernetes clusters is the primary source of success for this scenario. For example, it’s possible for Kubernetes to directly attach to OpenStack Cinder hosted volumes, use OpenStack Keystone as an authorization and authentication backend, or connect to OpenStack Neutron as a network overlay with OpenStack Kuryr. Conversely, it’s possible for an OpenStack cloud to share the same network overlay as a Kubernetes cluster with Neutron drivers for projects like Calico. The third scenario is less focused on how a cloud service is hosted (be it Kubernetes or OpenStack), and more on how independent services interact. II. OpenStack Container Integration Points Deploying OpenStack Infrastructure on Containers As noted in the introduction, the deployment and management of OpenStack has changed significantly with the rise of containers, because containers unlock new approaches to managing infrastructure code. Previous management strategies required either the creation and maintenance of heavyweight golden machine images, or using brittle state- maintaining configuration-management systems. Each approach comes with complexities and restrictions. Adding to the degree of difficulty is the management of a collection of services that all require their own dependencies that change from release-to-release. Without some form of application isolation, solving for the dependencies becomes difficult if not impossible. Infrastructure containers enable new OpenStack deployment projects to strike a balance between the two while elegantly solving the dependency problem. Using lightweight, independent, self-contained, and typically stateless application containers, a cloud operator gains tremendous flexibility when deploying a complex control plane. Combined with a container runtime and an orchestration engine, infrastructure containers make it possible to quickly deploy, maintain, and upgrade complex and highly available infrastructure. In building an OpenStack cluster, there are several dimensions for choosing deployment technologies. An operator could choose Linux Containers (LXC) or Docker for their base containers, use pre-built or custom-built application containers, and select either traditional configuration-management systems for orchestration or a more modern approach like Kubernetes. Table 1 summarizes the existing OpenStack deployment projects and their underlying technologies. Project Container Type Supported Containers Project OpenStack-Ansible LXC OSA LXC Containers Ansible Kolla-Ansible Docker Kolla Containers Ansible Triple-O Docker Kolla Containers Ansible OpenStack-Helm Docker Kolla Containers Kubernetes and Helm Loci Containers Table 1 Underlying each of these deployment systems are different approaches to building a set of containers for the OpenStack code and supporting services. The OpenStack Ansible (OSA) and Kolla projects provide their own project-hosted build systems, while LOCI focuses on building project application containers, without a specific orchestration system in mind. At a high level, the differences are: 1. OSA is unique in that it relies on lower-level LXC containers, and has a custom build system for creating LXC application containers. 2. The Kolla build system produces Docker containers, one for each service, along with supporting containers for initializing and managing an OpenStack deployment. Kolla containers are highly configurable, with a choice of base operating system, source or package installations, and a template engine for even further customization. 3. The final option for building OpenStack application containers is LOCI. LOCI also builds Docker containers, and delivers one container for each project. LOCI is focused on producing compact and secure containers quickly, for all common distributions, with the expectation that they will be used as
Load more

Recommended publications
  • Cloud Computing Bible Is a Wide-Ranging and Complete Reference
    A thorough, down-to-earth look Barrie Sosinsky Cloud Computing Barrie Sosinsky is a veteran computer book writer at cloud computing specializing in network systems, databases, design, development, The chance to lower IT costs makes cloud computing a and testing. Among his 35 technical books have been Wiley’s Networking hot topic, and it’s getting hotter all the time. If you want Bible and many others on operating a terra firma take on everything you should know about systems, Web topics, storage, and the cloud, this book is it. Starting with a clear definition of application software. He has written nearly 500 articles for computer what cloud computing is, why it is, and its pros and cons, magazines and Web sites. Cloud Cloud Computing Bible is a wide-ranging and complete reference. You’ll get thoroughly up to speed on cloud platforms, infrastructure, services and applications, security, and much more. Computing • Learn what cloud computing is and what it is not • Assess the value of cloud computing, including licensing models, ROI, and more • Understand abstraction, partitioning, virtualization, capacity planning, and various programming solutions • See how to use Google®, Amazon®, and Microsoft® Web services effectively ® ™ • Explore cloud communication methods — IM, Twitter , Google Buzz , Explore the cloud with Facebook®, and others • Discover how cloud services are changing mobile phones — and vice versa this complete guide Understand all platforms and technologies www.wiley.com/compbooks Shelving Category: Use Google, Amazon, or
    [Show full text]
  • Manager, Software Engineering
    RESUME RAMESH A (PRINCE2® Practitioner) E-mail : [email protected] Mobile : +919886311312 Summary: Over 14 years 10 months of involvement in IT industry with solid foundation on Software Testing (as Manager, Test/Technical lead, Test Architect, Scrum Master) in the cutting edge innovations/technologies Managing, Mentoring, Guiding and Leading 14 QA team members across 4 different projects Implementing QA strategies, Open source technologies to maximize the Product Quality and Test Coverage Accountable and Responsible for planning, managing, executing the complete End to End QE activities (Starting from Requirements gathering to QE Sign-off) Open source contributor for ManageIQ, Aeolus, Deltacloud API, Open Stack Well experienced in Designing automation framework using Selenium with Java and Python Possess rich experience in Design, Development and Testing with excellent analytical, problem solving, communication and interpersonal skills. Well aware of working with both Upstream(open source community) and Downstream(Enterprise release) Techno-functional with sound knowledge in management of various activities including development/ testing/ deployment/ configurations/ maintenance of an enterprise wide Operating System, Cloud applications, Middleware application, functional testing, API testing, non-functional testing, UAT, Automation and end-user trainings Experienced in writing/ maintaining test plans, test strategies, test cases, wiki pages and docs for the functionality, installation/ configuration, automation setup and
    [Show full text]
  • Innovation Across the Open Hybrid Cloud Red Hat Summit 2018 Press Conference
    INNOVATION ACROSS THE OPEN HYBRID CLOUD RED HAT SUMMIT 2018 PRESS CONFERENCE Paul Cormier Matt Hicks President, Products and Technologies SVP, Engineering Red Hat Red Hat Ashesh Badani Mike Ferris VP and General Manager, OpenShift VP, Technical Business Development & Red Hat Business Architecture Red Hat RED HAT’S INTENTIONAL 25-YEAR JOURNEY 1993 FOUNDED 2012 $1 BILLION IN REVENUE RED HAT STORAGE RELEASED 1999 IPO FUSESOURCE, POLYMITA & MANAGEIQ ACQUIRED 2002 FIRST RELEASE OF ENTERPRISE LINUX 2013 RED HAT OPENSTACK PLATFORM RELEASED OPENSHIFT ENTERPRISE RELEASED 2006 JBOSS ACQUIRED 2014 INKTANK (CEPH), ENOVANCE (OPENSTACK), 2009 RED HAT VIRTUALIZATION RELEASED & FEEDHENRY (MOBILE) ACQUIRED RED HAT ADDED TO S&P 500 INDEX 2015 ANSIBLE ACQUIRED 2011 2016 $2 BILLION IN REVENUE GLUSTER ACQUIRED OPENSHIFT RELEASED 3SCALE (API MANAGEMENT) ACQUIRED 2017 PERMABIT & CODENVY ACQUIRED COREOS ACQUIRED 2018 $3 BILLION ANNUAL RUN RATE REVENUE RED HAT SUMMIT 2018 NEWS ● REAL ENTERPRISE ADOPTION ● NEW TECHNOLOGY INNOVATIONS TO ADVANCE THE HYBRID CLOUD ● DEVELOPER MOMENTUM ● MOMENTUM ACROSS THE CLOUD-NATIVE ISV AND HYBRID CLOUD ECOSYSTEM THE 3 PILLARS OF RED HAT’S BUSINESS SUPPORTED BY AN ENTIRE TECHNOLOGY ECOSYSTEM We have the Linux We have the leading We have the foundation & the cloud enterprise Kubernetes management & platforms to win hybrid container platform with automation solutions to cloud infrastructure middleware services to make our portfolio sticky win the developer & easier to use WE HAVE THE PARTNER ECOSYSTEM TO WIN OPEN HYBRID CLOUD RED HAT MAKES THE HYBRID CLOUD AND CONTAINER-NATIVE ENTERPRISE A REALITY RED HAT ENABLES TRANSFORMATION ACROSS INDUSTRIES ANNOUNCING: NEW TECHNOLOGY INNOVATIONS TO ADVANCE THE HYBRID CLOUD HYBRID CLOUD INFRASTRUCTURE SUMMIT NEWS & DEMOS NEW - CoreOS INTEGRATION: OPENSHIFT AND RED HAT CoreOS HYBRID CLOUD NEW - OPENSHIFT+OPENSTACK: INTEGRATING HYBRID INFRASTRUCTURE CLOUD INFRASTRUCTURE WITH CLOUD-NATIVE APP DEV Infrastructure software across the 4 footprints, with DEMO - TOOLING AND SERVICES TO MIGRATE FROM VMware RHEL at the very core.
    [Show full text]
  • Connor Penhale Enterprise Software Architect
    Connor Penhale Enterprise Software Architect mailto: [email protected] ​ Open Source & Cloud Evangelist Tel:+13035526680 (mobile) Servant Leader 6421 W 72nd Dr Arvada, CO 80003 Entrepreneur Executive Summary: ● Developing Enterprise Applications utilizing Java EE and Messaging since 2005 ● Fortune 500 Experience: Bank of America, Coca Cola, CVS, Home Depot, Wells Fargo ● Founded Startup in 2014, $150k fundraising, $150k revenue, 5 staff, 13k+ personal man hours Battle-Tested Experience and Deep Technical Acumen: ● Enterprise Integration Patterns, Distributed Computing, and Messaging with technologies like Apache Camel, JBoss / Wildfly, ElasticSearch, JMS, Websockets, REST, Nginx, PostgresSQL ● DevSecOps in the Cloud, on-premise, and in hybrid environments with technologies like OpenShift, Kubernetes, Jenkins, Oauth, Puppet, Ansible, ManageIQ, Foreman, CloudFormation ● Design, Deployment, and Operation of On-Premise Datacenters with technologies like OpenStack, OVirt, Ceph, Cinder, iSCSI, SAN, Hyper Converged Infrastructure, HA, DR Professional Experience: Rogue Wave Software - OpenLogic – Louisville, CO 10/2018-Present Enterprise Architect 12/2012-04/2015 I joined OpenLogic in December of 2012, and got to realize my dream of being an open source evangelist as a full-time aspect of my professional duties. By bringing the white-glove service I perfected at Polycom to customers like Bank of America, Coca Cola, CVS, FirstData, Home Depot, and Wells Fargo, I was able to provide an incredible value to the team, and gain exposure at an architecture level to the best running and most challenging networks of applications in the Fortune 500. I’ve returned to this exciting role to spearhead the roll-out of Rogue Wave Software’s curated Cloud Native stacks. Turnberry Solutions – Englewood, CO 02/2018-10/2018 Java Lead Embedded at Comcast to tackle ETL business requirements through event-driven programming using core Java, Spring Boot, Camel ESB, Kafka, Avro, and other technologies.
    [Show full text]
  • Red Hat Cloudforms 5.0 Provisioning Virtual Machines and Instances
    Red Hat CloudForms 5.0 Provisioning Virtual Machines and Instances Provisioning, workload management, and orchestration for Red Hat CloudForms Last Updated: 2020-08-05 Red Hat CloudForms 5.0 Provisioning Virtual Machines and Instances Provisioning, workload management, and orchestration for Red Hat CloudForms Red Hat CloudForms Documentation Team [email protected] Legal Notice Copyright © 2020 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent.
    [Show full text]
  • Use of Open Source Cloud Technologies to Deliver Modern Public Health Services
    Use of open source cloud technologies to deliver modern public health services Francesco Giannoccaro 29th January 2020 About PHE ► Public Health England (PHE) is an executive agency of the Department of Health in the UK. PHE provide government, local government, the NHS, industry and the public with evidence-based professional, scientific and delivery expertise and support. ► Public Health England was established in 2013 to bring together public health specialists from more than 70 organisations into a single public health service. PHE employee about 5,500 staff, mostly scientists, researchers and public health professionals. ► PHE mission is to protect and improve the nation’s health and wellbeing, and reduce health inequalities. We do this through world-leading science, knowledge and intelligence, advocacy, partnerships and the delivery of specialist public health services. 2 Use of open-source technologies to deliver modern public health services Francesco Giannoccaro - London 2020/01/29 HIGHLIGHT THE AMBITIOUS AND INSPIRING MISSION PUBLIC HEALTH ENGLAND HAS. HOW THIS MISSION ALIGN TO THE OPEN SOURCE VALUES, IN THAT PHE AIMS TO DELIVER INNOVATIVE PUBLIC HEALTH SERVICES TO EVERYONE INDEPENDENTLY HOW RICH THEY ARE, REDUCING HEALTH INEQUALITY. Wide range of public health services PHE deliver a wide range of public health services including • research and scientific publications based on mathematical models such as Spatial Metapopulation Model for transmissible disease (eg Flu/Smallpox), predictive models applied to the Anthrax, inference problem to be able to infer: likely size of outbreak, location of source, spatial extent, etc • pathogen genomics service, based on whole genome sequencing, for pathogen typing, surveillance and outbreak investigation.
    [Show full text]
  • Ansible 2.2 Documentation Release 2.4
    Ansible 2.2 Documentation Release 2.4 Ansible, Inc October 06, 2017 Contents 1 About Ansible 1 i ii CHAPTER 1 About Ansible Welcome to the Ansible documentation! Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s main goals are simplicity and ease-of-use. It also has a strong focus on security and reliability, featuring a minimum of moving parts, usage of OpenSSH for transport (with other transports and pull modes as alternatives), and a language that is designed around auditability by humans–even those not familiar with the program. We believe simplicity is relevant to all sizes of environments, so we design for busy users of all types: developers, sysadmins, release engineers, IT managers, and everyone in between. Ansible is appropriate for managing all envi- ronments, from small setups with a handful of instances to enterprise environments with many thousands of instances. Ansible manages machines in an agent-less manner. There is never a question of how to upgrade remote daemons or the problem of not being able to manage systems because daemons are uninstalled. Because OpenSSH is one of the most peer-reviewed open source components, security exposure is greatly reduced. Ansible is decentralized–it relies on your existing OS credentials to control access to remote machines. If needed, Ansible can easily connect with Kerberos, LDAP, and other centralized authentication management systems. This documentation covers the current released version of Ansible (2.3) and also some development version features (2.4).
    [Show full text]
  • Ansible Everything
    ANSIBLE EVERYTHING From traditional to unorthodox, Ansible for Everything Adam Miller Principal Software Engineer AGENDA AGENDA WHAT WE’RE GOING TO TALK ABOUT TODAY ● What is Ansible? ● Command Line Tooling ● Why on earth would I want to do all the ● Event Based Execution things with Ansible? ● Workflow Automation ● Automation Tool ● CI/CD ● Configuration Management ● Ansible Container ● Provisioning and Systems ● Test-Driven Playbook Development Management ● Ansible Galaxy ● Deployment ● Security Auditing and Compliance ● Application Lifecycle Management ● Ansible Tower ● Orchestration WHAT IS ANSIBLE? QUICK INTRODUCTION WAIT, YOU DON’T KNOW WHAT ANSIBLE IS? Ansible is an automation tool ● Ansible is a simple agentless idempotent task automation tool ○ By default, tasks are executed in-order but we can change that if we want. ● Tasks are performed via modules ● Tasks are grouped together via plays ○ Also via roles, which are reusable sets of plays we can pass variables to ○ A play operates on a set of hosts ● Playbooks can contain one or many plays ● Plays nicely with "traditional" configuration management systems ○ There's even a puppet module! QUICK INTRODUCTION WAIT, YOU DON’T KNOW WHAT ANSIBLE IS? Module: yum Arguments: pkg=bash state=installed $ ansible localhost -m yum -a "pkg=bash state=installed" localhost | SUCCESS => { "changed": false, "msg": "Nothing to do" } ANSIBLE EVERYTHING USING ANSIBLE FOR EVERYTHING WHY WOULD I WANT TO DO THAT? Ansible is a simple automation tool that can: ● Execute tasks on one or many hosts ● Orchestrate
    [Show full text]
  • Brno University of Technology Dialog Editor In
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Digital library of Brno University of Technology BRNO UNIVERSITY OF TECHNOLOGY VYSOKÉ UČENÍ TECHNICKÉ V BRNĚ FACULTY OF INFORMATION TECHNOLOGY DEPARTMENT OF INTELLIGENT SYSTEMS FAKULTA INFORMAČNÍCH TECHNOLOGIÍ ÚSTAV INTELIGENTNÍCH SYSTÉMŮ DIALOG EDITOR IN ANGULARJS FOR MANAGEIQ EDITOR DIALOGŮ V ANGULARJS PRO MANAGEIQ BACHELOR’S THESIS BAKALÁŘSKÁ PRÁCE AUTHOR ROMAN BLANCO AUTOR PRÁCE SUPERVISOR Prof. Ing. VOJNAR TOMÁŠ, Ph.D. VEDOUCÍ PRÁCE BRNO 2016 Abstract The main goal of this bachelor thesis is to design and implement a new solution for a Dialog Editor for the ManageIQ application. The new editor is supposed to be created as a single-page application implemented by using JavaScript library AngularJS and drag&drop technique. The solution should bring more comfortable interface for end users than the current editor does. Abstrakt Hlavním cílem této bakalárské práce je návrh a implementace řešení pro editor dialogů pro aplikaci ManageIQ. Nový editor by měl být vytvořený jako jedno-stránová aplikace vytvořená pomocí JavaScriptové knihovny AngularJS a drag&drop techniky. Řešení mělo poskytnout komfortnější rozhraní koncovým uživatelůn, než nabízí současná implementace. Keywords ManageIQ, AngularJS, JavaScript, HTML, user interface. Klíčová slova ManageIQ, AngularJS, JavaScript, HTML, uživatelská rozhraní. Reference BLANCO, Roman. Dialog Editor in AngularJS for ManageIQ. Brno, 2016. Bachelor’s thesis. Brno University of Technology, Faculty of Information Technology. Supervisor Vojnar Tomáš. Dialog Editor in AngularJS for ManageIQ Declaration Hereby I declare that this bachelor’s thesis was prepared as an original author’s work under the supervision of prof. Ing. Tomáš Vojnar, Ph.D.
    [Show full text]
  • ANSIBLE SERVICE BROKER Deploying Multi-Container Applications on Openshift Todd Sanders John Matthews Openshift Commons Briefing
    ANSIBLE SERVICE BROKER Deploying multi-container applications on OpenShift Todd Sanders John Matthews OpenShift Commons Briefing May 31, 2017 Open Service Broker API Overview ● API working group formed in September 2016, officially announced December; successor to CF Service Broker API ● API defines an HTTP interface between the services marketplace of a platform and service brokers ● Service Broker is the component of the service that implements the Service Broker API, for which a platform's marketplace is a client ● Service brokers are responsible for advertising a catalog of service offerings and service plans to the marketplace, and acting on requests from the marketplace for: ○ Provisioning, binding, unbinding, and deprovisioning ○ Provisioning reserves a resource (service instance) ○ Binding typically generates credentials necessary for accessing the resource or provides the service instance with information for a configuration change ● Platform marketplace may expose services from one or many service brokers ● Individual service broker may support one or many platform marketplaces using different URL prefixes and credentials ● Backed by numerous industry leaders including Fujitsu, Google, IBM, Pivotal, Red Hat, and SAP 2 ANSIBLE SERVICE BROKER Orchestrating OpenShift Services ● Define, extend, and deliver “simple” to “complex” multi-container OpenShift services ● Standardized approach to using Ansible to manage and provision applications ● Leverage existing investment in Ansible roles/playbooks ● Easy management of applications
    [Show full text]
  • Deploying Multi-Container Applications with Ansible Broker
    11.7.2017 Deploying Multi-Container Applications with Ansible Broker Eric Dubé, Senior Principal Product Manager, Red Hat Todd Sanders, Director Software Engineering, Red Hat Agenda Service Catalog and Brokers Live Demonstration Open Service Broker API and High-level Architecture Walkthrough of Provision/Bind of selected services Ansible Broker More Information Ansible Playbook Bundle (APB) Definition Additional information to get you started What’s New and Future Plans Questions Roadmap Review What can we answer for you? 2 Service Catalog & Ansible Broker 3 Why Service Brokers? ☑ Open ticket ☑ Wait for allocation ☑ Receive credentials ☑ Add to app ☑ Deploy app SERVICE SERVICE CONSUMER PROVIDER Manual, Time-consuming, Error-prone, and Inconsistent 4 What is a Service Broker? SERVICE SERVICE SERVICE SERVICE CONSUMER CATALOG BROKER PROVIDER Brokers inform Service Catalog of the Service Classes it can provision Service Consumer only interacts with Service Catalog, the details of the Brokers are largely hidden Creates a process that is automated, standardized, and most importantly consistent 5 Service Broker Concepts CONSUMER: user of service deployed by the catalog/broker SERVICE: an offering that can be used by an app e.g. database PLAN: a specific flavor of a service e.g. Gold Tier SERVICE INSTANCE: an instance of the offering SERVICE SERVICE SERVICE SERVICE CONSUMER CATALOG BROKER PROVIDER PROVISION: creating a service instance BIND: associate a service instance and its credentials to an app 6 Service Catalog Where Services Are Published
    [Show full text]
  • Managing Kubernetes and Openshift with Manageiq
    Managing Kubernetes and OpenShift with ManageIQ Alissa Bonas, Dublin 2015 The stages of containers world Containerizing an app Alissa Bonas @ Cloud Open Dublin 2015 Run a container Alissa Bonas @ Cloud Open Dublin 2015 Run multiple containers Alissa Bonas @ Cloud Open Dublin 2015 Run multiple containers ● Orchestrate containers ● Run many containers on multiple hosts ● Manage a containers based environment Alissa Bonas @ Cloud Open Dublin 2015 Today we’ll focus on Kubernetes OpenShift ManageIQ Alissa Bonas @ Cloud Open Dublin 2015 Kubernetes ● Deployment, scaling and orchestration of containers across clusters of hosts. Developed ● 1.0 release - July 2015 in Go Alissa Bonas @ Cloud Open Dublin 2015 Kubernetes concepts ● Node - a machine that containers run on ● Pod - a group of containers ● Replication controller - ensures there are always X replicas of pods Alissa Bonas @ Cloud Open Dublin 2015 Kubernetes concepts ● Service - a base load balancer that provides traffic to pods ● Namespace - partitioning resources created by users into logical groups Alissa Bonas @ Cloud Open Dublin 2015 OpenShift ● Platform as a service for building and running applications - for developers Developed ● Built on top of Kubernetes in Go ● 3.0 release - June 2015 Alissa Bonas @ Cloud Open Dublin 2015 OpenShift concepts ● Provides additional capabilities ○ application lifecycle ○ routing - extends service ○ projects - extension of namespaces Build Deploy Run Alissa Bonas @ Cloud Open Dublin 2015 Insight and control ● How many containers exist in my environment?
    [Show full text]