WO2021109750A1 - 节点管理方法、装置、设备、存储介质和系统 - Google Patents

节点管理方法、装置、设备、存储介质和系统 Download PDF

Info

Publication number
WO2021109750A1
WO2021109750A1 PCT/CN2020/123533 CN2020123533W WO2021109750A1 WO 2021109750 A1 WO2021109750 A1 WO 2021109750A1 CN 2020123533 W CN2020123533 W CN 2020123533W WO 2021109750 A1 WO2021109750 A1 WO 2021109750A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
information
vim
request
resource
Prior art date
Application number
PCT/CN2020/123533
Other languages
English (en)
French (fr)
Inventor
谢宝国
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to KR1020227022357A priority Critical patent/KR20220103796A/ko
Priority to US17/779,767 priority patent/US20220413937A1/en
Priority to EP20895097.2A priority patent/EP4071609A4/en
Priority to JP2022532127A priority patent/JP7438355B2/ja
Publication of WO2021109750A1 publication Critical patent/WO2021109750A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5072—Grid computing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45595—Network integration; Enabling network access in virtual machine instances
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/505—Clust
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/508—Monitor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/065—Generation of reports related to network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning

Definitions

  • This application relates to the technical field of communication networks, for example, to a node management method, device, equipment, storage medium, and system.
  • cluster nodes In open source technologies, such as Kubernetes (K8s), cluster nodes (Cluster nodes) need to be used to run the container integrated environment.
  • a node is a working node in a Kubernetes cluster.
  • the service running on the node is used to run pod and communicate with the master.
  • NFV Network Functions Virtualization
  • This application provides a node management method, device, equipment, storage medium and system.
  • the embodiment of the present application provides a node management method, including:
  • the node life cycle management is performed on the node based on the node life cycle management information, where the node life cycle management includes one or more of the following: node creation, node shrinking, and node release.
  • An embodiment of the present application provides a node management device, including:
  • the receiving module is set to receive node life cycle management information
  • the management module is configured to perform life cycle management on nodes based on the node life cycle management information, where the node life cycle management includes one or more of the following: node creation, node shrinking, and node release.
  • the embodiment of the present application provides a cluster manager, including:
  • One or more processors are One or more processors;
  • Memory used to store one or more programs
  • the one or more processors When the one or more programs are executed by the one or more processors, the one or more processors implement any method as in the embodiments of the present application.
  • An embodiment of the present application provides a network function virtualization system, the system includes: a business operation support system OSS, a network function virtualization orchestrator NFVO, a virtualization basic setting manager VIM, and a cluster manager CNM;
  • the CNM generates a node life cycle management request based on the node life cycle management information, and sends the life cycle management request to the VIM,
  • the VIM performs life cycle management operations on the node based on the node life cycle management request.
  • the embodiment of the present application provides a storage medium that stores a computer program, and when the computer program is executed by a processor, any one of the methods in the embodiments of the present application is implemented.
  • FIG. 1 is a schematic diagram of the NFV system architecture defined by ETSI;
  • FIG. 2 is a flowchart of a node management method provided by an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a node management apparatus provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a network function virtualization system provided by an embodiment of the present application.
  • Figure 5 is a structural diagram of an NFV system with a cluster management function provided by an embodiment of the present application
  • FIG. 6 is a flowchart of a method for creating a node according to an embodiment of the present application.
  • FIG. 7 is a flowchart of a node resizing method provided by an embodiment of the present application.
  • FIG. 8 is a flowchart of a node release method provided by an embodiment of the present application.
  • FIG. 9 is a flowchart of a method for monitoring and reporting Node status according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a cluster manager provided by an embodiment of this application.
  • a node is a working node in a kubernetes cluster, which can be a virtual machine or a physical machine. Some services run on Node to run pod and communicate with master. The services on a node include the docker runtime environment and so on. Kubernetes needs to download container images on Node to create container objects, such as POD, Service, Deployment, etc. Service providers or operators can load applications on the container objects to implement network system services in the container environment.
  • NFV Network Functions Virtualization
  • FIG 1 is a schematic diagram of the NFV system architecture defined by ETSI.
  • the NFV system architecture defined by the European Telecommunications Standards Institute mainly includes: business operation support system and management support system (Operation-Support System) /Business Support System, OSS/BSS), Virtualized Network Function (Virtualized Network Function, VNF), Network Function Virtualization Infrastructure (NFVI), and Network Function Virtualization Management and Orchestration System (VNF-Management) and Orchestration, NFV-MANO).
  • NFVI is mainly responsible for comprehensively virtualizing hardware resources such as computing, storage, and networks, and mapping them into virtual resources; VNF uses software to implement various traditional physical network functions.
  • VNF runs on NFVI and uses process Virtual resources after NFVI virtualization.
  • NFV-MANO is responsible for managing and orchestrating the relationship between VNF and NFVI and the connection relationship between VNFs and/or with other physical network functions (PNF).
  • PNF physical network functions
  • NFV-MANO includes: Virtualized Infrastructure Manager (VIM), Virtualized Network Function Manager (VNFM), and Network Function Virtualization Orchestrator (NFVO).
  • VIM is responsible for controlling and managing virtualized resources.
  • VIM can also include the function of Physical Infrastructure Manager (PIM), which is responsible for the management of bare metal resources, such as physical servers; VNFM is responsible for VNF lifecycle management; NFVO is responsible for the orchestration and management of virtual infrastructure, and Life cycle management of network services (NS, Network Service).
  • PIM Physical Infrastructure Manager
  • NFM is responsible for the management of bare metal resources, such as physical servers
  • VNFM is responsible for VNF lifecycle management
  • NFVO is responsible for the orchestration and management of virtual infrastructure, and Life cycle management of network services (NS, Network Service).
  • FIG. 2 is a flowchart of a node management method provided by an embodiment of the present application.
  • the node management method provided in this embodiment is mainly applicable to the case of managing the life cycle of a node in an NFV system, and the node management method is executed by a node management device
  • the node management device can be implemented by a hardware and/or software method.
  • the node management method provided by the embodiment of the present application mainly includes steps S11 and S12.
  • S12. Perform life cycle management on nodes based on the node life cycle management information, where the node life cycle management includes one or more of the following: node creation, node shrinking, and node release.
  • the node life cycle management information is sent from one of the following nodes:
  • the virtual network function manager VNFM wherein the VNFM forwards the node life cycle management information sent by the NFVO.
  • the performing life cycle management on a 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 the virtualization basic settings manager VIM, the node life cycle management request is used to instruct the VIM to perform node resource management operations on the node, and the VIM generates operation result information after performing the node resource management operation; receives the operation result information fed back by the VIM , And forward it to OSS or NFVO.
  • the life cycle management of the node creation node based on the life cycle management request includes: sending to the VIM of the region to which the node belongs A node creation request, 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 includes one or more of the following: node size , Node identification, node resource; the node resource information model is generated based on node creation information, where the node creation information includes one or more of the following: node type, node size, node resource, node deployment; receiving the VIM feedback
  • the node creation completion information of, wherein the node creation completion information carries the number of nodes created and the resources allocated by the nodes.
  • the method further includes: adding the created node to the cluster; updating the cluster information, the cluster information including the cluster identifier and the cluster Node information of all nodes.
  • the cluster information after the cluster information is updated, it further includes: sending node creation success information to OSS or NFVO, where the node creation success information includes a cluster identifier and node information of all nodes in each cluster.
  • the VIM of the area to which the node belongs is determined based on the deployment of the node.
  • performing the life cycle management of node shrinkage on the node based on the life cycle management request includes: reporting to the VIM of the region to which the node belongs Send a node shrink request, wherein the node shrink request carries a node shrink information model, and the node shrink information model includes node shrink size and node resource requirements, and the node shrink request is used to indicate the
  • the VIM performs the node shrinking operation, and after the node shrinking operation is completed, the VIM generates node shrinking result information; receiving the node shrinking result information fed back by the VIM.
  • the method before sending the node resizing request to the VIM of the area where the node belongs, the method further includes: determining whether to initiate the node resizing request according to the node resizing strategy.
  • the determining whether to initiate a node shrinking request according to a node shrinking strategy includes: initiating a node ejecting request when the node resources are insufficient or the node size is insufficient, wherein the node ejecting includes Increase node resources or increase node scale; in the case where node idle resources are greater than the resources required by the business, initiate a node shrinking request, where the node shrinking includes reducing node resources or reducing node scale.
  • the method before sending a node bounce request to the VIM, the method further includes: sending a query request to the VIM in the area to which the node belongs; the query request is used to instruct the VIM to query whether free resources are satisfied Node resource requirements; in the case where the idle resources sent by the VIM meet the node resource requirements, perform the operation of sending the node bounce request to the VIM; in the case where the idle resources sent by the VIM do not meet the node resource requirements, Update node scaling and node resource requirements.
  • the method further includes: adding the newly created node to the cluster in the case that the node shrinking result information is to create a new node ; In the case where the node shrink result information is to increase the resource of the created node, update the node information of the created node in the cluster; in the case where the node shrink result information is to release the created node, the cluster The created node is deleted; in the case that the result information of the node collapse is to reduce the resources of the created node, the node information of the created node in the cluster is updated.
  • performing life cycle management of the node to release the node based on the life cycle management request includes: sending the node to the VIM in the area where the node belongs A release request, where the node release request carries a node identifier; the node release request is used to instruct the VIM to release the node and the resources occupied by the node, and the VIM generates node release result information after the node release operation is completed; receiving the VIM feedback The node release result information of, wherein the node release result information carries the identifier of the released node; the released node in the cluster is deleted.
  • the node release request is generated in one of the following ways:
  • the method further includes:
  • the node status information includes the cluster identification, node identification and node resource information of the cluster to which the node belongs.
  • the method includes: sending a node status query request to the VIM, where the node status query request is used to instruct the VIM to report node status information.
  • the method includes: receiving node abnormality information; wherein the node abnormality information is fed back by the VIM when there are abnormal nodes in the cluster; sending a node creation request to the VIM,
  • the node creation request carries the node resource information model; the node resource in the node resource information model is the same as the node resource of the node resource information model of the abnormal node; the node abnormal state information is sent to OSS or NFVO, and the node abnormal state
  • the information carries the newly created node information.
  • FIG 3 is a schematic structural diagram of a node management device provided by an embodiment of the present application.
  • the node management device provided in this embodiment is mainly applicable to the case of managing the life cycle of a node in an NFV system.
  • the node management device may be composed of hardware and/ Or software method implementation.
  • the node management apparatus provided by the embodiment of the present application mainly includes a receiving module 21 and a management module 22.
  • the receiving module 21 is set to receive node life cycle management information
  • the management module 22 is configured to perform life cycle management on nodes based on the node life cycle management information, where the node life cycle management includes one or more of the following: node creation, node shrinking, and node release.
  • the node life cycle management information is sent from one of the following nodes:
  • the virtual network function manager VNFM wherein the VNFM forwards the node life cycle management information sent by the NFVO.
  • the management module 22 is configured to generate a node life cycle management request based on the node life cycle management information; send the node life cycle management request to the virtualization infrastructure setting manager VIM, the The node lifecycle management request is used to instruct the VIM to perform a node resource management operation on the node. After the VIM performs the node resource management operation, the operation result information is generated; the operation result information fed back by the VIM is received and forwarded to the OSS or NFVO.
  • the management module 22 is configured to perform the life cycle management of node creation on the node based on the life cycle management request when the node life cycle management request is a node creation request.
  • the management module 22 is configured to send a node creation request to the VIM in the area where 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
  • the node resource information model includes one or more of the following: node size, node identifier, node resource; the node resource information model is generated based on node creation information, wherein the node creation information includes one or more of the following : Node type, node size, node resource, node deployment; receiving the node creation completion information fed back by the VIM, wherein the node creation completion information carries the number of nodes created and the resources allocated by the nodes.
  • the management module 22 is configured to add the created node to the cluster after the node creation completion information received from the VIM feedback; update the cluster information, and the cluster information includes the cluster Identifies and node information of all nodes in the cluster.
  • the management module 22 is configured to send node creation success information to OSS or NFVO after updating the cluster information, where the node creation success information includes the cluster identifier and all nodes in each cluster The node information.
  • the VIM of the area to which the node belongs is determined based on the deployment of the node.
  • the management module 22 is configured to perform the life cycle management of node collapse on the node based on the life cycle management request when the life cycle management request is a node collapse request, In an embodiment, the management module 22 is configured to send a node shrinkage request to the VIM of the area where the node belongs, wherein the node shrinkage request carries a node shrinkage information model, and the node shrinkage information model includes the nodeshrinking scale, node resource requirements, the node shrinking request is used to instruct the VIM to perform the node shrinking operation, after the node shrinking operation is completed, the VIM generates node shrinking result information; receiving the node shrinking result feedback from the VIM information.
  • the management module 22 is configured to determine whether to initiate a node shrink request according to the node shrink policy before sending the node shrink request to the VIM of the area where the node belongs.
  • the management module 22 is configured to initiate a node popup request when the node resources are insufficient or the node scale is insufficient, wherein the node popup includes increasing node resources or increasing node size; In the case where the idle resources are greater than the resources required by the service, a node shrinking request is initiated, where the node shrinking includes reducing node resources or reducing node scale.
  • the management module 22 is configured to send a query request to the VIM in the area to which the node belongs before sending a node bounce request to the VIM; the query request is used to instruct the VIM to query for availability Whether the resource meets the resource requirement of the node; when the idle resource sent by the VIM meets the resource requirement of the node, execute the operation of sending the node bounce request to the VIM; when the idle resource sent by the VIM does not meet the resource requirement of the node In this case, update the node shrinkage scale and node resource requirements.
  • the management module 22 is configured to, after receiving the node collapse result information fed back by the VIM, if the node collapse result information is to create a new node, create a new node.
  • the node of the node is added to the cluster; in the case that the node popping up the shrinking information is to increase the resource of the created node, update the node information of the created node in the cluster; when the node shrinking result information is the situation of releasing the created node Next, delete the created node in the cluster; in the case that the result information of the node collapse is to reduce the resources of the created node, update the node information of the created node in the cluster.
  • the management module 22 is configured to perform life cycle management on the node to release the node based on the life cycle management request when the life cycle management request is a node release request.
  • the management module 22 is configured to send a node release request to the VIM in the area to which the node belongs, where the node release request carries a node identifier; the node release request is used to indicate the VIM release node and the node occupied After the node release operation is completed, the VIM generates node release result information; receives the node release result information fed back by the VIM, where the node release result information carries the released node identifier; and deletes the released node in the cluster.
  • the node release request is generated in one of the following ways:
  • the management module 22 is configured to send a subscription request to the VIM, where the subscription request is used to instruct the VIM to report node status information within a set time; upon receiving the VIM In the case of node status information fed back, the node status information is sent to OSS or NFVO, and the node status information includes the cluster identification of the cluster to which the node belongs, the node identification, and node resource information.
  • the management module 22 is configured to send a node status query request to the VIM, and the node status query request is used to instruct the VIM to report node status information.
  • the management module 22 is configured to receive node abnormality information; wherein, the node abnormality information is fed back by the VIM when there are abnormal nodes in the cluster; and the VIM sends node creation Request, the node creation request carries the node resource information model; the node resource in the node resource information model is the same as the node resource of the node resource information model of the abnormal node; the node abnormal state information is sent to OSS or NFVO, and the node The abnormal state information carries the newly created node information.
  • Fig. 4 is a schematic structural diagram of a network function virtualization system provided by an embodiment of the present application. As shown in Fig. 4, the system includes a business operation support system OSS, a network function virtualization orchestrator NFVO, a virtualization basic setting manager VIM, and The cluster manager CNM.
  • OSS business operation support system
  • NFVO network function virtualization orchestrator
  • VIM virtualization basic setting manager
  • CNM cluster manager
  • the NFVO or OSS sends node life cycle management information to the CNM.
  • the CNM generates a node life cycle management request based on the node life cycle management information.
  • the CNM sends a node life cycle management request to the VIM.
  • the VIM performs a life cycle management operation on the node based on the node life cycle management request.
  • the operation result information of the node is generated, and the operation result information of the node is sent to the CNM; the CNM forwards the operation result information of the node To the NFVO or the OSS.
  • the node lifecycle management request is a node creation request
  • 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 size, node resources, node deployment, and the node resource information model includes the following one Or more: node size, node identification, node resource;
  • the CNM sends a node creation request to the VIM in the area to which the node belongs, where the node creation request carries a node resource information model;
  • the VIM creates a corresponding node based on the node resource information model
  • the CNM receives the node creation completion information fed back by the VIM, and adds the node to the cluster.
  • the node creation completion information carries the number of created nodes and the resources allocated by the nodes.
  • the method further includes:
  • the CNM sends a node shrinkage request to the VIM, wherein the node shrinkage request carries a node shrinkage information model, and the node shrinkage information model includes the node shrinkage scale and node resource requirements;
  • the VIM performs a node shrinking operation based on the node shrinking request and generates node shrinking result information
  • the CNM receives the result information of the node's resilience fed back by the VIM, and updates the cluster information where the node is located.
  • the CNM sends a query request to the VIM in the area to which the node belongs;
  • the VIM queries whether free resources meet the node resource requirements based on the query request, and feeds back the query result to the CNM;
  • the CNM sends a node bounce request to the VIM when the idle resource sent by the VIM meets the resource requirement of the node;
  • the CNM When the CNM receives the idle resource sent by the VIM and does not meet the resource requirement of the node, it updates the node shrinkage scale and the node resource requirement.
  • the life cycle management request is a node release request
  • the CNM sends a node release request to the VIM in the area to which the node belongs, where the node release request carries a node identifier;
  • the VIM releases the node and the resources occupied by the node based on the node release request, and generates node release result information
  • the CNM receives node release result information fed back by the VIM, where the node release result information carries a released node identifier;
  • the CNM deletes the released nodes in the cluster.
  • the CNM sends a subscription request to the VIM
  • the VIM reports node status information within a set time based on the subscription request
  • the node status information is sent to the OSS or NFVO, and the node status information includes the cluster identification of the cluster to which the node belongs, the node identification, and node resource information.
  • the VIM generates node abnormal information and feeds it back to the CNM when there are abnormal nodes in the cluster;
  • the CNM receives node abnormality information and sends a node creation request to the VIM.
  • the node creation request carries a node resource information model; the node resource in the node resource information model and the node of the node resource information model of the abnormal node The same resources;
  • the VIM creates a new node based on the node creation request and replaces the abnormal node;
  • the CNM sends node abnormal state information to OSS or NFVO, and the node abnormal state information carries newly created node information.
  • a cluster management function CNM Cluster Node Manager
  • CNM Cluster Node Manager
  • the cluster management function CNM is responsible for node lifecycle management, including functions such as node creation, node scaling, and node release.
  • the cluster management function CNM is also responsible for the update of cluster nodes, adding a newly created node to a cluster, updating the cluster where the related node is located when the node is updated, and deleting the node from the corresponding node when the node is released.
  • the cluster management function CNM can interact with OSS/NFVO, obtain creation information, update information, and release information of related nodes from OSS/NFVO, and report the created, updated, and released information of nodes to OSS/NFVO in a timely manner.
  • 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 from the VIM. After the VIM is successfully created, the CNM will be notified in time that the node has been created, updated, and released.
  • the cluster management function CNM can interact with the VNFM and obtain the node creation template information from the VNFM.
  • VIM When a node is abnormal, VIM will notify CNM when it detects that the node is abnormal, and CNM will report the abnormal information to OSS/NFVO in time. CNM will request VIM to create a completely replacement node to replace the abnormal node.
  • FIG. 6 is a flowchart of a node creation method provided by an embodiment of this application.
  • OSS/NFVO is based on network planning.
  • Third-party applications or operators need to initiate Node creation and carry Node to create an information model.
  • CNM parses the information model created by the Node.
  • CNM generates a Node resource information model, selects 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 a Node.
  • VIM successfully creates a Node, it returns the successful creation message of the node.
  • CNM adds the created Node to a Cluster Node and notifies OSS/NFVO to create the requested Node successfully.
  • S101 The operator will plan and design according to user needs and network planning, and create an information model for the required Node, including Node type, Node size (number of Nodes), Node resource requirements, Node deployment and other requirements using network function descriptions (virtual network functions) Descriptor/Physical Network Function Descriptor (Virtualized Network Function Descriptor/Physical Network Function Descriptor, VNFD/PNFD) for planning and design.
  • Node type Node size (number of Nodes), Node resource requirements, Node deployment and other requirements using network function descriptions (virtual network functions) Descriptor/Physical Network Function Descriptor (Virtualized Network Function Descriptor/Physical Network Function Descriptor, VNFD/PNFD) for planning and design.
  • VNFD/PNFD Virtualized Network Function Descriptor/Physical Network Function Descriptor
  • the Node creation information model can also be planned and designed using a newly defined Node function description template.
  • the Node function description template is used by OSS/NFVO to transfer Node creation information to CNM.
  • the OSS/NFVO directly sends the Node creation information model to the CNM, and may also forward the Node creation information model to the CNM through the VNFM; wherein the VNFM forwards the creation information model sent by the NFVO.
  • the CNM parses the received Node creation information model, parses the network function description or the related Node information in the Node function description, and generates a Node resource information model.
  • the Node resource information model includes the scale of the Node, the identification of the Node, and the resources required by the Node (computing, Storage, network) and other resource-related information.
  • the CNM selects the VIM in the area according to the Node deployment information, and initiates a Node creation request to the VIM.
  • the Node creation request carries the Node resource information model, including the Node size, the Node ID, and the resources required by the Node (computing, storage, network ), and send it to the VIM/PIM in the deployment area according to the Node deployment information.
  • the VIM creates a corresponding Node according to the Node resource information model, and returns the completion information of the Node creation.
  • the information carried is not limited to the number of nodes of the created Node, and the resources allocated by the Node (computing resources, storage resources, and network resources).
  • the Cluster Node information includes the Cluster cluster ID, and information about all Nodes in the cluster, such as Node ID, Node resource, and node status.
  • S107 CNM notifies OSS/NFVO that the Node has been established, and carries information about the successful creation of the Cluster Node, including the Cluster Node ID, and information such as the identity, resources, and deployment location of the created Node to which each Cluster Node belongs.
  • FIG. 7 is a flowchart of a node resizing method provided by an embodiment of this application.
  • OSS/NFVO can initiate Node resizing
  • CNM can also initiate a node bounce request. After CNM receives the request for elasticity and shrinkage, it first queries the selected VIM to see if the resource meets the node elasticity and shrinkage requirements. If not, it needs OSS/NFVO to update the node elasticity and shrinkage requirements, or CNM actively updates the Node elasticity and shrinkage requirements to make the VIM's Resources can meet the needs of elasticity.
  • CNM initiates a Node bounce request to VIM, and VIM performs a Node bounce operation.
  • CNM updates the Cluster Node and reports the shrinking results to OSS/NFVO.
  • the Node bounce request can be triggered by OSS/NFVO or initiated by the cluster node management function CNM.
  • OSS/NFVO can be triggered according to Node's shrinking strategy. For example, according to preset conditions, if the used number of Node is greater than a certain ratio (such as 80%), it will be triggered; or it can be triggered by a third party's use of Node, such as the one from Kubernetes (K8S). Node activation requirements.
  • the cluster node management system CNM can also actively initiate the scaling of the Node according to the strategy of the scaling of the Node, if the existing Node does not meet the business requirements.
  • Node popup is initiated, including two ways to increase Node resources and increase Node size; if the idle resources of Node are greater than the resources required by the business, then initiate Node shrinking, including reducing Node resources and reducing Node size 2 ways.
  • S202 CNM receives a Node bounce request initiated by OSS/NFVO, or receives a Node bounce request forwarded by VNFM.
  • the request message carries a Cluster cluster identifier, a Node bounce information model, and the Node bounce information model includes Node bounce information. Information such as scale, resources required by Node, etc.
  • the CNM actively initiates the Node resizing operation according to the resizing strategy, it can actively generate the Node resizing information model, including the size of the Node resizing, the resources required by the Node, and other information.
  • the CNM queries the VIM in the area based on the deployment information of the Node to see if the free resources meet the resource requirements of the Node. If the resource requirements are not met, it will feed back to OSS/NFVO, and the OSS/NFVO will update the Node’s elastic Scale down and shrink resources.
  • CNM actively adjusts the resizing scale and resizing resources of Node.
  • CNM initiates a shrink request to VIM, and VIM performs a Node shrink operation: When the Node pops up, VIM generates a new Node according to the Node shrink information, and allocates required resources, or increases the created Node resources; shrink operation At the time, reduce the resources of the created Node, or release the corresponding Node, including the release of the originally allocated resources.
  • the VIM notifies the CNM of the result of the Node bounce.
  • the CNM reports the result of the Node's compression to the OSS/NFVO. In addition, it is optional to report the update information of Cluster Node.
  • the update information includes Cluster cluster id and Node update information (such as id, resource).
  • FIG. 8 is a flowchart of a node release method provided in an embodiment of the present application.
  • OSS/NFVO or CNM can release a part of Nodes to save VIM resources when the idle Nodes are far greater than the required Nodes according to actual needs of Nodes.
  • OSS/NFVO initiates a Node release request
  • CNM initiates a Node release request according to a policy
  • VIM releases the created Node and its occupied resources according to the Node id.
  • CNM needs to update the Cluster information, delete the released Node, and notify OSS/NFVO of the result of the Node release.
  • the release of Node can be triggered by OSS/NFVO or initiated by CNM.
  • OSS/NFVO can be based on business deployment requirements. For example, if a network slicing service for 5G is terminated due to service expiration, the Node used for the network service can be notified to release the Node by the open source application.
  • the cluster node management system CNM can also actively initiate the release of Node according to the Node release strategy. For example, the existing idle Node has far exceeded the business demand, or the Node in a Cluster cluster is abnormal.
  • the CNM receives the Node release request initiated by the OSS/NFVO or the Node release request forwarded by the VNFM.
  • the request message carries the Cluster ID and the Node ID.
  • CNM can also actively initiate a Node release operation according to the Node release strategy, which is used to release idle or abnormal Nodes in the Cluster.
  • the CNM initiates a Node request to the VIM in the area where the Node is located, and carries the Node identifier.
  • the VIM releases the Node and the resources occupied by the Node, and notifies the CNM of the release result of the Node.
  • the CNM updates the cluster information, and deletes the successfully released Node from the cluster.
  • the CNM reports the released result information of the Node to the OSS/NFVO. In addition, it is optional to report the update information of Cluster Node.
  • the update information includes Cluster cluster id and Node update information (such as id, resource).
  • FIG. 9 is a flowchart of a method for monitoring and reporting Node status provided by an embodiment of this application.
  • CNM can subscribe to VIM or dynamically query Node status information, and send Node information to OSS/NFVO.
  • VIM actively reports to CNM.
  • CNM looks for alternative Nodes in the cluster information. If there is no alternative idle Node, CNM initiates creation of Nodes to VIM to replace abnormal Nodes, and reports to OSS/NFVO Node abnormal information, and report the created replaceable Node information to OSS/NFVO at the same time.
  • the CNM dynamically queries the VIM for the Node status, can subscribe to the VIM to periodically report the Node status information, and can also dynamically and actively query the Node status information.
  • the query message carries the identity of the Node.
  • the VIM periodically sends Node status information to the CNM according to the subscription mechanism, or returns the Node status after receiving a query request from the CNM.
  • CNM reports the status of Node to OSS/NFVO, or forwards it to OSS/NFVO through VNFM.
  • the message carries information such as the Cluster ID, the ID of the Node, and the status of the Node (free resources and occupied resources).
  • S405 The CNM searches whether there is an idle Node in the Cluster that can replace the Node, and if not, it requests the VIM to create a new Node with the same resources as the abnormal Node, and the Node is used to replace the abnormal Node.
  • the CNM reports the abnormal status information of the Node to the OSS/NFVO, and gives a replaceable Node identifier in the notification message.
  • FIG. 10 is a schematic structural diagram of a cluster manager provided by an embodiment of this application.
  • the cluster manager includes processing
  • the number of processors 100 in the cluster manager can be one or more.
  • one processor 100 is taken as an example; the number of processors 100 in the cluster manager is
  • the memory 101, the input device 102, and the output device 103 may be connected through a bus or other methods.
  • the connection through a bus is taken as an example.
  • the memory 101 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 embodiment of the present application (for example, the receiving module in the node management device). 21 and management module 22).
  • the processor 100 executes various functional applications and data processing of the cluster manager by running software programs, instructions, and modules stored in the memory 101, that is, implements any method provided in the embodiments of the present application.
  • the memory 101 may mainly include a program storage area and a data storage area.
  • the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the terminal.
  • the memory 101 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices.
  • the memory 101 may include a memory remotely provided with respect to the processor 100, and these remote memories may be connected to the cluster manager through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • the input device 102 can be used to receive inputted numeric or character information, and generate key signal inputs related to user settings and function control of the cluster manager.
  • the output device 103 may include a display device such as a display screen.
  • the embodiments of the present application also provide a storage medium containing computer-executable instructions.
  • the computer-executable instructions are used to execute any of the instructions provided in the embodiments of the present application when executed by a computer processor. method.
  • the method includes:
  • the node life cycle management is performed on the node based on the node life cycle management information, where the node life cycle management includes one or more of the following: node creation, node shrinking, and node release.
  • An embodiment of the present application provides a storage medium containing computer-executable instructions.
  • the computer-executable instructions are not limited to the method operations described above, and can also perform related operations in the node management method provided by any embodiment of the present application. .
  • this application can be implemented by software and necessary general-purpose hardware, or can be implemented by hardware.
  • this application can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access Random Access Memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including several instructions to make a computer device (which can be a personal computer, server, or network device, etc.) execute the various embodiments of this application Methods.
  • the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be realized; in addition, each The specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of this application.
  • user terminal encompasses any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser, or a vehicle-mounted mobile station.
  • the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.
  • Computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages Source code or object code.
  • ISA Instruction Set Architecture
  • the block diagram of any logic flow in the drawings of the present 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 can be stored on the memory.
  • the memory can be of any type suitable for the local technical environment and can 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 multi-function optical discs) (Digital Video Disc, DVD) or Compact Disk (CD)), etc.
  • Computer-readable media may include non-transitory storage media.
  • the data processor can be any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processors, DSP), application specific integrated circuits (ASICs) ), programmable logic devices (Field-Programmable Gate Array, FPGA), and processors based on multi-core processor architecture.
  • DSP Digital Signal Processors
  • ASICs application specific integrated circuits
  • FPGA Field-Programmable Gate Array
  • processors based on multi-core processor architecture such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processors, DSP), application specific integrated circuits (ASICs) ), programmable logic devices (Field-Programmable Gate Array, FPGA), and processors based on multi-core processor architecture.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mathematical Physics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种节点管理方法、装置、设备、存储介质和系统，所述节点管理方法包括：接收节点生命周期管理信息（S11）；基于所述节点生命周期管理信息对节点进行生命周期管理，其中，所述节点生命周期管理包括以下至少一个：节点创建、节点弹缩和节点释放（S12）。

