Network cloud tenant management methods, devices, equipment and storage media

Abstract

This application discloses a network cloud tenant management method, apparatus, device, and storage medium. The method includes: NFVO sending a first creation request for creating a container cluster tenant to a container infrastructure management device; and receiving a first creation result of the container cluster tenant returned by the container infrastructure management device. The first creation request includes: the name of the container cluster tenant, cluster tenant quota information, and the identifier of the associated parent tenant; the first creation result includes the identifier of the container cluster tenant. This allows for resource management at the container cluster level based on container cluster tenants, which is beneficial for improving the utilization rate of containerized resources and facilitating the management and scheduling of containerized resources.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus, device and storage medium for managing network cloud tenants. Background Technology

[0002] As cloud-native containerization continues to gain momentum, the number of systems and applications deployed using container technology in the network cloud management resource pool is constantly increasing, leading to a continuous rise in the required cluster resources. If the existing tenant management methods of the network cloud are used, there will be a lack of resource statistics and management capabilities at the container cluster level for management and compute nodes. This results in inaccurate statistics on the actual resource usage of customers, leading to resource waste and hindering the orchestration and statistical management of actual resource usage by different tenants. Currently, there is no effective solution to this problem. Summary of the Invention

[0003] In view of this, embodiments of this application provide a network cloud tenant management method, apparatus, device and storage medium, which aim to improve the resource management capabilities of multi-tenants based on container resources.

[0004] The technical solution of this application embodiment is implemented as follows:

[0005] In a first aspect, embodiments of this application provide a network cloud tenant management method applied to a network function virtualization orchestrator (NFVO), the method comprising:

[0006] Send the first creation request for creating a container cluster tenant to the container infrastructure management device;

[0007] Receive the first creation result of the container cluster tenant returned by the container infrastructure management device;

[0008] The first creation request includes: the name of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant. The first creation result includes the identifier of the container cluster tenant.

[0009] The method in the above scheme further includes:

[0010] In response to a second creation request for creating a container cluster, a first query request is sent to the container infrastructure management device, the first query request being used to query the container cluster specifications supported by the container infrastructure management device;

[0011] Receive the specification list information indicating supported container cluster specifications returned by the container infrastructure management device;

[0012] Based on the specification list information, determine the specification information of the container cluster to be created, and obtain the container cluster name and the identifier of the associated container cluster tenant of the container cluster to be created.

[0013] Send configuration information for creating a container cluster to the container infrastructure management device. The configuration information includes: the specification information, the container cluster name, and the identifier of the associated container cluster tenant.

[0014] Receive the second creation result of the container cluster returned by the container infrastructure management device;

[0015] Based on the second creation result, the identifiers of the container cluster and the associated container cluster tenant are associated.

[0016] The method in the above scheme further includes:

[0017] In response to the scaling request of the target container cluster, a second query request is sent to the container infrastructure management device. The second query request is used to query the current container cluster specifications of the target container cluster.

[0018] Receive specification information returned by the container infrastructure management device, indicating the current container cluster specification of the target container cluster;

[0019] Obtain parameter information for scaling up or down the target container cluster;

[0020] Based on the parameter information, the resource quotas of the container cluster tenants associated with the target container cluster are updated, and instructions for scaling up or down the target container cluster are sent to the container infrastructure management device.

[0021] Receive the scaling operation results of the target container cluster returned by the container infrastructure management device.

[0022] The method in the above scheme further includes:

[0023] Send a deletion request for deleting the container cluster tenant to the container infrastructure management device;

[0024] The deletion request includes: the identifier of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant.

[0025] The method in the above scheme further includes:

[0026] Send an update request to the container infrastructure management device to update the container cluster tenant;

[0027] The update request includes: the identifier of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant.

[0028] The method in the above scheme further includes:

[0029] Send a query request for the target container cluster tenant to the container infrastructure management device;

[0030] Receive tenant information of the target container cluster tenant returned by the container infrastructure management device;

[0031] The query request includes the identifier of the target container cluster tenant.

[0032] Secondly, embodiments of this application provide a network cloud tenant management method, applied to a container infrastructure management device, the method comprising:

[0033] Receive the first creation request for creating a container cluster tenant;

[0034] Based on the first creation request, the container cluster tenant is created;

[0035] Send the first creation result of the container cluster tenant to NFVO;

[0036] The first creation request includes: the name of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant. The first creation result includes the identifier of the container cluster tenant.

[0037] The method in the above scheme further includes:

[0038] Receive a first query request sent by NFVO, the first query request being used to query the container cluster specifications supported by the container infrastructure management device;

[0039] Send a list of specifications indicating supported container cluster specifications to the NFVO;

[0040] The system receives configuration information for creating a container cluster sent by the NFVO, the configuration information including: the specification information of the container cluster, the container cluster name of the container cluster, and the identifier of the container cluster tenant associated with the container cluster.

[0041] Based on the configuration information, the Virtual Infrastructure Manager (VIM) is controlled to create the container cluster;

[0042] Send the second creation result of the container cluster to the NFVO.

[0043] The method in the above scheme further includes:

[0044] Receive a second query request sent by NFVO, the second query request being used to query the current container cluster specification of the target container cluster;

[0045] Send specification information indicating the current container cluster specification of the target container cluster to the NFVO;

[0046] Receive the instruction sent by the NFVO for scaling up or down the target container cluster;

[0047] Based on the instructions, VIM is controlled to perform scaling operations on the target container cluster;

[0048] The scaling operation results of the target container cluster are sent to the NFVO.

[0049] Thirdly, embodiments of this application provide a network cloud tenant management device, including:

[0050] The first sending module is used to send the first creation request for creating a container cluster tenant to the container infrastructure management device;

[0051] The first receiving module is used to receive the first creation result of the container cluster tenant returned by the container infrastructure management device;

