Node management method, device, apparatus, storage medium and system

Abstract

The application provides a node management method, device, equipment, storage medium and system. The method comprises the following steps: receiving node life cycle management information; and performing life cycle management on a node based on the node life cycle management information, wherein the node life cycle management comprises one or more of the following: node creation, node scaling and node release.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication network, in particular to a node management method, device, equipment, storage medium and system. BACKGROUND

[0002] In existing open source technologies, such as Kubernetes (K8s), a cluster node (Cluster node) is needed to run a container integration environment. The node is a worker node in the Kubernetes cluster. The node node runs services to run pods and communicate with the master, etc. In the Network Functions Virtualization (NFV) system, the life cycle management of the nodes in the cluster is not involved.

[0003] SUMMARY

[0004] The present application provides a node management method, device, equipment, storage medium and system.

[0005] In a first aspect, the embodiments of the present application provide a node management method, comprising:

[0006] receiving node life cycle management information;

[0007] based on the node life cycle management information, performing life cycle management on the node, wherein the node life cycle management includes one or more of the following: node creation, node scaling and node release.

[0008] In a second aspect, the embodiments of the present application provide a node management device, comprising:

[0009] a receiving module configured to receive node life cycle management information;

[0010] a management module configured to perform life cycle management on the node based on the node life cycle management information, wherein the node life cycle management includes one or more of the following: node creation, node scaling and node release.

[0011] In a third aspect, the embodiments of the present application provide a cluster manager, characterized in that it comprises:

[0012] one or more processors;

[0013] a memory for storing one or more programs;

[0014] When the one or more programs are executed by the one or more processors, the one or more processors implement any one of the methods in the embodiments of the present application.

[0015] In a fourth aspect, an embodiment of the present application provides a network function virtualization system, and the system comprises: an operation support system (OSS), a network function virtualization orchestrator (NFVO), a virtualization infrastructure manager (VIM) and a cluster manager (CNM);

[0016] The NFVO or the OSS sends node lifecycle management information to the CNM;

[0017] The CNM generates a node lifecycle management request based on the node lifecycle management information and sends the lifecycle management request to the VIM,

[0018] The VIM performs a lifecycle management operation on the node based on the node lifecycle management request.

[0019] In a fifth aspect, an embodiment of the present application provides a storage medium, and the storage medium stores a computer program, and the computer program is executed by a processor to implement any one of the methods in the embodiments of the present application.

[0020] More details about the above embodiments and other aspects of the present application and implementation manners thereof are provided in the description of drawings, specific embodiments and claims. DETAILED DESCRIPTION

[0021] Figure 1 is a schematic diagram of an ETSI-defined NFV system architecture;

[0022] Figure 2 is a flowchart of a node management method provided by an embodiment of the present application;

[0023] Figure 3 is a structural schematic diagram of a node management apparatus provided by an embodiment of the present application;

[0024] Figure 4 is a structural schematic diagram of a network function virtualization system provided by an embodiment of the present application;

[0025] Figure 5 is a structural schematic diagram of an NFV system provided by an embodiment of the present application and having a cluster management function;

[0026] Figure 6 is a flowchart of a node creation method provided by an embodiment of the present application;

[0027] Figure 7 is a flowchart of a node scaling-in method provided by an embodiment of the present application;

[0028] Figure 8 is a flowchart of a node release method provided by an embodiment of the present application;

[0029] Figure 9is a flowchart of a node state monitoring and reporting method provided by an embodiment of the present application.

[0030] Figure 10 is a structural schematic diagram of a cluster manager provided by an embodiment of the present application. DETAILED DESCRIPTION

[0031] To make the objectives, technical solutions and advantages of the present application clearer, the embodiments of the present application will be described in detail below with reference to the drawings. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other as long as there is no conflict.

[0032] The steps shown in the flowchart of the drawings can be executed in a computer system such as a set of computer-executable instructions. Moreover, although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that here.

[0033] In existing open source technologies such as Kubernetes, a cluster node (Cluster node) is needed to run a container integration environment. The node is a worker node in the kubernetes cluster, which can be a virtual machine or a physical machine. Some services on the node are used to run pods and communicate with the master, etc. The services on a node include a docker runtime environment, etc. Kubnates needs to download container images on the node to establish container objects such as POD, Service, Deployment, etc. Service providers or operators can load application programs on the container objects to implement network system services in the container environment.

[0034] Network Function Virtualization (Network Functions Virtualization, NFV) is a software processing technology for carrying other functions by using general hardware and virtualization technology, aiming to reduce the cost of expensive network devices. NFV decouples software and hardware and abstracts functions, so that network device functions are no longer dependent on special hardware, resources can be fully and flexibly shared, and new services can be quickly developed and deployed, and automatic deployment, elastic scaling, fault isolation and self-healing based on actual business needs can be realized.

[0035] Figure 1 is a schematic diagram of the ETSI-defined NFV system architecture, such as Figure 1As shown, the NFV system architecture defined by the European Telecommunications Standards Institute (ETSI) mainly includes: an operation-support system and a management support platform (OSS / BSS), a virtualized network function (VNF), a network function virtualization infrastructure (NFVI), and a network function virtualization management and orchestration system (VNF-Management and Orchestration, NFV-MANO). Among them, the NFVI is mainly responsible for fully virtualizing hardware resources such as computing, storage, and network, and mapping them into virtual resources; the VNF is to use software to realize various traditional physical network functions, and the VNF runs on the NFVI and uses virtual resources that are virtualized by the NFVI. The NFV-MANO is responsible for managing and orchestrating the relationship between the VNF and the NFVI, and the connection relationship between the VNF and / or other physical network functions (PNF).

[0036] The NFV-MANO includes: a virtualized infrastructure manager (VIM), a virtual network function manager (VNFM), and a network function virtualization orchestrator (NFVO). The VIM is responsible for controlling and managing virtualized resources. In addition, the VIM can also include a PIM (Physical Infrastructure Manager) function, which is responsible for managing bare-metal resources, such as physical servers; the VNFM is responsible for the life cycle management of the VNF; and the NFVO is responsible for the orchestration and management of the virtual infrastructure, and the life cycle management of the network service (NS).

