DOCSLIB.ORG

A Guide to Your Cloud-Native Stack Table of Contents

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Guide to Your Cloud-Native Stack Table of Contents A Guide to Your Cloud-Native Stack Table of Contents A Guide to Your Cloud-Native Stack............................................................................................... 03 Orchestration Systems........................................................................................................................ 04 Enhancing the Stack............................................................................................................................ 06 Monitoring................................................................................................................................... 06 Logging.......................................................................................................................................... 10 Distributed Tracing.................................................................................................................... 12 Observability................................................................................................................................ 13 Service Mesh........................................................................................................................................... 14 Conclusion............................................................................................................................................... 16 02 A Guide to Your Cloud-Native Stack Cloud computing has been with us for The cloud-native paradigm is not all well over a decade now, and although its sweetness and light, however; in adoption has been steadily rising over exchange for the considerable benefits it that time, there are many reasons why affords, there is a price to pay in the form the rate of adoption hasn’t been swifter. of increased complexity. Chief among them, might be that organizations don’t necessarily believe Application workloads tend to be highly that a ‘lift and shift’ approach to distributed and often transient in nature, workload migration provides much which makes them all the harder to benefit. manage in a production setting. This hasn’t deterred the proponents of the Organizations want to transform the cloud-native approach though, and a lot way they operate; to be more agile and of effort has been put into the creation responsive, and simply replicating a data of tools, methods, and standards to fa- center in the cloud is not going to bring cilitate running these workloads, and to about that transformation. lower the bar to cloud-native adoption. We call this the ‘cloud-native stack’. Forward thinking organizations are be- ginning to make this transformation, by Defining the cloud-native stack is a bit embracing the cloud-native approach. like trying to nail jelly to the wall! New This is not just about moving software companies, projects, tools, and applications to run on cloud approaches are appearing almost on a infrastructure, but it is also about monthly basis. Trying to keep pace with building applications using the the change is both challenging and time microservices architecture. This makes consuming. But, some things are settled, those applications more resilient and and have become a fact of life. This guide scalable, and more capable of benefiting discusses the nature of the cloud-native from the on-demand, elastic nature of stack, and the choices that make up its the cloud. composition. This guide discusses the nature of the cloud-native stack, and the choices that make up its composition. 03 Orchestration Systems As the cloud-native approach has received the most interest and largest transitioned from a hype, to a level of contributions by the open source maturity that has encouraged community. They are also the most organizations to trust their business widely adopted. with, so too has the technology that characterizes it. Not least, the orchestration element of the stack that Docker Swarm hosts cloud-native applications. The Docker project introduced ‘Swarm Classic’ toward the end of 2015, but In the beginning, with the advent of the quickly replaced it with a more func- Docker container format, there wasn’t an tional ‘in-Engine’ version called ‘Swarm easy way to run containerized Mode’ in the middle of 2016. microservices at scale. The Docker Engine was perfect for local development but trying to wrestle with the intricacies of managing distributed workloads, was Apache Mesos beyond its capabilities. As a basis for hosting cloud-native applications as A platform for pooling the physical or vir- distributed workloads, a system was tual resources of a datacenter, Apache required that allowed applications to Mesos can be used in conjunction with scale easily and quickly. It also needed to ‘frameworks’ (e.g. Aurora, Marathon) for provide resilience in the event of providing the mechanisms for running inevitable failures, support advanced distributed workloads. deployment patterns, and facilitate automation for the delivery of frequent application updates. Kubernetes Though there weren’t any open source, purpose-built orchestration systems to Borrowing and building on the concepts provide these requirements early on, it inherent in Google’s proprietary Borg wasn’t long before a number of new cluster manager, Kubernetes is a very projects materialized to fill the void. popular open source project supported by many influential organizations, such This list is not exhaustive, but does as Google, Microsoft and IBM. represent the contenders that have 04 Orchestration Systems In a relatively short time, Kubernetes into a particular vendor, unless you rely has emerged as the de-facto choice for heavily on the value-add extras that running cloud-native applications. There particular vendors provide. may be many reasons for this, but prime among them is as a result of the many In some ways, it’s like choosing Linux as different organizations that have your preferred host operating system coalesced around Kubernetes, turning it (OS) kernel, and then electing to adopt into a well respected, open, Ubuntu as your preferred OS distribution. community-driven project. In the same way, because Kubernetes is open source, there is a wide choice That’s not to say that Swarm doesn’t available. Currently, there are over 50 continue to play a part in the ecosystem; different Kubernetes distributions from Swarm has a very low entry bar into the a myriad of vendors, each of which has orchestration of cloud-native been independently certified by the applications, and is still a foundational Cloud-native Computing Foundation component of Docker Enterprise Edition. (CNCF) as part of its Certified Kubernetes You’ll also find thatDC/OS , a distributed Conformance Program. operating system based on Mesos, can itself host Kubernetes clusters - One other factor to consider when deter- Kubernetes on Mesos, if you will. mining orchestration system choice, is complexity. There is no doubt that If Kubernetes has won the battle for the Kubernetes (and the other competing hearts and minds of engineering teams platforms) is technically complex, and as the de facto standard choice for requires significant knowledge and skill hosting cloud-native applications, then to operate. Many organizations prefer to we might be excused for thinking that focus on developing the value that char- we’re limited for choice. Whilst it’s true acterizes their business or cause, and to that adopting and investing in the leave the task of running infrastructure Kubernetes platform funnels you into a and operations, to third-parties (at least particular technology, it doesn’t lock you in part). If DIY is your preferred approach, be prepared to make a considerable investment in terms of engineering skills and know-how. 05 Enhancing the Stack Systems like Kubernetes provide a development decisions. significant level of automation that makes orchestrating cloud-native Taking a peek under the hood of our applications possible. These systems applications running in production is no can’t be everything to everybody though, easy task, but there are some techniques and at some point there has to be some and tools that can enhance our cloud-na- delineation in terms of purpose. tive stack. This allows us to begin to Otherwise, we end up creating a crack this difficult problem. functional monster and we start to become more opinionated, with choice Monitoring becoming the inevitable casualty. Monitoring is an operational practice To successfully operate a cloud-native that has been an essential ingredient for stack, it’s necessary to augment the managing the availability of software orchestration system with capabilities applications for a number of years. It’s a that enable us to gain insight into the tried and tested technique for health of the stack. We need to know observing the state of health of a when individual services are ailing, or complete system and has a mature set whether there is unacceptable latency of tools that pre-date the cloud-native between services, or a predetermined era. A lot of these tools are proprietary threshold of failed requests has been but some have been developed using the breached, and so on. open source software model. And we need to know about this health Generally, these tools are agent-based at all levels in the stack; right from the and collect metrics from the host operat- host machines, up to the application ing system and the monolithic services themselves. Tools that enable us applications that run on top of them, us- to observe what’s going on at every level ing ‘probes’. Their architecture is based of the stack,
Load more

