WO2020015751A1 - 容器服务快照的管理方法和装置 - Google Patents

容器服务快照的管理方法和装置 Download PDF

Info

Publication number
WO2020015751A1
WO2020015751A1 PCT/CN2019/096872 CN2019096872W WO2020015751A1 WO 2020015751 A1 WO2020015751 A1 WO 2020015751A1 CN 2019096872 W CN2019096872 W CN 2019096872W WO 2020015751 A1 WO2020015751 A1 WO 2020015751A1
Authority
WO
WIPO (PCT)
Prior art keywords
container service
snapshot
instance
container
information
Prior art date
Application number
PCT/CN2019/096872
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 WO2020015751A1 publication Critical patent/WO2020015751A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/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
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances

Definitions

  • the present application relates to communication technologies, and in particular, to a method and an apparatus for managing a container service snapshot.
  • Snapshot technology is a technology commonly used in the software field. It borrows the principle of photo imaging in photography and retains the image of the data at a certain moment, so that the subsequent image of the data can be found based on the snapshot. A technology that enhances data backup.
  • VNF virtual network function
  • a VNF snapshot refers to a replica of a VNF instance at a point in time, including snapshots of all Virtualized Network Function Component (VNFC) instances that make up the VNF instance, VNF descriptor files (Descriptor), and VNF information objects (For example, the status and settings of the virtual link and connection point associated with the VNF instance).
  • VNFC snapshot is a copy of a VNFC instance at a point in time. It captures all or part of the state of VNFC, the content stored in disks, memory, and devices, and the configuration of VNFC in the infrastructure.
  • Container as a Service is a specific type of Platform as a Service (PaaS) service.
  • Container is an operating system-level virtualization technology. It uses operating system isolation technologies such as CGroup and NameSpace under Linux to isolate different processes.
  • Container technology is different from hardware virtualization (Hypervisor) technology, there is no virtual hardware, there is no operating system inside the container, only processes. Because of this important feature of container technology, containers are lighter and easier to manage than virtual machines.
  • a set of common management operations are defined, such as: start, stop, pause, and delete, etc., to perform unified lifecycle management on the container.
  • the number of container services included in a VNF instance has increased significantly.
  • the number of container service snapshots corresponding to a VNF snapshot has also increased significantly, resulting in the number of container service snapshots that need to be managed. This increases the load pressure on the disks that store container service snapshots.
  • the present application provides a method and device for managing container service snapshots, which reduces the number of container service snapshots and improves the management efficiency of container service snapshots.
  • a first aspect of the present invention provides a method for managing a container service snapshot, including:
  • the container service manager receives a request for creating a container service snapshot sent by the virtual network function manager VNFM, where the creation request includes an identifier of the container service instance to be created;
  • the container service manager creates a container service snapshot for the container service instance.
  • the container service snapshot includes at least one dedicated snapshot information and one shared snapshot information.
  • the at least one dedicated snapshot information is the container service instance used when taking a picture. Specific operation information of a container service subscribed to by at least one VNF instance, wherein the at least one dedicated snapshot information corresponds to the at least one NVF instance one by one, and the shared snapshot information is a container service corresponding to the container service instance at Public running information in the snapshot;
  • the container service manager sends a container service snapshot creation response to the VNFM, and the creation response includes an identifier of the container service snapshot.
  • the container service manager creating a container service snapshot for the container service instance includes:
  • the container service manager generates the shared snapshot information of the container service snapshot according to the identifier of the container service instance.
  • the method saves the number of container service snapshots and improves the container service snapshot by saving the specific operation information of the container service subscribed by at least one VNF instance and the public operation information of the container service in the same container service snapshot. Management efficiency.
  • the container service snapshots taken for multiple VNF instances that call the same container service instance only need to save one copy of the container service instance's public operating information, which reduces the storage resources occupied by the container service snapshot, thereby reducing the storage container service snapshot.
  • the load pressure of the disk is a copy of the container service instance's public operating information
  • Optional also includes:
  • the container service manager receives a configuration request for a container service snapshot sent by the VNFM.
  • the configuration request includes: a name of a VNF, a name of a container service, and specific operation information of the container service subscribed by the VNF.
  • the dedicated snapshot information includes at least one of the following operation information: a monitoring value, an event status, and / or an alarm of an operation performance indicator of the container service instance;
  • the shared snapshot information includes at least one of the following operating information: a software image of the container service, configuration information of the container service resource, an identifier of the container service descriptor file, a state of the container service instance, and a time stamp of the photo.
  • Optional also includes:
  • the container service manager deletes the container service snapshot according to the delete request
  • the container service manager sends a delete response of the container service snapshot to the VNFM.
  • Optional also includes:
  • the recovery request is used to request that the operating environment of the container service instance be restored to the operating environment corresponding to the container service snapshot, and the restoration request includes a container service instance The identifier of the container service instance using the identifier of the VNF instance to be restored and the identifier of the container service snapshot;
  • the container service manager searches for the dedicated snapshot information corresponding to the VNF instance to be restored from the container service snapshot according to the identifier of the VNF instance to be restored and the identifier of the container service snapshot;
  • the container service manager generates a restored container service for the container service instance according to the dedicated snapshot information corresponding to the container service snapshot of the VNF instance to be restored and the shared snapshot information in the container service snapshot. Snapshot, restoring the running environment of the container service instance to the running environment corresponding to the running information stored in the generated restored container service snapshot;
  • the container service manager sends a recovery response of the container service snapshot to the VNFM.
  • a second aspect of the present application provides a container service snapshot management method, including:
  • the virtual network function manager VNFM obtains, from the virtual network function descriptor VNFD, specific operation information of a container service of a VNF subscription created according to the VNFD;
  • the VNFM sends a container service snapshot configuration request to the container service manager.
  • the configuration request includes: the name of the VNF, the name of the container service, and specific operation information of the container service subscribed by the VNF.
  • Optional also includes:
  • VNFM Sending, by the VNFM, a container service snapshot creation request to the container service manager, where the creation request includes an identifier of a container service instance to create a snapshot;
  • the VNFM receives a container service snapshot creation response sent by the container service manager, and the creation response includes an identifier of the created container service snapshot.
  • Optional also includes:
  • the VNFM sends a container service snapshot deletion request to the container service manager, and the deletion request includes an identifier of the container service snapshot;
  • the VNFM receives a deletion response of a container service snapshot sent by the container service manager.
  • Optional also includes:
  • the VNFM sends a recovery request to the container service manager, where the recovery request is used to request that the running environment of the container service instance be restored to the running environment corresponding to the container service snapshot, and the restoration request includes the container service instance's Identification, identification of the VNF instance to be restored using the container service instance, and identification of the container service snapshot;
  • the VNFM receives a recovery response of a container service snapshot sent by the container service manager.
  • a third aspect of the present application provides a container service snapshot management device, including:
  • a receiving module configured to receive a request for creating a container service snapshot sent by the virtual network function manager VNFM, where the creation request includes an identifier of a container service instance to create a snapshot;
  • a creating module configured to create a container service snapshot for the container service instance, the container service snapshot includes at least one dedicated snapshot information and one shared snapshot information, and the at least one dedicated snapshot information is obtained by using the container service instance when taking a picture Specific operation information of a container service to which at least one VNF instance is subscribed, wherein the at least one dedicated snapshot information corresponds to the at least one NVF instance one by one, and the shared snapshot information is a snapshot of a container service corresponding to the container service instance.
  • a sending module is configured to send a container service snapshot creation response to the VNFM, where the creation response includes an identifier of the container service snapshot.
  • the creation module is specifically configured to:
  • the receiving module is further configured to:
  • the configuration request including: a name of a VNF, a name of a container service, and specific operation information of the container service subscribed by the VNF.
  • the dedicated snapshot information includes at least one of the following operation information: a monitoring value, an event status, and / or an alarm of an operation performance indicator of the container service instance;
  • the shared snapshot information includes at least one of the following operating information: a software image of the container service, configuration information of the container service resource, an identifier of the container service descriptor file, a state of the container service instance, and a time stamp of the photo.
  • it also includes a deletion module
  • the receiving module is further configured to receive a deletion request of a container service snapshot sent by the VNFM, where the deletion request includes an identifier of the container service snapshot;
  • the deleting module is configured to delete the container service snapshot according to the deletion request
  • the sending module is further configured to send a deletion response of the container service snapshot to the VNFM.
  • it also includes a recovery module
  • the receiving module is further configured to receive a recovery request sent by the VNFM, where the recovery request is used to request that a running environment of the container service instance be restored to a running environment corresponding to a container service snapshot, and the restoration request includes a container The identifier of the service instance, using the identifier of the VNF instance to be restored of the container service instance and the identifier of the container service snapshot;
  • the recovery module is configured to find, according to the identifier of the VNF instance to be recovered and the identifier of the container service snapshot, the dedicated snapshot information corresponding to the VNF instance to be recovered from the container service snapshot;
  • the recovery module is further configured to generate the recovered service instance for the container service instance according to the dedicated snapshot information corresponding to the container service snapshot of the VNF instance to be restored and the shared snapshot information in the container service snapshot.
  • a container service snapshot restoring the running environment of the container service instance to the running environment corresponding to the running information stored in the generated restored container service snapshot;
  • the sending module is further configured to send a recovery response of the container service snapshot to the VNFM.
  • a fourth aspect of the present application provides a container service snapshot management device, including:
  • An obtaining module configured to obtain specific operation information of a container service of a VNF subscription created according to the VNFD from a virtual network function descriptor VNFD;
  • a sending module is configured to send a container service snapshot configuration request to the container service manager.
  • the configuration request includes: a name of the VNF, a name of the container service, and specific operation information of the container service subscribed by the VNF.
  • it also includes a receiving module
  • the sending module is further configured to send a container service snapshot creation request to the container service manager, where the creation request includes an identifier of a container service instance to be created with a snapshot;
  • the receiving module is further configured to receive a container service snapshot creation response sent by the container service manager, where the creation response includes an identifier of the created container service snapshot.
  • the sending module is further configured to send a deletion request of the container service snapshot to the container service manager, where the deletion request includes an identifier of the container service snapshot;
  • the receiving module is further configured to receive a deletion response of the container service snapshot sent by the container service manager.
  • Optional also includes:
  • the sending module is further configured to send a restoration request to the container service manager, where the restoration request is used to request that the running environment of the container service instance be restored to the running environment corresponding to the container service snapshot, in the restoration request.
  • the restoration request is used to request that the running environment of the container service instance be restored to the running environment corresponding to the container service snapshot, in the restoration request.
  • the receiving module is further configured to receive a recovery response of the container service snapshot sent by the container service manager.
  • a fifth aspect of the present application provides a container service manager, including a processor, a memory, and a transceiver.
  • the memory is used to store instructions
  • the transceiver is used to communicate with other devices
  • the processor is used to execute the memory.
  • a sixth aspect of the present application provides a VNFM, including a processor, a memory, and a transceiver.
  • the memory is used to store instructions.
  • the transceiver is used to communicate with other devices.
  • the processor is used to execute instructions stored in the memory. To enable the VNFM to perform the method according to the second aspect of the present application.
  • a seventh aspect of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores instructions, and when the instructions are executed, cause a computer to execute the method according to the first aspect of the present application.
  • An eighth aspect of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores instructions, and when the instructions are executed, cause a computer to execute the method according to the second aspect of the present application.
  • the container service snapshot management method and device provided in this application include: VNFM sends a container service snapshot creation request to the container service manager, the creation request includes an identifier of the container service instance to be created, and the container service manager serves the container.
  • An instance creates a container service snapshot.
  • the container service snapshot includes at least one dedicated snapshot information and one shared snapshot information.
  • the at least one dedicated snapshot information is specific operation information of a container service subscribed to by at least one VNF instance of the container service instance when taking a picture.
  • the shared snapshot information is the common running information of the container service corresponding to the container service instance in the snapshot.
  • the container service snapshots taken for multiple VNF instances that call the same container service instance only need to save one copy of the container service instance's public operating information, which reduces the storage resources occupied by the container service snapshot, thereby reducing the storage container service snapshot.
  • the load pressure of the disk is reduced.
  • FIG. 1 is a schematic diagram of a network architecture applicable to this application
  • FIG. 2 is a signaling flowchart of a container service snapshot management method provided in Embodiment 1 of the present application;
  • FIG. 3 is a schematic diagram of a correspondence relationship between a VNF snapshot and a container service snapshot
  • FIG. 4 is a signaling flowchart of a container service snapshot management method provided in Embodiment 2 of the present application;
  • FIG. 5 is a signaling flowchart of a container service snapshot management method provided in Embodiment 3 of the present application.
  • FIG. 6 is a signaling flowchart of a container service snapshot management method provided in Embodiment 4 of the present application.
  • FIG. 7 is a schematic structural diagram of a container service snapshot management apparatus provided in Embodiment 5 of the present application.
  • FIG. 8 is a schematic structural diagram of a container service snapshot management device provided in Embodiment 6 of the present application.
  • FIG. 9 is a schematic structural diagram of a container service manager provided in Embodiment 7 of the present application.
  • FIG. 10 is a schematic structural diagram of a VNFM provided in Embodiment 8 of the present application.
  • FIG. 1 is a schematic diagram of a network architecture applicable to the present application. As shown in FIG. 1, the network architecture includes a NFV MANO system and a container service manager.
  • NFV / MAMO Network Function Virtualization Management and Orchestration
  • FIG. 1 is a schematic diagram of a network architecture applicable to the present application. As shown in FIG. 1, the network architecture includes a NFV MANO system and a container service manager.
  • the NFV MANO system includes: Network Function Virtualization Orchestrator NFVO), Virtualised Network Function Manager (VNFM), Virtual Infrastructure Manager (VIM), Operations and Business Support Systems (OSS / BSS), Internet Element Manager (EM), Virtualized Network Function (VNF), and Virtualized Functions Infrastructure (Network Virtualization Infrastructure) (NFVI).
  • Network Function Virtualization Orchestrator NFVO Network Function Virtualization Orchestrator NFVO
  • VNFM Virtualised Network Function Manager
  • VIM Virtual Infrastructure Manager
  • OSS / BSS Operations and Business Support Systems
  • EM Internet Element Manager
  • VNF Virtualized Network Function
  • NFVI Virtualized Functions Infrastructure
  • Network Virtualization Infrastructure Network Virtualization Infrastructure
  • NFVO Network Service Descriptor
  • VNFFG Virtualised Network Function Forwarding Graph
  • VNFM can be used to implement the life cycle management of VNF, which can specifically include management and processing of Virtualised Network Function Descriptor (VNFD), initialization of VNF instances, expansion and reduction of VNF (that is, elastic scaling ), And the termination of the VNF instance, in addition, VNFM can also support the elastic scaling strategy of receiving NFVO, and realize the automatic elastic scaling of VNF.
  • VNFD Virtualised Network Function Descriptor
  • initialization of VNF instances that is, elastic scaling
  • VNF that is, elastic scaling
  • VNFM can also support the elastic scaling strategy of receiving NFVO, and realize the automatic elastic scaling of VNF.
  • VIM is mainly responsible for infrastructure layer hardware resources, management of virtualized resources (including reservation and allocation), monitoring of virtual resource status and fault reporting, and providing virtualized resource pools for upper-layer applications.
  • OSS / BSS is mainly for telecommunication service operators, providing comprehensive network management and business operation functions, including network management (such as fault monitoring, network information collection, etc.), billing management, and customer service management.
  • FCAPS Configuration, Management, Account Management, Performance Management, Security Management, FCAPS
  • VNF corresponds to a physical network function (PNF) in a traditional non-virtualized network, such as a virtualized EPC node (MME, SGW, PGW, etc.).
  • PNF physical network function
  • MME virtualized EPC node
  • MME virtualized EPC node
  • PNF virtualized EPC node
  • VNF components VNF components, VNFC
  • a VNF can be deployed in multiple virtual machines (Virtual Machines, VMs).
  • VMs Virtual Machines
  • each VM carries a VNFC function, and VNF can also be deployed on a VM.
  • a containerized VNF usually consists of one or more microservices, and each microservice is deployed on one or more containers.
  • the microservices that make up a containerized VNF can be understood as a serviced VNFC.
  • NFVI consists of hardware and virtual resources, and a virtualization layer. From a VNF perspective, the virtualization layer and hardware resources appear to be a complete entity capable of providing the required virtual resources.
  • the container service manager is used to manage container services and container service snapshots, such as configuring, creating, deleting, and restoring container service snapshots.
  • Container services are managed objects with a smaller granularity than VNFC.
  • VNF has undergone containerization and evolution, the number of container services included in a VNF instance has increased significantly. Accordingly, the number of container service snapshots corresponding to a VNF snapshot has also increased significantly.
  • a VNF snapshot can correspond to a snapshot of hundreds or thousands of container services.
  • a container service snapshot can be shared by multiple different VNF instances.
  • FIG. 2 is a signaling of the container service snapshot management method provided by the first embodiment of the application.
  • the flowchart is shown in FIG. 2. The method provided in this embodiment includes the following steps:
  • Step S101 The VNFM sends a container service snapshot creation request to the container service manager, and the creation request includes an identifier of the container service instance to be created.
  • VNFM receives a request to create a VNF snapshot, creates a VNF snapshot, and then sends a container service snapshot creation request to the container service manager according to the requirements of the VNF snapshot.
  • the creation request is used to request the creation of a container service snapshot for the container service instance.
  • the creation request The ID of the container service instance to be created is included in the snapshot.
  • the container service needs to be implemented through a container service instance.
  • One container service can be instantiated into multiple container service instances.
  • the container service snapshot is information obtained by taking a snapshot of the container service instance at a certain time.
  • the container service snapshot stores the running information of the container service instance at that time.
  • the container service instance's running environment can be restored to the container service snapshot based on the container service snapshot.
  • the operating environment corresponding to the point in time.
  • Step S102 The container service manager creates at least one dedicated snapshot information of the container service snapshot for the container service instance.
  • Step S103 The container service manager creates shared snapshot information of the container service snapshot for the container service instance.
  • the container service manager creates a container service snapshot for the container service instance corresponding to the identifier of the container service instance included in the creation request.
  • one container service instance can be used by one or more VNF instances.
  • the container service instance is in When used by different VNF instances at the same time, the running information of the container service instance is different. Therefore, in this embodiment, the container service snapshot created for the container service instance at a certain time includes at least one dedicated snapshot information and one shared snapshot information.
  • the at least one dedicated snapshot information is specific operation information of a container service subscribed by using at least one VNF instance of the container service instance when taking a picture, and the at least one dedicated snapshot information corresponds to the at least one NVF instance one by one, that is, each The VNF instance generates a dedicated snapshot information, and each dedicated snapshot information is uniquely identified by the corresponding VNF instance identifier, and the corresponding dedicated snapshot information can be found later based on the VNF instance identifier.
  • the special snapshot information includes at least one of the following information: a monitoring value, an event status, and / or an alarm of a running performance indicator of the container service instance.
  • the shared snapshot information is public running information of the container service corresponding to the container service instance in the snapshot.
  • the shared snapshot information includes at least one of the following running information: a software image of the container service, configuration information of the container service resource, The identifier of the container service descriptor file (ContainerServiceDescriptor), the status of the container service instance, and the timestamp of the photo.
  • the container service manager may generate at least one dedicated snapshot information of the container service snapshot according to the pre-acquired specific operation information of the container service subscribed by using at least one VNF instance of the container service, and generate according to the identifier of the container service instance.
  • Shared snapshot information for container service snapshots as a prerequisite, the container service manager can store specific running information of different container services subscribed to by the VNF.
  • the VNF instance of the container service instance determines the corresponding VNF name according to the VNF instance, determines the corresponding container service name according to the container service instance identifier, and according to the VNF name and the container service name, and the stored VNF Name, the name of the container service, and the specific operation information of the container service subscribed by the VNF, determine the specific operation information of the container service subscribed by the VNF, and use the specific operation information as the private snapshot information corresponding to the VNF instance in the container service snapshot .
  • the dedicated snapshot information in the container service snapshot can only be used by the corresponding VNF instance, and the shared snapshot information can be used by all VNF instances that use the container service instance when taking pictures.
  • the running information of the container service stored in each container service snapshot can only be used for a VNF instance that calls the container service instance.
  • at least one VNF instance is saved in the same container service snapshot.
  • the specific running information of the subscribed container service and the common running information of the container service in the snapshot are equivalent to storing the running information of the container service subscribed by multiple VNF instances in a container service snapshot, thereby reducing the number of container service snapshots. , which improves the management efficiency of container service snapshots.
  • the storage resources occupied by VNF snapshots are reduced, thereby reducing the load pressure on the disks that store snapshots.
  • VNF snapshots The correspondence between VNF snapshots and container service snapshots is shown in Figure 3.
  • VNF snapshots There are three VNF snapshots: VNF1 snapshot, VNF2 snapshot and VNF3 snapshot, and three container service snapshots: container service snapshot 1, container service snapshot 2 And container service snapshot 3.
  • the container service snapshot 1 includes dedicated snapshot information corresponding to VNF1, dedicated snapshot information corresponding to VNF2, and shared snapshot information.
  • Container service snapshot 2 includes dedicated snapshot information corresponding to VNF1, dedicated snapshot information corresponding to VNF3, and shared snapshot information.
  • the container service snapshot 3 includes dedicated snapshot information and shared snapshot information corresponding to VNF3.
  • Step S104 The container service manager sends a container service snapshot creation response to the VNFM, and the creation response includes an identifier of the container service snapshot.
  • the container service snapshot ID is used to uniquely identify a container service snapshot.
  • the container service instance sends the created container service snapshot ID to the VNFM in the creation response.
  • the VNFM sends a container service snapshot creation request to the container service manager.
  • the creation request includes an identifier of the container service instance to be created.
  • the container service manager creates a container service snapshot for the container service instance.
  • the container service snapshot It includes at least one dedicated snapshot information and one shared snapshot information.
  • the at least one dedicated snapshot information is specific operation information of a container service subscribed by using at least one VNF instance of the container service instance when taking a picture.
  • the shared snapshot information is a container corresponding to the container service instance. Public running information of the service in the snapshot.
  • the container service snapshots taken for multiple VNF instances that call the same container service instance only need to save one copy of the container service instance's public operating information, which reduces the storage resources occupied by the container service snapshot, thereby reducing the storage container service snapshot.
  • the load pressure of the disk is reduced.
  • FIG. 4 is a signaling flowchart of a container service snapshot management method provided in Embodiment 2 of this application.
  • This embodiment mainly describes a container service snapshot configuration process.
  • the container service snapshot configuration process precedes the container service snapshot creation process, that is, This embodiment is executed before Embodiment 1.
  • the method provided by this embodiment includes the following steps:
  • Step S201 The VNFM obtains, from the VNFD, specific operation information of a container service for a VNF subscription created according to the VNFD.
  • VNFD is a template used by vendors to deploy virtual network functions. It describes VNF composition, monitoring parameters, deployment specifications, and other information.
  • a VNFD can instantiate multiple VNFs according to different deployment specifications, and a VNFD can instantiate multiple VNFs according to the same deployment specification.
  • specific operation information of a container service subscribed by a VNF is added to the VNFD.
  • a VNF can be instantiated into multiple VNF instances. Each VNF instance may call one or more container services when creating a container service snapshot. Therefore, the specific operation information of the container service subscribed by the VNF instance refers to the VNF instance.
  • Specific operation information of the container service At least one of the following information: a monitoring value, an event status, and / or an alarm of an operation performance indicator of the container service instance.
  • Step S202 The VNFM sends a container service snapshot configuration request to the container service manager.
  • the configuration request includes: the name of the VNF, the name of the container service, and specific operation information of the container service subscribed by the VNF.
  • Step S203 The container service manager stores the name of the VNF included in the configuration request, the name of the container service, and specific operation information of the container service subscribed by the VNF.
  • VNFM saves the correspondence between the name of the VNF, the name of the container service, and the specific operation information of the container service subscribed by the VNF. Tuples are stored in a local database.
  • the container service manager stores the name of the VNF included in the configuration request, the name of the container service, and the specific running information of the container service subscribed by the VNF instance. Subsequently, when creating a snapshot of the container service, according to the name of the stored VNF, the container The name of the service and the specific running information of the container service that the VNF subscribes to, to generate private snapshot information for the container service snapshot.
  • Step S204 The container service manager sends a configuration response of the container service snapshot to the VNFM.
  • the container service snapshot configuration response is used to notify VNFM that the container service snapshot configuration is complete, and VNFM determines that the container service snapshot configuration is complete based on the configuration response.
  • the configuration process performed later will refresh the specific operation information of the container service for the VNF subscription determined in the configuration process performed previously.
  • the VNFM by adding specific operation information of the container service subscribed by the VNF instance to the VNFD, the VNFM obtains specific operation information of the container service subscribed by the VNF instance created by the VNFD from the VNFD, and sends the container service to the container service manager Snapshot configuration request.
  • the configuration request includes: the name of the VNF, the name of the container service, and the specific operation information of the container service subscribed by the VNF.
  • the container service manager saves the name of the VNF included in the configuration request, and the name of the container service. , And specific operation information of the container service subscribed by VNF, so as to facilitate subsequent creation of container service snapshots based on the saved information.
  • FIG. 5 is a signaling flowchart of a container service snapshot management method provided in Embodiment 3 of this application.
  • This embodiment mainly describes a container service snapshot deletion process.
  • the container service snapshot deletion process is after the container service snapshot creation process, that is, This embodiment is executed after the first embodiment.
  • the method provided by this embodiment includes the following steps:
  • Step S301 The VNFM sends a container service snapshot deletion request to the container service manager, and the deletion request includes an identifier of the container service snapshot.
  • the delete request is used to request deletion of the container service snapshot. After all VNF snapshots using the container service snapshot are deleted, VNFM sends the delete request to the container service manager.
  • the delete request includes the identifier of the container service snapshot to be deleted. .
  • Step S302 The container service manager deletes the container service snapshot according to the deletion request.
  • the container service manager deletes the container service snapshot corresponding to the container service snapshot identifier according to the container service snapshot identifier included in the delete request.
  • Step S303 The container service manager sends a deletion response of the container service snapshot to the VNFM.
  • the container service snapshot deletion response is used to notify VNFM that the container service snapshot deletion is complete, and VNFM determines that the container service snapshot deletion is complete according to the deletion response.
  • FIG. 6 is a signaling flowchart of a container service snapshot management method provided in Embodiment 4 of this application.
  • This embodiment mainly describes a process of restoring a container service instance to an operating environment corresponding to the container service snapshot.
  • the restoration process is performed in the container service snapshot.
  • the method provided by this embodiment includes the following steps:
  • Step S401 The VNFM sends a recovery request to the container service manager.
  • the recovery request includes the identifier of the container service instance, the identifier of the VNF instance to be restored using the container service instance, and the identifier of the container service snapshot.
  • the restore request is used to request that the running environment of the container service instance be restored to the running environment corresponding to the container service snapshot.
  • VNFM may send the restore request to the container service manager.
  • the recovery request is used to request recovery to the specified VNF snapshot.
  • Step S402 The container service manager searches for the dedicated snapshot information corresponding to the VNF instance to be restored from the container service snapshot according to the identifier of the VNF instance to be restored and the identifier of the container service snapshot.
  • the container service manager first finds the corresponding container service snapshot according to the identifier of the container service snapshot.
  • the container service snapshot includes at least one dedicated snapshot information and one shared snapshot information.
  • Each dedicated snapshot information uniquely corresponds to a VNF instance.
  • the container service manager According to the identifier of the VNF instance to be restored, the dedicated snapshot information corresponding to the identifier of the VNF instance to be restored is found from at least one dedicated snapshot information included in the container service snapshot.
  • Step S403 The container service manager generates a restored container service snapshot for the container service instance according to the dedicated snapshot information corresponding to the VNF instance to be restored in the container service snapshot and the shared snapshot information in the container service snapshot, and converts the container service instance's The operating environment is restored to the operating environment corresponding to the running information stored in the generated restored container service snapshot.
  • the restored container service snapshot of the container service instance includes a dedicated snapshot information and a shared snapshot information.
  • the container service instance sends the restored container service snapshot to the VNF instance, and the VNF instance sends the container service according to the restored container service snapshot.
  • the instance is restored to the running environment corresponding to the running information stored in the restored container service snapshot.
  • Step S404 The container service manager sends a recovery response to VNFM.
  • the recovery response is used to notify the VNFM container service manager to restore the container service instance to the running environment corresponding to the container service snapshot.
  • FIG. 7 is a schematic structural diagram of a container service snapshot management apparatus provided in Embodiment 5 of the present application.
  • the apparatus may be integrated in a container service manager. As shown in FIG. 7, the apparatus includes:
  • the receiving module 11 is configured to receive a container service snapshot creation request sent by the virtual network function manager VNFM, where the creation request includes an identifier of a container service instance to be created with a snapshot;
  • a creating module 12 is configured to create a container service snapshot for the container service instance, where the container service snapshot includes at least one dedicated snapshot information and one shared snapshot information, and the at least one dedicated snapshot information is to use the container service instance when taking a picture Specific operation information of a container service subscribed to by at least one VNF instance, wherein the at least one dedicated snapshot information corresponds to the at least one NVF instance one by one, and the shared snapshot information is a container service corresponding to the container service instance at Public running information in the snapshot;
  • the sending module 13 is configured to send a container service snapshot creation response to the VNFM, where the creation response includes an identifier of the container service snapshot.
  • the creation module 12 is specifically configured to:
  • the receiving module 11 is further configured to:
  • the configuration request including: a name of a VNF, a name of a container service, and specific operation information of the container service subscribed by the VNF.
  • the dedicated snapshot information includes at least one of the following operation information: a monitoring value, an event status, and / or an alarm of an operation performance indicator of the container service instance;
  • the shared snapshot information includes at least one of the following operating information: a software image of the container service, configuration information of the container service resource, an identifier of the container service descriptor file, a state of the container service instance, and a time stamp of the photo.
  • it further includes a deletion module (not shown in the figure);
  • the receiving module 11 is further configured to receive a deletion request of the container service snapshot sent by the VNFM, where the deletion request includes an identifier of the container service snapshot;
  • the deleting module is configured to delete the container service snapshot according to the deletion request
  • the sending module 13 is further configured to send a deletion response of the container service snapshot to the VNFM.
  • it further includes a recovery module (not shown in the figure);
  • the receiving module is further configured to receive a recovery request sent by the VNFM, where the recovery request is used to request to restore the running environment of the container service instance to the running environment corresponding to the container service snapshot, and the restore request
  • the identifier of the container service instance is included, the identifier of the VNF instance to be restored using the container service instance, and the identifier of the container service snapshot are used;
  • the recovery module is configured to find, according to the identifier of the VNF instance to be recovered and the identifier of the container service snapshot, the dedicated snapshot information corresponding to the VNF instance to be recovered from the container service snapshot;
  • the recovery module is further configured to generate the recovered service instance for the container service instance according to the dedicated snapshot information corresponding to the container service snapshot of the VNF instance to be restored and the shared snapshot information in the container service snapshot.
  • a container service snapshot restoring the running environment of the container service instance to the running environment corresponding to the running information stored in the generated restored container service snapshot;
  • the sending module 13 is further configured to send a recovery response of the container service snapshot to the VNFM.
  • the device provided in this embodiment may be used to execute the method steps performed by the container service manager in the first to fourth embodiments.
  • the specific implementation manner and technical effect are similar, and details are not described herein again.
  • FIG. 8 is a schematic structural diagram of a container service snapshot management apparatus provided in Embodiment 6 of the present application.
  • the apparatus may be integrated in VNFM. As shown in FIG. 8, the apparatus includes:
  • An obtaining module 21 configured to obtain specific operation information of a container service of a VNF subscription created according to the VNFD from a virtual network function descriptor VNFD;
  • the sending module 22 is configured to send a container service snapshot configuration request to the container service manager.
  • the configuration request includes: a name of the VNF, a name of the container service, and specific operation information of the container service subscribed by the VNF.
  • it further includes a receiving module 23;
  • the sending module 22 is further configured to send a container service snapshot creation request to the container service manager, where the creation request includes an identifier of a container service instance for which a snapshot is to be created;
  • the receiving module 23 is further configured to receive a container service snapshot creation response sent by the container service manager, where the creation response includes an identifier of the created container service snapshot.
  • the sending module 22 is further configured to send a deletion request of the container service snapshot to the container service manager, where the deletion request includes an identifier of the container service snapshot;
  • the receiving module 23 is further configured to receive a deletion response of the container service snapshot sent by the container service manager.
  • the sending module 22 is further configured to send a recovery request to the container service manager, where the recovery request is used to request that the running environment of the container service instance be restored to the running environment corresponding to the container service snapshot,
  • the recovery request includes an identifier of a container service instance, an identifier of a VNF instance to be restored using the container service instance, and an identifier of the container service snapshot;
  • the receiving module 23 is further configured to receive a recovery response of the container service snapshot sent by the container service manager.
  • the apparatus provided in this embodiment may be used to execute the method steps performed by the VNFM in the first to fourth embodiments.
  • the specific implementation manner and technical effect are similar, and are not described herein again.
  • FIG. 9 is a schematic structural diagram of a container service manager provided in Embodiment 7 of the present application.
  • the container service manager includes a processor 31, a memory 32, and a transceiver 33.
  • the memory 32 is configured to store instructions.
  • the transceiver 33 is configured to communicate with other devices, and the processor 31 is configured to execute instructions stored in the memory, so that the container service manager executes the execution of the container service manager as in the first to fourth embodiments.
  • the method steps, specific implementation methods and technical effects are similar, and are not repeated here.
  • FIG. 10 is a schematic structural diagram of a VNFM provided in Embodiment 8 of the application.
  • the VNFM provided in this embodiment includes a processor 41, a memory 42, and a transceiver 43.
  • the memory 42 is used to store instructions.
  • the transceiver 43 is configured to communicate with other devices, and the processor 41 is configured to execute instructions stored in the memory 42 to enable the VNFM to perform the method steps performed by the VNFM as in the first to fourth embodiments, and a specific implementation manner It is similar to the technical effect and will not be repeated here.
  • Embodiment 9 of the present application provides a computer-readable storage medium.
  • the computer-readable storage medium stores instructions.
  • the computer is caused to execute the instructions executed by the container service manager in Embodiments 1 to 4.
  • the method steps, specific implementation manners and technical effects are similar and will not be repeated here. .
  • a computer-readable storage medium stores instructions.
  • the computer is caused to execute the method steps performed by the VNFM in Embodiments 1 to 4.
  • the specific implementation manner is similar to the technical effect, and is not repeated here.
  • the processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or an off-the-shelf programmable gate array (FPGA). Or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present invention may be directly embodied as being executed by a hardware decoding processor, or may be executed and completed by using a combination of hardware and software units in the decoding processor.
  • the software unit can be located in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory or electrically erasable programmable memory, registers, etc.
  • Storage media The storage medium is located in a memory, and the processor reads the instructions in the memory and completes the steps of the foregoing method in combination with its hardware.
  • the disclosed apparatus and method may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be 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, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware, or in the form of hardware plus software functional units.

