WindowsServer 2016超融合解决方案介绍

1、 Windows Server 2016 Hyper-Converged Solution - Virtual Machines and Software Defined Storage on the Same ClusterWindows Server 2016 Technical Preview introduces Storage Spaces Direct, which enables building highly available (HA) storage systems with local storage. This is a significant step forward

2、 in Microsoft Windows Server software-defined storage (SDS) as it simplifies the deployment and management of SDS systems and also unlocks use of new classes of disk devices, such as SATA and NVMe disk devices, that were previously not possible with clustered Storage Spaces with shared disks. Window

3、s Server 2016 provides a hyper-converged solution by allowing the same set of servers to provide SDS, through Storage Spaces Direct (S2D), and serve as the hosts for virtual machines using Hyper-V. The sameHow to Use this Guide:This document provides both an introductory overview and specific standa

4、lone examples of how to deploy a Hyper Converged Solution with Storage Spaces Direct. Before taking any action, it is recommended that you do a quick read through of this document to familiarize yourself with the overall approach, to get a sense for the important Notes associated with some steps, an

5、d to acquaint yourself with the additional supporting resources and documentation. Hyper-converged Solution with Software Defined Storage Overview In the Hyper-Converged configuration described in this guide, Storage Spaces Direct seamlessly integrates with the features you know today that make up t

6、he Windows Server software defined storage stack, including Clustered Shared Volume File System (CSVFS), Storage Spaces and Failover Clustering. The hyper-converged deployment scenario has the Hyper-V (compute) and Storage Spaces Direct (storage) components on the same cluster. Virtual machines file

7、s are stored on local CSVs. This allows for scaling Hyper-V compute clusters together with the storage its using. Once Storage Spaces Direct is configured and the CSV volumes are available, configuring and provisioning Hyper-V is the same process and uses the same tools that you would use with any o

8、ther Hyper-V deployment on a failover cluster. Figure 5 illustrates the hyper-converged deployment scenario.FIGURE 5: Hyperconverged same cluster configured for Storage Spaces Direct and the hosting of virtual machinesHardware requirementsWe are working with our hardware partners to define and valid

9、ate specific hardware configurations, including SAS HBA, SATA SSD and HDD, RDMA enabled network adapters etc. to ensure a good user experience. You should contact your hardware vendors for the solutions that they have verified are compatible for use with Storage Spaces Direct.If you would like to ev

10、aluate Storage Spaces Direct in Windows Server 2016 Technical Preview without investing in hardware, you can use Hyper-V virtual machines, see HYPERLINK /b/clustering/archive/2015/05/27/10617612.aspx Testing Storage Spaces Direct using Windows Server 2016 virtual machines.For more information about

11、hardware options, see HYPERLINK /b/clausjor/archive/2015/11/23/hardware-options-for-evaluating-storage-spaces-direct-in-technical-preview-4.aspx Hardware options for evaluating Storage Spaces Direct in Technical Preview 4 Note Storage Spaces Direct does not support disks connected via multiple paths

12、, and the Microsoft Multipath MPIO software stack.Example Hardware for this GuideFor simplicity, this guide references a specific set of hardware that we were able to test. This is for example purposes only and most of the steps are not specific to hardware.Where something is specific to hardware, i

13、t will be noted. There are many hardware vendors with solutions that are compatible with the hyper-converged system described in this guide and this hardware example does not indicate a preference over other systems or hardware vendors.Due to limited resources and time constraints imposed by TP5, we

14、 are in a position to offer detailed guidance only for a specific subset of tested hardware configurations at this time.Server: Dell 730XDBios: HYPERLINK eecbuilddropdell 1.5.54HBA: Dell HBA330Firmware: HYPERLINK eecbuilddropdell 7 A00Network Interfaces: Mellanox ConnectX-3 Pro (dual port 10Gb, SFP+

15、) for RoCEv2 networksFirmware: HYPERLINK /support/home/us/en/04/product-support/servicetag/GXKCS22/drivers?rvps=y&s=BSD 0 or newerTop of Rack Switch (TOR) Cisco Nexus 3132BIOS version: 1.7.0Information GatheringThe following information will be needed as inputs to configure provision and manage the

