CN116647559A

CN116647559A - Edge resource capacity expansion method, edge cloud system, equipment and storage medium

Info

Publication number: CN116647559A
Application number: CN202310512722.4A
Authority: CN
Inventors: 焦日华; 李刚; 吴德新; 刘阳阳; 杨根超; 张澄虞
Original assignee: Alibaba China Co Ltd
Current assignee: Alibaba China Co Ltd
Priority date: 2023-05-08
Filing date: 2023-05-08
Publication date: 2023-08-25
Also published as: WO2024230429A1

Abstract

Embodiments of the present application provide a method for expanding the capacity of edge resources, an edge cloud system, a device, and a storage medium. In the embodiment of this application, the central service node in the central cloud can request the server producer to produce the target server based on the target user's edge resource expansion request; and install the operating system on the target server and deploy cloud services; after that, it can instruct the logistics The transport party transports the target server to the target edge cluster corresponding to the target user, so as to deploy the target server on the target edge cluster and realize the expansion of the edge nodes in the target edge cluster. In this embodiment, a full link process of capacity expansion is realized, which integrates the user's edge resource expansion request, server production, transportation, and edge cluster deployment, and realizes the integration of edge node expansion and end-to-end edge node expansion.

Description

Edge resource capacity expansion method, edge cloud system, equipment and storage medium

Technical Field

The present application relates to the field of cloud computing technologies, and in particular, to a method for expanding an edge resource, an edge cloud system, an edge cloud device, and a storage medium.

Background

Traditional cloud computing adopts a centralized Data Center (DC) mode, and has strong computing power. However, mass emerging mobile and internet of things device applications continue to emerge, and this centralized DC-dependent cloud computing mode can no longer well meet the needs of users. To solve the problem of centralized cloud computing, edge computing has been developed.

The edge cloud consists of edge nodes distributed in the same region, specifically processes service requests of users in the local region, and can rapidly and flexibly provide cloud computing services for the users. With the development of user applications, more and more users put forward the demand for edge node capacity expansion.

Disclosure of Invention

The application provides a capacity expansion method of edge resources, an edge cloud system, equipment and a storage medium, which are used for realizing integration of edge node capacity expansion.

The embodiment of the application provides a capacity expansion method of edge resources, which is suitable for a central service node in a central cloud; the method comprises the following steps:

acquiring an edge resource capacity expansion request provided by a target user;

providing a server production request to a server producer based on the edge resource capacity expansion request 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 transport instruction to a logistics transport party to instruct the logistics transport party to transport the target server to a target edge cluster corresponding to the target user, so that the target server is deployed on the target edge cluster.

The embodiment of the application also provides an edge cloud system, which comprises: a central cloud, and at least one edge cluster connected with the central cloud network; the center cloud includes: a central service node; the edge cluster includes: the cabinet and the edge nodes deployed on the cabinet;

the central service node is configured to execute the steps in the above-mentioned edge resource capacity expansion method.

The embodiment of the application also provides a computing device, which comprises: a memory, a processor, and a communication component; wherein the memory is used for storing a computer program;

the processor is coupled to the memory and the communication component for executing the computer program for performing the steps in the above-described method of expanding an edge resource.

Embodiments of the present application also provide a computer-readable storage medium storing computer instructions that, when executed by one or more processors, cause the one or more processors to perform steps in a method for expanding an edge resource as described above.

In the embodiment of the application, the central service node in the central cloud can request the server producer to produce the target server based on the edge resource capacity expansion request of the target user; installing an operating system on a target server and deploying cloud services; and then, the logistics transport party can be instructed to transport the target server to the target edge cluster corresponding to the target user so as to deploy the target server to the target edge cluster, thereby realizing the capacity expansion of the edge nodes in the target edge cluster. According to the embodiment, the capacity expansion all-link flow integrating the production, the transportation and the edge cluster deployment of the server into a whole is realized, and the integration of the capacity expansion of the edge nodes and the capacity expansion of the edge nodes from end to end are realized.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:

fig. 1 is a schematic structural diagram of an edge cloud system according to an embodiment of the present application;

FIG. 2 is a specific flow chart of a capacity expansion process of an edge resource according to an embodiment of the present application;

Fig. 3 is a flow chart of a method for expanding edge resources according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a computing device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

In some embodiments of the present application, a central service node in the central cloud may request a server producer to produce a target server based on an edge resource capacity expansion request of the target user; installing an operating system on a target server and deploying cloud services; and then, the logistics transport party can be instructed to transport the target server to the target edge cluster corresponding to the target user so as to deploy the target server to the target edge cluster, thereby realizing the capacity expansion of the edge nodes in the target edge cluster. According to the embodiment, the capacity expansion all-link flow integrating the production, the transportation and the edge cluster deployment of the server into a whole is realized, and the integration of the capacity expansion of the edge nodes and the capacity expansion of the edge nodes from end to end are realized.

The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.

It should be noted that: like reference numerals denote like objects in the following figures and embodiments, and thus once an object is defined in one figure or embodiment, further discussion thereof is not necessary in the subsequent figures and embodiments.

Fig. 1 is a schematic structural diagram of an edge cloud system according to an embodiment of the present application. As shown in fig. 1, the edge cloud system includes: a central cloud 10 and at least one edge cluster 20 in network connection with the central cloud 10.

The edge cloud is a cloud computing platform constructed on an edge infrastructure based on the cloud computing technology and the edge computing capability, and is a cloud platform with the computing, network, storage, security and other capabilities at the edge position. The edge cloud is a relative concept, the edge cloud is a cloud computing platform relatively close to a terminal, or is different from a management node or a traditional cloud computing platform, the management node or the traditional cloud computing platform can comprise a data center or a machine room with large resource scale and concentrated positions, the edge cloud is composed of a plurality of edge cloud nodes, the resource scale of a single edge cloud node is smaller, but the number of the edge cloud nodes is larger, so that the coverage range of the edge cloud is wider. In other words, the edge cloud system of the embodiment is also a cloud computing platform constructed on the edge infrastructure based on the cloud computing technology and the edge computing capability, is a cloud platform with computing, network, storage, security and other capabilities at the edge location, is a cloud computing platform relatively close to the terminal, and is also a network system constructed based on management and control nodes or the infrastructure between the traditional cloud computing system and the terminal. The terminal related to the embodiment refers to a demand end of a cloud computing service, and may be, for example, a terminal or a user end in the internet, or a terminal or a user end in the internet of things.

In this embodiment, the central cloud 10 is deployed with a central service node 101, and is combined with the edge clusters 20 and the terminals (not shown in fig. 1), so that a network architecture of "cloud edge three-body collaboration" can be formed, in which tasks such as network forwarding, storage, calculation, and intelligent data analysis can be put into each edge cluster 20 for processing, and since the edge clusters 20 are closer to the terminals, response delay can be reduced, pressure of management and control nodes or traditional cloud computing platforms can be reduced, and bandwidth cost can be reduced.

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

In this embodiment, one edge cluster 20 may be one machine room, one Data Center (DC), or an internet Data Center (Internet Data Center, IDC), etc. For an edge cloud network, one edge cluster 20 may include one or more edge nodes. The plural means 2 or more than 2. Each edge node may include a series of edge infrastructures including, but not limited to: distributed Data Center (DC), wireless room or cluster, operator's communication network, core network devices, base stations, edge gateways, home gateways, computing devices or storage devices, and corresponding network environments, etc. The location, capabilities, and inclusion of infrastructure of the different edge nodes may or may not be the same as described herein.

In this embodiment, the edge node may provide various resources to the outside. In this embodiment, the resources provided by the edge node may include hardware resources and software resources. Wherein the hardware resources may include: computing resources such as processors, memory, disk, and the like. The processor may be a central processing unit (Central Processing Unit, CPU), a parallel processor, or the like. The parallel processor may be a graphics processor (Graphics Processing Unit, GPU), a Field programmable gate array (Field-Programmable Gate Array, FPGA), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or the like. The software resources may include: bandwidth, network segment, network card configuration, etc., and an operating system, etc.

