Method for expanding edge resource, edge cloud system, device and storage medium

Abstract

Embodiments of the present application provide an edge resource expansion method, an edge cloud system, a device and a storage medium. In the embodiments of the present application, a center service node in a center cloud can request a server producer to produce a target server based on an edge resource expansion request of a target user; and install an operating system on the target server and deploy a cloud service; then, a logistics transportation party can be instructed to transport the target server to a target edge cluster corresponding to the target user, so as to deploy the target server in the target edge cluster and expand an edge node in the target edge cluster. In the embodiments, a whole-link expansion process integrating the user's edge resource expansion request, server production, transportation and edge cluster deployment is implemented, and the edge node expansion is integrated and end-to-end edge node expansion is implemented.

Description

Technical Field

[0001] This application relates to the field of cloud computing technology, and in particular to a method for expanding edge resources, an edge cloud system, a device, and a storage medium. Background Technology

[0002] Traditional cloud computing employs a centralized data center (DC) model, offering powerful computing capabilities. However, with the continuous emergence of massive new mobile and IoT device applications, this cloud computing model, reliant on centralized data centers, can no longer adequately meet user needs. To address the problems inherent in centralized cloud computing, edge computing has emerged.

[0003] Edge clouds consist of edge nodes distributed in the same region, specifically handling service requests from users in that region, and can quickly and elastically provide cloud computing services to users. As user applications evolve, more and more users are requesting the expansion of edge nodes. Summary of the Invention

[0004] This application provides a method for expanding edge resources, an edge cloud system, a device, and a storage medium to achieve integrated expansion of edge nodes.

[0005] This application provides a method for scaling up edge resources, applicable to central service nodes in a central cloud; the method includes:

[0006] Obtain edge resource expansion requests provided by the target user;

[0007] Based on the edge resource expansion request, a server production request is provided to the server producer to request the server producer to produce the target server.

[0008] Install the operating system and deploy cloud services on the target server;

[0009] Send a transport instruction to the logistics provider to instruct the logistics provider to transport the target server to the target edge cluster corresponding to the target user, so that the target server can be deployed in the target edge cluster.

[0010] This application embodiment also provides an edge cloud system, including: a central cloud and at least one edge cluster connected to the central cloud network; the central cloud includes: a central service node; the edge cluster includes: a server rack and edge nodes deployed in the server rack;

[0011] The central service node is used to execute the steps in the above-mentioned method for expanding edge resources.

[0012] This application embodiment also provides a computing device, including: a memory, a processor, and a communication component; wherein, the memory is used to store computer programs;

[0013] The processor is coupled to the memory and the communication component to execute the computer program for performing the steps in the above-described edge resource expansion method.

[0014] This application also provides a computer-readable storage medium storing computer instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps in the above-described edge resource expansion method.

[0015] In this embodiment, the central service node in the central cloud can request the server manufacturer to produce a target server based on the target user's edge resource expansion request; install an operating system and deploy cloud services on the target server; then, it can instruct the logistics provider to transport the target server to the target edge cluster corresponding to the target user, so as to deploy the target server in the target edge cluster and realize the expansion of edge nodes in the target edge cluster. This embodiment realizes a full-link expansion process integrating user-initiated edge resource expansion requests, server production, transportation, and edge cluster deployment, achieving integrated and end-to-end edge node expansion. Attached Figure Description

[0016] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0017] Figure 1 This is a schematic diagram of the structure of an edge cloud system provided in an embodiment of this application;

[0018] Figure 2 A detailed flowchart illustrating the scaling process of edge resources provided in this application embodiment;

[0019] Figure 3 A flowchart illustrating the edge resource expansion method provided in this application embodiment;

[0020] Figure 4 A schematic diagram of the structure of a computing device provided in an embodiment of this application. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0022] In some embodiments of this application, the central service node in the central cloud can request the server manufacturer to produce a target server based on the target user's edge resource expansion request; install an operating system and deploy cloud services on the target server; then, it can instruct the logistics provider to transport the target server to the target edge cluster corresponding to the target user, so as to deploy the target server in the target edge cluster and realize the expansion of edge nodes in the target edge cluster. This embodiment realizes a full-link expansion process integrating user-initiated edge resource expansion requests, server production, transportation, and edge cluster deployment, achieving integrated and end-to-end edge node expansion.

[0023] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0024] It should be noted that the same reference numerals denote the same object in the following figures and embodiments. Therefore, once an object is defined in one figure or embodiment, it does not need to be discussed further in subsequent figures and embodiments.

[0025] Figure 1 This is a schematic diagram of the structure of an edge cloud system provided in an embodiment of this application. Figure 1 As shown, the edge cloud system includes: a central cloud 10 and at least one edge cluster 20 connected to the central cloud 10 network.

[0026] Edge cloud, in this context, refers to a cloud computing platform built upon edge infrastructure, based on cloud computing technology and edge computing capabilities. It's a cloud platform located at the edge, possessing computing, networking, storage, and security capabilities. Edge cloud is a relative concept; it refers to a cloud computing platform relatively close to the terminal. In other words, it differs from control nodes or traditional cloud computing platforms. Control nodes or traditional cloud computing platforms can include resource-scalable and geographically concentrated data centers or server rooms, while edge cloud consists of multiple edge cloud nodes. While the resource scale of a single edge cloud node is relatively small, the large number of edge cloud nodes allows for a wider coverage area. In other words, the edge cloud system in this embodiment is also a cloud computing platform built upon edge infrastructure, based on cloud computing technology and edge computing capabilities. It's a cloud platform located at the edge, possessing computing, networking, storage, and security capabilities, relatively close to the terminal, and a network system built on the infrastructure between control nodes or traditional cloud computing systems and the terminal. The terminal involved in this embodiment refers to the demand side of cloud computing services, such as terminals or user terminals in the Internet of Things (IoT).

[0027] In this embodiment, the central cloud 10 is equipped with a central service node 101, which connects with the edge cluster 20 and terminals ( Figure 1 (Not shown in the image) When combined, a “cloud-edge-device three-body collaborative” network architecture can be formed. In this network architecture, tasks such as network forwarding, storage, computing, and intelligent data analysis can be processed in each edge cluster 20. Since the edge cluster 20 is closer to the terminal, it can reduce response latency, reduce the pressure on management nodes or traditional cloud computing platforms, and reduce bandwidth costs.

[0028] The central service node 101 refers to a device, software module, or software system with resource scheduling, management, and operation and maintenance functions. There can be one or more central service nodes 101. Multiple central service nodes 101 can be deployed on the same physical machine or on different physical machines.

[0029] In this embodiment, an edge cluster 20 can be a server room, a data center (DC), or an Internet data center (IDC), etc. For an edge cloud network, an edge cluster 20 can include one or more edge nodes. "Multiple" refers to two or more. Each edge node can include a series of edge infrastructures, including but not limited to: distributed data centers (DCs), wireless server rooms or clusters, operator communication networks, core network equipment, base stations, edge gateways, home gateways, computing devices or storage devices, and corresponding network environments, etc. It should be noted that the location, capabilities, and included infrastructure of different edge nodes can be the same or different.

[0030] In this embodiment, the edge node can provide various resources to the outside world. These resources can include hardware and software resources. Hardware resources can include computing resources such as processors, and storage resources such as memory and disks. The processor can be a Central Processing Unit (CPU) or a parallel processor, etc. The parallel processor can be a Graphics Processing Unit (GPU), a Field-Programmable Gate Array (FPGA), or an Application Specific Integrated Circuit (ASIC), etc. Software resources can include network resources such as bandwidth, network segment, and network interface card (NIC) configuration, as well as an operating system, etc.

[0031] In this embodiment, the infrastructure such as edge nodes in edge cluster 20 can belong to the users of edge cluster 20, be local resources of the users, and be operated and maintained by the users. Of course, the infrastructure such as edge nodes in edge cluster 20 can also be implemented partially or entirely in the target mode, that is, partially or entirely belonging to the public cloud (such as central cloud 10), and operated and maintained by the public cloud. The target mode extends the computing, storage, and network infrastructure of the public cloud to the user's local data center in a hardware and software integrated manner, providing a fully managed cloud service that meets the requirements of data security, local data processing, and low latency. The target mode is an extension of the public cloud in the user's local data center, deploying infrastructure resources belonging to the public cloud in the user's local data center or IDC, and having the public cloud manage and maintain the infrastructure resources corresponding to the target mode.

[0032] A server rack (also known as a server cabinet) serves as the infrastructure of a data center or server room, providing storage for servers and offering them power and communication resources. For the edge cluster 20, it may include: a server rack 201; the server rack 201 is used to install edge nodes. The server rack 201 serves as the storage for edge nodes and provides them with power and communication resources. Each server rack 201 can install one or more edge nodes.

[0033] In this embodiment, the central service node 101 can also provide edge node expansion functionality. Specifically, as shown below... Figure 1 and Figure 2 As shown, users of the edge cluster to be expanded (defined as target users) can submit edge resource expansion requests to the central cloud 10. Figure 1 and Figure 2 Step 1).

