A deployment method, apparatus, device, and storage medium

Abstract

This invention discloses a deployment method, apparatus, device, and storage medium. The method includes: an MDT server acquiring domain controller server information, management server information, network server information, storage server information, and compute server information; the MDT server deploying the domain controller server, management server, network server, storage server, and compute server based on the aforementioned information; the MDT server creating a management cluster to which the management server belongs, and establishing a VMM server on the management cluster, so that the VMM server creates a network cluster to which the network server belongs, a storage cluster to which the storage server belongs, and a compute cluster to which the compute server belongs. Through the technical solution of this invention, the difficulty of deployment can be reduced, labor costs can be decreased, and automated deployment can be achieved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a deployment method, apparatus, device and storage medium. Background Technology

[0002] SDDC (Software-defined data center) virtualizes and software-izes all the traditional, physical, and hardware resources of a data center. A data center is a globally collaborative network of specific devices used to accelerate information transmission over the Internet infrastructure.

[0003] Existing deployment and scaling solutions are based on a combination of UI and PowerShell scripts. Due to the unique technical complexity of the Microsoft SDDC environment, the deployment process is cumbersome and requires a lot of manual confirmation for preparation. Summary of the Invention

[0004] This invention provides a deployment method, apparatus, device, and storage medium that solves the problem of cumbersome deployment operations and the need for manual confirmation of a large amount of preparatory work due to the unique technical complexity of the Microsoft SDDC environment.

[0005] According to one aspect of the present invention, a deployment method is provided, the method comprising:

[0006] The MDT server obtains information about the domain controller server, management server, network server, storage server, and compute server.

[0007] The MDT server deploys the domain controller server, management server, network server, storage server, and compute server based on the domain controller server information, management server information, network server information, storage server information, and compute server information.

[0008] The MDT server creates the management cluster to which the management server belongs, and establishes a VMM server on the management cluster, so that the VMM server can create the network cluster to which the network server belongs, the storage cluster to which the storage server belongs, and the computing cluster to which the computing server belongs.

[0009] According to another aspect of the present invention, a deployment apparatus is provided, configured in an MDT server, the deployment apparatus comprising:

[0010] The acquisition module is used to acquire information about the domain controller server, management server, network server, storage server, and compute server.

[0011] The deployment module is used to deploy the domain controller server, management server, network server, storage server, and computing server based on the domain controller server information, management server information, network server information, storage server information, and computing server information.

[0012] A creation module is used to create the management cluster to which the management server belongs, and to establish a VMM server on the management cluster, so that the VMM server can create the network cluster to which the network server belongs, the storage cluster to which the storage server belongs, and the computing cluster to which the computing server belongs.

[0013] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0014] At least one processor; and

[0015] A memory communicatively connected to the at least one processor; wherein,

[0016] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the deployment method described in any embodiment of the present invention.

[0017] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the deployment method described in any embodiment of the present invention.

[0018] This invention, in its embodiments, obtains domain controller server information, management server information, network server information, storage server information, and compute server information through an MDT server. The MDT server then deploys the domain controller server, management server, network server, storage server, and compute server based on this information. The MDT server creates a management cluster to which the management server belongs, and establishes a VMM server on the management cluster. This allows the VMM server to create a network cluster to which the network server belongs, a storage cluster to which the storage server belongs, and a compute cluster to which the compute server belongs. This solves the problem of cumbersome deployment operations and the need for extensive manual confirmation of preparatory work due to the unique technical complexity of the Microsoft SDDC environment. It reduces deployment difficulty, lowers labor costs, and enables automated deployment.

[0019] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a flowchart of a deployment method according to Embodiment 1 of the present invention;

[0022] Figure 2 This is a schematic diagram related to bare metal push during the deployment of a server in Embodiment 1 of the present invention;

[0023] Figure 3 This is a schematic diagram related to the deployment of a VMM server during the server deployment process in Embodiment 1 of the present invention;

[0024] Figure 4 This is a schematic diagram related to the deployment of a software-defined network cluster during the server deployment process in Embodiment 1 of the present invention;

[0025] Figure 5 This is a schematic diagram related to the deployment of a storage cluster during the deployment of a server, as shown in Embodiment 1 of the present invention.

[0026] Figure 6 This is a schematic diagram related to the deployment of a computing cluster during the deployment of a server in Embodiment 1 of the present invention;

[0027] Figure 7 This is a schematic diagram illustrating the deployment of the SDDC monitoring component during the server deployment process according to Embodiment 1 of the present invention.

[0028] Figure 8 This is a schematic diagram of the structure of a deployment device according to Embodiment 2 of the present invention;

