Josh Cohen Presented to W3C WSRA WG 6/10/09

1. WS-Management Historical documents Josh Cohen Presented to W3C WSRA WG 6/10/09

2. Origin of WSMAN • In 2003, a group of enterprise customers met with a group of hardware vendors. They demanded an interoperable out of band solution. • At the time, Microsoft was not involved. • At the time, each hardware vendor had different and non-interoperable solutions for out of band scenarios • In-band management made use of CIM data models and HTTP + XML protocols • Out of band was binary protocols like ASF, IPMI or proprietary. There was little in the way of common models • Tools were vendor specific and highly specialized • Implementations were often limited to less than 1MB RAM

3. Out of Band Management Scenarios • No Operating System • Dead Operating System • Set up HW config • Read HW event logs, temp sensors, • Provision new systems • Power Control • Boot device selection • Others… • Goal: Use the same protocol for In band and Out of band

4. Solution • DMTF takes on the problem. SMASH/DASH • Proposal: Web Services Access to CIM Instrumentation • At first, the proposal was essentially laughed out of the room. • In Band App and OS developers did not understand the life of the HW developer. • Given the extreme constraints of HW controllers. XML Web Services were viewed as too heavyweight. They required too much of an abstraction layer to fit the WS architecture to the HW controllers. • Solution: Build a simplified WS Application profile • Make architectural tradeoffs in exchange for support on very limited systems. Find the middle ground between WS, HW and OS/App architectures. • Accepted that we would be committing some sins.

5. Standardization And Specs • Initial proposal generated by AMD, Dell, Intel, Microsoft and Sun. Grew to 13 vendors • Submission to DMTF in 2005 • 4 years and counting... • DSP 226: WS-Management Protocol • DSP 227: WS-Management CIM Binding • DSP 230: WS-CIM Schema • SMASH and DASH provide “wrapper specs” which include • CIM Model profiles (which classes are required) • Protocols for use and option profiles for them

6. Extras

7. Industry Adoption – Product Highlights • AMD OPMA based Hardware • Dell DRAC management card • HP ILO 2007 • Intel vPro Hardware • Broadcom devices • Microsoft Windows Vista, Windows XP,Windows Server 2003 R2 • Microsoft System Center • SAP NetWeaver Administrator • Oracle Enterprise Manager

8. Industry Adoption - Community • Sun “WISEMAN” open source Java • Used by Java Application Vendors • https://wiseman.dev.java.net/ • Microsoft Embedded WS-Management Stack • Available to embedded vendors • OpenWSMAN • Open source C implementation Founded by Intel • Compatible with many CIMOMs • OpenWBEM, Pegasus, others • http://www.openwsman.org/ • OpenPegasus WS-Management Connector

9. At your CIM_Service CIM Native MOF class Win32_Service : CIM_Service { string Caption; string ErrorControl; string Name; string PathName; boolean Started; }

10. Example <s:Envelope> <s:Header> <wsa:To>http://1.2.3.4/wsman/</wsa:To> <wsman:ResourceURI>http://microsoft.com/…/Win32_Service </wsman:ResourceURI> <wsa:Action>http://schemas.xmlsoap.org/ws/2004/09/transfer/Get </wsa:Action> <wsman:SelectorSet> <wsman:Selector Name=“Name">winrm</wsman:Selector> </wsman:SelectorSet> </s:Header> <s:Body/> </s:Envelope>

11. EPR Resource Addressing WS-Management “default” EPR addressing ResourceURI is additional SOAP header Selectors (required only to act as ‘keys’ for multi-instanced resources) Alternative addressing models are used for integration or where appropriate “__cimnamespace“ selector can identify CIMOM namespace <wsa:To> http://myserver/wsman</wsa:To> <wsman:ResourceURI> http://schemas.dmtf.org/wbem/wsman/1/wmi/root/cimv2/CIM_Service </wsman:ResourceURI> <wsman:SelectorSet> <wsman:Selector Name=“Name">winrm</wsman:Selector> </wsman:SelectorSet>