[0034] The edge resource expansion request can include: the resource expansion type (ReasonType) and the amount of resources to be expanded. The amount of resources to be expanded can be represented by Stock Keeping Units (SKUs). An SKU is the basic unit for external sales of the edge cluster, integrating computing, storage, and networking into one unit; one SKU can be installed in a complete rack.

[0035] Resource expansion types include: rack-wide expansion and non-rack-wide expansion. Among them, edge resource expansion has the following three scenarios: (1) upgrading only the existing computing SKUs in the edge cluster, that is, expanding computing resources in the existing racks of edge cluster 20; (2) expanding new computing SKUs, expanding computing resources in the form of rack-wide expansion; (3) upgrading both existing computing SKUs and expanding new computing SKUs, that is, expanding the computing resources of existing racks and expanding new racks. In the embodiments of this application, the resource expansion type corresponding to the above scenario (1) can be defined as non-rack-wide expansion; and the resource expansion types corresponding to the above scenarios (2) and (3) can be defined as rack-wide expansion.

[0036] The central service node 101 can obtain edge resource expansion requests provided by the target user; and based on the edge resource expansion requests, it provides server production requests to the service provider 30, requesting the server provider 30 to produce the target server. Figure 1 Step 2 and Figure 2 Steps 2 and 3).

[0037] Specifically, such as Figure 2 As shown, the central control node 101 can obtain the resource expansion type and the amount of resources to be expanded from the edge resource expansion request.

[0038] Furthermore, if the resource expansion type is a full rack expansion, the infrastructure information of the rack to be expanded can be constructed (corresponding to...). Figure 2 Step 2, "Building the Infrastructure Model". The rack to be expanded includes at least one target server.

[0039] Specifically, the location of the rack to be expanded within the data center of the operator of the rack to be expanded can be determined based on the location information of the existing racks of the target edge cluster within the data center of the operator of the rack to be expanded. Here, the target edge cluster is the edge cluster belonging to the target user who provided the edge resource expansion request.

[0040] For the target mode, the existing cabinets of the target edge cluster are operated by the central cloud. The central service node 101 can assign logical numbers to the cabinets in the target edge cluster and create logical cabinet positions in the operator's data center; then, based on the location information of the existing cabinets of the target edge cluster in the operator's data center, it plans the location of the cabinets to be expanded in the operator's data center.

[0041] The central service node 101 can also determine the network topology of the cabinets to be expanded based on the existing network topology of the target edge cluster cabinets in the operator's data center; and obtain the network requirements of the target users from edge resource expansion requests; further, it can determine the network resource information of the cabinets to be expanded based on the network requirements of the target users and the network resources provided by the operator. Network resource information refers to the resources required for the device to achieve network communication, which may include: network segments, routing, and Domain Name System (DNS), and may also include the device's network mode. The network mode can be Virtual Private Network (VPN) mode, Virtual Private Cloud (VPC) mode, or leased line mode, etc. The network mode refers to the network communication mode between the cabinet and the central cloud 10, indicating which mode the cabinet uses to communicate with the central cloud 10.

[0042] Specifically, the central service node 101 can obtain the target user's required number of Internet Protocol (IP) addresses (N) from the target user's network requirements; further, it can determine N unassigned IP addresses from the network segments provided by the operations and maintenance provider, which can be used as IP addresses for the racks to be expanded, etc. The central service node 101 can also use the routing information from the operations and maintenance provider as the routing information for the racks to be expanded, etc. And, it can obtain the network mode selected by the target user from the target user's network requirements, which can be used as the network mode for the racks to be expanded, etc.

[0043] Furthermore, the location of the rack to be expanded in the operator's data center, the network topology of the rack to be expanded, and the network resource information of the rack to be expanded can be used as the infrastructure information of the rack to be expanded.

[0044] The above example illustrates the implementation of constructing the infrastructure information for the rack to be expanded, using the following as examples: the location of the rack to be expanded in the operator's data center, the network topology of the rack to be expanded, and the network resource information of the rack to be expanded. However, it does not mean that the infrastructure information only includes the above-mentioned infrastructure information, nor does it mean that the infrastructure information includes the above-mentioned infrastructure information.

[0045] After determining the infrastructure information of the racks to be expanded, the central service node 101 can send a server production request to the server manufacturer based on the infrastructure information and the amount of resources to be expanded, requesting the server manufacturer to produce the racks to be expanded and the target servers. Figure 2 Step 3). The rack to be expanded includes at least one target server. The server production request may include infrastructure information of the rack to be expanded and the amount of resources to be expanded.

[0046] Specifically, the central service node 101 can issue a server production request to the server manufacturer based on the amount of resources to be expanded and the infrastructure information; after receiving the server production request, the server manufacturer begins to produce the rack to be expanded and the target server in the rack according to the amount of resources to be expanded and the infrastructure information; and after the production is completed, it is transported to the maintenance party of the rack to be expanded and the target server. Figure 1 Step 3, "Delivering the Target Server". The maintenance provider for the racks to be expanded and the target server can be the maintenance provider for the central cloud.

[0047] In some embodiments, if the resource expansion type is not a full rack expansion type, the central service node 101 may send a server production request to the server manufacturer based on the amount of resources to be expanded, in order to request the server manufacturer to produce the target server. Figure 2 Step 3). In this embodiment, the target server is to be installed in an existing rack of the target edge cluster. In this embodiment, the server production request may include the amount of resources to be expanded, etc.

[0048] Specifically, the central service node 101 can issue a server production request to the server producer 30 based on the amount of resources to be expanded; after receiving the server production request, the server producer begins to produce the target server to be expanded according to the amount of resources to be expanded; and after the production is completed, it is transported to the operation and maintenance party of the target server to be expanded. Figure 1 Step 3, “Delivering the target server”. The target server is deployed in the central cloud 10 by the operations and maintenance team.

[0049] The operations and maintenance team enters the information of the target server to be expanded into the Configuration Management Database (CMDB). Figure 2 Step 4, "Information Entry into CMDB". CMDB is a logical database used to store a series of related information about hardware and software assets (often called configuration items) and the relationships between them.

[0050] For an embodiment where the resource expansion type is full rack expansion, after the rack to be expanded arrives at the operations and maintenance (O&M) party, the O&M party's O&M personnel can connect the rack to be expanded into the O&M party's data center physical network based on the aforementioned infrastructure information. Figure 2 Step 5: "Rack access to physical network".