[0029] Figure 9 This is a schematic diagram of the structure of an electronic device according to Embodiment 3 of the present invention. Detailed Implementation

[0030] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0031] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0032] Example 1

[0033] Figure 1 This is a flowchart of a deployment method according to Embodiment 1 of the present invention. This embodiment is applicable to automated deployment based on the Microsoft SDDC environment. The method can be executed by the deployment device in this embodiment, which can be implemented in software and / or hardware, such as... Figure 1 As shown, the method specifically includes the following steps:

[0034] S110, the MDT server obtains information about the domain controller server, management server, network server, storage server, and compute server.

[0035] The deployment of each component of SDDC—Active Direct (AD) server, management cluster, Software Defined Network (SDN) cluster, compute cluster, and storage cluster—primarily relies on graphical interfaces and independent scripts. Because the rack locations, server roles and quantities, object names, and network IPs vary across different Availability Zones (AZs), various deployment operations require adaptive adjustments and modifications based on the AZ's specific requirements, resulting in low overall deployment efficiency and standardization. To improve deployment efficiency and achieve standardized and automated AZ deployment, the Microsoft Development Tool (MDT) server can be used for process orchestration, enabling automated one-click deployment.

[0036] Specifically, the MDT server can obtain information about the domain controller server, management server, network server, storage server, and compute server in the following way: At the beginning of the deployment of the MDT server, it is necessary to obtain and import various server information, that is, the MDT server obtains information about the domain controller (Active Direct, AD) server, management (MGMT) server, software defined network (SDN) server, storage server, and compute server, wherein the network server information refers to the software defined network server information.

[0037] The S120 MDT server deploys domain controllers, management servers, network servers, storage servers, and compute servers based on information from domain controllers, management servers, network servers, storage servers, and compute servers.

[0038] Specifically, the MDT server can deploy domain controllers, management servers, network servers, storage servers, and compute servers based on domain controller information, management server information, network server information, storage server information, and compute server information in the following way: obtain and import domain controller information, management server information, network server information, storage server information, and compute server information, and then deploy the domain controllers, management servers, network servers, storage servers, and compute servers in sequence based on the above information.

[0039] S130, the MDT server creates the management cluster to which the management server belongs, and establishes a VMM server on the management cluster, so that the VMM server can create the network cluster to which the network server belongs, the storage cluster to which the storage server belongs, and the computing cluster to which the compute server belongs.

[0040] The purpose of creating the management cluster to which the MDT server belongs is to create a VMM (Virtual Machine Management) server on the basis of this management cluster.

[0041] Specifically, the MDT server creates a management cluster belonging to the management server, and establishes a VMM server on the management cluster. The VMM server can then create a network cluster belonging to the network server, a storage cluster belonging to the storage server, and a compute cluster belonging to the compute server in the following ways: after cleaning up the disk, the management cluster belonging to the management server is created, the SQL server is deployed, and the VMM server is deployed. Once the VMM server is established, the subsequent deployment process is transferred to the VMM server for operation and control, and the network cluster belonging to the network server, the storage cluster belonging to the storage server, and the compute cluster belonging to the compute server are created.

[0042] Optionally, after the MDT server creates the management cluster to which the management server belongs, it also includes:

[0043] The MDT server configures the fault tolerance domain, heartbeat, shared volume, and network type of the management cluster.

[0044] The MDT server disables automatic load balancing for the management cluster.

[0045] It is important to note that when creating a management cluster for a management server on an MDT server, you need to clean up the disk first. If it is a new computer, you do not need to clean up the disk, but if it is an existing computer, you need to clean up the disk.

[0046] The shared volumes include the Library shared volume and the MGMT shared volume.

[0047] Specifically, the MDT server configures the fault tolerance domain, heartbeat, shared volume, and network type of the management cluster. The MDT server can disable automatic load balancing for the management cluster by: performing a systematic verification of the environment and configuration, configuring the AD server, cleaning up the disk, creating the management cluster, and configuring the fault tolerance domain, heartbeat, Library shared volume, MGMT shared volume, and cluster network type of the created management cluster, and then disabling automatic load balancing. In addition to configuring the fault tolerance domain, heartbeat, shared volume, and network type of the management cluster on the MDT server and disabling automatic load balancing, it is also necessary to start S2D (Storage Space Direct), create a file service role, and establish a shared file directory.

[0048] Optionally, a VMM server may be set up on the management cluster, including:

[0049] The MDT server creates the virtual machines for the management cluster;

[0050] The MDT server deploys an SQL server on the virtual machines of the management cluster based on an SQL configuration file;

[0051] The MDT server deploys at least two VMM servers on the virtual machines of the management server based on the VMM configuration file.

