Offene Standards für Cloud Plattformen

Transcription

1 Offene Standards für Cloud Plattformen Peter Rossi, IBM Schweiz

2 Agenda 1. Merkmale Definitionen einer Cloud 2. Private Clouds, Hybrid Clouds, Public Clouds 3. IBM Cloud Computing Referenz Architektur 4. Offene Standards und deren Motivation Weshalb Standards und Open Cloud -Was gibt's für Initiativen OpenStack Details OASIS / TOSCA Cloud Foundry 5. Kundenbeispiele -Private Cloud Projekte 2

3 Agenda 1. Merkmale Definitionen einer Cloud 2. Private Clouds, Hybrid Clouds, Public Clouds 3. IBM Cloud Computing Referenz Architektur 4. Offene Standards und deren Motivation Weshalb Standards und Open Cloud -Was gibt's für Initiativen OpenStack Details OASIS / TOSCA Cloud Foundry 5. Kundenbeispiele -Private Cloud Projekte 3

4 Cloud ein neues Verbrauchs- und Liefermodell und repräsentiert die industrialisierte Lieferung IT-unterstützter Dienstleistungen Cloud ist: ein neues Verbrauchsund Liefermodell, inspiriert durch das Internet Cloud Services Cloud ermöglicht: Self-service Sourcing Optionen Economies-of-scale Cloud Computing Model Cloud repräsentiert: Die industrialisierte Lieferung IT-unterstützter Dienstleistungen Verschiedene Cloud Typen existieren: Private, Public und Hybrid Workload und/oder Programming Model Spezifisch 4

5 Beobachtungen zu den Cloud Computing Definitionen Es gibt keine einheitliche Definition, aber einige wiederholt auftretende Punkte: - Bezug übers Netzwerk (Wolken-Symbol) - geteilte Ressourcen - Selbstbedienung / ohne Provider-Interaktion - dynamisch / schnell / near instantaneous - on demand / flexibel / elastisch / skalierbar - measured service / pay as you go - IaaS, PaaS, SaaS Definition von NIST als Orientierungspunkt ABER: Cloud Computing sollte nicht nur als Technologie- oder IT-Infrastruktur- Thema betrachtet werden. Und es geht nicht nur um eine 'Verlagerung ins Web'. - Cloud Computing ist nicht nur ein Computing Modell sondern ein Service Delivery Modell. - Das volle Potential von Cloud Computing entfaltet sich erst, wenn die zugrundeliegenden Konzepte auch in den anderen Bereichen eines Business gelebt werden. - Cloud Computing eröffnet neue Möglichkeiten für Innovation im Bereich Service Delivery. 5

6 Agenda 1. Merkmale Definitionen einer Cloud 2. Private Clouds, Hybrid Clouds, Public Clouds 3. IBM Cloud Computing Referenz Architektur 4. Offene Standards und deren Motivation Weshalb Standards und Open Cloud -Was gibt's für Initiativen OpenStack Details TOSCA Cloud Foundry 5. Kundenbeispiele -Private Cloud Projekte 6

7 Cloud Service Optionen und Modelle Delivery Model Onsite Local shore Nearshore Off- Asset Ownership Client Mixed Cloud Provider Datacenter Topology RZ I Client RZ II Client RZ I Client RZ II IBM RZ I IBM RZ II IBM RZ I IBM RZ II Service Type BPaaS SaaS PaaS IaaS BPaaS SaaS PaaS IaaS BPaaS SaaS PaaS IaaS BPaaS SaaS PaaS IaaS IaaS PaaS SaaS BPaaS Cloud Adoption Traditional Private Shared Hybrid Charging Model Fixed Fixed - Variable Pay-as-you-go 7

8 Cloud Deployment-Modelle Business Business Mgmt (HR, Finance,...) Product & Service Develop. Business Model Supply Chain Marketing & Sales AfterSales & Services Provider Integrator Consumer Business Operation IT Solutions Collaborative Solutions Applications & Data Operational Solutions IT Infrastructure Analytical Solutions... Architecture Service Model Enterprise data center Enterprise data center Enterprise Enterprise A B A Users B Business of IT IT Business Mgmt (HR, Finance,..) Customer, Demand & Service Mgmt IT Operation Appl. Dev., Maint. & Support Business Model for IT Infra. Dev., Operation & Support Private cloud Managed private cloud Hosted private cloud Deployment Model Shared cloud services Public cloud services Provider Integrator Consumer 8