[0052] The first creation request includes: the name of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant. The first creation result includes the identifier of the container cluster tenant.

[0053] Fourthly, embodiments of this application provide a network cloud tenant management device, including:

[0054] The second receiving module is used to receive the first creation request for creating a container cluster tenant;

[0055] The processing module is used to create the container cluster tenant based on the first creation request;

[0056] The second sending module is used to send the first creation result of the container cluster tenant to NFVO;

[0057] The first creation request includes: the name of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant. The first creation result includes the identifier of the container cluster tenant.

[0058] Fifthly, embodiments of this application provide a network device, including: a processor and a memory for storing a computer program capable of running on the processor, wherein the processor, when running the computer program, executes the steps of the method described in any aspect of the embodiments of this application.

[0059] Sixthly, embodiments of this application provide a computer storage medium storing a computer program, which, when executed by a processor, implements the steps of the method described in any aspect of embodiments of this application.

[0060] The technical solution provided in this application embodiment involves NFVO sending a first creation request for creating a container cluster tenant to the container infrastructure management device; and receiving a first creation result of the container cluster tenant returned by the container infrastructure management device. The first creation request includes: the name of the container cluster tenant, the identifier of the associated parent tenant, and quota information; the first creation result includes the identifier of the container cluster tenant. This allows for resource management at the container cluster level based on container cluster tenants, which is beneficial for improving the utilization rate of containerized resources and facilitating the management and scheduling of containerized resources. Attached Figure Description

[0061] Figure 1 This is a schematic diagram of the core cloud platform system in the relevant technology;

[0062] Figure 2 This is a schematic diagram of the tenant management system in the network cloud in related technologies;

[0063] Figure 3 This is a schematic diagram of the structure of the network cloud tenant management system in one application example of this application;

[0064] Figure 4 This is a schematic diagram of the structure of a network cloud tenant management system, which is another application example of this application.

[0065] Figure 5 This is a flowchart illustrating a network cloud tenant management method according to an embodiment of this application;

[0066] Figure 6 This is a flowchart illustrating another embodiment of the network cloud tenant management method of this application;

[0067] Figure 7 This is a schematic diagram of the tenant management system of the network cloud as an application embodiment of this application;

[0068] Figure 8 A schematic diagram illustrating the process of creating a container cluster tenant for an application embodiment of this application;

[0069] Figure 9 This is a schematic diagram illustrating the process of creating a container cluster and binding it to a container cluster tenant using this embodiment of the present application;

[0070] Figure 10 This is a schematic diagram illustrating the process of scaling up and down a container cluster and its association with deducting resources from container cluster tenants in an application embodiment of this application.

[0071] Figure 11 This is a schematic diagram of the structure of a network cloud tenant management device according to an embodiment of this application;

[0072] Figure 12 This is a schematic diagram of the structure of a network cloud tenant management device according to another embodiment of this application;

[0073] Figure 13 This is a schematic diagram of the network device according to an embodiment of this application. Detailed Implementation

[0074] The present application will now be described in further detail with reference to the accompanying drawings and embodiments.

[0075] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.

[0076] Traditional network equipment is customized based on specific specifications and technical requirements, making its maintenance and upgrade processes complex and its operational costs high for service deployment. To reduce the complexity and cost of network deployment and service deployment, a hardware-software decoupling approach based on a general-purpose hardware platform can effectively reduce the costs associated with equipment upgrades and accelerate the deployment of new services. Therefore, Network Function Virtualization (NFV), which enables the use of dedicated network elements, is increasingly being adopted.

[0077] The core cloud management functions of NFV are mainly implemented by MANO (NFV management and orchestration), the Operations Support System (OSS), and the Operation and Maintenance Center (OMC).

[0078] In related technologies, the core cloud platform system architecture is as follows: Figure 1As shown, it includes functional nodes such as the MANO system, OSS, OMC, virtualized network function (VNF), and network function virtualization infrastructure (NFVI). The MANO system includes the network function virtualization orchestrator (NFVO), virtualized network function manager (VNFM), virtualized infrastructure manager (VIM), and SDN controller (SDN-C).

[0079] The main functions of the MANO system include: lifecycle management of network elements, creation of images required by network elements, management of templates and software required by network elements, and allocation and management of network resources. Specifically, NFVO is responsible for unified resource scheduling, creating automatic scaling policies for VNFs, and providing specification configuration parameters for VNF instantiation; VNFM is responsible for VNF lifecycle management, such as parsing and processing VNFDs (VNF descriptions), initializing VNF instances, and scaling up and down VNFs; VIM is responsible for the scheduling and management of hardware and virtualization resources. With the development of cloud-native technologies, applications can be encapsulated in containers and deployed in the cloud based on microservice architectures. As the number of system applications deployed using container technology in the network cloud management resource pool continues to increase, the required cluster resources also increase. If the existing tenant management method of the network cloud is used, there will be a lack of resource statistics management capabilities for management nodes and compute nodes at the container cluster granularity, resulting in inaccurate statistics of actual resource usage by customers, leading to resource waste and hindering the orchestration and statistical management of actual resource usage by different tenants.

[0080] Among related technologies, based on the current state of network cloud services, NFVO can support the management capabilities of Tier 1 tenants, Tier 2 tenants, and VNF tenants. Figure 2This diagram illustrates a tenant management architecture for a network cloud oriented towards IaaS (Infrastructure-as-a-Service) resources. First-tier tenants are logical tenants on the NFVO, meaning the NFVO supports the creation of first-tier tenants and the setting of resource quotas for them, with unified quota management for first-tier tenants. Second-tier tenants correspond to the actual tenants created on the VIM. Third-tier tenants are represented on the NFVO as a "resource quota table" of VNF quotas. It is understandable that there is a hierarchical relationship between these tenant levels; third-tier tenants belong to second-tier tenants, and second-tier tenants belong to first-tier tenants.