[0052] Specifically, the MDT server can create the virtual machines for the management cluster by enabling the Credential SSP (Credential Server Service) for cross-level remote access, creating the virtual machines and cluster roles, and then disabling Credential SSP for security reasons.

[0053] Specifically, the MDT server deploys the SQL server on the virtual machines of the management cluster based on the SQL configuration file in the following ways: It performs a systematic verification of the environment and configuration; the MDT server creates the virtual machines and the virtual machine cluster for the management cluster; it obtains the SQL configuration file; and it deploys the SQL server based on the SQL configuration file. The purpose of deploying the SQL server is to store data from the VMM server; therefore, the SQL server must be deployed first, followed by the VMM server.

[0054] Specifically, the method for deploying at least two VMM servers on the virtual machine of the management server based on the VMM configuration file can be as follows: After deploying the SQL server, prepare for VMM installation, generate the VMM configuration file, and deploy at least two VMM servers based on the VMM configuration file.

[0055] It is important to note that the MDT deployment progress needs to be tracked throughout the entire deployment process.

[0056] Optional, also includes:

[0057] The MDT service configures the operating mode, account, host group, port information, virtual network adapter port definition, logical network definition, logical network address pool, managed network server, managed storage server, managed compute server, uplink port definition, physical network card, virtual network card, and logical switch for each VMM server.

[0058] Among them, port information is port classification information, managed network server is managed SDN server, managed storage server is managed Storage server, and managed computing server is managed Compute server.

[0059] Optionally, after the VMM server creates the network cluster to which the network server belongs, it also includes:

[0060] The VMM server configures the fault tolerance domain, heartbeat, shared volume, and network type of the network cluster.

[0061] The VMM server disables automatic load balancing for the network cluster.

[0062] It is important to note that once the VMM server is established, the subsequent deployment process will be transferred to the VMM server for operation and control. This involves sequentially establishing the VMM basic network environment, network virtualization components, network clusters, compute clusters, and storage clusters. After creating the network clusters, compute clusters, and storage clusters, the VMM server needs to configure the cluster's fault tolerance domain, heartbeat, shared volumes, network type, and other parameters, and disable the cluster's automatic load balancing.

[0063] Optional, also includes:

[0064] If the disk parameters meet the preset conditions, the VMM server creates virtual machines for the network cluster;

[0065] The VMM server deploys the NC server on the virtual machines in the network cluster according to the NC service template;

[0066] The VMM server starts the NC server;

[0067] The VMM server creates the logical network, network definition, and network address pool for the NC server;

[0068] The VMM server deploys the MUX server on the virtual machines in the network cluster according to the MUX service template;

[0069] The VMM server starts the MUX server;

[0070] The VMM server deploys the GW server on the virtual machines in the network cluster according to the GW service template;

[0071] The VMM server starts the GW server.

[0072] The default condition is that the disk has reserved the amount of memory required to create the cluster. The VMM server includes installing features, creating the cluster, deploying the NC (Network Controller) server, deploying the SLB MUX (Software Loadbalancer MUX) server, and deploying the GW (Gateway) server in the process of creating a network cluster and deploying network services.

[0073] Optionally, after the VMM server creates the storage cluster to which the storage server belongs, it also includes:

[0074] The VMM server configures the fault tolerance domain, heartbeat, shared volume, and network type of the storage cluster;

[0075] The VMM server disables automatic load balancing for the storage cluster.

[0076] It is important to note that after configuring the fault tolerance domain, heartbeat, shared volume, and network type of the storage cluster on the VMM server, and disabling automatic load balancing for the storage cluster, it is also necessary to create an extended file server to expand the capacity, and at the same time create storage categories, add storage devices, configure storage devices, create file sharing, and grant shared storage licenses.

[0077] Optionally, after the VMM server creates the computing cluster to which the computing server belongs, it also includes:

[0078] The VMM server configures the fault tolerance domain, heartbeat, shared volume, and network type of the computing cluster.

[0079] The VMM server disables automatic load balancing for the cluster.

[0080] It is important to note that after deployment, a separate module can be used for verification, including network interface card configurations such as MTU, RDMA, QoS, and SMB binding, as well as configurations of SDN's ncagent and SLB agent and the storage cluster's fault domain. This allows for a one-click display of whether there are any acceptance items that have not been configured correctly.

[0081] In a specific example, the MDT server establishes an AZ (Available Zone) domain controller based on the domain controller server information, deploys a management server based on the management server information, and establishes a management cluster to which the management server belongs. On the management cluster, the necessary basic virtual machines are built, including a database and a VMM (Virtual Machine Management) server. The relevant flowchart and detailed steps are as follows:

