Slides
description
Transcript of Slides
© 2005 IBM Corporation
Gerd Breiter ([email protected])STSM, ODOE Technology & Solutions Development
October, 2005
IBM Boeblingen Lab
IBM Dynamic Infrastructure –an Instantiation of IBM’s On Demand Infrastructure Architecture
© 2005 IBM Corporation2
Disclaimer
This presentation contains references to future product plans.
These plans are subject to change without notice and do not represent an IBM commitment.
© 2005 IBM Corporation3
Agenda
1. Introduction
2. The On Demand Infrastructure (ODI) based on SOA
3. Making the ODI real: The IBM Dynamic Infrastructure
© 2005 IBM Corporation4
Introduction
© 2005 IBM Corporation5
An On Demand Business is an enterprise whose business
processes — integrated end-to-end across the company and with
key partners, suppliers and customers — can respond with speed
to any customer demand, market opportunity or external threat.
Business Design
Information Technology Infrastructure
Business and IT processes
Optimizeprocess, resources, and infrastructure
Integratepeople, processes, and information
Extend your reach
Alignbusiness models and strategic objectives
Becoming an On Demand Business
© 2005 IBM Corporation6
Customers Current I/T State
ApplicationServers
Edge Servers / Load Balancer
Web Servers BackendResources
• Today’s infrastructures are largely static•Application layers are tightly bound to physical layers•Deployment of new apps is complex and time-consuming
• Significant under-utilization of distributed servers
•eBusiness scenarios drive 10:1 peak to average utilization ratios
• Significant time required to re-purpose new applications and servers
•Requires intensive manual intervention
•Complexity impedes change mgmt.• No I/T Virtualization
•No application insulation to disruptions in the I/T infrastructure•No seamless systems mgmt across heterogeneous layers
Cluster 1
Cluster 2
HR App
CRM App
© 2004 IBM Corporation7
SAP System Landscape – A Multiplication of Growth
Multiple Environments per mySAP Solution
Basic Platform Environment Separate Systems per mySAP Solution
Different Service Requirements (Availability, Performance, Size)
Cust. Business Apps, ABAP
SAP Business Apps, > 50 MLoC ABAP
SAP Bus. Programs
Business Data
Cust. Bus.Programs
DB-Server
Presentation Clients
High Bandwidth LAN
LAN
Application Servers
DEV
TEST
Pre-PROD
PROD
TRAIN
Business Data, 50 GB - 2 TB
> 3 MLoC C/C++/JAVA, growing
Web browser, Windows GUI, JAVA GUI, HTTP, XML, ...
... and Complexity
© 2005 IBM Corporation8
Customers Desired StateAn Internal Utility is a customer managed strategy that centralizes IT infrastructure to deliver it as services to the business providing flexible computing resources to the business when and where they are needed and accounting based on usage.
An Internal Utility is a customer managed strategy that centralizes IT infrastructure to deliver it as services to the business providing flexible computing resources to the business when and where they are needed and accounting based on usage.
Dev't TrainingTest
Shared Resource Pool
Service Enablement
Data Center Automation
On Demand Services
BWOffice
Calc.
ERP Catia
HR CRM
Da
ta C
en
ter
Vie
wL
ine
s o
f B
us
ine
ss
Vie
w
Value Proposition
Reduces Costs of managing IT through sharing and virtualization of resources
Automates systems management based on best practices
Accelerates deployment of new applications
Increases flexibility of overall infrastructure
Provides internal Accounting on a subscriber base, reporting on SLA conformance and/or autonomic Service Level Management
© 2005 IBM Corporation9
The on demand Infrastructure based on SOA
© 2005 IBM Corporation10
The on demand Operating Environment
Enterprise Service Bus
Business Connections
Mediation, Messaging, Events
Business Function Services
Business Process Choreography
Services
Common Services
User Access
Services
Choreography
Personalization…
Reporting
Custom Applications…
Packaged ApplicationsAdaptation
Business Rules…Interaction Acquired Services
User Interaction
Services
Collaboration
Presentation…
Connectivity…
Application Layer
Utility Management Services
Resource Virtualization Services
Availability Services…Security Services
BillingRatingMetering Services
Server Storage Resource Mapping…Network
Service Level Automation & Orchestration
Workload Services Configuration Services
Peering Settlement…
Infrastructure Services
Problem Management
Metadata Services …
Information Integration
InformationManagement
Services
Information Access
Analytics
Content
BusinessServices
BusinessServices
BusinessServices
BusinessServices
User
BusinessBusiness
Performance Management
BusinessServices
© 2005 IBM Corporation11
The On Demand Infrastructure Service Oriented Architecture
•Components
•Dynamic Deployment and Discovery
•Loose Coupling and Late Binding
•Introspection and negotiation
The need for Standardization•Interoperability vs. Portability
•WS-* Standards for composability and plugability
•Vendor Neutral
•Integration
Relationship to Autonomic Computing•Part of the On Demand definition
•Service level agreement and management
Relationship to Grid Computing•Its not about the type of application, its about the applicability of distributed compute infrastructure technologies
The Utility Compute Model•A services based model
•The ODS, an instantiation of a service offering…a composed resource
•Internal and External Consumption
•Multiple ODSs on a shared infrastructure
© 2005 IBM Corporation12
Defining, Driving and Exploiting Standardization Web Services and SOA
• WSDL• XML Schema • SOAP• WS-Addressing• Web Services Resource Framework (WSRF)
• WS-ResourceProperties• WS-Lifetime• WS-ServiceGroups• WS-BaseFaults• WS-Relationships (to be introduced)• WS-MetaData Descriptor (to be introduced)
• Web Services Notifications
• WS-BaseNotification• WS-BrokeredNotification• WS-Topics
• WS-MetaData Exchange• BPEL4WS• WS-Security• WS-Policy
Resource Models• Common Information Models (CIM)• CIM/Web Service Mapping (WS-CIM)• Common Management Interoperability Profiles• Storage Networking Industry Association (SNIA)• Storage Management Initiative (SMI)
Resource Management• WSDM - Management Using Web Services • WS-Agreement • Resource Allocation and Provisioning
© 2005 IBM Corporation13
Manageable Resources
Fundamental self-managing component within the architecture
– Component implementing standardized manageability interfaces (properties, metadata, and operations)
– Well-defined resource identity and lifecycle
– Model driven definition
– Manageability interfaces expressed with web services (WS-CIM, WSDM, WSRF)
– Focus on appropriate granularity and higher level resource abstractions
– WSDM compliant manageability capabilities (identity, metrics, relationships, correlate-able properties, capability metadata, etc)
© 2005 IBM Corporation14
Service level automation and orchestration Autonomic policy based QoS delivery of the On Demand Infrastructure
QoS attributes are measurable and capturable through SLA’s
QoS attributes are materialized through autonomic managers•Architected according MAPE(K) concept
•Driven by policies which govern their behavior
•Policies are internal directives defined to meet SLA objectives
Key disciplines currently defined•Problem Management
•Security Services
•Workload Services
•Availability Services
•Configuration Services
© 2005 IBM Corporation15
Utility Management Services
All functions necessary to offer IT resources and capabilities as commercial on Demand Services on a subscription and “pay per usage” basis
Tools for creating the offerings the service provider or IT org can provide
Tools for adding business related aspects to offerings
All other services supporting the need for knowledge and management of business implications in an On Demand Environment
•Contracting and Subscription
•Metering
•License Management
•Accounting: Rating and Billing
•Peering and Settlement
•Enrollment and Entitlement
•Reporting
© 2005 IBM Corporation16
Lifecycle of an “On Demand Service”
Offering
Offering Management•T’s & C’s(Ratings, Service Level Objectives,…)•Offering Presentation (e.g. Intranet) Head of IT
SubscriptionSubscription Mgmt•Sign Contract•Accept T’s&C’s
Head of LoB
On DemandService
Instantiation
Production
Termination
End-users
Ideally Automated
Change Management
AccountingRecord
Metering / Rating•Measurement•Rating•Aggregation•SLO conformance…
© 2005 IBM Corporation17
On Demand Infrastructure Summary
Concepts, base principles, and approaches to support the management of the ODOE
Services oriented programming model for IT infrastructure management
Support for ITIL based IT management process automation and transformation
Intended to facilitate alignment of business objectives with the management of IT
Focus on the expression and runtime behavior of manageable resources and their relationship to policy based service level management functions
Standards based definition targeting heterogeneous, distributed configurations
Reuse of existing resource instrumentation and management component implementations
Is meant to support incremental adoption
© 2005 IBM Corporation18
Making the ODI real:
IBM Dynamic Infrastructure
© 2005 IBM Corporation19
X
X
X
IBM Dynamic Infrastructure
X
IBM Dynamic Infrastructure for mySAP Business Suite
StandardUsage
Subscriber/Administrator
GUI
Server Pool
IBM eServer
Provisioning and
Management System
SAP IT LandscapeUtility Management
Services
Metering
Accounting
Rating
Metric Service
Provisioning
Monitoring
SAP System(SAPSID)Base System
Dynamic System
SAPDB
CI MS
...
SAP System
Base System
Dynamic System
DB
CI MS
...
SAP/DB2Product Stack
User
Data CenterModel
WorkflowWorkflowWorkflowA A A
TPM
Ordering
Subscription
Service Level ManagersSLA Mgmt
Mgmt Policies
Dynamic Optimizer
eWLM
TSA
…
Metering
© 2005 IBM Corporation20
IBM Dynamic Infrastructure for mySAP Business Suite - Core Functions
On Demand Service (ODS) instantiation: create and assign a SAP system to a customer– Establish context for this assignment (subscription)
Enable On Demand Service Creation - Modification - Termination– Through orders/service requests
Enable usage of a common resource pool(s) shared across multiple SAP Systems and customers
Enable measurement of resource usage for a customer / rating, accounting, billing
Enable to ensure, track and document SLA compliance for the ODS instances
Virtualization of resources (server, storage, network and SAP application)
Automated Provisioning
Dynamic Provisioning and Workload Management based on SLA‘s
Availability Management
Service Enablement (Utility Management Services) :
Data Center Automation:
Application Infrastructure Management Solution to build and manage SAP On Demand Utilities
© 2005 IBM Corporation21
Architectural Scope for IBM Dynamic Infrastructure for mySAP Business Suite Scenario I: Automated Provisioning and De-Provisioning of SAP Application Server
– Provisioning of additional application servers from pool– De-Provisioning of selected nodes back to pool
Scenario II: Move the SAP Database Server to another (more/less powerful) server – Provisioning of another (more/less powerful) database node– Move DB engine to new node– De-Provisioning of the old database node
Scenario III: Recover from an unplanned outage
Scenario IV: Dynamic and Arbitrated Provisioning and De-Provisioning of SAP Application Server – Policy-based provisioning of additional application servers from pool– Policy-based de-provisioning of selected nodes back to pool
Scenario V: Cost transparency for dynamic SAP infrastructure– Service Level Agreements – Providing metering and billing input– SLA compliance reports
Scenario VI: Automated LPAR reconfiguration
– Load balancing on Application Server and Database Server
– Non-disruptive provisioning / de-provisioning of CPU and memory
Scenario VII: Automated Cloning of an existing SAP system
– Provisioning of servers from free pool
– Provisioning of SAP application content based on existing database image
Scenario VIII: Dynamic LPAR reconfiguration (response time goal)
– Fully transparent load balancing on Application Server and Database Server
– Non-disruptive provisioning / de-provisioning of CPU and memory
Scenario IX: Integration with SAP Adaptive Controller
Scenario X: Automated Provisioning of Storage in a SAN Infrastructure
© 2005 IBM Corporation22
Architecture Requirements
– Design one system which supports all the different flavours and combination of the scenarios
• Ensuring abstraction, encapsulation, modularity of function – Ensure integration into existing customer processes (Enterprise and
Service Provider) – Service Enablement and ITIL compliance
– Ensure extensibility for adaptation to customer environments (support new scenarios and flavours of the solution)
– Ensure integration and plugability and substitutability of IBM and Non-IBM components („Lego Model“)
– Ensure extensibility for different Service Level Managers
– Provide Standard I/F to functions
– Ensure IBM Programming Model and SOA Compliance
– Ensure extensibility and maximum reuse to support other solutions
– Ensure ability to support different solutions in parallel on the same infrastructure
© 2005 IBM Corporation23
IBM Dynamic Infrastructure Componentization Architecture Overview
Components are Installable Units
– Deployment artefact (e.g. ear file)
– Deployment Descriptor
Components contain
– Implementation (code) of specific Manageable Resource(s)
• e.g. Subscription MR, SAP Application Server MR
– MR Service– MR factory, MR registry,
persistency helpers, instrumentations connectors, etc.
– Implementations of provisioning workflows
Orders (XML documents)– contain the buildplan (components and
relationships between them)
– and the data needed for the orchestration and interaction between the components
VirtualizationEngine
© 2005 IBM Corporation24
IBM DI Managed SAP Environment
IBM DIIBM DI Managed WebSphere Environment
Example: IBM DI SAP and WebSphere … a single management infrastructure
WebSphere Application User
WebServerLayer
ApplicationServer Layer
DB ServerLayer
WebSphere XDManagement Domain
EWLM Management Domain
ManagementInfrastructure
Administrator
LDAP NIM
IBM
DI Mgmt
Mgmt
DB
SAP IT Landscape
SAP System(SAPSID)Base System
Dynamic System
SAPDB
CI MS
...
SAP System
Base System
Dynamic System
DBCI DB
...
User
Different types of On Demand Services share same resources, Common set of automated administration tasks
© 2005 IBM Corporation25
Summary
– IBM DI Architecture and Design is build on odOE principles• Ensures abstraction, encapsulation, modularity of function • Ensures ability to support different solutions in parallel on the same
infrastructure• Ensures IBM Programming Model and SOA Compliance• Provides Standard I/F to functions
– Service Enablement Architecture of IBM DI • Ensures extensibility for adaptation to customer environments (support
new scenarios and flavours of the solution) • Ensures architected integration into existing customer processes
– Componentized Architecture with Common components, Support Components and Solution Components • Ensures integration and plugability and substitutability of components
(„Lego Model“)• Ensures extensibility to different solutions• Ensures Extensibility for different Service Level Managers
© 2005 IBM Corporation26
END