Description

节点管理方法、装置、设备、存储介质和系统
本申请要求在2019年12月02日提交中国专利局、申请号为201911216078.6的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信网络技术领域，例如涉及一种节点管理方法、装置、设备、存储介质和系统。
背景技术
开源技术中，如Kubernetes(K8s)，需要使用集群节点(Cluster节点)运行容器集成环境。节点是Kubernetes集群中的工作节点。节点上运行服务用来运行pod以及与master通信等。网络功能虚拟化(Network Functions Virtualization，NFV)系统中，并未涉及对集群中的节点进行生命周期管理。
发明内容
本申请提供一种节点管理方法、装置、设备、存储介质和系统。
本申请实施例提供一种节点管理方法，包括：
接收节点生命周期管理信息；
基于所述节点生命周期管理信息对节点进行生命周期管理，其中，所述节点生命周期管理包括以下一个或多个：节点创建、节点弹缩和节点释放。
本申请实施例提供一种节点管理装置，包括：
接收模块，被设置为接收节点生命周期管理信息；
管理模块，被设置为基于所述节点生命周期管理信息对节点进行生命周期管理，其中，所述节点生命周期管理包括以下一个或多个：节点创建、节点弹缩和节点释放。
本申请实施例提供一种集群管理器，包括：
一个或多个处理器；
存储器，用于存储一个或多个程序；
当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如本申请实施例中的任意一种方法。
本申请实施例提供一种网络功能虚拟化系统，所述系统包括：业务运营支撑系统OSS、网络功能虚拟化编排器NFVO、虚拟化基础设置管理器VIM和集群管理器CNM；
所述NFVO或OSS向所述CNM发送节点生命周期管理信息；
所述CNM基于节点生命周期管理信息生成节点生命周期管理请求，并向所述VIM发送生命周期管理请求，
所述VIM基于所述节点生命周期管理请求对节点进行生命周期管理操作。
本申请实施例提供了一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中的任意一种方法。
附图说明
图1是ETSI定义NFV系统架构的示意图；
图2是本申请实施例提供的节点管理方法的流程图；
图3是本申请实施例提供的节点管理装置的结构示意图；
图4是本申请实施例提供的网络功能虚拟化系统的结构示意图；
图5是本申请实施例提供的具有集群管理功能的NFV系统的结构图；
图6是本申请实施例提供的一种节点创建方法的流程图；
图7是本申请实施例提供的一种节点弹缩方法的流程图；
图8是本申请实施例提供的一种节点释放方法的流程图；
图9是本申请实施例提供的一种Node状态监控并上报的方法的流程图；
图10为本申请实施例提供的一种集群管理器的结构示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
开源技术中，如Kubernetes，需要使用集群节点(Cluster node)运行容器集成环境。node是kubernetes集群中的工作节点，可以是虚拟机也可以是物理机。Node(节点)上运行一些服务用来运行pod以及与master通信等。一个node上的服务包括docker运行时环境等。Kubernetes需要在Node上下载容器镜像建立容器对象，如POD，Service，Deployment等，服务提供商或运营商可以在容器对象上装载应用程序实现容器环境下的网络系统服务。
网络功能虚拟化(Network Functions Virtualization，NFV)是一种通过使用通用硬件以及虚拟化技术来承载其他功能的软件处理技术，旨在降低网络昂贵的设备成本。NFV通过软硬件解耦及功能抽象，使网络设备功能不再依赖于专用硬件，资源可以充分灵活共享，实现新业务的快速开发和部署，并基于实际业务需求进行自动部署、弹性伸缩、故障隔离和自愈等。
图1是ETSI定义NFV系统架构的示意图，如图1所示，欧洲电信标准协会(European Telecommunications Standards Institute，ETSI)定义的NFV系统架构主要包含：业务运营支撑系统和管理支撑平台(Operation-Support System/Business Support System，OSS/BSS)、虚拟化的网络功能(Virtualized Network Function，VNF)、网络功能虚拟化基础设施(Network Functions Virtualization Infrastructure，NFVI)和网络功能虚拟化管理和编排系统(VNF-Management and Orchestration，NFV-MANO)。其中，NFVI主要负责将计算、存储以及网络等硬件资源全面虚拟化，并映射成虚拟资源；VNF则是利用软件来实现各种传统的物理网络功能，VNF运行在NFVI之上，使用的是经过NFVI虚拟化后的虚拟资源。NFV-MANO负责管理和编排VNF和NFVI之间的关系以及VNF之间和\或与其他物理网络功能(Physical Network Functions，PNF)之间的连接关系。
NFV-MANO包含:虚拟化基础设置管理器(Virtualized Infrastructure Manager，VIM)、虚拟网络功能管理器(Virtualized Network Function Manager，VNFM)和网络功能虚拟化编排器(Network Function Virtualization Orchestrator，NFVO)。VIM负责控制和管理虚拟化资源。另外VIM还可包含物理基础设置管理器(Physical Infrastructure Manager，PIM)功能，负责对裸机资源进行管理，例如物理服务器；VNFM负责VNF的生命周期管理；NFVO负责对虚拟基础设施的编排和管理，以及对网络服务(NS，Network Service)的生命周期管理。
图2是本申请实施例提供的节点管理方法的流程图，本实施例提供的节点管理方法主要适用于NFV系统中对节点的生命周期进行管理的情况，所述节点管理方法由节点管理装置执行，所述节点管理装置可以由硬件和/或软件的方法实现。
如图2所示，本申请实施例提供的节点管理方法主要包括步骤S11和S12。
S11、接收节点生命周期管理信息。
S12、基于所述节点生命周期管理信息对节点进行生命周期管理，其中，所述节点生命周期管理包括以下一个或多个：节点创建、节点弹缩和节点释放。
在一个示例性的实施方式中，所述节点生命周期管理信息来自下述一项节点的发送：
业务运营支撑系统OSS；
网络功能虚拟化编排器NFVO；
虚拟网络功能管理器VNFM，其中，所述VNFM转发NFVO发送的节点生命周期管理信息。
在一个示例性的实施方式中，所述基于所述节点生命周期管理信息对节点进行生命周期管理，包括：基于所述节点生命周期管理信息生成节点生命周期管理请求；发送所述节点生命周期管理请求至虚拟化基础设置管理器VIM，所述节点生命周期管理请求用于指示VIM对节点进行节点资源管理操作，VIM执行节点资源管理操作后生成操作结果信息；接收所述VIM反馈的操作结果信息，并转发至OSS或NFVO。
在一个示例性的实施方式中，所述节点生命周期管理请求是节点创建请求的情况下，基于所述生命周期管理请求对节点进行创建节点的生命周期管理，包括：向节点所属区域的VIM发送节点创建请求，其中，所述节点创建请求中携带节点资源信息模型；所述节点资源信息模型用于指示所述VIM创建相应的节点；所述节点资源信息模型包括以下一个或多个：节点规模，节点标识，节点资源；所述节点资源信息模型基于节点创建信息生成，其中，所述节点创建信息包括以下一个或多个：节点类型、节点规模、节点资源、节点部署；接收所述VIM反馈的节点创建完成信息，其中，所述节点创建完成信息中携带创建的节点数量和节点分配的资源。
在一个示例性的实施方式中，所述接收所述VIM反馈的节点创建完成信息之后，还包括：将所创建的节点加入集群中；更新集群信息，所述集群信息包括集群标识和该集群中所有节点的节点信息。
在一个示例性的实施方式中，更新集群信息之后，还包括：向OSS或NFVO发送节点创建成功信息，其中，所述节点创建成功信息包括集群标识以及每个集群中所有节点的节点信息。
在一个示例性的实施方式中，所述节点所属区域的VIM基于所述节点部署 确定。
在一个示例性的实施方式中，所述生命周期管理请求是节点弹缩请求的情况下，基于所述生命周期管理请求对节点进行节点弹缩的生命周期管理，包括：向节点所属区域的VIM发送节点弹缩请求，其中，所述节点弹缩请求中携带节点弹缩信息模型，所述节点弹缩信息模型包括节点弹缩规模，节点资源需求，所述节点弹缩请求用于指示所述VIM执行节点弹缩操作，节点弹缩操作完成后VIM生成节点弹缩结果信息；接收所述VIM反馈的节点弹缩结果信息。
在一个示例性的实施方式中，向节点所属区域的VIM发送节点弹缩请求之前还包括：根据节点弹缩策略确定是否发起节点弹缩请求。
在一个示例性的实施方式中，所述根据节点弹缩策略确定是否发起节点弹缩请求，包括：在节点资源不足或节点规模不足的情况下，发起节点弹出请求，其中，所述节点弹出包括增加节点资源或增加节点规模；在节点空闲资源大于业务所需资源的情况下，发起节点缩入请求，其中，所述节点缩入包括减少节点资源或减少节点规模。
在一个示例性的实施方式中，所述向所述VIM发送节点弹缩请求之前，还包括：向节点所属区域的VIM发送查询请求；所述查询请求用于指示所述VIM查询空闲资源是否满足节点资源需求；在接收到VIM发送的空闲资源满足节点资源需求的情况下，执行向所述VIM发送节点弹缩请求的操作；在接收到VIM发送的空闲资源未满足节点资源需求的情况下，更新节点弹缩规模和节点资源需求。
在一个示例性的实施方式中，接收所述VIM反馈的节点弹缩结果信息之后，还包括：在所述节点弹缩结果信息是创建新的节点的情况下，将新创建的节点加入集群中；在所述节点弹缩结果信息是增加已创建节点资源的情况下，更新集群中该已创建节点的节点信息；在所述节点弹缩结果信息是释放已创建节点的情况下，将集群中该已创建节点删除；在所述节点弹缩结果信息是减少已创建节点资源的情况下，更新集群中该已创建节点的节点信息。
在一个示例性的实施方式中，所述生命周期管理请求是节点释放请求的情况下，基于所述生命周期管理请求对节点进行释放节点的生命周期管理，包括：向节点所属区域的VIM发送节点释放请求，其中所述节点释放请求携带节点标识；所述节点释放请求用于指示所述VIM释放节点以及节点所占用的资源，节点释放操作完成后VIM生成节点释放结果信息；接收所述VIM反馈的节点释放结果信息，其中，所述节点释放结果信息中携带已释放节点标识；将集群中已释放节点删除。
在一个示例性的实施方式中，所述节点释放请求通过以下方式之一生成：
在空闲节点大于所需节点的情况下生成；
在集群中存在异常节点的情况下生成。
在一个示例性的实施方式中，所述方法还包括：
向所述VIM发送订阅请求，所述订阅请求用于指示所述VIM在设定时间内上报节点状态信息；在接收到所述VIM反馈的节点状态信息的情况下，将所述节点状态信息发送至OSS或NFVO，所述节点状态信息包括节点所属集群的集群标识、节点标识和节点资源信息。
在一个示例性的实施方式中，所述方法包括：向所述VIM发送节点状态查询请求，所述节点状态查询请求用于指示所述VIM上报节点状态信息。
在一个示例性的实施方式中，所述方法包括：接收节点异常信息；其中，所述节点异常信息由所述VIM在集群中存在异常节点的情况下反馈；向所述VIM发送节点创建请求，所述节点创建请求中携带节点资源信息模型；所述节点资源信息模型中的节点资源与异常节点的节点资源信息模型的节点资源相同；向OSS或NFVO发送节点异常状态信息，所述节点异常状态信息中携带新创建的节点信息。
图3是本申请实施例提供的节点管理装置的结构示意图，本实施例提供的节点管理装置主要适用于NFV系统中对节点的生命周期进行管理的情况，所述节点管理装置可以由硬件和/或软件的方法实现。
如图3所示，本申请实施例提供的节点管理装置主要包括接收模块21和管理模块22。
接收模块21，被设置为接收节点生命周期管理信息；
管理模块22，被设置为基于所述节点生命周期管理信息对节点进行生命周期管理，其中，所述节点生命周期管理包括以下一个或多个：节点创建、节点弹缩和节点释放。
在一个示例性的实施方式中，所述节点生命周期管理信息来自下述一项节点的发送：
业务运营支撑系统OSS；
网络功能虚拟化编排器NFVO；
虚拟网络功能管理器VNFM，其中，所述VNFM转发NFVO发送的节点生命周期管理信息。
在一个示例性的实施方式中，管理模块22，被设置为基于所述节点生命周期管理信息生成节点生命周期管理请求；发送所述节点生命周期管理请求至虚拟化基础设置管理器VIM，所述节点生命周期管理请求用于指示VIM对节点进行节点资源管理操作，VIM执行节点资源管理操作后生成操作结果信息；接收所述VIM反馈的操作结果信息，并转发至OSS或NFVO。
在一个示例性的实施方式中，管理模块22，被设置为所述节点生命周期管理请求是节点创建请求的情况下，基于所述生命周期管理请求对节点进行创建节点的生命周期管理，在一实施例中，管理模块22，被设置为向节点所属区域的VIM发送节点创建请求，其中，所述节点创建请求中携带节点资源信息模型；所述节点资源信息模型用于指示所述VIM创建相应的节点；所述节点资源信息模型包括以下一个或多个：节点规模，节点标识，节点资源；所述节点资源信息模型基于节点创建信息生成，其中，所述节点创建信息包括以下一个或多个：节点类型、节点规模、节点资源、节点部署；接收所述VIM反馈的节点创建完成信息，其中，所述节点创建完成信息中携带创建的节点数量和节点分配的资源。
在一个示例性的实施方式中，管理模块22，被设置为在所述接收所述VIM反馈的节点创建完成信息之后，将所创建的节点加入集群中；更新集群信息，所述集群信息包括集群标识和该集群中所有节点的节点信息。
在一个示例性的实施方式中，管理模块22，被设置为在更新集群信息之后，向OSS或NFVO发送节点创建成功信息，其中，所述节点创建成功信息包括集群标识以及每个集群中所有节点的节点信息。
在一个示例性的实施方式中，所述节点所属区域的VIM基于所述节点部署确定。
在一个示例性的实施方式中，管理模块22，被设置为在所述生命周期管理请求是节点弹缩请求的情况下，基于所述生命周期管理请求对节点进行节点弹缩的生命周期管理，在一实施例中，管理模块22，被设置为向节点所属区域的VIM发送节点弹缩请求，其中，所述节点弹缩请求中携带节点弹缩信息模型，所述节点弹缩信息模型包括节点弹缩规模，节点资源需求，所述节点弹缩请求用于指示所述VIM执行节点弹缩操作，节点弹缩操作完成后VIM生成节点弹缩结果信息；接收所述VIM反馈的节点弹缩结果信息。
在一个示例性的实施方式中，管理模块22，被设置为在向节点所属区域的VIM发送节点弹缩请求之前，根据节点弹缩策略确定是否发起节点弹缩请求。
在一个示例性的实施方式中，管理模块22，被设置为在节点资源不足或节 点规模不足的情况下，发起节点弹出请求，其中，所述节点弹出包括增加节点资源或增加节点规模；在节点空闲资源大于业务所需资源的情况下，发起节点缩入请求，其中，所述节点缩入包括减少节点资源或减少节点规模。
在一个示例性的实施方式中，管理模块22，被设置为在向所述VIM发送节点弹缩请求之前，向节点所属区域的VIM发送查询请求；所述查询请求用于指示所述VIM查询空闲资源是否满足节点资源需求；在接收到VIM发送的空闲资源满足节点资源需求的情况下，执行向所述VIM发送节点弹缩请求的操作；在接收到VIM发送的空闲资源未满足节点资源需求的情况下，更新节点弹缩规模和节点资源需求。
在一个示例性的实施方式中，管理模块22，被设置为在接收所述VIM反馈的节点弹缩结果信息之后，在所述节点弹缩结果信息是创建新的节点的情况下，将新创建的节点加入集群中；在所述节点弹出结缩信息是增加已创建节点资源的情况下，更新集群中该已创建节点的节点信息；在所述节点弹缩结果信息是释放已创建节点的情况下，将集群中该已创建节点删除；在所述节点弹缩结果信息是减少已创建节点资源的情况下，更新集群中该已创建节点的节点信息。
在一个示例性的实施方式中，管理模块22，被设置为在所述生命周期管理请求是节点释放请求的情况下，基于所述生命周期管理请求对节点进行释放节点的生命周期管理，在一实施例中，管理模块22，被设置为向节点所属区域的VIM发送节点释放请求，其中，所述节点释放请求携带节点标识；所述节点释放请求用于指示所述VIM释放节点以及节点所占用的资源，节点释放操作完成后VIM生成节点释放结果信息；接收所述VIM反馈的节点释放结果信息，其中，所述节点释放结果信息中携带已释放节点标识；将集群中已释放节点删除。
在一个示例性的实施方式中，所述节点释放请求通过以下方式之一生成：
在空闲节点大于所需节点的情况下生成；
在集群中存在异常节点的情况下生成。
在一个示例性的实施方式中，管理模块22，被设置为向所述VIM发送订阅请求，所述订阅请求用于指示所述VIM在设定时间内上报节点状态信息；在接收到所述VIM反馈的节点状态信息的情况下，将所述节点状态信息发送至OSS或NFVO，所述节点状态信息包括节点所属集群的集群标识、节点标识和节点资源信息。
在一个示例性的实施方式中，管理模块22，被设置为向所述VIM发送节点状态查询请求，所述节点状态查询请求用于指示所述VIM上报节点状态信息。
在一个示例性的实施方式中，管理模块22，被设置为接收节点异常信息； 其中，所述节点异常信息由所述VIM在集群中存在异常节点的情况下反馈；向所述VIM发送节点创建请求，所述节点创建请求中携带节点资源信息模型；所述节点资源信息模型中的节点资源与异常节点的节点资源信息模型的节点资源相同；向OSS或NFVO发送节点异常状态信息，所述节点异常状态信息中携带新创建的节点信息。
图4是本申请实施例提供的网络功能虚拟化系统的结构示意图，如图4所示，所述系统包括业务运营支撑系统OSS、网络功能虚拟化编排器NFVO、虚拟化基础设置管理器VIM和集群管理器CNM。
其中，S31、所述NFVO或OSS向所述CNM发送节点生命周期管理信息。
S32、所述CNM基于节点生命周期管理信息生成节点生命周期管理请求。
S33、所述CNM向所述VIM发送节点生命周期管理请求。
S34、所述VIM基于所述节点生命周期管理请求对节点进行生命周期管理操作。
在一个示例性的实施方式中，在所述VIM对节点进行管理操作之后生成节点的操作结果信息，并向所述CNM发送节点的操作结果信息；所述CNM将所述节点的操作结果信息转发至所述NFVO或所述OSS。
在一个示例性的实施方式中，在所述节点生命周期管理请求是节点创建请求的情况下，
所述CNM基于所述节点创建信息生成节点资源信息模型，其中，所述节点创建信息包括以下一个或多个：节点类型、节点规模、节点资源、节点部署，所述节点资源信息模型包括以下一个或多个：节点规模，节点标识，节点资源；
所述CNM向节点所属区域的VIM发送节点创建请求，其中，所述节点创建请求中携带节点资源信息模型；
所述VIM基于所述节点资源信息模型创建相应的节点；
所述CNM接收所述VIM反馈的节点创建完成信息，并将该节点加入到集群中。其中，所述节点创建完成信息中携带创建的节点数量和节点分配的资源。
在一个示例性的实施方式中，所述生命周期管理请求是节点弹缩请求的情况下，所述方法还包括：
所述CNM向所述VIM发送节点弹缩请求，其中，所述节点弹缩请求中携带节点弹缩信息模型，所述节点弹缩信息模型包括节点弹缩规模，节点资源需求；
所述VIM基于节点弹缩请求执行节点弹缩操作并生成节点弹缩结果信息；
所述CNM接收所述VIM反馈的节点弹缩结果信息，并更新节点所在的集群信息。
在一个示例性的实施方式中，所述CNM向节点所属区域的VIM发送查询请求；
所述VIM基于所述查询请求查询空闲资源是否满足节点资源需求，并将查询结果反馈至所述CNM；
所述CNM在接收到VIM发送的空闲资源满足节点资源需求的情况下，向所述VIM发送节点弹缩请求；
所述CNM在接收到VIM发送的空闲资源未满足节点资源需求的情况下，更新节点弹缩规模和节点资源需求。
在一个示例性的实施方式中，在所述生命周期管理请求是节点释放请求的情况下，
所述CNM向节点所属区域的VIM发送节点释放请求，其中，所述节点释放请求携带节点标识；
所述VIM基于所述节点释放请求释放节点以及节点所占用的资源并生成节点释放结果信息；
所述CNM接收所述VIM反馈的节点释放结果信息，其中，所述节点释放结果信息中携带已释放节点标识；
所述CNM将集群中已释放节点删除。
在一个示例性的实施方式中，所述CNM向所述VIM发送订阅请求；
所述VIM基于所述订阅请求在设定时间内上报节点状态信息；
所述CNM在接收到所述VIM反馈的节点状态信息的情况下，将所述节点状态信息发送至OSS或NFVO，所述节点状态信息包括节点所属集群的集群标识、节点标识和节点资源信息。
在一个示例性的实施方式中，所述VIM在集群中存在异常节点的情况下，生成节点异常信息并反馈至所述CNM；
所述CNM接收节点异常信息，并向所述VIM发送节点创建请求，所述节点创建请求中携带节点资源信息模型；所述节点资源信息模型中的节点资源与异常节点的节点资源信息模型的节点资源相同；
所述VIM基于所述节点创建请求创建新的节点，替换异常节点；
所述CNM向OSS或NFVO发送节点异常状态信息，所述节点异常状态信 息中携带新创建的节点信息。
在一个应用性实例中，本申请中，新定义一个集群管理功能CNM(Cluster Node Manager)，该功能可以是物理的，也可以是逻辑的。如果是逻辑功能，可以嵌入到NFVO，VNFM，VIM等功能实体中，如果是物理功能，可以作为一个单独的实体设置在网络功能虚拟化系统中。图5是本申请实施例提供的具有集群管理功能的NFV系统的结构图。
如图5所示，集群管理功能CNM用于负责节点生命周期管理，包括节点创建、节点弹缩、节点释放等功能。
集群管理功能CNM也负责集群节点的更新，将新创建的节点加到某个集群，当节点更新时对相关的节点所在的集群进行更新，当节点释放时从相应的节点中删除该节点。
集群管理功能CNM可以与OSS/NFVO进行交互，可从OSS/NFVO获取相关节点的创建信息、更新信息及释放信息，以及将节点的已创建、已更新、已释放信息及时上报给OSS/NFVO。
集群管理功能CNM可以与VIM进行交互，CNM可以根据节点部署信息发现所在部署区域的VIM，向该VIM请求、更新及释放节点。VIM创建成功后，将节点已创建、已更新、已释放的信息及时通知给CNM。
集群管理功能CNM可以与VNFM进行交互，从VNFM获取节点的创建模板信息。
当节点异常时，VIM检测到节点异常会通知给CNM，CNM会及时上报给OSS/NFVO节点异常信息。CNM会请求VIM创建一个完全替代的节点来取代异常节点。
在一个应用性实例中，提供一种节点创建的流程，图6是本申请实施例提供的一种节点创建方法的流程图，如图6所示，本实施例中，OSS/NFVO根据网络规划、第三方应用或运营商需求发起Node创建，携带Node创建信息模型。CNM收到创建Node请求后，解析Node创建信息模型。CNM生成Node资源信息模型，并根据Node资源信息模型中的Node部署信息选择VIM，将节点创建请求及Node资源信息模型发送给选择的VIM，请求VIM创建Node。VIM成功创建Node后返回节点成功创建信息，CNM将已创建的Node加入某Cluster Node集群中，并通知OSS/NFVO创建成功所请求的Node。
S101，运营商根据用户需求及网络规划进行规划设计，将所需的Node创建信息模型，包括Node类型，Node规模(Node数量)、Node资源需求、Node部署等需求采用网络功能描述(虚拟网络功能描述符/物理网络功能描述符(Virtualized Network Function Descriptor/Physical Network Function Descriptor，VNFD/PNFD))进行规划设计。
所述Node创建信息模型也可采用新定义的Node功能描述模板进行规划设计。Node功能描述模板用于OSS/NFVO向CNM传递Node创建信息。
S102、OSS/NFVO直接将Node创建信息模型发送给CNM，也可以通过VNFM将Node创建信息模型转发给CNM；其中，所述VNFM转发NFVO发送的创建信息模型。
S103，CNM解析接收到的Node创建信息模型，解析网络功能描述或Node功能描述中相关的Node信息，生成Node资源信息模型，Node资源信息模型包含Node规模，Node标识，Node所需资源(计算、存储、网络)等与资源相关的信息。
S104，CNM根据Node部署信息选择所在区域的VIM，向所述VIM发起Node创建请求，所述Node创建请求携带Node资源信息模型，包含Node规模，Node标识，Node所需资源(计算、存储、网络)，并根据Node部署信息发送给所在部署区域的VIM/PIM。
S105，VIM根据Node资源信息模型，创建相应的Node，并返回Node创建完成信息。携带信息不限于创建的Node的节点数，Node所分配的资源(计算资源、存储资源、网络资源)。
S106，CNM将创建好的Node加入Cluster集群中，并更新Cluster集群信息。Cluster Node信息中包含Cluster集群ID，该集群中所有Node的信息，如Node标识，Node资源，node状态等。
S107，CNM向OSS/NFVO通知Node已建立完成，携带Cluster Node创建成功信息，包含Cluster Node ID，及每个Cluster Node集群所属的已创建Node的标识、资源、部署位置等信息。
在一个应用性实例中，本实施例描述了Node弹缩流程，图7是本申请实施例提供的一种节点弹缩方法的流程图，如图7所示，OSS/NFVO可发起Node弹缩请求，CNM也可主动发起node弹缩请求。CNM在收到弹缩请求后，先向选择的VIM查询资源是否满足Node弹缩需求，如果不满足，则需要OSS/NFVO更新Node弹缩需求，或CNM主动更新Node弹缩需求，使得VIM的资源能满 足弹缩需求。
CNM向VIM发起Node弹缩请求，VIM执行Node弹缩操作，弹缩有两种，一种是Node增加或减少资源，一种是新增node或释放已创建的Node。当Node弹缩成功后，CNM更新Cluster Node集群，并将弹缩结果上报给OSS/NFVO。
S201，Node弹缩请求可由OSS/NFVO触发或集群节点管理功能CNM主动发起。OSS/NFVO可根据Node弹缩策略，如根据预设条件，Node已使用数量大于一定的比率(如80％)就进行触发；或者来自第三方对Node的使用需求，如来自Kubernetes(K8S)的Node激活需求。
集群节点管理系统CNM也可以根据Node弹缩的策略主动发起Node的弹缩，如现存的Node不满足业务要求。
当Node资源不足，Node规模不足，则发起Node弹出，包括增加Node资源及增加Node规模两种方式；若Node空闲资源大于业务所需资源，则发起Node缩入，包括减少Node资源及减少Node规模2种方式。
S202，CNM收到OSS/NFVO发起的Node弹缩请求，或收到经VNFM转发的Node弹缩请求，请求消息中携带Cluster集群标识，Node弹缩信息模型，Node弹缩信息模型包括Node弹缩规模，Node所需的资源等信息。
若是CNM根据弹缩策略主动发起Node弹缩操作时，可以主动生成Node弹缩信息模型，包括Node弹缩规模，Node所需的资源等信息。
S203，CNM发起Node弹缩操作前，CNM根据Node的部署信息向所在区域的VIM查询空闲资源是否满足Node资源需求，如果不满足资源需求，则反馈给OSS/NFVO，OSS/NFVO更新Node的弹缩规模及弹缩资源。
若是CNM主动发起的Node弹缩操作，由CNM主动调整Node的弹缩规模及弹缩资源。
S204、CNM向VIM发起弹缩请求，VIM执行Node弹缩操作：Node弹出操作时，VIM根据Node弹缩信息新生成Node，并分配所需的资源，或增加已创建的Node资源；缩入操作时，减少已创建Node的资源，或释放相应的Node，包括释放原来已分配的资源。
S205，VIM将Node弹缩结果通知给CNM。
S206，对于Node弹出操作，CNM将成功新弹出的Node加入Cluster Node集群，若弹出的是现有Node的资源(Node资源增加)，则在集群信息中更新相关Node信息；对于Node缩入操作，CNM将成功缩入的Node在集群中删除，若缩入的是现有Node的资源(Node资源减少)，则在集群信息中更新相关Node 信息。
S207，CNM将Node的弹缩结果上报信息给OSS/NFVO。另外，可选的上报Cluster Node的更新信息，更新信息中包括Cluster集群id，Node更新信息(如id，资源)。
在一个应用性实例中，本实施例描述了Node释放流程，图8是本申请实施例提供的一种节点释放方法的流程图。如图8所示，该实施例中，OSS/NFVO或CNM根据Node的实际需求，当空闲的Node远远大于所需要的Node时，可释放一部分Node以节省VIM资源。
OSS/NFVO发起Node释放请求，或CNM根据策略发起Node释放请求，VIM根据Node id释放已创建的Node及其占用的资源。当Node释放成功后，CNM需要更新Cluster集群信息，删除其中已释放的Node，并将Node已释放的结果通知给OSS/NFVO。
S301，Node的释放可由OSS/NFVO触发或CNM主动发起。OSS/NFVO可根据业务部署需求，如用于5G的某网络切片服务因服务到期终止，则用于该网络服务的Node，开源应用可通知进行Node释放。
集群节点管理系统CNM也可以根据Node释放的策略主动发起Node的释放，如现存空闲的Node已远超业务的需求，或某Cluster集群中的Node出现异常。
S302，CNM收到OSS/NFVO发起的Node释放请求，或经VNFM转发的Node释放请求，请求消息种携带Cluster集群标识及Node标识。
CNM也可根据Node释放策略主动发起Node释放操作，用于释放Cluster集群中空闲的或异常的Node。
S303、CNM向Node所在区域的VIM发起Node请求，携带Node标识。
S304、VIM释放Node及Node所占用的资源，并将Node释放结果通知给CNM。
S305、CNM更新集群信息，将成功释放的Node在集群中删除。
S306、CNM将Node的已释放结果信息上报给OSS/NFVO。另外，可选的上报Cluster Node的更新信息，更新信息中包括Cluster集群id，Node更新信息(如id，资源)。
在一个应用性实例中，本实施例描述了Node状态监控并上报的流程，图9 是本申请实施例提供的一种Node状态监控并上报的方法的流程图，如图9所示，该实施例中，CNM可向VIM订阅或动态查询Node状态信息，并将Node信息发送给OSS/NFVO。当Node状态异常时，VIM向CNM主动上报，CNM在集群信息中寻找替代的Node，如果没有可替代的空闲Node，CNM向VIM发起创建Node，用以替换异常的Node，并向OSS/NFVO上报Node异常信息，并将已创建可替代的Node信息同时上报给OSS/NFVO。
S401，CNM向VIM动态查询Node状态，可向VIM订阅定期上报Node状态信息，也可动态主动查询Node状态信息。查询消息携带Node的标识。
S402，VIM根据订阅机制，向CNM定期发送Node状态信息，或收到CNM的查询请求后返回Node状态。
S403，CNM将Node的状态上报给OSS/NFVO，或通过VNFM转发给OSS/NFVO。消息中携带Cluster集群标识、Node的ID、Node的状态(空闲资源及占用资源)等信息。
S404，当Node出现异常时，VIM会向CNM上报Node异常状态信息。
S405，CNM查找Cluster集群中是否有空闲的Node可以替代该Node，如果没有，则向VIM请求创建一个与异常Node同等资源的新Node，该Node用于替换状态异常的Node。
S406、CNM向OSS/NFVO上报Node异常状态信息，并在通知消息中给出可替换的Node标识。
在上实施例的基础上，本申请实施例还提供一种集群管理器，图10为本申请实施例提供的一种集群管理器的结构示意图，如图10所示，该集群管理器包括处理器100、存储器101、输入装置102和输出装置103；集群管理器中处理器100的数量可以是一个或多个，图10中以一个处理器100为例；集群管理器中的处理器100、存储器101、输入装置102和输出装置103可以通过总线或其他方式连接，图10中以通过总线连接为例。
存储器101作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序以及模块，如本申请实施例中的节点管理方法对应的程序指令/模块(例如，节点管理装置中的接收模块21和管理模块22)。处理器100通过运行存储在存储器101中的软件程序、指令以及模块，从而执行集群管理器的各种功能应用以及数据处理，即实现本申请实施例中提供的任一方法。
存储器101可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据终端的使 用所创建的数据等。此外，存储器101可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器101可包括相对于处理器100远程设置的存储器，这些远程存储器可以通过网络连接至集群管理器。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
输入装置102可用于接收输入的数字或字符信息，以及产生与集群管理器的用户设置以及功能控制有关的键信号输入。输出装置103可包括显示屏等显示设备。
在上述实施例的基础上，本申请实施例还提供一种包含计算机可执行指令的存储介质，所述计算机可执行指令在由计算机处理器执行时用于执行本申请实施例中提供的任一方法。
如，在执行本申请实施例中提供提供的节点管理方法的情况下，该方法包括：
接收节点生命周期管理信息；
基于所述节点生命周期管理信息对节点进行生命周期管理，其中，所述节点生命周期管理包括以下一个或多个：节点创建、节点弹缩和节点释放。
本申请实施例所提供的一种包含计算机可执行指令的存储介质，其计算机可执行指令不限于如上所述的方法操作，还可以执行本申请任意实施例所提供的节点管理方法中的相关操作.
通过以上关于实施方式的描述，所属领域的技术人员可以清楚地了解到，本申请可借助软件及必需的通用硬件来实现，也可以通过硬件实现。基于这样的理解，本申请可以以软件产品的形式体现出来，该计算机软件产品可以存储在计算机可读存储介质中，如计算机的软盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、闪存(FLASH)、硬盘或光盘等，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述的方法。
值得注意的是，上述节点管理装置的实施例中，所包括的各个单元和模块只是按照功能逻辑进行划分的，但并不局限于上述的划分，只要能够实现相应的功能即可；另外，各功能单元的具体名称也只是为了便于相互区分，并不用于限制本申请的保护范围。
以上所述，仅为本申请的示例性实施例而已，并非用于限定本申请的保护范围。
本领域内的技术人员应明白，术语用户终端涵盖任何适合类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(ROM)、随机访问存储器(RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disk，CD))等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FPGA)以及基于多核处理器架构的处理器。