[0082] Figure 2 This is a schematic diagram related to bare metal push during the deployment of a server in Embodiment 1 of the present invention, as shown below. Figure 2 As shown, the detailed steps are as follows:

[0083] Start-A0_ADBareMetal

[0084] • Start-BareMetalActions_ImportBMCInfo – Retrieves and imports information about domain controllers, management servers, network servers, storage servers, and compute servers.

[0085] • Start-BareMetalActions_DeployADHost – Deploy Active Directory (AD) server

[0086] Start-A1_MGMTBareMetal

[0087] • Start-BareMetalActions_DeployMGMTHost – Deploy the MGMT (Management) Server

[0088] Start-A2_SDNBareMetal

[0089] • Start-BareMetalActions_DeploySDNHost – Deploy SDN (Software-Defined Networking)

[0090] server

[0091] Start-A3_StorageBareMetal

[0092] • Start-BareMetalActions_DeployStorageHost – Deploy the Storage server

[0093] Start-A4_ComputerBareMetal

[0094] • Start-BareMetalActions_DeployComputeHost – Deploy the Compute server

[0095] Figure 3 This is a schematic diagram illustrating the deployment of a VMM server during the server deployment process in Embodiment 1 of the present invention, as shown below. Figure 3 As shown, the detailed steps are as follows:

[0096] Start-B0_ModulePre-check – Pre-deployment verification

[0097] Start-B1_AD – Configure AD server related settings

[0098] Start-B2_MGMTCluster (can be broken down into the following steps:)

[0099] • Start-OsActions_ClearDisks – Clean up the disk

[0100] • Start-B02_02_ClusterActions_CreateCluster – Create a Management cluster

[0101] • Start-ClusterActions_CreateFaultDomain – Create a fault-tolerant domain

[0102] • Start-ClusterNetworkActions_ClusterHeartBeatQos – Set cluster heartbeat

[0103] • Start-B02_05_DisableClusterBalancer – Disables automatic cluster load balancing

[0104] • Start-B02_06_SetClusterNetworkType – Sets the cluster network type

[0105] • Start-S2dActions_EnableS2D – Enables S2D (Storage Space Direct).

[0106] • Start-B02_08_CreateVmVolumes – Create a shared Library volume

[0107] • Start-B02_09_CreateMgmtVolumes – Create MGMT shared volumes

[0108] • Start-B02_10_AddFileServiceRole – Create a file service role

[0109] • Start-B02_11_AddShareFiles – Create a shared file directory

[0110] Start-B3_CA (Cloud Management Portal Server Name, which can be broken down into the following steps:)

[0111] • Start-B3_EnableWSManCredSSP – Enables Credential SSP (enables cross-level remote access to the server; the following actions are similar).

[0112] • Start-HostActions_CreateVM – Create a virtual machine

[0113] • Start-HostActions_AddVMClusterRole – Create a virtual machine cluster role

[0114] • Start-B3_DisableWSManCredSSP – Disables Credential SSP (For security reasons, this function should be disabled after creation; the same applies to the following actions).

[0115] • Start-HostActions_StartClusterVM – Starts the cluster virtual machine (because the virtual machine is shut down by default after creation).

[0116] • Start-B3_CheckMDTDeployProcess – Track MDT deployment progress Start-B4_VMM&SQLSetup

[0117] • Start-B0_ModulePre-check – Pre-deployment verification

[0118] • Start-B4_EnableWSManCredSSP – Enable Credential SSP

[0119] • Start-HostActions_CreateVM – Create a virtual machine

[0120] • Start-HostActions_AddVMClusterRole – Add a virtual machine cluster role

[0121] ·Start-B4_DisableWSManCredSSP – Disable Credential SSP

[0122] • Start-HostActions_StartClusterVM – Start the cluster virtual machine

[0123] • Start-B4_CheckMDTDeployProcess – Check the deployment process

[0124] • Start-HostActions_CreateVMCluster – Create a virtual machine cluster

[0125] • Start-B4_GenerateSqlConfigureFile – Retrieves the SQL configuration file

[0126] ·Start-B4_InstallSqlServer–Install SQL Server

[0127] • Start-B4_EnableWSManCredSSP – Enable Credential SSP

[0128] • Start-HostActions_CreateVM – Create a virtual machine

[0129] • Start-HostActions_AddVMClusterRole – Add a virtual cluster role

[0130] ·Start-B4_DisableWSManCredSSP–turn off Credential SSP

[0131] • Start-HostActions_StartClusterVM – Start the cluster virtual machine

[0132] • Start-B4_CheckMDTDeployProcess – Track MDT deployment progress

[0133] • Start-HostActions_CreateVMCluster – Create a virtual machine cluster