[0037] Figure 2is a flow chart of a node management method provided by the embodiment of the application. The node management method provided by the embodiment of the application is mainly applicable to the case of managing the life cycle of a node in an NFV system. The node management method is executed by a node management device, and the node management device can be realized by a hardware and / or software method.

[0038] As shown in Figure 2 The node management method provided by the embodiment of the application mainly includes steps S11 and S12.

[0039] S11, receiving node life cycle management information;

[0040] S12, managing the life cycle of the node based on the node life cycle management information, wherein the node life cycle management includes one or more of the following: node creation, node scaling and node release.

[0041] In an exemplary embodiment, the node life cycle management information is sent from one of the following nodes:

[0042] an operation support system (OSS);

[0043] a network function virtualization orchestrator (NFVO);

[0044] a virtual network function manager (VNFM), wherein the VNFM forwards the node life cycle management information sent by the NFVO.

[0045] In an exemplary embodiment, the managing the life cycle of the node based on the node life cycle management information includes: generating a node life cycle management request based on the node life cycle management information; sending the node life cycle management request to a virtual infrastructure manager (VIM), wherein the node life cycle management request is used to instruct the VIM to perform a node resource management operation on the node, and the VIM generates operation result information after performing the node resource management operation; receiving the operation result information fed back by the VIM and forwarding the operation result information to the OSS or the NFVO.

[0046] In an example embodiment, in the case that the node lifecycle management request is a node creation request, performing lifecycle management of creating a node based on the lifecycle management request comprises: sending a node creation request to a VIM of a region to which the node belongs, wherein the node creation request carries a node resource information model; the node resource information model is used to instruct the VIM to create a corresponding node; the node resource information model comprises one or more of the following: node scale, node identifier, node resource; the node resource information model is generated based on node creation information, wherein the node creation information comprises one or more of the following: node type, node scale, node resource, node deployment; receiving node creation completion information fed back by the VIM, wherein the node creation completion information carries the number of created nodes and the resources allocated to the nodes.

[0047] In an example embodiment, after receiving the node creation completion information fed back by the VIM, the method further comprises: adding the created nodes to a cluster; and updating cluster information, wherein the cluster information comprises a cluster identifier and node information of all nodes in the cluster.

[0048] In an example embodiment, after updating the cluster information, the method further comprises: sending node creation success information to an OSS or an NFVO, wherein the node creation success information comprises a cluster identifier and node information of all nodes in each cluster.

[0049] In an example embodiment, the VIM of the region to which the node belongs is determined based on the node deployment.

[0050] In an example embodiment, in the case that the lifecycle management request is a node scaling request, performing lifecycle management of scaling a node based on the lifecycle management request comprises: sending a node scaling request to a VIM of a region to which the node belongs, wherein the node scaling request carries a node scaling information model, the node scaling information model comprises a node scaling scale and a node resource requirement, the node scaling request is used to instruct the VIM to perform a node scaling operation, and the VIM generates node scaling result information after the node scaling operation is completed; and receiving the node scaling result information fed back by the VIM.

[0051] In an example embodiment, before sending the node scaling request to the VIM of the region to which the node belongs, the method further comprises: determining whether to initiate the node scaling request according to a node scaling strategy.

[0052] In an exemplary embodiment, the determining whether to initiate the node shrink request according to the node shrink strategy comprises: in the case of insufficient node resources or insufficient node scale, initiating a node pop-out request, wherein the node pop-out comprises increasing node resources or increasing node scale; in the case of idle node resources being greater than required node resources, initiating a node shrink-in request, wherein the node shrink-in comprises decreasing node resources or decreasing node scale.

[0053] In an exemplary embodiment, before the sending of the node shrink request to the VIM, the method further comprises: sending a query request to the VIM of the region to which the node belongs; the query request is used to instruct the VIM to query whether idle resources meet node resource requirements; in the case of receiving the VIM feedback that idle resources meet node resource requirements, performing the operation of sending the node shrink request to the VIM; in the case of receiving the VIM feedback that idle resources do not meet node resource requirements, updating node shrink scale and node resource requirements.

[0054] In an exemplary embodiment, after receiving the node shrink result information fed back by the VIM, the method further comprises: in the case of the node pop-out result information being the creation of a new node, adding the newly created node to the cluster; in the case of the node pop-out result information being the increase of resources of an existing node, updating node information of the existing node in the cluster; in the case of the node pop-out result information being the release of an existing node, deleting the existing node in the cluster; in the case of the node pop-out result information being the decrease of resources of an existing node, updating node information of the existing node in the cluster.

[0055] In an exemplary embodiment, in the case of the lifecycle management request being a node release request, performing lifecycle management of the node based on the lifecycle management request comprises: sending a node release request to the VIM of the region to which the node belongs, wherein the node release request carries a node identifier; the node release request is used to instruct the VIM to release the node and resources occupied by the node, and the VIM generates node release result information after the node release operation is completed; receiving the node release result information fed back by the VIM, wherein the node release result information carries a released node identifier; deleting the released node in the cluster.

[0056] In an exemplary embodiment, the node release request is generated in one of the following ways:

[0057] In the case of idle nodes being greater than required nodes;

[0058] In the case of there being abnormal nodes in the cluster.

[0059] In an exemplary embodiment, the method further comprises:

[0060] sending a subscription request to the VIM, the subscription request being used to instruct the VIM to report node state information within a set time; and in a case where the node state information fed back by the VIM is received, sending the node state information to an OSS or an NFVO, the node state information including a cluster identifier of a cluster to which the node belongs, a node identifier, and node resource information.

[0061] In an exemplary embodiment, the method comprises sending a node state query request to the VIM, the node state query request being used to instruct the VIM to report node state information.

[0062] In an exemplary embodiment, the method comprises receiving node exception information, wherein the node exception information is fed back by the VIM in a case where there is an abnormal node in a cluster; sending a node creation request to the VIM, the node creation request carrying a node resource information model; the node resource in the node resource information model is the same as the node resource in a node resource information model of the abnormal node; and sending node exception state information to an OSS or an NFVO, the node exception state information carrying information of a newly created node.