[0051] Central service node 101 can install an operating system and deploy cloud services on the target server. Figure 1 Step 4 and Figure 2 Steps 9 and 10). Specifically, for embodiments where the resource expansion type is full rack expansion, the central service node 101 can deploy block storage services on the target server in the rack to be expanded. Figure 2 Step 9); and obtain the image file of the cloud computing service, and deploy the cloud computing service on the target server in the rack to be expanded based on the image file of the cloud computing service. Figure 2 Step 10); and configure the network for the cloud computing service. The central service node 101 can also deploy infrastructure operation and maintenance plugins on the target server. The central service node 101 can also connect the cloud computing service and block storage service to the log collection system to collect logs for the cloud computing service and block storage service. The central service node 101 can also initiate scheduled tasks for cloud computing service inspection, self-testing, and checks.

[0052] In this embodiment, the central service node 101 can also call the infrastructure operation and maintenance plugin to configure a security gateway for the target server in the rack to be expanded. Figure 2 Step 8, "Security Gateway Deployment".

[0053] For embodiments where the resource expansion type is rack-wide expansion, the central service node 101 can obtain a cloud computing service image file and deploy the cloud computing service on the target server in the rack to be expanded based on the cloud computing service image file. Figure 2Step 10, “Cloud Computing Service Deployment”, involves configuring the network for the cloud computing service. The central service node 101 can also deploy infrastructure operation and maintenance plugins on the target server. The central service node 101 can also connect the cloud computing service and block storage service to the log collection system for log collection. The central service node 101 can also initiate scheduled tasks for cloud computing service inspections, self-tests, and checks.

[0054] The cloud services deployed on the target server shown in the above embodiments are merely illustrative and do not constitute a limitation. Subsequently, as... Figure 1 As shown, the central service node 101 can send a transportation instruction to the logistics transporter 40, instructing the logistics transporter 40 to transport the target server to the target edge cluster corresponding to the target user, so that the target server can be deployed in the target edge cluster. Figure 1 Steps 5-7).

[0055] In this embodiment, the central service node in the central cloud can request the server manufacturer to produce a target server based on the target user's edge resource expansion request; then, it can install an operating system and deploy cloud services on the target server; subsequently, it can instruct the logistics provider to transport the target server to the target user's corresponding target edge cluster, thereby deploying the target server in the target edge cluster and expanding the edge nodes in the target edge cluster. This embodiment realizes a complete expansion process integrating user-initiated edge resource expansion requests, server production, transportation, and edge cluster deployment, achieving integrated and end-to-end edge node expansion. End-to-end refers to the process from when the user submits an edge resource expansion request to when the edge node expansion is implemented in the user's edge cluster.

[0056] In some embodiments of this application, such as Figure 2 As shown, before installing the operating system and deploying cloud services on the target server, for embodiments where the resource expansion type is whole-machine expansion, the central service node 101 can also perform network construction on the racks to be expanded. Figure 2 Step 6). Specifically, the central service node 101 can construct the network topology of the target server in the physical network of the operator in the central cloud based on the infrastructure information; apply for a network address for the target server in the operator's network; generate the network configuration information of the target server based on the equipment configuration specifications, network topology and network address of the target server; and provide the network configuration information of the target server to the target server after the rack to be expanded is connected to the operator's physical network.

[0057] Before installing the operating system and deploying cloud services on the target server, the central service node 101 can also perform performance testing on the target server. Figure 2Step 7). Specifically, the performance of the target server may include: the network quality of the target server, the hardware environment quality of the target server, and the software stress on the target server.

[0058] Accordingly, when performing performance testing on the target server, the central service node 101 may employ at least one of the following implementation methods:

[0059] Implementation Method 1: Detecting the network quality of the target server. Specifically, the central service node 101 can detect the correctness of the target server's network connection and network connectivity. Specifically, the central service node 101 can instruct the target server to send data packets to other devices; and collect network quality parameters of the target server based on the data packets. These network quality parameters refer to parameters reflecting network performance, and may include packet loss rate and latency, etc. Furthermore, the network quality of the target server can be determined based on its network quality parameters.

[0060] Implementation Method 2: Perform hardware environment testing on the target server. The hardware environment refers to the physical computer system comprised of the computer and its peripheral devices. Specifically, the central service node 101 can test whether each piece of hardware on the target server is malfunctioning. For example, the central service node 101 can test whether the target server's processor is malfunctioning. Specifically, the central service node 101 can instruct the target server's processor to run a set function; if the function runs successfully, it indicates that the target server's processor is normal. As another example, the central service node 101 can also test whether the target server's storage medium is malfunctioning. Specifically, the central service node 101 can perform data read and write operations on the storage medium; if the data read and write speed meets the set read and write speed requirements, it is determined that the target server's storage medium is normal, and so on.

[0061] Implementation Method 3: Perform stress testing on the target server. Specifically, the central service node 101 can input concurrent execution tasks to the target server and run the test under conditions of scarce system resources on the target server. Resources for software stress testing include internal memory, CPU availability, disk space, and network bandwidth, etc.

[0062] Furthermore, assuming the target server's performance meets the requirements, perform the aforementioned operations of installing the operating system and deploying cloud services on the target server.

[0063] In some embodiments of this application, for embodiments where the resource expansion type is rack-wide expansion, after the central service node 101 deploys cloud services on the target server, it can perform a secondary network quality test on the target server in the rack to be expanded to obtain the network quality test results. Figure 2 Step 12). Accordingly, the central service node 101 can obtain the network quality detection results ( Figure 2Step 17, "Retrieval of Secondary Network Quality Test Results"). Optionally, a secondary network quality test can be performed asynchronously on the target server in the rack to be expanded to obtain the network quality test results. Figure 2 Step 12), and asynchronously obtain the network detection results. Here, asynchronous means that it is executed asynchronously with steps 13-16.

[0064] If the network quality test results indicate that the network quality of the target server in the rack to be expanded is normal, then the subsequent operations can be performed; if the network quality test results indicate that the network quality of the target server in the rack to be expanded is abnormal, then network repair can be performed on the target server in the rack to be expanded until the network quality of the target server in the rack to be expanded is normal, and then the subsequent operations can continue.

[0065] In some embodiments, to prevent false alarms or misoperations such as being identified as abnormal and taken offline by the operation and maintenance system of the newly expanded target server before it is officially put into production, the central service node 101 may also set the target server's identifier as a blacklist label of the operation and maintenance system after deploying cloud services on the target server. Figure 2 Step 11, "Blacklisting the Target Server". The operations and maintenance system does not recognize servers with blacklist tags, thus preventing the system from misinterpreting newly expanded target servers as abnormal and triggering erroneous operations such as taking them offline. Furthermore, the central service node 101 can add an expansion lock tag to the target server's identifier, so that the target user's control system is unaware of the target server. The expansion lock tag can be implemented as: biz_status='mlock' (status is locked); lock_type='other' (lock type is other); lock_reason='cloudBoxScalOut' (lock reason is target mode expansion), etc. Based on this expansion lock tag, the target user's control system can determine that the target server has not yet been deployed to the target edge cluster and therefore is not open to the target user.

[0066] In some embodiments, the central service node 101 may also perform tagging processing on the target server on the aforementioned CMDB. Figure 2 Step 13, "Server Tagging," involves assigning a tag to the target server to indicate ownership. This allows the operations and maintenance system in the central service node 101 to apply owner-adapted operations and maintenance strategies to the target server. For example, in a target mode scenario, a target mode-specific resource tag can be assigned to the target server on the aforementioned CMDB. Accordingly, the operations and maintenance system in the central service node 101 applies a target mode-adapted operations and maintenance strategy to the target server.

[0067] In other embodiments, for information security, before instructing the logistics provider to transport the target server to the target edge cluster corresponding to the target user, the central service node 101 may also perform at least one sensitive information detection on the target server; and delete the detected sensitive information from the target server. Figure 2 Step 14 "Sensitive Information Cleanup" and Step 16 "Secondary Sensitive Information Cleanup").

[0068] Optionally, the central service node 101 may perform at least one sensitive information detection on the target server according to a pre-set sensitive information list; and determine that the information on the target server that is in the sensitive information list is sensitive information. Furthermore, the detected sensitive information may be deleted from the target server.