[0134] • Start-B4_InstallPrerequisiteForSCVMM – VMM Installation Preparation

[0135] • Start-B4_GenerateSCVMMConfigureFile – Generates the VMM configuration file

[0136] • Start-B4_InstallSCVMM – Install VMM node 1 (deploy at least two VMM servers)

[0137] • Start-B4_InstallSCVMM – Install VMM node 2 • Start-B5_MGMTSetupInVMM

[0138] • Start-B5_01_CreateRunAsAccounts – Creates run mode accounts

[0139] • Start-B5_02_CreateParentHostGroups – Create the parent host group

[0140] • Start-B5_03_CreatePortClassification – Create port classification

[0141] • Start-B5_04_CreateVNAdaptNativePortProfile – Creates a virtual network adapter port definition

[0142] • Start-B5_05_CreateMgmtStorageLogicalNetwork – Create MGMT and SMB logical networks

[0143] • Start-HostActions_CreateHostGroup – Creates an MGMT host group

[0144] • Start-HostActions_CreateHostGroup – Create an SDN host group

[0145] • Start-VmmActions_CreateLogicalNetworkDefinition – Creates a logical network definition

[0146] • Start-VmmActions_AllocateLogicalNetworkIPPool – Creates a logical network address pool

[0147] • Start-VmmActions_CreateUplinkProfile – Creates the uplink port definition

[0148] • Start-VmmActions_CreateLogicalSwitch – Create a logical switch

[0149] • Start-B5_12_MgmtHostAddToVMM – Manage MGMT cluster Start-B6_DeployWDS&DHCPServices – Deploy WDS&DHCP services Start-B7_ModulePost-check – Acceptance test upon deployment completion

[0150] Once the VMM is established, the VMM basic network environment, network virtualization components, SDN cluster, compute and storage clusters, etc., are sequentially built on the VMM server. Figure 4 This is a schematic diagram related to the deployment of a software-defined network cluster during the deployment of a server in Embodiment 1 of the present invention, as shown below. Figure 4 As shown, the detailed steps are as follows:

[0151] Start-C0_ModulePre-check – Pre-deployment verification

[0152] Start-C1_PushSDNHostOS

[0153] • Start-HostActions_HostAddToVMM – Manage SDN Servers

[0154] • Start-VmmActions_CreateUplinkProfile – Creates the uplink port definition

[0155] • Start-VmmActions_CreateLogicalSwitch – Create a logical switch

[0156] • Start-HostActions_SetPhysicalNetworkAdapter – Configure the physical network adapter

[0157] • Start-VmmActions_DeployLogicalSwitch – Deploy the logical switch

[0158] • Start-HostActions_SetVirtualNetworkAdapter – Configure the virtual network adapter

[0159] Start-C2_SDNCluster

[0160] • Start-OsActions_ClearDisks – Clear disk

[0161] ·Start-OsActions_InstallClusterFeature–Install Windows Feature

[0162] • Start-ClusterActions_CreateCluster – Create a cluster

[0163] • Start-ClusterActions_CreateFaultDomain – Create a fault-tolerant domain

[0164] • Start-ClusterNetworkActions_ClusterHeartBeatQos – Set cluster heartbeat

[0165] • Start-ClusterNetworkActions_DisableClusterBalancer – Disables automatic load balancing for the cluster

[0166] • Start-ClusterNetworkActions_SetClusterNetworkType – Configure cluster network

[0167] • Start-S2dActions_EnableS2D – Enable S2D

[0168] • Start-C02_09_CreateVmVolumes – Create a shared volume

[0169] Start-C3_NC (Network Controller Component Name)

[0170] • Start-C03_01_CheckParameters – Parameter Check

[0171] • Start-C03_02_ImportServiceTemplate – Import Service Template

[0172] • Start-C03_03_ConfigureAndDeployService – Configure and deploy NC

[0173] • Start-C03_04_OnBoardNetworkController – Start NC

[0174] • Start-C03_05_CreateLogicalNetworks – Create logical networks

[0175] • Start-C03_06_CreateSDNLogicalNetworkDefinition – Create a logical network definition

[0176] • Start-C03_07_CreateSDNLogicalNetworkIPPool – Create a logical network address pool

[0177] Start-C4_VMMSDNSetup,networks (Deploying software-defined networks in the VMM)

[0178] Start-C5_MUX (Load Balancer Component Name)

[0179] • Start-C04_01_CheckParameters – Parameter Check

[0180] • Start-C04_02_ImportServiceTemplate – Import Service Template

[0181] • Start-C04_03_ConfigureAndDeployService – Configure and deploy MUX

[0182] • Start-C04_04_OnBoardSLB – Start MUX