9 Es gibt ein Spektrum von Lieferoptionen für Cloud-basierte Dienste. Öffentliche-, private- bis hin zu Hybrid-Modellen Private Hybrid Cloud infrastructure is operated solely for an organization, may be managed by the organization or a third party and may exist on premise or off premise. Cloud infrastructure is a composition of two or more clouds (private, community, or public). Public Cloud infrastructure is made available to the general public and is owned by an organization selling cloud services. Enterprise data center Enterprise data center Enterprise A Enterprise B A Users B Private cloud Deplyoment Models Managed private cloud Third-party operated Off Premises Shared Off Premises Dedicated On Premises Utility Hosted private cloud Managed Operations Third-party hosted and operated Shared cloud services Public Cloud Services Public cloud services Freely accessible Register online Credit card payment Click to contract On Premises Traditional IT Private Cloud Services 9 Fixed Mixed Financial Models Variable

10 Service-Modelle Business Business Mgmt (HR, Finance,...) Product & Service Develop. Business Model Supply Chain Marketing & Sales AfterSales & Services Provider Integrator Consumer Business Operation IT Solutions Collaborative Solutions Applications & Data Operational Solutions IT Infrastructure Analytical Solutions... Architecture Service Model Enterprise data center Enterprise data center Enterprise Enterprise A B A Users B Business of IT IT Business Mgmt (HR, Finance,..) Customer, Demand & Service Mgmt IT Operation Appl. Dev., Maint. & Support Business Model for IT Infra. Dev., Operation & Support Private cloud Managed private cloud Hosted private cloud Deployment Model Shared cloud services Public cloud services Provider Integrator Consumer 10

11 Service-Modelle mit unterschiedlicher Zuständigkeit und entsprechend unterschiedlichem Service-Bezug Traditional On-Premises Infrastructure as a Service Platform as a Service Software as a Service Applications Applications Applications Applications Data Data Data Data Runtime Runtime Runtime Runtime Middleware Middleware Middleware Middleware O/S O/S O/S O/S Virtualization Virtualization Virtualization Virtualization Servers Servers Servers Servers Storage Storage Storage Storage Networking Networking Networking Networking Client Managed Vendor Managed Service Standardization (faster & cheaper) 11

12 Cloud Architektur Business Business Mgmt (HR, Finance,...) Product & Service Develop. Business Model Supply Chain Marketing & Sales AfterSales & Services Provider Integrator Consumer Business Operation IT Solutions Collaborative Solutions Applications & Data Operational Solutions IT Infrastructure Analytical Solutions... Architecture Service Model Enterprise data center Enterprise data center Enterprise Enterprise A B A Users B Business of IT IT Business Mgmt (HR, Finance,..) Customer, Demand & Service Mgmt IT Operation Appl. Dev., Maint. & Support Business Model for IT Infra. Dev., Operation & Support Private cloud Managed private cloud Hosted private cloud Deployment Model Shared cloud services Public cloud services Provider Integrator Consumer 12

13 Agenda 1. Merkmale Definitionen einer Cloud 2. Private Clouds, Hybrid Clouds, Public Clouds 3. IBM Cloud Computing Referenz Architektur 4. Offene Standards und deren Motivation Weshalb Standards und Open Cloud Was gibt's für Initiativen OpenStack Details OASIS / TOSCA Cloud Foundry 5. Kundenbeispiele -Private Cloud Projekte 13

14 Evolution der Cloud Computing Reference Architecture (CCRA 3.5) February 2011 Submitted CCRA to The Open Group April 2011 Public Cloud RA whitepaper available on ibm.com July 2011 Released CCRA 2.0 for Business Partners 2012/13 CCRA Standardization ongoing October 2010 Used in Cloud Launch and various customer/analyst sessions March 2009 Initiated CCAB SC CCMP Reference Architecture March 2010 Published CC & CCMP Reference Architecture 1.0 March 2011 Release CCRA 2.0 Early 2012 Release CCRA 2.5 Reach milestone of ~1500 IBMers formally educated on the CCRA November 2012 Release CCRA 3.0 Adoption Patterns Prescriptive guidance on IaaS/PaaS/CSP/SaaS October 2013 Release CCRA 3.5 Adoption to additional requirements from the market like Big Data, Analytics and Mobile Defined overall architectural foundation Added product-and integration focused solution architectures 14

15 CCRA: Architektur Diagramm 15

