Integrated Management of OpenPOWER Converged Infrastructures. Revolutionizing the Datacenter

Transcription

1 Integrated Management of OpenPOWER Converged Infrastructures Marcelo Perazolo, Architect IBM Systems Revolutionizing the Datacenter Join the Conversation #OpenPOWERSummit

2 Converged Infrastructure Systems Traditional Converged Hyperconverged CAGR upwards of 12% 19+ B$ Market Converged and Hyperconverged are accelerating at fast pace, following market demand 2 delivery models: Single-SKU, Reference Architecture Pre-packaged IaaS, PaaS, integrated solutions (Cloud, CloudFoundry, Data Mining, Deep Learning, etc.) OpenPOWER must play key enablement role in landscape 2

3 Management stack OS/Virtualization stack Your logo Single-SKU Converged Offering: PurePower Reserved for Top of Rack Switch Multi-rack support: more Power, Data Virtualization technology: PowerVM Empty / Customer choice Integrated Management PurePower Integrated Mgr S822/S822L Power8 compute nodes SX1710 Mellanox 40Gbps Switches (data) G8052 1Gbps Switches (management) SAN48B-5 Brocade FC Switches (storage) V7000 Fab1 (Gen2) Storage Controller X3550 (x2) management nodes IBM Smart PDUs (4x) & B42 Rack 3

4 Move to a Power-based Hyperconverged offering Lower cost, commodity hardware Manage both x86 and Power equally (key areas / scenarios) Publish and fulfill Reference Architectures with OpenPOWER hardware Leverage a fully-open IaaS stack KVM, OpenStack, Docker, Kubernetes, Ceph, Swift, vxlan, OVS, etc. DevOps delivery model & Open Source applications Your logo Problem: proliferation of management tools, not many fully support Power Users adopt different management tools to perform similar tasks H/W+F/W often isn t fully configured & managed, so Power optimizations might get lost Effective tooling support often drives decision making (i.e. My preferred XYZ tool doesn t work well with Power, so let s buy x86 instead ) Solution: open project & framework to support effective Power management Engage OpenPOWER community to help instrument most popular tools increase Power penetration in the Market 4

5 Operational Management - Approach Your logo DevOps philosophy Big Picture - know w to go Gradual development Pick an area (biggest need first) Identify existing solutions (e.g. OpenStack, DevOps tools) Adopt most popular & strategic Identify value added for Power (minimum: same level as x86) Iterate Expand scope to other areas Example: Monitoring Several tools out t e.g. Nagios, Sensu, Icinga, Zabbix, etc. Plugins for Power support do exist, but: - NOT covered on all popular tools; or - NOT fully enabled for Power HW; or - Multiple uncoordinated hacks Infrastructure as Code CI/CD DevOps Code Build Test Package Release Configure Monitor Develop Deploy Operate 5

6 Big Picture (we ll get t, eventually) Git / Jenkins Ansible MaaS/JuJu Existing Open Source Management / DevOps Tools Docker / Kubernetes Mesos Landscape, Nagios Ganglia Grafana ELK User s choice of existing tools (with tool examples) Operational Management - Incubation: Drivers, Plugins, APIs Extensibility Framework Discovery, Inventory Provisioning, Scaling Compliance, Updates Configuration, Monitoring Remote Access focus/scope OpenStack Runtime Services Nova Neutron Cinder Keystone Other Power-Enabled IaaS Runtime Services LBaaS Workflow Auto-Scale VPNaaS Auth/Athn Horizon Catalog Glance Health Metrics Ceilometer Ceph, Swift Containers etc. Ironic, Heat etc. Delivery Repository Monitoring Repository optional / tactical: direct H/W+F/W management Pre-packaged IaaS framework + upward integration interfaces / plugins Control Plane x86, ppc OpenPOWER Reference Architecture Compute Plane x86, ppc Network Switches 10Gb (D), 1Gb (M) Storage Plane HDD SSD Published reference architectures, Power optimized OpenPOWER compute nodes with large processing power OpenPOWER storage nodes with large amount of disk 6

7 Open Project - Get Engaged! Discussions proposed within OpenPOWER Integrated Solutions Work Group Link: Open Source project kick-off proposed for 2Q or early 3Q16 Goal 1: build extensibility framework Goal 2: build initial ecosystem of Microservices (Tools, APIs, Plugins) for focus area(s) Investigating synergy with existing OpenStack projects & APIs (e.g. Murano/App-Catalog, Horizon, Ceilometer/Monasca, Ironic/Bifrost, Magnum, etc.) We need partners to help us support Power in this framework!!! Scenarios / focus areas Reference Architectures / Power Hardware Model & architecture Ecosystem (widely used DevOps tools to integrate) Contribute plugins to open source Contact: mperazol@us.ibm.com 7

8 Backup 8

9 IaaS / DevOps Tooling Landscape (partial*) * Not an endorsement ; no tools or logos were harmed in the making of this chart 9

10 Open Source - Extensible Model Open Source Community extends with additional management function, capability Interfaces and plugins Existing APIs might be reused (e.g. look at OpenStack projects) Tool providers extend framework with support for their tools Capability provides 1..n Integrator implements 1..n extends Element enables Plugin HW/SW vendors extend framework with support for their products Elements are further specialized as Logical, such as a Power Ubuntu OS, or Physical, such as a NVIDIA GPU HW/SW vendors and tool providers can mix plugins to support their strategic management combinations 10

11 Incubation Example: Monitoring Standard Health API, such as Telemetry API from OpenStack Integration code to configure and feed data into Nagios Capability provides 1..n Integrator implements 1..n extends Element enables Plugin Logical and Physical abstract elements for integrated inventory: OpenPOWER nodes, Power OSs, Power f/w e.g. IPMI, OpenBMC, Redfish, GPUs, FPGAs Pre-packaged and ready to deploy into a reference IaaS stack with OpenStack and Nagios Power-enabled abstract monitoring drivers for IPMI, OpenBMC, Power Linux distros, Syslog, SNMP, etc. (Ceilometer, other services)

12 Building Blocks: Microservices Delivery (a.k.a. AppStore ) View Apps / Bundles Nagios Power Microservices Actions install / open / update / etc. description implements: Capability - probes: x, y, z - events: a, b, c requires: Logical/Physical/etc. integrator: Nagios Nagios Integrator Health Monitoring API Power Plugins Sort / Search by metadata IPMI SNMP Integrated Operational Views by Physical Element Type by Logical Element Type by Capability by Integration Point (contextual services & launch) Follows Docker Container model, w: Layers ~= Images Apps ~= Containers Containers individually sized and controlled Easy to update, curated on a per-layer basis 12

13 DevOps - Incremental Delivery Instrument support for open DevOps provisioning tools e.g. Ansible, Juju, etc. CI/CD Microservices BUILD SHIP RUN Dockerfile Docker Image Docker Container Layers Private Registry Docker Registry Cloud Bare Metal 13

14 DevOps - Delivery Management JSON Defines what services to run, what ports to listen, how things get connected Automatic management of Containers to fulfill your IaaS stack Containers run granular microservices and are sized / managed individually, container bundles an integrated tool set Self-Healing Automatic recovery if t s a problem with one of the containers Self-Updating Makes updates easier, run new version when available, toggle to it + easy to roll-back if t s a problem (toggle back) TBD should we consider Mesos as strategic on a future iteration? 14