Standards Support and Interoperability in Windows Server 2012 : Networking , Management, and Storage

1. WSV308 Standards Support and Interoperability in Windows Server 2012: Networking, Management, and Storage Jeffrey Snover Distinguished Engineer and Lead Architect for Windows Server Microsoft Corporation

2. In the past, Windows Server has been a great OS for a server and its devices

3. Windows Server 8 is a great OS for lots of servers and the devices connecting themwhether they are physical orvirtualwhether they are on-premise or off

4. A CloudOS Must Support Standards • Traditional job of an OS is to abstract underlying hardware • CloudOS extends this to abstract the underlying datacenter • Servers, Storage, Networking, Power Distribution Units, … • Standards are the HAL of the datacenter

5. What this means for you • Standards allow us to build a datacenter plug-n-play model • Purchasing products which support standards mean they’ll “just work” • Minimize the software • Minimize the steps • Minimize the systems integration • Minimize the risk • We do the work so you don’t have to

6. Storage Standards and Interoperability in Networking See-Mong Tan Principal Program Mangaer Windows Networking

7. Standards in Networking • There is no area in Windows more dependent on standards than Networking • Standards are required for Interoperability • Networking exists in a multi-vendor marketplace • Multiple standards bodies impact networking

8. Microsoft Confidential Windows Networking PrinciplesA Standards-based Approach

9. WS2012 Networking Standards in the Hybrid Cloud

10. From IPv4 to IPv6 Windows has robust in-box and standards-compliant support for IPv4 and IPv6. IPv6 support was introduced in Windows XP SP3, and was available by default starting in Windows Vista. Fully-featured support includes IPsec and DHCPv6 Windows is IPv6 Ready, certified by independent 3rd party testing to be compliant with IPv6 standards.

11. Standards in NIC Teaming Switch independent team • Switch independent mode • Doesn’t require any configuration of a switch • Protects against adjacent switch failures • Switch dependent modes • Generic or static teaming • IEEE 802.1ax teaming • Also known as LACP or 802.3ad • Requires configuration of the adjacent switch Hyper-V Extensible Switch LBFO Frame distribution/aggregation Failure detection Control protocol implementation NIC 3 Switch dependent team Network switch NIC 1 NIC 2

12. Data Center Bridging on Windows Server 8 Windows Server 8 QoS Application Application Application Application PowerShell WMI Winsock File I/O API Traffic Classification Windows Network Stack Windows Storage Stack Up to 8 classes kRDMA DCB LAN Miniport

13. Remote DMA (Network Direct, SMB2-Direct) • RDMA reduces system overhead by enabling the NIC to transfer data directly to/from memory, removing the need to copy data between memory and data buffers in the operating system and offloading the network stack to hardware • Storage traffic demands higher throughput with lower CPU utilization • SMB2-Direct uses new kRDMAcapability if the NICs present support RDMA • HPC’s Network Direct feature is now in Windows Server 8 for low latency, high speed application-to-application data transfer • Initial testing with SMB2-Direct saw • CPU utilization drop by almost 2/3rds • File access latency now approximates local storage • //BUILD/ Server keynote: 2 Gbytes/sec through <1% CPU

14. Networking Standards Summary • Networking wouldn’t work without standards; the Internet as we know it wouldn’t exist • Our guiding principles are based on standards • Standards permeate our work in the hybrid cloud • Deperimeterization and end-to-end security through IPsec • LACP for NIC teaming • DCB for QOS to the Top of Rack switch • RDMA for low latency, high bandwidth storage with SMB Direct

15. Call to Action • Migrate to IPv6: Windows 8 and Windows Server 2012 are IPv6 ready • Deploy DirectAccess: Now easier to deploy in WS2012 • Move to continuous availability: NIC teaming is used in 75% of servers and now natively supported inbox in WS2012 • Get cheaper storage: SMB Direct in WS2012 is a low cost alternative to SANs with comparable performance

16. Management Standards and Interoperability in Management Wojtek Kozaczynski Principal Architect Windows Server Management

17. Standard-Based Management • There is no management interoperability without a standard interface and protocol • Without them we end up with a proprietary agents, protocols and clients • Complicates deployment and maintenance • Consumes additional resources • Increases the security exposure

