WO2023078194A1 - 通信方法和装置 - Google Patents

通信方法和装置 Download PDF

Info

Publication number
WO2023078194A1
WO2023078194A1 PCT/CN2022/128497 CN2022128497W WO2023078194A1 WO 2023078194 A1 WO2023078194 A1 WO 2023078194A1 CN 2022128497 W CN2022128497 W CN 2022128497W WO 2023078194 A1 WO2023078194 A1 WO 2023078194A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
container cluster
ccm
request message
cluster management
Prior art date
Application number
PCT/CN2022/128497
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 华为技术有限公司
Publication of WO2023078194A1 publication Critical patent/WO2023078194A1/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
    • 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
    • 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/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • 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

Definitions

  • the embodiments of the present application relate to the technical field of communication, and more specifically, to a communication method and device.
  • the container cluster management feature is deployed to the container cluster in a static configuration manner. For example, during the process of creating a container cluster, predefined container cluster management features can be added to the container cluster, and during the process of deleting a container cluster, the container cluster management features used by the container cluster can be deleted, so as to realize container cluster management Tight coupling of features to container clusters.
  • deploying container cluster management features in a static configuration manner is increasingly unable to meet the needs of operators, especially in environments where container clusters are applied in multi-tenant management. Operators urgently need a method that can dynamically deploy container cluster management features in container clusters according to the operator's operation and management requirements. Therefore, how to realize the dynamic deployment of container cluster management features is an urgent problem to be solved.
  • Embodiments of the present application provide a communication method and device, which can implement dynamic deployment of container cluster management features.
  • a communication method including:
  • the container cluster management CCM receives a first request message from the network device, the first request message is used to request the CCM to associate the target customized container cluster management feature with the target container cluster, and the first request message includes the identifier of the target customized container cluster management feature information and identification information of the target container cluster; wherein, the network device is a consumer entity of the CCM; and the CCM associates the management feature of the target customized container cluster with the target container cluster according to the first request message.
  • the network device is a network function virtualization orchestrator NFVO.
  • CCM can receive the first request message from NFVO, and associate the target customized container cluster management feature with the target container cluster according to the first request message, thereby realizing the dynamic deployment of the container cluster management feature and better meeting the operator's needs.
  • the solution proposed in this application to realize the dynamic deployment of container cluster management features does not require interaction between CCM and CISM, which can avoid increasing the multi-vendor environment integration cost of interoperability between container platform layer functions.
  • the first request message further includes application scope information of the associated operation; the application scope information of the associated operation is used to indicate that the target customized container cluster management feature is applied to the target container All namespaces in the cluster; or, the application range information of the associated operation is used to indicate that the target customized container cluster management feature is applied to some namespaces in the target container cluster, and the first request message also includes identification information of some namespaces.
  • the first request message further includes information about consumers in the target container cluster that use the target customized container cluster management feature, and the consumer information that uses the target customized container cluster management feature Consumers are control plane functional entities and/or user plane functional entities.
  • the method further includes:
  • the CCM sends a first response message to the network device, where the first response message is used to indicate that the target customized container cluster management feature is successfully associated with the target container cluster.
  • the method before the CCM receives the first request message from the network device, the method further includes:
  • the CCM receives a second request message from the network device, the second request message is used to request the CCM to load the target file, the second request message includes specific information, and the specific information is used to determine the target file; wherein, the target file includes deployment and operation target customization Configuration, status and policy information of container cluster management features; CCM determines the target file according to the second request message, and verifies whether the target file can be loaded; if the target file can be loaded, CCM loads the target file; CCM sends the target file to the network device A second response message, where the second response message is used to indicate that the CCM has successfully loaded the target file.
  • the target file is a managed container cluster object declarative descriptor MDD file;
  • the specific information includes the identification information of the target file, and/or, the storage path of the target file information.
  • the method further includes:
  • the CCM receives a third request message from the network device.
  • the third request message is used to request the CCM to create a target customized container cluster management feature.
  • the third request message includes specific information; the CCM determines the target file according to the third request message; the CCM determines the target file according to the target file Deployment information in , create a target object instance, which corresponds to the target customized container cluster management feature; CCM sends a third response message to the network device, and the third response message is used to instruct CCM to successfully create the target customized container cluster management feature , the third response message includes identification information of the target object instance.
  • the method further includes:
  • the CCM receives a fourth request message from the network device, and the fourth request message is used to request to disassociate the target customized container cluster management characteristic from the target container cluster; wherein, the fourth request message includes the identification information and the target customized container cluster management characteristic.
  • the identification information of the target container cluster the CCM de-associates the target customized container cluster management characteristics with the target container cluster according to the fourth request message; the CCM sends the fourth response message to the network device, and the fourth response message is used to indicate that the CCM has successfully customized Disassociate the container cluster management feature with the target container cluster.
  • the CCM can receive the fourth request message from NFVO, and complete the disassociation between the target customized container cluster management feature and the target container cluster according to the fourth request message, thereby realizing dynamic container cluster management without deleting the container cluster.
  • the customized container cluster management feature is removed from the container cluster to better meet the needs of operators.
  • the CCM may receive the fourth request message from the NFVO, and complete the disassociation of the target customized container cluster management feature from the target container cluster according to the fourth request message.
  • the solution of the present application can dynamically de-associate the customized container cluster management features from the container cluster without accompanying the deletion process of the container cluster, which better meets the ever-changing needs of operators.
  • the method further includes:
  • the CCM receives the fifth request message from the network device, and the fifth request message is used to request to delete the target customized container cluster management feature; wherein, the fifth request message includes the identification information of the target customized container cluster management feature; the CCM according to the fifth request message to delete the target customized container cluster management feature; the CCM sends a fifth response message to the network device, and the fifth response message is used to instruct the CCM to successfully delete the target customized container cluster management feature.
  • a communication method including:
  • the network device determines to associate the target customized container cluster management feature with the target container cluster; the network device sends a first request message to the container cluster manager CCM, and the first request message is used to request the CCM to associate the target customized container cluster management feature with the target container cluster
  • the container cluster is associated, and the first request message includes the identification information of the target customized container cluster management feature and the identification information of the target container cluster; wherein, the network device is a consumer entity of the CCM.
  • the network device is a network function virtualization orchestrator NFVO.
  • NFVO can determine that the target customized container cluster management feature needs to be associated with the target container cluster, and further, NFVO sends a first request message to CCM, so that CCM associates the target customized container cluster according to the first request message Management features and target container clusters, so as to realize the dynamic deployment of container cluster management features and better meet the needs of operators.
  • the solution proposed in this application to realize the dynamic deployment of container cluster management features does not require interaction between CCM and CISM, which can avoid increasing the multi-vendor environment integration cost of interoperability between container platform layer functions.
  • the first request message further includes application range information of the associated operation; the application range information of the associated operation is used to indicate that the target customized container cluster management feature is applied to the target container All namespaces in the cluster; or, the application range information of the associated operation is used to indicate that the target customized container cluster management feature is applied to some namespaces in the target container cluster, and the first request message also includes identification information of some namespaces.
  • the first request message further includes information about consumers in the target container cluster that use the target customized container cluster management feature, and the consumer information that uses the target customized container cluster management feature Consumers are control plane functional entities and/or user plane functional entities.
  • the method further includes:
  • the network device receives a first response message from the CCM, where the first response message is used to indicate that the target customized container cluster management characteristic is successfully associated with the target container cluster.
  • the method further includes:
  • the network device determines the target file, and the target file includes the configuration, status, and policy information of the deployment and operation target customized container cluster management features; the network device sends a second request message to the CCM, and the second request message is used to request the CCM to load the target file.
  • the second request message includes specific information, and the specific information is used to determine the target file; the network device receives a second response message from the CCM, and the second response message is used to instruct the CCM to successfully load the target file.
  • the target file is a managed container cluster object declarative descriptor MDD file;
  • the specific information includes the identification information of the target file, and/or, the storage path of the target file information.
  • the method further includes:
  • the network device determines to create a target customized container cluster management feature; the network device sends a third request message to the CCM, the third request message is used to request the CCM to create a target customized container cluster management feature, and the third request message includes specific information; the network device sends from The CCM receives the third response message, the third response message is used to instruct the CCM to successfully create the target customized container cluster management feature, the third response message includes identification information of the target object instance, and the target object instance corresponds to the target customized container cluster management feature.
  • the method further includes:
  • the network device determines to disassociate the target customized container cluster management feature with the target container cluster; the network device sends a fourth request message to the CCM, and the fourth request message is used to request to disassociate the target customized container cluster management feature with the target container cluster;
  • the fourth request message includes the identification information of the management characteristics of the target customized container cluster and the identification information of the target container cluster; the network device receives the fourth response message from the CCM, and the fourth response message is used to indicate that the CCM has successfully configured the target customized container cluster Management properties are disassociated from the target container cluster.
  • the NFVO may send a fourth request message to the CCM, so that the CCM completes the target customized container cluster management feature according to the fourth request message
  • the de-association with the target container cluster enables the dynamic removal of customized container cluster management features from the container cluster without deleting the container cluster, which better meets the needs of operators.
  • the method further includes:
  • the network device determines to delete the target customized container cluster management feature; the network device sends a fifth request message to the CCM, and the fifth request message is used to request to delete the target customized container cluster management feature; wherein, the fifth request message includes the target customized Identification information of the container cluster management feature; the network device receives a fifth response message from the CCM, and the fifth response message is used to indicate that the CCM successfully deletes the target customized container cluster management feature.
  • a container cluster manager CCM including:
  • a transceiver unit and a processing unit connected to the transceiver unit.
  • the transceiver unit is configured to receive a first request message from the network device, the first request message is used to request the CCM to associate the target customized container cluster management characteristic with the target container cluster, and the first request message includes the target customized container cluster management characteristic Identification information and identification information of the target container cluster; wherein, the network device is a consumer entity of the CCM.
  • a processing unit configured to associate the target customized container cluster management feature with the target container cluster according to the first request message.
  • the first request message further includes application scope information of the associated operation; the application scope information of the associated operation is used to indicate that the target customized container cluster management feature is applied to the target container All namespaces in the cluster; or, the application range information of the associated operation is used to indicate that the target customized container cluster management feature is applied to some namespaces in the target container cluster, and the first request message also includes identification information of some namespaces.
  • the first request message further includes information about consumers in the target container cluster that use the target customized container cluster management feature, and the consumers using the target customized container cluster management feature Consumers are control plane functional entities and/or user plane functional entities.
  • the transceiver unit is further configured to send a first response message to the network device, where the first response message is used to indicate that the target customized container cluster management feature is successfully associated with the target container cluster.
  • the transceiver unit is further configured to receive a second request message from the network device, the second request message is used to request the CCM to load the target file, the second request message includes specific information, and the specific information is used to determine the target file; wherein the target file includes a deployment and run target-customized configuration, status, and policy information for container cluster management features.
  • the processing unit is further configured to determine the target file according to the second request message, and verify whether the target file can be loaded.
  • the processing unit is also used to load the target file.
  • the transceiver unit is further configured to send a second response message to the network device, where the second response message is used to indicate that the CCM has successfully loaded the target file.
  • the target file is a managed container cluster object declarative descriptor MDD file;
  • the specific information includes the identification information of the target file, and/or, the storage path of the target file information.
  • the transceiver unit is further configured to receive a third request message from the network device, the third request message is used to request the CCM to create a target customized container cluster management feature, and the third request message includes specific information.
  • the processing unit is further configured to determine the target file according to the third request message.
  • the processing unit is also used to create a target object instance according to the deployment information in the target file, and the target object instance corresponds to the management feature of the target customized container cluster.
  • the transceiver unit is further configured to send a third response message to the network device, the third response message is used to instruct the CCM to successfully create the target customized container cluster management feature, and the third response message includes identification information of the target object instance.
  • the transceiver unit is further configured to receive a fourth request message from the network device, and the fourth request message is used to request to disassociate the target customized container cluster management feature from the target container cluster; wherein, the fourth request message includes the target customized container cluster management The identification information of the attribute and the identification information of the target container cluster.
  • the processing unit is further configured to disassociate the target customized container cluster management feature from the target container cluster according to the fourth request message.
  • the transceiver unit is further configured to send a fourth response message to the network device, where the fourth response message is used to instruct the CCM to successfully disassociate the target customized container cluster management feature from the target container cluster.
  • the transceiver unit is further configured to receive a fifth request message from the network device, where the fifth request message is used to request deletion of the target customized container cluster management feature; wherein, the fifth request message includes identification information of the target customized container cluster management feature.
  • the processing unit is further configured to delete the target customized container cluster management feature according to the fifth request message.
  • the transceiver unit is further configured to send a fifth response message to the network device, where the fifth response message is used to indicate that the CCM has successfully deleted the target customized container cluster management feature.
  • a network device including:
  • a transceiver unit and a processing unit connected to the transceiver unit.
  • a processing unit is configured to determine to associate the target customized container cluster management feature with the target container cluster.
  • the transceiver unit is configured to send a first request message to the container cluster manager CCM, the first request message is used to request the CCM to associate the target customized container cluster management characteristics with the target container cluster, and the first request message includes the target customized container cluster The identification information of the management characteristic and the identification information of the target container cluster.
  • the network device is a consumer entity of the CCM.
  • the first request message further includes the application range information of the associated operation; the application range information of the associated operation is used to indicate that the target customized container cluster management feature is applied to the target container All namespaces in the cluster; or, the application range information of the associated operation is used to indicate that the target customized container cluster management feature is applied to some namespaces in the target container cluster, and the first request message also includes identification information of some namespaces.
  • the first request message further includes information about consumers in the target container cluster that use the target customized container cluster management feature, and the consumer information that uses the target customized container cluster management feature Consumers are control plane functional entities and/or user plane functional entities.
  • the transceiver unit is further configured to receive a first response message from the CCM, where the first response message is used to indicate that the target customized container cluster management feature is successfully associated with the target container cluster .
  • the processing unit is also used to determine the target file, and the target file includes configuration, status and policy information of deployment and running target customized container cluster management features.
  • the transceiver unit is further configured to send a second request message to the CCM, the second request message is used to request the CCM to load the target file, the second request message includes specific information, and the specific information is used to determine the target file.
  • the transceiver unit is further configured to receive a second response message from the CCM, where the second response message is used to indicate that the CCM has successfully loaded the target file.
  • the target file is a managed container cluster object declarative descriptor MDD file;
  • the specific information includes the identification information of the target file, and/or, the storage path of the target file information.
  • the processing unit is also used to determine the creation target customized container cluster management characteristics.
  • the transceiver unit is further configured to send a third request message to the CCM, where the third request message is used to request the CCM to create a target customized container cluster management feature, and the third request message includes specific information.
  • the transceiver unit is further configured to receive a third response message from the CCM, the third response message is used to instruct the CCM to successfully create the target customized container cluster management feature, the third response message includes the identification information of the target object instance, the target object instance and the target customized It corresponds to the container cluster management feature.
  • the processing unit is further configured to determine to disassociate the target customized container cluster management feature with the target container cluster.
  • the transceiver unit is further configured to send a fourth request message to the CCM, where the fourth request message is used to request that the target customized container cluster management characteristics be disassociated from the target container cluster; wherein, the fourth request message includes the target customized container cluster management characteristics and the identification information of the target container cluster;
  • the transceiver unit is further configured to receive a fourth response message from the CCM, where the fourth response message is used to instruct the CCM to successfully disassociate the target customized container cluster management feature from the target container cluster.
  • the processing unit is also used to determine to delete the target customized container cluster management feature.
  • the transceiver unit is further configured to send a fifth request message to the CCM, where the fifth request message is used to request deletion of the target customized container cluster management feature; wherein, the fifth request message includes identification information of the target customized container cluster management feature.
  • the transceiver unit is further configured to receive a fifth response message from the CCM, where the fifth response message is used to indicate that the CCM has successfully deleted the target customized container cluster management feature.
  • a communication device including a communication interface and a processor.
  • the processor executes the computer program or instruction stored in the memory, so that the communication device executes the method in any possible implementation manner of the first aspect to the second aspect.
  • the memory may be located in the processor, or implemented by a chip independent of the processor, which is not specifically limited in the present application.
  • a computer-readable storage medium including a computer program.
  • the computer program runs on a computer, the computer executes the method in any possible implementation manner of the first aspect to the second aspect.
  • a chip is provided, and a processing circuit is disposed on the chip, and the processing circuit is configured to execute the method in any possible implementation manner of the first aspect to the second aspect.
  • a computer program product includes: a computer program (also referred to as code, or an instruction), when the computer program is executed, the computer executes any one of the first aspect to the second aspect. method in one possible implementation.
  • a computer program also referred to as code, or an instruction
  • FIG 1 shows a system to which this application applies.
  • FIG. 2 shows a system to which this application applies.
  • Fig. 3 shows a schematic flow chart of the solution proposed in this application.
  • Fig. 4 shows a schematic block diagram of a communication device provided by this application.
  • Fig. 5 shows a schematic block diagram of a communication device provided in this application.
  • the network function virtualization (NFV) system mainly includes the following functional entities:
  • Network function virtualization orchestrator (network function virtualization orchestrator, NFVO): NFVO is mainly used for life cycle management of network service (network service, NS) and virtual resources in network function virtualization infrastructure (network functions virtualization infrastructure, NFVI) allocation and scheduling.
  • NFVO can communicate with one or more virtualized network function managers (virtualized network function managers, VNFM) to perform operations related to instantiating NS, such as sending corresponding configuration information to VNFM, and requesting one or more virtual network functions from VNFM ( Virtualized network function (VNF) status information.
  • VNFM Virtualized network function
  • NFVO can also communicate with a virtualized infrastructure manager (virtualized infrastructure manager, VIM), perform allocation and/or reservation of various resources in NFVI, exchange resource configuration and status information, etc.
  • VIM virtualized infrastructure manager
  • VNFM is mainly responsible for the lifecycle management of one or more VNFs, such as instantiating VNFs, updating VNFs, querying VNFs, scaling VNFs, and terminating VNFs.
  • VNFM can communicate with VNF to manage the life cycle of VNF, exchange configuration information and status information with VNF, etc. It can be understood that the NFV system may contain one or more VNFMs, and each VNFM performs life cycle management on different types of VNFs.
  • NFVI refers to the infrastructure of the NFV system, including hardware components, software components and their combination, in order to establish a virtualized environment, deploy, manage and implement VNF in a virtualized environment.
  • NFVI can at least include computing hardware, storage hardware, and network hardware; the virtualization layer of NFVI can abstract the aforementioned hardware, decouple each hardware and VNF, and obtain corresponding virtual computing resources, virtual storage resources, and virtual network resources. , thereby providing a virtualized machine (virtualized machine, VM) and other forms of virtualized containers for the VNF.
  • VM virtualized machine
  • VIM is mainly used to control and manage the interaction between VNF and computing hardware, storage hardware, network hardware, virtual computing resources, virtual storage resources, and virtual network resources.
  • VIM can perform resource management functions, such as adding corresponding virtual resources to virtual machines or other forms of virtual containers, collecting fault information of NFVI during system operation, and so on.
  • the VIM can communicate with the VNFM, such as receiving resource allocation requests from the VNFM, and feeding back resource configuration and status information to the VNFM.
  • VNF The NFV system can include one or more VNFs (usually multiple VNFs), which can run one or more virtual machines or other forms of virtual containers, corresponding to a group of network functions originally implemented by dedicated devices.
  • Element management system (element management system, EMS): EMS can be used to configure and manage VNFs, and initiate life cycle management operations such as instantiation of new VNFs to VNFM. It can be understood that one or more EMSs may be included in the NFV system.
  • OSS/BSS can support various end-to-end telecommunication services.
  • the management functions supported by OSS can include network configuration, service provision, fault management, etc.
  • BSS can be used to process related services such as orders, payment, and income, and support functions such as product management, order management, revenue management, and customer management.
  • the OSS/BSS can serve as a service requester to request the NFVO to instantiate the NS, and the OSS/BSS or the computing device on which the OSS/BSS depends can generally be called a service requester.
  • Cloud native is a new system implementation paradigm for building, running and managing software in a cloud environment. It makes full use of cloud infrastructure and platform services, adapts to the cloud environment, and has (micro) service, elastic scaling, distributed, and high availability.
  • Architectural practices for key features such as , multi-tenancy, and automation.
  • container management into the reference architecture of NFV management and orchestration (MANO) is a key link in the many practices of NFV towards cloud native. For this reason, as shown in Figure 2, the following two new logic functions are introduced in the NFV MANO system.
  • Container infrastructure service management (container infrastructure service management, CISM): CISM is also called CaaS management. The open source prototype is Kubernetes. CISM is responsible for managing the container objects called by the containerized VNF, including the creation, update, and deletion of container objects. In the container cluster node resource pool managed by CISM, container objects are scheduled to corresponding node resources. CISM is also responsible for managing the container infrastructure service (container infrastructure service, CIS) instance of the container user plane process.
  • container infrastructure service container infrastructure service management
  • CCM CIS Cluster Management
  • CCM is also called CIS cluster management.
  • CCM is responsible for managing container clusters, including the creation of node resource pools used by container clusters and node expansion and contraction.
  • BM bare-metal server
  • CISM and CCM are independent logical functions.
  • CCM and CISM can be located in different physical entities.
  • CISM is deployed in VNFM
  • CCM is deployed in VIM; they can also be combined Located in the same physical entity, for example: both are deployed in VNFM.
  • the container cluster management feature is deployed to the container cluster in a static configuration manner. For example, during the process of creating a container cluster, predefined container cluster management features can be added to the container cluster, and during the process of deleting a container cluster, the container cluster management features used by the container cluster can be deleted, so as to realize container cluster management Tight coupling of features to container clusters.
  • deploying container cluster management features in a static configuration manner is increasingly unable to meet the needs of operators, especially in environments where container clusters are applied in multi-tenant management. Operators urgently need a method that can dynamically deploy container cluster management features in container clusters according to the operator's operation and management requirements.
  • the present application proposes a communication method 300, as shown in FIG. 3, for implementing dynamic deployment of container cluster management features.
  • the method 300 is applicable to the systems shown in FIGS. 1 and 2 .
  • the consumer entity of the CCM is NFVO as an example below.
  • the method 300 includes:
  • the NFVO determines to associate the customized container cluster management characteristic #1 (an example of the target customized container cluster management characteristic) with the container cluster #1 (an example of the target container cluster).
  • NFVO may determine to associate the customized container cluster management feature #1 with the container cluster #1 according to requirements (for example, according to the operator's strategy for deploying container clusters).
  • the policy of container cluster #1 deployed by the operator is that container cluster #1 is not associated with customized container cluster management feature #1.
  • the operator adjusts the policy of container cluster #1 so that container cluster #1 is associated with customized container cluster management feature #1.
  • NFVO may determine to associate the customized container cluster management feature #1 with the container cluster #1 according to the adjusted policy of the container cluster #1.
  • the following example illustrates the custom container cluster management feature #1.
  • Customized container cluster management feature #1 can be enhanced for container clusters (CIS cluster enhanced characteristics, CCEC).
  • the open source community prototype of this feature is the custom resource definition (CRD) of Kubernetes.
  • CCD custom resource definition
  • container clusters can support the addition of new enhanced feature capabilities to their baseline feature set.
  • the container cluster enhancement feature CCEC can be applied to container clusters to implement advanced features and operations in container clusters.
  • container cluster enhancement feature the feature of selecting the appropriate container network interface (CNI) plug-in in the implementation of the auxiliary container cluster network
  • CNI container network interface
  • Custom container cluster management feature #1 can be a daemon workload, also known as a daemon object.
  • the prototype of the open source community for this feature is the Kubernetes daemon set, which loads specific-purpose daemons (for example, collecting logs, monitoring status) to CIS cluster nodes, and monitors the running status of CIS cluster nodes.
  • the daemon payload is used to deploy a custom container cluster management feature with the same functionality to all applicable container cluster nodes.
  • a daemon load run a managed CIS cluster object (MCCO) instance on each container cluster node to collect logs, and run an MCCO instance on each container cluster node to monitor Node status, and run an MCCO instance on each container cluster node to dynamically configure routing information.
  • MCCO managed CIS cluster object
  • a CISM instance uses a daemon load to simultaneously control a set of daemons across different container clusters.
  • Custom container cluster management feature #1 may also be another example, which is not limited in this application.
  • Custom container cluster management features can be process-specific (eg, specific binary processes).
  • the NFVO sends a first request message to the CCM, where the first request message is used to request to associate the customized container cluster management feature #1 with the container cluster #1.
  • the CCM receives the first request message.
  • the first request message includes the identification information of the customized container cluster management feature #1 and the identification information of the container cluster #1.
  • the first request message may also include one or more of the following:
  • the application scope information of the associated operation may indicate that the customized container cluster management feature #1 is associated with all namespaces in the container cluster #1.
  • the application scope information of the associated operation may indicate that the customized container cluster management feature #1 is associated with some namespaces in the container cluster #1.
  • the first request message also includes identification information of the part of the namespace.
  • the consumer using the customized container cluster management feature #1 can be a functional entity in the container cluster #1.
  • the functional entity may be a control plane functional entity (for example, a CISM entity) in container cluster #1.
  • the functional entity may be a user plane functional entity (for example, a CIS entity) in container cluster #1.
  • the functional entity may be a control plane functional entity and a user plane functional entity in container cluster #1.
  • the CCM associates the customized container cluster management feature #1 with the container cluster #1 according to the first request message.
  • CCM can create a list of customized container cluster management features associated with container cluster #1 (denoted as list #1), CCM can add customized container cluster management feature #1 in list #1 Identification information, thereby associating the customized container cluster management feature #1 with the container cluster #1.
  • the CCM may also configure the type of the consumer using the customized container cluster management feature #1 in the container cluster #1 according to the first request message.
  • the CCM configures the control plane functional entity in the container cluster #1 to use the customized container cluster management feature #1.
  • the CCM configures the user plane functional entity in the container cluster #1 to use the customized container cluster management feature #1.
  • both the control plane functional entity and the user plane functional entity in the CCM configuration container cluster #1 can use the customized container cluster management feature #1.
  • the CCM can also send a request message #A to NFVO, and the request message #A is used to request the NFVO license to be allocated in the container cluster #1
  • the infrastructure resource used to deploy the custom container cluster management feature #1 (denoted as, infrastructure resource #1).
  • the infrastructure resource #1 may be a virtual machine resource or a bare metal resource.
  • the NFVO may send a response message #A to the CCM, which indicates permission to allocate the infrastructure resource #1 in the container cluster #1.
  • the CCM sends a request message #B to the VIM, and the request message #B is used to request allocation of infrastructure resource #1 for the customized container cluster management feature #1 in the container cluster #1.
  • VIM allocates corresponding infrastructure resource #1 in container cluster #1 according to the request message #B. This process is similar to the resource management granting process of VNF life cycle management (life cycle management, LCM) operation.
  • the CCM can receive the first request message from NFVO, and associate the customized container cluster management feature #1 with the container cluster #1 according to the first request message, thereby realizing the dynamic deployment of the container cluster management feature, which is better meet the needs of operators.
  • the solution for implementing dynamic deployment of container cluster management features in this application does not require interaction between CCM and CISM, which can avoid increasing interoperability and integration costs between container platform layer functions in a multi-vendor environment.
  • the CCM sends a first response message to the NFVO, where the first response message is used to indicate that the customized container cluster management feature #1 is successfully associated with the container cluster #1.
  • the method 300 also includes S301-S309:
  • NFVO determines file #1 (an example of a target file).
  • the file #1 is a template file containing configuration, status and policy information for deploying and running the customized container cluster management feature #1.
  • the file #1 is a managed CIS cluster object (MCCO) declarative descriptor (MCCO declarative descriptor, MDD) file.
  • MCCO is an abstract NFV object used in the container cluster management process, and its characteristics are represented by the object's configuration, state, requested and allocated infrastructure resources, and applicable operation policies.
  • MCCO can represent the managed objects in the following scenarios, embodied as a group of associated containers running on the CIS instance of the container user plane, or as configuration objects in the CISM instance of the container management plane.
  • CCM is responsible for the lifecycle management of MCCOs, for example, by requesting CISM to create and deploy MCCOs through daemon workload objects, install MCCOs to container clusters, delete MCCOs from container clusters, etc.
  • CCM is also responsible for requesting permission from NFVO to deploy resources required for MCCO instances.
  • MDD is a template file used to describe the basic characteristics of MCCO, for example, the desired state of MCCO is included in the file.
  • the MDD file can be implemented using a native descriptor template (native descriptor) file used by the open source community.
  • this file #1 includes one or more of the following information:
  • Deploy the computing resources, storage resources, and network resource information required by the customized container cluster management feature #1 deploy and access the security authentication mechanism of the customized container cluster management feature #1 role-based access control (RBAC) ) information to monitor the information of the cloud provider controller (cloud provider controller) running in the customized container cluster management feature #1.
  • RBAC role-based access control
  • the operator can configure the file #1 to the NFVO, and further, the NFVO can store the file #1 in a corresponding storage space.
  • the NFVO sends a second request message to the CCM, where the second request message is used to request the CCM to load the file #1.
  • the second request message includes information #A, and the information #A is used to determine the file #1.
  • the information #A includes the identification information of the file #1.
  • the information #A includes the access path information of the file #1.
  • the CCM determines file #1 according to information #A, and verifies whether file #1 can be loaded.
  • the CCM may verify the authentication mechanism of the file #1, for example, the integrity, authenticity, validity, usability, etc. of the file #1 in the container cluster.
  • the CCM can also verify that the mandatory attributes in Document #1 are in place.
  • File #1 is able to load.
  • the CCM may store the file #1 in a corresponding storage space, and the storage space may be a local storage space of the CCM or a storage space of other devices. It should be understood that the CCM has the right to access the storage space.
  • the CCM sends a second response message to the NFVO, where the second response message is used to indicate whether the CCM successfully loads the file #1.
  • S301-S305 may also exist independently, that is, other steps in this application may not be included after S301-S305.
  • the NFVO determines that it is necessary to create a customized container cluster management feature #1.
  • NFVO can determine the need to create a customized container cluster management feature #1 according to the needs (eg, according to the operator's strategy for deploying container clusters).
  • the NFVO sends a third request message to the CCM, where the third request message is used to request creation of the customized container cluster management feature #1.
  • the CCM receives the third request message.
  • the third request message includes the identification information of file #1.
  • the CCM creates a customized container cluster management feature #1 according to the third request message.
  • the CCM can access file #1 according to the identification information of file #1 in the third request message, and analyze the deployment information of object instance #1 in file #1, and create object instance #1 according to the deployment information of object instance #1.
  • the object instance #1 corresponds to the custom container cluster management feature #1. That is, the object instance #1 is an abstract expression of the customized container cluster management feature #1.
  • the object instance #1 may be a managed container cluster object (managed CIS cluster object, MCCO) instance #1.
  • managed container cluster object managed CIS cluster object, MCCO
  • the CCM sends a third response message to the NFVO, where the third response message is used to instruct the CCM to successfully create the customized container cluster management feature #1.
  • the third response message includes identification information of object instance #1 (eg, MCCO instance #1).
  • S306-S309 may also exist independently, that is, other steps in this application may not be included before and after S306-S309.
  • the method 300 further includes S341-S344:
  • the NFVO determines to disassociate the customized container cluster management feature #1 from the container cluster #1.
  • NFVO may determine to disassociate the customized container cluster management feature #1 from the container cluster #1 according to requirements (for example, according to the operator's strategy for deploying container clusters).
  • disassociation means disassociation
  • the NFVO sends a fourth request message to the CCM, where the fourth request message is used to request the CCM to disassociate the customized container cluster management feature #1 from the container cluster #1.
  • the CCM receives the fourth request message.
  • the fourth request message includes the identification information of the customized container cluster management feature #1 and the identification information of the container cluster #1.
  • the CCM disassociates the customized container cluster management feature #1 from the container cluster #1 according to the fourth request message.
  • the CCM can delete the identification information of the customized container cluster management feature #1 from the list #1 above.
  • the CCM may receive the fourth request message from the NFVO, and complete the disassociation of the customized container cluster management feature #1 from the container cluster #1 according to the fourth request message.
  • the solution of this application can dynamically de-associate the customized container cluster management features with the container cluster without accompanying the deletion process of the container cluster, which better meets the ever-changing container cluster management needs of operators.
  • the CCM sends a fourth response message to the NFVO, where the fourth response message is used to indicate that the CCM successfully disassociates the customized container cluster management feature #1 from the container cluster #1.
  • S341-S344 may also exist independently.
  • S341-S344 are not performed on the basis of S310-S340.
  • the CCM disassociates the customized management feature #1 from the container cluster #1, it may not execute S310-S340 to dynamically associate the customized management feature #1 with the container cluster #1.
  • the method 300 further includes S345-S348:
  • NFVO determines to delete the customized container cluster management feature #1.
  • NFVO can determine to delete the customized container cluster management feature #1 according to requirements (for example, according to the operator's strategy for deploying container clusters).
  • the NFVO sends a fifth request message to the CCM, where the fifth request message is used to request to delete the customized container cluster management feature #1.
  • the CCM receives the fifth request message.
  • the fifth request message includes the identification information of the customized container cluster management feature #1.
  • the CCM deletes the customized container cluster management feature #1 according to the fifth request message.
  • the CCM needs to determine whether there is a container cluster using the customized container cluster management feature #1. For example, CCM determines that container cluster #1 is using customized container cluster management feature #1. At this time, the CCM may firstly disassociate the customized container cluster management feature #1 from the container cluster #1, and then delete the customized container cluster management feature #1.
  • the CCM sends a fifth response message to the NFVO, where the fifth response message is used to indicate that the CCM has successfully deleted the customized container cluster management feature #1.
  • S345-S348 can also exist independently.
  • S345-S348 are not performed on the basis of S310-S340.
  • the CCM deletes the customized management feature #1, it may not perform S310-S340 to dynamically associate the customized management feature #1 with the container cluster #1.
  • FIG. 4 is a communication device provided in an embodiment of the present application, and the communication device includes a transceiver unit 401 and a processing unit 402 .
  • the transceiver unit 401 may be used to implement a corresponding communication function.
  • the transceiver unit 401 may also be called a communication interface or a communication unit.
  • the processing unit 402 may be configured to perform processing operations.
  • the device further includes a storage unit, which can be used to store instructions and/or data, and the processing unit 402 can read the instructions and/or data in the storage unit, so that the device implements the above-mentioned method embodiments. action of the device.
  • a storage unit which can be used to store instructions and/or data
  • the processing unit 402 can read the instructions and/or data in the storage unit, so that the device implements the above-mentioned method embodiments. action of the device.
  • the device may be the CCM in the foregoing embodiments, or a component (such as a chip) of the CCM.
  • the transceiver unit is configured to receive a first request message from the network device, and the first request message is used to request the CCM to associate the target customized container cluster management feature with the target container cluster; the processing unit is configured to associate Target customized container cluster management features and target container clusters.
  • the transceiver unit is further configured to send a first response message to the network device, where the first response message is used to indicate that the target customized container cluster management feature is successfully associated with the target container cluster.
  • the transceiver unit is further configured to receive a second request message from the network device, the second request message is used to request the CCM to load the target file; the processing unit is also configured to determine the target file according to the second request message, And verify whether the target file can be loaded; in the case that the target file can be loaded, the processing unit is also used to load the target file; the transceiver unit is also used to send a second response message to the network device, and the second response message is used to indicate the CCM Target file loaded successfully.
  • the transceiver unit is further configured to receive a third request message from the network device, the third request message is used to request the CCM to create a target customized container cluster management feature; the processing unit is further configured to receive the third request message according to the third request message , to determine the target file; the processing unit is also used to create a target object instance according to the deployment information in the target file; the transceiver unit is also used to send a third response message to the network device, and the third response message is used to indicate that the CCM has successfully created the target Customized container cluster management features, the third response message includes identification information of the target object instance.
  • the transceiver unit is further configured to receive a fourth request message from the network device, and the fourth request message is used to request to disassociate the target customized container cluster management feature from the target container cluster; the processing unit is also configured to According to the fourth request message, the management characteristics of the target customized container cluster are de-associated with the target container cluster; the transceiver unit is also used to send a fourth response message to the network device, and the fourth response message is used to indicate that the CCM successfully associates the target customized container cluster Management properties are disassociated from the target container cluster.
  • the transceiver unit is further configured to receive a fifth request message from the network device, the fifth request message is used to request to delete the target customized container cluster management feature; the processing unit is further configured to receive the fifth request message according to the fifth request message to delete the target customized container cluster management feature; the transceiver unit is further configured to send a fifth response message to the network device, where the fifth response message is used to instruct the CCM to successfully delete the target customized container cluster management feature.
  • the device may be the NFVO in the foregoing embodiments, or a component (such as a chip) of the NFVO.
  • processing unit is used to determine to associate the target customized container cluster management feature with the target container cluster; Customized container cluster management features are associated with the target container cluster.
  • the processing unit is also used to determine the target file; the transceiver unit is also used to send a second request message to the CCM, and the second request message is used to request the CCM to load the target file; the transceiver unit is also used to receive the target file from the CCM A second response message, where the second response message is used to indicate that the CCM has successfully loaded the target file.
  • the processing unit is further configured to determine the management characteristics of the target customized container cluster; the transceiver unit is further configured to send a third request message to the CCM, and the third request message is used to request the CCM to create the target customized container cluster The management feature; the transceiver unit is further configured to receive a third response message from the CCM, where the third response message is used to instruct the CCM to successfully create the target customized container cluster management feature.
  • the processing unit is further configured to determine to disassociate the target customized container cluster management feature from the target container cluster; the transceiver unit is further configured to send a fourth request message to the CCM, and the fourth request message is used to request the The target customized container cluster management feature is de-associated from the target container cluster; the transceiver unit is also configured to receive a fourth response message from the CCM, and the fourth response message is used to instruct the CCM to successfully de-associate the target customized container cluster management feature from the target container cluster associated.
  • the processing unit is further configured to determine to delete the target customized container cluster management feature; the transceiver unit is further configured to send a fifth request message to the CCM, and the fifth request message is used to request that the target customized container cluster Deletion of management characteristics; the transceiver unit is further configured to receive a fifth response message from the CCM, where the fifth response message is used to indicate that the CCM has successfully deleted the management characteristics of the target customized container cluster.
  • unit here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor for executing one or more software or firmware programs (such as a shared processor, a dedicated processor, or a group processor, etc.) and memory, incorporated logic, and/or other suitable components to support the described functionality.
  • ASIC application specific integrated circuit
  • processor for executing one or more software or firmware programs (such as a shared processor, a dedicated processor, or a group processor, etc.) and memory, incorporated logic, and/or other suitable components to support the described functionality.
  • the device may specifically be the first network element in the above embodiments, and may be used to execute each process corresponding to the first network element in the above method embodiments and/or steps, or, the device may specifically be the network management network element in the above embodiments, and may be used to execute the various processes and/or steps corresponding to the network management network elements in the above method embodiments. In order to avoid repetition, it is not repeated here repeat.
  • the above-mentioned communication device has the function of implementing the corresponding steps performed by the device in the above-mentioned method.
  • the functions may be implemented by hardware, or may be implemented by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver ), and other units, such as a processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.
  • transceiver unit 401 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit.
  • the device in FIG. 4 may be the device in the foregoing method embodiment, or may be a chip or a chip system, for example: a system on chip (system on chip, SoC).
  • the transceiver unit may be an input-output circuit or a communication interface;
  • the processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip. It is not limited here.
  • the embodiment of the present application also provides a communication device, as shown in FIG. 5 , including: a processor 501 and a communication interface 502 .
  • the processor 501 is configured to execute computer programs or instructions stored in the memory 503, or read data stored in the memory 503, so as to execute the methods in the above method embodiments.
  • the communication interface 502 is used for receiving and/or sending signals.
  • the processor 501 is configured to control the communication interface 502 to receive and/or send signals.
  • the communication device further includes a memory 503, and the memory 503 is used to store computer programs or instructions and/or data.
  • the memory 503 can be integrated with the processor 501, or can also be set separately.
  • the processor 501, the communication interface 502, and the memory 503 are connected to each other through a bus 504;
  • the bus 504 may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA ) bus, etc.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the above-mentioned bus 504 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used in FIG. 5 , but it does not mean that there is only one bus or one type of bus.
  • the communication device is used to implement the operations performed by the CCM or the NFVO in each method embodiment above.
  • the processor 501 is configured to execute computer programs or instructions stored in the memory 503, so as to implement related operations of the CCM in each method embodiment above.
  • the processor 501 is configured to execute the computer programs or instructions stored in the memory 503, so as to implement related operations of the NFVO in each method embodiment above.
  • the processor (such as the processor 501) mentioned in the embodiment of the present application may be a central processing unit (central processing unit, CPU), a network processor (network processor, NP) or a combination of CPU and NP.
  • the processor may further include hardware chips.
  • the aforementioned hardware chip may be an application-specific integrated circuit (application-specific integrated circuit, ASIC), a programmable logic device (programmable logic device, PLD) or a combination thereof.
  • the aforementioned PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL) or any combination thereof.
  • the memory (such as the memory 503 ) mentioned in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM), which acts as external cache memory.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