16 Cloud Computing Referenz-Architektur -Allg. Drilldown 16

17 Rollen Business Business Mgmt (HR, Finance,...) Product & Service Develop. Business Model Supply Chain Marketing & Sales AfterSales & Services Provider Integrator Consumer Business Operation IT Solutions Collaborative Solutions Applications & Data Operational Solutions IT Infrastructure Analytical Solutions... Architecture Service Model Enterprise data center Enterprise data center Enterprise Enterprise A B A Users B Business of IT IT Business Mgmt (HR, Finance,..) Customer, Demand & Service Mgmt IT Operation Appl. Dev., Maint. & Support Business Model for IT Infra. Dev., Operation & Support Private cloud Managed private cloud Hosted private cloud Deployment Model Shared cloud services Public cloud services Provider Integrator Consumer 17

18 Cloud Computing Rollen (Übersicht) - Was ist Ihre Rolle? Cloud Service Consumer may act as a Cloud Service Provider may include Service Providers offer services based on a management infrastructure. They may also develop services. Service Providers can build their services by (optionally) consuming services provided by other service providers. Service Providers can host services developed by other service developers (on top of their own services) Cloud Service Developer 18 Consumer Business Manager Business / financial (e.g. approval) responsibility for consumed services Accounted for used services instances Consumer Administrator Consumer End User Uses service instances provided by service provider Requests service instances and changes of service instances (typically on behalf of Consumer Business Manager ) Provides access to services for service users Service Business Manager Offers all types of services (SPI) developed by service developer Accounts services consumers for services potentially offered by service provider themselves and services offered on behalf of service developer div. weitere Service Operations Manager Manages technical infrastructure required for providing cloud services Service Transition Manager Service Security Manager Responsible for ensuring that the Service Provider appropriately manages risks associated with development, delivery, support and use of services Responsible for enabling a consumer to use the cloud service, incl. boarding, integration, and process adoption Designs, implements, and maintains service templates (technical aspect)

19 Agenda 1. Merkmale Definitionen einer Cloud 2. Private Clouds, Hybrid Clouds, Public Clouds 3. IBM Cloud Computing Referenz Architektur 4. Offene Standards und deren Motivation Weshalb Standards und Open Cloud -Was gibt's für Initiativen OpenStack Details OASIS / TOSCA Cloud Foundry 5. Kundenbeispiele -Private Cloud Projekte 19

20 Motivation für und Vorbehalte gegenüber Open Source und Open Standards Vendor Lock-In vermeiden / Interoperabilität Verbesserte Qualität Bessere Resistenz gegen / schnellere Abwehr von Cyber-Bedrohungen Schnellere / flexiblere Technologie-Weiterentwicklung Transparenz der Code-Basis Kosten??? Nicht volle Kompatibilität zu proprietärer Standard-Software Kein garantierter After-'Sales' Service Höhere Einstiegshürde Im Cloud-Bereich scheinen uns die Punkte Interoperabilität, Transparenz und Entwicklungs-Dynamik wichtig. Namentlich wegen der allgemein angestrebten Interoperabilität kommen Open Standards Hand in Hand mit Open Source - leider z.t. noch konkurrierend. 20

21 Offene Architekturen verbreiten sich OAuth TOSCA cloudfoundry.org OSLC Built on open technologies Hardware 21

22 IaaS Standards Die Entwicklung von IaaS zu einer dynamischeren Software definierten Umgebung Value Simplified & standardized management Agile infrastructure Understanding & programming workloads Capability Embedded analytics Workload-aware optimization Integrated security & governance Workload definition Orchestration Optimization Resource Abstraction, Optimization & Security Software Defined Compute Software Defined Storage Software Defined Networking Hardware 22

23 OpenStack Foundation OpenStack is a global collaboration of developers & cloud computing technologists working to produce an ubiquitous Infrastructure as a Service (IaaS) open source cloud computing platform for public & private clouds. Platinum Sponsors Exponential growth in 1 YR APR Contributors 2600 Individuals APR Contributors Individuals Gold Sponsors Maximum of 8 Guaranteed board seat Responsible for committing full-time resources Provide significant portion of funding Maximum of 24 Gold Members elect 8 to represent on Foundation board Provide funding and pledge strategic alignment to the OpenStack mission 23