Claims (28)

  1. 一种节点管理方法，包括：
    接收节点生命周期管理信息；
    基于所述节点生命周期管理信息对节点进行生命周期管理，其中，所述节点生命周期管理包括以下至少一个：节点创建、节点弹缩和节点释放。
  2. 根据权利要求1所述的方法，其中，所述节点生命周期管理信息来自下述一项节点的发送：
    业务运营支撑系统OSS；
    网络功能虚拟化编排器NFVO；
    虚拟网络功能管理器VNFM，其中，所述VNFM转发NFVO发送的节点生命周期管理信息。
  3. 根据权利要求1所述的方法，其中，所述基于所述节点生命周期管理信息对节点进行生命周期管理，包括：
    基于所述节点生命周期管理信息生成节点生命周期管理请求；
    发送所述节点生命周期管理请求至虚拟化基础设置管理器VIM，所述节点生命周期管理请求用于指示所述VIM对所述节点进行节点资源管理操作，以及所述VIM执行所述节点资源管理操作后生成操作结果信息；
    接收所述VIM反馈的操作结果信息，并将所述操作结果信息转发至OSS或NFVO。
  4. 根据权利要求3所述的方法，其中，在所述节点生命周期管理请求是节点创建请求的情况下，基于所述节点生命周期管理请求对节点进行创建节点的生命周期管理，包括：
    向节点所属区域的VIM发送所述节点创建请求，其中，所述节点创建请求中携带节点资源信息模型；所述节点资源信息模型用于指示所述VIM创建节点；所述节点资源信息模型包括以下至少一个：节点规模，节点标识，节点资源；所述节点资源信息模型基于节点创建信息生成，其中，所述节点创建信息包括以下至少一个：节点类型、节点规模、节点资源、节点部署；
    接收所述节点所属区域的VIM反馈的节点创建完成信息，其中，所述节点创建完成信息中携带创建的节点数量和节点分配的资源。
  5. 根据权利要求4所述的方法，其中，在所述接收所述节点所属区域的VIM反馈的节点创建完成信息之后，还包括：
    将所创建的节点加入集群中；
    更新集群信息，所述集群信息包括集群标识和所述集群中所有节点的节点信息。
  6. 根据权利要求5所述的方法，其中，在所述更新集群信息之后，还包括：
    向所述OSS或所述NFVO发送节点创建成功信息，其中，所述节点创建成功信息包括所述集群标识以及每个集群中所有节点的节点信息。
  7. 根据权利要求4所述的方法，其中，所述节点所属区域的VIM基于所述节点部署确定。
  8. 根据权利要求3所述的方法，其中，在所述节点生命周期管理请求是节点弹缩请求的情况下，基于所述节点生命周期管理请求对节点进行节点弹缩的生命周期管理，包括：
    向节点所属区域的VIM发送所述节点弹缩请求，其中，所述节点弹缩请求中携带节点弹缩信息模型，所述节点弹缩信息模型包括节点弹缩规模，节点资源需求，所述节点弹缩请求用于指示所述VIM执行节点弹缩操作，以及在所述节点弹缩操作完成后所述VIM生成节点弹缩结果信息；
    接收所述节点所属区域的VIM反馈的节点弹缩结果信息。
  9. 根据权利要求8所述的方法，其中，在所述向节点所属区域的VIM发送所述节点弹缩请求之前还包括：
    根据节点弹缩策略确定是否发起所述节点弹缩请求。
  10. 根据权利要求9所述的方法，其中，所述根据节点弹缩策略确定是否所述发起节点弹缩请求，包括：
    在节点资源不足或节点规模不足的情况下，发起节点弹出请求，其中，节点弹出包括增加所述节点资源或增加所述节点规模；
    在节点空闲资源大于业务所需资源的情况下，发起节点缩入请求，其中，节点缩入包括减少所述节点资源或减少所述节点规模。
  11. 根据权利要求8所述的方法，其中，在所述向所述节点所属区域的VIM发送所述节点弹缩请求之前，还包括：
    向节点所属区域的VIM发送查询请求，所述查询请求用于指示所述VIM查询空闲资源是否满足节点资源需求；
    在接收到所述节点所属区域的VIM发送的空闲资源满足所述节点资源需求的情况下，执行向所述VIM发送所述节点弹缩请求的操作；
    在接收到所述VIM发送的空闲资源未满足所述节点资源需求的情况下，更 新节点弹缩规模和节点资源需求。
  12. 根据权利要求8所述的方法，其中，在所述接收所述节点所属区域的VIM反馈的节点弹缩结果信息之后，还包括：
    在所述节点弹缩结果信息是创建新的节点的情况下，将新创建的节点加入集群中；
    在所述节点弹缩结果信息是增加已创建节点资源的情况下，更新集群中已创建节点的节点信息；
    在所述节点弹缩结果信息是释放已创建节点的情况下，将集群中所述已创建节点删除；
    在所述节点弹缩结果信息是减少已创建节点资源的情况下，更新集群中已创建节点的节点信息。
  13. 根据权利要求3所述的方法，其中，在所述节点生命周期管理请求是节点释放请求的情况下，基于所述节点生命周期管理请求对节点进行释放节点的生命周期管理，包括：
    向节点所属区域的VIM发送所述节点释放请求，其中，所述节点释放请求携带节点标识；所述节点释放请求用于指示所述VIM释放节点以及节点所占用的资源，以及在节点释放操作完成后所述VIM生成节点释放结果信息；
    接收所述VIM反馈的节点释放结果信息，其中，所述节点释放结果信息中携带已释放节点标识；
    将集群中已释放节点删除。
  14. 根据权利要求13所述的方法，其中，所述节点释放请求通过以下方式之一生成：
    在空闲节点大于所需节点的情况下生成；
    在集群中存在异常节点的情况下生成。
  15. 根据权利要求1所述的方法，还包括：
    向VIM发送订阅请求，所述订阅请求用于指示所述VIM在设定时间内上报节点状态信息；
    在接收到所述VIM反馈的节点状态信息的情况下，将所述节点状态信息发送至OSS或NFVO，所述节点状态信息包括节点所属集群的集群标识、节点标识和节点资源信息。
  16. 根据权利要求15所述的方法，还包括：
    向所述VIM发送节点状态查询请求，所述节点状态查询请求用于指示所述VIM上报所述节点状态信息。
  17. 根据权利要求15所述的方法，还包括：
    接收节点异常信息，其中，所述节点异常信息由所述VIM在集群中存在异常节点的情况下反馈；
    向所述VIM发送节点创建请求，所述节点创建请求中携带节点资源信息模型；所述节点资源信息模型中的节点资源与所述异常节点的节点资源信息模型的节点资源相同；
    向所述OSS或所述NFVO发送节点异常状态信息，所述节点异常状态信息中携带新创建的节点信息。
  18. 一种节点管理装置，包括：
    接收模块，被设置为接收节点生命周期管理信息；
    管理模块，被设置为基于所述节点生命周期管理信息对节点进行生命周期管理，其中，所述节点生命周期管理包括以下至少一个：节点创建、节点弹缩和节点释放。
  19. 一种集群管理器，包括：
    一个或多个处理器；
    存储器，设置为存储一个或多个程序；
    所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-17中任一项所述的节点管理方法。
  20. 一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1-17中任一项所述的节点管理方法。
  21. 一种网络功能虚拟化系统，包括：业务运营支撑系统OSS、网络功能虚拟化编排器NFVO、虚拟化基础设置管理器VIM和集群管理器CNM；
    所述NFVO或所述OSS向所述CNM发送节点生命周期管理信息；
    所述CNM基于所述节点生命周期管理信息生成节点生命周期管理请求，并向所述VIM发送所述节点生命周期管理请求；
    所述VIM基于所述节点生命周期管理请求对节点进行生命周期管理操作。
  22. 根据权利要求21中所述的系统，还包括：
    在所述VIM对节点进行所述生命周期管理操作之后生成节点的操作结果信 息，并向所述CNM发送所述节点的操作结果信息；
    所述CNM将所述节点的操作结果信息转发至所述NFVO或所述OSS。
  23. 根据权利要求21中所述的系统，其中，在所述节点生命周期管理请求是节点创建请求的情况下，还包括：
    所述CNM基于节点创建信息生成节点资源信息模型，其中，所述节点创建信息包括以下至少一个：节点类型、节点规模、节点资源、节点部署，所述节点资源信息模型包括以下至少一个：节点规模，节点标识，节点资源；
    所述CNM向节点所属区域的VIM发送所述节点创建请求，其中，所述节点创建请求中携带所述节点资源信息模型；
    所述VIM基于所述节点资源信息模型创建节点；
    所述CNM接收所述VIM反馈的节点创建完成信息，并将所创建的节点加入到集群中，其中，所述节点创建完成信息中携带创建的节点数量和节点分配的资源。
  24. 根据权利要求21中所述的系统，其中，在所述节点生命周期管理请求是节点弹缩请求的情况下，还包括：
    所述CNM向所述VIM发送所述节点弹缩请求，其中，所述节点弹缩请求中携带节点弹缩信息模型，所述节点弹缩信息模型包括节点弹缩规模，节点资源需求；
    所述VIM基于所述节点弹缩请求执行节点弹缩操作并生成节点弹缩结果信息；
    所述CNM接收所述VIM反馈的节点弹缩结果信息，并更新节点所在的集群信息。
  25. 根据权利要求24中所述的系统，还包括：
    所述CNM向节点所属区域的VIM发送查询请求；
    所述VIM基于所述查询请求查询空闲资源是否满足节点资源需求，并将查询结果反馈至所述CNM；
    所述CNM在接收到所述VIM发送的空闲资源满足所述节点资源需求的情况下，向所述VIM发送所述节点弹缩请求；
    所述CNM在接收到所述VIM发送的空闲资源未满足所述节点资源需求的情况下，更新节点弹缩规模和节点资源需求。
  26. 根据权利要求21所述的系统，还包括：在所述节点生命周期管理请求是 节点释放请求的情况下，
    所述CNM向节点所属区域的VIM发送所述节点释放请求，其中，所述节点释放请求携带节点标识；
    所述VIM基于所述节点释放请求释放节点以及节点所占用的资源并生成节点释放结果信息；
    所述CNM接收所述VIM反馈的节点释放结果信息，其中，所述节点释放结果信息中携带已释放节点标识；
    所述CNM将集群中已释放节点删除。
  27. 根据权利要求21所述的系统，还包括：
    所述CNM向所述VIM发送订阅请求；
    所述VIM基于所述订阅请求在设定时间内上报节点状态信息；
    所述CNM在接收到所述VIM反馈的节点状态信息的情况下，将所述节点状态信息发送至所述OSS或所述NFVO，所述节点状态信息包括节点所属集群的集群标识、节点标识和节点资源信息。
  28. 根据权利要求21所述的系统，还包括：
    所述VIM在集群中存在异常节点的情况下，生成节点异常信息并将所述节点异常信息反馈至所述CNM；
    所述CNM接收所述节点异常信息，并向所述VIM发送节点创建请求，所述节点创建请求中携带节点资源信息模型；所述节点资源信息模型中的节点资源与所述异常节点的节点资源信息模型的节点资源相同；
    所述VIM基于所述节点创建请求创建新的节点，替换所述异常节点；
    所述CNM向所述OSS或所述NFVO发送节点异常状态信息，所述节点异常状态信息中携带新创建的节点信息。