In this embodiment, the infrastructure such as the edge nodes in the edge cluster 20 may belong to the users of the edge cluster 20, and are local resources for the users, and are operated and maintained by the users. Of course, the infrastructure such as edge nodes in the edge cluster 20 may also be partially or fully implemented as a target model, that is, partially or fully belonging to a public cloud (such as the central cloud 10), and operated and maintained by the public cloud. The target mode is to extend and deploy infrastructure such as public cloud computing, storage, network and the like to a local machine room of a user in a soft and hard integrated mode, and full support cloud service meeting requirements of data security, data local processing, low delay and the like is realized. The target mode is the extension of public cloud in the local data center of the user, infrastructure resources belonging to the public cloud are deployed in the local machine room or IDC of the user, and the public cloud manages and maintains the infrastructure resources corresponding to the target mode.

The rack (also called a cabinet) is used as an infrastructure of a data center or a machine room, can be used as a carrier for storing servers, and can also provide power, communication and other resources for the servers. For edge clusters 20, it may include: a cabinet 201; the cabinet 201 is used to install edge nodes. The cabinet 201 is a carrier for storing edge nodes and may provide resources such as power and communications for the edge nodes. Each cabinet 201 may be equipped with 1 or more edge nodes.

In this embodiment, the central service node 101 may also provide an edge node capacity expansion function. Specifically, as shown in fig. 1 and 2, a user of an edge cluster to be expanded (defined as a target user) may provide an edge resource expansion request to the central cloud 10 (step 1 of fig. 1 and 2).

Wherein, the edge resource capacity expansion request may include: a resource capacity expansion type (ReasonType) and an amount of resources to be expanded. The amount of resources to be expanded may be expressed in stock units (Stock Keeping Unit, SKU). SKUs may be the basic unit of out-sales by the edge cluster 20, integrating computing, storage, networking, etc., and one SKU may be packaged as an entire cabinet.

The resource capacity expansion type comprises: the whole cabinet expansion type and the non-whole cabinet expansion type. The edge resource is expanded with the following 3 scenes: (1) Only the original computing SKU in the edge cluster is upgraded, i.e. the computing resources are expanded in the existing cabinet of the edge cluster 20; (2) Expanding the new computing SKU, and expanding computing resources in the form of a whole cabinet; (3) The original computing SKU is upgraded, and the new computing SKU is expanded, namely, the computing resources of the existing cabinet and the new cabinet are expanded. In the embodiment of the application, the resource capacity expansion type corresponding to the scene (1) can be defined as a non-whole cabinet capacity expansion type; and the resource capacity expansion types corresponding to the scenes (2) and (3) are defined as the capacity expansion type of the whole cabinet.

The central service node 101 can acquire an edge resource capacity expansion request provided by a target user; and provides a server production request to the service producer 30 based on the edge resource capacity expansion request to request the server producer 30 to produce the target server (step 2 of fig. 1 and steps 2 and 3 of fig. 2).

Specifically, as shown in fig. 2, the central management node 101 may obtain the type of resource expansion and the amount of resources to be expanded from the edge resource expansion request.

Further, if the resource expansion type is a non-whole cabinet expansion type, infrastructure information of the cabinet to be expanded may be constructed (corresponding to "constructing infrastructure modeling" in step 2 of fig. 2). The cabinet to be expanded comprises at least one target server to be expanded.

Specifically, the position of the rack to be expanded in the machine room of the operation and maintenance party of the rack to be expanded can be determined according to the position information of the existing rack of the target edge cluster in the machine room of the operation and maintenance party of the rack to be expanded. The target edge cluster is an edge cluster of a target user which belongs to the edge resource capacity expansion request.

For the target mode, the operation and maintenance party of the existing cabinet of the target edge cluster is a central cloud. The central service node 101 may logically number the cabinets in the target edge cluster and create a logical cabinet in the machine room of the operation and maintenance party; and then, planning the position of the cabinet to be expanded in the machine room of the operation and maintenance party according to the position information of the existing cabinet of the target edge cluster in the machine room of the operation and maintenance party.

The central service node 101 may further determine a network topology structure of the cabinet to be expanded according to a network topology structure of the existing cabinet of the target edge cluster in the machine room of the operation and maintenance party; obtaining the network demand of the target user from the edge resource capacity expansion request; further, network resource information of the cabinet to be expanded can be determined according to network requirements of the target user and network resources provided by the operation and maintenance party. The network resource information refers to resources required by the device to enable network communication, and may include: network segments, routing and domain name systems (Domain Name System, DNS), etc., may also include the network mode of the device. The network mode may be a virtual private network (Virtual Private Network, VPN) mode, a virtual private cloud (Virtual Private Cloud, VPC) mode, or a network private line mode, among others. The network mode refers to a network communication mode between the cabinet and the central cloud 10, and refers to which mode the cabinet adopts to communicate with the central cloud 10.

Specifically, the central service node 101 may obtain, from the network requirement of the target user, the number requirement N of internet protocol (Internet Protocol, IP) addresses of the target user; further, N unassigned IP addresses may be determined from the network segment provided by the operation and maintenance party, as IP addresses of the enclosure to be expanded, and so on. The central service node 101 may also use the routing information of the operation and maintenance party as the routing information of the cabinet to be expanded, and so on. And acquiring the network mode selected by the target user from the network requirements of the target user, and taking the network mode as the network mode of the cabinet to be expanded.

Further, the position of the cabinet to be expanded in the machine room of the operation and maintenance party, the network topology structure 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.

The above-mentioned infrastructure information included only with the infrastructure information is: the location of the cabinet to be expanded in the machine room of the operation and maintenance side, the network topology of the cabinet to be expanded, and the network resource information of the cabinet to be expanded are taken as examples, and the embodiment of constructing the infrastructure information of the cabinet to be expanded is described as an example, but it does not mean that the infrastructure information only includes the above-mentioned infrastructure information, and it does not mean that the infrastructure information includes the above-mentioned infrastructure information.

After determining the infrastructure information of the enclosure to be expanded, the central service node 101 may send a server production request to the server producer requesting the server producer to produce the enclosure to be expanded and the target server based on the infrastructure information and the amount of resources to be expanded (step 3 of fig. 2). The cabinet to be expanded includes at least one target server. The server production request may include infrastructure information of the enclosure to be expanded, the amount of resources to be expanded, and the like.

Specifically, the central service node 101 may issue a server production request to a server producer according to the amount of resources to be extended and the infrastructure information; after receiving the server production request, the server producer starts to produce the cabinet to be expanded and the target server in the cabinet according to the resource quantity to be expanded and the infrastructure information; and after the production is completed, the system is transported to the cabinet to be expanded and the operation and maintenance side of the target server (step 3 of fig. 1, "transporting the target server"). The operation and maintenance party of the cabinet to be expanded and the target server can be the operation and maintenance party of the central cloud.

In some embodiments, if the resource expansion type is a non-whole cabinet expansion type, the central service node 101 may send a server production request to the server producer to request the server producer to produce the target server based on the amount of the resource to be expanded (step 3 of fig. 2). In this embodiment, the target server is to be installed in an existing enclosure of the target edge cluster. In this embodiment, the server production request may include the amount of resources to be extended, etc.

Specifically, the central service node 101 may issue a server production request to the server producer 30 according to the amount of resources to be expanded; after receiving the server production request, the server producer starts to produce a target server to be expanded according to the resource quantity to be expanded; and after the production is completed, the server is transported to the operation and maintenance side of the target server to be expanded (step 3 of fig. 1, "transporting the target server"). The operation and maintenance party of the target server is deployed in the central cloud 10.

The operator enters the information of the target server to be expanded into a configuration management database (Configuration Management Database, CMDB) (fig. 2, step 4 "information entry CMDB"). The CMDB is a logical database that stores a series of related information of hardware and software assets (commonly referred to as configuration items), and the relationships between them.