24 OpenStack Infrastructure Management Software The framework for IBM Software Defined Infrastructure SD Infrastructure APIs Services and Resources Server, Storage and Network Broad Ecosystem Forming SD Infrastructure Services Software Image Services Infrastructure Patterns VM Placement Intelligence OpenStack API IBM Differentiation provided via extensions and value added services Cinder Nova Neutron Vendor Led Scalable Model Drivers provided by the vendors Broad Ecosystem Forming Management standardization drivers drivers drivers SVC ESX Hyper-V KVM OpenFlow v7000 EMC PowerVC XEN DOVE Storage Server Network 24

25 OpenStack components Nova OpenStack Compute Provision and manage large networks of virtual machines Glance Imaging Service Image registration and (optional) storage Swift Object Storage Scalable, redundant http-based put/get object store Horizon Dashboard End-user self-service portal and administrative interface Cinder Block Storage Block storage service, create/clone/manage volumes Neutron Network Network-connectivity-as-a-service, provision and manage L2 networks Ceilometer Monitoring / Metering Extendable statistics and metering service Keystone Identity Unified authentication system, integrates with existing systems Heat Orchestration Combines resources into a running cloud stack 25

26 Wer schreibt am Code für OpenStack? 26

27 OASIS TOSCA - Topology & Orchestration Specification for Cloud Applications cloudfoundry.org TOSCA Cloud Operating Environment Services & Composition Patterns API & Integration Services datastore mobile middleware Services security ops dev Traditional Workloads Traditional Workloads Workload definition, Optimization, & Orchestration Hardware Software Defined Environment Software Defined Compute Resource Abstraction & Optimization Software Defined Storage Software Defined Networking 27

28 Founding members of the TOSCA 28

29 TOSCA vereinfacht den Cloud Ansatz durch die Entkopplung von Infrastruktur und Inhalten TOSCA The Topology & Orchestration Specification for Cloud Applications (TOSCA) will enable compose once & play anywhere management of cloud infrastructure topologies. TOSCA provides: A structural model for cloud services, components & relationships A process model for build & management plans A packaging specification for cloud services & related artifacts OASIS Forms TOSCA Technical Committee to Advance Open Standard for Cloud Portability Established Jan 2012; Co-chairs: CA Technologies & IBM 29

30 TOSCA Übersicht Standardizes a language for describing The structure of Cloud services (aka Topology ), including their components and relationships between components The manageability behavior of Cloud services (aka Orchestration ) In the form of plans based on the BPMN 2.0 standard Declarative model reaching from application components to virtual and physical infrastructure Topology Orchestration 30

31 TOSCA im Detail Topology and Orchestration Specification for Cloud Applications A language for defining Service Templates including a Topology Template describing the structure of a service Relationship Template Service Template Topology Template type for Properties Node Types Capabilities Requirements Interfaces Scripts Installables Definition of building blocks for services along with the implementation artifacts for manageability operations type for Images and the definition of deployment artifacts for components Node Template including the definition of plans for orchestrating the application Plans Properties Relationship Types Interfaces Definition of possible links between components Packaging format (CSAR) for packaging models and all related 31 artifacts. Cloud Service ARchive (CSAR)

32 Beispiel - Import und Einsatz vom SugarCRM TOSCA Archiv PHP Module DependsOn SugarCRM App ConnectsTo SugarCRM DB (1) Import TOSCA archive HostedOn HostedOn HostedOn Apache Web Server MySQL HostedOn HostedOn OS-Apache HostedOn OS-MySQL HostedOn (2) Locate or generate plug-ins (3) Import pattern and bind to plug-ins Virtual Application Pattern VM-Apache VM-MySQL SugarCRM as OASIS interop case implemented by System Plug-ins More information on TOSCA TOSCA TC Home: TOSCA Committee Specification Draft 2: 32

33 Erfolgreiche Demonstration der TOSCA Portabilität October 15-16, Luxembourg Private demos of SAP CRM, ERP and Mobile application portability Slides, videos: Participating Companies: Design Tools Service Designer Workload Deployer Cloud Monitoring Other cloud optimization tools Service Marketplaces ISM Cloud Marketplace SAP HANA Marketplace Cloud Managers FlexFrame Orchestrator Cloud Services Telco Cloud Solution Cloud Orchestrator Supported Clouds 33 Different partner cloud orchestration engines & tools interpreting and seamlessly deploying, running and monitoring the same TOSCA service templates on different clouds.