PCT/CN2020/123533 2019-12-02 2020-10-26 节点管理方法、装置、设备、存储介质和系统 WO2021109750A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020227022357A KR20220103796A (ko) 2019-12-02 2020-10-26 노드 관리 방법, 장치, 디바이스, 저장 매체 및 시스템
US17/779,767 US20220413937A1 (en) 2019-12-02 2020-10-26 Node management method, device and apparatus, storage medium, and system
EP20895097.2A EP4071609A4 (en) 2019-12-02 2020-10-26 NODE MANAGEMENT APPARATUS, DEVICE AND METHOD, STORAGE MEDIUM AND SYSTEM
JP2022532127A JP7438355B2 (ja) 2019-12-02 2020-10-26 ノード管理方法、装置、機器、記憶媒体及びシステム

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911216078.6 2019-12-02
CN201911216078.6A CN111090495A (zh) 2019-12-02 2019-12-02 节点管理方法、装置、设备、存储介质和系统

Publications (1)

Publication Number Publication Date
WO2021109750A1 true WO2021109750A1 (zh) 2021-06-10

Family

ID=70393829

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/123533 WO2021109750A1 (zh) 2019-12-02 2020-10-26 节点管理方法、装置、设备、存储介质和系统

Country Status (6)

Country Link
US (1) US20220413937A1 (zh)
EP (1) EP4071609A4 (zh)
JP (1) JP7438355B2 (zh)
KR (1) KR20220103796A (zh)
CN (1) CN111090495A (zh)
WO (1) WO2021109750A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111090495A (zh) * 2019-12-02 2020-05-01 中兴通讯股份有限公司 节点管理方法、装置、设备、存储介质和系统
EP4187879A4 (en) * 2020-09-24 2023-11-22 Samsung Electronics Co., Ltd. METHOD AND APPARATUS FOR OFFLOADING HARDWARE TO A SOFTWARE PACKAGE
CN112241342A (zh) * 2020-10-22 2021-01-19 浪潮云信息技术股份公司 一种实现容器云节点自治的方法及系统
CN115473802B (zh) * 2022-09-13 2024-02-23 重庆紫光华山智安科技有限公司 节点管理方法、系统、设备及存储介质
CN117707609B (zh) * 2024-02-06 2024-04-30 云账户技术(天津)有限公司 一种基于容器编排管理工具管理脚本任务的方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160335111A1 (en) * 2014-02-24 2016-11-17 Hewlett-Packard Development Company, L.P. Virtual network function management with deactivated virtual machines
CN106375101A (zh) * 2015-07-20 2017-02-01 华为技术有限公司 一种生命周期管理方法及装置
CN107819598A (zh) * 2016-09-13 2018-03-20 中兴通讯股份有限公司 一种管理网络功能节点的方法及装置
CN108628660A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 一种虚拟机扩缩容方法及虚拟管理设备
CN109947557A (zh) * 2017-12-20 2019-06-28 慧与发展有限责任合伙企业 用于云平台的分布式生命周期管理
CN111090495A (zh) * 2019-12-02 2020-05-01 中兴通讯股份有限公司 节点管理方法、装置、设备、存储介质和系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017018435A1 (ja) * 2015-07-27 2017-02-02 日本電気株式会社 リソース監視装置、仮想ネットワークファンクション管理システム、リソース監視方法及びプログラム
US11397605B2 (en) * 2017-02-01 2022-07-26 Nec Corporation Management system, management apparatus, management method, and program

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160335111A1 (en) * 2014-02-24 2016-11-17 Hewlett-Packard Development Company, L.P. Virtual network function management with deactivated virtual machines
CN106375101A (zh) * 2015-07-20 2017-02-01 华为技术有限公司 一种生命周期管理方法及装置
CN107819598A (zh) * 2016-09-13 2018-03-20 中兴通讯股份有限公司 一种管理网络功能节点的方法及装置
CN108628660A (zh) * 2017-03-24 2018-10-09 华为技术有限公司 一种虚拟机扩缩容方法及虚拟管理设备
CN109947557A (zh) * 2017-12-20 2019-06-28 慧与发展有限责任合伙企业 用于云平台的分布式生命周期管理
CN111090495A (zh) * 2019-12-02 2020-05-01 中兴通讯股份有限公司 节点管理方法、装置、设备、存储介质和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4071609A4 *