[0069] In this embodiment, the number of times and the order in which sensitive information is detected on the target server are not limited. Figure 2 The illustration only uses secondary sensitive information detection on the target server as an example and does not constitute a limitation. Sensitive information detection can be performed before or after any stage or operation until no sensitive information is detected on the target server. Preferably, sensitive information detection can be performed on the target server before it is shut down, and the target server can be shut down only after no sensitive information is found on the target server.

[0070] In some embodiments of this application, before sending transportation instructions to the logistics provider, the central service node 101 can also modify the network connection and DNS resolution configuration of the target server; and modify the virtual IP address of the target server to the virtual IP address of any tunnel corresponding to the availability zone of the target edge cluster, so that the target server can connect to the central cloud after being deployed to the target edge cluster. Figure 2 Step 15, "Modify network connection configuration". Here, AnyTunnel's virtual IP is a public access VIP provided within the VPC network, allowing access to all VPCs.

[0071] Optionally, after modifying the virtual IP address of the target server to the virtual IP address of any connection channel (Any Tunnel) corresponding to the availability zone of the target edge cluster, sensitive information detection can be performed on the target server again until no sensitive information is found on the target server. Figure 2 Step 16, "Secondary Cleanup of Sensitive Information". After that, the target server can be shut down.

[0072] Optionally, the central service node 101 can remotely control the shutdown of the target server. Figure 2Step 18, "Remote Shutdown". In some embodiments, the central service node 101 can remotely control the shutdown of the target server's cloud computing service and block storage service; and after the target server's cloud computing service and block storage service are shut down, it can remotely control the shutdown of the target server. The operation and maintenance personnel of the target server's operator can disconnect the network and power to the target server in the operator's data center. Figure 2 Step 19, "Power off and network disconnected." Afterwards, the target server can be packaged and delivered to the target user. Figure 2 Step 20, “Packaging and Delivery”.

[0073] Subsequently, the central service node 101 can send a transportation instruction to the logistics transporter 40, instructing the logistics transporter 40 to transport the target server to the target edge cluster corresponding to the target user. Figure 2 Step 21, "Logistics Transportation".

[0074] Staff working on the target edge cluster or those maintaining the target server can deploy the target server to the target edge cluster. Figure 2 Step 22: "Deploy the target server to the target edge cluster"); and provide physical network connection and power to the target server.

[0075] Furthermore, the central service node 101 can perform network configuration and network debugging on the target server and the rack where the target server is located until the target server and the rack where the target server is located are connected to the central cloud. Figure 2 Step 23, "Network Configuration and Debugging". For the embodiment of full rack expansion, the rack where the target server is located is the rack to be expanded mentioned above; for the embodiment of non-full rack expansion, the target server is an existing rack in the target edge cluster.

[0076] In some embodiments, for a target server that is a computing node in target mode, the central service node 101 may also switch the network mode of the target server to target mode, so that the data packets of the target server can be transmitted to the central service node by the security gateway through a dedicated network. Figure 2 Step 24, “Security Gateway Traffic Redirection”. The dedicated network can be a dedicated communication network between the target mode compute node and the central cloud, such as a VPC, VPN, or dedicated network cable. Specifically, switching the network mode of the target server to the target mode allows the security gateway to proxy the target server's data packets and transmit them to the central service node 101 via the dedicated network.

[0077] In some embodiments, the central service node 101 can also configure environmental monitoring for the target server. Figure 2Step 25, “Environmental Monitoring Configuration,” will synchronize the environmental monitoring configuration information to the operation and maintenance system in the central service node. Environmental monitoring refers to the centralized monitoring of the target server and its environmental variables.

[0078] In some embodiments of this application, after the target server is deployed in the target edge cluster, the central service node 101 can also detect the network quality of the target server in the target edge cluster. Figure 2 Step 26, "Network Quality Testing," and the use of a cloud-edge collaboration approach to verify the central service node's management capabilities over the target server. Figure 2 Step 27, “Cloud-Edge Collaborative Verification”.

[0079] When the central service node 101 detects the network quality of the target server in the target edge cluster, it can control the target server to send probe data packets to other devices; and collect the network quality parameters of the target server based on the probe data packets; then, it can determine the network quality of the target server in the target edge cluster based on the network quality parameters of the target server.

[0080] In some embodiments, the central service node 101 may employ a cloud-edge collaboration approach to verify its management capabilities for the target server. Specifically, the central service node 101 may use a cloud-edge collaboration approach to verify its lifecycle management capabilities for the cloud computing services on the target server. For example, the central service node 101 may create, start, and destroy cloud computing services on the target server to verify its lifecycle management capabilities for the cloud computing services on the target server. And / or, the central service node 101 may also use a cloud-edge collaboration approach to verify the operational capabilities of the operation and maintenance system within the central service node for the target server. For example, the central service node 101 may perform operation and maintenance operations on the target server and obtain the operation and maintenance operation results; if the operation and maintenance operation results indicate that the operation and maintenance system is functioning normally, then it is determined that the operation and maintenance system's operational capabilities for the target server meet the standards.

[0081] In actual use, the target user can also perform acceptance testing on the target server, etc. Figure 2 Step 28, “Target User Acceptance”. The target user acceptance process is not covered by this application, therefore, it will not be described in detail.

[0082] After the above operations are completed and all performance tests meet the standards, the central service node 101 can remove the blacklist label of the operation and maintenance system corresponding to the identifier of the target server. Figure 2Step 29, "Remove from Blacklist". This allows the target server's operations and maintenance system to identify the target server. Furthermore, an expansion lock tag can be added to the target server's identifier, allowing the target user's control system to detect the target server and make it available for user use.

[0083] It is worth noting that the above Figure 2 The processing flow for expansions without the label "(Full rack)" is the common process for both full rack expansions and non-full rack expansions; the processing flow for expansions with the label "(Full rack)" is a unique process for full rack expansions.

[0084] The above Figure 2 The provided edge node expansion process enables end-to-end edge node expansion. The entire edge node expansion process integrates hardware installation, software deployment, network setup, security compliance, logistics relocation, and cloud-edge collaborative verification, achieving integrated expansion of edge cluster nodes. Furthermore, the edge node expansion method provided in this application is also compatible with both full-rack and non-rack expansion.

[0085] In addition to the aforementioned edge cloud system, this application also provides an edge resource expansion method. The edge resource expansion method provided in this application is described below by way of example.

[0086] Figure 3 This is a flowchart illustrating a method for scaling up edge resources as provided in an embodiment of this application. This scaling up method is applicable to central service nodes in a centralized cloud. Figure 3 As shown, this capacity expansion method mainly includes:

[0087] 301. Obtain the edge resource expansion request provided by the target user.

[0088] 302. Based on the edge resource expansion request, provide a server production request to the server manufacturer to request the server manufacturer to produce the target server.

[0089] 303. Install the operating system and deploy cloud services on the target server.

[0090] 304. Send a transportation instruction to the logistics provider to instruct the logistics provider to transport the target server to the target edge cluster corresponding to the target user, so that the target server can be deployed in the target edge cluster.

[0091] In this embodiment, the central service node can provide edge node expansion functionality. Specifically, users of the edge cluster to be expanded (defined as target users) can submit edge resource expansion requests to the central cloud. These requests may include: the resource expansion type and the amount of resources to be expanded. Resource expansion types include: full rack expansion and non-full rack expansion.

[0092] For the central service node, in step 301, the edge resource expansion request provided by the target user can be obtained; and in step 302, based on the edge resource expansion request, a server production request is provided to the server producer to request the server producer to produce the target server.

[0093] Specifically, the resource expansion type and the amount of resources to be expanded can be obtained from edge resource expansion requests. Furthermore, if the resource expansion type is not a full rack expansion, the infrastructure information of the rack to be expanded can be constructed. The rack to be expanded includes at least one target server.