Landscapes

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

Abstract

本申请提供一种容器服务快照的管理方法和装置，包括：VNFM向容器服务管理器发送容器服务快照的创建请求，容器服务管理器为容器服务实例创建容器服务快照，该容器服务快照包括至少一个专用快照信息和一个共享快照信息，通过在同一个容器服务快照中保存至少一个VNF实例订阅的容器服务的特定运行信息和该容器服务在快照中的公共运行信息，降低了容器服务快照的数量，提高了容器服务快照的管理效率。另外，由于针对调用同一容器服务实例的多个VNF实例进行拍照的容器服务快照只需要保存一份容器服务实例的公共运行信息，降低了容器服务快照占用的存储资源，从而减轻了存储容器服务快照的磁盘的负载压力。

Description

容器服务快照的管理方法和装置
本申请要求于2018年7月20日提交中国国家知识产权局、申请号为201810804668.X、发明名称为“容器服务快照的管理方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术，尤其涉及一种容器服务快照的管理方法和装置。
背景技术
快照(Snapshot)技术是软件领域常用的一种技术，借鉴了摄影中的照片成像的原理，将数据在某一时刻的映像保留下来，以便后续可以根据快照查找数据在某一时刻的映像，作为增强数据备份的一种技术。
目前已将快照技术应用在了虚拟化网络功能(Virtualised Network Function，VNF)在线测试、故障诊断和快速恢复等过程中，是VNF自动化运维过程中非常重要的一个环节。VNF快照是指VNF实例在某个时间点的复制品，包括组成该VNF实例的所有虚拟化网络功能组件(Virtualized Network Function Component，VNFC)实例的快照、VNF描述符文件(Descriptor)和VNF信息对象(例如，与该VNF实例关联的虚拟链路、连接点的状态与设置)。VNFC快照是一个VNFC实例在某个时间点的复制品，它捕获了VNFC全部或部分的状态、在磁盘、内存和设备中存储的内容以及VNFC在基础设施中的配置等。虚拟化的电信网络功能逐渐进行容器化演进，容器即服务(Container as a Service，CaaS)是一种特定类型的平台即服务(Platform as a Service，PaaS)服务。容器是一种操作系统级别的虚拟化技术，通过操作系统隔离技术如Linux下的CGroup和NameSpace，将不同的进程隔离开来。容器技术不同于硬件虚拟化(Hypervisor)技术，并没有虚拟硬件，容器内部也没有操作系统，只有进程。正是由于容器技术的这个重要特点，使得容器相比虚拟机更轻量，管理也更方便。在容器的运行态，定义了一组公共的管理操作，例如：启动、停止、暂停和删除等，对容器进行统一的生命周期管理。
当虚拟化的电信网络功能进行容器化演进后，一个VNF实例包括的容器服务的数量显著增加，相应的，一个VNF快照对应的容器服务快照的数量也显著增加，导致需要管理的容器服务快照数量增加，存储容器服务快照的磁盘的负载压力大，另外，也不便于维护容器服务快照之间关联关系，从而影响容器服务故障定位和快速恢复。
发明内容
本申请提供一种容器服务快照的管理方法和装置，降低了容器服务快照的数量，提高了容器服务快照的管理效率。
本发明第一方面提供一种容器服务快照的管理方法，包括：
容器服务管理器接收虚拟化网络功能管理器VNFM发送的容器服务快照的创建请求，所述创建请求中包括待创建快照的容器服务实例的标识；
所述容器服务管理器为所述容器服务实例创建容器服务快照，所述容器服务快照包括至 少一个专用快照信息和一个共享快照信息，所述至少一个专用快照信息为拍照时使用所述容器服务实例的至少一个VNF实例订阅的容器服务的特定运行信息，其中，所述至少一个专用快照信息与所述至少一个NVF实例一一对应，所述共享快照信息为所述容器服务实例对应的容器服务在快照中的公共运行信息；
所述容器服务管理器向所述VNFM发送容器服务快照的创建响应，所述创建响应中包括所述容器服务快照的标识。
可选的，所述容器服务管理器为所述容器服务实例创建容器服务快照，包括：
所述容器服务管理器根据预先获取的使用所述容器服务的所述至少一个VNF实例订阅的所述容器服务的特定运行信息，生成所述容器服务快照的所述至少一个专用快照信息；
所述容器服务管理器根据所述容器服务实例的标识，生成所述容器服务快照的所述共享快照信息。
所述方法，通过在同一个容器服务快照中保存至少一个VNF实例订阅的容器服务的特定运行信息和该容器服务在快照中的公共运行信息，降低了容器服务快照的数量，提高了容器服务快照的管理效率。另外，由于针对调用同一容器服务实例的多个VNF实例进行拍照的容器服务快照只需要保存一份容器服务实例的公共运行信息，降低了容器服务快照占用的存储资源，从而减轻了存储容器服务快照的磁盘的负载压力。
可选的，还包括：
所述容器服务管理器接收所述VNFM发送的容器服务快照的配置请求，所述配置请求中包括：VNF的名称，容器服务的名称，以及所述VNF订阅的所述容器服务的特定运行信息。
可选的，所述专用快照信息包括以下运行信息中的至少一种：容器服务实例的运行性能指标的监控值、事件状态和/或告警；
所述共享快照信息包括以下运行信息中的至少一种：容器服务的软件镜像、容器服务资源的配置信息、容器服务描述符文件的标识、容器服务实例的状态、拍照的时间戳。
可选的，还包括：
所述容器服务管理器接收所述VNFM发送的容器服务快照的删除请求，所述删除请求中包括所述容器服务快照的标识；
所述容器服务管理器根据所述删除请求，删除所述容器服务快照；
所述容器服务管理器向所述VNFM发送容器服务快照的删除响应。
可选的，还包括：
所述容器服务管理器接收所述VNFM发送的恢复请求，所述恢复请求用于请求将所述容器服务实例的运行环境恢复到容器服务快照对应的运行环境，所述恢复请求中包括容器服务实例的标识，使用所述容器服务实例的待恢复的VNF实例的标识和所述容器服务快照的标识；
所述容器服务管理器根据所述待恢复的VNF实例的标识和所述容器服务快照的标识，从所述容器服务快照中查找所述待恢复的VNF实例对应的专用快照信息；
所述容器服务管理器根据所述待恢复的VNF实例在所述容器服务快照中对应的专用快照信息和所述容器服务快照中的共享快照信息，为所述容器服务实例生成恢复后的容器服务快照，将所述容器服务实例的运行环境恢复到所述生成的恢复后的容器服务快照中存储的运行信息对应的运行环境；
所述容器服务管理器向所述VNFM发送容器服务快照的恢复响应。
本申请第二方面提供一种容器服务快照的管理方法，包括：
虚拟化网络功能管理器VNFM从虚拟化网络功能描述符VNFD中获取根据所述VNFD创建的VNF订阅的容器服务的特定运行信息；
所述VNFM向容器服务管理器发送容器服务快照的配置请求，所述配置请求中包括：VNF的名称，容器服务的名称，以及所述VNF订阅的所述容器服务的特定运行信息。
可选的，还包括：
所述VNFM向所述容器服务管理器发送容器服务快照的创建请求，所述创建请求中包括待创建快照的容器服务实例的标识；
所述VNFM接收所述容器服务管理器发送的容器服务快照的创建响应，所述创建响应中包括创建的容器服务快照的标识。
可选的，还包括：
所述VNFM向所述容器服务管理器发送容器服务快照的删除请求，所述删除请求中包括所述容器服务快照的标识；
所述VNFM接收所述容器服务管理器发送的容器服务快照的删除响应。
可选的，还包括：
所述VNFM向所述容器服务管理器发送恢复请求，所述恢复请求用于请求将所述容器服务实例的运行环境恢复到容器服务快照对应的运行环境，所述恢复请求中包括容器服务实例的标识、使用所述容器服务实例的待恢复的VNF实例的标识和所述容器服务快照的标识；
所述VNFM接收所述容器服务管理器发送的容器服务快照的恢复响应。
本申请第三方面提供一种容器服务快照的管理装置，包括：
接收模块，用于接收虚拟化网络功能管理器VNFM发送的容器服务快照的创建请求，所述创建请求中包括待创建快照的容器服务实例的标识；
创建模块，用于为所述容器服务实例创建容器服务快照，所述容器服务快照包括至少一个专用快照信息和一个共享快照信息，所述至少一个专用快照信息为拍照时使用所述容器服务实例的至少一个VNF实例订阅的容器服务的特定运行信息，其中，所述至少一个专用快照信息与所述至少一个NVF实例一一对应，所述共享快照信息为所述容器服务实例对应的容器服务在快照中的公共运行信息；
发送模块，用于向所述VNFM发送容器服务快照的创建响应，所述创建响应中包括所述容器服务快照的标识。
可选的，所述创建模块具体用于：
根据预先获取的使用所述容器服务的所述至少一个VNF实例订阅的所述容器服务的特定运行信息，生成所述容器服务快照的所述至少一个专用快照信息；
根据所述容器服务实例的标识，生成所述容器服务快照的所述共享快照信息。
可选的，所述接收模块还用于：
接收所述VNFM发送的容器服务快照的配置请求，所述配置请求中包括：VNF的名称，容器服务的名称，以及所述VNF订阅的所述容器服务的特定运行信息。
可选的，所述专用快照信息包括以下运行信息中的至少一种：容器服务实例的运行性能指标的监控值、事件状态和/或告警；
所述共享快照信息包括以下运行信息中的至少一种：容器服务的软件镜像、容器服务资源的配置信息、容器服务描述符文件的标识、容器服务实例的状态、拍照的时间戳。
可选的，还包括删除模块；
所述接收模块，还用于接收所述VNFM发送的容器服务快照的删除请求，所述删除请求中包括所述容器服务快照的标识；
所述删除模块，用于根据所述删除请求，删除所述容器服务快照；
所述发送模块，还用于向所述VNFM发送容器服务快照的删除响应。
可选的，还包括恢复模块；
所述接收模块，还用于接收所述VNFM发送的恢复请求，所述恢复请求用于请求将所述容器服务实例的运行环境恢复到容器服务快照对应的运行环境，所述恢复请求中包括容器服务实例的标识，使用所述容器服务实例的待恢复的VNF实例的标识和所述容器服务快照的标识；
所述恢复模块，用于根据所述待恢复的VNF实例的标识和所述容器服务快照的标识，从所述容器服务快照中查找所述待恢复的VNF实例对应的专用快照信息；
所述恢复模块，还用于根据所述待恢复的VNF实例在所述容器服务快照中对应的专用快照信息和所述容器服务快照中的共享快照信息，为所述容器服务实例生成恢复后的容器服务快照，将所述容器服务实例的运行环境恢复到所述生成的恢复后的容器服务快照中存储的运行信息对应的运行环境；
所述发送模块，还用于向所述VNFM发送容器服务快照的恢复响应。
本申请第四方面提供一种容器服务快照的管理装置，包括：
获取模块，用于从虚拟化网络功能描述符VNFD中获取根据所述VNFD创建的VNF订阅的容器服务的特定运行信息；
发送模块，用于向容器服务管理器发送容器服务快照的配置请求，所述配置请求中包括：VNF的名称，容器服务的名称，以及所述VNF订阅的所述容器服务的特定运行信息。
可选的，还包括接收模块；
所述发送模块，还用于向所述容器服务管理器发送容器服务快照的创建请求，所述创建请求中包括待创建快照的容器服务实例的标识；
所述接收模块，还用于接收所述容器服务管理器发送的容器服务快照的创建响应，所述创建响应中包括创建的容器服务快照的标识。
可选的，所述发送模块还用于：向所述容器服务管理器发送容器服务快照的删除请求，所述删除请求中包括所述容器服务快照的标识；
所述接收模块，还用于接收所述容器服务管理器发送的容器服务快照的删除响应。
可选的，还包括：
所述发送模块，还用于向所述容器服务管理器发送恢复请求，所述恢复请求用于请求将所述容器服务实例的运行环境恢复到容器服务快照对应的运行环境，所述恢复请求中包括容器服务实例的标识、使用所述容器服务实例的待恢复的VNF实例的标识和所述容器服务快照的标识；
所述接收模块，还用于接收所述容器服务管理器发送的容器服务快照的恢复响应。
本申请第五方面提供一种容器服务管理器，包括处理器、存储器和收发器，所述存储器用于存储指令，所述收发器用于和其他设备通信，所述处理器用于执行所述存储器中存储的指令，以使所述容器服务管理器执行如本申请第一方面所述的方法。
本申请第六方面提供一种VNFM，包括处理器、存储器和收发器，所述存储器用于存储指令，所述收发器用于和其他设备通信，所述处理器用于执行所述存储器中存储的指令，以使所述VNFM执行如本申请第二方面所述的方法。
本申请第七方面提供一种计算机可读存储介质，所述计算机可读存储介质存储有指令，当所述指令被执行时，使得计算机执行如本申请第一方面所述的方法。
本申请第八方面提供一种计算机可读存储介质，所述计算机可读存储介质存储有指令，当所述指令被执行时，使得计算机执行如本申请第二方面所述的方法。
本申请提供的容器服务快照的管理方法和装置，包括：VNFM向容器服务管理器发送容器服务快照的创建请求，创建请求中包括待创建快照的容器服务实例的标识，容器服务管理器为容器服务实例创建容器服务快照，该容器服务快照包括至少一个专用快照信息和一个共享快照信息，该至少一个专用快照信息为拍照时使用容器服务实例的至少一个VNF实例订阅的容器服务的特定运行信息，该共享快照信息为容器服务实例对应的容器服务在快照中的公共运行信息。通过在同一个容器服务快照中保存至少一个VNF实例订阅的容器服务的特定运行信息和该容器服务在快照中的公共运行信息，降低了容器服务快照的数量，提高了容器服务快照的管理效率。另外，由于针对调用同一容器服务实例的多个VNF实例进行拍照的容器服务快照只需要保存一份容器服务实例的公共运行信息，降低了容器服务快照占用的存储资源，从而减轻了存储容器服务快照的磁盘的负载压力。
附图说明
图1为本申请适用的网络架构的示意图；
图2为本申请实施例一提供的容器服务快照的管理方法的信令流程图；
图3为VNF快照和容器服务快照的对应关系的示意图；
图4为本申请实施例二提供的容器服务快照的管理方法的信令流程图；
图5为本申请实施例三提供的容器服务快照的管理方法的信令流程图；
图6为本申请实施例四提供的容器服务快照的管理方法的信令流程图；
图7为本申请实施例五提供的容器服务快照的管理装置的结构示意图；
图8为本申请实施例六提供的容器服务快照的管理装置的结构示意图；
图9为本申请实施例七提供的容器服务管理器的结构示意图；
图10为本申请实施例八提供的VNFM的结构示意图。
具体实施方式
本申请提供一种容器服务快照的管理方法，本申请的方法基于网络功能虚拟化管理和编排(Network Function Virtualization MANagement and Orchestration，NFV MAMO)架构，本申请在NFV MANO系统架构中引入了容器服务管理功能，容器服务管理功能由容器服务(Container as a Service，CaaS)管理器完成。图1为本申请适用的网络架构的示意图，如图1所示，该网络架构为包括NFV MANO系统和容器服务管理器，其中，NFV MANO系统包括：网络功能虚拟化编排器(Network Function Virtualization Orchestrator，NFVO)、虚拟化网络功能管理器(Virtualised Network Function Manager，VNFM)、虚拟基础设施管理器(Virtualised Infrastructure Manager，VIM)、运营和商务支撑系统(Operations and Business Support Systems，OSS/BSS)、网元管理器(Element Manager，EM)、虚拟化网络功能(Virtualized Network Function，VNF)和虚拟化功能基础设施(Network Functions Virtualisation Infrastructure，NFVI)。
NFVO，用于实现网络服务描述符(Network Service Descriptor，NSD)和虚拟网络功能 转发图(Virtualised Network Function Forwarding Graph，VNFFG)的管理及处理，以及还用于对网络服务生命周期的管理，还可以和VNFM配合实现VNF的生命周期管理和资源的全局视图功能。
VNFM可以用于实现VNF的生命周期管理，具体可以包括虚拟化网络功能描述符(Virtualised Network Function Descriptor，VNFD)的管理及处理、VNF实例的初始化、VNF的扩容和缩容(即：弹性伸缩scaling)，以及VNF实例的终止，另外，VNFM还可以支持接收NFVO下发的弹性伸缩策略，实现VNF的自动化弹性伸缩。
VIM主要负责基础设施层硬件资源，虚拟化资源的管理(包括预留和分配)，虚拟资源状态的监控和故障上报，面向上层应用提供虚拟化资源池。
OSS/BSS主要面向电信服务运营商，提供综合的网络管理和业务运营功能，包括网络管理(例如故障监控、网络信息收集等)、计费管理以及客户服务管理等。
EM针对VNF执行传统的故障、配置、用户、性能和安全管理(Fault Management,Configuration Management，Account Management,Performance Management，Security Management，FCAPS)功能。
VNF对应于传统非虚拟化网络中的物理网络功能(PNF)，如虚拟化的EPC节点(MME，SGW，PGW等)。网络功能的功能性行为和状态与虚拟化与否无关，NFV技术需求希望VNF和PNF拥有相同的功能性行为和外部接口。VNF包括容器化VNF和传统VNF，传统VNF可以由一个或多个更低功能级别的VNF组件(VNF Component，VNFC)来组成，因此，一个VNF可以部署在多个虚拟机(Virtual Machine，VM)上，每个VM承载一个VNFC的功能，VNF也可以部署在一个VM上。容器化VNF通常由一个或多个微服务组成，每个微服务部署在一个或多个容器上，组成容器化VNF的微服务可以理解为服务化的VNFC。
NFVI由硬件资源和虚拟资源以及虚拟化层组成。从VNF的角度来说，虚拟化层和硬件资源看起来是一个能够提供所需虚拟资源的完整实体。
容器服务管理器用于对容器服务以及容器服务快照进行管理，例如配置、创建、删除、恢复容器服务快照。容器服务是比VNFC粒度更小的被管理对象，当VNF进行容器化演进后，一个VNF实例包括的容器服务的数量显著增加，相应的，一个VNF快照对应的容器服务快照的数量也显著增加，例如，一个VNF快照可以对应上百个或上千个容器服务的快照。另外，对于一些容器服务快照，一个容器服务快照可以被多个不同VNF实例共享使用，如果简单地按需(即：根据创建或删除VNF快照的需求)创建/删除容器服务快照，那么需要管理的容器服务快照的数量众多，对存储快照的磁盘带来较高的负载压力，同时也不便于维护不同的容器服务快照之间的关联关系，而这些关联关系在VNF故障定位分析或快速恢复中将发挥重要的线索作用。
为了上述问题，本申请实施例一提供一种容器服务快照的管理方法，本实施例主要描述容器服务快照的创建过程，图2为本申请实施例一提供的容器服务快照的管理方法的信令流程图，如图2所示，本实施例提供的方法包括以下步骤：
步骤S101、VNFM向容器服务管理器发送容器服务快照的创建请求，创建请求中包括待创建快照的容器服务实例的标识。
VNFM接收创建VNF快照的请求，并创建VNF快照，然后根据VNF快照的需求向容器服务管理器发送容器服务快照的创建请求，该创建请求用于请求为容器服务实例创建容器服务快照，该创建请求中包括待创建快照的容器服务实例的标识。
需要说明的是，容器服务需要通过容器服务实例实现，可以将一个容器服务实例化为多个容器服务实例。容器服务快照是对容器服务实例在某个时间进行快照得到的信息，容器服务快照中保存有容器服务实例在该时间的运行信息，后续根据容器服务快照可以将容器服务实例的运行环境恢复到该时间点对应的运行环境。
步骤S102、容器服务管理器为容器服务实例创建容器服务快照的至少一个专用快照信息。
步骤S103、容器服务管理器为容器服务实例创建容器服务快照的共享快照信息。
容器服务管理器为该创建请求中包括的容器服务实例的标识对应的容器服务实例创建容器服务快照，本实施例中，一个容器服务实例可以被一个或多个VNF实例使用，该容器服务实例在同一时间被不同VNF实例使用时，该容器服务实例的运行信息不同。因此，本实施例中，在某一时间对该容器服务实例创建的容器服务快照包括至少一个专用快照信息和一个共享快照信息。
其中，该至少一个专用快照信息为拍照时使用该容器服务实例的至少一个VNF实例订阅的容器服务的特定运行信息，该至少一个专用快照信息与该至少一个NVF实例一一对应，即为每个VNF实例生成一个专用快照信息，各专用快照信息通过对应的VNF实例的标识唯一标识，后续根据VNF实例的标识可以找到对应的专用快照信息。该专用快照信息包括以下信息中的至少一种：容器服务实例的运行性能指标的监控值、事件状态和/或告警。
该共享快照信息为容器服务实例对应的容器服务在快照中的公共运行信息，该共享快照信息包括以下运行信息中的至少一种：容器服务的软件镜像(image)、容器服务资源的配置信息、容器服务描述符文件(Container Service Descriptor)的标识、容器服务实例的状态、拍照的时间戳等。
示例性的，容器服务管理器可以根据预先获取的使用该容器服务的至少一个VNF实例订阅的容器服务的特定运行信息，生成容器服务快照的至少一个专用快照信息，根据容器服务实例的标识，生成容器服务快照的共享快照信息。其中，作为先决条件容器服务管理器可以存储不同的VNF对该容器服务订阅的特定运行信息，后续在创建容器服务快照的专用快照信息时，根据创建请求中包括的容器服务实例的标识确定正在使用该容器服务实例的VNF实例，根据VNF实例确定对应的VNF的名称，根据容器服务实例的标识确定对应的容器服务的名称，并根据该VNF的名称和该容器服务的名称，以及存储的VNF的名称，容器服务的名称，以及VNF订阅的容器服务的特定运行信息，确定该VNF订阅的该容器服务的特定运行信息，将该特定运行信息作为容器服务快照中对应于该VNF实例的专用快照信息。
本实施例中，容器服务快照中的各专用快照信息只能被对应的VNF实例使用，而共享快照信息可以被拍照时使用该容器服务实例的所有VNF实例使用。现有技术中，每个容器服务快照中存储的容器服务的运行信息只能为调用该容器服务实例的一个VNF实例使用，而本实施例中通过在同一个容器服务快照中保存至少一个VNF实例订阅的容器服务的特定运行信息和该容器服务在快照中的公共运行信息，相当于在一个容器服务快照中存储了多个VNF实例订阅的容器服务的运行信息，从而减少了容器服务快照的数量，提高了容器服务快照的管理效率。另外，由于多个VNF实例只需要保存一份公共运行信息，降低了VNF快照占用的存储资源，从而减轻了存储快照的磁盘的负载压力。
VNF快照和容器服务快照的对应关系，如图3所示，共有三个VNF快照：VNF1的快照、VNF2的快照和VNF3的快照，以及三个容器服务快照：容器服务快照1、容器服务快照2和容器服务快照3。容器服务快照1中包括VNF1对应的专用快照信息、VNF2对应的专用快照信息 以及共享快照信息。容器服务快照2中包括VNF1对应的专用快照信息、VNF3对应的专用快照信息以及共享快照信息。容器服务快照3中包括VNF3对应的专用快照信息和共享快照信息。
步骤S104、容器服务管理器向VNFM发送容器服务快照的创建响应，创建响应中包括容器服务快照的标识。
容器服务快照的标识用于唯一标识一个容器服务快照，容器服务实例将创建的容器服务快照的标识携带在创建响应中发送给VNFM。
本实施例中，VNFM向容器服务管理器发送容器服务快照的创建请求，创建请求中包括待创建快照的容器服务实例的标识，容器服务管理器为容器服务实例创建容器服务快照，该容器服务快照包括至少一个专用快照信息和一个共享快照信息，该至少一个专用快照信息为拍照时使用容器服务实例的至少一个VNF实例订阅的容器服务的特定运行信息，该共享快照信息为容器服务实例对应的容器服务在快照中的公共运行信息。通过在同一个容器服务快照中保存至少一个VNF实例订阅的容器服务的特定运行信息和该容器服务在快照中的公共运行信息，降低了容器服务快照的数量，提高了容器服务快照的管理效率。另外，由于针对调用同一容器服务实例的多个VNF实例进行拍照的容器服务快照只需要保存一份容器服务实例的公共运行信息，降低了容器服务快照占用的存储资源，从而减轻了存储容器服务快照的磁盘的负载压力。
图4为本申请实施例二提供的容器服务快照的管理方法的信令流程图，本实施例主要描述容器服务快照的配置过程，容器服务快照的配置过程在容器服务快照的创建过程之前，即本实施例在实施例一之前执行，如图4所示，本实施例提供的方法包括以下步骤：
步骤S201、VNFM从VNFD中获取根据该VNFD创建的VNF订阅的容器服务的特定运行信息。
VNFD是厂商用来部署虚拟网络功能的模板，描述的是VNF的组成、监控参数、部署规格等信息。一个VNFD根据不同的部署规格可以实例化多个VNF，一个VNFD根据同一个部署规格也可以实例化多个VNF。本实施例中，在VNFD增加了VNF订阅的容器服务的特定运行信息。其中，一个VNF可以实例化为多个VNF实例，每个VNF实例在创建容器服务快照时可能调用一个或多个容器服务，因此，这里VNF实例订阅的容器服务的特定运行信息是指该VNF实例在创建容器服务快照时所调用的一个或多个容器服务的特定运行信息。容器服务的特定运行信息以下信息中的至少一种：容器服务实例的运行性能指标的监控值、事件状态和/或告警。
步骤S202、VNFM向容器服务管理器发送容器服务快照的配置请求，该配置请求中包括：VNF的名称，容器服务的名称，以及VNF订阅的容器服务的特定运行信息。
步骤S203、容器服务管理器存储该配置请求中包括的VNF的名称，容器服务的名称，以及VNF订阅的该容器服务的特定运行信息。
VNFM保存VNF的名称、容器服务的名称、以及VNF订阅的容器服务的特定运行信息三者的对应关系，VNFM可以将VNF的名称、容器服务的名称以及VNF订阅的容器服务的特定运行信息以三元组形式保存在本地数据库中。容器服务管理器通过存储该配置请求中包括的VNF的名称，容器服务的名称，以及VNF实例订阅的该容器服务的特定运行信息，后续在创建容器服务快照时，根据存储的VNF的名称，容器服务的名称，以及VNF订阅的该容器服务的特定运行信息，生成容器服务快照的专用快照信息。
步骤S204、容器服务管理器向VNFM发送容器服务快照的配置响应。
该容器服务快照的配置响应用于通知VNFM容器服务快照配置完成，VNFM根据该配置响 应确定容器服务快照配置完成。
需要说明的是，如果对相同的VNF和容器服务执行多次容器服务快照的配置过程，那么后执行的配置过程将刷新前面执行的配置过程中确定的该VNF订阅的容器服务的特定运行信息。
本实施例中，通过在VNFD中增加VNF实例订阅的容器服务的特定运行信息，VNFM从VNFD中获取根据VNFD创建的VNF实例订阅的容器服务的特定运行信息，并向容器服务管理器发送容器服务快照的配置请求，该配置请求中包括：VNF的名称，容器服务的名称，以及VNF订阅的容器服务的特定运行信息，容器服务管理器保存该配置请求中包括的VNF的名称，容器服务的名称，以及VNF订阅的容器服务的特定运行信息，以便于后续根据保存的信息创建容器服务快照。
图5为本申请实施例三提供的容器服务快照的管理方法的信令流程图，本实施例主要描述容器服务快照的删除过程，容器服务快照的删除过程在容器服务快照的创建过程之后，即本实施例在实施例一之后执行，如图5所示，本实施例提供的方法包括以下步骤：
步骤S301、VNFM向容器服务管理器发送容器服务快照的删除请求，该删除请求中包括容器服务快照的标识。
该删除请求用于请求删除容器服务快照，VNFM在使用该容器服务快照的所有VNF快照都被删除之后，向容器服务管理器发送该删除请求，该删除请求中包括待删除的容器服务快照的标识。
步骤S302、容器服务管理器根据该删除请求，删除容器服务快照。
容器服务管理器根据该删除请求中包括的容器服务快照的标识，将该容器服务快照的标识对应的容器服务快照删除。
步骤S303、容器服务管理器向VNFM发送容器服务快照的删除响应。
该容器服务快照的删除响应用于通知VNFM容器服务快照删除完成，VNFM根据该删除响应确定容器服务快照删除完成。
图6为本申请实施例四提供的容器服务快照的管理方法的信令流程图，本实施例主要描述将容器服务实例恢复到容器服务快照对应的运行环境的过程，该恢复过程在容器服务快照的创建过程之后，即本实施例在实施例一之后执行，如图6所示，本实施例提供的方法包括以下步骤：
步骤S401、VNFM向容器服务管理器发送恢复请求，该恢复请求中包括容器服务实例的标识、使用容器服务实例的待恢复的VNF实例的标识和容器服务快照的标识。
该恢复请求用于请求将容器服务实例的运行环境恢复到容器服务快照对应的运行环境，VNFM可以在接收到VNF快照的恢复请求时，向容器服务管理器发送该恢复请求，其中，VNF快照的恢复请求用于请求恢复到指定的VNF快照。
步骤S402、容器服务管理器根据待恢复的VNF实例的标识和容器服务快照的标识，从容器服务快照中查找待恢复的VNF实例对应的专用快照信息。
容器服务管理器先根据容器服务快照的标识找到对应的容器服务快照，该容器服务快照中包括至少一个专用快照信息和一个共享快照信息，每个专用快照信息唯一对应一个VNF实例，容器服务管理器根据待恢复的VNF实例的标识，从该容器服务快照包括的至少一个专用 快照信息中找到待恢复的VNF实例的标识对应的专用快照信息。
步骤S403、容器服务管理器根据待恢复的VNF实例在容器服务快照中对应的专用快照信息和容器服务快照中的共享快照信息，为容器服务实例生成恢复后的容器服务快照，将容器服务实例的运行环境恢复到生成的恢复后的容器服务快照中存储的运行信息对应的运行环境。
容器服务实例的恢复后的容器服务快照中包括一个专用快照信息和一个共享快照信息，容器服务实例将恢复后的容器服务快照发送给VNF实例，由VNF实例根据恢复后的容器服务快照将容器服务实例恢复到恢复后的容器服务快照中存储的运行信息对应的运行环境。
步骤S404、容器服务管理器向VNFM发送恢复响应。
该恢复响应用于通知VNFM容器服务管理器将容器服务实例恢复到了容器服务快照对应的运行环境。
图7为本申请实施例五提供的容器服务快照的管理装置的结构示意图，该装置可以集成在容器服务管理器中，如图7所示，该装置包括：
接收模块11，用于接收虚拟化网络功能管理器VNFM发送的容器服务快照的创建请求，所述创建请求中包括待创建快照的容器服务实例的标识；
创建模块12，用于为所述容器服务实例创建容器服务快照，所述容器服务快照包括至少一个专用快照信息和一个共享快照信息，所述至少一个专用快照信息为拍照时使用所述容器服务实例的至少一个VNF实例订阅的容器服务的特定运行信息，其中，所述至少一个专用快照信息与所述至少一个NVF实例一一对应，所述共享快照信息为所述容器服务实例对应的容器服务在快照中的公共运行信息；
发送模块13，用于向所述VNFM发送容器服务快照的创建响应，所述创建响应中包括所述容器服务快照的标识。
可选的，所述创建模块12具体用于：
根据预先获取的使用所述容器服务的所述至少一个VNF实例订阅的所述容器服务的特定运行信息，生成所述容器服务快照的所述至少一个专用快照信息；
根据所述容器服务实例的标识，生成所述容器服务快照的所述共享快照信息。
可选的，所述接收模块11还用于：
接收所述VNFM发送的容器服务快照的配置请求，所述配置请求中包括：VNF的名称，容器服务的名称，以及所述VNF订阅的所述容器服务的特定运行信息。
可选的，所述专用快照信息包括以下运行信息中的至少一种：容器服务实例的运行性能指标的监控值、事件状态和/或告警；
所述共享快照信息包括以下运行信息中的至少一种：容器服务的软件镜像、容器服务资源的配置信息、容器服务描述符文件的标识、容器服务实例的状态、拍照的时间戳。
可选的，还包括删除模块(图中未示出)；
相应的，所述接收模块11，还用于接收所述VNFM发送的容器服务快照的删除请求，所述删除请求中包括所述容器服务快照的标识；
所述删除模块，用于根据所述删除请求，删除所述容器服务快照；
所述发送模块13，还用于向所述VNFM发送容器服务快照的删除响应。
可选的，还包括恢复模块(图中未示出)；
相应的，所述接收模块，还用于接收所述VNFM发送的恢复请求，所述恢复请求用于请求 将所述容器服务实例的运行环境恢复到容器服务快照对应的运行环境，所述恢复请求中包括容器服务实例的标识，使用所述容器服务实例的待恢复的VNF实例的标识和所述容器服务快照的标识；
所述恢复模块，用于根据所述待恢复的VNF实例的标识和所述容器服务快照的标识，从所述容器服务快照中查找所述待恢复的VNF实例对应的专用快照信息；
所述恢复模块，还用于根据所述待恢复的VNF实例在所述容器服务快照中对应的专用快照信息和所述容器服务快照中的共享快照信息，为所述容器服务实例生成恢复后的容器服务快照，将所述容器服务实例的运行环境恢复到所述生成的恢复后的容器服务快照中存储的运行信息对应的运行环境；
所述发送模块13，还用于向所述VNFM发送容器服务快照的恢复响应。
本实施例提供的装置，可用于执行实施例一至实施例四中容器服务管理器执行的方法步骤，具体实现方式和技术效果类似，这里不再赘述。
图8为本申请实施例六提供的容器服务快照的管理装置的结构示意图，该装置可以集成在VNFM中，如图8所示，该装置包括：
获取模块21，用于从虚拟化网络功能描述符VNFD中获取根据所述VNFD创建的VNF订阅的容器服务的特定运行信息；
发送模块22，用于向容器服务管理器发送容器服务快照的配置请求，所述配置请求中包括：VNF的名称，容器服务的名称，以及所述VNF订阅的所述容器服务的特定运行信息。
可选的，还包括接收模块23；
所述发送模块22，还用于向所述容器服务管理器发送容器服务快照的创建请求，所述创建请求中包括待创建快照的容器服务实例的标识；
所述接收模块23，还用于接收所述容器服务管理器发送的容器服务快照的创建响应，所述创建响应中包括创建的容器服务快照的标识。
可选的，所述发送模块22还用于：向所述容器服务管理器发送容器服务快照的删除请求，所述删除请求中包括所述容器服务快照的标识；
所述接收模块23，还用于接收所述容器服务管理器发送的容器服务快照的删除响应。
可选的，所述发送模块22，还用于向所述容器服务管理器发送恢复请求，所述恢复请求用于请求将所述容器服务实例的运行环境恢复到容器服务快照对应的运行环境，所述恢复请求中包括容器服务实例的标识、使用所述容器服务实例的待恢复的VNF实例的标识和所述容器服务快照的标识；
所述接收模块23，还用于接收所述容器服务管理器发送的容器服务快照的恢复响应。
本实施例提供的装置，可用于执行实施例一至实施例四中VNFM执行的方法步骤，具体实现方式和技术效果类似，这里不再赘述。
图9为本申请实施例七提供的容器服务管理器的结构示意图，如图9所示，该容器服务管理器包括处理器31、存储器32和收发器33，所述存储器32用于存储指令，所述收发器33用于和其他设备通信，所述处理器31用于执行所述存储器中存储的指令，以使所述容器服务管理器执行如实施例一至实施例四中容器服务管理器执行的方法步骤，具体实现方式和技术效果类似，这里不再赘述。
图10为本申请实施例八提供的VNFM的结构示意图，如图10所示，本实施例提供的VNFM包括处理器41、存储器42和收发器43，所述存储器42用于存储指令，所述收发器43用于和其他设备通信，所述处理器41用于执行所述存储器42中存储的指令，以使所述VNFM执行如实施例一至实施例四中VNFM执行的方法步骤，具体实现方式和技术效果类似，这里不再赘述。
本申请实施例九提供一种计算机可读存储介质，所述计算机可读存储介质存储有指令，当所述指令被执行时，使得计算机执行如实施例一至实施例四中容器服务管理器执行的方法步骤，具体实现方式和技术效果类似，这里不再赘述。。
本申请第八方面提供一种计算机可读存储介质，所述计算机可读存储介质存储有指令，当所述指令被执行时，使得计算机执行如实施例一至实施例四中VNFM执行的方法步骤，具体实现方式和技术效果类似，这里不再赘述。
上述各个实施例中处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本发明实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件单元组合执行完成。软件单元可以位于随机存取存储器(random access memory，RAM)、闪存、只读存储器(read-only memory，ROM)、可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的指令，结合其硬件完成上述方法的步骤。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。