34 Hong Kong, November 5-8, 2013 OpenStack Heat Team stimmt einer Vereinbarung zu TOSCA s new Simple Profile zu unterstützen. Adopt a model which allows HOT->TOSCA and TOSCA->HOT transformations (or just adopt TOSCA), - Heat Software Orchestration design session, OpenStack Design Summit, HK IBM, Red Hat, SAP, Fujitsu, HP have been working to create a Simple Profile of TOSCA in YAML that aligns with OpenStack Heat project, public draft target February (session notes) Independent TOSCA efforts from Summit: NFV has ACCEPTED TOSCA to be a candidate for NFV data model. The proposal of using TOSCA as data model in NFV has got support from operator community including AT&T and Centurylink. CloudCycle, an extensible cloud mgmt. system with a security policy framework Built on OpenTOSCA. Targets small/medium public sector agencies needing secure cloud services Canonical Juju, Configure, manage, maintain, deploy and scale efficiently on any cloud Discussions underway to align TOSCA and Juju as an open source project. 34

35 CloudFoundry Platform as a Service cloudfoundry.org TOSCA Cloud Operating Environment Services & Composition Patterns API & Integration Services datastore mobile middleware Services security ops dev Traditional Workloads Traditional Workloads Workload definition, Optimization, & Orchestration Hardware Software Defined Environment Software Defined Compute Resource Abstraction & Optimization Software Defined Storage Software Defined Networking 35

36 Cloud Foundry Community Eine offene Plattform als Service Lösung um schneller und einfacher zu entwickeln, testen, und implementieren TOTAL CONTRIBUTORS 1,191 Average per month 2013 average: mo average: 98 Lifetime average: 58 LINES OF CODE WEEKLY PULL REQUESTS 604k COMPANIES COMMUNITY PRIORITIES Established a Cloud Foundry Governance Structure Name an advisory board of 5-8 founding members Expand the governance structure to support the broad partner ecosystem ADVISORY BOARD Feedback on the Cloud Foundry roadmap Advise on daily operations, community assets Guidance on the Cloud Foundry charter: scope, definition of cloud profiles ADVISORY BOARD MEMBERS 9 members: IBM, Piston, CenturyLink, Intel, Pivotal, ActiveState, Stark & Wayne, Canonical, Cloud Creedo 36 Technology Achievements New Lighting Fast CLI Loggregator High Availability Elastic Runtime v2 Service Broker API 1-way API instead of 2-way Service Brokers can now be apps CentOS / RHEL compatible Community Achievements Community Advisory Board forum meetings Open Dojo program Public story trackers Open Inception process Incubation process AdminUI Spiff Diego Contribution guidelines

37 Was ist Cloud Foundry? Eine offene Plattform als Service Lösung um schneller und einfacher zu entwickeln, testen, und implementieren Das System unterstützt mehrere Frameworks, mehrere Anwendungsinfrastrukturen und die Bereitstellung auf mehreren Clouds 37

38 Languages / Frameworks / Service Multi-Language Ruby, Java, Scala, Node.js, Erlang, Python, PHP,... Multi-Framework Rails, Sinatra, Spring, Grails, Express, Lift,... Multi-Services MySQL, Postgres, MongoDB, Redis, RabbitMQ,... Multi-Cloud, Multi-IaaS Public Cloud, MicroCloud, Private Cloud 38

39 CloudFoundryArchitektur CF Kernel Internal 39

40 Services in der IBM Bluemix Plattform basierend auf CloudFoundry Runtimes Liberty for Java Node.js Ruby Bring Your Own Buildpack Dev Ops Data Management Services Monitoring and Analytics Git Hosting Deployment Automation Web IDE Agile Historian Development MQTT SQL Database JSON Database Mongo DB MySQL PostgreSQL BLU Data Warehouse MapReduce Mobile Services Push CloudCode Mobile App Mgmt Mobile Quality Assurance Mobile Data Twilio Web & App Application 40 Data Cache Session Cache Elastic MQ Decision SSO Redis RabbitMQ Log Analysis

41 DevOps on Bluemix Fully integrated environment for deploying and managing your application Single Dashboard Single view of application health, usage and status Health and Monitoring Integrated monitoring and diagnostics with the ability to add on features such as code level tracing Scaling Ability to scale the application by adding new runtime instances 41

42 Das gesamte Bild External ecosystems around open source platforms OAuth Open data services Open API communities Open source for undifferentiated service fabric OpenShift cloudfoundry.org Open source utilities provide access to developer communities Add-on services based on popular open source software TOSCA Hardware OSLC Software Defined Compute Resource Abstraction & Optimization Software Defined Storage Software Defined Networking Based on an Open & Ecosystem rich approach 42

