IBM SmartCloud Orchestrator Architected for Extensibility


Published on

IBM SmartCloud Orchestrator
Architected for Extensibility

Published in: Technology

IBM SmartCloud Orchestrator Architected for Extensibility

  1. 1. ! Click to add text © 2013 IBM Corporation IBM SmartCloud Orchestrator Architected for Extensibility
  2. 2. © 2013 IBM Corporation Need for End to end Orchestration End to End Automation Automate everything to deliver a production environment: multi node applications, storage, network, change and configuration, … Standardization Deliver “services”: repeatable and controlled processes, auditable, simplified self service consumption, An Open and Flexible Platform Integrate with existing data center, processes and tools. Provide choices to customers that want to avoid a technology lock in - based on Open Standards Provisioning is not enough. Customers need end to end automation to accelerate delivery of IT services, while reducing costs
  3. 3. © 2013 IBM Corporation3 IBM Confidential Why do we need an Orchestrator ? 1.  Customers are looking for end to end automation of cloud service delivery to achieve greater returns 2.  Provisioning play a key role, but is just one of many steps that must be automated 3.  Each customer has unique requirements to integrate with existing data center processes and tools. VM Provisioning Real customer example
  4. 4. © 2013 IBM Corporation Orchestration Engine Network Domain Storage Domain IT ManagementMonitoring Domain Data Availability Domain Compute Domain Monitoring IT Asset Management Service Desk Storage Domain Change Management Provision Pattern Orchestrate Network Domain Workload Orchestration Workload aware placement, optimization and operation Resource Orchestration Onboard, provision, manage CPU, Storage and Network Service Orchestration Manage the lifecycle of business applications DBAppWeb Managing workloads in a Cloud Enabled Data Center requires orchestration
  5. 5. © 2013 IBM Corporation5 What is SmartCloud Orchestration … An open and scalable cloud platform An easy to use orchestrator for cloud service automation A ready to use automation library A marketplace for content sharing and re-use
  6. 6. © 2013 IBM Corporation6 High level architecture SCOrchestrator Automation Engine BPM Process Server Modeling and Admin Image Library VMWare vCenter ICCT Image Creation Self ServiceAutomation Modeling UI IBM Business Process Manager (BPM) IBM Tivoli Monitoring (ITM) KVM Content packages         Composite Patterns Management APISmartCloud Cost Management (SCCM) Cloud User Offering Catalog API Service Desk Account ing Cost Mgmt Network FW/LB Storage File-based Hypervisor Management OpenStack Gateway Amazon EC2 Hybrid Extension OpenStack … *) supported in following releases
  7. 7. © 2013 IBM Corporation7 Zoom in the provisioning engine Virtual   Applica,ons   Hypervisors & IAAS Management SHIM REST  APIs   Self  Service  and  Admin  UI   OpenStack    Shim   Deployment   Virtual   Systems   IAAS Gateway VM   KVMvCenter OpenStack1 ... VM   KVMvCenter OpenStackN Virtual Image Library SCE SCE
  8. 8. © 2013 IBM Corporation8 SCOrchestrator – Content Types §  Software Bundle –  A software bundle contains and describes the software available for use within a virtual image. It includes information about how to install and configure the software, prerequisites of the software, and parameters available for customizing. A software bundle is used during image creation with Image Construction and Composition Tool (ICCT, Part of SCP/SCO) §  Virtual Image –  A Virtual image contains the base operating system and the optional activation code which configures a virtual server which is based on such virtual image. In addition it may also contain one or more software components. §  Pattern (vSys & addOns) –  A pattern is a collection of multiple images, each with optional software components. Patterns are a logical representation of a recurring topology for a given set of deployment requirements such as e.g. a multi-tiered web application comprising of HTTP Server, App Server and DB Server. In this example, each tier would be represented by its own virtual image, which includes configuration scripts to configure the multi-tier application accordingly §  Resource type operations (implemented as BPM workflows) §  Patterns (vApp & TOSCA) –  Patterns to compose workload aware topologies §  Orchestration –  Content for orchestration can be complete ready to use offerings implemented as workflow processes including the corresponding user interface –  … and/or a collection of building blocks to ease the creation of orchestration. These building blocks can be activity implementations, user interfaces, UI widget, … Service Orchestration Manage the lifecycle of business applications Workload Orchestration Workload aware placement, optimization and operation Resource Orchestration Onboard, provision, manage CPU, Storage and Network
  9. 9. © 2013 IBM Corporation Multiple pattern types to enable open ecosystem Virtual Application Patterns • Highly automated deployments using expert patterns • Business policy driven elasticity • Built for the cloud environment • Leverages elastic workload management services Virtual System Patterns • Automated deployment of middleware topologies • Traditional administration and management model • Application and infrastruture driven elasticity Virtual Appliances • Standard software installation and configuration on OS • Images created through extend/ capture • Traditional administration and management model • Infrastructure driven elasticity Virtual Appliance Metadata Software application Operating system Virtual Appliance Virtual Appliance Metadata Application Server Operating system Virtual Appliance Metadata Application Server Operating system Virtual Appliance Metadata HTTP Server Operating system Virtual Application Patterns Virtual System PatternsVirtual Appliances Software application
  10. 10. © 2013 IBM Corporation10 Custom Orchestration Operations § SCO allows definition of custom operations for various orchestration granularities –  Event triggered Actions … used to extend the basic pattern engine capabilities … plug into existing programming flows at predefined plugpoints/events … with defined semantics and data model e.g. Approval (‘pre’), Open firewall port (‘post’), … –  User triggered Actions … used to extend the basic manageability actions of service instances … provide addtl mgmt capabilities for all or specific patterns e.g. Backup, Install SW, Open problem, … –  Service Operations … implementation of service catalog offerings … used for end user customized operations, e.g. deploy pattern, create filesystem, … … used for administrative actions such as datacenter configuration e.g. Register StorageHost, User onboarding, … A B A B C X
  11. 11. © 2013 IBM Corporation11 SCO Custom BPM processes Pattern engine base processing Event triggered actions for typical pattern deployment Resolve Model Define Placement Copy images Configure hypervisor Start VM Execute Config Scripts Notify user Pre-provision Event Pre-VM-start Event Post-provison Post-provision-failed Event                                 Trigger one or multiple custom processes on certain events
  12. 12. © 2013 IBM Corporation12 Orchestration Registry
  13. 13. © 2013 IBM Corporation13 SCO Self-Service Catalog
  14. 14. © 2013 IBM Corporation14 Configuration of Orchestration Actions BPM process which implements the orchestration logic BPM process which implements the end user interface
  15. 15. © 2013 IBM Corporation15 Configuration of Self Service Offerings BPM process which implements the orchestration logic BPM process which implements the end user interface Settings to define the visualization of the offering in the service catalog 1 2 3 1 2 3
  16. 16. © 2013 IBM Corporation16 Approval / Human Tasks
  17. 17. © 2013 IBM Corporation Library of virtual templates, sw packages, script, add on ( disks, network cards, etc) Graphical editor for composing and configuring workloads Creation of patterns Reuse chef recipes from community
  18. 18. © 2013 IBM Corporation Connecting images in a pattern: example
  19. 19. © 2013 IBM Corporation19 Scenario 1 – Speed up business application deployment End User : (1) Access the SCO self service catalog to deploy a new Media Wiki application. Service Designer: (2) Modify the Media Wiki service via the pattern editor. (3) Publish the new service in the catalog
  20. 20. © 2013 IBM Corporation20 Scenario 2 – End to end automation Service Designer: (1) Access the cloud market place and download a storage automation package. (2) Create a new MediaWiki offering which also performs automated storage and network configuration. (3) Publish the new offering in the catalog. End User : (4) Access the catalogue and requests new “Media Wiki”
  21. 21. © 2013 IBM Corporation21 Cloud Marketplace §  Enable customers to rapidly discover and implement cloud solutions §  Enable business partners and ISVs to create value by adding content to IBM cloud solutions §  Enable IBM services and development to rapidly deliver & iterate on capabilities in response to changing customer requirements and integration needs §  Enable collaboration within the ecosystem to accelerate customer value creation Establish cloud platform agility and value by rapidly delivering content (organic & partner ecosystem) using the AppStore model
  22. 22. © 2013 IBM Corporation22 Managing the infrastructure Cloud group1 IWDOpenStack . . . Region 1 Compute node1 Compute nodeX Availability zone1 ... Compute node1 Compute nodeK Availability zoneZ ...... Region n Compute node1' Compute nodeX' Availability zone1' ... Compute node1' Compute nodeK' Availability zoneZ' ...... Cloud groupZ Cloud group1' Cloud groupZ' l  A cloud group represents a pair [Region, availability zone] in OpenStack l  For each cloud group a single hypervisor is assigned despite the number of compute nodes in the availability zone
  23. 23. © 2013 IBM Corporation23 Managing the infrastructure IWDOpenStack . . . Region 1 Compute node1 Compute nodeX Availability zone1 ... Compute node1 Compute nodeK Availability zoneZ ...... Region n Compute node1' Compute nodeX' Availability zone1' ... Compute node1' Compute nodeK' Availability zoneZ' ...... Network1 IP group1 Network2 IP group2 Networkn IP groupn l  For each network in each region a pair [network, IP group] is created in IWD l  Each network in a region is attached to all hypervisors in IWD related to that region
  24. 24. © 2013 IBM Corporation In the beginning, there was the perfect image… Then users starting making changes and “snapshots”… …and what they put in the images is unknown… Then they get copied to multiple locations… …and some change again… Then you need to apply a critical security patch…how? … where? What’s  the  problem  with  Virtualiza,on  and  Standardiza,on?   Managing images
  25. 25. © 2013 IBM Corporation25 Capturing Images is easy l  There are many tool that simplify the process l  All you need is enough space the store them However managing images is hard: l  Standardization l  Search l  Version control l  Drift Detection l  Vulnerability l  Image building Virtual Image Library and Image Construction and Composition Tool help you addressing these issues!
  26. 26. © 2013 IBM Corporation What's new in Virtual Image Library •  OpenStack support –  Ability to federate OpenStack regions –  Ability to use OpenStack Keystone as custom user registry –  In addition, VIL 2.2 exposes OpenStack Glance-compliant REST APIs •  Federating operational repositories across WAN to support geographically distributed data centers –  New Proxy components to decentralize analytics and check-in/out capabilities over distributed sites –  New analytics engine providing better performances when introspecting image contents –  New Reference Repository based on a peer-to-peer network of nodes that build a shared repository –  Firewall-friendly solution to traverse segregated networks •  Improved control over indexing functions –  Canceling queued indexing tasks –  Handling of user-initiated actions at higher priority than the automatically triggered tasks •  Handling OVA images and related metadata
  27. 27. © 2013 IBM Corporation27 What's new in ICCT •  New Cloud Provider for OpenStack –  Possibility to interact directly with an OpenStack instance –  Possibility to interact with the IaaS GW component and the VIL image service exposed through that component
  28. 28. © 2013 IBM Corporation •  Learn more about the IBM SmartCloud Orchestrator •  Join the open development community to get access to SmartCloud Orchestrator • •  Watch the video for a quick overview of SmartCloud Orchestrator •  Learn more about the benefits of cloud orchestration IDC Technology Spotlight on IBM SmartCloud Orchestrator •  Join the IBM SmartCloud Community References