Also Published As

Publication number Publication date
KR20220103796A (ko) 2022-07-22
JP2023504469A (ja) 2023-02-03
US20220413937A1 (en) 2022-12-29
EP4071609A4 (en) 2024-01-10
EP4071609A1 (en) 2022-10-12
CN111090495A (zh) 2020-05-01
JP7438355B2 (ja) 2024-02-26

Similar Documents

Publication Publication Date Title
WO2021109750A1 (zh) 节点管理方法、装置、设备、存储介质和系统
CN111385114B (zh) Vnf服务实例化方法及装置
US10764132B2 (en) Scale-out association method and apparatus, and system
EP3200393B1 (en) Method and device for virtual network function management
US10924966B2 (en) Management method, management unit, and system
EP3059900B1 (en) Network service template management method and device
US20210075683A1 (en) Policy management method and system, and apparatus
CN107005426B (zh) 一种虚拟网络功能的生命周期管理方法及装置
EP3518465B1 (en) Method and device for initiating software modification
WO2016121834A1 (ja) ネットワーク機能仮想化管理方法とシステムと装置とプログラム
US20200042344A1 (en) Cloud Management Platform, and Virtual Machine Management Method and System
EP3694167A1 (en) Method and device for managing services in network function virtualization architecture
CN111061432B (zh) 一种业务迁移方法、装置、设备及可读存储介质
WO2021063130A1 (zh) 网络资源管理方法、系统、网络设备和可读存储介质
WO2019100266A1 (zh) 移动边缘主机服务通知方法和装置
JP2021524104A (ja) マスター・スタンドバイコンテナシステム切替
US20220365822A1 (en) Data Processing Method and Computer Device
EP3661140B1 (en) Method for applying for common service resource and related device
WO2021175105A1 (zh) 连接方法、装置、设备和存储介质
WO2022140945A1 (zh) 容器集群的管理方法和装置
CN105307130A (zh) 一种资源分配方法及系统
WO2019091284A1 (zh) 设备升级方法及装置
CN112015515B (zh) 一种虚拟网络功能的实例化方法及装置
CN114443059A (zh) Kubernetes集群的部署方法、装置及设备
US20200244525A1 (en) System and method for device configuration update

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20895097

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022532127

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20227022357

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020895097

Country of ref document: EP

Effective date: 20220704