43 Agenda 1. Merkmale Definitionen einer Cloud 2. Private Clouds, Hybrid Clouds, Public Clouds 3. IBM Cloud Computing Referenz Architektur 4. Offene Standards und deren Motivation Weshalb Standards und Open Cloud -Was gibt's für Initiativen OpenStack Details OASIS / TOSCA Cloud Foundry 5. Kundenbeispiele - Private Cloud Projekte 43

44 1. Beispiel eines Schweizer Kunden - Software Defined Network Customer: MSP in der Schweiz Situation: Neues Data Center Project Lead: IBM / Business Partner Business Driver: - Flexibler Netzwerk Service - Schnelle Netzwerk Bereitstellung - Wartung und Fehler reduzieren - Kosten senken Background: - Keine befriedigende SDN Lösung am Markt verfügbar - MPLS VPN im Data Center zur Kundentrennung Network Services - Transparent Hosting - Secure Hosting (firewall) - Multiple Optional Services (LB, IPS, etc.) - Shared Services (management, backup, etc.) 44

45 Projekt Umfang und Ziel: Automatische End to End Netzwerk Bereitstellung im Data Center Web Portal Other Service Management tools Orchestration Network Automation API IP Address Management Network Monitoring Other systems MPLS VPN: Cisco routers ( ) Cisco switches (few hundreds) 45

46 Herausforderungen IP Addresses IPv4 / IPv6 / Overlapping IPs Provisioning Multiple devices / Provisioning order Roll-back and Error handling Data Center Geo-redundant Customers Demanding industry High SLA expectation Mehr als nur script Automation 46

47 Die Lösung mit IBM Cloud Orchestrator und Netcool Configuration Manager - Integration Details Self-Service UI in ICO ICO Workflow Engine ICO Toolkit for NCM Offer service provisioning to admins and operations Gather input from UI, enrich with information stored in DB, call actions from toolkit Execute network services (with parameters) Network Service Manager API Abstraction layer of NCM features, expose service templates via REST API Netcool Configuration Mgr. Parameterized config templates for particular device types Configure network devices & check compliance for multi-vendor networks with routers, switches, firewalls, loadbalancers,... 47

48 2. Beispiel eines Schweizer Kunden Workflow Orchestrierung der bestehenden Umgebung Customer: Versicherung Situation: Ablösung bestehender Workflow Lösung Project Lead: IBM Business Driver: - EOL bestehende Lösung - Automatisierte Service Bereitstellung - Wartung und Fehler reduzieren - Kosten senken Background: - Alte Lösung nur script basiert - Keine state full Lösung am Markt erhältlich - Kein Fireandforgetmöglich Services - Integration in bestehende Service Management Umgebung - AD Integration - Event Management Bi-Direktional - Plattform Services 48

49 Herausforderungen Verschiedene interne Bereiche Jeder Bereich hat seine eigenen Anforderungen und Lösungen Verschiedene Automations-Lösungen bereits vorhanden Integration der bestehenden Lösungen End to End Sichtweise Verschiedene Prozessschritte für die unterschiedlichen Lösungen Komplexe interne Prozesse Abbilden der internen Prozesse in den Workflows Mehr als nur script Automation 49

50 Architektur der Lösung mit dem IBM Cloud Orchestrator Presentation Layer Business Layer ICOrchestrator Integration Layer Integration Toolkits Automation Layer LDAP Toolkit Management Systems Service Now update invoke Business Process invoke Snow Toolkit WebSphere Toolkit Puppet Toolkit Scripting Toolkit invoke SCCM Puppet... Managed Applications SCCM Toolkit Managed Platforms Omnibus, Impact invoke update Persistence Toolkit Omnibus Toolkit Managed IT Infrastructure Configuration Layer CMDB 50

51 Die Verwaltung von Workloads über den Lebenszyklus erfordert Orchestrierung Data Compute Availability Domain Domain Storage Monitoring Domain Domain Network Domain IT Management Monitoring Storage IT Asset Domain Management Network Change Domain Management Orchestration Engine Web App DB Service Desk Provision Pattern Resource Orchestration Onboard, provision, manage CPU, Storage and Network Workload Orchestration Workload aware placement, optimization and operation Service Orchestration Manage the lifecycle of business applications 51

52 Fragen? 52

53 Peter Rossi Cloud Solution Architect