For the embodiment that the resource capacity expansion type is the whole cabinet capacity expansion type, after the cabinet to be expanded reaches the operation and maintenance party, the operation and maintenance personnel of the operation and maintenance party can access the cabinet to be expanded into the physical network of the machine room of the operation and maintenance party based on the constructed infrastructure information (step 5 of fig. 2, the cabinet is accessed into the physical network).

The central service node 101 may install an operating system on the target server and deploy cloud services (step 4 of fig. 1 and steps 9 and 10 of fig. 2). Specifically, for embodiments in which the resource expansion type is a complete cabinet expansion type, the central service node 101 may deploy a block storage service on a target server in the cabinet to be expanded (step 9 of fig. 2); acquiring an image file of the cloud computing service, and deploying the cloud computing service on a target server in the cabinet to be expanded according to the image file of the cloud computing service (step 10 of fig. 2); and performing network configuration for the cloud computing service. The central service node 101 may also deploy infrastructure operation and maintenance plug-ins or the like on the target servers. The central service node 101 may also access the cloud computing service and the block storage service to a log collection system to log the cloud computing service and the block storage service. The central service node 101 may also initiate cloud computing service inspection tasks, self-tests, and the like.

In this embodiment, the central service node 101 may also invoke an infrastructure operations and maintenance plug-in to configure a security gateway for the target server in the enclosure to be extended (fig. 2 step 8 "security gateway deployment").

For the embodiment in which the resource capacity expansion type is the whole cabinet capacity expansion type, the central service node 101 may obtain an image file of the cloud computing service when the capacity expansion type is the non-whole cabinet capacity expansion type, 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 (fig. 2, step 10, "cloud computing service deployment"); and performing network configuration for the cloud computing service. The central service node 101 may also deploy infrastructure operation and maintenance plug-ins or the like on the target servers. The central service node 101 may also access the cloud computing service and the block storage service to a log collection system to log the cloud computing service and the block storage service. The central service node 101 may also initiate cloud computing service inspection tasks, self-tests, and the like.

The cloud services deployed on the target servers shown in the above embodiments are only exemplary and not limiting. Thereafter, as shown in fig. 1, the central service node 101 may send a transport instruction to the logistics transport party 40 to instruct the logistics transport party 40 to transport the target server to the target edge cluster corresponding to the target user, so that the target server is deployed on the target edge cluster (steps 5-7 in fig. 1).

In this embodiment, a central service node in the central cloud may request a server producer to produce a target server based on an edge resource capacity expansion request of a target user; installing an operating system on a target server and deploying cloud services; and then, the logistics transport party can be instructed to transport the target server to the target edge cluster corresponding to the target user so as to deploy the target server to the target edge cluster, thereby realizing the capacity expansion of the edge nodes in the target edge cluster. According to the embodiment, the capacity expansion all-link flow integrating the production, the transportation and the edge cluster deployment of the server into a whole is realized, and the integration of the capacity expansion of the edge nodes and the capacity expansion of the edge nodes from end to end are realized. The end-to-end refers to the process from the user to the process from the edge resource capacity expansion request to the process of realizing the capacity expansion of the edge node in the edge cluster of the user.

In some embodiments of the present application, as shown in fig. 2, before installing an operating system on a target server and deploying a cloud service, for an embodiment in which the resource capacity expansion type is a complete machine capacity expansion type, the central service node 101 may also perform network construction on a rack to be expanded (step 6 in fig. 2). Specifically, the central service node 101 may construct a network topology structure of the target server in the physical network of the operation and maintenance party of the central cloud according to the infrastructure information; applying for a network address for the target server in the network of the operation and maintenance party; generating network configuration information of the target server according to the equipment configuration specification, the network topology structure and the network address of the target server; and providing the network configuration information of the target server to the target server after the cabinet to be expanded is accessed to the physical network of the operation and maintenance party.

The central service node 101 may also perform performance testing on the target server (step 7 of fig. 2) before installing the operating system on the target server and deploying the cloud service. Specifically, the performance of the target server may include: network quality of the target server, hardware environment quality of the target server, software pressure of the target server, and the like.

Accordingly, when performing performance testing on the target server, the central service node 101 may perform performance testing in at least one of the following embodiments:

embodiment 1: the network quality of the target server is detected. Specifically, the central service node 101 may detect the correctness of the network connection and the network connectivity of the target server. Specifically, the central service node 101 may instruct the target server to send data packets to other devices; and collecting network quality parameters of the target server based on the data packets. The network quality parameter refers to a parameter reflecting network performance, and may include: packet loss rate, delay, etc. Further, the network quality of the target server may be determined based on the network quality parameters of the target server.

Embodiment 2: and detecting the hardware environment of the target server. The hardware environment refers to a computer physical system consisting of a computer and peripheral devices thereof. Specifically, the center service node 101 may test whether each hardware of the target server is abnormal. For example, the central service node 101 may test whether the processor of the target server is abnormal. Specifically, the central service node 101 may instruct the processor of the target server to run the set functions; and if the operation is successful, the processor of the target server is normal. For another example, the central service node 101 may also test whether the storage medium of the target server is abnormal. Specifically, the central service node 101 may read and write data from and to the storage medium; if the data read-write speed meets the set read-write speed requirement, determining that the storage medium of the target server is normal, and the like.

Embodiment 3: and performing pressure test on the target server. Specifically, the central service node 101 may input concurrent execution tasks to the target server, running the test under conditions of starvation of system resources of the target server. The resources for software stress testing include internal memory, CPU availability, disk space, network bandwidth, and the like.

Further, in the case that the performance of the target server meets the standards, the above-described operation of installing an operating system on the target server and deploying the cloud service is performed.

In some embodiments of the present application, for embodiments in which the resource capacity expansion type is whole cabinet capacity expansion, after the cloud service is deployed on the target server, the central service node 101 may perform secondary detection on the network quality of the target server in the cabinet to be expanded, so as to obtain a network quality detection result (step 12 in fig. 2). Accordingly, the center service node 101 may acquire the network quality detection result (step 17 "network quality secondary detection result recovery" of fig. 2). Optionally, the network quality of the target server in the rack to be expanded may be asynchronously detected secondarily to obtain a network quality detection result (step 12 of fig. 2), and the network detection result may be asynchronously obtained. Wherein asynchronous refers to execution asynchronously with steps 13-16.

If the network quality detection result indicates that the network quality of the target server in the cabinet to be expanded is normal, the subsequent operation can be executed; 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 are continuously performed.

In some embodiments, to prevent false alarms of the newly expanded target server before formally putting into production or false operations such as triggering a drop-out by the operation and maintenance system of the operation and maintenance party being identified as abnormal, the central service node 101 may further set the identification of the target server to a blacklist tab of the operation and maintenance system after the cloud service is deployed on the target server (fig. 2, step 11, "target server blackout"). The operation and maintenance system does not identify the server with the blacklist label, so that misoperation such as off-line triggering and the like caused by the fact that the operation and maintenance system identifies the newly expanded target server as abnormal can be prevented. Further, the central service node 101 may further add a capacity expansion locking tag to the identifier of the target server, so that the control system of the target user does not have a sense on the target server. Wherein, the dilatation locking label can be realized as: biz_status= 'mlock' (state locked); lock_type= 'other' (lock type is other); lock_releas= 'cloudebox scaleout' (lock cause is target mode expansion), etc. The control system of the target user can determine that the target server is not deployed to the target edge cluster based on the capacity expansion locking tag, but is not opened for the target user to use.

In some embodiments, the central service node 101 may further perform a marking process on the CMDB on the target server (step 13 "server marking" in fig. 2), where the marked tag is used to characterize the ownership of the target server, so that the operation and maintenance system in the central service node 101 may apply an operation and maintenance policy adapted by the owner to the target server to perform operation and maintenance on the target server. For example, for a target schema scenario, a target server may be tagged with a target schema specific resource tag on the CMDB. Accordingly, the operation and maintenance system in the central service node 101 adopts the operation and maintenance policy adapted to the target mode for the target server, and performs operation and maintenance on the target server.