[0094] Specifically, the location of the rack to be expanded within the data center of the operator of the rack to be expanded can be determined based on the location information of the existing racks of the target edge cluster within the data center of the operator of the rack to be expanded. Here, the target edge cluster is the edge cluster belonging to the target user who provided the edge resource expansion request.

[0095] For the target model, the existing racks of the target edge cluster are operated by the central cloud. Logical numbers can be assigned to the racks in the target edge cluster, and logical rack slots can be created in the operator's data center. Then, based on the location information of the existing racks in the target edge cluster within the operator's data center, the locations of the racks to be expanded within the operator's data center are planned.

[0096] Furthermore, based on the network topology of the existing cabinets of the target edge cluster in the operator's data center, the network topology of the cabinets to be expanded can be determined; and the network requirements of the target users can be obtained from edge resource expansion requests; furthermore, based on the network requirements of the target users and the network resources provided by the operator, the network resource information of the cabinets to be expanded can be determined. Network resource information refers to the resources required for the device to achieve network communication, which may include: network segments, routing and DNS, etc., and may also include the device's network mode.

[0097] Specifically, the required number of IP addresses (N) for the target user can be obtained from the target user's network requirements. Furthermore, N unassigned IP addresses can be identified from the network segments provided by the operations and maintenance (O&M) provider as the IP addresses for the racks to be expanded. Additionally, the routing information from the O&M provider can be used as the routing information for the racks to be expanded. Finally, the network mode selected by the target user can be obtained from their network requirements and used as the network mode for the racks to be expanded.

[0098] Furthermore, the location of the rack to be expanded in the operator's data center, the network topology of the rack to be expanded, and the network resource information of the rack to be expanded can be used as the infrastructure information of the rack to be expanded.

[0099] The above example illustrates the implementation of constructing the infrastructure information for the rack to be expanded, using the following as examples: the location of the rack to be expanded in the operator's data center, the network topology of the rack to be expanded, and the network resource information of the rack to be expanded. However, it does not mean that the infrastructure information only includes the above-mentioned infrastructure information, nor does it mean that the infrastructure information includes the above-mentioned infrastructure information.

[0100] After determining the infrastructure information of the rack to be expanded, a server production request can be submitted to the server manufacturer based on the infrastructure information and the amount of resources to be expanded. This request requests the manufacturer to produce the rack to be expanded and the target server. The rack to be expanded includes at least one target server. The server production request includes: the infrastructure information of the rack to be expanded and the amount of resources to be expanded.

[0101] Specifically, a server production request can be issued to the server manufacturer based on the amount of resources to be expanded and the infrastructure information. After receiving the server production request, the server manufacturer will start producing the rack to be expanded and the target server in the rack according to the amount of resources to be expanded and the infrastructure information. After the production is completed, the rack will be transported to the maintenance party of the rack to be expanded.

[0102] In some embodiments, if the resource expansion type is not a full rack expansion type, a server production request can be provided to the server manufacturer based on the amount of resources to be expanded, requesting the server manufacturer to produce the target server. In this embodiment, the target server is to be installed in an existing rack of the target edge cluster. The server production request includes the amount of resources to be expanded, etc.

[0103] Specifically, a server production request can be issued to the server producer based on the amount of resources to be expanded. After receiving the server production request, the server producer will begin producing the target server to be expanded according to the amount of resources to be expanded. After production is completed, the server will be delivered to the operation and maintenance team of the target server. The operation and maintenance team of the target server is deployed in the central cloud.

[0104] The operations and maintenance (O&M) team enters the information of the target server to be expanded into the CMDB. For an embodiment where the resource expansion type is full rack expansion, after the rack to be expanded arrives at the O&M team, the O&M personnel can connect the rack to be expanded into the physical network of the O&M team's data center based on the infrastructure information constructed above.

[0105] In step 303, an operating system can be installed and cloud services deployed on the target server. Specifically, for embodiments where the resource expansion type is rack-wide expansion, block storage services can be deployed on the target server in the rack to be expanded; and an image file of the cloud computing service can be obtained. Based on the image file, the cloud computing service is deployed on the target server in the rack to be expanded; and network configuration is performed for the cloud computing service. Furthermore, infrastructure operation and maintenance plugins can also be deployed on the target server. Of course, the cloud computing service and block storage service can also be connected to a log collection system to collect logs from the cloud computing service and block storage service; and scheduled tasks, self-tests, and checks of the cloud computing service can be initiated.

[0106] In this embodiment, the infrastructure operation and maintenance plugin can also be invoked to configure a security gateway for the target server in the rack to be expanded.

[0107] For embodiments where the resource expansion type is rack-wide expansion, in cases where the expansion type is not rack-wide expansion, an image file of the cloud computing service can be obtained. Based on the image file, the cloud computing service is deployed on the target server in the rack to be expanded, and network configuration is performed for the cloud computing service. Furthermore, infrastructure operation and maintenance plugins can be deployed on the target server, and the cloud computing service and block storage service can be connected to a log collection system to collect logs from the cloud computing service and block storage service, as well as to initiate scheduled tasks, self-tests, and checks for the cloud computing service.

[0108] The cloud services deployed on the target server shown in the above embodiments are merely illustrative and do not constitute a limitation. Subsequently, in step 304, a transportation instruction can be sent to the logistics provider to instruct them to transport the target server to the target edge cluster corresponding to the target user, so that the target server can be deployed on the target edge cluster.

[0109] In this embodiment, the central service node in the central cloud can request the server manufacturer to produce a target server based on the target user's edge resource expansion request; then, it can install an operating system and deploy cloud services on the target server; subsequently, it can instruct the logistics provider to transport the target server to the target user's corresponding target edge cluster, thereby deploying the target server in the target edge cluster and expanding the edge nodes in the target edge cluster. This embodiment realizes a complete expansion process integrating user-initiated edge resource expansion requests, server production, transportation, and edge cluster deployment, achieving integrated and end-to-end edge node expansion. End-to-end refers to the process from when the user submits an edge resource expansion request to when the edge node expansion is implemented in the user's edge cluster.

[0110] In some embodiments of this application, before installing the operating system and deploying cloud services on the target server, for embodiments where the resource expansion type is full-machine expansion, network construction can also be carried out on the rack to be expanded. Specifically, based on infrastructure information, the network topology of the target server in the physical network of the rack's operator can be constructed; and a network address can be applied for for the target server in the operator's network; and network configuration information of the target server can be generated based on the equipment configuration specifications, network topology, and the target server's network address; and after the rack to be expanded is connected to the operator's physical network, the network configuration information of the target server is provided to the target server.

[0111] Before installing the operating system and deploying cloud services on the target server, performance testing can be performed. Specifically, the target server's performance can include: network quality, hardware environment quality, and software stress.

[0112] Alternatively, when performing performance testing on the target server, at least one of the following implementation methods can be used:

[0113] Implementation Method 1: Detect the network quality of the target server. Specifically, the correctness of the target server's network connection and network connectivity can be detected. Specifically, the target server can be instructed to send data packets to other devices; and network quality parameters of the target server can be collected based on the data packets. These network quality parameters reflect network performance and may include packet loss rate and latency, etc. Furthermore, the network quality of the target server can be determined based on its network quality parameters.

[0114] Implementation Method 2: Perform hardware environment testing on the target server. The hardware environment refers to the physical computer system comprised of the computer and its peripherals. Specifically, it can test whether each piece of hardware on the target server is malfunctioning. For example, it can test whether the target server's processor is malfunctioning. Specifically, the target server's processor can be instructed to run a set function; if the function runs successfully, it indicates that the target server's processor is normal. As another example, it can also test whether the target server's storage medium is malfunctioning. Specifically, data can be read and written to the storage medium; if the data read and write speed meets the set read and write speed requirements, it is determined that the target server's storage medium is normal, and so on.

[0115] Implementation Method 3: Perform stress testing on the target server. Specifically, concurrent execution tasks can be input to the target server, and the test can be run under conditions of limited system resources. Resources for software stress testing include internal memory, CPU availability, disk space, and network bandwidth.