[0183] Start-C6_GW (Gateway Component Name)

[0184] • Start-C05_01_CheckParameters – Parameter Check

[0185] • Start-C05_02_ImportServiceTemplate – Import Service Template

[0186] • Start-C05_03_ConfigureAndDeployService – Configure and deploy GW

[0187] • Start-C05_04_OnBoardGW – Start GW

[0188] Start-C7_ModulePost-check – Acceptance of deployment completion

[0189] Figure 5 This is a schematic diagram related to the deployment of a storage cluster during the deployment of a server in Embodiment 1 of the present invention, as shown below. Figure 5 As shown, the detailed steps are as follows:

[0190] Start-D0_ModulePre-check – Pre-deployment verification

[0191] Start-D1_PushStorageHostOS

[0192] • Start-HostActions_HostAddToVMM – Manage Storage Server

[0193] • Start-VmmActions_CreateLogicalNetworkDefinition – Create a logical network

[0194] • Start-D1_02_AllocateLogicalNetworkIPPool – Create an IP pool

[0195] • Start-VmmActions_CreateUplinkProfile – Creates a switch port configuration file

[0196] • Start-VmmActions_CreateLogicalSwitch – Create a logical switch

[0197] • Start-HostActions_SetPhysicalNetworkAdapter – Configure network adapter

[0198] • Start-VmmActions_DeployLogicalSwitch – Deploy the logical switch

[0199] • Start-HostActions_SetVirtualNetworkAdapter – Virtual network adapter settings Start-D2_StorageCluster

[0200] • Start-OsActions_ClearDisks – Clean up the disk

[0201] • Start-D2_01_InstallStorageClusterFeature – Install storage cluster feature

[0202] • Start-D2_02_CreateCluster – Create a cluster

[0203] ·Start-OsActions_InstallClusterFeature–Install Windows Feature

[0204] • Start-D2_03_CreateFaultDomain – Creates a fault domain.

[0205] • Start-ClusterNetworkActions_ClusterHeartBeatQos – Set cluster heartbeat

[0206] • Start-ClusterNetworkActions_DisableClusterBalancer – Disable cluster load balancing

[0207] • Start-ClusterNetworkActions_SetClusterNetworkType – Sets the cluster network type

[0208] Start-D3_SOFS

[0209] • Start-D3_02_S2D – Enable S2D

[0210] • Start-D3_03_CreateClusterScaleOutFileServerRole – Create an extended file server

[0211] • Start-D03_03_CreateStorageClassification – Create storage classification

[0212] • Start-D03_04_AddStorageDevice – Add storage device

[0213] • Start-D03_05_SetStorageDevice – Set up the storage device

[0214] • Start-D03_06_CreateFileShare – Create a file share

[0215] • Start-D03_07_GrantSharePermission – Shared Storage Authorization

[0216] Start-D4_ModulePost-check – Acceptance of deployment completion

[0217] Figure 6 This is a schematic diagram related to the deployment of a computing cluster during the deployment of a server in Embodiment 1 of the present invention, as shown below. Figure 6 As shown, the detailed steps are as follows:

[0218] Start-E0_ModulePre-check – Pre-deployment verification

[0219] Start-E1_PushComputeHostOS

[0220] • Start-HostActions_HostAddToVMM – Manage Compute Servers

[0221] • Start-VmmActions_CreateLogicalNetworkDefinition – Creates a logical network definition

[0222] • Start-VmmActions_AllocateLogicalNetworkIPPool – Creates a logical network address pool

[0223] • Start-VmmActions_CreateUplinkProfile – Creates the uplink port definition

[0224] • Start-VmmActions_CreateLogicalSwitch – Create a logical switch

[0225] • Start-HostActions_SetPhysicalNetworkAdapter – Configure the physical network adapter

[0226] • Start-VmmActions_DeployLogicalSwitch – Push virtual switch

[0227] • Start-HostActions_SetVirtualNetworkAdapter – Configure the virtual network adapter

[0228] Start-E2_ComputeCluster

[0229] ·Start-OsActions_InstallClusterFeature–Install Windows Feature

[0230] • Start-ClusterActions_CreateCluster – Create a cluster

[0231] • Start-ClusterActions_CreateFaultDomain – Create a fault-tolerant domain

[0232] • Start-ClusterNetworkActions_ClusterHeartBeatQos – Set cluster heartbeat

[0233] • Start-ClusterNetworkActions_DisableClusterBalancer – Disables automatic load balancing for the cluster

[0234] • Start-ClusterNetworkActions_SetClusterNetworkType – Sets the cluster network type

[0235] Start-E3_VMMStor-compSetup

[0236] •Start-E03_01_AddComputerFileShare – Register Storage