[0063] Figure 3 FIG. 1 is a structural schematic diagram of a node management apparatus provided by an embodiment of the present application. The node management apparatus provided by the embodiment of the present application is mainly applicable to a case where the life cycle of a node is managed in an NFV system, and can be implemented by a hardware and / or software method.

[0064] As shown in FIG. 1, the node management apparatus provided by the embodiment of the present application mainly comprises a receiving module 21 and a management module 22. Figure 3 The receiving module 21 is configured to receive node life cycle management information.

[0065] The management module 22 is configured to perform life cycle management on a node based on the node life cycle management information, wherein the node life cycle management comprises one or more of the following: node creation, node scaling, and node release.

[0066] In an exemplary embodiment, the node life cycle management information is sent by one of the following nodes:

[0067] a business operation support system (OSS);

[0068] a network virtualization function orchestrator (NFVO);

[0069] a network function virtualization orchestrator (NFVO);

[0070] A virtual network function manager VNFM, wherein the VNFM forwards node lifecycle management information sent by the NFVO.

[0071] In one example embodiment, the management module 22 is configured to generate a node lifecycle management request based on the node lifecycle management information; send the node lifecycle management request to a virtualization infrastructure manager VIM, the node lifecycle management request being used to instruct the VIM to perform a node resource management operation on the node, the VIM generating operation result information after performing the node resource management operation; receive the operation result information fed back by the VIM and forward the operation result information to the OSS or the NFVO.

[0072] In one example embodiment, when the node lifecycle management request is a node creation request, the management module 22 is configured to perform lifecycle management of creating the node based on the node lifecycle management request, and further configured to send a node creation request to the VIM of the region to which the node belongs, wherein the node creation request carries a node resource information model; the node resource information model is used to instruct the VIM to create a corresponding node; the node resource information model comprises one or more of the following: node scale, node identifier, node resource; the node resource information model is generated based on node creation information, wherein the node creation information comprises one or more of the following: node type, node scale, node resource, node deployment; receive node creation completion information fed back by the VIM, wherein the node creation completion information carries the number of created nodes and the resources allocated to the nodes.

[0073] In one example embodiment, after receiving the node creation completion information fed back by the VIM, the management module 22 is configured to add the created nodes to a cluster; update cluster information, the cluster information comprising a cluster identifier and node information of all nodes in the cluster.

[0074] In one example embodiment, after updating the cluster information, the management module 22 is configured to send node creation success information to the OSS or the NFVO, wherein the node creation success information comprises a cluster identifier and node information of all nodes in each cluster.

[0075] In one example embodiment, the VIM of the region to which the node belongs is determined based on the node deployment.

[0076] In an example embodiment, the management module 22 is configured to, in the case that the lifecycle management request is a node scaling-out request, perform lifecycle management of the node based on the lifecycle management request, and further, the management module 22 is configured to send a node scaling-out request to a VIM of a region to which the node belongs, wherein the node scaling-out request carries a node scaling-out information model, the node scaling-out information model includes a node scaling-out scale and a node resource requirement, the node scaling-out request is used to instruct the VIM to perform a node scaling-out operation, and the VIM generates node scaling-out result information after the node scaling-out operation is completed; and the management module 22 is configured to receive the node scaling-out result information fed back by the VIM.

[0077] In an example embodiment, the management module 22 is configured to, before sending the node scaling-out request to the VIM of the region to which the node belongs, determine whether to initiate the node scaling-out request according to a node scaling-out policy.

[0078] In an example embodiment, the management module 22 is configured to, in the case that the node resource is insufficient or the node scale is insufficient, initiate a node scaling-out request, wherein the node scaling-out includes increasing the node resource or increasing the node scale; and in the case that the idle resource of the node is greater than the resource required by a service, initiate a node scaling-in request, wherein the node scaling-in includes reducing the node resource or reducing the node scale.

[0079] In an example embodiment, the management module 22 is configured to, before sending the node scaling-out request to the VIM, send a query request to the VIM of the region to which the node belongs; the query request is used to instruct the VIM to query whether the idle resource meets the node resource requirement; in the case that the idle resource meeting the node resource requirement is received from the VIM, perform the operation of sending the node scaling-out request to the VIM; and in the case that the idle resource not meeting the node resource requirement is received from the VIM, update the node scaling-out scale and the node resource requirement.

[0080] In an example embodiment, the management module 22 is configured to, after receiving the node scaling-out result information fed back by the VIM, in the case that the node scaling-out result information is to create a new node, add the newly created node to a cluster; in the case that the node scaling-out result information is to increase a resource of an existing node, update node information of the existing node in the cluster; in the case that the node scaling-out result information is to release the existing node, delete the existing node in the cluster; and in the case that the node scaling-out result information is to reduce a resource of the existing node, update the node information of the existing node in the cluster.

[0081] In an example embodiment, the management module 22 is configured to, in the case that the lifecycle management request is a node release request, perform lifecycle management of releasing the node based on the lifecycle management request, and further configured to send a node release request to a VIM of a region to which the node belongs, wherein the node release request carries a node identifier; the node release request is used to instruct the VIM to release the node and resources occupied by the node, and the VIM generates node release result information after completion of the node release operation; receive the node release result information fed back by the VIM, wherein the node release result information carries a released node identifier; and delete the released node in the cluster.

[0082] In an example embodiment, the node release request is generated in one of the following ways:

[0083] In the case that the number of idle nodes is greater than the number of required nodes;

[0084] In the case that there is an abnormal node in the cluster.

[0085] In an example embodiment, the management module 22 is configured to send a subscription request to the VIM, wherein the subscription request is used to instruct the VIM to report node state information within a set time; and in the case that the node state information fed back by the VIM is received, send the node state information to an OSS or an NFVO, wherein the node state information includes a cluster identifier of a cluster to which the node belongs, a node identifier, and node resource information.

[0086] In an example embodiment, the management module 22 is configured to send a node state query request to the VIM, wherein the node state query request is used to instruct the VIM to report node state information.

[0087] In an example embodiment, the management module 22 is configured to receive node abnormal information, wherein the node abnormal information is fed back by the VIM in the case that there is an abnormal node in the cluster; send a node creation request to the VIM, wherein the node creation request carries a node resource information model; the node resources in the node resource information model are the same as node resources in a node resource information model of the abnormal node; and send node abnormal state information to an OSS or an NFVO, wherein the node abnormal state information carries information of a newly created node.