In other embodiments, for information security, the central service node 101 may further perform at least one sensitive information detection on the target server before instructing the logistics transporter 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 (step 14 "sensitive information clean" and step 16 "sensitive information secondary clean" of fig. 2).

Optionally, the central service node 101 may perform at least one sensitive information detection on the target server according to a preset sensitive information list; and determining the information in the sensitive information list on the target server as sensitive information. Further, the detected sensitive information may be deleted from the target server.

In the present embodiment, the number and order of detection of sensitive information to the target server are not limited. Fig. 2 illustrates an example of secondary sensitive information detection performed on the target server, but the present application is not limited thereto. Sensitive information detection may occur before or after any stage or operation until no sensitive information is detected on the target server. Preferably, the target server may be subjected to sensitive information detection before the target server is powered off, until the target server is not provided with sensitive information, and then the target server is powered off.

In some embodiments of the present application, central service node 101 may also modify the network connection and DNS resolution configuration of the target server prior to sending the transport instructions to the logistics transport party; and modifies the virtual IP address of the target server to the virtual IP address of Any connection channel (Any Tunnel) corresponding to the available area of the target edge cluster, so that the target server may communicate with the central cloud after being deployed to the target edge cluster (step 15 "modify network connection configuration" in fig. 2). Wherein the virtual IP of the AnyTunnel is a public access VIP provided in the VPC network, which has access to all VPCs.

Optionally, after the virtual IP address of the target server is modified to the virtual IP address of Any connection channel (Any Tunnel) corresponding to the available area of the target edge cluster, the sensitive information detection may be performed on the target server again until no sensitive information exists on the target server (step 16 "sensitive information secondary cleaning" in fig. 2). Thereafter, a shutdown process may be performed on the target server.

Alternatively, the central service node 101 may remotely control the target server to power off (step 18 "remote power off" of fig. 2). In some embodiments, central service node 101 may remotely control the cloud computing service and the block storage service of the target server to shut down; and remotely controlling the target server to be powered off after the cloud computing service and the block storage service of the target server are powered off. An operator of the operation and maintenance party of the target server may perform network disconnection and power outage on the target server in a machine room of the operation and maintenance party (step 19 of fig. 2, "power outage and power outage"). Thereafter, a package delivery may be made to the target server to the target user (step 20 "package delivery" of FIG. 2).

Thereafter, the central service node 101 may send a transport instruction to the logistics transport party 40 to instruct the logistics transport party 40 to transport the target server to the target edge cluster corresponding to the target user (step 21 "logistics transport" in fig. 2).

The worker of the target edge cluster or the worker of the operator of the target server may deploy the target server to the target edge cluster (fig. 2, step 22, "target server is deployed to the target edge cluster"); and performs physical network connection and power supply to the target server.

Further, the central service node 101 may 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 (step 23 "network configuration and debugging" in fig. 2). For the embodiment of the whole cabinet expansion, 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.

In some embodiments, for compute nodes whose target server is in the target mode, the central service node 101 may also switch the network mode of the target server to the target mode for transmission of the data packets of the target server by the security gateway to the central service node over the private network (step 24 "security gateway offload" of fig. 2). The private network may be a private communication network between the compute node of the target mode and the central cloud, such as a VPC, VPN, or private network line, etc. Specifically, switching the network mode of the target server to the target mode may enable the security gateway to proxy the data packet of the target server and transmit it to the central service node 101 through the private network.

In some embodiments, the central service node 101 may also perform a ring monitoring configuration on the target server (step 25 "ring monitoring configuration" of fig. 2), and synchronize the ring monitoring configuration information to the operation and maintenance system in the central service node. The dynamic ring monitoring is to monitor the target server and the environment variable in the target server in a centralized way by the pointer.

In some embodiments of the present application, after the target server is deployed on the target edge cluster, the central service node 101 may further detect the network quality of the target server on the target edge cluster (step 26 "network quality detection" in fig. 2), and verify the management capability of the central service node on the target server in a cloud-edge cooperative manner (step 27 "cloud-edge cooperative verification" in fig. 2).

When the central service node 101 detects the network quality of the target server in the target edge cluster, the central service node can control the target server to send detection data packets to other devices; acquiring network quality parameters of the target server based on the detection data packet; and then, according to the network quality parameters of the target server, determining the network quality of the target server in the target edge cluster.

In some embodiments, the central service node 101 may verify the management capability of the central service node to the target server in a cloud-edge cooperative manner. Specifically, the central service node 101 may verify its lifecycle management capability of the cloud computing service of the target server in a cloud-edge cooperative manner. For example, the central service node 101 may create, launch, and destroy cloud computing services on a target server, enabling verification of lifecycle management capabilities of the cloud computing services of the target server. And/or, the central service node 101 may also adopt a cloud edge cooperative manner to verify the operation and maintenance capability of the operation and maintenance system in the central service node to the target server. For example, the central service node 101 may perform operations such as operation and maintenance on the target server, and obtain an operation and maintenance operation result; if the operation result of the operation and maintenance shows that the operation and maintenance of the operation and maintenance system is normal, determining that the operation and maintenance capability of the operation and maintenance system on the target server meets the standard, and the like.

During actual use, the target user may also make an acceptance or the like with the target server (step 28 "target user acceptance" of fig. 2). The acceptance process of the target user is not in the protection scope of the application, so that redundant description is not made.

After the above operations are completed and various performance tests are up to standard, the central service node 101 may release the blacklist tab of the operation and maintenance system corresponding to the identification of the above-mentioned target server (step 29 of fig. 2, "release blacklist"). In this way, the operation and maintenance system of the target server can identify the target server. Furthermore, the expansion locking label can be added on the identification of the target server, so that the control system of the target user can sense the target server and open the target server for the user.

It should be noted that, the processing flow of the unidentified "(whole cabinet)" in fig. 2 is a common processing flow of the whole cabinet expansion and the non-whole cabinet expansion; the processing flow marked with the whole cabinet is the unique processing flow for the whole cabinet capacity expansion.

The edge node capacity expansion flow provided in fig. 2 can realize end-to-end edge node capacity expansion. The full-link flow of the edge node capacity expansion integrates the operations of hardware installation, software deployment, network erection, safety compliance, logistics relocation, cloud edge collaborative verification and the like, and realizes the integrated capacity expansion of the edge cluster nodes. In addition, the capacity expansion method of the edge node provided by the embodiment of the application can be compatible with the capacity expansion of the whole cabinet and the capacity expansion of the non-whole cabinet.

In addition to the above-mentioned edge cloud system, the embodiment of the present application further provides an edge resource capacity expansion method, and an exemplary description is given below of the edge resource capacity expansion method provided by the embodiment of the present application.

Fig. 3 is a flow chart of a method for expanding edge resources according to an embodiment of the present application. The capacity expansion method is suitable for the central service node in the central cloud. As shown in fig. 3, the capacity expansion method mainly includes:

301. and acquiring an edge resource capacity expansion request provided by a target user.

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

303. Installing an operating system on a target server and deploying cloud services.

304. And sending a transport instruction to the logistics transport party to instruct the logistics transport party to transport the target server to the target edge cluster corresponding to the target user so as to enable the target server to be deployed on the target edge cluster.

In this embodiment, the central service node may provide an edge node capacity expansion function. Specifically, a user of an edge cluster to be expanded (defined as a target user) may provide an edge resource expansion request to the central cloud. Wherein, the edge resource capacity expansion request may include: the type of the expansion of the resource and the amount of the resource to be expanded. The resource capacity expansion type comprises: the whole cabinet expansion type and the non-whole cabinet expansion type.

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