[0237] Start-E4_ModulePost-check – Acceptance of deployment completion

[0238] Figure 7 This is a schematic diagram illustrating the deployment of the SDDC monitoring component during server deployment in Embodiment 1 of the present invention, as shown below. Figure 7 As shown, the detailed steps are as follows:

[0239] Start-F0_ModulePre-check – Verification before deployment and installation

[0240] Start-F1_SCOMinstall – Install SDDC monitoring components

[0241] Start-F2_ModulePost-check – Installation completion verification

[0242] The technical solution of this embodiment obtains domain controller server information, management server information, network server information, storage server information, and compute server information through an MDT server. The MDT server deploys the domain controller server, management server, network server, storage server, and compute server based on this information. The MDT server creates a management cluster to which the management server belongs, and establishes a VMM server on the management cluster. This allows the VMM server to create a network cluster to which the network server belongs, a storage cluster to which the storage server belongs, and a compute cluster to which the compute server belongs. This solves the problem of cumbersome deployment operations and the need for manual confirmation of a large amount of preparatory work due to the unique technical complexity of the Microsoft SDDC environment. It reduces deployment difficulty, lowers labor costs, and enables automated deployment.

[0243] Example 2

[0244] Figure 8 This is a schematic diagram of a deployment device according to Embodiment 2 of the present invention. This embodiment is applicable to automated deployment based on the Microsoft SDDC environment. The device can be implemented using software and / or hardware, and can be integrated into any device that provides deployment functionality, such as… Figure 8 As shown, the deployment device specifically includes: an acquisition module 210, a deployment module 220, and a creation module 230.

[0245] The acquisition module 210 is used to acquire information about the domain controller server, management server, network server, storage server, and computing server.

[0246] Deployment module 220 is used to deploy a domain controller server, a management server, a network server, a storage server, and a computing server based on the domain controller server information, management server information, network server information, storage server information, and computing server information.

[0247] The creation module 230 is used to create the management cluster to which the management server belongs, and to establish a VMM server on the management cluster, so that the VMM server can create the network cluster to which the network server belongs, the storage cluster to which the storage server belongs, and the computing cluster to which the computing server belongs.

[0248] Optional, also includes:

[0249] The configuration module is used by the MDT server to configure the fault tolerance domain, heartbeat, shared volume, and network type of the management cluster.

[0250] The disable module is used by the MDT server to disable automatic load balancing of the management cluster.

[0251] Optionally, the creation module is specifically used for:

[0252] The MDT server creates the virtual machines for the management cluster;

[0253] The MDT server deploys an SQL server on the virtual machines of the management cluster based on an SQL configuration file;

[0254] The MDT server deploys at least two VMM servers on the virtual machines of the management server based on the VMM configuration file.

[0255] Optionally, the creation module is also used for:

[0256] The MDT service configures the operating mode, account, host group, port information, virtual network adapter port definition, logical network definition, logical network address pool, managed network server, managed storage server, managed compute server, uplink port definition, physical network card, virtual network card, and logical switch for each VMM server.

[0257] Optional, also includes:

[0258] The VMM server configures the fault tolerance domain, heartbeat, shared volume, and network type of the network cluster.

[0259] The VMM server disables automatic load balancing for the network cluster.

[0260] Optional, also includes:

[0261] If the disk parameters meet the preset conditions, the VMM server creates virtual machines for the network cluster;

[0262] The VMM server deploys the NC server on the virtual machines in the network cluster according to the NC service template;

[0263] The VMM server starts the NC server;

[0264] The VMM server creates the logical network, network definition, and network address pool for the NC server;

[0265] The VMM server deploys the MUX server on the virtual machines in the network cluster according to the MUX service template;

[0266] The VMM server starts the MUX server;

[0267] The VMM server deploys the GW server on the virtual machines in the network cluster according to the GW service template;

[0268] The VMM server starts the GW server.

[0269] Optional, also includes:

[0270] The VMM server configures the fault tolerance domain, heartbeat, shared volume, and network type of the storage cluster;

[0271] The VMM server disables automatic load balancing for the storage cluster.

[0272] Optional, also includes:

[0273] The VMM server configures the fault tolerance domain, heartbeat, shared volume, and network type of the computing cluster.

[0274] The VMM server disables automatic load balancing for the cluster.

[0275] The above-described products can perform the methods provided in any embodiment of the present invention, and have the corresponding functional modules and beneficial effects for performing the methods.