[0081] However, the aforementioned multi-tenant management method is primarily an orchestration and management solution for tenant and quota information in VNF scenarios. In multi-tenant management, different role information is configured for each tenant user based on different business scenarios to achieve orchestration and management of the current tenant's resources and services.

[0082] As more and more B-domain (business domain), O-domain (operation domain), or M-domain (management domain) applications are deployed to various resource pools in the network cloud using containerization, it is necessary to evolve network cloud orchestration and management capabilities in conjunction with the development of existing network services. For containerized network cloud business scenarios, it is necessary to research and develop a new tenant management system based on container technology's NFVO orchestration and management, adding a unified orchestration and management solution for the computing, network, and storage resources of container clusters and container tenants.

[0083] This application provides a network cloud tenant management method based on container resources, which aims to realize the management of multi-level tenants in the network cloud based on container resources. Before describing the method, an exemplary description of a network cloud tenant management system that applies the method will be provided.

[0084] The main functions of the network cloud tenant management system include container cluster lifecycle management, container application information management, container application lifecycle management, and allocation and management of container-related resources. For example... Figure 3As shown in the example application, the network cloud tenant management system includes: NFVO, CCM (Container Cluster Manager), and CIM (Container Infrastructure Manager). NFVO supports the creation and management of container clusters, which support multiple modes, primarily dedicated and shared modes. Shared mode means the container cluster can be used by multiple secondary tenants. The container cluster contains CIM (Container Infrastructure Manager) nodes and CIE (Container Infrastructure Engine) nodes. For example, the resources of the container cluster can be virtual machines (VMs) or bare metal servers. Figure 3 As shown, NFVI can include VIM, PIM (physical infrastructure manager), and a monitor (Hypervisor).

[0085] right Figure 3 The components shown are explained below:

[0086] NFVO: Responsible for the unified scheduling of resources, including virtualization resources, container cluster resources, etc.

[0087] CCM: Responsible for the lifecycle management of container clusters, such as the creation, deletion, scaling up, and shrinking of container clusters.

[0088] CIM: Responsible for the scheduling and management of infrastructure such as nodes, storage, and networks within the resource pool.

[0089] CIE: Responsible for allocating and organizing resources, building and delivering containers, and executing container management commands in accordance with CIM requirements.

[0090] In other application examples, NFVO can also directly interface with the native Kubernetes (K8S) platform system. Simultaneously, an NFVO-CIM tenant management interface needs to be added to form a unified end-to-end NFVO container tenant management capability. For example, a Kubernetes-based network cloud tenant management system such as... Figure 4 As shown.

[0091] Kubernetes divides the infrastructure resources of a container cluster into a Kubernetes master node and a group of worker nodes. The master node (also called the management node) runs a set of processes related to container cluster management, such as the Application Programming Interface Server (API server) and the Replication Controller (RC). These processes implement management functions for the entire container cluster, including resource management, pod scheduling, elastic scaling, security control, system monitoring, and error correction. Each worker node runs three components: kubelet, proxy, and docker, responsible for managing the lifecycle of pods on that node and implementing service proxying. A pod can contain at least one container; therefore, a pod can be understood as a container repository composed of one or more containers.

[0092] Among them, the API Server provides the sole entry point for operating resource objects. All other components operate on resource data through the API interface it provides, and complete related business functions by performing "full queries" and "change monitoring" on the relevant resource data.

[0093] The controller manager is the management and control center of a container cluster. Its main purpose is to automate fault detection and recovery for the Kubernetes cluster. For example, it can replicate or remove Pods according to the definition of the RC to ensure that the number of Pod instances conforms to the definition of the RC; create and update service endpoints based on the management relationship between services and Pods; discover, manage, and monitor the status of nodes; and clean up locally cached image files.

[0094] The kubelet component is responsible for the entire lifecycle management of Pods on this node, including creation, modification, monitoring, and deletion. At the same time, Kubelet periodically reports the status information of this node to the API Server.

[0095] The proxy component is used to implement service proxying and software-based load balancing.

[0096] The Docker component provides the runtime environment for containers.

[0097] For example, embodiments of this application provide a network cloud tenant management method applied to NFVO, such as... Figure 5 As shown, the method includes:

[0098] Step 501: Send a first creation request for creating a container cluster tenant to the container infrastructure management device.

[0099] Here, the operator can initiate the process of creating a container cluster tenant on the NFVO, triggering the NFVO to send the first creation request to the container infrastructure management device. This container infrastructure management device can be either the aforementioned CCM or CIM. It is understood that for... Figure 3 The system shown can manage container cluster tenants based on the NFVO-CCM tenant management interface. Figure 4 The system shown can manage container cluster tenants based on the NFVO-CIM tenant management interface. For example, the first creation request includes: the name of the container cluster tenant, cluster tenant quota information, and the identifier of the associated parent tenant.

[0100] For example, the identifier of the associated parent tenant can be the identifier of the associated second-level tenant (secTenantID). Cluster tenant quota information can include system quota information and container tenant quota information.

[0101] Step 402: Receive the first creation result of the container cluster tenant returned by the container infrastructure management device.

[0102] Here, after receiving the first creation request, the container infrastructure management device can create a container cluster tenant based on the request and return the first creation result of the container cluster tenant to the NFVO. The first creation result includes the identifier of the container cluster tenant. The NFVO can write the identifier (clusterTenantID) of the created container cluster tenant into its system database and display the relevant information to the user.

[0103] Understandably, by establishing container cluster tenants, resource management at the container cluster level can be achieved based on container cluster tenants, which is conducive to improving the utilization rate of containerized resources and facilitating the management and scheduling of containerized resources.

[0104] In practical applications, when a container cluster is initially created, it is associated with a corresponding container cluster tenant. The resource quotas for the container cluster management nodes and compute nodes are managed and operated through the assigned container cluster tenant. After the container cluster is created, NFVO automatically associates the clusterTenantID with the corresponding container cluster. For example, the method further includes:

[0105] In response to a second creation request for creating a container cluster, a first query request is sent to the container infrastructure management device, the first query request being used to query the container cluster specifications supported by the container infrastructure management device;

[0106] Receive the specification list information indicating supported container cluster specifications returned by the container infrastructure management device;

[0107] Based on the specification list information, determine the specification information of the container cluster to be created, and obtain the container cluster name and the identifier of the associated container cluster tenant of the container cluster to be created.

[0108] Send configuration information for creating a container cluster to the container infrastructure management device. The configuration information includes: the specification information, the container cluster name, and the identifier of the associated container cluster tenant.

[0109] Receive the second creation result of the container cluster returned by the container infrastructure management device;

[0110] Based on the second creation result, the identifiers of the container cluster and the associated container cluster tenant are associated.

[0111] Understandably, when initiating a second creation request for a container cluster, the NFVO interface can display the specifications of the supported container clusters. The operator selects the identifier of the container cluster tenant associated with the container cluster to be created. In this way, NFVO can automatically associate the created container cluster with the container cluster tenant. For example, it can bind the container cluster with the corresponding clusterTenantID and deduct the quota resources of the container cluster from the total quota of the container cluster tenant, thereby realizing the management of the resource quota of the container cluster based on the container cluster tenant.

[0112] In practical applications, container cluster scaling management can also be implemented based on container cluster tenants. For example, the method further includes:

[0113] In response to the scaling request of the target container cluster, a second query request is sent to the container infrastructure management device. The second query request is used to query the current container cluster specifications of the target container cluster.

[0114] Receive specification information returned by the container infrastructure management device, indicating the current container cluster specification of the target container cluster;

[0115] Obtain parameter information for scaling up or down the target container cluster;

[0116] Based on the parameter information, the resource quotas of the container cluster tenants associated with the target container cluster are updated, and instructions for scaling up or down the target container cluster are sent to the container infrastructure management device.

[0117] Receive the scaling operation results of the target container cluster returned by the container infrastructure management device.

[0118] It is understandable that when scaling up or down a container cluster, the resources of the container cluster to be scaled up or down will be deducted and verified against the corresponding container cluster tenant. The resource quotas of the container cluster management node and compute node will be managed and operated through the container cluster tenant to which they belong.

[0119] Exemplarily, the method may further include:

[0120] Send a deletion request for deleting the container cluster tenant to the container infrastructure management device;

[0121] The deletion request includes: the identifier of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant.

[0122] It should be noted that the operator needs to delete the container cluster and related configuration information under the container cluster tenant on the NFVO in advance. Then, the NFVO sends a deletion request to the container infrastructure management device to delete the container cluster tenant. In this way, the deletion management of the container cluster tenant can be realized based on the deletion request.

[0123] Exemplarily, the method may further include:

[0124] Send an update request to the container infrastructure management device to update the container cluster tenant;

[0125] The update request includes: the identifier of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant.

[0126] In this way, the update management of container cluster tenants can be realized based on the update request, for example, the update management of quota information of container cluster tenants.

[0127] Exemplarily, the method may further include:

[0128] Send a query request for the target container cluster tenant to the container infrastructure management device;

[0129] Receive tenant information of the target container cluster tenant returned by the container infrastructure management device;

[0130] The query request includes the identifier of the target container cluster tenant.

[0131] In this way, based on the query request, the query management of container cluster tenants can be conveniently realized, thereby obtaining the tenant information of the target container cluster tenant. For example, the tenant information may include at least one of the following: cluster quota identifier, quota information.

[0132] For example, embodiments of this application also provide a network cloud tenant management method, applied to a container infrastructure management device, which can be a CCM or a CIM. Figure 6 As shown, the method includes:

[0133] Step 601: Receive the first creation request for creating a container cluster tenant.

[0134] Here, the operator can initiate the process of creating a container cluster tenant on the NFVO, triggering the NFVO to send a first creation request to the container infrastructure management device. For example, the first creation request includes: the name of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant.

[0135] Step 602: Based on the first creation request, create the container cluster tenant.

[0136] Step 603: Send the first creation result of the container cluster tenant to NFVO.

[0137] Here, after receiving the first creation request, the container infrastructure management device can create a container cluster tenant based on the request and return the first creation result of the container cluster tenant to the NFVO. The first creation result includes the identifier of the container cluster tenant. The NFVO can write the identifier (clusterTenantID) of the created container cluster tenant into its system database and display the relevant information to the user.

[0138] Understandably, by establishing container cluster tenants, resource management at the container cluster level can be achieved based on container cluster tenants, which is conducive to improving the utilization rate of containerized resources and facilitating the management and scheduling of containerized resources.

[0139] Exemplarily, the method further includes:

[0140] Receive a first query request sent by NFVO, the first query request being used to query the container cluster specifications supported by the container infrastructure management device;

[0141] Send a list of specifications indicating supported container cluster specifications to the NFVO;

[0142] The system receives configuration information for creating a container cluster sent by the NFVO, the configuration information including: the specification information of the container cluster, the container cluster name of the container cluster, and the identifier of the container cluster tenant associated with the container cluster.

[0143] Based on the configuration information, control the Virtual Infrastructure Manager (VIM) to create the container cluster;

[0144] Send the second creation result of the container cluster to the NFVO.

[0145] Understandably, when initiating a second creation request for a container cluster, NFVO interacts with the container infrastructure management device. The NFVO interface can display the specifications of the supported container clusters. The operator selects the identifier of the container cluster tenant associated with the container cluster to be created. In this way, NFVO can automatically associate the created container cluster with the container cluster tenant. For example, it can bind the container cluster with the corresponding clusterTenantID and deduct the quota resources of the container cluster from the total quota of the container cluster tenant, thereby realizing the management of the resource quota of the container cluster based on the container cluster tenant.