[0088] Figure 4 is a structural schematic diagram of a network function virtualization system provided by an embodiment of the present application, as shown in Figure 4 The system includes an operation support system (OSS), a network function virtualization orchestrator (NFVO), a virtualization infrastructure manager (VIM), and a cluster manager (CNM).

[0089] S31, the NFVO or the OSS sends node lifecycle management information to the CNM.

[0090] S32, the CNM generates a node lifecycle management request based on the node lifecycle management information.

[0091] S33, the CNM sends the node lifecycle management request to the VIM.

[0092] S34, the VIM performs a lifecycle management operation on the node based on the node lifecycle management request.

[0093] In an exemplary embodiment, the VIM generates operation result information of the node after performing the management operation on the node, and sends the operation result information of the node to the CNM; the CNM forwards the operation result information of the node to the NFVO or the OSS.

[0094] In an exemplary embodiment, in the case that the lifecycle management request is a node creation request,

[0095] The CNM generates a node resource information model based on the node creation information, wherein the node creation information includes one or more of the following: node type, node scale, node resource, node deployment, and the node resource information model includes one or more of the following: node scale, node identifier, and node resource.

[0096] The CNM sends a node creation request to the VIM of the region to which the node belongs, wherein the node creation request carries the node resource information model.

[0097] The VIM creates a corresponding node based on the node resource information model.

[0098] The CNM receives node creation completion information fed back by the VIM, and adds the node to the cluster, wherein the node creation completion information carries the number of created nodes and the resources allocated to the nodes.

[0099] In an exemplary embodiment, in the case that the lifecycle management request is a node scaling request, the method comprises:

[0100] The CNM sends a node scaling request to the VIM, wherein the node scaling request carries a node scaling information model, and the node scaling information model includes a node scaling scale and a node resource requirement.

[0101] The VIM performs a node scaling operation based on the node scaling request and generates node scaling result information.

[0102] The CNM receives the node shrink result information fed back by the VIM, and updates the cluster information in which the node is located.

[0103] In an exemplary embodiment, the CNM sends a query request to the VIM to which the node belongs to the VIM in the area to which the node belongs.

[0104] The VIM queries whether the idle resources meet the node resource requirements based on the query request, and feeds back the query result to the CNM.

[0105] The CNM sends a node shrink request to the VIM in the case that the idle resources meet the node resource requirements.

[0106] The CNM updates the node shrink scale and the node resource requirements in the case that the idle resources do not meet the node resource requirements.

[0107] In an exemplary embodiment, in the case that the lifecycle management request is a node release request,

[0108] The CNM sends a node release request to the VIM to which the node belongs, wherein the node release request carries the node identifier.

[0109] The VIM releases the node and the resources occupied by the node based on the node release request, and generates node release result information.

[0110] The CNM receives the node release result information fed back by the VIM, wherein the node release result information carries the released node identifier.

[0111] The CNM deletes the released node in the cluster.

[0112] In an exemplary embodiment, the CNM sends a subscription request to the VIM.

[0113] The VIM reports the node state information within a set time based on the subscription request.

[0114] The CNM sends the node state information to the OSS or the NFVO in the case that the node state information fed back by the VIM is received, wherein the node state information comprises the cluster identifier of the cluster to which the node belongs, the node identifier, and the node resource information.

[0115] In an exemplary embodiment, the VIM generates node exception information and feeds back to the CNM in the case that there is an abnormal node in the cluster.

[0116] The CNM receives node exception information, and sends a node creation request to the VIM, the node creation request carrying a node resource information model; the node resources in the node resource information model are the same as the node resources in the node resource information model of the exception node;

[0117] The VIM creates a new node based on the node creation request to replace the exception node;

[0118] The CNM sends node exception state information to the OSS or NFVO, the node exception state information carrying the information of the newly created node.

[0119] In an application example, a cluster management function CNM (Cluster Node Manager) is newly defined in the present application. The function can be physical or logical. If it is a logical function, it can be embedded into the NFVO, VNFM, VIM, etc. If it is a physical function, it can be set as a separate entity in the network function virtualization system. Figure 5 is a result diagram of the NFV system with the cluster management function provided by the embodiments of the present application.

[0120] As shown in Figure 5 , the cluster management function CNM is used to be responsible for node lifecycle management, including node creation, node scaling, node release, etc.

[0121] The cluster management function CNM is also responsible for updating the cluster nodes, adding the newly created node to a certain cluster, updating the cluster where the node is located when the node is updated, and deleting the node from the corresponding node when the node is released.

[0122] The cluster management function CNM can interact with the OSS / NFVO, and can obtain the creation information, update information and release information of the related node from the OSS / NFVO, and timely report the created, updated and released information of the node to the OSS / NFVO.

[0123] The cluster management function CNM can interact with the VIM. The CNM can discover the VIM in the deployment area according to the node deployment information, and request, update and release the node to the VIM. After the VIM creates successfully, the VIM timely notifies the CNM of the created, updated and released information of the node.

[0124] The cluster management function CNM can interact with the VNFM, and obtain the creation template information of the node from the VNFM.

[0125] When the node is abnormal, the VIM detects the node abnormality and notifies the CNM, and the CNM timely reports the node abnormality information to the OSS / NFVO. The CNM requests the VIM to create a completely replaced node to replace the abnormal node.

[0126] In one application example, a node creation process is provided, Figure 6 is a flowchart of a node creation method provided by the embodiment of the application, as shown in Figure 6 In the embodiment, the OSS / NFVO initiates the Node creation according to the network planning, third-party application or operator demand, and carries the Node creation information model. After receiving the Node creation request, the CNM parses the Node creation information model. The CNM generates the Node resource information model, selects the VIM according to the Node deployment information in the Node resource information model, sends the Node creation request and the Node resource information model to the selected VIM, and requests the VIM to create the Node. After the VIM successfully creates the Node, the VIM returns the Node successful creation information, the CNM adds the created Node to a certain Cluster Node cluster, and notifies the OSS / NFVO that the requested Node is successfully created.