18. What (infrastructure) Standards? • DMTF standards • CIM => interface semantics • WS-Man => protocol • CIM Schema => standard resource definitions • OData • RESTful protocol

19. Design Objectives • One management infrastructure spanning Windows and non-Windows • One programming model that simplifies instrumenting Windows and non-Windows resources • PowerShell to manage standard-compliant,Windows or non-Windowsresources • OData for non-Windows clients that want to manage Windows resources

20. Benefits for Two Communities Greatley simplified managment interface definition and implementation PowerShell to manage Windows and non-Windows . . . . . IT Pros Developers of managed services and devices OData to manage Windows

21. One Managment Infrastructure • New WMI provider API (MI) with extended PowerShell semantics • Open Management Infrastructure (OMI) for Linux and Unix with the same MI provider API • Full implementation of WS-Man on Windows and Linux/Unix • New MI client with integrated PowerShell layer PowerShell MI Client API .NetMI API Native MI API non-Windows Windows WS-Man Protocol Handler v1 Provider MI Provider v1 Provider MI Provider Classical Provider MI Provider any device OMI WMI WS-Man Protocol Handler WS-Man Protocol Handler WS-Man ProtocolHandler WS-Man

22. OMI • Open Source WBEM server implemented by Microsoft • Portable • Small footprint • Scalable • High performance • Includes WS-Man protocol stack • Interacts with MI client and PowerShell out-of-the-box • Uses the same MI provider interface as WMI • Can share provider development tools with WMI

23. OMI vs. OpenPegasus

24. WMI + WinRM MI Provider v2 Provider v2 Provider v2 Provider • WS-Man as the primary/default protocol • Greatly simplified provider development, registration and testing . . . . . . PowerShell v1 Provider MI Client API CIM Client APIs v1 Provider v1 Provider Classic Provider .NetMI API WMI Engine Native MI API Client WS-Man Protocol Handler Server WS-Man Protocol Handler Client (D)COM Protocol Handler Server (D)COM Protocol Handler Local + Remote Local + Remote

25. PowerShell Client • Built on top of MI client stack, including session management • Extended WMI provider semantics (-WhatIf, -Confirm, -Verbose) • CIM Cmdletscorrespond to generic CIM operations • CIM-Based Cmdletsgenerated at run time from CDXML CIM-to-PowerShell mapping file PowerShell CIM-Based Cmdlets CIM Cmdlets CIM Client APIs MI Client API .NetMI API Native MI API WS-Man Protocol Handler

26. OData For REST Clients non-Windows REST Clients • Declarative dispatching to PowerShell • Uses PowerShell to CIM mapping • CIM Cmdlets can be used to access WMI • Scripts can be used to build higher-level OData abstractions Management OData Service Dispatching Layer PowerShell CIM Module Service Module CIM Module Service Module Module CIM Module MI Client WMI or OMI CIM Client WS-Man Protocol Handler

27. Management Interoperability Hardware  Windows Linux

28. Demo Windows Server 2012 Win8 VM Linux VM BrodcomBMC 3 2 1 PowerShell IntelBMC Windows managing non-Windows via WS-Man 1 Windows managing Linux running OMI 2 non-Windows managing Windows via OData 3

29. The End Result • Almost half of the 2,400 PowerShell Cmdlets are CIM-Based • PowerShell can access any device that exposes its management interface via WS-Man • Any client implementing WS-Man protocol can manage Windows (no agents required) • OData can be used to manage Windows from any client • OMI can run anywhere (network switches, storage devices, motherboards, …)

30. Call to Action • Buy servers that support DMTF management profiles • Buy storage that supports SNIA management profiles • If you are developing devices or drivers that run in/with Windows, like network devices, implement standards-based management for them • If there are no management standards in your domain, join DMTF and create them

31. Storage Standards and Interoperability in Storage Gene Chellis Director of Program Management Windows Server Storage & Availability

32. Standards & Interoperability in StorageDe Jure and De Facto Standards • Storing and retrieving data is the essence of interoperability • It’s also pretty important to keeping customers happy  • Microsoft has a long history of interoperability in storage • Industry-leading protocol documentation and licensing • Active engagement in plugfest and interop events

