Post on 20-Aug-2020
Revolutionizing the Datacenter
Join the Conversation #OpenPOWERSummit
Integrated Management ofOpenPOWER Converged Infrastructures
Marcelo Perazolo, Architect
IBM Systems
Join the Conversation #OpenPOWERSummit
Your logohere
Converged Infrastructure Systems
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
24/1/2016
Traditional Converged Hyperconverged
CAGR upwards of 12% 19+ B$ Market
Your logohere
Single-SKU Converged Offering: PurePower
34/1/2016
S822/S822L Power8 compute nodes
SX1710 Mellanox 40Gbps Switches (data)G8052 1Gbps Switches (management)SAN48B-5 Brocade FC Switches (storage)
X3550 (x2) management nodes
V7000 Fab1 (Gen2) Storage Controller
Empty / Customer choice
Reserved for Top of Rack Switch
IBM Smart PDUs (4x) & B42 Rack
Integrated
Management
PurePower
Integrated Mgr
Man
agem
en
t st
ack
OS/
Vir
tual
izat
ion
sta
ck
• Multi-rack support: more Power, Data• Virtualization technology: PowerVM
Your logohere
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
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
44/1/2016
Your logohere
Operational Management - Approach DevOps philosophy
Big Picture - know where 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 there…
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”
54/1/2016
DevOps
Code
Build
Test
Package
Release
Configure
Monitor
Infrastructure as Code CI/CD
Develop
Deploy
Operate
Your logohere
Existing Open Source Management / DevOps Tools
Big Picture (we’ll get there, eventually)
64/1/2016
OpenStack Runtime Services
OpenPOWER Reference Architecture
Nova Neutron Cinder
GlanceKeystoneCeph, Swift
Ceilometer
Horizon
Control Planex86, ppc
Compute Planex86, ppc
Size: 2U Size: 2USize: 2U Size: 2U Size: 2U Size: 2U
Ironic,
Heat
Size: 2USize: 2U
Network Switches10Gb (D), 1Gb (M)
Size: 2U Size: 2U
Storage Plane
Size: 2U
HDD
Size: 2U
SSD
Operational Management - Incubation: Drivers, Plugins, APIs
Provisioning,
Scaling
Compliance,
Updates
Extensibility
Framework
Discovery,
Inventory… Remote
Access
Delivery
Repository
Monitoring
Repository
Other Power-Enabled IaaS Runtime Services
LBaaS Workflow Auto-Scale
CatalogVPNaaS Metrics
Health
Auth/Athn
Containers
…etc.
…etc.
Configuration,
Monitoring
OpenPOWER compute nodeswith large processing power
OpenPOWER storage nodeswith large amount of disk
optional / tactical:direct H/W+F/W management
Docker /
KubernetesMesosGit / Jenkins
Ansible
MaaS/JuJu
Landscape,
Nagios…Ganglia
GrafanaELK
User’s choice
of existing tools
(with tool examples)
Pre-packaged
IaaS framework
+ upward integration
interfaces / plugins
Published reference
architectures, Power
optimized
focus/scope
Your logohere
Open Project - Get Engaged ! Discussions proposed within OpenPOWER Integrated Solutions Work Group
• Link: https://members.openpowerfoundation.org/wg/IntSol/dashboard
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
74/1/2016
Your logohere
Backup
4/1/2016 8
Your logohere
94/1/2016
* Not an endorsement ; no tools or logos were harmed in the making of this chart
IaaS / DevOps Tooling Landscape (partial*)
Your logohere
Open Source - Extensible Model
104/1/2016
Element
Capability Integrator
Plugin
extendsimplements
provides
enables
1..n
1..n
Tool providers extend framework with support for their tools
HW/SW vendors and tool providers can mix plugins to support their strategic management combinations
Open Source Community extends with additional management function,capability Interfaces and plugins
HW/SW vendors extend framework with support for their products
Elements are further specialized asLogical, such as a Power Ubuntu OS,or Physical, such as a NVIDIA GPU
Existing APIs might be reused here(e.g. look at OpenStack projects)
Your logohere
Incubation Example: Monitoring
Element
Capability Integrator
Plugin
extendsimplements
provides
enables
1..n
1..n
Standard Health API , such as Telemetry API
from OpenStack
Integration code to configure and feed data into Nagios
Power-enabled abstract monitoring drivers for IPMI, OpenBMC, Power Linux distros, Syslog, SNMP, etc. (Ceilometer,other services)
Logical and Physical abstract elements for integrated inventory:OpenPOWER nodes,Power OSs, Power f/we.g. IPMI, OpenBMC,Redfish, GPUs, FPGAs
Pre-packaged and readyto deploy into a referenceIaaS stack with OpenStackand Nagios
Your logohere
Building Blocks: Microservices
124/1/2016
Nagios PowerMicroservices
descriptionimplements: Capability- probes: x, y, z- events: a, b, crequires: Logical/Physical/etc.integrator: Nagios
install / open / update / etc.
Apps / Bundles
Actions
Sort / Search by metadata
Integrated Operational Views• by Physical Element Type• by Logical Element Type• by Capability• by Integration Point (contextual services & launch)
Delivery (a.k.a. “AppStore”) View
IPMI
Power Plugins
HealthMonitoring API
Nagios Integrator
Follows Docker Container model, where:Layers ~= ImagesApps ~= Containers
Containers individually sized and controlledEasy to update, curated on a per-layer basis
SNMP …
Your logohere
DevOps - Incremental Delivery
134/1/2016
BUILD SHIP RUN
Dockerfile Docker Image Docker Container
CI/CD Microservices
DockerRegistry
PrivateRegistry
Cloud
Bare Metal
Layers
Instrument support for open
DevOps provisioning toolse.g. Ansible, Juju, etc.
Your logohere
DevOps - Delivery Management
144/1/2016
JSON
Defines what services
to run, what ports to listen,how things get connected
Makes updates easier,
run new version whenavailable, toggle to it
1.1
1.2
Automatic management
of Containers to fulfill yourIaaS stack
Automatic recovery
if there’s a problem withone of the containers
Self-Healing Self-Updating
+ easy to roll-back if there’sa problem (toggle back)
Containers run granular microservices
and are sized / managed individually,
container bundles an integrated tool set
TBD – should we consider Mesos as strategic on a future iteration?