[0127] S101, the operator plans and designs according to the user demand and network planning, creates the Node creation information model including the Node type, Node scale (Node number), Node resource demand, Node deployment and other demands, and plans and designs by using the existing network function description (VNFD / PNFD).

[0128] The Node creation information model can also be planned and designed by using the newly defined Node function description template. The Node function description template is used for the OSS / NFVO to deliver the Node creation information to the CNM.

[0129] S102, the OSS / NFVO directly sends the Node creation information model to the CNM, or forwards the Node creation information model to the CNM through the VNFM; wherein the VNFM forwards the creation information model sent by the NFVO.

[0130] S103, the CNM parses the received Node creation information model, parses the related Node information in the network function description or the Node function description, generates the Node resource information model, and the Node resource information model contains the Node scale, Node identifier, Node required resources (computing, storage, network) and other resource-related information.

[0131] S104, the CNM selects the VIM in the region according to the Node deployment information, initiates a Node creation request to the VIM, and carries the Node resource information model in the Node creation request, including the Node scale, Node identification, and Node required resources (computing, storage, and network). The Node deployment information is sent to the VIM / PIM in the deployment region.

[0132] S105, the VIM creates the corresponding Node according to the Node resource information model, and returns Node creation completion information. The carried information is not limited to the number of created Nodes and the resources (computing resources, storage resources, and network resources) allocated to the Node.

[0133] S106, the CNM adds the created Node to the Cluster cluster and updates the Cluster cluster information. The Cluster Node information includes the Cluster cluster ID, information of all Nodes in the Cluster cluster, such as Node identification, Node resources, and node state.

[0134] S107, the CNM notifies the OSS / NFVO that the Node has been established, carries the Cluster Node creation success information, and includes the Cluster Node ID, and the identification, resources, and deployment location of the created Node to which each Cluster Node cluster belongs.

[0135] In one application example, the embodiment describes a Node scaling process, Figure 7 is a flowchart of a node scaling method provided by the embodiment of the application, as Figure 7 shown. The OSS / NFVO can initiate a Node scaling request, and the CNM can also actively initiate a node scaling request. After receiving the scaling request, the CNM first queries the VIM selected to determine whether the resources meet the Node scaling requirements. If the resources do not meet the scaling requirements, the OSS / NFVO needs to update the Node scaling requirements, or the CNM actively updates the Node scaling requirements, so that the resources of the VIM can meet the scaling requirements.

[0136] The CNM initiates a Node scaling request to the VIM, the VIM performs a Node scaling operation, and there are two kinds of scaling, one is to increase or decrease the resources of the Node, and the other is to add a Node or release the created Node. When the Node scaling is successful, the CNM updates the Cluster Node cluster and reports the scaling result to the OSS / NFVO.

[0137] S201, Node scaling requests can be triggered by OSS / NFVO or initiated proactively by the Cluster Node Management (CNM) function. OSS / NFVO can be triggered based on Node scaling policies, such as when the number of used Nodes exceeds a certain percentage (e.g., 80%) according to preset conditions; or from third-party usage requests for Nodes, such as Node activation requests from Kubernetes (K8S).

[0138] The Cluster Node Management System (CNM) can also proactively initiate node scaling based on the node scaling strategy, such as when existing nodes no longer meet business requirements.

[0139] When Node resources are insufficient or Node size is insufficient, Node popping is initiated, which includes two methods: increasing Node resources and increasing Node size. If the idle resources of a Node are greater than the resources required by the business, Node shrinking is initiated, which includes two methods: reducing Node resources and reducing Node size.

[0140] S202, CNM receives a Node scaling request initiated by OSS / NFVO, or receives a Node scaling request forwarded by VNFM. The request message carries the Cluster identifier and the Node scaling information model, including the Node scaling size and the resources required by the Node.

[0141] If CNM initiates a node scaling operation based on the scaling strategy, it can proactively generate a node scaling information model, including the node scaling scale and the resources required by the node.

[0142] S203, Before CNM initiates the Node scaling operation, CNM queries the VIM in the region based on the Node's deployment information to see if the available resources meet the Node's resource requirements. If the resource requirements are not met, it reports back to OSS / NFVO, and OSS / NFVO updates the Node's scaling scale and scaling resources.

[0143] If the node scaling operation is initiated by CNM, CNM will actively adjust the scaling size and scaling resources of the node.

[0144] S204, CNM initiates a scaling request to VIM, and VIM performs Node scaling operation: When a Node is popped out, VIM generates a new Node based on the Node scaling information and allocates the required resources, or increases the resources of an already created Node; when a Node is shrunk in, it reduces the resources of an already created Node, or releases the corresponding Node, including releasing the resources that were originally allocated.

[0145] S205, VIM notifies CNM of the Node shrinkage result.

[0146] S206, for the Node popping operation, CNM will add the newly popped Node to the Cluster Node cluster. If the popped Node is an existing Node's resource (Node resource increases), the relevant Node information will be updated in the cluster information. For the Node shrinking operation, CNM will delete the successfully shrunken Node from the cluster. If the shrunken Node is an existing Node's resource (Node resource decreases), the relevant Node information will be updated in the cluster information.

[0147] S207, CNM reports the node scaling results to OSS / NFVO. Optionally, it also reports ClusterNode update information, including the Cluster ID and node update information (such as ID and resources).

[0148] In an application example, this embodiment describes the Node release process. Figure 8 This is a flowchart of a node release method provided in an embodiment of this application; as shown below. Figure 8 As shown in this embodiment, OSS / NFVO or CNM can release some nodes to save VIM resources when the number of idle nodes is much greater than the number of required nodes, based on the actual needs of the nodes.

[0149] OSS / NFVO initiates a Node release request, or CNM initiates a Node release request according to the policy. VIM releases the created Node and its occupied resources based on the Node ID. After the Node is successfully released, CNM needs to update the Cluster information, delete the released Node, and notify OSS / NFVO of the release result.

[0150] S301, Node release can be triggered by OSS / NFVO or initiated proactively by CNM. OSS / NFVO can release Nodes based on service deployment needs. For example, if a network slice service used for 5G terminates due to service expiration, the open-source application can notify the release of the Nodes used for that network service.