Recommended publications
  • Monitoring Container Environment with Prometheus and Grafana
    Matti Holopainen Monitoring Container Environment with Prometheus and Grafana Metropolia University of Applied Sciences Bachelor of Engineering Information and Communication Technology Bachelor’s Thesis 3.5.2021 Abstract Tekijä Matti Holopainen Otsikko Monitoring Container Environment with Prometheus and Grafana Sivumäärä Aika 50 sivua 3.5.2021 Tutkinto Insinööri (AMK) Tutkinto-ohjelma Tieto- ja viestintätekniikka Ammatillinen pääaine Ohjelmistotuotanto Ohjaajat Nina Simola, Projektipäällikkö Auvo Häkkinen, Yliopettaja Insinöörityön tavoitteena oli oppia pystyttämään monitorointijärjestelmä konttiympäristön re- surssien käytön seuraamista, monitorointia ja analysoimista varten. Tavoitteena oli helpot- taa monitorointijärjestelmän käyttöönottoa. Työ tehtiin käytettävien ohjelmistojen dokumen- taation ja käytännön tekemisellä opittujen asioiden pohjalta. Insinöörityön alussa käytiin läpi työssä käytettyjä teknologioita. Tämän jälkeen käytiin läpi monitorointi järjestelmän konfiguraatio ja käyttöönotto. Seuraavaksi tutustuttiin PromQL-ha- kukieleen, jonka jälkeen näytettiin kuinka pystyttää valvontamonitori ja hälytykset sähköpos- timuistutuksella. Työn lopussa käydään läpi kuinka monitorointijärjestelmässä saatua dataa analysoidaan ja mietitään miten monitorointijärjestelmää voisi parantaa. Keywords Monitorointi, Kontti, Prometheus, Grafana, Docker Abstract Author Matti Holopainen Title Monitoring Container Environment with Prometheus and Grafana Number of Pages Date 50 pages 3.5.2021 Degree Bachelor of Engineering Degree Programme Information
    [Show full text]
  • Experimental Methods for the Evaluation of Big Data Systems Abdulqawi Saif
    Experimental Methods for the Evaluation of Big Data Systems Abdulqawi Saif To cite this version: Abdulqawi Saif. Experimental Methods for the Evaluation of Big Data Systems. Computer Science [cs]. Université de Lorraine, 2020. English. NNT : 2020LORR0001. tel-02499941 HAL Id: tel-02499941 https://hal.univ-lorraine.fr/tel-02499941 Submitted on 5 Mar 2020 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. AVERTISSEMENT Ce document est le fruit d'un long travail approuvé par le jury de soutenance et mis à disposition de l'ensemble de la communauté universitaire élargie. Il est soumis à la propriété intellectuelle de l'auteur. Ceci implique une obligation de citation et de référencement lors de l’utilisation de ce document. D'autre part, toute contrefaçon, plagiat, reproduction illicite encourt une poursuite pénale. Contact : [email protected] LIENS Code de la Propriété Intellectuelle. articles L 122. 4 Code de la Propriété Intellectuelle. articles L 335.2- L 335.10 http://www.cfcopies.com/V2/leg/leg_droi.php http://www.culture.gouv.fr/culture/infos-pratiques/droits/protection.htm
    [Show full text]
  • Pentest-Report Prometheus 05.-06.2018 Cure53, Dr.-Ing
    Dr.-Ing. Mario Heiderich, Cure53 Bielefelder Str. 14 D 10709 Berlin cure53.de · [email protected] Pentest-Report Prometheus 05.-06.2018 Cure53, Dr.-Ing. M. Heiderich, M. Wege, MSc. N. Krein, BSc. J. Hector, Dipl.-Ing. A. Inführ, J. Larsson Index Introduction Scope Test Methodology Part 1 (Manual Code Auditing) Part 2 (Code-Assisted Penetration Testing) Hardening Recommendations General Security Recommendations HTTP Security Headers Content Security Policy & Beyond Authentication / Authorization Non-Idempotent Request Protection Transport Security Clients/metrics endpoint API Endpoint Admin GUI Identified Vulnerabilities PRM-01-001 Web: Prometheus lifecycle killed with CSRF (Medium) PRM-01-003 Web: CORS header exposes API data to all origins (High) PRM-01-005 Server: Clients can cause Denial of Service via Gzip Bomb (Medium) Miscellaneous Issues PRM-01-002 Client: Clients leak Metrics data through unprotected endpoint (Low) PRM-01-004 Web: Parameters used insecurely in HTML templates (Low) Conclusions Cure53, Berlin · 06/11/18 1/18 Dr.-Ing. Mario Heiderich, Cure53 Bielefelder Str. 14 D 10709 Berlin cure53.de · [email protected] Introduction “An open-source monitoring system with a dimensional data model, flexible query language, efficient time series database and modern alerting approach.” From https://prometheus.io/ This report documents the findings of a security assessment targeting the Prometheus software compound and carried out by Cure53 in 2018. It should be noted that the project was sponsored by The Linux Foundation / Cloud Native Computing Foundation. In terms of the scope, the assignment entailed two main components as the Prometheus project was investigated through both a dedicated source code audit and comprehensive penetration testing.
    [Show full text]
  • Virtualization/Containerization of the PNNL High Energy Physics Computing Infrastructure
    Virtualization/Containerization of the PNNL High Energy Physics Computing Infrastructure Kevin Fox, David Cowley, Malachi Schram, Evan Felix, James Czebotar, Smith Gary Grid Services Deployed DIRAC Belle2DB Distributed Data Management REST Service System UI Service Gatekeeper Services Payload Service Many development and testing Squid Cache services Postgresql Relational Database Condor CE's FTS3 DIRAC SiteDirector CVMFS Stratum HTCondor cluster Zero Squid Cache One Leadership Class Facility CE's Authorization DIRAC SiteDirector Gums HPC Cluster VOMS Server with multiple VO's SE's BestMan2 Gridftp Backed by Lustre Note to the Sysadmins New methodology for system administration. Cloud Native focuses around what the user cares about most, not what we Sysadmins are used to caring about. Users care about services. Users do not care about machines providing service. Pets vs Cattle analogy. We must unlearn what we have learned. Try and separate pets and cattle to different pools of resource. Our Infrastructure Journey Individual machines Automated provisioning Virtual machines OpenStack Cloud Repo Mirrors Containers Kubernetes Infrastructure Deployed Kubernetes + Docker Engine Prometheus OpenStack + KVM Grafana Ceph CheckMK GitLab ElasticSearch Lustre 389-DS LoadBalancing/HA Cobbler PerfSonar NFS Metric/Log gathering is very important for system problem analysis Current tool stack includes CheckMK Grafana/Prometheus Kibana/ElasticSearch/LogShippers Kubernetes Load Balancers Give users a load balancer to talk to. Back it with multiple instances of the software making up of the service whenever possible. When not possible, make it very quick to redeploy. Deployment Flow Separate Build and Deploy steps. Kubernetes/Docker example: #Build > docker build . -t pnnlhep/condor-compute:2017-09-01 … > docker push pnnlhep/condor-compute:2017-09-01 … #Deploy > helm install --name ce0-compute condor-compute \ –set version=2017-09-01 ..
    [Show full text]
  • Lumada Edge Version
    Hitachi - Inspire The Next December 20, 2019 @ 01:04 Lumada Edge V e r s i o n 3 . 0 Component Component Version License OpenShift Origin v3.7.0-alpha.0 Apache License 2.0 Docker Moby v1.10.0-rc1 Apache License 2.0 golang.org/x/oauth2 20190130-snapshot-99b60b75 BSD 3-clause "New" or "Revised" License golang sys 20180821-snapshot-3b58ed4a BSD 3-clause "New" or "Revised" License Docker Moby v1.12.0-rc1 Apache License 2.0 Go programming language 20180824-snapshot-4910a1d5 BSD 3-clause "New" or "Revised" License hpcloud-tail v1.0.0 MIT License Ethereum v1.5.0 BSD 3-clause "New" or "Revised" License zerolog v1.12.0 MIT License cadvisor v0.28.2 Apache License 2.0 Go programming language 0.0~git20170629.0.5ef0053 BSD 3-clause "New" or "Revised" License golang-github-docker-go-connections-dev 0.4.0 Apache License 2.0 docker 18.06.1 Apache License 2.0 mattn-go-isatty 20180120-snapshot MIT License Docker Moby v1.1.0 Apache License 2.0 cadvisor v0.23.4 Apache License 2.0 docker v17.12.1-ce-rc2 Apache License 2.0 Kubernetes v1.15.0-alpha.2 Apache License 2.0 projectcalico/calico-cni 20170522-snapshot Apache License 2.0 Kubernetes v1.7.0-alpha.3 Apache License 2.0 Kubernetes v1.2.0-alpha.6 Apache License 2.0 Kubernetes v1.4.0-alpha.2 Apache License 2.0 Go programming language v0.2.0 BSD 3-clause "New" or "Revised" License kubevirt v1.7.0 Apache License 2.0 certificate-transparency 1.0.21 Apache License 2.0 kubernetes/api kubernetes-1.15.0 Apache License 2.0 cadvisor v0.28.1 Apache License 2.0 Go programming language v0.3.0 BSD 3-clause "New" or "Revised"
    [Show full text]
  • (PDF) What Can Cloud Native Do for Csps?
    What Can Cloud Native Do for CSPs? Cloud Native Can Improve…. Development Cloud native is a way of approaching the development and deployment of applications in such a way that takes account of the characteristics and nature of the cloud—resulting in processes and workflows that fully take advantage of the platform. Operations Cloud native is an approach to building and running software applications that exploits the advantages of the cloud computing delivery model. Cloud-native is about how applications are created and deployed, not where. Infrastructure Cloud native platforms available “as a service” in the cloud can accommodate hybrid and multi-cloud environments. What are Cloud Native Core Concepts? Continuous Integration DevSecOps Microservices Containers and Deployment Not My Problem Release Once Every Tightly Coupled Directly Ported to a VM Separate tools, varied 6 Months Components Monolithic application incentives, opaque process More bugs in production Slow deployment cycles unable to leverage modern waiting on integrated tests cloud tools teams Shared Responsibility Release Early Loosely Coupled Packaged for Containers Common incentives, tools, and Often Components Focus on business process and culture Higher quality of code Automated deploy without software by leveraging waiting on individual the platform ecosystem components What are the Benefits of Cloud Native? Business Optimization Microservices architecture enables flexibility, agility, and reuse across various platforms. CAPEX and OPEX Reduction Service-based architecture allows integration with the public Cloud to handle overload capacity, offer new services with less development, and take advantage of other 3rd party services such as analytics, machine learning, and artificial intelligence. Service Agility Common services can be shared by all network functions deployed on the Cloud-Native Environment (CNE).
    [Show full text]
  • A Complete Introduction to Monitoring Kubernetes with New Relic the Fundamentals You Need to Know to Effectively Monitor Kubernetes Deployments Table of Contents
    White Paper A Complete Introduction to Monitoring Kubernetes with New Relic The fundamentals you need to know to effectively monitor Kubernetes deployments Table of Contents Introduction 03 Monitoring Kubernetes with New Relic 04 Getting started 04 Exploring clusters with the Kubernetes cluster explorer 05 Benefits of monitoring with the cluster explorer 06 Kubernetes Observability 07 Visualizing services 07 Monitoring cluster health and capacity 07 Correlating Kubernetes events with cluster health 12 Integrating with APM data 13 Integrating with Prometheus metrics 15 Using Prometheus data in New Relic 15 Monitoring logs in context 16 Investigating end-user experience 17 Scaling Kubernetes with Success: A Real-World Example 18 02 A Complete Introduction to Monitoring Kubernetes with New Relic Introduction Before Kubernetes took over the world, cluster adminis- • Automatic scheduling of pods can cause capacity trators, DevOps engineers, application developers, and issues, especially if you’re not monitoring resource operations teams had to perform many manual tasks availability. in order to schedule, deploy, and manage their contain- erized applications. The rise of the Kubernetes con- In effect, while Kubernetes solves old problems, it can tainer orchestration platform has altered many of these also create new ones. Specifically, adopting containers responsibilities. and container orchestration requires teams to rethink and adapt their monitoring strategies to account for the Kubernetes makes it easy to deploy and operate applica- new infrastructure layers introduced in a distributed tions in a microservice architecture. It does so by creating Kubernetes environment. an abstraction layer on top of a group of hosts, so that development teams can deploy their applications and let With that in mind, we designed this guide to highlight the Kubernetes manage: fundamentals of what you need to know to effectively monitor Kubernetes deployments with New Relic.
    [Show full text]
  • TIBCO® Operational Intelligence Hawk® Redtail - Container Edition Installation, Configuration, and Administration Version 7.0.0 November 2020
    TIBCO® Operational Intelligence Hawk® RedTail - Container Edition Installation, Configuration, and Administration Version 7.0.0 November 2020 Copyright © 2011-2020. TIBCO Software Inc. All Rights Reserved. 2 | Contents Contents Contents 2 TIBCO Documentation and Support Services 4 TIBCO® OI Hawk® RedTail - Container Edition Overview 6 Deployment Architecture and Components 7 Hawk Agent 8 Hawk Microagents 8 Hawk Console 9 Grafana 9 Time Series Storage (Prometheus) 9 Apache Zookeeper 10 Query Node 10 Webapp 10 Hardware and Software Requirements 11 Building Docker Images for the Components 13 Running TIBCO OI Hawk RedTail - Container Edition in Standalone Docker Compose Mode 16 Running TIBCO OI Hawk RedTail - Container Edition Containers in Kubernetes Cluster 18 Persistent Volume Claim for TIBCO OI Hawk RedTail - Container Edition Nodes 19 Environment Variables for TIBCO OI Hawk RedTail - Container Edition Components 20 TIBCO® Operational Intelligence Hawk® RedTail - Container Edition Installation, Configuration, and Administration 3 | Contents Configuring Grafana Data Source 36 Administration 39 Administration Tab 39 Adding a User 40 Adding a Role 41 Deleting a User or a Role 43 Configuring a Remote LDAP Server 44 Choosing a License 44 Adding Custom Hawk Plug-Ins to the TIBCO OI Hawk RedTail - Container Edition Agent 45 TIBCO OI Hawk RedTail - Container Edition Programming 47 Legal and Third-Party Notices 49 TIBCO® Operational Intelligence Hawk® RedTail - Container Edition Installation, Configuration, and Administration 4 | TIBCO Documentation and Support Services TIBCO Documentation and Support Services For information about this product, you can read the documentation, contact TIBCO Support, and join TIBCO Community. How to Access TIBCO Documentation Documentation for TIBCO products is available on the TIBCO Product Documentation website, mainly in HTML and PDF formats.
    [Show full text]
  • 5 Real-World Prometheus Monitoring Use Cases.Indd
    5 Real-World Prometheus Monitoring Use Cases. CUSTOMER STORIES 5 Real-World Prometheus rising. Prometheus Microservices built on containers and orchestrated by tools like Kubernetes are helping organizations build, run, and improve software applications much faster than ever be- Monitoring fore. In these new infrastructure stacks, keeping track of what’s happening becomes a Use Cases. new challenge. Good news – modern monitoring solutions help you get the visibility you need to under- stand what’s happening from performance and health, to security. y The Prometheus open-source monitoring toolkit has emerged as a leading solution for providing metrics and monitoring for cloud native applications. y Sysdig, the first unified approach to monitor and secure containers across the entire software lifecycle, delivers enterprise-class data management, scale, and support with Prometheus integration. Read on to learn how five progressive companies are taking advantage of Prometheus with Sysdig to gain a 360-degree view of their modern enterprise applications and infra- structure. Sysdig | REPORT 2 How do you build and operate a large-scale, next-generation platform to provide competitive offerings for online hosting, email and website services that are both secure and high- performance? This online services company turned to the Red Hat OpenShift as the foundation of their cloud hosting business. By offering a simple scalable platform for containers, customers can focus on delivering the best application code possible without the headaches of managing their own infrastructure. But what about visibility into performance? The web hosting firm’s customers bring a wide-range of apps to the platform. This includes modern services built on open-source components, as well as legacy apps brought into the new world of containers.
    [Show full text]
  • Cloud Native Introduction
    Cloud Native Introduction Balaji Ethirajulu Ericsson Internal | 2018-02-21 5G is use case driven Massive MTC Critical MTC Enhanced MBB Fixed Wireless Access Ericsson Internal | 2018-02-21 Mobile data trafficoutlook Global mobile traffic outlook (EB per month) 160 In 2024, 25 percent of mobile 140 data traffic will be 120 carried by 5G 100 networks. 80 60 40 20 x5 Total mobile data 0 traffic is expected to 2014 2016 2018 2020 2022 2024 increase by five times Ericsson Internal | 2018-02-21 5G – Cornerstones and role of open source — Cloud Native / Microservices — Automation — Orchestration — AI and AI driven Policy Ericsson Internal | 2018-02-21 Ericsson Demo’s – Booth 401 — Enabling Edge Cloud. — 5G Automation & Network Slicing — Cloud native 5G Core & Exposure — Cognitive OSS & AI/ML Platform Ericsson Internal | 2018-02-21 Ericsson – Tutorial Highlights — Cloud native Introduction – Balaji Ethirajulu — Cloud native design principles / Architecture – Tamas Zsiros — A Cloud Native Application Design, Opportunities & Challenges – Henrik Saavedra Persson — Cloud native “Dual-mode 5G cloud core” and Network Exposure (Programmability) – Jitendra Manocha — Cloud Container distribution /Distributed cloud - Sampathkumar Santhanakrishnan — Demo – Show the configuration and installation of CCD/k8’S and also show a scaling on a Kubernetes cluster - Sampathkumar Santhanakrishnan and Russ Mahon Ericsson Internal | 2018-02-21 ONS2019 Cloud Native Tutorial Principles & Architecture Tamas Zsiros Ericsson Internal | 2018-02-21 Cloud native values 5G relies
    [Show full text]
  • How to Deploy on AWS from Gitlab
    How to deploy on AWS from GitLab A single application for Lambda, Fargate, EC2, EKS, and ECS 1 What's inside? How can you use GitLab for AWS? » GitLab + Lambda » GitLab + Fargate » GitLab + EKS » GitLab + ECS » GitLab + EC2 Additional AWS functionality in the works Getting started with GitLab » Installing GitLab from AWS Management console » Installing GitLab from AWS Marketplace Benefits of using GitLab for AWS services 2 Introduction Amazon Web Services (AWS) is the de facto leader in the worldwide cloud infrastructure market, accounting for nearly 33% in 2019. As of January 2020, AWS offers nearly 160 global cloud-based products including compute, storage, databases, analytics, networking, mobile, developer tools, management tools, IoT, security and enterprise applications. Millions of customers, including startups, large-scale enterprises, and government agencies rely on AWS cloud services to power their business. Developer tools have a high capacity for driving cloud usage and organizations adopt cloud native application development to take advantage of the power of the cloud computing model. Teams utilize cloud native technologies to build and deploy to a limitless number of cloud services, but with small teams managing microservices written in different languages deployed using separate tools, information silos eventually emerge. Toolchain complexity is a common thread among DevOps teams that are doing cloud native development today. In a 2019 Forrester survey of IT professionals, they found that many software development teams are struggling with managing and integrating multiple tools. In order to leverage AWS services, development teams can through five or more different tools just to deploy code. Teams then have to manage these tools.
    [Show full text]
  • Was Ist Das Eigentlich? Und Was Kann Es?
    Was ist das eigentlich? Und was kann es? Sebastian Dehn Solution Architect Partner Enablement [email protected] Wer bin ich? Worüber reden wir heute? Die Idee hinter OpenShift Wieso, weshalb warum…? Lasst uns über Technik reden! Das wichtigste in Kürze Proof it! Ein kurzer Einblick in die reale OpenShift Welt Q&A Ich beantworte eure Fragen. Habt ihr welche? 3 Wer kennt es nicht? Parts Unlimited Bill - VP IT Steve - CEO Chris - VP AppDev Der Fokus Steve - die Kosten minimieren/Ressourcen effizient nutzen Bill - Modernisierung Infrastruktur & Standardisierung der IT Prozesse Chris - Modern AppDev & Innovative Technologien A consistent container application platform From your data center, to the cloud, to the edge Automated Secure by Network Over-the-air Monitoring Pluggable Multi-tenant operations default traffic control updates & chargeback architecture Bare metal, VMware vSphere, Red Hat Virtualization, Red Hat OpenStack Platform, Amazon Web Services, Microsoft Azure, Google, IBM Cloud CONFIDENTIAL Designator Zeit für Praxis! 8 CONFIDENTIAL Designator Die Technik Was sich unter der Haube versteckt 9 Empowering Zeit für Innovationen! developers to innovate 10 OpenShift enables developer productivity BUILD TEST DEPLOY Self-service Consistent Automated CI/CD Configuration App logs & provisioning environments build & deploy pipelines management metrics CODE REVIEW MONITOR SPRING & JAVA™ EE MICROSERVICES FUNCTIONS LANGUAGES DATABASES APPLICATION SERVICES LINUX WINDOWS* * coming soon BUILD AND DEPLOY CONTAINER IMAGES DEPLOY YOUR DEPLOY YOUR DEPLOY YOUR SOURCE CODE APP BINARY CONTAINER IMAGE DEPLOY SOURCE CODE WITH SOURCE-TO-IMAGE (S2I) Git code BUILD APP Repository (OpenShift) Developer Source-to-Image BUILD IMAGE (S2I) (OpenShift) Builder Image Image Registry Application deploy DEPLOY Container (OpenShift) User/Tool Does OpenShift Does DEPLOY APP BINARY WITH SOURCE-TO-IMAGE (S2I) Application build Binary BUILD APP (e.g.
    [Show full text]