Specifically, the resource capacity expansion type and the amount of the resources to be expanded can be obtained from the edge resource capacity expansion request. Further, if the resource capacity expansion type is a non-complete machine cabinet capacity expansion type, infrastructure information of the cabinet to be expanded can be constructed. The cabinet to be expanded comprises at least one target server to be expanded.

For the target mode, the operation and maintenance party of the existing cabinet of the target edge cluster is a central cloud. The machine cabinets in the target edge cluster can be logically numbered, and logical cabinet positions are created in the machine room of the operation and maintenance party; and then, planning the position of the cabinet to be expanded in the machine room of the operation and maintenance party according to the position information of the existing cabinet of the target edge cluster in the machine room of the operation and maintenance party.

Further, the network topology structure of the cabinet to be expanded can be determined according to the network topology structure of the existing cabinet of the target edge cluster in the machine room of the operation and maintenance party; obtaining the network demand of the target user from the edge resource capacity expansion request; further, network resource information of the cabinet to be expanded can be determined according to network requirements of the target user and network resources provided by the operation and maintenance party. The network resource information refers to resources required by the device to enable network communication, and may include: network segments, routes, DNS, etc., may also include the network mode of the device.

Specifically, the number requirement N of the IP addresses of the target user may be obtained from the network requirements of the target user; further, N unassigned IP addresses may be determined from the network segment provided by the operation and maintenance party, as IP addresses of the enclosure to be expanded, and so on. Further, the routing information of the operation and maintenance party can be used as the routing information of the cabinet to be expanded, and the like. And acquiring the network mode selected by the target user from the network requirements of the target user, and taking the network mode as the network mode of the cabinet to be expanded.

After determining the infrastructure information of the rack to be expanded, a server production request may be provided to the server producer requesting the server producer to produce the rack to be expanded and the target server based on the infrastructure information and the amount of resources to be expanded. The cabinet to be expanded includes at least one target server. The server production request includes: infrastructure information of the cabinet to be expanded and the amount of resources to be expanded.

Specifically, a server production request can be issued to a server producer according to the amount of resources to be expanded and the infrastructure information; after receiving the server production request, the server producer starts to produce the cabinet to be expanded and the target server in the cabinet according to the resource quantity to be expanded and the infrastructure information; and after the production is completed, the equipment is transported to an operation and maintenance party of the cabinet to be expanded.

In some embodiments, if the resource capacity expansion type is a non-complete cabinet capacity expansion type, a server production request may be provided to a server producer to request the server producer to produce a target server based on the amount of the resource to be expanded. In this embodiment, the target server is to be installed in an existing enclosure of the target edge cluster. The server production request includes the amount of resources to be extended, etc.

Specifically, a server production request can be issued to a server producer according to the amount of resources to be expanded; after receiving the server production request, the server producer starts to produce a target server to be expanded according to the resource quantity to be expanded; and after the production is completed, the target server is transported to an operation and maintenance party of the target server to be expanded. The operation and maintenance party of the target server is deployed in the central cloud.

The operator enters the information of the target server to be expanded into the CMDB. For the embodiment that the resource capacity expansion type is the capacity expansion type of the whole cabinet, after the cabinet to be expanded reaches the operation and maintenance party, the operation and maintenance personnel of the operation and maintenance party can access the cabinet to be expanded into the physical network of the machine room of the operation and maintenance party based on the constructed infrastructure information.

In step 303, an operating system may be installed on the target server and cloud services deployed. Specifically, for embodiments in which the resource expansion type is a complete machine cabinet expansion type, a block storage service may be deployed on a target server in a cabinet to be expanded; acquiring an image file of the cloud computing service, and deploying the cloud computing service on a target server in the cabinet to be expanded according to the image file of the cloud computing service; and performing network configuration for the cloud computing service. Further, infrastructure operation plug-ins and the like can also be deployed on the target servers. Of course, the cloud computing service and the block storage service can be accessed into the log acquisition system to acquire logs of the cloud computing service and the block storage service; and starting cloud computing service inspection tasks, self-test, inspection and the like.

In this embodiment, the infrastructure operation and maintenance plug-in may also be invoked to configure a security gateway for the target server in the rack to be extended.

For the embodiment of the resource capacity expansion type being the capacity expansion type of the whole cabinet, the image file of the cloud computing service can be obtained under the condition that the capacity expansion type is the capacity expansion type of the non-whole cabinet, and the cloud computing service is deployed on the target server in the cabinet to be expanded according to the image file of the cloud computing service; and performing network configuration for the cloud computing service. Furthermore, an infrastructure operation and maintenance plug-in and the like can be deployed on the target server, and the cloud computing service and the block storage service can be accessed into a log acquisition system so as to acquire logs of the cloud computing service and the block storage service, and tasks, self-test, inspection and the like when the cloud computing service inspection is started.

The cloud services deployed on the target servers shown in the above embodiments are only exemplary and not limiting. Thereafter, in step 304, a transport instruction may be sent to the logistics transport party to instruct the logistics transport party to transport the target server to the target edge cluster corresponding to the target user, so that the target server is deployed to the target edge cluster.

In some embodiments of the present application, before installing an operating system on a target server and deploying a cloud service, for an embodiment in which the resource capacity expansion type is a complete machine capacity expansion type, network construction may also be performed on a rack to be expanded. Specifically, a network topology structure of the target server in the physical network of the operation and maintenance side of the cabinet can be constructed according to the infrastructure information; applying for a network address for the target server in the network of the operation and maintenance party; generating network configuration information of the target server according to the equipment configuration specification, the network topology structure and the network address of the target server; and providing the network configuration information of the target server to the target server after the cabinet to be expanded is accessed to the physical network of the operation and maintenance party.

Performance detection may also be performed on the target server before installing the operating system on the target server and deploying the cloud service. Specifically, the performance of the target server may include: network quality of the target server, hardware environment quality of the target server, software pressure of the target server, and the like.

Optionally, in performing performance testing on the target server, performance testing may be performed using at least one of the following embodiments:

embodiment 1: the network quality of the target server is detected. Specifically, the correctness of the network connection and the network connectivity of the target server can be detected. Specifically, the target server may be instructed to send data packets to other devices; and collecting network quality parameters of the target server based on the data packets. The network quality parameter refers to a parameter reflecting network performance, and may include: packet loss rate, delay, etc. Further, the network quality of the target server may be determined based on the network quality parameters of the target server.

Embodiment 2: and detecting the hardware environment of the target server. The hardware environment refers to a computer physical system consisting of a computer and peripheral devices thereof. Specifically, whether or not each hardware of the target server is abnormal may be tested. For example, the target server's processor may be tested for anomalies. Specifically, the processor of the target server may be instructed to run the set functions; and if the operation is successful, the processor of the target server is normal. For another example, it may also be tested whether the storage medium of the target server is abnormal. Specifically, the data can be read from or written to the storage medium; if the data read-write speed meets the set read-write speed requirement, determining that the storage medium of the target server is normal, and the like.

Embodiment 3: and performing pressure test on the target server. Specifically, concurrent execution tasks may be input to the target server, and the test may be run under conditions of starvation of system resources of the target server. The resources for software stress testing include internal memory, CPU availability, disk space, network bandwidth, and the like.

In some embodiments of the present application, for embodiments in which the resource capacity expansion type is capacity expansion of a complete machine cabinet, after the cloud service is deployed on the target server and before a transport instruction is sent to the logistics transport party, network quality of the target server in the cabinet to be expanded may be detected secondarily, and a network quality detection result of the secondary detection may be obtained. If the network quality detection result indicates that the network quality of the target server in the cabinet to be expanded is normal, the subsequent operation can be executed; 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 are continuously performed.

