"Enabling Commerce Using the Internet” and “Enhancing Collaboration using Web 2.0”
Enabling Self-Management - Proposal for WSDM 2.0 -
description
Transcript of Enabling Self-Management - Proposal for WSDM 2.0 -
1
Enabling Self-ManagementEnabling Self-Management- Proposal for WSDM 2.0 -- Proposal for WSDM 2.0 -
19 Jan., 200519 Jan., 2005
Fujitsu LimitedFujitsu Limited
IBM CorporationIBM Corporation
2
Self-Management ObjectiveSelf-Management Objective
Self-management reduces the cost and complexity of operating and maintaining a heterogeneous and multi-vendor IT infrastructure
Key capabilities Self-configuring Self-healing Self-optimizing Self-protecting
Self-management must manage all type of resources in a consistent manner
Hardware Servers, storage, and network
Software Operating systems, middle ware products, and business
applications
3
Self-management MechanismSelf-management Mechanism Companies targeting self-management establish similar
mechanisms
Those mechanisms could be summarized as:
Basic activity cycle Monitoring Analysis and projection Action
Policy driven, knowledge-based
knowledge& policy
Monitoring Execution
Analysis Adaptation
knowledge& policy
Monitoring Execution
Analysis Adaptation
IBM Fujitsu
4
Standardization Standardization in Self-management Mechanismin Self-management Mechanism
Monitoring Monitoring the load, utilization of resources, and the running states of service
components, and also detecting faults Covered by MUWS 1.0 and MOWS 1.0
Analysis and projection Performed against current configurations by evaluating and determining
compliance with the established policy and SLAs Analysis is also necessary to predict future resource behavior based on
history and projected requirements Not covered by MUWS 1.0 and MOWS 1.0
Unexplored and tough area Lower priority than monitoring and action
Through the standardization of monitoring and action, we can complete “the autonomic loop” in a multi-vendor environment as the first step
Standardization of analysis and projection becomes necessary if we want to share “management knowledge” among autonomic managers as the second step
5
Standardization Standardization in Self-management Mechanismin Self-management Mechanism (con (cont.)t.)
Action Execution of plans derived from analysis and projection
By interacting directly with managed resources E.g., adjust priorities, change allocation of processors, or
change allocation of tasks among processors within a cluster
By communicating with other managers E.g., make provisioning requests to add additional
processors to the cluster Not fully covered by MUWS 1.0 and MOWS 1.0
Standardization is critical for interoperability Particularly actions on managed resources
6
Use CasesUse Cases Use cases based on our experience
Analysis of common administrative tasks at customers’ sites Customers’ requests to our existing management products
Job-level service-level attainment Data center-level service-level attainment Remove a server due to cracking (security violati
on) Applying security patches
7
(#1) (#1) Job Level ManagementJob Level Management Job initiation
The IT business activity manager submits a job, which must be executed so that it satisfies the specified service level (such as response time, availability, etc,).
At a later stage, changes in the operating environment of the job may occur.
Increased number of transactions from web, etc. The resource requirements are recalculated in the
service level attainment loop. The provisioning steps (including resource allocation and
deployment) are triggered (action) as a result of the changing conditions.
The resources are in a ready state for the required components of the job to start, including starting executable resources such as application server or DBMS.
8
(#1-a) Server Provisioning(#1-a) Server Provisioning
LAN
Storage
FC switch
Add a server with consistent reconfiguration of LAN and storage/SAN
Server
HBA
Network Load Balancer
Network switch
LAN
HBAHBA
9
Operations to Add a New ServerOperations to Add a New Server
Storage FC switch
List storage domain (Get FC switch info)
Add storage domain (Configure FC switch, Zoning)
RAID device List storage group (Get RAID group info)
Add storage group (Create RAID group)
Create logical volume
Server Server Power on
Software deployment
Reset server (Reboot server)
Modify software configuration (IP address, etc.)
Start middleware/application
Network Network switch List network domain (Get port info)
Add network domain (Create ports, Add ports to VLAN)
Load Balancer Add SLB configuration (Configure SLB for servers)
Set server IP address (activate server IP address)
Operation: Independent of resource type
10
(#1-b) Storage Provisioning(#1-b) Storage Provisioning
Add a new LUN by adding an HDD to a RAID device in an SAN environment
LAN
Storage
FC switch
Server
HBA
Network Load Balancer
Network switch
HBA
LAN
HBAHBA HBA
11
Operations to Add a Storage LUNOperations to Add a Storage LUN
Storage FC switch
List storage domain (Get FC switch info)
Add storage domain (Configure FC switch, Zoning)
RAID device List storage group (Get RAID group info)
Add storage group (Create RAID group)
Create logical volume
Server Server List server info (Get installed software configuration info)
Modify software configuration (Configure installed software & HBA driver configuration)
Network
<no operation is required for Network>
Operation: Independent of resource type
12
(#2) Data(#2) Data CenterCenter Level Management Level Management Objective
Improve resource utilization while maintaining the SLAs of running jobs
Data center level manager Add new resources to prepare for expected load increases Release surplus resources in order to reduce costs Adjust resources allocated to jobs based on policy
Example: the priority of a job relative to other jobs
Monitoring
Analysis
Analysis and Projection
Action Action
Job Level
Data center Level
Note: ‘Same’ loop operates at different levels.
Monitoring
In the Analysis and Projection phase, information about the available resources and current load, and estimates of the expected future utilization and load are evaluated
13
Operations for Data Center Level ManagementOperations for Data Center Level Management
Operations used for this case is basically the same as those used for job level management
Management capabilities aggregating separate use case scenarios to provide higher order capabilities such as: Workload Balancing
Includes: Server provisioning Storage provisioning Application management and prioritization Resource de-provisioning as loads reduce
More…
14
(#3) Remove a server (Self protecting)(#3) Remove a server (Self protecting)
Remove a server against cracking (security violation)
LAN
Storage
FC switch
Server
HBA
Network Load Balancer
Network switch
HBA HBA
LAN
15
Operations to Remove a ServerOperations to Remove a Server
Network Load Balancer List network group (Get configured IP address info)
Delete server IP address
Network switch List network domain (Get port info)
Delete network domain (Delete ports from VLAN configuration & Shutdown Network ports)
Storage FC switch
List storage domain (Get FC switch info)
Delete storage domain (Shutdown FC port)
Server Server List server info (Get IP address info)
Power off
Operation: Independent of resource type
After those operations, the software on the server may be re-installed using software deployment mentioned in case #1
16
(#4) Apply Security Patches to Servers(#4) Apply Security Patches to Servers
LAN
Server
Network Load Balancer
Network switch
New security patches
Patch Management Server
LAN
Install patches
LAN LAN
17
Operations to Apply PatchesOperations to Apply Patches
Network Load Balancer List network group (Get configured IP address info)
Delete server IP address
Network switch
List network group (Get port info)
Remove network group (Shutdown port)
Server Server Power on (if necessary)
List software image info (Get applied patch info)
Request software deployment (Install/apply patch)
Reset server
Network Network switch List network group (Get port info)
Add network group (Activate port)
Load Balancer Add SLB configuration (Configure SLB for servers)
Set server IP address (activate server IP address)
Storage <no operation is required for Storage>
Operation: Independent of resource type
18
WSDM 2.0 ProposalWSDM 2.0 Proposal
Management operations (“actions”) can be categorized as: Resource type independent operations
Power on/off, Get info, etc. Resource type dependent operations
Create volume, Add port, etc.
Define resource type independent actions As extension to MUWS 1.0
Resource type dependent actions are defined in other/existing standards
Consider those standards to cover important IT resource types Server, Storage and Network
19
Computer System
Consistency with Consistency with Resource Type-Specific StandardsResource Type-Specific Standards
Resource type-specific standards (e.g., SMI-S, SMASH) may define both application interfaces and object models of managed resources
Actions should be consistent with those models and can wrap their interfaces
WSDM
Subsystemmanagement
Subsystemmanagement
Subsystemmanagement
API API API
Agent Agent Agent
Managementconsumer Actions
Resource type-specificstandards
Consistent
20
MUWS 1.0
MOWS
Servermanagement
(SMASH)
StorageManagement
(SMI-S)
NetworkManagement
(?)
No modificationOther/existing specifications
Extension
WSDM 2.0 Structure PossibilityWSDM 2.0 Structure Possibility (Document (Document point of viewpoint of view))
MUWS 2.0
etc.
Resource-type independentmanagement actions
21
WSDM 2.0 Structure PossibilityWSDM 2.0 Structure Possibility(Application point of view(Application point of view))
Managed Elements
Manageability Access Points
Native Access Methods
Remote Access Protocols
CIM Model / Profile
Is transported in
models
Is used by
“WS-CIM”
CIM ServerInfrastructure
WS Server Infrastructure
„SMWG“ Infrastructure
Is used by
Mgmt Apps
Typically local, also remote
Provisioning
Software Lifecycle
Mgmt
Self Protection Function
Others…
Management Applications using WSDMResource specific capabilities provided by WSDM layer.
WSDM exporting mgmt capabilities
CIM Server
22
Open IssuesOpen Issues
Owners of resource type-specific specification - How to keep consistency with them
Server: DMTF SM-WG (SMASH) Storage: SNIA (SMI-S)
Defining scope of management activities Basic functionality: power-on, reset, deploy, configure May be extended to include snapshot, replicate, … (particularly consi
dering servers) Actions related to deploy and configuration
GGF CDDLM’s basic service APIs Deploy actions may be issued not to managed resources (target serv
ers) but managing resources (deployment management servers) Manageability of components of “composite” resources
Software-managed virtual servers (e.g. VMware, Java VM) Cascading configuration, e.g. a NAS server and underlying RAIDs
23
ReferenceReference
Foster I., et al: The Open Grid Services Architecture, Version 1.0. GGF OGSA Working Group (OGSA-WG). Draft 19, 2004.
Treadwell, J. (ed.) Open Grid Services Architecture Glossary of Terms. GGF OGSA-WG. Draft 7, 2004.
24
Thank you!Thank you!