16、hyper-converged system, and therefore it will speed up the process and make it easier for you if you have it on hand when you start:Server Names you should be familiar with your organizations naming policies for computers, files, paths, and other resources as you will be provisioning several servers

17、 with Nano installations and each will need to have a unique server name. Domain name you will be joining computers to your domain, and you will need to specify the domain name. It would be good to familiarize with your internal domain naming and domain joining policies.Administrator Password for th

18、e new servers: When the Nano images are created, the command to create the images will prompt you to input the password for the local administrator account. For RDMA configurationsTop of Rack switch make/modelNetwork Adapter make/model There are 2 types of RDMA protocols, note which type your RDMA a

19、dapter is (RoCEv2 or iWarp)Vlan IDs to be used for the 2 network interfaces used by the management OS on the hyper-converged hosts. You should be able to obtain this from your network administrator. Nano or Full/Core Install OptionsHyper-converged deployments can be done using either Nano or Full in

20、stallations of Windows Server 2016 Preview. Nano is a new install type for Windows Server 2016, see this link for more information on the advantages of using Nano and deploying and managing Nano server. This guide will focus on deploying hyper-converged systems using Nano server and the “Deploy the

21、operating system” section is a step-by-step method of deploying Nano server.However, the steps in the “Configure the Network” and “Configure Storage Spaces Direct” sections are identical whether you are using Nano or full or core installations.For full and core installations, instead of following th

22、e “Deploy the operating system” in this guide, you can deploy Windows Server 2012 Datacenter like you would any other Failover Cluster deployment. This would include joining them to an Active Directory domain and installing the Hyper-V role and Failover Cluster feature and if using RoCE RDMA devices

23、 including the “Data Center Bridging” feature. Nano server installations require all management to be done remotely, except what can be done through the Nano Recovery Console. On Full and core installations you can use the remote management steps in this guide, or in some cases you can log into the

24、servers and do the commands and management locally.Nano: Installing and configuring Hyper-Converged SystemThis section includes instructions to install and configure the components of a Hyper-Converged system using the Windows Server 2016 Technical Preview with a Nano Server configuration of the ope

25、rating system. The act of deploying a Hyper-Converged system can be divided into three high level phases: HYPERLINK l _Deploy_the_operating Deploy the operating system HYPERLINK l _Network_Configuration Configure the Network HYPERLINK l _Configure_Storage_Spaces Configure Storage Spaces DirectFigure

26、 6 illustrates the process for building a hyper-converged solution using Windows Server 2016 Technical Preview. Figure 6: Process for building a hyper-converged solution using Windows Server 2016 Technical Preview.You can tackle these steps a few at a time or all at once, but they do need to be comp

27、leted in the order shown in Figure 6. After describing some prerequisites and terminology, we will describe each of the three phases in more detail and provides examples. Important This preview release should not be used in production environments. Prerequisites and TerminologyThe provisioning and d

28、eployment process for a Windows Server Nano server involves specific steps that include:Creating a bootable .VHDx file for each Nano serverCopying the bootable .VHDx files to a physical host and configuring the host to boot from the .VHDx filesRemotely managing the newly deployed host machines runni

29、ng Nano ServersNote: The Image creation machine and the Management machine (defined below) can be the same machine. The critical factor is that the machine from which you are managing must be of the same version (or higher) as the Nano server that are being managed. For Windows Server 2016 Technical

30、 Preview 5 evaluation we recommend that your Management machine be running WS2016 TP5 so you will be able to efficiently manage the Nano Servers (which are also running TP5).Image creation machine. The instructions in this guide includes creating bootable Nano .VHDx files for each server. Its a simp

31、le process, but you will need a system (Windows 10 or Windows Server 2012 R2 or later) where you can use PowerShell to create and temporarily store the .VHDX files that will be copied to the servers. The cmdlet modules used to create the image are imported from the Windows Server 2016 preview ISO, t