[0276] The technical solution of this embodiment obtains domain controller server information, management server information, network server information, storage server information, and compute server information through an MDT server. The MDT server deploys the domain controller server, management server, network server, storage server, and compute server based on this information. The MDT server creates a management cluster to which the management server belongs, and establishes a VMM server on the management cluster. This allows the VMM server to create a network cluster to which the network server belongs, a storage cluster to which the storage server belongs, and a compute cluster to which the compute server belongs. This solves the problem of cumbersome deployment operations and the need for manual confirmation of a large amount of preparatory work due to the unique technical complexity of the Microsoft SDDC environment. It reduces deployment difficulty, lowers labor costs, and enables automated deployment.

[0277] Example 3

[0278] Figure 9 This is a schematic diagram of an electronic device according to Embodiment 3 of the present invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0279] like Figure 9As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0280] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0281] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as deployment methods.

[0282] In some embodiments, the deployment method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the deployment method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the deployment method by any other suitable means (e.g., by means of firmware).

[0283] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0284] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0285] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0286] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0287] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0288] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0289] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0290] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A deployment method, characterized in that, include: The MDT server obtains information about the domain controller server, management server, network server, storage server, and compute server. The MDT server deploys the domain controller server, management server, network server, storage server, and compute server based on the domain controller server information, management server information, network server information, storage server information, and compute server information. The MDT server creates the management cluster to which the management server belongs, and establishes a VMM server on the management cluster, so that the VMM server can create the network cluster to which the network server belongs, the storage cluster to which the storage server belongs, and the computing cluster to which the computing server belongs. After the MDT server creates the management cluster to which the management server belongs, it also includes: The MDT server configures the fault tolerance domain, heartbeat, shared volume, and network type of the management cluster. The MDT server disables automatic load balancing for the management cluster; Setting up a VMM server on the management cluster includes: The MDT server creates the virtual machines for the management cluster; The MDT server deploys an SQL server on the virtual machines of the management cluster based on an SQL configuration file; The MDT server deploys at least two VMM servers on the virtual machines of the management server based on the VMM configuration file.

2. The method according to claim 1, characterized in that, Also includes: The MDT service configures the operating mode, account, host group, port information, virtual network adapter port definition, logical network definition, logical network address pool, managed network server, managed storage server, managed compute server, uplink port definition, physical network card, virtual network card, and logical switch for each VMM server.

3. The method according to claim 2, characterized in that, After the VMM server creates the network cluster to which the network server belongs, it also includes: The VMM server configures the fault tolerance domain, heartbeat, shared volume, and network type of the network cluster. The VMM server disables automatic load balancing for the network cluster.

4. The method according to claim 3, characterized in that, Also includes: If the disk parameters meet the preset conditions, the VMM server creates virtual machines for the network cluster; The VMM server deploys the NC server on the virtual machines in the network cluster according to the NC service template; The VMM server starts the NC server; The VMM server creates the logical network, network definition, and network address pool for the NC server; The VMM server deploys the MUX server on the virtual machines in the network cluster according to the MUX service template; The VMM server starts the MUX server; The VMM server deploys the GW server on the virtual machines in the network cluster according to the GW service template; The VMM server starts the GW server.

5. The method according to claim 4, characterized in that, After the VMM server creates the storage cluster to which the storage server belongs, it also includes: The VMM server configures the fault tolerance domain, heartbeat, shared volume, and network type of the storage cluster; The VMM server disables automatic load balancing for the storage cluster.

6. The method according to claim 5, characterized in that, After the VMM server creates the compute cluster to which the compute server belongs, it also includes: The VMM server configures the fault tolerance domain, heartbeat, shared volume, and network type of the computing cluster. The VMM server disables automatic load balancing for the computing cluster.

7. A deployment device, characterized in that, The deployment device, configured in the MDT server, includes: The acquisition module is used to acquire information about the domain controller server, management server, network server, storage server, and compute server. The deployment module is used to deploy the domain controller server, management server, network server, storage server, and computing server based on the domain controller server information, management server information, network server information, storage server information, and computing server information. A creation module is used to create the management cluster to which the management server belongs, and to establish a VMM server on the management cluster, so that the VMM server can create the network cluster to which the network server belongs, the storage cluster to which the storage server belongs, and the computing cluster to which the computing server belongs. The device further includes: a setting module, used by the MDT server to set the fault tolerance domain, heartbeat, shared volume and network type of the management cluster; The module is disabled to disable automatic load balancing of the management cluster on the MDT server. The creation module is specifically used for: The MDT server creates the virtual machines for the management cluster; The MDT server deploys an SQL server on the virtual machines of the management cluster based on an SQL configuration file; The MDT server deploys at least two VMM servers on the virtual machines of the management server based on the VMM configuration file.

8. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor to enable the at least one processor to perform the deployment method according to any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that are used to cause a processor to execute the deployment method according to any one of claims 1-6.

Images