[0116] Furthermore, assuming the target server's performance meets the requirements, perform the aforementioned operations of installing the operating system and deploying cloud services on the target server.

[0117] In some embodiments of this application, for embodiments where the resource expansion type is full rack expansion, after deploying cloud services on the target server and before sending transportation instructions to the logistics provider, a secondary network quality test can be performed on the target server in the rack to be expanded, and the network quality test results of the secondary test can be obtained. If the network quality test results indicate that the network quality of the target server in the rack to be expanded is normal, subsequent operations can be performed; if the network quality test results indicate that the network quality of the target server in the rack to be expanded is abnormal, network repair can be performed on the target server in the rack to be expanded until the network quality of the target server in the rack to be expanded is normal, and subsequent operations can continue to be performed.

[0118] In some embodiments, to prevent false alarms or misoperations such as being identified as abnormal and taken offline by the operations and maintenance (O&M) system before the newly expanded target server is officially put into production, the target server's identifier can be set as a blacklist label for the O&M system after the cloud service is deployed on the target server and before the transportation instructions are sent to the logistics provider. The O&M system does not recognize servers with blacklist labels, thereby preventing the O&M system from identifying the newly expanded target server as abnormal and triggering misoperations such as being taken offline. Furthermore, an expansion lock label can be added to the target server's identifier so that the target user's control system is unaware of the target server. Based on this expansion lock label, the target user's control system can determine that the target server has not yet been deployed to the target edge cluster and is therefore not open to the target user.

[0119] In some embodiments, the target server can also be tagged on the CMDB. The tag is used to represent the ownership of the target server, so that the operation and maintenance system in the central service node can adopt the owner-adapted operation and maintenance strategy to perform operation and maintenance on the target server.

[0120] In other embodiments, for information security, after deploying cloud services on the target server and before sending transportation instructions to the logistics provider, at least one sensitive information detection can be performed on the target server; and the detected sensitive information can be deleted from the target server.

[0121] Optionally, the target server can be subjected to at least one sensitive information detection according to a pre-defined sensitive information list; and the information on the target server that is in the sensitive information list can be identified as sensitive information. Furthermore, the detected sensitive information can be deleted from the target server.

[0122] In this embodiment, the number of times and the order in which sensitive information detection is performed on the target server are not limited. Sensitive information detection can be performed before or after any stage or operation until no sensitive information is detected on the target server. Preferably, sensitive information detection can be performed on the target server before it is shut down, and the target server can be shut down after no sensitive information is found on the target server.

[0123] In some embodiments of this application, after deploying cloud services on the target server and before sending transportation instructions to the logistics provider, the network connection and DNS resolution configuration of the target server can be modified; and the virtual IP address of the target server can be modified to the virtual IP address of any tunnel corresponding to the availability zone of the target edge cluster, so that the target server can connect to the central cloud after being deployed to the target edge cluster. The virtual IP of the AnyTunnel is a public access VIP provided in the VPC network, which can access all VPCs.

[0124] Optionally, after modifying the virtual IP address of the target server to the virtual IP address of any tunnel corresponding to the availability zone of the target edge cluster, the target server can be checked for sensitive information again until no sensitive information is found on the target server. Afterwards, the target server can be shut down.

[0125] Optionally, the target server can be remotely shut down. In some embodiments, the cloud computing service and block storage service of the target server can be remotely shut down; and the target server can be remotely shut down after the cloud computing service and block storage service of the target server are shut down. The operation and maintenance personnel of the target server's operator can disconnect the network and power to the target server in the operator's data center.

[0126] Afterwards, a transportation instruction can be sent to the logistics provider, instructing them to transport the target server to the target edge cluster corresponding to the target user. Staff at the target edge cluster or those maintaining the target server can then deploy the target server to the target edge cluster and provide physical network connectivity and power.

[0127] Furthermore, after the target server is deployed in the target edge cluster, network configuration and debugging can be performed on the target server and the rack where it is located until the target server and the rack where it is located are connected to the central cloud. In the embodiment of full rack expansion, the rack where the target server is located is the rack to be expanded mentioned above; in the embodiment of non-full rack expansion, the target server is an existing rack in the target edge cluster.

[0128] In some embodiments, for computing nodes where the target server is in target mode, the network mode of the target server can also be switched to target mode so that the data packets of the target server can be transmitted to the central service node by the security gateway through a dedicated network.

[0129] In some embodiments, after the target server is deployed on the target edge cluster, environmental monitoring can be configured on the target server, and the environmental monitoring configuration information can be synchronized to the operation and maintenance system in the central service node. Environmental monitoring refers to centralized monitoring of the target server and its environmental variables.

[0130] In some embodiments of this application, after the target server is deployed in the target edge cluster, the network quality of the target server in the target edge cluster can be detected, and the management capability of the central service node over the target server can be verified.

[0131] When detecting the network quality of the target server in the target edge cluster, the target server can be controlled to send probe data packets to other devices; and the network quality parameters of the target server can be collected based on the probe data packets; then, the network quality of the target server in the target edge cluster can be determined based on the network quality parameters of the target server.

[0132] In some embodiments, a cloud-edge collaboration approach can be used to verify the central service node's management capabilities over the target server. Specifically, its ability to manage the lifecycle of cloud computing services on the target server can be verified. For example, cloud computing services can be created, started, and destroyed on the target server to verify the lifecycle management capabilities of the target server's cloud computing services. And / or, the operational capabilities of the operation and maintenance system in the central service node over the target server can also be verified.

[0133] In actual use, the target user may also conduct acceptance testing on the target server. The target user's acceptance process is not covered by this application and therefore will not be elaborated upon.

[0134] After the above operations are completed and all performance tests meet the standards, the blacklist tag corresponding to the target server's identifier can be removed from the operation and maintenance system's list. This allows the target server's operation and maintenance system to identify the target server. Furthermore, an expansion lock tag can be added to the target server's identifier, allowing the target user's control system to detect the target server and open it to user use.

[0135] This application provides a complete process for edge node expansion, integrating hardware installation, software deployment, network setup, security compliance, logistics relocation, and cloud-edge collaborative verification, thus achieving integrated expansion of edge cluster nodes. Furthermore, the edge node expansion method provided in this application is also compatible with both full-rack and non-rack expansion.

[0136] It should be noted that the execution subject of each step of the method provided in the above embodiments can be the same device, or the method can be executed by different devices. For example, the execution subject of steps 301 and 302 can be device A; or the execution subject of step 301 can be device A, and the execution subject of step 302 can be device B; and so on.

[0137] Furthermore, some processes described in the above embodiments and accompanying drawings include multiple operations that appear in a specific order. However, it should be clearly understood that these operations may not be executed in the order they appear herein, or they may be executed in parallel. The operation numbers, such as 301, 302, etc., are merely used to distinguish different operations and do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed sequentially or in parallel.

[0138] Accordingly, embodiments of this application also provide a computer-readable storage medium storing computer instructions, which, when executed by one or more processors, cause one or more processors to perform the steps in the above-described method for expanding edge resources.

[0139] Figure 4 This is a schematic diagram of the computing device provided in an embodiment of this application. The computing device provided in this embodiment can be implemented as a central service node in an edge cloud system. The central service node is deployed in a central cloud. Figure 4 As shown, the computing device includes: a memory 40a, a processor 40b, and a communication component 40c; wherein, the memory 40a is used to store computer programs.

[0140] The processor 40b is coupled to the memory 40a and the communication component 40c, and is used to execute a computer program for: obtaining an edge resource expansion request provided by a target user; based on the edge resource expansion request, sending a server production request to the server manufacturer via the communication component 40c to request the server manufacturer to produce a target server; installing an operating system and deploying cloud services on the target server; and sending a transportation instruction to a logistics provider via the communication component 40c to instruct the logistics provider to transport the target server to the target edge cluster corresponding to the target user, so that the target server can be deployed in the target edge cluster.