32、he instructions below will have details on this process.Management machine. For the purposes of this document, the machine that has the management tools to remotely manage the Nano servers will be referred to as the Management system. The management system machine has the following requirements:Runn

33、ing Windows Server 2016 Technical Preview 5, domain joined to the same domain or fully trusted domain as the Nano systems.Remote Server Administration Tools (RSAT) and PowerShell modules for Hyper-V and Failover Clustering. RSAT tools and PowerShell modules are available on Windows Server 2016 and c

34、an be installed without installing other features. They are also available by installing the RSAT package for Windows clients.Management system can be run inside of a Virtual Machine or on a physical machine. Requires network connectivity to the Nano serversHost machines. In the example below, the e

35、xpectation is that you start with physical machines that are booted to a Windows Server operating system (full or core). Well be copying the VHDs files to the Host machines and then re-booting into Nano operation system that was created in the VHDx files. Booting from a VHDx file is the method of de

36、ployment being outlined in this guide. Other methods of deploying VHDx boot files can also be used. Deploy the operating systemDeploying the operating system is composed of the following tasks: HYPERLINK l _Acquire_an_ISO Acquire an ISO image of Windows Server 2016 TP5 HYPERLINK l _Use_the_ISO Use t

37、he ISO and PowerShell to create the new Nano Server Images HYPERLINK l _Copy_the_new Copy the new Nano Server images to the Host machines HYPERLINK l _Reboot_into_the Reboot into the new Nano Server image HYPERLINK l _Connecting_to_and Connecting to and managing the Nano Servers from the Management

38、system machineComplete the steps below to create and deploy the Nano Server as the operating system on your Host machines in a Hyper-Converged system. Note: The HYPERLINK /library/mt126167.aspx “Getting Started with Nano Server” guide has many more examples and detailed explanations of how to deploy

39、 and manage a Nano server. The instructions below are solely intended to illustrate one of many possible deployments; you need to find an approach that fits your organizations needs and situation. Acquire an ISO image of Windows Server 2016 TP5 DatacenterDownload a copy Datacenter ISO from to your I

40、mage creation machine and note the path.Use the ISO and PowerShell to Create the new Nano Server ImagesThere are other methods do deploy Nano, but in the case of this example well provide a set of steps below. If you want to learn more about creating and managing different kinds of Nano deployments

41、or images, see the HYPERLINK /library/mt126167.aspx “Getting Started with Nano Server” guide, starting in the section “To quickly deploy Nano Server on a physical server”. NoteIf your deployment isnt using a RoCEv2 RDMA adapter, then you can remove the “-Packages Microsoft-NanoServer-DCB-Package” pa

42、rameter in the PowerShell commandlet string below. Our example hardware for this guide does use RoCEv2 RDMA adapters and Data Center Bridging, so the DCB package is included in the example. NoteIf you are going to manage the servers with System Center, add the following items in the “-Packages” sect

43、ion of the “New-NanoServerImage” commandMicrosoft-NanoServer-SCVMM-PackageMicrosoft-NanoServer-SCVMM-Compute-Package NoteIf you have drivers that are recommended by your hardware vendor, It is simplest to inject the network drivers into the image during the “New-NanoServerImage” step below. If you d

44、ont, you may be able to use the in-box drivers using the OEMDrivers parameter in the “New-NanoServerImage” command, and then update the drivers using Windows Update after deployment. It is important to have the drivers that your hardware vender recommends, so that the networks provide the best relia

45、bility and performance possible.On the Image creation machine, mount the Windows Server Technical Preview .ISO. To mount the ISO, in File Explorer select and right click on the ISO, then choose Mount. Once the mounted drive is opened, navigate to the NanoServerNanoServerImageGenerator directory and

46、copy the contents to a directory to your desired working folder on your Image creation machine where you want to create and store your new Nano Server Images. In this example, the NanoServerImageGenerator directory will be copied to: C:NanoBuildNanoBuildScripts Start Windows PowerShell as an adminis