Claims (24)

  1. 一种容器服务快照的管理方法，其特征在于，包括：
    容器服务管理器接收虚拟化网络功能管理器VNFM发送的容器服务快照的创建请求，所述创建请求中包括待创建快照的容器服务实例的标识；
    所述容器服务管理器为所述容器服务实例创建容器服务快照，所述容器服务快照包括至少一个专用快照信息和一个共享快照信息，所述至少一个专用快照信息为拍照时使用所述容器服务实例的至少一个VNF实例订阅的容器服务的特定运行信息，其中，所述至少一个专用快照信息与所述至少一个NVF实例一一对应，所述共享快照信息为所述容器服务实例对应的容器服务在快照中的公共运行信息；
    所述容器服务管理器向所述VNFM发送容器服务快照的创建响应，所述创建响应中包括所述容器服务快照的标识。
  2. 根据权利要求1所述的方法，其特征在于，所述容器服务管理器为所述容器服务实例创建容器服务快照，包括：
    所述容器服务管理器根据预先获取的使用所述容器服务的所述至少一个VNF实例订阅的所述容器服务的特定运行信息，生成所述容器服务快照的所述至少一个专用快照信息；
    所述容器服务管理器根据所述容器服务实例的标识，生成所述容器服务快照的所述共享快照信息。
  3. 根据权利要求2所述的方法，其特征在于，还包括：
    所述容器服务管理器接收所述VNFM发送的容器服务快照的配置请求，所述配置请求中包括：VNF的名称，容器服务的名称，以及所述VNF订阅的所述容器服务的特定运行信息。
  4. 根据权利要求1所述的方法，其特征在于，所述专用快照信息包括以下运行信息中的至少一种：容器服务实例的运行性能指标的监控值、事件状态和/或告警；
    所述共享快照信息包括以下运行信息中的至少一种：容器服务的软件镜像、容器服务资源的配置信息、容器服务描述符文件的标识、容器服务实例的状态、拍照的时间戳。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，还包括：
    所述容器服务管理器接收所述VNFM发送的容器服务快照的删除请求，所述删除请求中包括所述容器服务快照的标识；
    所述容器服务管理器根据所述删除请求，删除所述容器服务快照；
    所述容器服务管理器向所述VNFM发送容器服务快照的删除响应。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，还包括：
    所述容器服务管理器接收所述VNFM发送的恢复请求，所述恢复请求用于请求将所述容器服务实例的运行环境恢复到容器服务快照对应的运行环境，所述恢复请求中包括容器服务实例的标识，使用所述容器服务实例的待恢复的VNF实例的标识和所述容器服务快照的标识；
    所述容器服务管理器根据所述待恢复的VNF实例的标识和所述容器服务快照的标识，从所述容器服务快照中查找所述待恢复的VNF实例对应的专用快照信息；
    所述容器服务管理器根据所述待恢复的VNF实例在所述容器服务快照中对应的专用快照信息和所述容器服务快照中的共享快照信息，为所述容器服务实例生成恢复后的容器服务快照，将所述容器服务实例的运行环境恢复到所述生成的恢复后的容器服务快照中存储的运行 信息对应的运行环境；
    所述容器服务管理器向所述VNFM发送容器服务快照的恢复响应。
  7. 一种容器服务快照的管理方法，其特征在于，包括：
    虚拟化网络功能管理器VNFM从虚拟化网络功能描述符VNFD中获取根据所述VNFD创建的VNF订阅的容器服务的特定运行信息；
    所述VNFM向容器服务管理器发送容器服务快照的配置请求，所述配置请求中包括：VNF的名称，容器服务的名称，以及所述VNF订阅的所述容器服务的特定运行信息。
  8. 根据权利要求7所述的方法，其特征在于，还包括：
    所述VNFM向所述容器服务管理器发送容器服务快照的创建请求，所述创建请求中包括待创建快照的容器服务实例的标识；
    所述VNFM接收所述容器服务管理器发送的容器服务快照的创建响应，所述创建响应中包括创建的容器服务快照的标识。
  9. 根据权利要求7或8所述的方法，其特征在于，还包括：
    所述VNFM向所述容器服务管理器发送容器服务快照的删除请求，所述删除请求中包括所述容器服务快照的标识；
    所述VNFM接收所述容器服务管理器发送的容器服务快照的删除响应。
  10. 根据权利要求7-9任一项所述的方法，其特征在于，还包括：
    所述VNFM向所述容器服务管理器发送恢复请求，所述恢复请求用于请求将所述容器服务实例的运行环境恢复到容器服务快照对应的运行环境，所述恢复请求中包括容器服务实例的标识、使用所述容器服务实例的待恢复的VNF实例的标识和所述容器服务快照的标识；
    所述VNFM接收所述容器服务管理器发送的容器服务快照的恢复响应。
  11. 一种容器服务快照的管理装置，其特征在于，包括：
    接收模块，用于接收虚拟化网络功能管理器VNFM发送的容器服务快照的创建请求，所述创建请求中包括待创建快照的容器服务实例的标识；
    创建模块，用于为所述容器服务实例创建容器服务快照，所述容器服务快照包括至少一个专用快照信息和一个共享快照信息，所述至少一个专用快照信息为拍照时使用所述容器服务实例的至少一个VNF实例订阅的容器服务的特定运行信息，其中，所述至少一个专用快照信息与所述至少一个NVF实例一一对应，所述共享快照信息为所述容器服务实例对应的容器服务在快照中的公共运行信息；
    发送模块，用于向所述VNFM发送容器服务快照的创建响应，所述创建响应中包括所述容器服务快照的标识。
  12. 根据权利要求11所述的装置，其特征在于，所述创建模块具体用于：
    根据预先获取的使用所述容器服务的所述至少一个VNF实例订阅的所述容器服务的特定运行信息，生成所述容器服务快照的所述至少一个专用快照信息；
    根据所述容器服务实例的标识，生成所述容器服务快照的所述共享快照信息。
  13. 根据权利要求12所述的装置，其特征在于，所述接收模块还用于：
    接收所述VNFM发送的容器服务快照的配置请求，所述配置请求中包括：VNF的名称，容器服务的名称，以及所述VNF订阅的所述容器服务的特定运行信息。
  14. 根据权利要求11所述的装置，其特征在于，所述专用快照信息包括以下运行信息中的至少一种：容器服务实例的运行性能指标的监控值、事件状态和/或告警；
    所述共享快照信息包括以下运行信息中的至少一种：容器服务的软件镜像、容器服务资源的配置信息、容器服务描述符文件的标识、容器服务实例的状态、拍照的时间戳。
  15. 根据权利要求11-14任一项所述的装置，其特征在于，还包括删除模块；
    所述接收模块，还用于接收所述VNFM发送的容器服务快照的删除请求，所述删除请求中包括所述容器服务快照的标识；
    所述删除模块，用于根据所述删除请求，删除所述容器服务快照；
    所述发送模块，还用于向所述VNFM发送容器服务快照的删除响应。
  16. 根据权利要求11-15任一项所述的装置，其特征在于，还包括恢复模块；
    所述接收模块，还用于接收所述VNFM发送的恢复请求，所述恢复请求用于请求将所述容器服务实例的运行环境恢复到容器服务快照对应的运行环境，所述恢复请求中包括容器服务实例的标识，使用所述容器服务实例的待恢复的VNF实例的标识和所述容器服务快照的标识；
    所述恢复模块，用于根据所述待恢复的VNF实例的标识和所述容器服务快照的标识，从所述容器服务快照中查找所述待恢复的VNF实例对应的专用快照信息；
    所述恢复模块，还用于根据所述待恢复的VNF实例在所述容器服务快照中对应的专用快照信息和所述容器服务快照中的共享快照信息，为所述容器服务实例生成恢复后的容器服务快照，将所述容器服务实例的运行环境恢复到所述生成的恢复后的容器服务快照中存储的运行信息对应的运行环境；
    所述发送模块，还用于向所述VNFM发送容器服务快照的恢复响应。
  17. 一种容器服务快照的管理装置，其特征在于，包括：
    获取模块，用于从虚拟化网络功能描述符VNFD中获取根据所述VNFD创建的VNF订阅的容器服务的特定运行信息；
    发送模块，用于向容器服务管理器发送容器服务快照的配置请求，所述配置请求中包括：VNF的名称，容器服务的名称，以及所述VNF订阅的所述容器服务的特定运行信息。
  18. 根据权利要求17所述的装置，其特征在于，还包括接收模块；
    所述发送模块，还用于向所述容器服务管理器发送容器服务快照的创建请求，所述创建请求中包括待创建快照的容器服务实例的标识；
    所述接收模块，还用于接收所述容器服务管理器发送的容器服务快照的创建响应，所述创建响应中包括创建的容器服务快照的标识。
  19. 根据权利要求18所述的装置，其特征在于，所述发送模块还用于：向所述容器服务管理器发送容器服务快照的删除请求，所述删除请求中包括所述容器服务快照的标识；
    所述接收模块，还用于接收所述容器服务管理器发送的容器服务快照的删除响应。
  20. 根据权利要求17-19任一项所述的装置，其特征在于，还包括：
    所述发送模块，还用于向所述容器服务管理器发送恢复请求，所述恢复请求用于请求将所述容器服务实例的运行环境恢复到容器服务快照对应的运行环境，所述恢复请求中包括容器服务实例的标识、使用所述容器服务实例的待恢复的VNF实例的标识和所述容器服务快照的标识；
    所述接收模块，还用于接收所述容器服务管理器发送的容器服务快照的恢复响应。
  21. 一种容器服务管理器，其特征在于，包括处理器、存储器和收发器，所述存储器用于存储指令，所述收发器用于和其他设备通信，所述处理器用于执行所述存储器中存储的指令，以使所述容器服务管理器执行如权利要求1-6任一项所述的方法。
  22. 一种虚拟化网络功能管理器VNFM，其特征在于，包括处理器、存储器和收发器，所述存储器用于存储指令，所述收发器用于和其他设备通信，所述处理器用于执行所述存储器中存储的指令，以使所述VNFM执行如权利要求7-10任一项所述的方法。
  23. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有指令，当所述指令被执行时，使得计算机执行如权利要求1-6任一项所述的方法。
  24. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有指令，当所述指令被执行时，使得计算机执行如权利要求7-10任一项所述的方法。