[0141] Optionally, when processor 40b provides a server production request to the server manufacturer based on the edge resource expansion request, it is specifically used to: obtain the resource expansion type and the amount of resources to be expanded from the edge resource expansion request; if the resource expansion type is a rack-wide expansion type, construct the infrastructure information of the rack to be expanded; based on the infrastructure information and the amount of resources to be expanded, provide a server production request to the server manufacturer through communication component 40c, requesting the server manufacturer to produce the rack to be expanded and the target server; the target server is to be deployed in the rack to be expanded; and if the resource expansion type is not a rack-wide expansion type, based on the amount of resources to be expanded, provide a server production request to the server manufacturer through communication component 40c, requesting the server manufacturer to produce the target server; the target server is to be deployed in the existing rack of the target edge cluster.

[0142] Furthermore, when constructing the infrastructure information of the rack to be expanded, the processor 40b specifically performs the following: determining the location of the rack to be expanded in the operator's data center based on the location information of the existing racks of the target edge cluster in the operator's data center; determining the network topology of the rack to be expanded based on the network topology of the existing racks of the target edge cluster in the operator's data center; obtaining the network requirements of the target user from the edge resource expansion request; determining the network resource information of the rack to be expanded based on the network requirements of the target user and the network resources provided by the operator; and using the location of the rack to be expanded in the operator's data center, the network topology of the rack to be expanded, and the network resource information of the rack to be expanded as the infrastructure information of the rack to be expanded.

[0143] In some embodiments, the processor 40b is further configured to: when the resource expansion type is rack expansion, construct the network topology of the target server in the physical network of the operator of the target server based on the infrastructure information; apply for a network address for the target server in the network segment of the operator; generate network configuration information of the target server based on the equipment configuration specifications, network topology and network address; and after the rack to be expanded is connected to the physical network of the operator, provide the network configuration information of the target server to the target server through the communication component 40c.

[0144] Optionally, the processor 40b is also used to: perform performance testing on the target server before installing the operating system and deploying cloud services on the target server; and, if the performance of the target server is found to be up to standard, perform the operation of installing the operating system and deploying cloud services on the target server.

[0145] Furthermore, when performing performance testing on the target server, the processor 40b is specifically used for: detecting the network quality of the target server; and / or, detecting the hardware environment of the target server; and / or, performing stress testing on the target server.

[0146] In some embodiments, when the processor 40b deploys a cloud service on the target server, it is specifically configured to: deploy a block storage service on the target server in the rack to be expanded when the expansion type is a full rack expansion type; obtain an image file of the cloud computing service; deploy the cloud computing service on the target server in the rack to be expanded according to the image file of the cloud computing service, and perform network configuration for the cloud computing service; and deploy an infrastructure operation and maintenance plugin on the target server; or, when the expansion type is not a full rack expansion type, obtain an image file of the cloud computing service; deploy the cloud computing service on the target server in the rack to be expanded according to the image file of the cloud computing service, and perform network configuration for the cloud computing service; and deploy an infrastructure operation and maintenance plugin on the target server.

[0147] Furthermore, processor 40b is also used to: in the case of full rack expansion, call the infrastructure operation and maintenance plugin to configure a security gateway for the target server in the rack to be expanded.

[0148] Optionally, the processor 40b is also used to: perform a secondary network quality test on the target server after deploying cloud services on the target server in the case of a full rack expansion, and before sending a transportation instruction to the logistics provider, and to obtain the network quality test results of the secondary test.

[0149] Optionally, the processor 40b is also used to: after deploying cloud services on the target server and before sending transportation instructions to the logistics provider, set the identifier of the target server to a blacklist label of the operation and maintenance system so that the operation and maintenance system in the central service node does not recognize the target server; and add an expansion lock label to the identifier of the target server so that the control system of the target user is unaware of the target server.

[0150] Optionally, the processor 40b is also used to: after the target server is deployed on the target edge cluster, remove the blacklist label of the operation and maintenance system corresponding to the identifier of the target server so that the operation and maintenance system can identify the target server; and remove the expansion lock label added to the identifier of the target server so that the control system of the target user can perceive the target server.

[0151] In other embodiments, the processor 40b is also configured to: perform at least one sensitive information detection on the target server after deploying the cloud service on the target server and before sending a transportation instruction to the logistics provider to the target server; and delete the detected sensitive information from the target server.

[0152] Optionally, the processor 40b is also configured to: modify the network connection and domain name system resolution configuration of the target server after deploying the cloud service on the target server and before sending transportation instructions to the logistics carrier; and modify the virtual IP address of the target server to the virtual IP address of any connection channel corresponding to the availability zone of the target edge cluster.

[0153] In some other embodiments, the processor 40b is further configured to: after the target server is deployed in the target edge cluster, perform network configuration and network debugging on the target server and the rack where the target server is located until the target server and the rack where the target server is located are connected to the central cloud; switch the network mode of the target server to the target mode so that the data packets of the target server can be transmitted to the central service node through the security gateway via a dedicated network; configure environmental monitoring on the target server and synchronize the environmental monitoring configuration information to the operation and maintenance system in the central service node; detect the network quality of the target server in the target edge cluster; and verify the management capability of the central service node over the target server using a cloud-edge collaboration method.

[0154] Optionally, when the processor 40b uses a cloud-edge collaboration approach to detect the network quality of the target server in the target edge cluster, it is specifically used to: verify the lifecycle management capability of the central service node for the target server's cloud computing services using a cloud-edge collaboration approach; and / or, verify the operation and maintenance capability of the operation and maintenance system in the central service node for the target server using a cloud-edge collaboration approach.

[0155] In some alternative implementations, such as Figure 4 As shown, the computing device may further include components such as a power supply component 40d. In some embodiments, the computing device may be implemented as a terminal device such as a computer, mobile phone, or workstation. Accordingly, the computing device may further include optional components such as a display component 40e and an audio component 40f. Figure 4 The diagram only shows some components and does not mean that the computing device must contain them. Figure 4 The inclusion of all components does not imply that a computing device can only include... Figure 4 The components shown.

[0156] In this embodiment, the central service node in the central cloud can request the server manufacturer to produce a target server based on the target user's edge resource expansion request; then, it can install an operating system and deploy cloud services on the target server; subsequently, it can instruct the logistics provider to transport the target server to the target edge cluster corresponding to the target user, so as to deploy the target server in the target edge cluster and realize the expansion of edge nodes in the target edge cluster. This embodiment realizes a full-link expansion process that integrates user-initiated edge resource expansion requests, server production, transportation, and edge cluster deployment, achieving integrated and end-to-end edge node expansion.

[0157] In this embodiment, the memory is used to store computer programs and can be configured to store various other data to support operation on its host device. The processor can execute the computer programs stored in the memory to implement corresponding control logic. The memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random-Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Electrically Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0158] In the embodiments of this application, the processor can be any hardware processing device capable of executing the above-described method logic. Optionally, the processor can be a central processing unit (CPU), a graphics processing unit (GPU), or a microcontroller unit (MCU); it can also be a programmable device such as a field-programmable gate array (FPGA), a programmable array logic (PAL), a general array logic (GAL), or a complex programmable logic device (CPLD); or an application-specific integrated circuit (ASIC) chip; or an advanced RISC machine (ARM) or system-on-chip (SoC), etc., but is not limited thereto.

[0159] In this embodiment, the communication component is configured to facilitate wired or wireless communication between its host device and other devices. The device housing the communication component can access wireless networks based on communication standards, such as Wireless Fidelity (WiFi), 2G or 3G, 4G, 5G, or combinations thereof. In one exemplary embodiment, the communication component receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In another exemplary embodiment, the communication component may also be implemented based on Near Field Communication (NFC), Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra Wide Band (UWB), Bluetooth (BT), or other technologies.