47、trator, change directory your desired working folder where you copied the “NanoServerImageGenerator” contents to, and run the following command to import the Nano Server Image Generator PowerShell module. This module will enable you to create the new Nano Server images.Import-Module .NanoServerImage

48、Generator Verbose You should see something like this:Copy network drivers to a directory and note the path. The example in the next step will use c:WS2016TP5_Drivers Before using the following PowerShell commands to create the new Nano Server images please read the following section to get an overvi

49、ew of the entire task. Some features, need specific packages to be specified to be included in the “New-NanoServerImage” command below.In this step, you will create a unique image for each Host machine. We need 4 images; one for each physical host in the HyperConverged setup.Creating each Nano Serve

50、r image can take several minutes depending on the size of the drivers and other packages being included. It is not unusual for a large image to take 30 minutes to complete the creation process. Create the images one at a time. Because of possible file collision, we recommend creating the images one

51、at a time. You will be prompted to input a password for the Administrator accounts of your new Nano Servers. Type carefully and note your password for later use. You will use these passwords later to log into the new Nano Servers You will need the following information (at a minimum)MediaPath: Speci

52、fies the path to the mounted Windows Server Preview ISO. It will usually be something like D:TargetPath: Specifies the path where the resulting .VHDx file will be located. NOTE: this path needs to pre-exist before running the new-NanaServerImage cmdlet. ComputerName: Specifies the name that the Nano

53、 server will use and be accessed by. Domain name: Specifies the fully qualified name to the domain that your server will join.DriversPath folder location where the expanded drivers that you want to inject to the image are maintainedOther options: If you want a richer understanding of the all the inp

54、ut parameters associated with New-NanoServerImage you can learn more from the HYPERLINK /library/mt126167.aspx “Getting Started with Nano Server” guide. New-NanoServerImage -MediaPath -TargetPath -ComputerName -Compute -Storage -Clustering -DomainName DomainName -OEMDrivers -DeploymentType Host -Edi

55、tion Datacenter -EnableRemoteManagementPort -ReuseDomainNode -DriversPath -Packages Microsoft-NanoServer-DCB-PackageThe following is an example of how you can execute the same thing in a script:/Example definition of variable names and values$myNanoServerName = myComputer-1$myNanoImagePath = .NanoNa

56、noServerPhysical$myNanoServerVHDXname = myComputer=1.VHDX$myDomainFQDN = $MediaPath = d: $myDriversPath = C:WS2016TP5_DriversNew-NanoServerImage -MediaPath d: -TargetPath $myNanoImagePath$myNanoServerVHDXname -ComputerName $myNanoServerName -Compute -Storage -Clustering -DomainName $myDomainFQDN -OE

57、MDrivers -DeploymentType Host -Edition Datacenter -EnableRemoteManagementPort -ReuseDomainNode -DriversPath $myDriversPath -Packages Microsoft-NanoServer-DCB-PackageWhen you complete this task, you should have 1 VHDx file for each of the four hyper-converged systems that you are provisioningOther Pa

58、ckages that you may want to include:Desired State Configuration. An example feature that requires this is the Software Defined Network feature. The packages to include are:Microsoft-NanoServer-DSC-PackageShielded VMMicrosoft-NanoServer-SecureStartup-PackageMicrosoft-NanoServer-ShieldedVM-PackageMana

59、ging Nano with System Center Virtual Machine Manager or Operations ManagerMicrosoft-NanoServer-SCVMM-PackageMicrosoft-NanoServer-SCVMM-Compute-PackageCopy the new Nano Server images to the Host machinesThe tasks in this section assume that the servers that will be used for the hyper-converged system

60、 (Host Machines) are booted into a Windows Server operating system and accessible to the network.Log in as an Administrator on the Host machines that will be the nodes of the hyper-converged system. Copy the VHDX files that you created earlier to each respective Host machine and configure each Host