In some embodiments, in order to prevent a new expanded target server from false alarming before formally putting into production or triggering incorrect operations such as offline due to being identified as abnormal by an operation and maintenance system of an operation and maintenance party, after a cloud service is deployed on the target server and before a transport instruction is sent to a logistics transport party, an identifier of the target server may be set as a blacklist tag of the operation and maintenance system. The operation and maintenance system does not identify the server with the blacklist label, so that misoperation such as off-line triggering and the like caused by the fact that the operation and maintenance system identifies the newly expanded target server as abnormal can be prevented. Further, a capacity expansion locking label can be added on the identification of the target server, so that the control system of the target user does not feel the target server. The control system of the target user can determine that the target server is not deployed to the target edge cluster based on the capacity expansion locking tag, but is not opened for the target user to use.

In some embodiments, the target server may be further marked on the CMDB, where the marked tag is used to characterize the ownership of the target server, so that the operation and maintenance system in the central service node may use the operation and maintenance policy adapted by the owner to the target server to perform operation and maintenance on the target server.

In other embodiments, for information security, at least one sensitive information detection may also be performed on the target server after the cloud service is deployed on the target server and before the transport instruction is sent to the logistics transport party; and deleting the detected sensitive information from the target server.

Optionally, detecting the sensitive information of the target server at least once according to a preset sensitive information list; and determining the information in the sensitive information list on the target server as sensitive information. Further, the detected sensitive information may be deleted from the target server.

In the present embodiment, the number and order of detection of sensitive information to the target server are not limited. Sensitive information detection may occur before or after any stage or operation until no sensitive information is detected on the target server. Preferably, the target server may be subjected to sensitive information detection before the target server is powered off, until the target server is not provided with sensitive information, and then the target server is powered off.

In some embodiments of the present application, after the cloud service is deployed on the target server and before the transport instruction is sent to the logistics transport party, the network connection and DNS resolution configuration of the target server may also be modified; and modifying the virtual IP address of the target server into the virtual IP address of Any connection channel (Any Tunnel) corresponding to the available area of the target edge cluster, so that the target server can be communicated with the central cloud after being deployed to the target edge cluster. Wherein the virtual IP of the AnyTunnel is a public access VIP provided in the VPC network, which has access to all VPCs.

Optionally, after the virtual IP address of the target server is modified to the virtual IP address of Any connection channel (Any Tunnel) corresponding to the available area of the target edge cluster, the sensitive information detection may be performed on the target server again until no sensitive information exists on the target server. Thereafter, a shutdown process may be performed on the target server.

Alternatively, the target server may be remotely controlled to shut down. In some embodiments, cloud computing services and block storage services of the target server may be remotely controlled to shut down; and remotely controlling the target server to be powered off after the cloud computing service and the block storage service of the target server are powered off. An operation and maintenance person of an operation and maintenance party of the target server can conduct network disconnection and power failure on the target server in a machine room of the operation and maintenance party.

And then, a transport instruction can be sent to the logistics transport party to instruct the logistics transport party to transport the target server to the target edge cluster corresponding to the target user. 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; and performs physical network connection and power supply to the target server.

Further, after the target server is deployed in the target edge cluster, network configuration and network debugging can be performed 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 communicated with the central cloud. For the embodiment of the whole cabinet expansion, 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.

In some embodiments, for a computing node whose target server is in the target mode, the network mode of the target server may also be switched to the target mode for the data packets of the target server to be transmitted by the security gateway to the central service node through the private network.

In some embodiments, after the target server is deployed on the target edge cluster, the target server may also be configured for ring monitoring, and the ring monitoring configuration information is synchronized to the operation and maintenance system in the central service node. The dynamic ring monitoring is to monitor the target server and the environment variable in the target server in a centralized way by the pointer.

In some embodiments of the present application, after the target server is deployed on the target edge cluster, the network quality of the target server on the target edge cluster may also be detected, and the management capability of the central service node on the target server may be verified.

When the network quality of the target server in the target edge cluster is detected, the target server can be controlled to send detection data packets to other devices; acquiring network quality parameters of the target server based on the detection data packet; and then, according to the network quality parameters of the target server, determining the network quality of the target server in the target edge cluster.

In some embodiments, cloud-edge collaboration may be used to verify the management capabilities of the central service node to the target server. In particular, it may be validated for lifecycle management capabilities of the cloud computing service of the target server. For example, cloud computing services may be created, initiated, and destroyed on a target server, enabling verification of lifecycle management capabilities of the cloud computing services of the target server. And/or, the operation and maintenance system in the central service node can also verify the operation and maintenance capability of the target server, etc.

In the actual use process, the target user can also check and accept the target server. The acceptance process of the target user is not in the protection scope of the application, so that redundant description is not made.

After the operation is completed and the various performance tests reach the standard, the blacklist label of the operation and maintenance system corresponding to the identification of the target server can be released. In this way, the operation and maintenance system of the target server can identify the target server. Furthermore, the expansion locking label can be added on the identification of the target server, so that the control system of the target user can sense the target server and open the target server for the user.

The embodiment of the application provides a full-link flow for edge node capacity expansion, integrates hardware installation, software deployment, network erection, safety compliance, logistics relocation, cloud edge collaborative verification and the like, and realizes the integrated capacity expansion of the edge cluster nodes. In addition, the capacity expansion method of the edge node provided by the embodiment of the application can be compatible with the capacity expansion of the whole cabinet and the capacity expansion of the non-whole cabinet.

It should be noted that, the execution subjects of each step of the method provided in the above embodiment may be the same device, or the method may also be executed by different devices. For example, the execution subject of steps 301 and 302 may be device a; for another example, the execution body of step 301 may be device a, and the execution body of step 302 may be device B; etc.

In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations appearing in a specific order are included, but it should be clearly understood that the operations may be performed out of the order in which they appear herein or performed in parallel, the sequence numbers of the operations such as 301, 302, etc. are merely used to distinguish between the various operations, and the sequence numbers themselves do not represent any order of execution. In addition, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel.

Accordingly, embodiments of the present application also provide a computer-readable storage medium storing computer instructions that, when executed by one or more processors, cause the one or more processors to perform the steps in the above-described method for expanding an edge resource.

Fig. 4 is a schematic structural diagram of a computing device according to an embodiment of the present application. The computing device provided by the embodiment may be implemented as a central service node in an edge cloud system. The central service node is deployed in the central cloud. As shown in fig. 4, the computing device includes: a memory 40a, a processor 40b, and a communication component 40c; wherein the memory 40a is used for storing a computer program.

Processor 40b is coupled to memory 40a and communication component 40c for executing computer programs for: acquiring an edge resource capacity expansion request provided by a target user; based on the edge resource expansion request, sending a server production request to the server producer via the communication component 40c to request the server producer to produce the target server; installing an operating system on a target server and deploying cloud services; and sending a transport instruction to the logistics transport party through the communication component 40c to instruct the logistics transport party to transport the target server to the target edge cluster corresponding to the target user, so that the target server is deployed on the target edge cluster.

Optionally, the processor 40b is specifically configured to, when providing the server production request to the server producer based on the edge resource capacity expansion request: acquiring a resource capacity expansion type and a resource quantity to be expanded from an edge resource capacity expansion request; under the condition that the resource capacity expansion type is the capacity expansion type of the whole cabinet, constructing infrastructure information of the cabinet to be expanded; providing a server production request to a server producer through a communication component 40c based on the infrastructure information and the amount of resources to be expanded to request the server producer to produce a cabinet to be expanded and a target server; the target server is to be deployed in the cabinet to be expanded; and, in case the resource capacity expansion type is a non-whole cabinet capacity expansion type, providing a server production request to a server producer through the communication component 40c based on the amount of the resource to be expanded to request the server producer to produce a target server; the target server is to be deployed in an existing cabinet of the target edge cluster.

Further, the processor 40b is specifically configured to, when constructing the infrastructure information of the enclosure to be expanded: determining the position of the cabinet to be expanded in the machine room of the operation and maintenance party according to the position information of the existing cabinet of the target edge cluster in the machine room of the operation and maintenance party of the cabinet to be expanded; determining a network topology structure of the cabinet to be expanded according to the network topology structure of the existing cabinet of the target edge cluster in the machine room of the operation and maintenance party; acquiring the network demand of a target user from the edge resource capacity expansion request; according to the network requirements of the target user and the network resources provided by the operation and maintenance party, determining the network resource information of the cabinet to be expanded; and taking the position of the cabinet to be expanded in the machine room of the operation and maintenance party, the network topology structure 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.