[0160] In embodiments of this application, the display component may include a liquid crystal display (LCD) and a touch panel (TP). If the display component includes a touch panel, the display component can be implemented as a touchscreen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of touch or swipe actions but also the duration and pressure associated with the touch or swipe operation.

[0161] In this embodiment, a power supply component is configured to provide power to various components of the device in which it resides. The power supply component may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device in which the power supply component resides.

[0162] In embodiments of this application, the audio component can be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC), which is configured to receive external audio signals when the device containing the audio component is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals can be further stored in memory or transmitted via a communication component. In some embodiments, the audio component also includes a speaker for outputting audio signals. For example, in devices with voice interaction capabilities, voice interaction with the user can be achieved through the audio component.

[0163] It should be noted that the terms "first" and "second" in this article are used to distinguish different messages, devices, modules, etc., and do not represent a chronological order, nor do they limit "first" and "second" to different types.

[0164] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, compact disc read-only memory (CD-ROM), optical storage, etc.) containing computer-usable program code.

[0165] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (or systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0166] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0167] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0168] In a typical configuration, a computing device includes one or more processors (such as a CPU), input / output interfaces, network interfaces, and memory.

[0169] Memory may include non-persistent storage in computer-readable media, such as random-access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0170] Computer storage media are readable storage media, also known as removable media. Removable and non-removable media can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random-access memory (SRAM), dynamic random-access memory (DRAM), other types of random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, Digital Video Disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media do not include transient computer-readable media, such as modulated data signals and carrier waves.

[0171] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the aforementioned element.

[0172] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for expanding the capacity of edge resources, characterized in that, Applicable to central service nodes in a central cloud; the method includes: Obtain the edge resource expansion request provided by the target user; the edge resource expansion request includes: the amount of resources to be expanded; Based on the edge resource expansion request, a server production request is provided to the server producer to request the server producer to produce the target server based on the amount of resources to be expanded. Install the operating system and deploy cloud services on the target server; Send a transport instruction to the logistics provider to instruct the logistics provider to transport the target server to the target edge cluster corresponding to the target user, so that the target server can be deployed in the target edge cluster.

2. The method according to claim 1, characterized in that, The step of providing a server production request to the server manufacturer based on the edge resource expansion request includes: From the edge resource expansion request, obtain the resource expansion type and the amount of resources to be expanded; When the resource expansion type is a full rack expansion type, the infrastructure information of the rack to be expanded is constructed; based on the infrastructure information and the amount of resources to be expanded, a server production request is provided to the server manufacturer to request the server manufacturer to produce the rack to be expanded and the target server; the target server is to be deployed in the rack to be expanded. When the resource expansion type is not a full rack expansion type, a server production request is provided to the server manufacturer based on the amount of resources to be expanded, requesting the server manufacturer to produce the target server; the target server is to be deployed in the existing rack of the target edge cluster.

3. The method according to claim 2, characterized in that, The infrastructure information for constructing the rack to be expanded includes: Based on the location information of the existing racks of the target edge cluster in the data center of the central cloud, determine the location of the rack to be expanded in the data center of the central cloud's operator. Based on the network topology of the existing cabinets of the target edge cluster in the operator's data center, determine the network topology of the cabinets to be expanded. Obtain the network requirements of the target user from the edge resource expansion request; determine the network resource information of the rack to be expanded based on the network requirements of the target user and the network resources provided by the operator; The location of the rack to be expanded in the operator's data center, the network topology of the rack to be expanded, and the network resource information of the rack to be expanded are used as the infrastructure information of the rack to be expanded.

4. The method according to claim 2, characterized in that, When the resource expansion type is a full rack expansion type, the method further includes: Based on the infrastructure information, construct the network topology of the target server in the physical network of the target server's operator; Within the network segment of the operation and maintenance party, apply for a network address for the target server; Based on the device configuration specifications, the network topology, and the network address, generate the network configuration information of the target server; After the rack to be expanded is connected to the physical network of the operator, the network configuration information of the target server is provided to the target server.

5. The method according to any one of claims 1-4, characterized in that, Before installing the operating system and deploying cloud services on the target server, the following steps are also included: Perform performance testing on the target server; If the performance of the target server is found to meet the requirements, the operation of installing the operating system and deploying cloud services on the target server will be performed. The performance testing of the target server includes: Detect the network quality of the target server; and / or, perform hardware environment detection on the target server; and / or, perform stress testing on the target server.

6. The method according to claim 2, characterized in that, Deploying cloud services on the target server includes: When the expansion type is a full rack expansion, deploy a block storage service on the target server in the rack to be expanded; obtain an image file of a cloud computing service; deploy the cloud computing service on the target server in the rack to be expanded according to the image file of the cloud computing service, and perform network configuration for the cloud computing service; deploy an infrastructure operation and maintenance plugin on the target server. or, When the expansion type is not a full rack expansion type, obtain the image file of the cloud computing service; based on the image file of the cloud computing service, deploy the cloud computing service on the target server in the rack to be expanded, and perform network configuration for the cloud computing service; deploy the infrastructure operation and maintenance plugin on the target server.

7. The method according to claim 6, characterized in that, When the expansion type is a full rack expansion type, the method further includes: The infrastructure operation and maintenance plugin is invoked to configure a security gateway for the target server in the rack to be expanded.

8. The method according to claim 2, characterized in that, After deploying the cloud service on the target server and before sending transportation instructions to the logistics provider, the method further includes: When the expansion type is a full rack expansion type, the network quality of the target server is tested a second time, and the network quality test results of the second test are obtained. And / or, Perform at least one sensitive information detection on the target server; and delete the detected sensitive information from the target server.

9. The method according to any one of claims 1-4 and 6-8, characterized in that, After deploying the cloud service on the target server and before sending transportation instructions to the logistics provider, the method further includes: The identifier of the target server is set as a blacklist label in the operation and maintenance system of the central service node, so that the operation and maintenance system does not recognize the target server; Add an expansion lock tag to the identifier of the target server so that the target user's control system is unaware of the target server; Furthermore, after the target server is deployed in the target edge cluster, the method further includes: Remove the blacklist label of the operation and maintenance system corresponding to the identifier of the target server so that the operation and maintenance system can identify the target server; Remove the identifier of the target server and add an expansion lock tag so that the target user's control system can detect the target server.

10. The method according to any one of claims 1-4 and 6-8, characterized in that, After deploying the cloud service on the target server and before sending transportation instructions to the logistics provider, the method further includes: Modify the network connection and Domain Name System (DNS) resolution configuration of the target server; Modify the virtual IP address of the target server to the virtual IP address of any connection channel corresponding to the availability zone of the target edge cluster.

11. The method according to any one of claims 1-4 and 6-8, characterized in that, After the target server is deployed in the target edge cluster, the method further includes: Perform network configuration and network debugging on the target server and the rack where the target server is located until the target server and the rack where the target server is located are connected to the central cloud; The network mode of the target server is switched to target mode so that the data packets of the target server can be transmitted to the central service node through a dedicated network by the entire gateway; the target mode is the mode in which the target server is managed and maintained by the central cloud. Configure environmental monitoring for the target server and synchronize the environmental monitoring configuration information to the operation and maintenance system in the central service node; The network quality of the target server in the target edge cluster is detected; and the management capability of the central service node over the target server is verified using a cloud-edge collaboration approach.

12. An edge cloud system, characterized in that, include: A central cloud, and at least one edge cluster connected to the central cloud network; The central cloud includes: a central service node; the edge cluster includes: a server rack and edge nodes deployed in the server rack; The central service node is used to execute the steps in the method according to any one of claims 1-11.

13. A computing device, characterized in that, include: Memory, processor, and communication components; wherein the memory is used to store computer programs; The processor is coupled to the memory and the communication component for executing the computer program to perform the steps of the method according to any one of claims 1-11.

14. A computer-readable storage medium storing computer instructions, characterized in that, When the computer instructions are executed by one or more processors, the one or more processors are caused to perform the steps of the method according to any one of claims 1-11.

Images