33. NFS InteroperabilityNetwork File System remote file protocol • Microsoft has shipped an NFS v3 server and client since 1999 • Services for Unix (SFU) versions 1 to 3.5 • Included in Windows Server 2003 R2 as Microsoft Services for Network File System • NFS server and client in Windows Server 2008 and 2008 R2 • Windows Server 2012 NFS v3 server with Active On continuous availability • Windows Server 2012 includes a new NFS v4.1 server • RFC 5661 compliant • Highly competitive performance and scalability • Bakeathons, Connectathons, UNH lab • Sponsorship of University of Michigan open source NFS v4.1 client development • Windows Server 2012 NFS server (v2, v3, v4.1) and client (v2, v3) tested with: • Fedora14, Fedora15, Fedora16 • RHEL 6.1, RHEL 6.2 • SUSE 11.3 • CentOS 5.5 • OpenSolaris10 • Oracle Solaris 11 • Ubuntu 10.10 • FreeBSD 8.1 • OSX 10.6.5 • AIX 7.1 • HPUX 11 • UMICH • OpenText • Ganesha • VMware ESX4, VMware ESX5 • ONTAP8.0.1

34. iSCSI InteroperabilityNetwork connected remote block storage protocol • Microsoft has shipped an • iSCSI initiator since 2003 • iSCSI target since 2006 • iSCSI initiator • Included in Windows Vista, Windows Server 2003 • Native in Windows 7, Windows Server 2008, Windows Server 2008 R2 • iSCSI target • First released in Windows Unified Data Storage Server 2003 (WUDSS) in 2006 • Available with Windows Storage Server 2008 • Included in Windows Storage Server 2008 R2 • Available as free download for Windows Server 2008 R2 • Windows Server 2012 includes iSCSI Target with Active On continuous availability iSCSI Initiator(s) Normal storage access through Node A Client automatically reconnects to Node Band application IO continues 1 Failover of iSCSI Target connections to Node B 3 2 Clustered iSCSI Target Node A Node B

35. SMB InteroperabilityServer Message Block remote file protocol 2011 SNIA CIFS/SMB/SMB2 Plugfest • Sponsored by Microsoft since 2008 • >27 companies and organizations • >50 platforms and products • >110 test engineers and developers • Representation from 5 continents • Published documentation • CIFS/SMB draft spec in 1997 • SMB 1.0 documentation in 2002 • SMB 2.0 documentation in 2006 • Microsoft patent maps on microsoft.com/openspecifications • Interoperable SMB-based products • Enterprise storage systems • NAS devices, printers • Implementations such as Samba, Likewise used by many other companies • One of Microsoft’s most active licensing programs • SMB 3.0 industry adoption • Preliminary documentation published 9/2011 • EMC, NetApp support announced • Samba working on support • Others …

36. SMI-S InteroperabilitySNIA Storage Management Initiative Specification • In the past, Windows storage management was based on VDS • Storage vendors needed to create VDS providers for specific hardware • Microsoft joined the SNIA SMI-S technical working group in 2010 • Windows Server 2012 includes new Storage Management Provider (SMP) model • New WMI-based class structure for managing heterogeneous storage • Single Windows API for applications and management software • PowerShell commands simplify end-to-end storage management, remote administration and scripting • Converged support for both WMI and standards-based SMI-S SMI-S Example

37. video demo Heterogeneous Storage Management with SMI-S SMI-S Demo

38. More Information • Microsoft Open Specifications • microsoft.com/openspecifications • Microsoft Openness • microsoft.com/openness • Interoperability Bridges • www.interoperabilitybridges.com

39. SIA, WSV, and VIR Track Resources #TE(sessioncode) Talk to our Experts at the TLC Hands-On Labs DOWNLOAD Windows Server 2012 Release Candidate microsoft.com/windowsserver DOWNLOAD Windows Azure Windowsazure.com/ teched

40. Resources Learning TechNet • Connect. Share. Discuss. • Microsoft Certification & Training Resources http://northamerica.msteched.com www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers http://microsoft.com/technet http://microsoft.com/msdn

41. Complete an evaluation on CommNet and enter to win!

42. MS Tag Scan the Tag to evaluate this session now on myTechEd Mobile

43. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.