[0151] The Cluster Node Management System (CNM) can also proactively release nodes based on the node release policy, such as when the number of existing idle nodes far exceeds the business needs, or when a node in a cluster malfunctions.

[0152] S302, CNM receives a Node release request initiated by OSS / NFVO, or a Node release request forwarded by VNFM, and the request message carries the Cluster identifier and Node identifier.

[0153] CNM can also proactively initiate Node release operations based on the Node release policy to release idle or abnormal Nodes in the Cluster.

[0154] S303 and CNM initiate a Node request to the VIM in the region where the Node is located, carrying the Node identifier.

[0155] S304. VIM releases the Node and the resources it occupies, and notifies CNM of the Node release result.

[0156] S305 and CNM update cluster information and delete successfully released nodes from the cluster.

[0157] S306 and CNM report the release results of Nodes to OSS / NFVO. Optionally, they can also report ClusterNode update information, including the Cluster ID and Node update information (such as ID and resources).

[0158] In an application example, this embodiment describes the Node status monitoring and reporting process. Figure 9 This is a flowchart of a Node status monitoring and reporting method provided in an embodiment of this application, such as... Figure 9 As shown in the diagram. In this embodiment, the CNM can subscribe to or dynamically query Node status information from the VIM and send the Node information to OSS / NFVO. When a Node is in an abnormal state, the VIM proactively reports it to the CNM. The CNM searches for a replacement Node in the cluster information. If there is no available replacement Node, the CNM initiates the creation of a Node to replace the abnormal Node from the VIM, and reports the Node abnormality information to OSS / NFVO, while also reporting the information of the created replacement Node to OSS / NFVO.

[0159] S401, CNM dynamically queries Node status from VIM. It can subscribe to VIM for periodic reporting of Node status information, or it can actively query Node status information dynamically. The query message carries the Node's identifier.

[0160] S402, VIM periodically sends Node status information to CNM according to the subscription mechanism, or returns Node status after receiving a query request from CNM.

[0161] S403, CNM reports the Node's status to OSS / NFVO, or forwards it to OSS / NFVO via VNFM. The message carries information such as the Cluster identifier, the Node ID, and the Node's status (idle resources and occupied resources).

[0162] S404 When a Node malfunctions, VIM will report the Node malfunction status information to CNM.

[0163] S405, CNM checks if there is an idle Node in the Cluster that can replace the abnormal Node. If not, it requests VIM to create a new Node with the same resources as the abnormal Node, which is used to replace the abnormal Node.

[0164] S406 and CNM report abnormal Node status information to OSS / NFVO and provide a replacement Node identifier in the notification message.

[0165] Based on the above embodiments, this application also provides a cluster manager. Figure 10 This is a schematic diagram of the structure of a cluster manager provided in an embodiment of this application, such as... Figure 10 As shown, the cluster manager includes a processor 100, a memory 101, an input device 102, and an output device 103; the number of processors 100 in the cluster manager can be one or more. Figure 10 Taking a single processor 100 as an example; the processor 100, memory 101, input device 102, and output device 103 in the cluster manager can be connected via a bus or other means. Figure 10 Taking the example of a connection between China and Israel via a bus.

[0166] The memory 101, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the node management method in the embodiments of this application (e.g., receiving module 21 and management module 22 in the node management device). The processor 100 executes various functional applications and data processing of the cluster manager by running the software programs, instructions, and modules stored in the memory 101, thereby implementing any of the methods provided in the embodiments of this application.

[0167] The memory 101 may primarily include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on terminal usage. Furthermore, the memory 101 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory, or other non-volatile solid-state storage device. In some instances, the memory 101 may further include memory remotely located relative to the processor 100, which can be connected to a cluster manager via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0168] Input device 102 can be used to receive input numeric or character information, and to generate key signal inputs related to user settings and function control of the cluster manager. Output device 103 may include display devices such as a display screen.

[0169] Based on the above embodiments, this application also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform any of the methods provided in the embodiments of this application.

[0170] For example, when implementing the node management method provided in the embodiments of this application, the method includes:

[0171] Receive node lifecycle management information;

[0172] The node lifecycle is managed based on the node lifecycle management information, wherein the node lifecycle management includes one or more of the following: node creation, node shrinking, and node release.

[0173] Of course, the computer-executable instructions provided in the embodiments of this application are not limited to the method operations described above, but can also perform related operations in the node management method provided in any embodiment of this application.

[0174] Based on the above description of the implementation methods, those skilled in the art can clearly understand that this application can be implemented using software and necessary general-purpose hardware, and of course, it can also be implemented using hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk, or optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0175] It is worth noting that in the embodiments of the above-mentioned node management device, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of this application.

[0176] The above description is merely an exemplary embodiment of this application and is not intended to limit the scope of protection of this application.

[0177] Those skilled in the art will understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0178] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0179] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0180] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored in memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Multifunction Discs, DVDs, or CDs), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), programmable logic devices (FGPAs), and processors based on multi-core processor architectures.

[0181] A detailed description of exemplary embodiments of this application has been provided above through exemplary and non-limiting examples. However, various modifications and adjustments to the above embodiments will be apparent to those skilled in the art when considered in conjunction with the accompanying drawings and claims, without departing from the scope of this application. Therefore, the proper scope of this application will be determined by the claims.

Claims