[0146] Exemplarily, the method further includes:

[0147] Receive a second query request sent by NFVO, the second query request being used to query the current container cluster specification of the target container cluster;

[0148] Send specification information indicating the current container cluster specification of the target container cluster to the NFVO;

[0149] Receive the instruction sent by the NFVO for scaling up or down the target container cluster;

[0150] Based on the instructions, VIM is controlled to perform scaling operations on the target container cluster;

[0151] The scaling operation results of the target container cluster are sent to the NFVO.

[0152] It is understandable that when scaling up or down a container cluster, the resources of the container cluster to be scaled up or down will be deducted and verified against the corresponding container cluster tenant. The resource quotas of the container cluster management node and compute node will be managed and operated through the container cluster tenant to which they belong.

[0153] The present application will now be described in further detail with reference to an application embodiment.

[0154] In this application example, for the scheduling and management of containerized resources, the tenant management architecture of the network cloud under the new container cluster mode is as follows: Figure 7 As shown in the figure. Among them, the container cluster tenant belongs to the second-level tenant, and the CIM tenant belongs to the container cluster tenant.

[0155] For example, the tenant management system and parameter definitions for the newly added container cluster mode of the network cloud are shown in Table 1 below:

[0156] Table 1

[0157]

[0158] For a Level 1 tenant: xxxQuotaUsed refers to the total resource quota allocated to all Level 2 tenants by the Level 1 tenant; xxxQuotaRemain indicates the remaining allocable resource quota for the Level 1 tenant; xxxUsed refers to the sum of the actual resource usage of all Level 2 tenants under the Level 1 tenant; and xxxRemain refers to the total remaining usable resources under the Level 1 tenant.

[0159] Second-level tenant: xxxQuotaUsed refers to the total quota allocated to all cluster resources by the second-level tenant; xxxQuotaRemain refers to the remaining allocable resource quota for the second-level tenant; xxxUsed refers to the sum of the resource usage of all container systems and the actual resource usage of CIM tenants under the second-level tenant; and xxxRemain refers to the total remaining usable resources under the second-level tenant.

[0160] Container cluster tenant: xxxQuotaUsed refers to the total quota allocated to system resources and CIM tenants in this cluster; xxxQuotaRemain refers to the remaining allocable resource quota in this cluster; xxxUsed refers to the sum of the resource usage of all containers in this cluster and the actual resource usage of CIM tenants; xxxRemain refers to the total remaining usable resources in this container cluster tenant.

[0161] CIM Tenant: xxxUsed refers to the sum of actual resource usage of container services under this CIM tenant.

[0162] In this application example, the container infrastructure management device is defined as CCM. Interface expansion and additions are performed between NFVO and CCM, as detailed below:

[0163] 1) New API addition: CreateClusterQuota (Create container cluster tenant)

[0164] Interface access method: POST / v1 / tenants / clustertenant / {secTenantID}. For example, the parameters passed to the interface for creating a container cluster tenant are shown in Table 2 below:

[0165] Table 2

[0166]

[0167] 2) New API addition: DeleteClusterQuota (Delete container cluster tenant)

[0168] Interface access method: DELETE / v1 / tenants / {clusterTenantID}. For example, the parameters passed to the interface for deleting a container cluster tenant are shown in Table 3 below:

[0169] Table 3

[0170]

[0171] 3) New API addition: UpdateClusterQuota (Update container cluster tenant)

[0172] Interface access method: PUT / v1 / tenants / {clusterTenantID}{secTenantID}. For example, the parameters passed to the interface for updating container cluster tenants are shown in Table 4 below:

[0173] Table 4

[0174]

[0175] 4) New API addition: QueryClusterQuota (Query container cluster tenants)

[0176] Interface access method: GET / v1.0 / tenants / {clusterTenantID}. For example, the parameters passed to the interface for querying container cluster tenants are shown in Table 5 below:

[0177] Table 5

[0178]

[0179]

[0180] The following is an exemplary illustration of the end-to-end process of container cluster deployment and association with container cluster tenants in this application embodiment:

[0181] Figure 8 This document illustrates a flowchart of the container cluster tenant creation process in this application embodiment, as shown below. Figure 8 As shown, the creation of a container cluster tenant can include:

[0182] Step 801: Initiate the container cluster tenant creation process.

[0183] Here, the operator can initiate the process of creating a container cluster tenant on NFVO, and enter request parameters such as the name of the container cluster tenant and quota information.

[0184] Step 802: Verify the validity of the request parameters.

[0185] Here, NFVO can perform validity checks on request parameters. For example, it can check the quota information in the request parameters based on the quota information of the second-level tenant, and execute step 803 after the check passes.

[0186] Step 803: Send a request to create a container cluster tenant.

[0187] Here, NFVO can call the CreateClusterQuota interface to send a request to create a container cluster tenant (CreateClusterQuota request, i.e. the first creation request mentioned above) to CCM.

[0188] Step 804 returns the Container Cluster Tenant Creation Response.

[0189] Here, after receiving the CreateClusterQuota request from NFVO, CCM completes the creation of the container cluster tenant and returns a CreateClusterQuota response to NFVO. NFVO then writes the created container cluster tenant's clusterTenantID information into its system database.

[0190] Step 805 returns the container cluster tenant creation result.

[0191] NFVO returns the container cluster tenant creation results to the operator to display relevant information.

[0192] Figure 9 This illustration shows a flowchart of the process for creating a container cluster and binding it to a container cluster tenant in this application embodiment. Figure 9 As shown, the creation of the container cluster and its binding with a container cluster tenant can include:

[0193] Step 901 triggers a container cluster creation request.

[0194] Here, the operator triggers a container cluster creation request on NFVO (i.e., the aforementioned second creation request).

[0195] Step 902: Send a container cluster specification query request.