PCT/CN2019/096872 2018-07-20 2019-07-19 容器服务快照的管理方法和装置 WO2020015751A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810804668.XA CN110737503B (zh) 2018-07-20 2018-07-20 容器服务快照的管理方法和装置
CN201810804668.X 2018-07-20

Publications (1)

Publication Number Publication Date
WO2020015751A1 true WO2020015751A1 (zh) 2020-01-23

Family

ID=69164282

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/096872 WO2020015751A1 (zh) 2018-07-20 2019-07-19 容器服务快照的管理方法和装置

Country Status (2)

Country Link
CN (1) CN110737503B (zh)
WO (1) WO2020015751A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112835683A (zh) * 2021-03-02 2021-05-25 杭州雅观科技有限公司 一种智慧社区软件的容器化部署系统

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111786904B (zh) * 2020-07-07 2021-07-06 上海道客网络科技有限公司 一种实现容器休眠与唤醒的系统及休眠与唤醒方法
CN116662267B (zh) * 2023-08-02 2024-04-05 中国电子投资控股有限公司 一种基于云原生的分布式应用快照系统和快照创建方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140195753A1 (en) * 2013-01-09 2014-07-10 International Business Machines Corporation Managing virtual hard disk snapshots
CN104809020A (zh) * 2013-11-20 2015-07-29 华为技术有限公司 一种生成快照的方法、系统和装置
CN105335253A (zh) * 2015-10-28 2016-02-17 北京百度网讯科技有限公司 创建虚拟机系统盘快照的方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101616028B (zh) * 2009-06-25 2012-02-29 中兴通讯股份有限公司 一种通信程序业务不中断升级方法及系统
CN103049334B (zh) * 2012-12-14 2015-09-30 华为技术有限公司 一种任务处理的方法和虚拟机

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140195753A1 (en) * 2013-01-09 2014-07-10 International Business Machines Corporation Managing virtual hard disk snapshots
CN104809020A (zh) * 2013-11-20 2015-07-29 华为技术有限公司 一种生成快照的方法、系统和装置
CN105335253A (zh) * 2015-10-28 2016-02-17 北京百度网讯科技有限公司 创建虚拟机系统盘快照的方法和装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112835683A (zh) * 2021-03-02 2021-05-25 杭州雅观科技有限公司 一种智慧社区软件的容器化部署系统
CN112835683B (zh) * 2021-03-02 2023-12-12 杭州雅观科技有限公司 一种智慧社区软件的容器化部署系统