1. A node management method for a network functional virtualization system, wherein the network functional virtualization system includes a service operation support system (OSS), a network virtualization function orchestrator (NFVO), a virtualization infrastructure manager (VIM), and a cluster manager (CNM); The method is executed by the cluster manager CNM and includes: Receive node lifecycle management information from the Business Operation Support System (OSS) or the Network Virtualization Orchestrator (NFVO), and generate a node lifecycle management request based on the node lifecycle management information and send it to the Virtualization Infrastructure Manager (VIM). The Virtualization Infrastructure Manager (VIM) performs lifecycle management on nodes based on the node lifecycle management request, wherein the node lifecycle management includes one or more of the following: node creation, node shrinking, and node release; When the node lifecycle management request is a node creation request, the node creation lifecycle management is performed based on the lifecycle management request, including: adding the created node to the cluster; updating the cluster information, which includes a cluster identifier and node information of all nodes in the cluster; after updating the cluster information, the method further includes: sending node creation success information to the Service Operation Support System (OSS) or the Network Virtualization Function Orchestrator (NFVO); wherein, the node creation success information includes a cluster identifier and node information of all nodes in each cluster; The method also includes node status monitoring and reporting: Send a subscription request to the Virtualization Infrastructure Manager (VIM), the subscription request being used to instruct the Virtualization Infrastructure Manager (VIM) to report node status information within a set time period; Upon receiving node status information from the Virtualization Infrastructure Manager (VIM), the node status information is sent to the Service Operation Support System (OSS) or the Network Virtualization Function Orchestrator (NFVO). The node status information includes the cluster identifier, node identifier, and node resource information of the cluster to which the node belongs. When a node malfunctions, node malfunction information is received; wherein, the node malfunction information is fed back by the Virtualization Infrastructure Manager (VIM) when there is an abnormal node in the cluster. A node creation request is sent to the Virtualization Infrastructure Manager (VIM), the node creation request carrying a node resource information model; the node resources in the node resource information model are the same as the node resources in the node resource information model of the abnormal node; Send node abnormal status information to the Business Operation Support System (OSS) or the Network Virtualization Function Orchestrator (NFVO), the node abnormal status information carrying information about the newly created node.

2. The method according to claim 1, characterized in that, When the node lifecycle management request is a node creation request, the lifecycle management of the created node is performed based on the lifecycle management request, and also includes: A node creation request is sent to the Virtualization Infrastructure Manager (VIM) of the region to which the node belongs. The node creation request carries a node resource information model. This model instructs the VIM to create the corresponding node. The node resource information model includes one or more of the following: node size, node identifier, and node resources. The model is generated based on node creation information, which includes one or more of the following: node type, node size, node resources, and node deployment. The node creation completion information is received from the VIM, and this information carries the number of nodes created and the resources allocated to each node.

3. The method according to claim 2, characterized in that, The Virtualization Infrastructure Manager (VIM) for the region to which the node belongs is determined based on the node's deployment.

4. The method according to claim 1, characterized in that, When the lifecycle management request is a node scaling request, lifecycle management of the node based on the lifecycle management request includes: A node scaling request is sent to the Virtualization Infrastructure Manager (VIM) of the region to which the node belongs. The node scaling request carries a node scaling information model, which includes the node scaling scale and node resource requirements. The node scaling request is used to instruct the Virtualization Infrastructure Manager (VIM) to perform a node scaling operation. After the node scaling operation is completed, the Virtualization Infrastructure Manager (VIM) generates node scaling result information. Receive node scaling result information from the Virtualization Infrastructure Manager (VIM).

5. The method according to claim 4, characterized in that, Before sending a node scaling request to the Virtualization Infrastructure Manager (VIM) of the node's region, the following steps are also included: The decision to initiate a node scaling request is based on the node scaling strategy.

6. The method according to claim 5, characterized in that, The step of determining whether to initiate a node scaling request based on the node scaling strategy includes: If there is insufficient node resources or insufficient node size, a node pop-up request is initiated, wherein the node pop-up includes increasing node resources or increasing node size. If the idle resources of a node exceed the resources required by the business, a node shrinkage request is initiated, wherein the node shrinkage includes reducing node resources or reducing node size.

7. The method according to claim 4, characterized in that, Before sending a node scaling request to the Virtualization Infrastructure Manager (VIM), the method also includes: Send a query request to the Virtualization Infrastructure Manager (VIM) of the region to which the node belongs; the query request is used to instruct the VIM to check whether the available resources meet the node's resource requirements; If the Virtualization Infrastructure Manager (VIM) sends a message indicating that the available resources meet the node's resource requirements, the operation of sending a node scaling-up request to the VIM is executed. If the virtualization infrastructure manager (VIM) sends a message indicating that the available resources do not meet the node's resource requirements, update the node scaling down and node resource requirements.

8. The method according to claim 4, characterized in that, After receiving the node scaling result information fed back by the Virtualization Infrastructure Manager (VIM), the process also includes: If the node displays a result indicating that a new node is to be created, then add the newly created node to the cluster. If the result information displayed by the node indicates that resources for an already created node have been added, update the node information of that already created node in the cluster. If the node displays a result indicating that the created node has been released, then delete the created node from the cluster. If the result information displayed by the node indicates a reduction in the resources of the created node, update the node information of the created node in the cluster.

9. The method according to claim 1, characterized in that, When the lifecycle management request is a node release request, the lifecycle management of the node is performed based on the lifecycle management request, including: A node release request is sent to the Virtualization Infrastructure Manager (VIM) of the region to which the node belongs. The node release request carries the node identifier. The node release request is used to instruct the Virtualization Infrastructure Manager (VIM) to release the node and the resources occupied by the node. After the node release operation is completed, the Virtualization Infrastructure Manager (VIM) generates node release result information. Receive node release result information fed back by the Virtualization Infrastructure Manager (VIM), wherein the node release result information carries the identifier of the released node; Delete the released nodes from the cluster.

10. The method according to claim 9, characterized in that, The node release request is generated in one of the following ways: Generate when there are more free nodes than required nodes; This is generated when there are abnormal nodes in the cluster.

