Edge-resource expansion method, edge cloud system, device, and storage medium
By obtaining user requests in the central cloud, producing and deploying target servers, and transporting them to edge clusters, the problem of edge node expansion under traditional cloud computing mode is solved, and efficient expansion and capacity improvement of edge nodes is achieved.
Patent Information
- Application Number
- PCT/CN2024/088057
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-08
- Filing Date
- 2024-04-16
- Publication Date
- 2024-11-14
AI Technical Summary
The traditional centralized cloud computing model is difficult to meet the needs of massive mobile and IoT devices, resulting in an increase in the expansion of edge nodes and it is difficult for the existing technology to achieve efficient expansion of edge nodes.
Provide an edge resource expansion method, obtain user requests through the central cloud, produce target servers to the server producer, install operating systems and deploy cloud services on the target server, and then transport them to the edge cluster to achieve the expansion of edge nodes.
It realizes end-to-end expansion of edge nodes, integrates hardware installation, software deployment, network setup, security compliance and logistics relocation, improves edge computing capabilities and meets users' expansion needs.
Smart Images

Figure CN2024088057_14112024_PF_FP_ABST
Abstract
Description
Edge resource expansion method, edge cloud system, device and storage medium
[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on May 8, 2023, with application number 202310512722.4 and invention name “Method for expanding edge resources, edge cloud system, device and storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of cloud computing technology, and in particular to an edge resource expansion method, an edge cloud system, a device, and a storage medium. Background Art
[0003] Traditional cloud computing utilizes a centralized data center (DC) model, offering powerful computing capabilities. However, with the emergence of a vast array of emerging mobile and IoT device applications, this cloud computing model, which relies on centralized DCs, no longer adequately meets user needs. Edge computing has emerged to address the challenges of centralized cloud computing.
[0004] The edge cloud consists of edge nodes distributed in the same region, specifically processing service requests from users in that region and providing cloud computing services to users quickly and flexibly. As user applications evolve, more and more users are demanding the expansion of edge node capacity.
[0005] Summary of the Invention
[0006] Multiple aspects of the present application provide an edge resource expansion method, an edge cloud system, a device, and a storage medium to achieve integrated edge node expansion.
[0007] An embodiment of the present application provides a method for expanding edge resources, which is applicable to a central service node in a central cloud; the method includes: obtaining an edge resource expansion request provided by a target user; based on the edge resource expansion request, providing a server production request to a server producer to request the server producer to produce a target server; installing an operating system and deploying cloud services on the target server; sending a transportation instruction to a logistics transporter to instruct the logistics transporter to transport the target server to a target edge cluster corresponding to the target user, so that the target server can be deployed in the target edge cluster.
[0008] An embodiment of the present application also provides an edge cloud system, comprising: a central cloud, and at least one edge cluster connected to the central cloud network; the central cloud comprises: a central service node; the edge cluster comprises: a cabinet and an edge node deployed in the cabinet; the central service node is used to execute the steps in the above-mentioned edge resource expansion method.
[0009] An embodiment of the present application also provides a computing device, comprising: a memory, a processor, and a communication component; wherein the memory is used to store a computer program; the processor is coupled to the memory and the communication component, and is used to execute the computer program to perform the steps in the above-mentioned edge resource expansion method.
[0010] An embodiment of the present application further provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed by one or more processors, the one or more processors are caused to execute the steps in the above-mentioned method for expanding edge resources. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0012] FIG1 is a schematic diagram of the structure of an edge cloud system provided in an embodiment of the present application;
[0013] FIG2 is a specific flow chart of the process of expanding edge resources provided in an embodiment of the present application;
[0014] FIG3 is a flow chart of a method for expanding edge resources according to an embodiment of the present application;
[0015] FIG4 is a schematic diagram of the structure of a computing device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0016] To make the purpose, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with the specific embodiments of this application and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.
[0017] In some embodiments of the present 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 the operating system and deploy cloud services on the target server; and then instruct the logistics transporter 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 expand the edge nodes in the target edge cluster. This embodiment implements a full-link expansion process that integrates the user's edge resource expansion request, server production, transportation, and edge cluster deployment, realizing integrated edge node expansion and end-to-end edge node expansion.
[0018] The following describes in detail the technical solutions provided by various embodiments of the present application in conjunction with the accompanying drawings.
[0019] It should be noted that the same reference numerals denote the same objects in the following drawings and embodiments, and therefore, once an object is defined in one drawing or embodiment, it does not need to be further discussed in the subsequent drawings and embodiments.
[0020] Figure 1 is a schematic diagram of the structure of an edge cloud system provided by an embodiment of the present application. As shown in Figure 1, the edge cloud system includes: a central cloud 10 and at least one edge cluster 20 connected to the central cloud 10 through a network.
[0021] The edge cloud is a cloud computing platform built on edge infrastructure based on cloud computing technology and edge computing capabilities. It is a cloud platform with computing, networking, storage, and security capabilities at the edge. The term "edge cloud" is a relative term. It refers to a cloud computing platform relatively close to the terminal. In other words, it is different from a control node or traditional cloud computing platform. Control nodes or traditional cloud computing platforms can include data centers or computer rooms with large-scale and centralized resources. In contrast, an edge cloud is composed of multiple edge cloud nodes. The resource scale of a single edge cloud node is relatively small, but the number of edge cloud nodes is large, which makes the edge cloud's coverage wider. In other words, the edge cloud system of this embodiment is also based on cloud computing technology and edge computing capabilities, built on edge infrastructure. It is a cloud computing platform with computing, networking, storage, and security capabilities at the edge. It is a cloud computing platform relatively close to the terminal and a network system built on the infrastructure between the control node or traditional cloud computing system and the terminal. The terminal referred to in this embodiment refers to the demand side of cloud computing services, such as a terminal or user end on the Internet or a terminal or user end in the Internet of Things.
[0022] In this embodiment, the central cloud 10 is deployed with a central service node 101, which, combined with the edge cluster 20 and the terminal (not shown in Figure 1), can form a "cloud-edge-end three-body collaboration" network architecture. 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, alleviate the pressure on the management and control nodes or traditional cloud computing platforms, and reduce bandwidth costs.
[0023] The central service node 101 refers to a device, software module, or software system that has 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.
[0024] In this embodiment, an edge cluster 20 may be a computer room, a data center (DC), or an Internet data center (IDC), etc. For an edge cloud network, an edge cluster 20 may include one or more edge nodes. Multiple refers to 2 or more. Each edge node may include a series of edge infrastructures, including but not limited to: distributed data centers (DCs), wireless computer rooms or clusters, operators' communication networks, core network equipment, base stations, edge gateways, home gateways, computing devices or storage devices, and other edge devices and corresponding network environments, etc. It is noted here that the locations, capabilities, and infrastructures contained in different edge nodes may be the same or different.
[0025] In this embodiment, the edge node can provide various resources to the outside world. In this embodiment, the resources provided by the edge node may include hardware resources and software resources. Among them, the hardware resources may include: computing resources such as processors, storage resources such as memory and disks. Among them, the processor may be a central processing unit (CPU) and a parallel processor, etc. The parallel processor may be a graphics processing unit (GPU), a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), etc. Software resources may include: network resources such as bandwidth, network segment, network card configuration, and operating system, etc.
[0026] In this embodiment, the edge nodes and other infrastructure in the edge cluster 20 may belong to the users of the edge cluster 20, be local resources of the users, and be operated and maintained by the users. Of course, the edge nodes and other infrastructure in the edge cluster 20 may also be partially or fully implemented as a target mode, that is, partially or fully belong to the public cloud (such as the central cloud 10), and be operated and maintained by the public cloud. Among them, the target mode is to extend the computing, storage, network and other infrastructure of the public cloud to the user's local computer room in a hardware and software integrated manner, and to provide a fully managed cloud service that meets the requirements of data security, local data processing, low latency, etc. The target mode is an extension of the public cloud in the user's local data center, which is to deploy the infrastructure resources belonging to the public cloud in the user's local computer room or IDC, and the public cloud manages and maintains the infrastructure resources corresponding to the target mode.
[0027] Racks (also known as cabinets) serve as the infrastructure of a data center or computer room. They can store servers and provide them with resources such as power and communications. Edge cluster 20 may include cabinets 201, which are used to house edge nodes. Cabinets 201 store edge nodes and provide them with resources such as power and communications. Each cabinet 201 can house one or more edge nodes.
[0028] In this embodiment, the central service node 101 can also provide edge node expansion capabilities. Specifically, as shown in Figures 1 and 2, users of the edge cluster to be expanded (defined as target users) can provide edge resource expansion requests to the central cloud 10 (Step 1 of Figures 1 and 2).
[0029] The edge resource expansion request may include the resource expansion type (ReasonType) and the amount of resources to be expanded. The amount of resources to be expanded may be expressed in Stock Keeping Units (SKUs). SKUs are the basic units for external sales of edge clusters 20, integrating computing, storage, and networking. One SKU can be installed in an entire cabinet.
[0030] Resource expansion types include: whole cabinet expansion type and non-whole cabinet expansion type. Among them, there are three scenarios for edge resource expansion: (1) only upgrading the original computing SKU in the edge cluster, that is, expanding the computing resources in the existing cabinet of the edge cluster 20; (2) expanding the new computing SKU, expanding the computing resources in the form of a whole cabinet; (3) upgrading the original computing SKU and expanding the new computing SKU, that is, expanding the computing resources of the existing cabinet and the new cabinet. In the embodiment of the present application, the resource expansion type corresponding to the above scenario (1) can be defined as a non-whole cabinet expansion type; and the resource expansion type corresponding to the above scenarios (2) and (3) can be defined as a whole cabinet expansion type.
[0031] The central service node 101 can obtain the edge resource expansion request provided by the target user; and based on the edge resource expansion request, provide a server production request to the service producer 30 to request the server producer 30 to produce the target server (step 2 of Figure 1 and steps 2 and 3 of Figure 2).
[0032] Specifically, as shown in FIG2 , the central control node 101 may obtain the resource expansion type and the amount of resources to be expanded from the edge resource expansion request.
[0033] Furthermore, if the resource expansion type is non-whole cabinet expansion, infrastructure information of the cabinet to be expanded can be constructed (corresponding to "constructing infrastructure model" in step 2 of FIG. 2 ). The cabinet to be expanded includes at least one target server to be expanded.
[0034] Specifically, the location of the cabinet to be expanded in the computer room of the operator of the cabinet to be expanded can be determined based on the location information of the existing cabinets of the target edge cluster in the computer room of the operator of the cabinet to be expanded. The target edge cluster is an edge cluster belonging to the target user who provided the edge resource expansion request.
[0035] In the target mode, the existing cabinets in the target edge cluster are operated by the central cloud. The central service node 101 can logically number the cabinets in the target edge cluster and create logical cabinet locations in the operator's computer room. Then, based on the location information of the existing cabinets in the target edge cluster, it plans the location of the cabinets to be expanded in the operator's computer room.
[0036] The central service node 101 can also determine the network topology of the cabinet to be expanded based on the network topology of the existing cabinets of the target edge cluster in the computer room of the operation and maintenance party; and obtain the network requirements of the target user from the edge resource expansion request; further, the network resource information of the cabinet to be expanded can be determined based on the network requirements of the target user and the network resources provided by the operation and maintenance party. Network resource information refers to the resources required for the device to achieve network communication, which may include: network segments, routes and domain name systems (Domain Name System, DNS), etc., and may also include the network mode of the device. The network mode can be a virtual private network (VPN) mode, a virtual private cloud (VPC) mode or a dedicated network line mode, etc. The network mode refers to the network communication mode between the cabinet and the central cloud 10, which refers to which mode the cabinet uses to communicate with the central cloud 10.
[0037] Specifically, the central service node 101 can obtain the target user's Internet Protocol (IP) address quantity N from the target user's network requirements. Furthermore, it can determine N unassigned IP addresses from the network segment provided by the operator and use them as the IP addresses of the cabinets to be expanded. The central service node 101 can also use the operator's routing information as the routing information of the cabinets to be expanded. Furthermore, it can obtain the target user's selected network mode from the target user's network requirements as the network mode of the cabinets to be expanded.
[0038] Furthermore, the location of the cabinet to be expanded in the computer room of the operation and maintenance party, the network topology of the cabinet to be expanded, and the network resource information of the cabinet to be expanded can be used as the infrastructure information of the cabinet to be expanded.
[0039] The above only takes the infrastructure information including: the location of the cabinet to be expanded in the operation and maintenance party's computer room, the network topology structure of the cabinet to be expanded and the network resource information of the cabinet to be expanded as an example to illustrate the implementation method of constructing the infrastructure information of the cabinet to be expanded, but it does not mean that the infrastructure information only includes the above infrastructure information, nor does it mean that the infrastructure information includes the above infrastructure information.
[0040] After determining the infrastructure information of the cabinet to be expanded, the central service node 101 may 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 cabinet to be expanded and the target server (step 3 in Figure 2). The cabinet to be expanded includes at least one target server. The server production request may include the infrastructure information of the cabinet to be expanded and the amount of resources to be expanded.
[0041] Specifically, the central service node 101 can issue a server production request to the server producer based on the amount of resources to be expanded and the infrastructure information. After receiving the server production request, the server producer begins to produce the cabinet to be expanded and the target server in the cabinet according to the amount of resources to be expanded and the infrastructure information. After production is completed, it is shipped to the operator of the cabinet to be expanded and the target server (Step 3 "Ship Target Server" in Figure 1). The operator of the cabinet to be expanded and the target server can be the operator of the central cloud.
[0042] In some embodiments, if the resource expansion type is not a full-cabinet 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, requesting the server manufacturer to produce the target server (step 3 of Figure 2). In this embodiment, the target server is to be installed in an existing cabinet in the target edge cluster. In this embodiment, the server production request may include the amount of resources to be expanded, etc.
[0043] 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 producing the target server to be expanded based on the amount of resources to be expanded. After production is completed, the server producer delivers the target server to the operator of the target server to be expanded (Step 3 "Delivering the target server" in Figure 1). The operator of the target server is deployed in the central cloud 10.
[0044] The operator enters the target server information into the Configuration Management Database (CMDB) (Figure 2, Step 4, "Entering Information into the CMDB"). A CMDB is a logical database that stores information about hardware and software assets (often called configuration items) and the relationships between them.
[0045] For an embodiment in which the resource expansion type is the whole cabinet expansion type, after the cabinet to be expanded arrives at the operation and maintenance party, the operation and maintenance personnel of the operation and maintenance party can connect the cabinet to be expanded to the physical network of the operation and maintenance party's computer room based on the infrastructure information constructed above (Figure 2 Step 5 "Cabinet connection to physical network").
[0046] The central service node 101 can install the operating system on the target server and deploy the cloud service (step 4 in Figure 1 and steps 9 and 10 in Figure 2). Specifically, for an embodiment in which the resource expansion type is the whole cabinet expansion type, the central service node 101 can deploy the block storage service on the target server in the cabinet to be expanded (step 9 in Figure 2); and obtain the image file of the cloud computing service, and deploy the cloud computing service on the target server in the cabinet to be expanded according to the image file of the cloud computing service (step 10 in Figure 2); and perform network configuration for the cloud computing service. The central service node 101 can also deploy infrastructure operation and maintenance plug-ins on the target server. The central service node 101 can also connect the cloud computing service and the block storage service to the log collection system to collect logs for the cloud computing service and the block storage service. The central service node 101 can also start cloud computing service inspection scheduled tasks, self-tests and inspections, etc.
[0047] In this embodiment, the central service node 101 may also call the infrastructure operation and maintenance plug-in to configure a security gateway for the target server in the cabinet to be expanded (Step 8 “Security Gateway Deployment” in FIG. 2 ).
[0048] For an embodiment in which the resource expansion type is a whole cabinet expansion type, the central service node 101 may obtain the image file of the cloud computing service when the expansion type is a non-whole machine expansion type, and deploy the cloud computing service on the target server in the cabinet to be expanded based on the image file of the cloud computing service (step 10 "Cloud computing service deployment" in Figure 2); and perform network configuration for the cloud computing service. The central service node 101 may also deploy infrastructure operation and maintenance plug-ins on the target server. The central service node 101 may also connect the cloud computing service and the block storage service to the log collection system to collect logs for the cloud computing service and the block storage service. The central service node 101 may also initiate scheduled inspection tasks, self-tests, and checks for the cloud computing service.
[0049] The cloud services deployed on the target server shown in the above embodiment are for illustrative purposes only and are not intended to be limiting. Subsequently, as shown in FIG1 , the central service node 101 may send a transport instruction to the logistics transport provider 40 , instructing the logistics transport provider 40 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 ( FIG1 , steps 5-7 ).
[0050] In this embodiment, the central service node in the central cloud can request the server manufacturer to produce the target server based on the target user's edge resource expansion request; and install the operating system and deploy cloud services on the target server; after that, it can instruct the logistics transporter 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 the edge node in the target edge cluster. In this embodiment, a full-link expansion process is implemented that integrates the user's request for edge resource expansion, server production, transportation and edge cluster deployment, realizing the integration of edge node expansion and end-to-end edge node expansion. Among them, end-to-end refers to the process from the user's request for edge resource expansion to the realization of edge node expansion in the user's edge cluster.
[0051] In some embodiments of the present application, as shown in FIG2 , before installing the operating system and deploying the cloud service on the target server, for an embodiment in which the resource expansion type is the whole-machine expansion type, the central service node 101 may also perform network construction for the cabinet to be expanded ( FIG2 , step 6). Specifically, the central service node 101 may construct the network topology of the target server in the physical network of the operation and maintenance party of the central cloud based on the infrastructure information; and apply for a network address for the target server in the network of the operation and maintenance party; and generate the network configuration information of the target server based on the device configuration specification, the network topology, and the network address of the target server; and provide the network configuration information of the target server to the target server after the cabinet to be expanded is connected to the physical network of the operation and maintenance party.
[0052] Before installing the operating system and deploying cloud services on the target server, the central service node 101 may also perform a performance test on the target server (step 7 in Figure 2). 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 pressure of the target server.
[0053] Accordingly, when performing a performance test on a target server, the central service node 101 may use at least one of the following implementations to perform the performance test:
[0054] Implementation 1: Detecting the target server's network quality. 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. Network quality parameters reflect network performance and may include packet loss rate and latency. Furthermore, the target server's network quality can be determined based on the target server's network quality parameters.
[0055] Implementation method 2: Perform hardware environment detection on the target server. The hardware environment refers to the computer physical system composed of a computer and its peripheral devices. Specifically, the central service node 101 can test whether the hardware of the target server is abnormal. For example, the central service node 101 can test whether the processor of the target server is abnormal. Specifically, the central service node 101 can instruct the processor of the target server to run the set function; if the operation is successful, it means that the processor of the target server is normal. For another example, the central service node 101 can also test whether the storage medium of the target server is abnormal. Specifically, the central service node 101 can read and write data to the storage medium; if the data reading and writing speed meets the set reading and writing speed requirements, it is determined that the storage medium of the target server is normal, and so on.
[0056] Implementation 3: Stress testing the target server. Specifically, the central service node 101 can input concurrent execution tasks to the target server and run the test under the condition that the target server's system resources are scarce. Resources for software stress testing include internal memory, CPU availability, disk space, and network bandwidth.
[0057] Furthermore, when the performance of the target server meets the requirements, the above-mentioned operations of installing the operating system on the target server and deploying the cloud service are performed.
[0058] In some embodiments of the present application, for embodiments in which the resource expansion type is the expansion of the entire cabinet, after the central service node 101 deploys the cloud service on the target server, it can perform a secondary inspection on the network quality of the target server in the cabinet to be expanded to obtain the network quality inspection result (step 12 of Figure 2). Accordingly, the central service node 101 can obtain the network quality inspection result (step 17 of Figure 2 "Network quality secondary inspection result recovery"). Optionally, the network quality of the target server in the cabinet to be expanded can be asynchronously subjected to a secondary inspection to obtain the network quality inspection result (step 12 of Figure 2), and the network inspection result can be obtained asynchronously. Here, asynchronous refers to asynchronous execution with steps 13-16.
[0059] If the network quality detection result indicates that the network quality of the target server in the cabinet to be expanded is normal, subsequent operations can be performed; if the network quality detection result indicates that the network quality of the target server in the cabinet to be expanded is abnormal, network repair can be performed on the target server in the cabinet to be expanded until the network quality of the target server in the cabinet to be expanded is normal, and subsequent operations can be continued.
[0060] In some embodiments, to prevent the newly expanded target server from falsely alarming or being identified as abnormal by the operator's operation and maintenance system before it officially goes into production, triggering erroneous operations such as offline operation, the central service node 101 can also set the target server's identifier to a blacklist tag in the operation and maintenance system after deploying the cloud service on the target server (Step 11 "Target Server Blacklisted" in Figure 2). The operation and maintenance system does not recognize servers with blacklist tags, thereby preventing the operation and maintenance system from identifying the newly expanded target server as abnormal and triggering erroneous operations such as offline operation. Furthermore, the central service node 101 can also add an expansion lock tag to the target server's identifier to prevent the target user's control system from being aware 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 the 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 will not be open to the target user.
[0061] In some embodiments, the central service node 101 may also tag the target server on the aforementioned CMDB (Step 13 "Server Tagging" in Figure 2). This tag is used to represent the ownership of the target server, allowing the operation and maintenance system in the central service node 101 to adopt an operation and maintenance policy adapted to the owner of the target server and perform operation and maintenance on the target server. For example, for a target mode scenario, the target server may be labeled with a target mode-specific resource tag on the aforementioned CMDB. Accordingly, the operation and maintenance system in the central service node 101 adopts an operation and maintenance policy adapted to the target mode and performs operation and maintenance on the target server.
[0062] In other embodiments, for the sake of information security, the central service node 101 may also perform at least one sensitive information detection on the target server before instructing the logistics transport party to transport the target server to the target edge cluster corresponding to the target user; and delete the detected sensitive information from the target server (Figure 2 step 14 "Sensitive information cleaning" and step 16 "Sensitive information secondary cleaning").
[0063] 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. Further, the detected sensitive information may be deleted from the target server.
[0064] In this embodiment, the number and order of sensitive information detection on the target server are not limited. Figure 2 illustrates only the example of performing a secondary sensitive information detection on the target server, but this does not constitute a limitation. Sensitive information detection can be performed at any stage or before or after any operation, until it is determined that no sensitive information exists on the target server. Preferably, sensitive information detection can be performed on the target server before shutting down the target server, and the target server can be shut down only after no sensitive information exists on the target server.
[0065] In some embodiments of the present application, before sending the transport instruction to the logistics transport party, the central service node 101 may 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 connection channel (Any Tunnel) corresponding to the availability zone of the target edge cluster, so that the target server can be connected to the central cloud after being deployed to the target edge cluster (Step 15 "Modify network connection configuration" in Figure 2). Among them, the virtual IP of AnyTunnel is a public access VIP provided in the VPC network, which can access all VPCs.
[0066] Optionally, after the target server's virtual IP address is changed to the virtual IP address of any tunnel corresponding to the target edge cluster's availability zone, the target server can be checked for sensitive information again until no sensitive information is present (Step 16, "Secondary Cleanup of Sensitive Information," in Figure 2). The target server can then be shut down.
[0067] Optionally, the central service node 101 can remotely control the shutdown of the target server (step 18 "remote shutdown" in Figure 2). In some embodiments, the central service node 101 can remotely control the shutdown of the cloud computing service and block storage service of the target server; and after the cloud computing service and block storage service of the target server are shut down, remotely control the shutdown of the target server. The operation and maintenance personnel of the operation and maintenance party of the target server can disconnect the target server from the network and power on in the operation and maintenance party's computer room (step 19 "power off and disconnect from the network" in Figure 2). Afterwards, the target server can be packaged and delivered to the target user (step 20 "package delivery" in Figure 2).
[0068] Afterwards, the central service node 101 may send a transportation instruction to the logistics transporter 40 to instruct the logistics transporter 40 to transport the target server to the target edge cluster corresponding to the target user (step 21 “Logistics Transport” in FIG. 2 ).
[0069] The staff of the target edge cluster or the staff of the operation and maintenance party of the target server can deploy the target server to the target edge cluster (step 22 of Figure 2 "Deploy the target server to the target edge cluster"); and physically connect the target server to the network and provide power.
[0070] Furthermore, the central service node 101 can perform network configuration and debugging on the target server and the cabinet where the target server is located until the target server and the cabinet where the target server is located are connected to the central cloud (Figure 2, step 23 "Network Configuration and Debugging"). For the whole cabinet expansion embodiment, the cabinet where the target server is located is the cabinet to be expanded; for the non-whole cabinet expansion embodiment, the target server is an existing cabinet in the target edge cluster.
[0071] In some embodiments, for a computing node in target mode as the target server, 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 are transmitted from the security gateway to the central service node through the dedicated network (step 24 "Security Gateway Diversion" in Figure 2). The dedicated network may be a dedicated communication network between the computing node in target mode and the central cloud, such as a VPC, VPN, or a dedicated network cable. Specifically, switching the network mode of the target server to target mode allows the security gateway to proxy the data packets of the target server and transmit them to the central service node 101 through the dedicated network.
[0072] In some embodiments, the central service node 101 can also configure dynamic environment monitoring for the target server (step 25 "Dynamic Environment Monitoring Configuration" in Figure 2) and synchronize the dynamic environment monitoring configuration information to the operation and maintenance system in the central service node. Dynamic environment monitoring refers to centralized monitoring of the target server and the environmental variables in the target server.
[0073] In some embodiments of the present 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 (step 26 "Network quality detection" in Figure 2), and use cloud-edge collaboration to verify the management capabilities of the central service node for the target server (step 27 "Cloud-edge collaboration verification" in Figure 2).
[0074] When detecting the network quality of the target server in the target edge cluster, the central service node 101 can control the target server to send a detection data packet to other devices; and collect the network quality parameters of the target server based on the detection data packet; 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.
[0075] In some embodiments, the central service node 101 may adopt a cloud-edge collaboration method to verify the management capability of the central service node for the target server. Specifically, the central service node 101 may adopt a cloud-edge collaboration method to verify its lifecycle management capability of the cloud computing service for the target server. For example, the central service node 101 may create, start and destroy cloud computing services on the target server to verify the lifecycle management capability of the cloud computing service of the target server. And / or, the central service node 101 may also adopt a cloud-edge collaboration method to verify the operation and maintenance capability of the operation and maintenance system in 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 of the operation and maintenance system is normal, it is determined that the operation and maintenance capability of the operation and maintenance system for the target server meets the standards, etc.
[0076] In actual use, the target user may also perform acceptance inspection on the target server (step 28 "target user acceptance" in FIG2 ). The acceptance inspection process of the target user is not within the scope of protection of this application, and therefore, will not be described in detail.
[0077] After the above operations are completed and all performance tests meet the requirements, the central service node 101 can remove the blacklist tag corresponding to the target server's identifier from the operation and maintenance system (step 29 "Remove Blacklist" in Figure 2). This allows the target server's operation and maintenance system to recognize the target server. Furthermore, the expansion lock tag added to the target server's identifier can be removed to allow the target user's control system to detect the target server and make it available to the user.
[0078] It is worth noting that the processing flow not marked with "(whole cabinet)" in Figure 2 above is a common processing flow for whole cabinet expansion and non-whole cabinet expansion; the processing flow marked with "(whole cabinet)" is a processing flow unique to whole cabinet expansion.
[0079] The edge node expansion process provided in Figure 2 above enables end-to-end edge node expansion. The full-link process for edge node expansion integrates hardware installation, software deployment, network setup, security compliance, logistics relocation, and cloud-edge collaborative verification, achieving integrated expansion of edge cluster nodes. Moreover, the edge node expansion method provided in the embodiments of the present application is also compatible with both full-cabinet expansion and non-full-cabinet expansion.
[0080] In addition to the above-mentioned edge cloud system, the embodiment of the present application also provides an edge resource expansion method. The following is an exemplary description of the edge resource expansion method provided in the embodiment of the present application.
[0081] FIG3 is a flow chart of a method for expanding edge resources according to an embodiment of the present application. The expansion method is applicable to a central service node in a central cloud. As shown in FIG3 , the expansion method mainly includes:
[0082] 301. Obtain an edge resource expansion request provided by a target user.
[0083] 302. Based on the edge resource expansion request, provide a server production request to the server producer to request the server producer to produce a target server.
[0084] 303. Install the operating system on the target server and deploy cloud services.
[0085] 304. Send a transportation instruction to the logistics transport provider to instruct the logistics transport 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.
[0086] In this embodiment, the central service node provides edge node expansion capabilities. 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-cabinet expansion and non-full-cabinet expansion.
[0087] For the central service node, in step 301, an 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.
[0088] Specifically, the resource expansion type and the amount of resources to be expanded can be obtained from the edge resource expansion request. Furthermore, if the resource expansion type is not a full-cabinet expansion, infrastructure information for the cabinet to be expanded can be constructed. The cabinet to be expanded includes at least one target server to be expanded.
[0089] Specifically, the location of the cabinet to be expanded in the computer room of the operator of the cabinet to be expanded can be determined based on the location information of the existing cabinets of the target edge cluster in the computer room of the operator of the cabinet to be expanded. The target edge cluster is an edge cluster belonging to the target user who provided the edge resource expansion request.
[0090] In target mode, the existing cabinets in the target edge cluster are operated by the central cloud. The cabinets in the target edge cluster can be logically numbered and logical locations created in the operator's computer room. The locations of the cabinets to be expanded are then planned in the operator's computer room based on the locations of the existing cabinets in the target edge cluster.
[0091] Furthermore, the network topology of the cabinets to be expanded can be determined based on the network topology of the existing cabinets in the target edge cluster within the operator's computer room. The target user's network requirements can be obtained from the edge resource expansion request. Furthermore, the network resource information of the cabinets to be expanded can be determined based on the target user's network requirements and the network resources provided by the operator. Network resource information refers to the resources required for a device to achieve network communication, and can include network segments, routing, DNS, etc., as well as the device's network mode.
[0092] Specifically, the target user's required number of IP addresses, N, can be obtained from their network requirements. Furthermore, N unassigned IP addresses can be determined from the network segment provided by the operator and used as the IP addresses of the cabinets to be expanded. Furthermore, the operator's routing information can be used as the routing information of the cabinets to be expanded. Furthermore, the target user's selected network mode can be obtained from their network requirements and used as the network mode of the cabinets to be expanded.
[0093] Furthermore, the location of the cabinet to be expanded in the computer room of the operation and maintenance party, the network topology of the cabinet to be expanded, and the network resource information of the cabinet to be expanded can be used as the infrastructure information of the cabinet to be expanded.
[0094] The above only takes the infrastructure information including: the location of the cabinet to be expanded in the operation and maintenance party's computer room, the network topology structure of the cabinet to be expanded and the network resource information of the cabinet to be expanded as an example to illustrate the implementation method of constructing the infrastructure information of the cabinet to be expanded, but it does not mean that the infrastructure information only includes the above infrastructure information, nor does it mean that the infrastructure information includes the above infrastructure information.
[0095] After determining the infrastructure information of the cabinet 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, requesting the server manufacturer to produce the cabinet to be expanded and the target server. The cabinet to be expanded includes at least one target server. The server production request includes the infrastructure information of the cabinet to be expanded and the amount of resources to be expanded.
[0096] 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 starts to produce the cabinet to be expanded and the target server in the cabinet according to the amount of resources to be expanded and the infrastructure information; and after production is completed, it will be transported to the operation and maintenance party of the cabinet to be expanded.
[0097] In some embodiments, if the resource expansion type is not a full-cabinet expansion, a server production request can be submitted 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 cabinet in the target edge cluster. The server production request includes, among other things, the amount of resources to be expanded.
[0098] Specifically, a server production request can be issued to a server manufacturer based on the amount of resources to be expanded. Upon receiving the server production request, the server manufacturer begins producing the target server based on the amount of resources to be expanded. After production is complete, the server is shipped to the operator of the target server, which is deployed in the central cloud.
[0099] The operator enters the target server information into the CMDB. For the entire cabinet expansion implementation, once the cabinet arrives at the operator, the operator's personnel can connect the cabinet to the operator's computer room's physical network based on the infrastructure information established above.
[0100] In step 303, an operating system can be installed on the target server and cloud services can be deployed. Specifically, for an embodiment in which the resource expansion type is a whole-cabinet expansion type, a block storage service can be deployed on the target server in the cabinet to be expanded; an image file for the cloud computing service can be obtained, and based on the image file for the cloud computing service, the cloud computing service can be deployed on the target server in the cabinet to be expanded; and network configuration can be performed for the cloud computing service. Furthermore, infrastructure operation and maintenance plug-ins can be deployed on the target server. Of course, the cloud computing service and block storage service can also be connected to the log collection system to collect logs for the cloud computing service and block storage service; and cloud computing service inspection scheduler tasks, self-tests, and inspections can be initiated.
[0101] In this embodiment, the infrastructure operation and maintenance plug-in may also be called to configure a security gateway for the target server in the cabinet to be expanded.
[0102] For implementations where the resource expansion type is whole-cabinet expansion, if the expansion type is non-whole-cabinet expansion, the cloud computing service image file can be obtained and, based on the cloud computing service image file, the cloud computing service can be deployed on the target server in the cabinet to be expanded. Network configuration can also be performed for the cloud computing service. Furthermore, infrastructure operations and maintenance plug-ins can be deployed on the target server, and the cloud computing service and block storage service can be connected to the log collection system to collect logs for the cloud computing service and block storage service, as well as to initiate scheduled inspection tasks, self-tests, and checks for the cloud computing service.
[0103] The cloud services deployed on the target server shown in the above embodiment are for illustrative purposes only and are not intended to be limiting. Subsequently, in step 304, a transport instruction may be sent to the logistics provider, instructing 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 on the target edge cluster.
[0104] In this embodiment, the central service node in the central cloud can request the server manufacturer to produce the target server based on the target user's edge resource expansion request; and install the operating system and deploy cloud services on the target server; after that, it can instruct the logistics transporter 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 the edge node in the target edge cluster. In this embodiment, a full-link expansion process is implemented that integrates the user's request for edge resource expansion, server production, transportation and edge cluster deployment, realizing the integration of edge node expansion and end-to-end edge node expansion. Among them, end-to-end refers to the process from the user's request for edge resource expansion to the realization of edge node expansion in the user's edge cluster.
[0105] In some embodiments of the present application, before installing the operating system and deploying cloud services on the target server, for embodiments where the resource expansion type is a whole-machine expansion type, network construction may also be performed for the cabinet to be expanded. Specifically, based on infrastructure information, a network topology structure of the target server in the physical network of the cabinet's operator can be constructed; a network address can be requested for the target server in the operator's network; and network configuration information for the target server can be generated based on the device configuration specifications, the network topology structure, and the network address of the target server. After the cabinet to be expanded is connected to the operator's physical network, the network configuration information of the target server can be provided to the target server.
[0106] Before installing the operating system and deploying cloud services on the target server, you can also perform a performance test on the target server. Specifically, the performance of the target server may include: the target server's network quality, the target server's hardware environment quality, and the target server's software pressure.
[0107] Optionally, when performing a performance test on a target server, at least one of the following implementation methods may be used for the performance test:
[0108] Implementation 1: Detecting the target server's network quality. Specifically, the correctness of the target server's network connection and 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. Network quality parameters are parameters that reflect network performance and may include packet loss rate and latency. Furthermore, the target server's network quality can be determined based on the target server's network quality parameters.
[0109] Implementation 2: Perform hardware environment testing on the target server. The hardware environment refers to the physical computer system consisting of a computer and its peripheral devices. Specifically, the target server's hardware can be tested for any anomalies. For example, the target server's processor can be tested for any anomalies. Specifically, the target server's processor can be instructed to run a set function; if the function is successful, the target server's processor is normal. For another example, the target server's storage medium can be tested for any anomalies. Specifically, data can be read and written to the storage medium; if the data read and write speeds meet the set read and write speed requirements, the target server's storage medium is determined to be normal, and so on.
[0110] Implementation 3: Stress testing the target server. Specifically, you can input concurrent execution tasks to the target server and run the test under the condition of insufficient system resources on the target server. Resources for software stress testing include internal memory, CPU availability, disk space, and network bandwidth.
[0111] Furthermore, when the performance of the target server meets the requirements, the above-mentioned operations of installing the operating system on the target server and deploying the cloud service are performed.
[0112] In some embodiments of the present application, for embodiments in which the resource expansion type is whole-cabinet expansion, after deploying the cloud service on the target server and before sending the transportation instructions to the logistics transport party, the network quality of the target server in the cabinet to be expanded can be secondary tested, and the network quality test results of the secondary test can be obtained. If the network quality test result indicates that the network quality of the target server in the cabinet to be expanded is normal, subsequent operations can be performed; if the network quality test result indicates that the network quality of the target server in the cabinet to be expanded is abnormal, the network of the target server in the cabinet to be expanded can be repaired until the network quality of the target server in the cabinet to be expanded is normal, and subsequent operations can be continued.
[0113] In some embodiments, in order to prevent the newly expanded target server from falsely alarming before it is officially put into production or being identified as abnormal by the operation and maintenance system of the operation and maintenance party, thereby triggering erroneous operations such as offline operation, after the cloud service is deployed on the target server and before the transportation instructions are sent to the logistics transportation party, the identifier of the target server can be set as a blacklist label of the operation and maintenance system. The operation and maintenance system does not recognize servers with blacklist labels, thereby preventing the operation and maintenance system from identifying the newly expanded target server as abnormal and triggering erroneous operations such as offline operation. Furthermore, an expansion lock label can be added to the identifier of the target server so that the control system of the target user is unaware of the target server. Based on the expansion lock label, the control system of the target user can determine that the target server has not been deployed to the target edge cluster and is not open to the target user for use.
[0114] In some embodiments, the target server can also be marked on the above-mentioned CMDB. The marked label 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 operation and maintenance strategy adapted to the holder to operate and maintain the target server.
[0115] In other embodiments, for information security, after the cloud service is deployed on the target server and before the transportation instructions are sent to the logistics transport party, the target server can be checked for sensitive information at least once; and the detected sensitive information can be deleted from the target server.
[0116] Optionally, the target server may be subjected to at least one sensitive information detection according to a pre-set sensitive information list, and information on the target server that is in the sensitive information list may be determined to be sensitive information. Further, the detected sensitive information may be deleted from the target server.
[0117] In this embodiment, there is no limit on the number and order of sensitive information detection performed on the target server. Sensitive information detection can be performed at any stage or before or after any operation until it is determined that no sensitive information exists on the target server. Preferably, sensitive information detection can be performed on the target server before shutting down the target server, and the target server can be shut down only after no sensitive information exists on the target server.
[0118] In some embodiments of the present application, after deploying the cloud service on the target server and before sending the transportation instructions to the logistics transport party, the network connection and DNS resolution configuration of the target server can also be modified; and the virtual IP address of the target server can be modified to the virtual IP address of any connection channel (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. Among them, the virtual IP of AnyTunnel is a public access VIP provided by the VPC network, which can access all VPCs.
[0119] Optionally, after changing the target server's virtual IP address to the virtual IP address of any tunnel corresponding to the target edge cluster's availability zone, perform another sensitive information check on the target server until no sensitive information is found. The target server can then be shut down.
[0120] Optionally, the target server can be remotely shut down. In some embodiments, the target server's cloud computing services and block storage services can be remotely shut down. After the target server's cloud computing services and block storage services are shut down, the target server can be remotely shut down. The target server's operators can disconnect the target server from the network and power supply in their computer room.
[0121] Afterwards, a transport instruction can be sent to the logistics transport provider, instructing them to transport the target server to the target edge cluster corresponding to the target user. The staff of the target edge cluster or the operation and maintenance staff of the target server can deploy the target server to the target edge cluster and connect the target server to the physical network and power it.
[0122] After the target server is deployed in the target edge cluster, network configuration and debugging can be performed on the target server and the cabinet where it resides until the target server and the cabinet where it resides are connected to the central cloud. For the whole-cabinet expansion implementation, the cabinet where the target server resides is the cabinet to be expanded. For the non-whole-cabinet expansion implementation, the target server is an existing cabinet in the target edge cluster.
[0123] In some embodiments, for a computing node in target mode of the target server, 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 from the security gateway to the central service node through the dedicated network.
[0124] In some embodiments, after the target server is deployed in the target edge cluster, dynamic environment monitoring can be configured for the target server and the dynamic environment monitoring configuration information can be synchronized to the operation and maintenance system in the central service node. Dynamic environment monitoring refers to the centralized monitoring of the target server and the environmental variables in the target server.
[0125] In some embodiments of the present 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 also be tested, and the management capability of the central service node for the target server can be verified.
[0126] When detecting the network quality of the target server in the target edge cluster, the target server can be controlled to send a detection data packet to other devices; and the network quality parameters of the target server can be collected based on the detection data packet; 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.
[0127] In some embodiments, a cloud-edge collaboration approach can be employed to verify the central service node's ability to manage the target server. Specifically, its ability to manage the lifecycle of the target server's cloud computing services can be verified. For example, cloud computing services can be created, started, and terminated on the target server to verify the target server's ability to manage the lifecycle of the cloud computing services. Furthermore, / or, the operation and maintenance system within the central service node can be verified for its ability to manage the target server's operations and maintenance.
[0128] In actual use, the target user may also conduct acceptance inspection on the target server, etc. The acceptance inspection process of the target user is not within the scope of protection of this application, and therefore, will not be described in detail.
[0129] After the above operations are completed and all performance tests meet the requirements, the blacklist tag associated with the target server's identifier can be removed from the operation and maintenance system. This allows the target server's operation and maintenance system to identify the target server. Furthermore, the expansion lock tag added to the target server's identifier can be removed, allowing the target user's control system to detect the target server and make it available for user use.
[0130] The embodiments of this application provide a full-link 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 by the embodiments of this application is also compatible with both full-cabinet and part-cabinet expansion.
[0131] It should be noted that the execution entity of each step of the method provided in the above embodiment can be the same device, or the method can be executed by different devices. For example, the execution entity of steps 301 and 302 can be device A; for another example, the execution entity of step 301 can be device A, and the execution entity of step 302 can be device B; and so on.
[0132] In addition, some of the processes described in the above embodiments and the 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 in which they appear in this document or may be executed in parallel. The sequence numbers of the operations, such as 301, 302, etc., are merely used to distinguish between 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.
[0133] Accordingly, an embodiment of the present application further provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed by one or more processors, the one or more processors are caused to execute the steps in the above-mentioned edge resource expansion method.
[0134] Figure 4 is a schematic diagram of the structure of a computing device provided in an embodiment of the present 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. As shown in Figure 4, the computing device includes: memory 40a, processor 40b, and communication component 40c; wherein memory 40a is used to store computer programs.
[0135] 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 producer through the communication component 40c to request the server producer to produce a target server; installing an operating system on the target server and deploying cloud services; and sending a transportation instruction to the logistics transporter through the communication component 40c to instruct the logistics transporter 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.
[0136] Optionally, when the processor 40b provides a server production request to the server producer 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; when the resource expansion type is a whole cabinet expansion type, build the infrastructure information of the cabinet to be expanded; based on the infrastructure information and the amount of resources to be expanded, provide a server production request to the server producer through the communication component 40c to request the server producer to produce the cabinet to be expanded and the target server; the target server is to be deployed in the cabinet to be expanded; and, when the resource expansion type is a non-whole cabinet expansion type, based on the amount of resources to be expanded, provide a server production request to the server producer through the communication component 40c to request the server producer to produce the target server; the target server is to be deployed in an existing cabinet of the target edge cluster.
[0137] Furthermore, when constructing the infrastructure information of the cabinet to be expanded, the processor 40b is specifically used to: determine the location of the cabinet to be expanded in the computer room of the operation and maintenance party based on the location information of the existing cabinets of the target edge cluster in the computer room of the operation and maintenance party of the cabinet to be expanded; determine the network topology of the cabinet to be expanded based on the network topology of the existing cabinets of the target edge cluster in the computer room of the operation and maintenance party; obtain the network requirements of the target user from the edge resource expansion request; determine the network resource information of the cabinet to be expanded based on the network requirements of the target user and the network resources provided by the operation and maintenance party; and use the location of the cabinet to be expanded in the computer room of the operation and maintenance party, the network topology of the cabinet to be expanded, and the network resource information of the cabinet to be expanded as the infrastructure information of the cabinet to be expanded.
[0138] In some embodiments, the processor 40b is also used to: when the resource expansion type is the whole cabinet expansion type, build the network topology structure of the target server in the physical network of the operation and maintenance party of the target server based on the infrastructure information; apply for a network address for the target server in the network segment of the operation and maintenance party; generate the network configuration information of the target server based on the device configuration specifications, network topology structure and network address; after the cabinet to be expanded is connected to the physical network of the operation and maintenance party, provide the network configuration information of the target server to the target server through the communication component 40c.
[0139] Optionally, the processor 40b is further configured to: perform a performance test on the target server before installing the operating system and deploying the cloud service on the target server; and, if it is detected that the performance of the target server meets the requirements, execute the operation of installing the operating system and deploying the cloud service on the target server;
[0140] Furthermore, when performing performance testing on the target server, the processor 40b is specifically used to: detect the network quality of the target server; and / or perform hardware environment testing on the target server; and / or perform stress testing on the target server.
[0141] In some embodiments, when the processor 40b deploys the cloud service on the target server, it is specifically used to: when the expansion type is the whole cabinet expansion type, deploy the block storage service on the target server in the cabinet to be expanded; obtain the image file of the cloud computing service; according to the image file of the cloud computing service, deploy the cloud computing service on the target server in the cabinet to be expanded, and perform network configuration for the cloud computing service; deploy the infrastructure operation and maintenance plug-in on the target server; or, when the expansion type is a non-whole cabinet expansion type, obtain the image file of the cloud computing service; according to the image file of the cloud computing service, deploy the cloud computing service on the target server in the cabinet to be expanded, and perform network configuration for the cloud computing service; deploy the infrastructure operation and maintenance plug-in on the target server.
[0142] Furthermore, the processor 40b is further configured to: when the expansion type is the whole cabinet expansion type, call the infrastructure operation and maintenance plug-in to configure a security gateway for the target server in the cabinet to be expanded.
[0143] Optionally, the processor 40b is also used to: when the expansion type is the whole cabinet expansion type, after deploying the cloud service on the target server, and before sending the transportation instructions to the logistics transportation party, perform a secondary inspection on the network quality of the target server, and obtain the network quality inspection results of the secondary inspection.
[0144] Optionally, the processor 40b is also used to: after deploying the cloud service on the target server, and before sending the transportation instructions to the logistics transportation party, set the identifier of the target server to the 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; 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.
[0145] Optionally, the processor 40b is also used to: after the target server is deployed in the target edge cluster, remove the blacklist label of the operation and maintenance system corresponding to the target server's identifier so that the operation and maintenance system can identify the target server; delete the expansion lock label added to the target server's identifier so that the target user's control system can perceive the target server.
[0146] In other embodiments, the processor 40b is further used to: perform at least one sensitive information detection on the target server after deploying the cloud service on the target server, and before sending transportation instructions for the target server to the logistics transport party; and delete the detected sensitive information from the target server.
[0147] Optionally, the processor 40b is also used 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 the transportation instructions to the logistics transportation party; 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.
[0148] In some other embodiments, the processor 40b is also used to: after the target server is deployed in the target edge cluster, perform network configuration and network debugging on the target server and the cabinet where the target server is located, until the target server and the cabinet where the target server is located are connected to the central cloud; switch the network mode of the target server to target mode, so that the data packets of the target server can be transmitted from the security gateway to the central service node through the dedicated network; configure dynamic environment monitoring on the target server, and synchronize the dynamic environment monitoring configuration information to the operation and maintenance system in the central service node; and detect the network quality of the target server in the target edge cluster; and use cloud-edge collaboration to verify the management capabilities of the central service node for the target server.
[0149] Optionally, when the processor 40b uses the cloud-edge collaboration method to detect the network quality of the target server in the target edge cluster, it is specifically used to: use the cloud-edge collaboration method to verify the lifecycle management capabilities of the central service node's cloud computing service for the target server; and / or use the cloud-edge collaboration method to verify the operation and maintenance capabilities of the operation and maintenance system in the central service node for the target server.
[0150] In some optional embodiments, as shown in FIG4 , 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. FIG4 illustrates only some components, and does not necessarily mean that the computing device must include all components shown in FIG4 , nor does it mean that the computing device can only include the components shown in FIG4 .
[0151] 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 the operating system and deploy cloud services on the target server; and then instruct the logistics transport 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 expand the edge nodes in the target edge cluster. This embodiment implements a full-link expansion process that integrates user-submitted edge resource expansion requests, server production, transportation, and edge cluster deployment, achieving integrated and end-to-end edge node expansion.
[0152] In an embodiment of the present application, the memory is used to store computer programs and can be configured to store various other data to support operations on the device where it is located. The processor can execute the computer program stored in the memory to implement the 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), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
[0153] In the embodiment of the present application, the processor can be any hardware processing device that can execute the logic of the above method. 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 device (PAL), a general array logic device (GAL), a complex programmable logic device (CPLD); or an application specific integrated circuit (ASIC) chip; or an advanced reduced instruction set (RISC) processor (Advanced RISC Machines, ARM) or a system on chip (SoC), etc., but is not limited thereto.
[0154] In an embodiment of the present application, the communication component is configured to facilitate wired or wireless communication between the device in which it is located and other devices. The device in which the communication component is located can access a wireless network based on a communication standard, such as Wireless Fidelity (WiFi), 2G or 3G, 4G, 5G or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component can also be based on Near Field Communication (NFC) technology, Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology or other technologies.
[0155] In an embodiment of the present 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 may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can not only sense the boundaries of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
[0156] In embodiments of the present application, a power supply assembly is configured to provide power to various components of the device in which it is located. The power supply assembly 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 assembly is located.
[0157] In an embodiment of the present application, the audio component may be configured to output and / or input audio signals. For example, the audio component includes a microphone (MIC), and when the device where the audio component is located is in an operating mode, such as call mode, recording mode, and voice recognition mode, the microphone is configured to receive external audio signals. The received audio signal may be further stored in a memory or sent via a communication component. In some embodiments, the audio component further includes a speaker for outputting audio signals. For example, for a device with a language interaction function, voice interaction with the user can be achieved through the audio component.
[0158] It should be noted that the descriptions such as "first" and "second" in this article are used to distinguish different messages, devices, modules, etc., and do not represent the order of precedence, nor do they limit "first" and "second" to different types.
[0159] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, compact disc read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical storage, etc.) that contain computer-usable program code.
[0160] The present application is described with reference to the flow chart and / or block diagram of the method, device (or system) and computer program product according to the embodiment of the present application. It should be understood that each flow process and / or box in the flow chart and / or block diagram and the combination of the flow process and / or box in the flow chart and / or block diagram can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processing machine or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for realizing the function specified in one flow chart flow or multiple flows and / or one box or multiple boxes of the block diagram.
[0161] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0162] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0163] In a typical configuration, a computing device includes one or more processors (such as a CPU, etc.), input / output interfaces, network interfaces, and memory.
[0164] Memory may include non-permanent storage in a computer-readable medium, random-access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.
[0165] Computer storage media is readable storage media, also known as readable media. Readable storage media include permanent and non-permanent, removable and non-removable media that 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 technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. According to the definition in this article, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.
[0166] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, commodity, or apparatus comprising the aforementioned elements.
[0167] The above content is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and modifications. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should be included in the scope of the claims of the present application.
Claims
1. A method for expanding edge resources, characterized in that: Applicable to a central service node in a central cloud; the method comprises: Obtain edge resource expansion requests provided by target users; Based on the edge resource expansion request, providing a server production request to a server producer to request the server producer to produce a target server; Installing an operating system on the target server and deploying cloud services; A transport instruction is sent to a logistics transporter to instruct the logistics transporter to transport the target server to a target edge cluster corresponding to the target user, so that the target server is deployed in the target edge cluster.
2. The method according to claim 1, characterized in that The providing a server production request to a server producer based on the edge resource expansion request includes: Acquire the resource expansion type and the amount of resources to be expanded from the edge resource expansion request; In the case where the resource expansion type is the whole cabinet expansion type, constructing infrastructure information of the cabinet to be expanded; based on the infrastructure information and the amount of resources to be expanded, providing a server production request to a server manufacturer to request the server manufacturer to produce the cabinet to be expanded and the target server; the target server is to be deployed in the cabinet to be expanded; In the case where the resource expansion type is a non-whole cabinet expansion type, based on 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 target server; the target server is to be deployed in an existing cabinet of the target edge cluster.
3. The method according to claim 2, characterized in that The infrastructure information of the cabinet to be expanded is constructed, including: Determine the location of the cabinet to be expanded in the computer room of the operation and maintenance party of the central cloud according to the location information of the existing cabinet of the target edge cluster in the computer room of the central cloud; Determine the network topology of the cabinet to be expanded according to the network topology of the existing cabinets of the target edge cluster in the computer room of the operation and maintenance party; Obtaining the network demand of the target user from the edge resource expansion request; determining the network resource information of the cabinet to be expanded according to the network demand of the target user and the network resources provided by the operation and maintenance party; The location of the cabinet to be expanded in the computer room of the operation and maintenance party, the network topology of the cabinet to be expanded, and the network resource information of the cabinet to be expanded are used as the infrastructure information of the cabinet to be expanded.
4. The method according to claim 2, characterized in that: In the case where the resource expansion type is a whole cabinet expansion type, the method further includes: Constructing a network topology structure of the target server in a physical network of an operator of the target server according to the infrastructure information; Apply for a network address for the target server in the network segment of the operation and maintenance party; Generate the network address of the target server according to the device configuration specification, the network topology and the network address Configuration information; After the cabinet to be expanded is connected to the physical network of the operation and maintenance party, the network configuration information of the target server is provided to the target server.
5. The method according to any one of claims 1 to 4, characterized in that: Before installing the operating system on the target server and deploying the cloud service, the following steps are also included: Performing performance testing on the target server; When it is detected that the performance of the target server meets the standard, the operation of installing the operating system on the target server and deploying the cloud service is performed; The performing of performance testing on the target server includes: Detecting the network quality of the target server; and / or, performing a hardware environment test on the target server; and / or, performing a stress test on the target server.
6. The method according to claim 2, characterized in that Deploying a cloud service on the target server includes: In the case where the capacity expansion type is the whole cabinet capacity expansion type, a block storage service is deployed on the target server in the cabinet to be expanded; an image file of a cloud computing service is obtained; according to the image file of the cloud computing service, a cloud computing service is deployed on the target server in the cabinet to be expanded, and a network configuration is performed for the cloud computing service; an infrastructure operation and maintenance plug-in is deployed on the target server; or, In the case where the expansion type is a non-whole cabinet expansion type, an image file of a cloud computing service is obtained; based on the image file of the cloud computing service, the cloud computing service is deployed on a target server in the cabinet to be expanded, and a network configuration is performed for the cloud computing service; an infrastructure operation and maintenance plug-in is deployed on the target server.
7. The method according to claim 6, characterized in that In the case where the capacity expansion type is a whole cabinet capacity expansion type, the method further includes: The infrastructure operation and maintenance plug-in is called to configure a security gateway for the target server in the cabinet 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 the transportation instruction to the logistics transporter, the method further includes: In the case where the capacity expansion type is a whole cabinet capacity expansion type, performing a secondary detection on the network quality of the target server, and obtaining a network quality detection result of the secondary detection; 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 or 6-8, characterized in that: After deploying the cloud service on the target server and before sending the transportation instruction to the logistics transporter, the method further includes: Setting the identifier of the target server as a blacklist tag of the operation and maintenance system in the central service node so that the operation and maintenance system does not recognize the target server; Adding an expansion lock tag to the identifier of the target server so that the control system of the target user is not aware of the target server; And, 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; An expansion lock tag is added to the identifier of the target server so that the control system of the target user can perceive the target server.
10. The method according to any one of claims 1-4 or 6-8, characterized in that: After deploying the cloud service on the target server and before sending the transportation instruction to the logistics transporter, the method further includes: Modify the network connection and domain name system resolution configuration of the target server; The virtual IP address of the target server is modified to the virtual IP address of any connection channel corresponding to the available zone of the target edge cluster.
11. The method according to any one of claims 1 to 4 or 6 to 8, characterized in that: After the target server is deployed in the target edge cluster, the method further includes: Performing network configuration and network debugging on the target server and the cabinet where the target server is located until the target server and the cabinet 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 are transmitted from the full gateway to the central service node through the dedicated network; the target mode is a mode in which the target server is managed and maintained by the central cloud; Performing dynamic environment monitoring configuration on the target server, and synchronizing the dynamic environment 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 for the target server is verified by cloud-edge collaboration.
12. An edge cloud system, characterized in that: include: A central cloud, and at least one edge cluster network-connected to the central cloud; The central cloud includes: a central service node; the edge cluster includes: a cabinet and an edge node deployed in the cabinet; 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, and is configured to execute the computer program to perform the steps in the method according to any one of claims 1 to 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 execute the steps in the method according to any one of claims 1 to 11.
Citation Information
Patent Citations
Container service cluster node scheduling method and device, server and storage medium
CN112235383A
Node cluster management method and device, equipment and storage medium
CN112799789A
Private network connection method and device, equipment and storage medium
CN112994949A
Expansion method of edge resources, edge cloud system, equipment and storage medium
CN116647559A
Network system, service provision and resource scheduling method, device, and storage medium
WO2020207264A1
Cited By
Edge cluster node label synchronization method and device, electronic equipment, storage medium and program product
CN119788689A