Landscapes

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

Abstract

本申请实施例提供了一种通信方法和装置。该方法包括：容器集群管理CCM从网络设备接收第一请求消息，第一请求消息用于请求CCM将目标定制化容器集群管理特性与目标容器集群进行关联，第一请求消息包括目标定制化容器集群管理特性的标识信息以及目标容器集群的标识信息；其中，网络设备为CCM的消费者实体；CCM根据第一请求消息关联目标定制化容器集群管理特性与目标容器集群。根据本申请的方案，可以实现容器集群管理特性的动态部署，更好地满足了运营商的需求。此外，本申请提出的实现容器集群管理特性动态部署的方案不需要CCM与CISM之间进行交互，可以避免增加容器平台层功能之间在多厂商环境下的互操作集成成本。

Description

通信方法和装置
本申请要求于2021年11月05日提交中国专利局、申请号为202111303494.7、申请名称为“通信方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，并且更具体地，涉及一种通信方法和装置。
背景技术
当前，容器集群管理特性是采用静态配置的方式部署到容器集群中的。例如，在创建容器集群的过程中可以将预定义的容器集群管理特性加入到容器集群中，在删除一个容器集群的过程中伴随删除该容器集群所使用的容器集群管理特性，从而实现容器集群管理特性与容器集群的紧耦合。然而，采用静态配置的方式部署容器集群管理特性越来越无法满足运营商的需求，特别是在容器集群应用在多租户管理的环境中。运营商迫切地需要一种可以按照运营商的运营管理需求在容器集群中动态地部署容器集群管理特性的方法。因此，如何实现容器集群管理特性的动态部署是一个亟待解决的问题。
发明内容
本申请实施例提供一种通信方法和装置，可以实现容器集群管理特性的动态部署。
第一方面，提供了一种通信方法，包括：
容器集群管理CCM从网络设备接收第一请求消息，第一请求消息用于请求CCM将目标定制化容器集群管理特性与目标容器集群进行关联，第一请求消息包括目标定制化容器集群管理特性的标识信息以及目标容器集群的标识信息；其中，网络设备为CCM的消费者实体；CCM根据第一请求消息关联目标定制化容器集群管理特性与目标容器集群。
在一种可能的实现方式中，该网络设备为网络功能虚拟化编排器NFVO。
根据本申请的方案，CCM可以从NFVO接收第一请求消息，并根据第一请求消息关联目标定制化容器集群管理特性与目标容器集群，从而实现了容器集群管理特性的动态部署，更好地满足了运营商的需求。此外，本申请提出的实现容器集群管理特性动态部署的方案不需要CCM与CISM之间进行交互，可以避免增加容器平台层功能之间互操作的多厂商环境集成成本。
结合第一方面，在第一方面的某些实现方式中，第一请求消息中还包括关联操作的应用范围信息；关联操作的应用范围信息用于指示目标定制化容器集群管理特性应用于目标容器集群中的全部命名空间；或者，关联操作的应用范围信息用于指示目标定制化容器集群管理特性应用于目标容器集群中的部分命名空间，第一请求消息中还包括部分命名空间的标识信息。
结合第一方面，在第一方面的某些实现方式中，第一请求消息中还包括目标容器集群中使用目标定制化容器集群管理特性的消费者的信息，使用目标定制化容器集群管理特性的消费者为控制面功能实体和/或用户面功能实体。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：
CCM向网络设备发送第一响应消息，第一响应消息用于指示目标定制化容器集群管理特性与目标容器集群成功关联。
结合第一方面，在第一方面的某些实现方式中，在CCM从网络设备接收第一请求消息之前，该方法还包括：
CCM从网络设备接收第二请求消息，第二请求消息用于请求CCM加载目标文件，第二请求消息中包括特定信息，特定信息用于确定目标文件；其中，目标文件包括部署和运行目标定制化容器集群管理特性的配置、状态及策略信息；CCM根据第二请求消息，确定目标文件，并验证目标文件是否能够加载；在目标文件能够加载的情况下，CCM加载目标文件；CCM向网络设备发送第二响应消息，第二响应消息用于指示CCM成功加载目标文件。
结合第一方面，在第一方面的某些实现方式中，目标文件为被管理的容器集群对象声明式描述符MDD文件；特定信息包括目标文件的标识信息，和/或，目标文件的存储路径信息。
结合第一方面，在第一方面的某些实现方式中，在CCM加载目标文件之后，该方法还包括：
CCM从网络设备接收第三请求消息，第三请求消息用于请求CCM创建目标定制化容器集群管理特性，第三请求消息包括特定信息；CCM根据第三请求消息，确定目标文件；CCM根据目标文件中的部署信息，创建目标对象实例，目标对象实例与目标定制化容器集群管理特性对应；CCM向网络设备发送第三响应消息，第三响应消息用于指示CCM成功创建目标定制化容器集群管理特性，第三响应消息包括目标对象实例的标识信息。
结合第一方面，在第一方面的某些实现方式中，在CCM将目标定制化容器集群管理特性与目标容器集群进行关联之后，该方法还包括：
CCM从网络设备接收第四请求消息，第四请求消息用于请求将目标定制化容器集群管理特性与目标容器集群去关联；其中，第四请求消息包括目标定制化容器集群管理特性的标识信息与目标容器集群的标识信息；CCM根据第四请求消息将目标定制化容器集群管理特性与目标容器集群去关联；CCM向网络设备发送第四响应消息，第四响应消息用于指示CCM成功将目标定制化容器集群管理特性与目标容器集群去关联。
根据本申请的方案，CCM可以从NFVO接收第四请求消息，并根据第四请求消息完成目标定制化容器集群管理特性与目标容器集群的去关联，从而实现了不需要将容器集群删除即可动态地将定制化容器集群管理特性从容器集群中移出，更好地满足了运营商的需求。
根据本申请的方案，CCM可以从NFVO接收第四请求消息，并根据第四请求消息完成目标定制化容器集群管理特性与目标容器集群的去关联。相比之下，本申请的方案不需要伴随容器集群的删除过程即可动态地将定制化容器集群管理特性与容器集群去关联，更好地满足了运营商不断变化的需求。
结合第一方面，在第一方面的某些实现方式中，在CCM将目标定制化容器集群管理特性与目标容器集群去关联之后，该方法还包括：
CCM从网络设备接收第五请求消息，第五请求消息用于请求将目标定制化容器集群管理特性删除；其中，第五请求消息包括目标定制化容器集群管理特性的标识信息；CCM根据第五请求消息，将目标定制化容器集群管理特性删除；CCM向网络设备发送第五响应消息，第五响应消息用于指示CCM成功将目标定制化容器集群管理特性删除。
第二方面，提供了一种通信方法，包括：
网络设备确定将目标定制化容器集群管理特性与目标容器集群进行关联；网络设备向容器集群管理器CCM发送第一请求消息，第一请求消息用于请求CCM将目标定制化容器集群管理特性与目标容器集群进行关联，第一请求消息包括目标定制化容器集群管理特性的标识信息以及目标容器集群的标识信息；其中，网络设备为CCM的消费者实体。
在一种可能的实现方式中，该网络设备为网络功能虚拟化编排器NFVO。
根据本申请的方案，NFVO可以确定需要将目标定制化容器集群管理特性与目标容器集群进行关联，进一步地，NFVO向CCM发送第一请求消息，使得CCM根据第一请求消息关联目标定制化容器集群管理特性与目标容器集群，从而实现了容器集群管理特性的动态部署，更好地满足了运营商的需求。此外，本申请提出的实现容器集群管理特性动态部署的方案不需要CCM与CISM之间进行交互，可以避免增加容器平台层功能之间互操作的多厂商环境集成成本。
结合第二方面，在第二方面的某些实现方式中，第一请求消息中还包括关联操作的应用范围信息；关联操作的应用范围信息用于指示目标定制化容器集群管理特性应用于目标容器集群中的全部命名空间；或者，关联操作的应用范围信息用于指示目标定制化容器集群管理特性应用于目标容器集群中的部分命名空间，第一请求消息中还包括部分命名空间的标识信息。
结合第二方面，在第二方面的某些实现方式中，第一请求消息中还包括目标容器集群中使用目标定制化容器集群管理特性的消费者的信息，使用目标定制化容器集群管理特性的消费者为控制面功能实体和/或用户面功能实体。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：
网络设备从CCM接收第一响应消息，第一响应消息用于指示目标定制化容器集群管理特性与目标容器集群成功关联。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：
网络设备确定目标文件，目标文件包括部署和运行目标定制化容器集群管理特性的配置、状态及策略信息；网络设备向CCM发送第二请求消息，第二请求消息用于请求CCM加载目标文件，第二请求消息中包括特定信息，特定信息用于确定目标文件；网络设备从CCM接收第二响应消息，第二响应消息用于指示CCM成功加载目标文件。
结合第二方面，在第二方面的某些实现方式中，目标文件为被管理的容器集群对象声明式描述符MDD文件；特定信息包括目标文件的标识信息，和/或，目标文件的存储路径信息。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：
网络设备确定创建目标定制化容器集群管理特性；网络设备向CCM发送第三请求消 息，第三请求消息用于请求CCM创建目标定制化容器集群管理特性，第三请求消息包括特定信息；网络设备从CCM接收第三响应消息，第三响应消息用于指示CCM成功创建目标定制化容器集群管理特性，第三响应消息包括目标对象实例的标识信息，目标对象实例与目标定制化容器集群管理特性对应。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：
网络设备确定将目标定制化容器集群管理特性与目标容器集群去关联；网络设备向CCM发送第四请求消息，第四请求消息用于请求将目标定制化容器集群管理特性与目标容器集群去关联；其中，第四请求消息包括目标定制化容器集群管理特性的标识信息与目标容器集群的标识信息；网络设备从CCM接收第四响应消息，第四响应消息用于指示CCM成功将目标定制化容器集群管理特性与目标容器集群去关联。
根据本申请的方案，当需要将目标定制化容器集群管理特性与目标容器集群去关联时，可以由NFVO向CCM发送第四请求消息，使得CCM根据第四请求消息完成目标定制化容器集群管理特性与目标容器集群的去关联，从而实现了不需要将容器集群删除即可动态地将定制化容器集群管理特性从容器集群中移出，更好地满足了运营商的需求。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：
网络设备确定将目标定制化容器集群管理特性删除；网络设备向CCM发送第五请求消息，第五请求消息用于请求将目标定制化容器集群管理特性删除；其中，第五请求消息包括目标定制化容器集群管理特性的标识信息；网络设备从CCM接收第五响应消息，第五响应消息用于指示CCM成功将目标定制化容器集群管理特性删除。
第三方面，提供了一种容器集群管理器CCM，包括：
收发单元，以及与收发单元连接的处理单元。
收发单元，用于从网络设备接收第一请求消息，第一请求消息用于请求CCM将目标定制化容器集群管理特性与目标容器集群进行关联，第一请求消息包括目标定制化容器集群管理特性的标识信息以及目标容器集群的标识信息；其中，网络设备为CCM的消费者实体。
处理单元，用于根据第一请求消息关联目标定制化容器集群管理特性与目标容器集群。
结合第三方面，在第三方面的某些实现方式中，第一请求消息中还包括关联操作的应用范围信息；关联操作的应用范围信息用于指示目标定制化容器集群管理特性应用于目标容器集群中的全部命名空间；或者，关联操作的应用范围信息用于指示目标定制化容器集群管理特性应用于目标容器集群中的部分命名空间，第一请求消息中还包括部分命名空间的标识信息。
结合第三方面，在第三方面的某些实现方式中，第一请求消息中还包括目标容器集群中使用目标定制化容器集群管理特性的消费者的信息，使用目标定制化容器集群管理特性的消费者为控制面功能实体和/或用户面功能实体。
结合第三方面，在第三方面的某些实现方式中：
收发单元，还用于向网络设备发送第一响应消息，第一响应消息用于指示目标定制化容器集群管理特性与目标容器集群成功关联。
结合第三方面，在第三方面的某些实现方式中：
收发单元，还用于从网络设备接收第二请求消息，第二请求消息用于请求CCM加载目标文件，第二请求消息中包括特定信息，特定信息用于确定目标文件；其中，目标文件包括部署和运行目标定制化容器集群管理特性的配置、状态及策略信息。
处理单元，还用于根据第二请求消息，确定目标文件，并验证目标文件是否能够加载。
在目标文件能够加载的情况下，处理单元，还用于加载目标文件。
收发单元，还用于向网络设备发送第二响应消息，第二响应消息用于指示CCM成功加载目标文件。
结合第三方面，在第三方面的某些实现方式中，目标文件为被管理的容器集群对象声明式描述符MDD文件；特定信息包括目标文件的标识信息，和/或，目标文件的存储路径信息。
结合第三方面，在第三方面的某些实现方式中：
收发单元，还用于从网络设备接收第三请求消息，第三请求消息用于请求CCM创建目标定制化容器集群管理特性，第三请求消息包括特定信息。
处理单元，还用于根据第三请求消息，确定目标文件。
处理单元，还用于根据目标文件中的部署信息，创建目标对象实例，目标对象实例与目标定制化容器集群管理特性对应。
收发单元，还用于向网络设备发送第三响应消息，第三响应消息用于指示CCM成功创建目标定制化容器集群管理特性，第三响应消息包括目标对象实例的标识信息。
结合第三方面，在第三方面的某些实现方式中：
收发单元，还用于从网络设备接收第四请求消息，第四请求消息用于请求将目标定制化容器集群管理特性与目标容器集群去关联；其中，第四请求消息包括目标定制化容器集群管理特性的标识信息与目标容器集群的标识信息。
处理单元，还用于根据第四请求消息将目标定制化容器集群管理特性与目标容器集群去关联。
收发单元，还用于向网络设备发送第四响应消息，第四响应消息用于指示CCM成功将目标定制化容器集群管理特性与目标容器集群去关联。
结合第三方面，在第三方面的某些实现方式中：
收发单元，还用于从网络设备接收第五请求消息，第五请求消息用于请求将目标定制化容器集群管理特性删除；其中，第五请求消息包括目标定制化容器集群管理特性的标识信息。
处理单元，还用于根据第五请求消息，将目标定制化容器集群管理特性删除。
收发单元，还用于向网络设备发送第五响应消息，第五响应消息用于指示CCM成功将目标定制化容器集群管理特性删除。
第四方面，提供一种网络设备，包括：
收发单元，以及与收发单元连接的处理单元。
处理单元，用于确定将目标定制化容器集群管理特性与目标容器集群进行关联。
收发单元，用于向容器集群管理器CCM发送第一请求消息，第一请求消息用于请求CCM将目标定制化容器集群管理特性与目标容器集群进行关联，第一请求消息包括目标定制化容器集群管理特性的标识信息以及目标容器集群的标识信息。
其中，网络设备为CCM的消费者实体。
结合第四方面，在第四方面的某些实现方式中，第一请求消息中还包括关联操作的应用范围信息；关联操作的应用范围信息用于指示目标定制化容器集群管理特性应用于目标容器集群中的全部命名空间；或者，关联操作的应用范围信息用于指示目标定制化容器集群管理特性应用于目标容器集群中的部分命名空间，第一请求消息中还包括部分命名空间的标识信息。
结合第四方面，在第四方面的某些实现方式中，第一请求消息中还包括目标容器集群中使用目标定制化容器集群管理特性的消费者的信息，使用目标定制化容器集群管理特性的消费者为控制面功能实体和/或用户面功能实体。
结合第四方面，在第四方面的某些实现方式中，收发单元，还用于从CCM接收第一响应消息，第一响应消息用于指示目标定制化容器集群管理特性与目标容器集群成功关联。
结合第四方面，在第四方面的某些实现方式中：
处理单元，还用于确定目标文件，目标文件包括部署和运行目标定制化容器集群管理特性的配置、状态及策略信息。
收发单元，还用于向CCM发送第二请求消息，第二请求消息用于请求CCM加载目标文件，第二请求消息中包括特定信息，特定信息用于确定目标文件。
收发单元，还用于从CCM接收第二响应消息，第二响应消息用于指示CCM成功加载目标文件。
结合第四方面，在第四方面的某些实现方式中，目标文件为被管理的容器集群对象声明式描述符MDD文件；特定信息包括目标文件的标识信息，和/或，目标文件的存储路径信息。
结合第四方面，在第四方面的某些实现方式中：
处理单元，还用于确定创建目标定制化容器集群管理特性。
收发单元，还用于向CCM发送第三请求消息，第三请求消息用于请求CCM创建目标定制化容器集群管理特性，第三请求消息包括特定信息。
收发单元，还用于从CCM接收第三响应消息，第三响应消息用于指示CCM成功创建目标定制化容器集群管理特性，第三响应消息包括目标对象实例的标识信息，目标对象实例与目标定制化容器集群管理特性对应。
结合第四方面，在第四方面的某些实现方式中：
处理单元，还用于确定将目标定制化容器集群管理特性与目标容器集群去关联。
收发单元，还用于向CCM发送第四请求消息，第四请求消息用于请求将目标定制化容器集群管理特性与目标容器集群去关联；其中，第四请求消息包括目标定制化容器集群管理特性的标识信息与目标容器集群的标识信息；
收发单元，还用于从CCM接收第四响应消息，第四响应消息用于指示CCM成功将目标定制化容器集群管理特性与目标容器集群去关联。
结合第四方面，在第四方面的某些实现方式中：
处理单元，还用于确定将目标定制化容器集群管理特性删除。
收发单元，还用于向CCM发送第五请求消息，第五请求消息用于请求将目标定制化 容器集群管理特性删除；其中，第五请求消息包括目标定制化容器集群管理特性的标识信息。
收发单元，还用于从CCM接收第五响应消息，第五响应消息用于指示CCM成功将目标定制化容器集群管理特性删除。
第五方面，提供一种通信设备，包括通信接口和处理器。当该通信设备运行时，处理器执行存储器存储的计算机程序或指令，使得该通信设备执行第一方面至第二方面中任一种可能实现方式中的方法。该存储器可以位于处理器中，也可以为与处理器通过相互独立的芯片来实现，本申请对此不具体限定。
第六方面，提供一种计算机可读存储介质，包括计算机程序，当计算机程序在计算机上运行时，使得计算机执行第一方面至第二方面中任一种可能实现方式中的方法。
第七方面，提供一种芯片，芯片上设置有处理电路，处理电路用于执行该第一方面至第二方面中任一种可能实现方式中的方法。
第八方面，提供了一种计算机程序产品，计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当计算机程序被运行时，使得计算机执行第一方面至第二方面中任一种可能实现方式中的方法。
附图说明
图1示出了本申请适用的系统。
图2示出了本申请适用的系统。
图3示出了本申请提出的方案的示意性流程图。
图4示出本申请提供的通信装置的一种示意性框图。
图5示出本申请提供的通信设备的一种示意性框图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
首先结合图1和图2对本申请实施例适用的系统进行说明。
网络功能虚拟化(network function virtualisation，NFV)系统主要包括如下功能实体：
网络功能虚拟化编排器(network function virtualisation orchestrator，NFVO)：NFVO主要用于负责网络服务(network service，NS)的生命周期管理，负责网络功能虚拟基础设施(network functions virtualisation infrastructure，NFVI)中虚拟资源的分配和调度。NFVO可以与一个或多个虚拟网络功能管理器(virtualised network function manager，VNFM)通信，执行实例化NS的相关操作，比如向VNFM发送相应的配置信息、从VNFM请求一个或多个虚拟网络功能(virtualised network function，VNF)的状态信息。另外，NFVO还可以与虚拟基础设施管理器(virtualised infrastructure manager，VIM)通信，执行对NFVI中的各项资源进行分配和/或预留，交换资源配置和状态信息等。
VNFM：VNFM主要负责一个或多个VNF的生命周期管理，比如实例化(instantiating)VNF、更新(updating)VNF、查询VNF、弹性伸缩(scaling)VNF、终止(terminating)VNF等。VNFM可以与VNF通信，从而管理VNF的生命周期、与VNF交换配置信息和状态信息等。可以理解，NFV系统中可以包含一个或多个VNFM，各个VNFM分别对不同类型的 VNF进行生命周期管理。
NFVI：NFVI指的是NFV系统的基础设施，包含硬件部件、软件部件及其结合，以便建立虚拟化环境，在虚拟化环境中部署、管理及实现VNF。NFVI至少可以包含计算(computing)硬件、存储硬件、网络硬件；NFVI的虚拟化层可以对前述各个硬件进行抽象，解耦各个硬件与VNF，得到相应的虚拟计算资源、虚拟存储资源、虚拟网络资源，从而为VNF提供虚拟机(virtualised machine，VM)以及其它形式的虚拟化容器。
VIM：VIM主要用于控制和管理VNF与计算硬件、存储硬件、网络硬件、虚拟计算资源、虚拟存储资源、虚拟网络资源的交互。比如，VIM可以执行资源管理功能，具体如向虚拟机或其它形式的虚拟容器增加相应的虚拟资源、搜集NFVI在系统运行过程中的故障信息等。另外，VIM可以和VNFM进行通信，比如接收来自VNFM的资源分配请求、向VNFM反馈资源配置和状态信息等。
VNF：NFV系统中可以包括一个或多个VNF(通常是多个VNF)，可以运行一个或多个虚拟机或其它形式的虚拟容器，对应于一组原本由专用设备实现的网络功能。
网元管理系统(element management system，EMS)：EMS可以用于对VNF进行配置和管理，以及向VNFM发起新的VNF的实例化等生命周期管理操作。可以理解，NFV系统中可以包括一个或多个EMS。
运营支持系统(operations support system，OSS)或者业务支持系统(business support system，BSS)：OSS/BSS可以支持各种端到端的电信业务。其中，OSS支持的管理功能可以包括网络配置、业务提供、故障管理等；BSS可以用于处理订单、付费、收入等相关业务，支持产品管理、订单管理、收益管理及客户管理等功能。需要说明的是，OSS/BSS可以作为业务请求方请求NFVO实例化NS，OSS/BSS或OSS/BSS所依赖的计算设备通常可以对应称为业务请求方。
可以理解，如图1所示的NFV系统中，前述各个功能实体可以各自部署在不同的计算设备中，也可能将部分功能实体集成到同一个计算设备中。不予限制。
此外，电信网络变革正经历着从NFV向云原生(cloud-native)演进的进程中。云原生是在云环境下构建、运行和管理软件的一种新的系统实现范式，充分利用云基础设施和平台服务，适应云环境，具备(微)服务化、弹性伸缩、分布式、高可用、多租户和自动化等关键特征的架构实践。在这场变革中，在NFV管理编排(management and orchestration,MANO)的参考架构内引入容器管理是NFV走向云原生的众多实践的关键一环。为此，如图2所示，在NFV MANO系统中引入了如下两个新的逻辑功能。
容器基础设施服务管理(container infrastructure service management,CISM)：CISM也称为CaaS管理，开源原型是Kubernetes，CISM负责管理容器化VNF所调用的容器对象，包括容器对象的创建、更新和删除，并在CISM纳管的容器集群节点资源池中将容器对象调度到相应的节点资源上。CISM也负责管理容器用户面的进程容器基础设施服务(container infrastructure service,CIS)实例。
容器集群管理(CIS Cluster Management,CCM)：CCM也称为CIS集群管理，CCM负责对容器集群进行管理，包括容器集群所使用的节点资源池的创建和节点扩缩容。
例如，在指定的容器集群节点资源池中分配新的虚拟机或裸金属服务器(bare-metal machine，BM)。
应理解，CISM和CCM都是独立的逻辑功能，在功能部署的过程中，CCM可以和CISM可以分设在不同的物理实体中，例如：CISM部署在VNFM中，CCM部署在VIM中；也可以合设在同一物理实体中，例如：两者都部署在VNFM中。
当前，容器集群管理特性是采用静态配置的方式部署到容器集群中的。例如，在创建容器集群的过程中可以将预定义的容器集群管理特性加入到容器集群中，在删除一个容器集群的过程中伴随删除该容器集群所使用的容器集群管理特性，从而实现容器集群管理特性与容器集群的紧耦合。然而，采用静态配置的方式部署容器集群管理特性越来越无法满足运营商的需求，特别是在容器集群应用在多租户管理的环境中。运营商迫切地需要一种可以按照运营商的运营管理需求在容器集群中动态地部署容器集群管理特性的方法。
基于此，本申请提出了一种通信方法300，如图3所示，用于实现容器集群管理特性的动态部署。该方法300适用于图1和图2所示的系统。为了便于描述，下文以CCM的消费者实体为NFVO为例进行说明。该方法300包括：
S310，NFVO确定将定制化容器集群管理特性#1(目标定制化容器集群管理特性的一例)与容器集群#1(目标容器集群的一例)进行关联。
作为一种可能的情况，NFVO可以按照需求(例如，按照运营商部署容器集群的策略)，确定将定制化容器集群管理特性#1与容器集群#1进行关联。
例如，一开始，运营商部署的容器集群#1的策略为容器集群#1不关联定制化容器集群管理特性#1。后续，运营商将容器集群#1的策略调整为容器集群#1关联定制化容器集群管理特性#1。此时，NFVO可以根据调整后的容器集群#1的策略确定将定制化容器集群管理特性#1与容器集群#1进行关联。
下面举例说明定制化容器集群管理特性#1。
示例1：
定制化容器集群管理特性#1可以为容器集群增强特性(CIS cluster enhanced characteristics，CCEC)，该特性的开源社区原型为Kubernetes的定制化资源定义(custom resource definition，CRD)。为了满足部署容器化VNF或运营容器集群(例如，用于虚拟化环境的辅助容器网络)的额外容器集群功能的新需求，容器集群可以支持向其基线的特性能力集添加新的增强特性功能。容器集群增强特性CCEC可以应用于容器集群，从而实现容器集群中的高级特性和操作。例如，将容器集群增强特性(在实现辅助的容器集群网络中选择适当的容器网络接口(container network interface，CNI)插件的特性)加入到CISM实例中，增强CISM北向的应用编程接口(application program interfaces，APIs)。
示例2：
定制化容器集群管理特性#1可以为守护进程负载(daemon workload)，也称为守护进程对象。该特性的开源社区的原型是Kubernetes的守护进程集(daemon set)，将特定用途的守护进程(例如，收集日志、监控状态)加载到CIS集群节点，监控CIS集群节点的运行状态。守护进程负载用于将具有相同功能的定制化容器集群管理特性部署到所有适用的容器集群节点上。以下是使用守护进程负载的示例：在每个容器集群节点上运行一个被管理的容器集群对象(managed CIS cluster object，MCCO)实例来收集日志，在每个容器集群节点上运行一个MCCO实例来监控节点的状态，并在每个容器集群节点上运行一个MCCO实例来动态配置路由信息。CISM实例使用守护进程负载来同时控制一组跨不同 的容器群集的守护进程。
应理解，定制化容器集群管理特性#1还可以为其他示例，本申请对此不作限定。定制化容器集群管理特性可以为特定的进程(例如，特定的二进制进程)。
S320，NFVO向CCM发送第一请求消息，第一请求消息用于请求将定制化容器集群管理特性#1与容器集群#1进行关联。相应地，CCM接收第一请求消息。
其中，第一请求消息包括定制化容器集群管理特性#1的标识信息、容器集群#1的标识信息。
可选地，第一请求消息还可以包括以下中的一项或多项：
关联操作的应用范围信息、容器集群#1中使用定制化容器集群管理特性#1的消费者的信息。
一示例，该关联操作的应用范围信息可以指示定制化容器集群管理特性#1与容器集群#1中的全部命名空间关联。
又一示例，该关联操作的应用范围信息可以指示定制化容器集群管理特性#1与容器集群#1中的部分命名空间关联。此时，第一请求消息中还包括该部分命名空间的标识信息。
使用定制化容器集群管理特性#1的消费者可以为容器集群#1中的功能实体。一示例，该功能实体可以为容器集群#1中的控制面功能实体(例如，CISM实体)。又一示例，该功能实体可以为容器集群#1中的用户面功能实体(例如，CIS实体)。又一示例，该功能实体可以为容器集群#1中的控制面功能实体和用户面功能实体。
S330，CCM根据第一请求消息，将定制化容器集群管理特性#1与容器集群#1进行关联。
作为一种可能的方式，CCM可以创建与容器集群#1关联的定制化容器集群管理特性的列表(记为列表#1)，CCM可以在列表#1中添加定制化容器集群管理特性#1的标识信息，从而，关联定制化容器集群管理特性#1与容器集群#1。
可选地，CCM还可以根据第一请求消息配置容器集群#1中使用定制化容器集群管理特性#1的消费者的类型。
一示例，CCM配置容器集群#1中的控制面功能实体可以使用定制化容器集群管理特性#1。
又一示例，CCM配置容器集群#1中的用户面功能实体可以使用定制化容器集群管理特性#1。
又一示例，CCM配置容器集群#1中的控制面功能实体和用户面功能实体均可以使用定制化容器集群管理特性#1。
可选地，在CCM关联定制化容器集群管理特性#1与容器集群#1之前，CCM还可以向NFVO发送请求消息#A，该请求消息#A用于请求NFVO许可在容器集群#1中分配用于部署定制化容器集群管理特性#1的基础设施资源(记为，基础设施资源#1)。例如，该基础设施资源#1可以为虚机资源或裸机资源。作为一种情况，NFVO可以向CCM发送响应消息#A，该响应消息#A指示许可在容器集群#1中分配基础设施资源#1。进一步地，CCM向VIM发送请求消息#B，该请求消息#B用于请求在容器集群#1中为定制化容器集群管理特性#1分配基础设施资源#1。VIM根据该请求消息#B在容器集群#1中分配相应的 基础设施资源#1。该过程与VNF生命周期管理(life cycle management，LCM)操作的资源管理许可(granting)过程类似。
根据本申请的方案，CCM可以从NFVO接收第一请求消息，并根据第一请求消息关联定制化容器集群管理特性#1与容器集群#1，从而实现了容器集群管理特性的动态部署，更好地满足了运营商的需求。此外，本申请中实现容器集群管理特性动态部署的方案不需要CCM与CISM之间进行交互，可以避免增加容器平台层功能之间在多厂商环境下的互操作集成成本。
可选地，S340，CCM向NFVO发送第一响应消息，该第一响应消息用于指示定制化容器集群管理特性#1与容器集群#1成功关联。
可选地，在S310之前，该方法300还包括S301-S309：
S301，NFVO确定文件#1(目标文件的一例)。
该文件#1为包含部署和运行定制化容器集群管理特性#1的配置、状态及策略信息的模板文件。
一示例，该文件#1为被管理的容器集群对象(managed CIS cluster object，MCCO)声明式描述符(MCCO declarative descriptor，MDD)文件。其中，MCCO是用于容器集群管理过程的抽象NFV对象，其特征表示为对象的配置、状态、请求和分配的基础设施资源以及适用的操作策略。根据MCCO对象的适用性和功能范围，MCCO可以表征以下场景下的被管理对象，体现为容器用户面CIS实例上运行的一组关联的容器，或者为容器管理面CISM实例中的配置对象。
CCM负责MCCO的生命周期管理，例如，通过向CISM请求通过守护进程工作负载对象创建和部署MCCO，将MCCO安装到容器集群，从容器集群中删除MCCO等。此外，由于MCCO实例可以消耗CIS集群的计算、网络和/或存储资源，CCM也有责任向NFVO请求许可部署MCCO实例所需的资源。
a)增强或添加一组容器集群管理特性；
b)支持容器集群管理的过程，例如：容器集群的部署实现或保障；
MDD是用于描述MCCO的基本特征的模板文件，例如在文件中包括了MCCO的期望状态。MDD文件可以采用开源社区使用的原生描述符模板(native descriptor)文件来实现。具体地，该文件#1包括以下中的一项或多项信息：
部署定制化容器集群管理特性#1所需的计算资源、存储资源、网络资源信息，部署访问定制化容器集群管理特性#1的安全鉴权机制基于角色的接入控制(role based access control，RBAC)信息，监控定制化容器集群管理特性#1运行的云供应商控制器(cloud provider controller)信息。
作为一种可能的情况，运营商可以向NFVO配置文件#1，进一步地，NFVO可以将该文件#1存储到相应的存储空间。
S302，NFVO向CCM发送第二请求消息，第二请求消息用于请求CCM加载文件#1。第二请求消息中包括信息#A，该信息#A用于确定文件#1。
一示例，该信息#A包括文件#1的标识信息。
又一示例，该信息#A包括文件#1的访问路径信息。
S303，CCM根据信息#A确定文件#1，并验证文件#1是否能够加载。
一示例，CCM可以验证文件#1的鉴权机制，例如，该文件#1在容器集群中的完整性、真实性、有效性、可使用性等。CCM还可以验证文件#1中强制性的属性是否就绪。
作为一种可能的情况，如果文件#1在容器集群中的完整性、和/或真实性、和/或有效性、和/或可使用性、和/或强制性满足预设的条件，则文件#1能够加载。
S304，在文件#1能够加载的情况下，CCM加载(onboard)文件#1。
作为一种可能的情况，CCM可以将文件#1存储到相应的存储空间，该存储空间可以为CCM本地的存储空间，也可以为其他设备的存储空间。应理解，CCM具有访问该存储空间的权限。
应理解，在文件#1不能加载的情况下，CCM不加载文件#1。
可选地，S305，CCM向NFVO发送第二响应消息，该第二响应消息用于指示CCM是否成功加载文件#1。
应理解，S301-S305还可以独立存在，即，S301-S305之后可能不包括本申请中的其他步骤。
S306，NFVO确定需要创建定制化容器集群管理特性#1。
作为一种可能的情况，NFVO可以按照需求(例如，按照运营商部署容器集群的策略)，确定需要创建定制化容器集群管理特性#1。
S307，NFVO向CCM发送第三请求消息，该第三请求消息用于请求创建定制化容器集群管理特性#1。相应地CCM接收该第三请求消息。
该第三请求消息中包括文件#1的标识信息。
S308，CCM根据第三请求消息，创建定制化容器集群管理特性#1。
具体地，CCM可以根据第三请求消息中文件#1的标识信息，访问文件#1，并解析文件#1中对象实例#1的部署信息，根据对象实例#1的部署信息，创建对象实例#1。该对象实例#1与定制化容器集群管理特性#1对应。即，该对象实例#1为定制化容器集群管理特性#1的一种抽象表现形式。
一示例，该对象实例#1可以为被管理的容器集群对象(managed CIS cluster object，MCCO)实例#1。
可选地，S309，CCM向NFVO发送第三响应消息，该第三响应消息用于指示CCM成功创建定制化容器集群管理特性#1。
该第三响应消息中包括对象实例#1(例如，MCCO实例#1)的标识信息。
应理解，S306-S309还可以独立存在，即，S306-S309之前和之后可能不包括本申请中的其他步骤。
可选地，在S340之后，该方法300还包括S341-S344：
S341，NFVO确定将定制化容器集群管理特性#1与容器集群#1去关联。
作为一种可能的情况，NFVO可以按照需求(例如，按照运营商部署容器集群的策略)，确定将定制化容器集群管理特性#1与容器集群#1去关联。
应理解，“去关联”的含义为解除关联关系。
S342，NFVO向CCM发送第四请求消息，该第四请求消息用于请求CCM将定制化容器集群管理特性#1与容器集群#1去关联。相应地，CCM接收第四请求消息。
其中，第四请求消息中包括定制化容器集群管理特性#1的标识信息与容器集群#1的 标识信息。
S343，CCM根据第四请求消息，将定制化容器集群管理特性#1与容器集群#1去关联。
作为一种可选的方式，CCM可以将定制化容器集群管理特性#1的标识信息从上文中的列表#1中删除。
根据本申请的方案，CCM可以从NFVO接收第四请求消息，并根据第四请求消息完成定制化容器集群管理特性#1与容器集群#1的去关联。相比之下，本申请的方案不需要伴随容器集群的删除过程即可动态地将定制化容器集群管理特性与容器集群去关联，更好地满足了运营商不断变化的容器集群管理需求。
可选地，S344，CCM向NFVO发送第四响应消息，该第四响应消息用于指示CCM成功将定制化容器集群管理特性#1与容器集群#1去关联。
应理解，上述S341-S344还可以独立存在。例如，S341-S344不在S310-S340的基础上执行。换句话说，CCM在将定制化管理特性#1与容器集群#1去关联之前，有可能并没有执行S310-S340动态地将定制化管理特性#1与容器集群#1关联。
可选地，在S344之后，该方法300还包括S345-S348：
S345，NFVO确定将定制化容器集群管理特性#1删除。
作为一种可能的情况，NFVO可以按照需求(例如，按照运营商部署容器集群的策略)，确定将定制化容器集群管理特性#1删除。
S346，NFVO向CCM发送第五请求消息，该第五请求消息用于请求将定制化容器集群管理特性#1删除。相应地，CCM接收第五请求消息。
其中，第五请求消息中包括定制化容器集群管理特性#1的标识信息。
S347，CCM根据第五请求消息将定制化容器集群管理特性#1删除。
应理解，如果S347是在S343的基础上进行的，即，在执行S347时已经没有使用定制化容器集群管理特性#1的容器集群了，此时，可以直接将定制化容器集群管理特性#1删除。
作为另一种情况，如果S347不是在S343的基础上进行的，则CCM需要判断是否有使用定制化容器集群管理特性#1的容器集群。例如，CCM判断容器集群#1正在使用定制化容器集群管理特性#1。此时，CCM可以首先将定制化容器集群管理特性#1与容器集群#1去关联，然后再将定制化容器集群管理特性#1删除。
可选地，S348，CCM向NFVO发送第五响应消息，该第五响应消息用于指示CCM成功将定制化容器集群管理特性#1删除。
应理解，S345-S348还可以独立存在。例如，S345-S348不在S310-S340的基础上执行。换句话说，CCM在将定制化管理特性#1删除之前，有可能并没有执行S310-S340动态地将定制化管理特性#1与容器集群#1关联。
根据前述方法，图4为本申请实施例提供的一种通信装置，该通信装置包括收发单元401和处理单元402。
其中，收发单元401可以用于实现相应的通信功能。收发单元401还可以称为通信接口或通信单元。处理单元402可以用于进行处理操作。
可选地，该装置还包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元402可以读取存储单元中的指令和/或数据，以使得装置实现前述各个方法实施例中的 装置的动作。
作为第一种设计，该装置可以是前述实施例中的CCM，也可以是CCM的组成部件(如芯片)。
其中，收发单元，用于从网络设备接收第一请求消息，第一请求消息用于请求CCM将目标定制化容器集群管理特性与目标容器集群进行关联；处理单元，用于根据第一请求消息关联目标定制化容器集群管理特性与目标容器集群。
在一种情况中，收发单元，还用于向网络设备发送第一响应消息，第一响应消息用于指示目标定制化容器集群管理特性与目标容器集群成功关联。
在另一种情况中，收发单元，还用于从网络设备接收第二请求消息，第二请求消息用于请求CCM加载目标文件；处理单元，还用于根据第二请求消息，确定目标文件，并验证目标文件是否能够加载；在目标文件能够加载的情况下，处理单元，还用于加载目标文件；收发单元，还用于向网络设备发送第二响应消息，第二响应消息用于指示CCM成功加载目标文件。
在另一种情况中，收发单元，还用于从网络设备接收第三请求消息，第三请求消息用于请求CCM创建目标定制化容器集群管理特性；处理单元，还用于根据第三请求消息，确定目标文件；处理单元，还用于根据目标文件中的部署信息，创建目标对象实例；收发单元，还用于向网络设备发送第三响应消息，第三响应消息用于指示CCM成功创建目标定制化容器集群管理特性，第三响应消息包括目标对象实例的标识信息。
在另一种情况中，收发单元，还用于从网络设备接收第四请求消息，第四请求消息用于请求将目标定制化容器集群管理特性与目标容器集群去关联；处理单元，还用于根据第四请求消息将目标定制化容器集群管理特性与目标容器集群去关联；收发单元，还用于向网络设备发送第四响应消息，第四响应消息用于指示CCM成功将目标定制化容器集群管理特性与目标容器集群去关联。
在另一种情况中，收发单元，还用于从网络设备接收第五请求消息，第五请求消息用于请求将目标定制化容器集群管理特性删除；处理单元，还用于根据第五请求消息，将目标定制化容器集群管理特性删除；收发单元，还用于向网络设备发送第五响应消息，第五响应消息用于指示CCM成功将目标定制化容器集群管理特性删除。
作为第二种设计，该装置可以是前述实施例中的NFVO，也可以是NFVO的组成部件(如芯片)。
其中，处理单元，用于确定将目标定制化容器集群管理特性与目标容器集群进行关联；收发单元，用于向容器集群管理器CCM发送第一请求消息，第一请求消息用于请求CCM将目标定制化容器集群管理特性与目标容器集群进行关联。
作为一种情况，处理单元，还用于确定目标文件；收发单元，还用于向CCM发送第二请求消息，第二请求消息用于请求CCM加载目标文件；收发单元，还用于从CCM接收第二响应消息，第二响应消息用于指示CCM成功加载目标文件。
作为另一种情况，处理单元，还用于确定创建目标定制化容器集群管理特性；收发单元，还用于向CCM发送第三请求消息，第三请求消息用于请求CCM创建目标定制化容器集群管理特性；收发单元，还用于从CCM接收第三响应消息，第三响应消息用于指示CCM成功创建目标定制化容器集群管理特性。
作为另一种情况，处理单元，还用于确定将目标定制化容器集群管理特性与目标容器集群去关联；收发单元，还用于向CCM发送第四请求消息，第四请求消息用于请求将目标定制化容器集群管理特性与目标容器集群去关联；收发单元，还用于从CCM接收第四响应消息，第四响应消息用于指示CCM成功将目标定制化容器集群管理特性与目标容器集群去关联。
作为另一种情况，处理单元，还用于确定将目标定制化容器集群管理特性删除；收发单元，还用于向CCM发送第五请求消息，第五请求消息用于请求将目标定制化容器集群管理特性删除；收发单元，还用于从CCM接收第五响应消息，第五响应消息用于指示CCM成功将目标定制化容器集群管理特性删除。
应理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
还应理解，这里的装置以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，装置可以具体为上述实施例中的第一网元，可以用于执行上述各方法实施例中与第一网元对应的各个流程和/或步骤，或者，装置可以具体为上述实施例中的网络管理网元，可以用于执行上述各方法实施例中与网络管理网元对应的各个流程和/或步骤，为避免重复，在此不再赘述。
上述通信装置具有实现上述方法中的装置所执行的相应步骤的功能。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块；例如收发单元可以由收发机替代(例如，收发单元中的发送单元可以由发送机替代，收发单元中的接收单元可以由接收机替代)，其它单元，如处理单元等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
此外，上述收发单元401还可以是收发电路(例如可以包括接收电路和发送电路)，处理单元可以是处理电路。
需要指出的是，图4中的装置可以是前述方法实施例中的装置，也可以是芯片或者芯片系统，例如：片上系统(system on chip，SoC)。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。在此不做限定。
本申请实施例还提供一种通信设备，如图5所示，包括：处理器501和通信接口502。处理器501用于执行存储器503存储的计算机程序或指令，或读取存储器503存储的数据，以执行上文各方法实施例中的方法。可选地，处理器501为一个或多个。通信接口502用于信号的接收和/或发送。例如，处理器501用于控制通信接口502进行信号的接收和/或发送。
可选地，如图5所示，该通信设备还包括存储器503，存储器503用于存储计算机程序或指令和/或数据。该存储器503可以与处理器501集成在一起，或者也可以分离设置。可选地，存储器503为一个或多个。
可选地，处理器501、通信接口502以及存储器503通过总线504相互连接；总线504可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准 结构(extended industry standard architecture，EISA)总线等。上述总线504可以分为地址总线、数据总线和控制总线等。为便于表示，图5中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
作为一种方案，该通信设备用于实现上文各个方法实施例中由CCM，或者NFVO执行的操作。
例如，处理器501用于执行存储器503存储的计算机程序或指令，以实现上文各个方法实施例中CCM的相关操作。
又如，处理器501用于执行存储器503存储的计算机程序或指令，以实现上文各个方法实施例中NFVO的相关操作。
应理解，本申请实施例中提及的处理器(如处理器501)可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。处理器还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device,CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
还应理解，本申请实施例中提及的存储器(如存储器503)可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各 个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (24)

  1. 一种通信方法，其特征在于，包括：
    容器集群管理CCM从网络设备接收第一请求消息，所述第一请求消息用于请求所述CCM将目标定制化容器集群管理特性与目标容器集群进行关联，所述第一请求消息包括所述目标定制化容器集群管理特性的标识信息以及所述目标容器集群的标识信息；
    其中，所述网络设备为所述CCM的消费者实体；
    所述CCM根据所述第一请求消息关联所述目标定制化容器集群管理特性与所述目标容器集群。
  2. 根据权利要求1所述的方法，其特征在于，
    所述第一请求消息中还包括关联操作的应用范围信息；
    所述关联操作的应用范围信息用于指示所述目标定制化容器集群管理特性应用于所述目标容器集群中的全部命名空间；或者，
    所述关联操作的应用范围信息用于指示所述目标定制化容器集群管理特性应用于所述目标容器集群中的部分命名空间，所述第一请求消息中还包括所述部分命名空间的标识信息。
  3. 根据权利要求1或2所述的方法，其特征在于，
    所述第一请求消息中还包括所述目标容器集群中使用所述目标定制化容器集群管理特性的消费者的信息，使用所述目标定制化容器集群管理特性的消费者为控制面功能实体和/或用户面功能实体。
  4. 根据权利要求1-3中任一项所述的方法，其特征在于，
    所述方法还包括：
    所述CCM向所述网络设备发送第一响应消息，所述第一响应消息用于指示所述目标定制化容器集群管理特性与所述目标容器集群成功关联。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，
    在所述CCM从所述网络设备接收第一请求消息之前，所述方法还包括：
    所述CCM从所述网络设备接收第二请求消息，所述第二请求消息用于请求所述CCM加载目标文件，所述第二请求消息中包括特定信息，所述特定信息用于确定所述目标文件；
    其中，所述目标文件包括部署和运行所述目标定制化容器集群管理特性的配置、状态及策略信息；
    所述CCM根据所述第二请求消息，确定所述目标文件，并验证所述目标文件是否能够加载；
    在所述目标文件能够加载的情况下，所述CCM加载所述目标文件；
    所述CCM向所述网络设备发送第二响应消息，所述第二响应消息用于指示所述CCM成功加载所述目标文件。
  6. 根据权利要求5所述的方法，其特征在于，
    所述目标文件为被管理的容器集群对象声明式描述符MDD文件；
    所述特定信息包括所述目标文件的标识信息，和/或，所述目标文件的存储路径信息。
  7. 根据权利要求5或6所述的方法，其特征在于，
    在所述CCM加载所述目标文件之后，所述方法还包括：
    所述CCM从所述网络设备接收第三请求消息，所述第三请求消息用于请求所述CCM创建所述目标定制化容器集群管理特性，所述第三请求消息包括所述特定信息；
    所述CCM根据所述第三请求消息，确定所述目标文件；
    所述CCM根据所述目标文件中的部署信息，创建目标对象实例，所述目标对象实例与所述目标定制化容器集群管理特性对应；
    所述CCM向所述网络设备发送第三响应消息，所述第三响应消息用于指示所述CCM成功创建所述目标定制化容器集群管理特性，所述第三响应消息包括所述目标对象实例的标识信息。
  8. 根据权利要求1-7中任一项所述的方法，其特征在于，
    在所述CCM将所述目标定制化容器集群管理特性与所述目标容器集群进行关联之后，所述方法还包括：
    所述CCM从所述网络设备接收第四请求消息，所述第四请求消息用于请求将所述目标定制化容器集群管理特性与所述目标容器集群去关联；
    其中，所述第四请求消息包括所述目标定制化容器集群管理特性的标识信息与所述目标容器集群的标识信息；
    所述CCM根据所述第四请求消息将所述目标定制化容器集群管理特性与所述目标容器集群去关联；
    所述CCM向所述网络设备发送第四响应消息，所述第四响应消息用于指示所述CCM成功将所述目标定制化容器集群管理特性与所述目标容器集群去关联。
  9. 根据权利要求8所述的方法，其特征在于，
    在所述CCM将所述目标定制化容器集群管理特性与所述目标容器集群去关联之后，所述方法还包括：
    所述CCM从所述网络设备接收第五请求消息，所述第五请求消息用于请求将所述目标定制化容器集群管理特性删除；
    其中，所述第五请求消息包括所述目标定制化容器集群管理特性的标识信息；
    所述CCM根据所述第五请求消息，将所述目标定制化容器集群管理特性删除；
    所述CCM向所述网络设备发送第五响应消息，所述第五响应消息用于指示所述CCM成功将所述目标定制化容器集群管理特性删除。
  10. 根据权利要求1-9中任一项所述的方法，其特征在于，
    所述网络设备为网络功能虚拟化编排器NFVO。
  11. 一种通信方法，其特征在于，包括：
    网络设备确定将目标定制化容器集群管理特性与目标容器集群进行关联；
    所述网络设备向容器集群管理CCM发送第一请求消息，所述第一请求消息用于请求所述CCM将所述目标定制化容器集群管理特性与所述目标容器集群进行关联，所述第一请求消息包括所述目标定制化容器集群管理特性的标识信息以及所述目标容器集群的标识信息；
    其中，所述网络设备为所述CCM的消费者实体。
  12. 根据权利要求11所述的方法，其特征在于，
    所述第一请求消息中还包括关联操作的应用范围信息；
    所述关联操作的应用范围信息用于指示所述目标定制化容器集群管理特性应用于所述目标容器集群中的全部命名空间；或者，
    所述关联操作的应用范围信息用于指示所述目标定制化容器集群管理特性应用于所述目标容器集群中的部分命名空间，所述第一请求消息中还包括所述部分命名空间的标识信息。
  13. 根据权利要求11或12所述的方法，其特征在于，
    所述第一请求消息中还包括所述目标容器集群中使用所述目标定制化容器集群管理特性的消费者的信息，使用所述目标定制化容器集群管理特性的消费者为控制面功能实体和/或用户面功能实体。
  14. 根据权利要求11-13中任一项所述的方法，其特征在于，
    所述方法还包括：
    所述网络设备从所述CCM接收第一响应消息，所述第一响应消息用于指示所述目标定制化容器集群管理特性与所述目标容器集群成功关联。
  15. 根据权利要求11-14中任一项所述的方法，其特征在于，
    所述方法还包括：
    所述网络设备确定目标文件，所述目标文件包括部署和运行所述目标定制化容器集群管理特性的配置、状态及策略信息；
    所述网络设备向所述CCM发送第二请求消息，所述第二请求消息用于请求所述CCM加载所述目标文件，所述第二请求消息中包括特定信息，所述特定信息用于确定所述目标文件；
    所述网络设备从所述CCM接收第二响应消息，所述第二响应消息用于指示所述CCM成功加载所述目标文件。
  16. 根据权利要求15所述的方法，其特征在于，
    所述目标文件为被管理的容器集群对象声明式描述符MDD文件；
    所述特定信息包括所述目标文件的标识信息，和/或，所述目标文件的存储路径信息。
  17. 根据权利要求15或16所述的方法，其特征在于，
    所述方法还包括：
    所述网络设备确定创建所述目标定制化容器集群管理特性；
    所述网络设备向所述CCM发送第三请求消息，所述第三请求消息用于请求所述CCM创建所述目标定制化容器集群管理特性，所述第三请求消息包括所述特定信息；
    所述网络设备从所述CCM接收第三响应消息，所述第三响应消息用于指示所述CCM成功创建所述目标定制化容器集群管理特性，所述第三响应消息包括目标对象实例的标识信息，所述目标对象实例与所述目标定制化容器集群管理特性对应。
  18. 根据权利要求11-17中任一项所述的方法，其特征在于，
    所述方法还包括：
    所述网络设备确定将所述目标定制化容器集群管理特性与所述目标容器集群去关联；
    所述网络设备向所述CCM发送第四请求消息，所述第四请求消息用于请求将所述目 标定制化容器集群管理特性与所述目标容器集群去关联；
    其中，所述第四请求消息包括所述目标定制化容器集群管理特性的标识信息与所述目标容器集群的标识信息；
    所述网络设备从所述CCM接收第四响应消息，所述第四响应消息用于指示所述CCM成功将所述目标定制化容器集群管理特性与所述目标容器集群去关联。
  19. 根据权利要求18所述的方法，其特征在于，
    所述网络设备确定将所述目标定制化容器集群管理特性删除；
    所述网络设备向所述CCM发送第五请求消息，所述第五请求消息用于请求将所述目标定制化容器集群管理特性删除；
    其中，所述第五请求消息包括所述目标定制化容器集群管理特性的标识信息；
    所述网络设备从所述CCM接收第五响应消息，所述第五响应消息用于指示所述CCM成功将所述目标定制化容器集群管理特性删除。
  20. 根据权利要求11-19中任一项所述的方法，其特征在于，
    所述网络设备为网络功能虚拟化编排器NFVO。
  21. 一种通信装置，其特征在于，包括用于执行权利要求1-20中任一项方法的单元。
  22. 一种通信设备，其特征在于，包括：通信接口和处理器，所述处理器用于执行计算机程序或指令，使得所述通信设备执行如权利要求1-20中任一项所述的方法。
  23. 一种计算机可读存储介质，其特征在于，包括计算机程序或指令，当所述计算机程序或所述指令在计算机上运行时，使得所述计算机执行如权利要求1-20中任意一项所述的方法。
  24. 一种计算机程序产品，其特征在于，包含指令，当所述指令在计算机上运行时，使得所述计算机执行如权利要求1-20中任意一项所述的方法。