[0196] Here, in response to the container cluster creation request, NFVO sends a container cluster specification query request to CCM to query the container cluster specifications supported by CCM.

[0197] Step 903 returns the container cluster specification information.

[0198] Here, CCM returns a list of specifications indicating the supported container cluster specifications to NFVO.

[0199] Step 904: Enter container cluster creation information.

[0200] Here, the operator enters information such as the cluster name and cluster node specifications on the NFVO interface. Understandably, they also need to enter the identifier (clusterTenantID) of the associated container cluster tenant.

[0201] Step 905: Bind the corresponding container cluster tenant and perform resource verification and deduction.

[0202] Here, NFVO binds and associates the newly created container cluster with the corresponding container cluster tenant (clusterTenantID) information, and verifies and deducts the quota resources of the corresponding cluster tenant.

[0203] Step 906: Send a request to create a container cluster.

[0204] NFVO sends a request to create a container cluster to CCM.

[0205] Step 907: Create a container cluster.

[0206] CCM accesses VIM to perform container cluster creation operations.

[0207] Step 908 returns the Container Cluster Creation response.

[0208] CCM returns a container cluster creation response to NFVO.

[0209] Step 909 returns the container cluster creation result.

[0210] NFVO returns the container cluster creation result to the operator and can also record and display the binding information between the container cluster and the container cluster tenant. Thus, after the container cluster creation is complete, NFVO can automatically associate the clusterTenantID with the corresponding container cluster.

[0211] Figure 10 This illustration shows a flowchart illustrating the process of scaling up and down a container cluster and its association with deducting resources from container cluster tenants in this application embodiment. Figure 10 As shown, the scaling up and down of the container cluster and its association with the deduction of container cluster tenant resources can include:

[0212] Step 1001: Trigger a request to scale the container cluster up or down.

[0213] Here, the operator triggers a scaling request for the target container cluster on NFVO.

[0214] Step 1002: Send a container cluster specification query request.

[0215] Here, in response to the container cluster creation request, NFVO sends a container cluster specification query request to CCM to query the container cluster specification of the target container cluster.

[0216] Step 1003: Return container cluster specification information.

[0217] Here, CCM returns specification information indicating the current container cluster specification of the target container cluster to NFVO.

[0218] Step 1004: Input container cluster scaling information.

[0219] Here, the operator enters information such as the specifications of the cluster nodes to be scaled up or down on the NFVO interface.

[0220] Step 1005: Query the bound container cluster tenant and perform resource verification and deduction.

[0221] Here, NFVO queries the container cluster tenant information, and then deducts the remaining quota resources from the corresponding container cluster tenant (clusterTenantID) based on the scaling up or down of the cluster resources.

[0222] Step 1006: Send a request to scale up or down the container cluster.

[0223] NFVO sends a request to scale up or down the container cluster to CCM.

[0224] Step 1007: Scaling up or down the container cluster.

[0225] CCM accesses VIM to perform container cluster scaling operations.

[0226] Step 1008 returns the response for scaling up and down the container cluster.

[0227] CCM returns the scaling response for the container cluster to NFVO.

[0228] Step 1009 returns the results of scaling up or down the container cluster.

[0229] NFVO returns the scaling results of the container cluster to the user, and simultaneously writes the updated container cluster information and container cluster tenant information into the system database.

[0230] It is understood that this application embodiment constructs a system based on... Figure 3 The system shown demonstrates an end-to-end process for managing container cluster tenants and resources throughout the entire lifecycle of the container cluster. This process can meet the management and allocation needs of network cloud managers and business users for different resource objects, thereby improving the utilization rate of existing network resources.

[0231] It should be noted that, for Figure 4The system shown can realize end-to-end resource management processes for container cluster tenants and the entire lifecycle of container clusters based on the process interaction between NFVO and CIM. For details, please refer to the process interaction between NFVO and CCM, which will not be elaborated here.

[0232] In order to implement the method of the embodiments of this application, the embodiments of this application also provide a network cloud tenant management device, which corresponds to the above-mentioned NFVO-side management method. The steps in the above-mentioned NFVO-side management method embodiments are also fully applicable to the embodiments of this network cloud tenant management device.

[0233] like Figure 11 As shown, the network cloud tenant management device includes a first sending module 1101 and a first receiving module 1102. The first sending module 1101 is used to send a first creation request for creating a container cluster tenant to the container infrastructure management device; the first receiving module 1102 is used to receive a first creation result of the container cluster tenant returned by the container infrastructure management device; wherein, the first creation request includes: the name of the container cluster tenant, the identifier of the associated parent tenant and quota information, and the first creation result includes the identifier of the container cluster tenant.

[0234] For example, the network cloud tenant management device further includes: a container cluster management module 1103, specifically used for:

[0235] In response to a second creation request for creating a container cluster, a first query request is sent to the container infrastructure management device, the first query request being used to query the container cluster specifications supported by the container infrastructure management device;

[0236] Receive the specification list information indicating supported container cluster specifications returned by the container infrastructure management device;

[0237] Based on the specification list information, determine the specification information of the container cluster to be created, and obtain the container cluster name and the identifier of the associated container cluster tenant of the container cluster to be created.

[0238] Send configuration information for creating a container cluster to the container infrastructure management device. The configuration information includes: the specification information, the container cluster name, and the identifier of the associated container cluster tenant.

[0239] Receive the second creation result of the container cluster returned by the container infrastructure management device;

[0240] Based on the second creation result, the identifiers of the container cluster and the associated container cluster tenant are associated.

[0241] For example, the container cluster management module 1103 is also used for:

[0242] In response to the scaling request of the target container cluster, a second query request is sent to the container infrastructure management device. The second query request is used to query the current container cluster specifications of the target container cluster.

[0243] Receive specification information returned by the container infrastructure management device, indicating the current container cluster specification of the target container cluster;