In some embodiments, the processor 40b is further configured to: under the condition that the resource capacity expansion type is the capacity expansion type of the whole cabinet, constructing a network topology structure of the target server in a physical network of an operation and maintenance party of the target server according to the infrastructure information; applying for a network address for a target server in a network segment of an operation and maintenance party; generating network configuration information of the target server according to the equipment configuration specification, the network topology structure and the network address; after the cabinet to be expanded is accessed to the physical network of the operation and maintenance party, the network configuration information of the target server is provided to the target server through the communication component 40 c.

Optionally, the processor 40b is further configured to: before installing an operating system on a target server and deploying cloud service, performing performance detection on the target server; and executing the operation of installing an operating system on the target server and deploying the cloud service under the condition that the performance of the target server is detected to reach the standard;

further, the processor 40b is specifically configured to, when performing performance detection on the target server: detecting the network quality of a target server; and/or, performing hardware environment detection on the target server; and/or performing stress test on the target server.

In some embodiments, the processor 40b is specifically configured to, when deploying the cloud service on the target server: under the condition that the capacity expansion type is the capacity expansion type of the whole cabinet, deploying a block storage service on a target server in the cabinet to be expanded; acquiring an image file of a cloud computing service; according to the mirror image file of the cloud computing service, deploying the cloud computing service on a target server in the cabinet to be expanded, and carrying out network configuration on the cloud computing service; deploying an infrastructure operation and maintenance plug-in on a target server; or under the condition that the capacity expansion type is the non-whole cabinet capacity expansion type, acquiring a mirror image file of the cloud computing service; according to the mirror image file of the cloud computing service, deploying the cloud computing service on a target server in the cabinet to be expanded, and carrying out network configuration on the cloud computing service; an infrastructure operation and maintenance plug-in is deployed on the target server.

Further, the processor 40b is configured to: and calling an infrastructure operation and maintenance plug-in to configure a security gateway for a target server in the cabinet to be expanded under the condition that the capacity expansion type is the capacity expansion type of the whole cabinet.

Optionally, the processor 40b is further configured to: and under the condition that the capacity expansion type is the capacity expansion type of the whole cabinet, after the cloud service is deployed on the target server and before a transport instruction is sent to a logistics transport party, performing secondary detection on the network quality of the target server, and acquiring a network quality detection result of the secondary detection.

Optionally, the processor 40b is further configured to: after the cloud service is deployed on the target server and before a transport instruction is sent to the logistics transport party, the identification of the target server is set as a blacklist label of the operation and maintenance system so that the operation and maintenance system in the central service node does not identify the target server; and adding a capacity expansion locking label on the identification of the target server so that a control system of the target user does not feel the target server.

Optionally, the processor 40b is further configured to: after the target server is deployed on the target edge cluster, removing a blacklist tag of the operation and maintenance system corresponding to the identification of the target server so as to enable the operation and maintenance system to identify the target server; and adding a capacity expansion locking label on the identifier of the deleted target server so that a control system of the target user perceives the target server.

In other embodiments, the processor 40b is further configured to: after the cloud service is deployed on the target server and before a transport instruction is sent to the target server by a logistics transport party, detecting sensitive information of the target server at least once; and deleting the detected sensitive information from the target server.

Optionally, the processor 40b is further configured to: after deploying the cloud service on the target server and before sending the transport instruction to the logistics transport party, modifying the network connection and domain name system resolution configuration of the target server; and modifying the virtual IP address of the target server into the virtual IP address of any connection channel corresponding to the available area of the target edge cluster.

In still other embodiments, the processor 40b is further configured to: after the target server is deployed on the target edge cluster, carrying out network configuration and network debugging on the target server and a cabinet where the target server is located until the target server and the cabinet where the target server is located are communicated with the central cloud; switching the network mode of the target server into a target mode so that the data packet of the target server is transmitted to the central service node through the special network by the security gateway; performing dynamic ring monitoring configuration on the target server, and synchronizing dynamic ring monitoring configuration information to an operation and maintenance system in the central service node; detecting the network quality of the target server in the target edge cluster; and verifying the management capability of the central service node to the target server by adopting a cloud edge cooperative mode.

Optionally, when the processor 40b detects the network quality of the target server in the target edge cluster in the cloud edge cooperative manner, the method is specifically used for: verifying the life cycle management capability of the center service node to the cloud computing service of the target server in a cloud edge cooperative mode; and/or verifying the operation and maintenance capability of the operation and maintenance system in the central service node to the target server by adopting a cloud edge cooperative mode.

In some alternative implementations, as shown in fig. 4, the computing device may further include: power supply assembly 40d, etc. In some embodiments, the computing device may be implemented as a terminal device such as a computer, a cell phone, a workstation, or the like. Accordingly, the computing device may further include: optional components such as a display component 40e and an audio component 40 f. Only a portion of the components are schematically shown in fig. 4, which does not mean that the computing device must contain all of the components shown in fig. 4, nor that the computing device can only include the components shown in fig. 4.

In this embodiment, a central service node in the central cloud may request a server producer to produce a target server based on an edge resource capacity expansion request of a target user; installing an operating system on a target server and deploying cloud services; and then, the logistics transport party can be instructed to transport the target server to the target edge cluster corresponding to the target user so as to deploy the target server to the target edge cluster, thereby realizing the capacity expansion of the edge nodes in the target edge cluster. According to the embodiment, the capacity expansion all-link flow integrating the production, the transportation and the edge cluster deployment of the server into a whole is realized, and the integration of the capacity expansion of the edge nodes and the capacity expansion of the edge nodes from end to end are realized.

In an embodiment of the present application, the memory is used to store a computer program and may be configured to store various other data to support operations on the device on which it resides. Wherein the processor may execute a computer program stored in the memory to implement the corresponding control logic. The Memory may be implemented by any type or combination of volatile or non-volatile Memory devices, such as Static Random-Access Memory (SRAM), electrically erasable programmable Read-Only Memory (Electrically Erasable Programmable Read Only Memory, EEPROM), erasable programmable Read-Only Memory (Electrical Programmable Read Only Memory, EPROM), programmable Read-Only Memory (Programmable Read Only Memory, PROM), read Only Memory (ROM), magnetic Memory, flash Memory, magnetic or optical disk.

In an embodiment of the present application, the processor may be any hardware processing device that may execute the above-described method logic. Alternatively, the processor may be a central processing unit (Central Processing Unit, CPU), a graphics processor (Graphics Processing Unit, GPU) or a micro control unit (Microcontroller Unit, MCU); programmable devices such as Field programmable gate arrays (Field-Programmable Gate Array, FPGA), programmable array logic devices (Programmable Array Logic, PAL), general array logic devices (General Array Logic, GAL), complex programmable logic devices (Complex Programmable Logic Device, CPLD), and the like; or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC) chip; or an advanced reduced instruction set (Reduced Instruction Set Compute, RISC) processor (Advanced RISC Machines, ARM) or System on Chip (SoC), etc., but is not limited thereto.

In an embodiment of the 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 may access a wireless network based on a communication standard, such as wireless fidelity (Wireless Fidelity, wiFi), 2G or 3G,4G,5G or a combination thereof. In one exemplary embodiment, the communication component receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component may also be implemented based on near field communication (Near Field Communication, NFC) technology, radio frequency identification (Radio Frequency Identification, RFID) technology, infrared data association (Infrared Data Association, irDA) technology, ultra Wide Band (UWB) technology, bluetooth (BT) technology, or other technologies.