PCT/CN2022/128497 2021-11-05 2022-10-31 通信方法和装置 WO2023078194A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111303494.7A CN116094912A (zh) 2021-11-05 2021-11-05 通信方法和装置
CN202111303494.7 2021-11-05

Publications (1)

Publication Number Publication Date
WO2023078194A1 true WO2023078194A1 (zh) 2023-05-11

Family

ID=86197789

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/128497 WO2023078194A1 (zh) 2021-11-05 2022-10-31 通信方法和装置

Country Status (2)

Country Link
CN (1) CN116094912A (zh)
WO (1) WO2023078194A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111324571A (zh) * 2020-01-22 2020-06-23 中国银联股份有限公司 一种容器集群管理方法、装置及系统
CN111935110A (zh) * 2020-07-24 2020-11-13 北京金山云网络技术有限公司 一种对租户访问容器实例的权限的控制方法和装置
CN111949364A (zh) * 2019-05-16 2020-11-17 华为技术有限公司 容器化vnf的部署方法和相关设备
US20210084048A1 (en) * 2019-09-18 2021-03-18 International Business Machines Corporation Cognitive Access Control Policy Management in a Multi-Cluster Container Orchestration Environment
CN112799837A (zh) * 2021-01-27 2021-05-14 浪潮云信息技术股份公司 一种容器动态平衡调度方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111949364A (zh) * 2019-05-16 2020-11-17 华为技术有限公司 容器化vnf的部署方法和相关设备
US20210084048A1 (en) * 2019-09-18 2021-03-18 International Business Machines Corporation Cognitive Access Control Policy Management in a Multi-Cluster Container Orchestration Environment
CN111324571A (zh) * 2020-01-22 2020-06-23 中国银联股份有限公司 一种容器集群管理方法、装置及系统
CN111935110A (zh) * 2020-07-24 2020-11-13 北京金山云网络技术有限公司 一种对租户访问容器实例的权限的控制方法和装置
CN112799837A (zh) * 2021-01-27 2021-05-14 浪潮云信息技术股份公司 一种容器动态平衡调度方法