[0244] Obtain parameter information for scaling up or down the target container cluster;

[0245] Based on the parameter information, the resource quotas of the container cluster tenants associated with the target container cluster are updated, and instructions for scaling up or down the target container cluster are sent to the container infrastructure management device.

[0246] Receive the scaling operation results of the target container cluster returned by the container infrastructure management device.

[0247] For example, the network cloud tenant management device further includes: a deletion module 1104, used to send a deletion request for deleting a container cluster tenant to the container infrastructure management device; the deletion request includes: the identifier of the container cluster tenant, the identifier of the associated parent tenant, and quota information.

[0248] For example, the network cloud tenant management device further includes: an update module 1105, used to send an update request for updating the container cluster tenant to the container infrastructure management device; the update request includes: the identifier of the container cluster tenant, the identifier of the associated parent tenant, and quota information.

[0249] Exemplarily, the network cloud tenant management device further includes: a query module 1106, specifically used for:

[0250] Send a query request for the target container cluster tenant to the container infrastructure management device;

[0251] Receive tenant information of the target container cluster tenant returned by the container infrastructure management device;

[0252] The query request includes the identifier of the target container cluster tenant.

[0253] In practical applications, the first sending module 1101, the first receiving module 1102, the container cluster management module 1103, the deletion module 1104, the update module 1105, and the query module 1106 can be implemented by the processor in the network cloud tenant management device. Of course, the processor needs to run the computer program in the memory to implement its functions.

[0254] In order to implement the method of the embodiments of this application, the embodiments of this application also provide a network cloud tenant management device, which corresponds to the management method of the container infrastructure management device side described above. The steps of the management method embodiment of the container infrastructure management device side described above are also fully applicable to the embodiments of this network cloud tenant management device.

[0255] like Figure 12 As shown, the network cloud tenant management device includes: a second receiving module 1201, a processing module 1202, and a second sending module 1203. The second receiving module 1201 receives a first creation request for creating a container cluster tenant; the processing module 1202 creates the container cluster tenant based on the first creation request; the second sending module 1203 sends the first creation result of the container cluster tenant to the NFVO; wherein, the first creation request includes: the name of the container cluster tenant, the identifier of the associated parent tenant, and quota information, and the first creation result includes the identifier of the container cluster tenant.

[0256] For example, the second receiving module 1201 is further configured to receive a first query request sent by NFVO, the first query request being used to query the container cluster specifications supported by the container infrastructure management device;

[0257] The second sending module 1203 is also used to send a list of specifications indicating supported container cluster specifications to the NFVO;

[0258] The second receiving module 1201 is also used to receive configuration information for creating a container cluster sent by the NFVO, the configuration information including: the specification information of the container cluster, the container cluster name of the container cluster, and the identifier of the container cluster tenant associated with the container cluster.

[0259] The processing module 1202 is also used to control the Virtual Infrastructure Manager (VIM) to create the container cluster based on the configuration information;

[0260] The second sending module 1203 is also used to send the second creation result of the container cluster to the NFVO.

[0261] For example, the second receiving module 1201 is further configured to receive a second query request sent by NFVO, the second query request being used to query the current container cluster specification of the target container cluster;

[0262] The second sending module 1203 is also used to send specification information indicating the current container cluster specification of the target container cluster to the NFVO;

[0263] The second receiving module 1201 is also used to receive instructions sent by the NFVO for scaling up or down the target container cluster;

[0264] The processing module 1202 is also used to control VIM to perform scaling operations on the target container cluster based on the instructions.

[0265] The second sending module 1203 is also used to send the scaling operation results of the target container cluster to the NFVO.

[0266] In practical applications, the second receiving module 1201, the processing module 1202, and the second transmitting module 1203 can be implemented by the processor in the network cloud tenant management device. Of course, the processor needs to run the computer program in the memory to implement its functions.

[0267] It should be noted that the network cloud tenant management device provided in the above embodiments is only illustrated by the division of the above program modules when performing network cloud tenant management. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the network cloud tenant management device and the network cloud tenant management method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0268] Based on the hardware implementation of the above-described program modules, and in order to implement the method of this application embodiment, this application embodiment also provides a network device. This network device can be the aforementioned NFVO or container infrastructure management device. Figure 13 This is only an exemplary structure of the network device, not the entire structure; implementation is possible as needed. Figure 13 The structure shown may be part or all of the structure.

[0269] like Figure 13 As shown, the network device 1300 provided in this embodiment includes at least one processor 1301, a memory 1302, a user interface 1303, and at least one network interface 1304. The various components in the network device 1300 are coupled together via a bus system 1305. It can be understood that the bus system 1305 is used to implement communication between these components. In addition to a data bus, the bus system 1305 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in… Figure 13The general labeled all buses as Bus System 1305.

[0270] The user interface 1303 may include a monitor, keyboard, mouse, trackball, click wheel, buttons, touchpad, or touch screen.

[0271] The memory 1302 in this embodiment is used to store various types of data to support the operation of the network device. Examples of such data include any computer program used to operate on the network device.

[0272] The network cloud tenant management method disclosed in this application embodiment can be applied to or implemented by the processor 1301. The processor 1301 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the network cloud tenant management method can be completed by the integrated logic circuit of the hardware in the processor 1301 or by instructions in the form of software. The processor 1301 mentioned above may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 1301 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of this application can be directly reflected as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in the memory 1302. The processor 1301 reads the information in the memory 1302 and, in conjunction with its hardware, completes the steps of the network cloud tenant management method provided in the embodiments of this application.

[0273] In an exemplary embodiment, the network device may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned methods.

[0274] It is understood that memory 1302 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Sync Link Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0275] In an exemplary embodiment, this application also provides a computer storage medium, specifically a computer-readable storage medium, such as a memory 1302 storing a computer program. This computer program can be executed by the processor 1301 of a network device to complete the steps described in the method of this application embodiment. The computer-readable storage medium can be a ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM, etc.