In an embodiment of the present application, the display assembly may include a liquid crystal display (Liquid Crystal Display, LCD) and a Touch Panel (TP). If the display assembly includes a touch panel, the display assembly 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, swipes, and gestures on the touch panel. The touch sensor may sense not only the boundary of a touch or sliding action, but also the duration and pressure associated with the touch or sliding operation.

In an embodiment of the application, the power supply assembly is configured to provide power to the various components of the device in which it is located. The power components may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the devices in which the power components are located.

In embodiments of the application, the audio component may be configured to output and/or input audio signals. For example, the audio component includes a Microphone (MIC) configured to receive external audio signals when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may be further stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals. For example, for a device with language interaction functionality, voice interaction with a user, etc., may be accomplished through an audio component.

It should be noted that, the descriptions of "first" and "second" herein are used to distinguish different messages, devices, modules, etc., and do not represent a sequence, and are not limited to the "first" and the "second" being different types.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, CD-ROM (Compact Disc Read-Only Memory), optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (or systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (e.g., CPUs, etc.), input/output interfaces, network interfaces, and memory.

The Memory may include volatile Memory, random-Access Memory (RAM), and/or nonvolatile Memory in a computer-readable medium, such as Read Only Memory (ROM) or Flash Memory (Flash RAM). Memory is an example of computer-readable media.

The storage medium of the computer is a readable storage medium, which may also be referred to as a readable medium. Readable storage media, including both permanent and non-permanent, removable and non-removable media, may be implemented in any method or technology for information storage. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase-Change Memory (PRAM), static Random-Access Memory (SRAM), dynamic Random-Access Memory (Dynamic Random Access Memory, DRAM), other types of Random-Access Memory (RAM), read-only Memory (ROM), electrically erasable programmable read-only Memory (Electrically Erasable Programmable Read Only Memory, EEPROM), flash Memory or other Memory technology, read-only compact disc read-only Memory (CD-ROM), digital versatile discs (Digital Video Disc, DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by the computing device. Computer-readable Media, as defined herein, does not include Transitory computer-readable Media (transmission Media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.

Claims

1. The capacity expansion method of the edge resource is characterized by being suitable for a central service node in a central cloud; the method comprises the following steps:

2. The method of claim 1, wherein providing the server production request to the server producer based on the edge resource expansion request comprises:

acquiring a resource capacity expansion type and a resource quantity to be expanded from the edge resource capacity expansion request;

under the condition that the resource capacity expansion type is the capacity expansion type of the whole cabinet, constructing infrastructure information of the cabinet to be expanded; providing a server production request to a server producer based on the infrastructure information and the amount of resources to be expanded, so as 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;

Providing a server production request to a server producer based on the resource amount to be expanded under the condition that the resource expansion type is a non-whole cabinet expansion type so as 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.

3. The method of claim 2, wherein the constructing infrastructure information of the enclosure to be expanded comprises:

determining the position of the cabinet to be expanded in the machine room of the operation and maintenance party of the center cloud according to the position information of the existing cabinet of the target edge cluster in the machine room of the center cloud;

determining a network topology structure of the cabinet to be expanded according to the network topology structure of the existing cabinet of the target edge cluster in the machine room of the operation and maintenance party;

acquiring the network demand of the target user from the edge resource capacity expansion request; according to the network requirements of the target user and the network resources provided by the operation and maintenance party, determining the network resource information of the cabinet to be expanded;

and taking the position of the cabinet to be expanded in the machine room of the operation and maintenance party, the network topology structure 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.

4. The method according to claim 2, wherein in case the resource expansion type is a complete cabinet expansion type, the method further comprises:

constructing a network topology structure of the target server in a physical network of an operation and maintenance party of the target server according to the infrastructure information;

applying for a network address for the target server in the network segment of the operation and maintenance party;

generating network configuration information of the target server according to the equipment configuration specification, the network topology structure and the network address;

and after the cabinet to be expanded is accessed to the physical network of the operation and maintenance party, providing the network configuration information of the target server to the target server.

5. The method of any of claims 1-4, further comprising, prior to installing an operating system and deploying cloud services on the target server:

performing performance detection on the target server;

executing the operation of installing an operating system on the target server and deploying cloud services under the condition that the performance of the target server is detected to reach the standard;

wherein, the performance detection for the target server includes:

Detecting the network quality of the target server; and/or, performing hardware environment detection on the target server; and/or performing a stress test on the target server.

6. The method of claim 2, wherein deploying a cloud service on the target server comprises:

under the condition that the capacity expansion type is the capacity expansion type of the whole cabinet, deploying a block storage service on a target server in the cabinet to be expanded; acquiring an image file of a cloud computing service; according to the mirror image file of the cloud computing service, deploying the cloud computing service on a target server in the cabinet to be expanded, and carrying out network configuration on the cloud computing service; deploying an infrastructure operation and maintenance plug-in on the target server;

or,

acquiring a mirror image file of the cloud computing service under the condition that the capacity expansion type is a non-whole cabinet capacity expansion type; according to the mirror image file of the cloud computing service, deploying the cloud computing service on a target server in the cabinet to be expanded, and carrying out network configuration on the cloud computing service; an infrastructure operation and maintenance plug-in is deployed on the target server.

7. The method of claim 6, wherein in the case where the capacity expansion type is a complete cabinet capacity expansion type, the method further comprises:

And calling the infrastructure operation and maintenance plug-in to configure a security gateway for the target server in the cabinet to be expanded.

8. The method of claim 2, wherein after deploying the cloud service on the target server and before sending the transport instructions to the logistics transport party, the method further comprises:

under the condition that the capacity expansion type is the capacity expansion type of the whole cabinet, performing secondary detection on the network quality of the target server, and acquiring a network quality detection result of the secondary detection;

and/or the number of the groups of groups,

detecting sensitive information of the target server at least once; and deleting the detected sensitive information from the target server.

9. The method of any of claims 1-4 and 6-8, wherein after deploying a cloud service on the target server and before sending a transport instruction to a logistics transport party, the method further comprises:

setting the identification of the target server as a blacklist tag of an operation and maintenance system in the central service node so that the operation and maintenance system does not identify the target server;

adding a capacity expansion locking label on the identification of the target server so that a control system of the target user does not sense the target server;

And after the target server is deployed to the target edge cluster, the method further comprises:

releasing a blacklist tag of an operation and maintenance system corresponding to the identification of the target server so as to enable the operation and maintenance system to identify the target server;

and deleting the identifier of the target server and adding a capacity expansion locking label to enable a control system of the target user to perceive the target server.

10. The method of any of claims 1-4 and 6-8, wherein after deploying a cloud service on the target server and before sending a transport instruction to a logistics transport party, the method further comprises:

modifying the network connection and domain name system resolution configuration of the target server;

and modifying the virtual IP address of the target server into the virtual IP address of any connecting channel corresponding to the available area of the target edge cluster.

11. The method of any of claims 1-4 and 6-8, wherein after the target server is deployed to the target edge cluster, the method further comprises:

performing network configuration and network debugging on the target server and a cabinet where the target server is located until the target server and the cabinet where the target server is located are communicated with the central cloud;

Switching the network mode of the target server into a target mode so that the data packet of the target server is transmitted to the central service node through a private network by a full gateway; the target mode is a mode that the target server is managed and maintained by the central cloud;

performing dynamic ring monitoring configuration on the target server, and synchronizing dynamic ring monitoring configuration information to an operation and maintenance system in the central service node;

detecting the network quality of the target server in the target edge cluster; and verifying the management capability of the central service node to the target server by adopting a cloud edge cooperative mode.

12. An edge cloud system, comprising: a central cloud, and at least one edge cluster connected with the central cloud network; the center cloud includes: a central service node; the edge cluster includes: the cabinet and the edge nodes deployed on the cabinet;

the central service node being adapted to perform the steps of the method of any of claims 1-11.

13. A computing device, comprising: a memory, a processor, and a communication component; wherein the memory is used for storing a computer program;

The processor is coupled to the memory and the communication component for executing the computer program for performing the steps in the method of any of claims 1-11.

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