Also Published As

Publication number Publication date
CN110737503B (zh) 2021-09-14
CN110737503A (zh) 2020-01-31

Similar Documents

Publication Publication Date Title
US10831574B2 (en) Remote procedure call method for network device and network device
US10326653B2 (en) Method for upgrading network functions virtualization application, service forwarding method, and apparatus
CN110377395B (zh) 一种Kubernetes集群中的Pod迁移方法
US10073902B2 (en) Snapshot and replication of a multi-stream application on multiple hosts at near-sync frequency
US20180018193A1 (en) Virtual network function management apparatus, system, healing method, and program
CN107608757B (zh) 一种基于容器的隔离处理方法及相关设备
CN111641515B (zh) Vnf的生命周期管理方法及装置
WO2020015751A1 (zh) 容器服务快照的管理方法和装置
US20190146827A1 (en) Virtualized network function resource management method and device
EP3694167B1 (en) Method and device for managing services in network function virtualization architecture
US20210294623A1 (en) Data processing method and apparatus, and server
EP3452904B1 (en) Snapshot creation in virtual network environment
WO2016121834A1 (ja) ネットワーク機能仮想化管理方法とシステムと装置とプログラム
US9710332B1 (en) Data provenance in computing infrastructure
WO2020103925A1 (zh) 一种容器化虚拟网络功能的部署方法和装置
US20190377592A1 (en) System and method for provisioning devices of a decentralized cloud
US9959157B1 (en) Computing instance migration
CN109428764B (zh) 虚拟网络功能的实例化方法
WO2017045436A1 (zh) 虚拟机故障处理方法和装置
WO2016062116A1 (zh) 一种虚拟化网络备份、恢复的方法和相应装置
US11656944B1 (en) Code function checkpoint and restore
CN113326098B (zh) 支持kvm虚拟化与容器虚拟化的云管平台
US11543945B1 (en) Accurate local depiction of preview of a program window included in a remote graphical desktop
WO2020211685A1 (zh) 恢复vnf实例的方法、装置和设备
CN110677268B (zh) Nfv自动编排调度方法、装置和系统

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19838387

Country of ref document: EP

Kind code of ref document: A1