11. A node management device for a Network Functions Virtualization (NFV) system, the NFV system comprising a Service Operation Support System (OSS), a Network Virtualization Function Orchestrator (NFVO), a Virtualization Infrastructure Manager (VIM), and a Cluster Manager (CNM); the device comprising: The receiving module is configured to receive node lifecycle management information from the Business Operation Support System (OSS) or the Network Virtualization Orchestrator (NFVO), and generate a node lifecycle management request based on the node lifecycle management information and send it to the Virtualization Infrastructure Manager (VIM). The management module is configured to allow the Virtualization Infrastructure Manager (VIM) to perform lifecycle management on nodes based on the node lifecycle management request. The node lifecycle management includes one or more of the following: node creation, node shrinking, and node release. When the node lifecycle management request is a node creation request, the node creation lifecycle management is performed based on the lifecycle management request, including: adding the created node to the cluster; updating the cluster information, which includes a cluster identifier and node information of all nodes in the cluster; after updating the cluster information, the method further includes: sending node creation success information to the Service Operation Support System (OSS) or the Network Virtualization Function Orchestrator (NFVO); wherein, the node creation success information includes a cluster identifier and node information of all nodes in each cluster; The management device is also used for node status monitoring and reporting: A subscription request is sent to the Virtualization Infrastructure Manager (VIM), which instructs the VIM to report node status information within a set time. Upon receiving the node status information from the VIM, the node status information is sent to the Service Operation Support System (OSS) or the Network Virtualization Function Orchestrator (NFVO). The node status information includes the cluster identifier of the cluster to which the node belongs, the node identifier, and the node resource information. When a node malfunctions, the system receives node malfunction information; this information is provided by the Virtualization Infrastructure Manager (VIM) in the presence of an abnormal node in the cluster; a node creation request is sent to the VIM, carrying a node resource information model; the node resources in this model are identical to those in the abnormal node's node resource information model; and node malfunction status information is sent to the Service Operation Support System (OSS) or the Network Virtualization Function Orchestrator (NFVO), carrying information about the newly created node.

12. A cluster manager, characterized in that, include: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-10.

13. A storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the method described in any one of claims 1-10.

14. A network functional virtualization system, characterized in that, The system includes: Service Operation Support System (OSS), Network Virtualization Function Orchestrator (NFVO), Virtualization Infrastructure Manager (VIM), and Cluster Manager (CNM); The Network Virtualization Function Orchestrator (NFVO) or the Service Operation Support System (OSS) sends node lifecycle management information to the Cluster Manager (CNM). The cluster manager (CNM) generates a node lifecycle management request based on the node lifecycle management information and sends the lifecycle management request to the virtualization infrastructure manager (VIM). The Virtualization Infrastructure Manager (VIM) performs lifecycle management operations on nodes based on the node lifecycle management request; wherein, the node lifecycle management includes one or more of the following: node creation, node shrinking, and node release; When the node lifecycle management request is a node creation request, the node creation lifecycle management is performed based on the lifecycle management request, including: adding the created node to the cluster; updating the cluster information, which includes a cluster identifier and node information of all nodes in the cluster; after updating the cluster information, the method further includes: sending node creation success information to the Service Operation Support System (OSS) or the Network Virtualization Function Orchestrator (NFVO); wherein, the node creation success information includes a cluster identifier and node information of all nodes in each cluster; The system is also used for node status monitoring and reporting: The cluster manager CNM sends a subscription request to the virtualization infrastructure manager VIM; The Virtual Infrastructure Manager (VIM) reports node status information within a set time based on the subscription request; Upon receiving node status information from the Virtualization Infrastructure Manager (VIM), the Cluster Manager (CNM) sends the node status information to the Service Operation Support System (OSS) or the Network Virtualization Function Orchestrator (NFVO). The node status information includes the cluster identifier, node identifier, and node resource information of the cluster to which the node belongs. In the event of an abnormal node in the cluster, the Virtualization Infrastructure Manager (VIM) generates node abnormality information and feeds it back to the Cluster Manager (CNM). The cluster manager CNM receives node anomaly information and sends a node creation request to the virtualization infrastructure manager VIM. The node creation request carries a node resource information model. The node resources in the node resource information model are the same as the node resources in the node resource information model of the abnormal node. The Virtualization Infrastructure Manager (VIM) creates new nodes and replaces abnormal nodes based on the node creation request. The cluster manager (CNM) sends node abnormal status information to the service operation support system (OSS) or the network virtualization function orchestrator (NFVO), and the node abnormal status information carries information about newly created nodes.

15. The system according to claim 14, characterized in that, When the node lifecycle management request is a node creation request, it includes: The cluster manager CNM generates a node resource information model based on the node creation information, wherein the node creation information includes one or more of the following: node type, node size, node resources, and node deployment; and the node resource information model includes one or more of the following: node size, node identifier, and node resources. The cluster manager (CNM) sends a node creation request to the virtualization infrastructure manager (VIM) of the region to which the node belongs. The node creation request carries a node resource information model. The Virtual Infrastructure Management (VIM) system creates corresponding nodes based on the node resource information model. The cluster manager (CNM) receives node creation completion information from the virtualization infrastructure manager (VIM); the node creation completion information includes the number of nodes created and the resources allocated to the nodes.

16. The system according to claim 14, characterized in that, When the lifecycle management request is a node scaling request, it includes: The cluster manager CNM sends a node scaling request to the virtualization infrastructure manager VIM. The node scaling request carries a node scaling information model, which includes the node scaling scale and node resource requirements. The Virtual Infrastructure Management (VIM) system executes node scaling operations based on node scaling requests and generates node scaling result information. The cluster manager (CNM) receives node scaling results from the virtualization infrastructure manager (VIM) and updates the cluster information where the nodes reside.

17. The system according to claim 16, characterized in that, include: The cluster manager CNM sends a query request to the virtualization infrastructure manager VIM, which is the virtualization infrastructure manager of the region to which the node belongs. The Virtualization Infrastructure Manager (VIM) queries whether the available resources meet the node's resource requirements based on the query request, and then feeds back the query results to the Cluster Manager (CNM). When the cluster manager CNM receives a message from the virtualization infrastructure manager VIM indicating that the available resources meet the node's resource requirements, it sends a node scaling-out request to the virtualization infrastructure manager VIM. When the Cluster Manager (CNM) receives a message from the Virtualization Infrastructure Manager (VIM) indicating that the available resources do not meet the node resource requirements, it updates the node scaling and node resource requirements.

18. The system according to claim 14, characterized in that, Including, in the case that the lifecycle management request is a node release request, The cluster manager CNM sends a node release request to the virtualization infrastructure manager VIM in the region to which the node belongs, wherein the node release request carries the node identifier; The Virtualization Infrastructure Manager (VIM) releases the node and the resources it occupies based on the node release request and generates node release result information. The cluster manager CNM receives node release result information from the virtualization infrastructure manager VIM, wherein the node release result information carries the identifier of the released node; The cluster manager CNM deletes the released nodes from the cluster.

Images