Also Published As

Publication number Publication date
CN116094912A (zh) 2023-05-09

Similar Documents

Publication Publication Date Title
CN108536519B (zh) 自动搭建Kubernetes主节点的方法及终端设备
CN107657169B (zh) 权限管理方法、装置、介质和电子设备
US9626526B2 (en) Trusted public infrastructure grid cloud
WO2019062304A1 (zh) 用于管理区块链节点的计算资源的方法、设备和系统
US10601666B2 (en) Network functions virtualization management and orchestration policy descriptor management method and apparatus
CN107959582B (zh) 一种切片实例的管理方法及装置
US10924966B2 (en) Management method, management unit, and system
US10999326B1 (en) Fine grained network security
US20190050248A1 (en) Control apparatus, vnf deployment destination selection method and program
EP3839726B1 (en) Software modification initiation method and apparatus
US10356155B2 (en) Service onboarding
CN110716788B (zh) 管理虚拟化资源的方法和装置
US9342825B2 (en) Software license and installation process management within an organization
US20150128130A1 (en) Method and system for providing and dynamically deploying hardened task specific virtual hosts
US20230261950A1 (en) Method of container cluster management and system thereof
CN109743202B (zh) 数据的管理方法、装置、设备及可读存储介质
US20210185007A1 (en) Integration of an orchestration services with a cloud automation services
US20230342183A1 (en) Management method and apparatus for container cluster
JP7439928B2 (ja) 管理装置、管理方法、管理プログラム、及び管理システム
WO2023078194A1 (zh) 通信方法和装置
CN109218259B (zh) 许可管理方法及装置、applm功能实体及计算机可读存储介质
WO2022133827A1 (zh) 一种任务处理请求的处理方法、装置以及区块链节点设备
US11075803B1 (en) Staging configuration changes with deployment freeze options
US11949561B2 (en) Automated preventative controls in digital workflow
WO2022267995A1 (zh) 通信方法、装置、相关设备及存储介质

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: 22889219

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022889219

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022889219

Country of ref document: EP

Effective date: 20240521