© 2005 Global Grid Forum The information contained herein is subject to change without notice Leading the pervasive adoption of grid computing for research and industry GGF14 – OGSA MWS BOF WS-Management John Tollefsrud Sun Microsystems

Agenda Motivation WS-Management introduction Wiseman open source project Announced supplier support

Trends in systems management Distributed environments more common. –Crossing companies, geographies, platforms. Building a common substrate for IT with Web services. –Web services used for: Device discovery and eventing. Single sign on and identity management. Enterprise application integration. Mobile. … Lifecycle support costs growing, eating up more IT budget. –Over $15 Billion in 2004? –80% of IT budgets go to running the business, not innovation* Source: “IT Spending, How Do You Stack Up?”, Gartner, Jan. 2004

Challenges in systems management Consistent management of systems resources Consistent reporting of system failures OS awareness of the hardware state Monitoring DMZ servers and applications Net result – high TCO

Addressing the problem CORE REQUIREMENTS Build to support all sizes of device and application Work in all pre- and post-boot operational environments Provide consistent access across multiple management models Enable management across multiple administrative domains Support access to traditional- & SOA-based applications equally Make it secure, on all devices Tightly align with WS-* arch. Aim for future-proof DevicesClientsServers CPU, NIC… Systems on one computer Distributed service Scale Up & Down on Hardware Scale Up & Down in Software/Firmware Create standard scaleable management protocol Data model neutral Composable protocol stack

What is WS-Management? WS-Management defines a SOAP-based protocol for Systems Management Is a profile – a collection of references to other composable specs –WS-Addressing, WS-Eventing, WS-Transfer and WS- Enumeration Specifies extensions to and restricts how these protocols can be used Designed to scale down to small-devices Defined over existing standards –HTTP/S, TCP/IP, TLS, XML, URI, SOAP Designed to be Model-agnostic –compatible with the CIM Object Model WS-Management First Published: Oct 2004 Authors: AMD BMC Dell Intel Microsoft Sun WBEM Solutions

WS-Management targets typical management operations Typical systems management operations –Get, Put and Delete properties of managed resources –Create references to manageable resources –Enumerate the contents of containers and collections such as large tables and logs –Subscribe to events emitted by managed resources –Execute specific management methods –(Resource Discovery is out of scope in the current version of the spec) Operations are optional in WS-Management and implementations are free to add more

WS-Management Transfer functions Defined by WS-Transfer –Get –Put –Create –Delete Defined by WS-Mgmt –Partial Get –Partial Put –Rename

Enumerating data sources Same as WS-Enumeration specification WS-Management allows using partial results Enumerate EnumerateResponse (Context) Pull(3) PullResponse Pull(4) PullResponse Release ReleaseResponse Client Agent Item Collection

WS-Management Eventing functions Defined by WS-Eventing –Subscribe –Push Subscribe Group Policy Deliver Management Console Server Get Defined by WS-Management –PushWithAck –Batched –Pull

Heartbeats Pseudo-events as part of subscription monitoring Instruction included in wse:Subscribe

Bookmarks Optional capability for Log-backed subscriptions Bookmark is included with each event delivery –Service-defined cursor in the event stream –Opaque to the client Allows a later restart where the subscription left off

Security Profiles Request-reply –wsman:secprofile/https/standard –wsman:secprofile/https/mutual Events –wsman:secprofile/https/standard/userRef –wsman:secprofile/https/mutual/certhash Not an exhaustive list, more profiles could be supported

WS-Management Catalog Lists the available ResourceURIs Provides searchable metadata (Keywords) Provides relationships to external and internal resources (eg Web URLs) Describes supported actions for each resource Can provide the complete WSDL for a resource using WS-Transfer:Get Can provide the XML Schema for a resource using WS-Transfer:Get

Implementation The wiseman project

An open source project by Sun Microsystems Apache License 2.0 Prototype code – not yet product-quality –Developed outside of formal processes –Architecture, APIs can change Proven interoperability Initial Implementation is for Java SE 5+

Wiseman project base technologies Java SE 5+ –Base platform org.w3c.dom –Document, Element, Node, Attributes SOAP with Attachments API for Java (SAAJ) 1.3 –Message, Envelope, Body, Header, Fault Java Architecture for XML Binding (JAXB) 2.0 –XML ↔ Java (based on Schema)

Wiseman handler architecture

Wiseman project to-do’s WS-Management –Fragment-level WS-Transfer –Eventing extensions –Many Faults CIM Mapping WS-Managment Catalog A Simple API for the casual developer Documentation –JavaDoc, FAQ, Developer Guide

Delivering WS-Management Suppliers have announced WS-Management product plans

Sun Microsystems product support for WS-Management Sun announced product support plans: – x64 servers / service processors in 2006 –Solaris –N1 Preso source: Microsoft WinHEC2005

Microsoft Windows Server 2003 “R2” (2005) Supported features –WS-management stack (server and client) –Supports HTTPS – in-band and OOB –IPMI kernel driver (supports version 1.5 or higher) –IPMI provider – subset of CIM IPMI profile –Support for X86, IA64, AMD32/64 –Report SEL events to NT event log –Report BSOD and shutdown to BMC SEL –Remote subscriptions to SEL events OOB (over HTTPS) –Scripting client API (OLE Automation) Limitations –Only subset of classes in IPMI CIM profile supported –Only supports management controllers with KCS interface –Only supports https –No remote discovery of WMI instrumentation Preso source: Microsoft WinHEC2005

WS-Management & Microsoft Operations Manager Windows Server 2003 “R2” –Existing MOM agent can integrate using WS-man scripting interface –Management Packs can be modified to support IPMI Windows Longhorn and MOM V3 –Use of WS-Management for agentless monitoring across firewall –Use of WS-Management for OOB access –Down-level support is planned (Windows Server 2003 SP1 or newer releases) Support out-of-band access for existing BMC –Not included in Windows –Delivery vehicle TBD Preso source: Microsoft WinHEC2005

Windows Longhorn Update (planning in process) Forwarding OS events –Client side monitoring –Forwarding from DMZ servers TCP transport –SOAP framing protocol –Integrated security for Windows to Windows scenarios Full access to and discovery of WMI instrumentation –CIM to XML mapping –Mapping WMI namespaces to Catalog New administration tools in the box –Instrumentation viewer –New Event Viewer Additional h/w management capabilities –Set of additional IPMI profiles for richer h/w management experience Preso source: Microsoft WinHEC2005

Intel AMT Host platform managed through the external interface Intel® AMT accesses sensor and effectors Intel® AMT accesses Host OS and Applications HW FW SEI Providers OS Execution Environment WS-Man Intel® AMT Hardware Application Managed Node Intel® AMT BIOS Network Mgmt Apps & Other consumers Platform Mgmt Agent Capability Modules Intel® AMT WS-MAN for both IB & OOB Preso source: Microsoft WinHEC2005

To Summarize.. based on the Web Service infrastructure, which means –Platform Independence –Same toolset for applications and systems management a common management protocol for the entire stack –Hardware –Operating System –Applications –Services

For more information – – –