[0276] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0277] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0278] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for managing network cloud tenants, characterized in that, The method, applied to a Network Functions Virtualization Orchestrator (NFVO), includes: Send the first creation request for creating a container cluster tenant to the container infrastructure management device; Receive the first creation result of the container cluster tenant returned by the container infrastructure management device; The first creation request includes: the name of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant; the first creation result includes the identifier of the container cluster tenant; the container cluster tenant is used to implement resource management at the container cluster level. The method further includes: Send configuration information for creating a container cluster to the container infrastructure management device. The configuration information includes: the specification information of the container cluster to be created, the container cluster name of the container cluster to be created, and the identifier of the associated container cluster tenant. Receive the second creation result of the container cluster returned by the container infrastructure management device; Based on the second creation result, the identifiers of the container cluster and the associated container cluster tenant are associated.

2. The method according to claim 1, characterized in that, The method further includes: In response to a second creation request for creating a container cluster, a first query request is sent to the container infrastructure management device, the first query request being used to query the container cluster specifications supported by the container infrastructure management device; Receive the specification list information indicating supported container cluster specifications returned by the container infrastructure management device; Based on the specification list information, determine the specification information of the container cluster to be created, and obtain the container cluster name and the identifier of the associated container cluster tenant.

3. The method according to claim 2, characterized in that, The method further includes: In response to the scaling request of the target container cluster, a second query request is sent to the container infrastructure management device. The second query request is used to query the current container cluster specifications of the target container cluster. Receive specification information returned by the container infrastructure management device, indicating the current container cluster specification of the target container cluster; Obtain parameter information for scaling up or down the target container cluster; Based on the parameter information, the resource quotas of the container cluster tenants associated with the target container cluster are updated, and instructions for scaling up or down the target container cluster are sent to the container infrastructure management device. Receive the scaling operation results of the target container cluster returned by the container infrastructure management device.

4. The method according to claim 1, characterized in that, The method further includes: Send a deletion request for deleting the container cluster tenant to the container infrastructure management device; The deletion request includes: the identifier of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant.

5. The method according to claim 1, characterized in that, The method further includes: Send an update request to the container infrastructure management device to update the container cluster tenant; The update request includes: the identifier of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant.

6. The method according to claim 1, characterized in that, The method further includes: Send a query request for the target container cluster tenant to the container infrastructure management device; Receive tenant information of the target container cluster tenant returned by the container infrastructure management device; The query request includes the identifier of the target container cluster tenant.

7. A method for managing network cloud tenants, characterized in that, Applied to container infrastructure management devices, the method includes: Receive the first creation request for creating a container cluster tenant; Based on the first creation request, the container cluster tenant is created; Send the first creation result of the container cluster tenant to NFVO; The first creation request includes: the name of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant; the first creation result includes the identifier of the container cluster tenant; the container cluster tenant is used to implement resource management at the container cluster level. The method further includes: The system receives configuration information for creating a container cluster sent by the NFVO, the configuration information including: the specification information of the container cluster, the container cluster name of the container cluster, and the identifier of the container cluster tenant associated with the container cluster. Based on the configuration information, the Virtual Infrastructure Manager (VIM) is controlled to create the container cluster; Send the second creation result of the container cluster to the NFVO.

8. The method according to claim 7, characterized in that, The method further includes: Receive a first query request sent by NFVO, the first query request being used to query the container cluster specifications supported by the container infrastructure management device; Send a list of specifications indicating supported container cluster specifications to the NFVO.

9. The method according to claim 7, characterized in that, The method further includes: Receive a second query request sent by NFVO, the second query request being used to query the current container cluster specification of the target container cluster; Send specification information indicating the current container cluster specification of the target container cluster to the NFVO; Receive the instruction sent by the NFVO for scaling up or down the target container cluster; Based on the instructions, VIM is controlled to perform scaling operations on the target container cluster; The scaling operation results of the target container cluster are sent to the NFVO.

10. A network cloud tenant management device, characterized in that, include: The first sending module is used to send the first creation request for creating a container cluster tenant to the container infrastructure management device; The first receiving module is used to receive the first creation result of the container cluster tenant returned by the container infrastructure management device; The first creation request includes: the name of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant; the first creation result includes the identifier of the container cluster tenant; the container cluster tenant is used to implement resource management at the container cluster level. The container cluster management module is used to send configuration information for creating a container cluster to the container infrastructure management device. The configuration information includes: the specification information of the container cluster to be created, the container cluster name of the container cluster to be created, and the identifier of the associated container cluster tenant. Receive the second creation result of the container cluster returned by the container infrastructure management device; Based on the second creation result, the identifiers of the container cluster and the associated container cluster tenant are associated.

11. A network cloud tenant management device, characterized in that, include: The second receiving module is used to receive the first creation request for creating a container cluster tenant; The processing module is used to create the container cluster tenant based on the first creation request; The second sending module is used to send the first creation result of the container cluster tenant to NFVO; The first creation request includes: the name of the container cluster tenant, the cluster tenant quota information, and the identifier of the associated parent tenant; the first creation result includes the identifier of the container cluster tenant; the container cluster tenant is used to implement resource management at the container cluster level. The second receiving module is further configured to: receive configuration information for creating a container cluster sent by the NFVO, the configuration information including: the specification information of the container cluster, the container cluster name of the container cluster, and the identifier of the container cluster tenant associated with the container cluster; The processing module is also used to: control the Virtual Infrastructure Manager (VIM) to create the container cluster based on the configuration information; The second sending module is also used to: send the second creation result of the container cluster to the NFVO.

12. A network device, characterized in that, include: A processor and memory for storing computer programs that can run on the processor, wherein, The processor, when running a computer program, performs the steps of the method according to any one of claims 1 to 9.

13. A computer storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 9.

Images