WO2019109948A1 - Paas management method and device, and storage medium - Google Patents
Paas management method and device, and storage medium Download PDFInfo
- Publication number
- WO2019109948A1 WO2019109948A1 PCT/CN2018/119367 CN2018119367W WO2019109948A1 WO 2019109948 A1 WO2019109948 A1 WO 2019109948A1 CN 2018119367 W CN2018119367 W CN 2018119367W WO 2019109948 A1 WO2019109948 A1 WO 2019109948A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- target service
- service
- instance
- tenant
- paas
- Prior art date
Links
Images
Classifications
-
- 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/508—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement
- H04L41/5096—Network service management, e.g. ensuring proper service fulfilment according to agreements based on type of value added network service under agreement wherein the managed service relates to distributed or central networked applications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
-
- 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
-
- 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5061—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the interaction between service providers and their network customers, e.g. customer relationship management
- H04L41/5064—Customer relationship management
Definitions
- the present application relates to the field of cloud computing technologies, and in particular, to a method, an apparatus, and a storage medium for managing Platform as a Service (PaaS).
- PaaS Platform as a Service
- PaaS refers to providing the server as a service to users so that users can develop, test, and deploy applications such as applications online.
- the implementation of PaaS is mainly through Network Function Virtualization (NFV) technology, that is, the PaaS is deployed in the NFV architecture, and the virtualized network function (VNF) in the NFV architecture is in the instance.
- NFV Network Function Virtualization
- VNF virtualized network function
- the service deployed on the PaaS needs to be invoked, the service is instantiated to implement the network function corresponding to the service.
- instantiation refers to the process of configuring virtual resources for services or VNFs through the Network Function Virtualization Infrastructure (NFVI) in the NFV architecture.
- NFVI Network Function Virtualization Infrastructure
- the VNF that invokes a service can be called the service tenant of the service.
- the life cycle of the public service is independent of the life cycle of the VNF that invokes the public service, that is, the public service remains online after the instantiation, and a VNF in the NFV architecture needs to be invoked during the instantiation process.
- the public service only needs to invoke the instance corresponding to the public service, and the instance of the public service does not end with the termination of the instance of the VNF.
- the life cycle of a proprietary service is closely related to the life cycle of the VNF that invokes the proprietary service, that is, the proprietary service is instantiated with the instantiation of the VNF that invoked the proprietary service, with the call of the proprietary service
- the end of the VNF instance ends.
- the public service instance is kept online, which increases the resource occupation burden on the PaaS; and for the proprietary service, the proprietary service The instance of the service will be terminated with the termination of the instance of the VNF that invoked the proprietary service, so each time the proprietary service is invoked, the proprietary service needs to be instantiated, reducing the flexibility of the application of the proprietary service. Sex.
- the present application provides a method, an apparatus, and a storage medium for managing a PaaS.
- the technical solution is as follows:
- a method for managing a PaaS which is applied to a PaaS deployed in an NFV architecture, where a plurality of services are deployed on the PaaS, and the method includes:
- a service configuration request for a target service sent by a Management and Orchestration (MANO) entity in the NFV architecture the service configuration request being a target service tenant in the determining the NFV architecture by the MANO entity
- the target service is any one of the multiple services
- the contract binding relationship between the target service tenant and the target service is first released, and other service tenants and target services in the NFV architecture are determined to be absent.
- the contract binding relationship is terminated, all instances of the target service are terminated, instead of terminating all instances of the target service directly when the target service tenant no longer invokes the target service. Therefore, the service provided by the present application does not have to end with the end of the service tenant instance like the proprietary service, which improves the application flexibility of the service on the PaaS.
- the service configuration request carries a configuration type, an identifier of the target service tenant, and an identifier of the target service, where the configuration type is a contract cancellation.
- the contract binding relationship between the target service tenant and the target service needs to be dismissed, and in some scenarios, the use binding relationship between the target service tenant instance and the target service instance needs to be released.
- the type of configuration carried in the service configuration request can be used to determine which relationship needs to be terminated.
- the method further includes:
- the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and a lag time, where the configuration type is decommissioning;
- the canceling a contract binding relationship between the target service tenant and the target service based on the service configuration request includes:
- the contract binding relationship between the target service and the target service tenant is released.
- the configuration type when the configuration type is decommissioning, it indicates that the MANO entity wants to release the use binding relationship between the target service tenant instance and the target service instance, and the PaaS is between the target service tenant instance and the target service instance. After the binding relationship is used, the contract binding relationship between the target service tenant and the target service can also be cancelled in the above manner.
- the method further includes:
- the second type of service configuration response message indicating that a usage binding relationship between the instance of the target service and an instance of the target service tenant has been released.
- the MANO entity needs to be notified in time that the binding relationship has been released.
- the method before receiving the service configuration request for the target service sent by the MANO entity in the NFV architecture, the method further includes:
- the PaaS may establish a binding relationship between the target service tenant instance and the target service instance when the MANO entity sends the configuration request, and establish the target service tenant and the target service according to actual conditions. Contract binding relationship between.
- the method before receiving the configuration request sent by the MANO entity, the method further includes:
- the first response message is used to indicate that the target service has been instantiated, and the A response message carries an identifier of an instance of the target service;
- the MANO entity sends an instantiation response message, the instantiated response message carrying an identity of an instance of the target service.
- the MANO entity can obtain the identity of the instance of the target service by sending an instance acquisition request to the PaaS.
- the PaaS determines that there is currently no instance of the target service, it also needs to feed back to the MANO entity an instance of the target service that does not currently exist, so that the MANO entity sends an instantiation request for the target service.
- the instantiating the target service based on the identifier of the target service, and obtaining an instance of the target service including:
- the PaaS can instantiate the target service through the above process to obtain an instance of the target service.
- the MANO entity is a virtual network function manager (VNFM) in the NFV architecture.
- VNFM virtual network function manager
- the MANO entity may be a VNFM in the NFV architecture.
- Another method for managing a PaaS is provided, which is applied to a MANO entity in a network function virtualization NFV architecture, where the NFV architecture is deployed with PaaS, wherein a plurality of services are deployed on the PaaS.
- the method includes:
- the service configuration request is used to instruct the PaaS to cancel a contract binding relationship between the target service tenant and the target service based on the service configuration request, and determine that there is no other service tenant and the target service. Terminating all instances of the target service when the contract binding relationship is, the target service being any of the plurality of services.
- the MANO entity may send a service configuration request to the PaaS, so that the PaaS first removes the contract binding relationship between the target service tenant and the target service, and determines
- the PaaS first removes the contract binding relationship between the target service tenant and the target service, and determines
- all instances of the target service are terminated, instead of terminating all instances of the target service directly when the target service tenant no longer invokes the target service. Therefore, the service provided by the present application does not have to end with the end of the service tenant instance like the proprietary service, which improves the application flexibility of the service on the PaaS.
- a service configuration request for the target service to the PaaS, including:
- the MANO entity may be triggered to send a service configuration request to the PaaS.
- the method further includes:
- the MANO entity When the MANO entity receives the first type of service configuration response message, it indicates that the PaaS has released the contract binding relationship between the target service and the target service tenant.
- a service configuration request for the target service to the PaaS, including:
- the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and the lag time, where the configuration type is use.
- the MANO entity may be triggered to send a service configuration request to the PaaS.
- the method further includes:
- the MANO entity When the MANO entity receives the second type of service configuration response message, it indicates that the PaaS has deactivated the use binding relationship between the instance of the target service and the instance of the target service tenant.
- the method before the sending the service configuration request for the target service to the PaaS, the method further includes:
- the MANO entity may send a configuration request to the PaaS to enable the PaaS to establish a binding relationship between the instance of the target service tenant and the instance of the target service.
- the method before the sending the configuration request to the PaaS, the method further includes:
- the MANO entity may obtain the identifier of the instance of the target service by using the foregoing two methods before sending the configuration request.
- the MANO entity may also obtain the identifier of the instance of the target service by sending an instantiation request when the instance of the target service does not exist in the PaaS.
- the MANO entity is a virtual network function manager VNFM in the NFV architecture.
- the MANO entity may be a VNFM in the NFV architecture.
- a management apparatus for a PaaS having a function of implementing a behavior of a management method of PaaS in the above first aspect.
- the management device of the PaaS includes at least one module for implementing the management method of the PaaS provided by the above first aspect.
- a fourth aspect there is provided another management apparatus for a PaaS, the management apparatus of the PaaS having a function of implementing the behavior of the management method of the PaaS in the second aspect.
- the management device of the PaaS includes at least one module for implementing the management method of the PaaS provided by the second aspect.
- the management device of the PaaS includes a processor and a memory, and the memory is configured to store a PaaS-enabled management device to perform the PaaS provided by the first aspect.
- the processor is configured to execute a program stored in the memory.
- the operating device of the storage device may further include a communication bus for establishing a connection between the processor and the memory.
- the management device of the PaaS includes a processor and a memory, and the memory is configured to store a PaaS-supporting management device to perform the PaaS provided by the second aspect.
- the processor is configured to execute a program stored in the memory.
- the operating device of the storage device may further include a communication bus for establishing a connection between the processor and the memory.
- a computer readable storage medium having stored therein instructions for causing a computer to execute the PaaS management method of the first aspect described above when it is run on a computer.
- another computer readable storage medium having stored therein instructions for causing a computer to execute the PaaS management method of the second aspect described above when it is run on a computer.
- a computer program product comprising instructions which, when run on a computer, cause the computer to perform the PaaS management method of the first aspect described above.
- a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of managing the PaaS described in the second aspect above.
- multiple services are deployed on the PaaS, and when the MANO entity determines that the target service tenant no longer needs to invoke the target service, it sends a service configuration request for the target service to the PaaS. Based on the service configuration request, the PaaS releases the contract binding relationship between the target service tenant and the target service, and terminates the target service when determining that there is no contract binding relationship between the other service tenant and the target service. All instances. Therefore, the services provided in this application do not have to remain online as public services, resulting in resources that cannot be released by public services for a long time, enhancing the dynamic availability of resources on the PaaS platform, and the services provided by this application do not have to be proprietary. The service is terminated as the service tenant's instance ends, which improves the reusability of the service instance between multiple service tenants, greatly improving the efficiency of the PaaS platform's resource management.
- FIG. 1 is a schematic diagram of an NFV architecture provided by an embodiment of the present application.
- FIG. 2A is a schematic diagram of an NFV architecture deployed with PaaS according to an embodiment of the present application
- 2B is a schematic structural diagram of a PaaS according to an embodiment of the present application.
- FIG. 3 is a flowchart of a method for managing a PaaS according to an embodiment of the present application
- 4A is a block diagram of a management device for a PaaS according to an embodiment of the present application.
- 4B is a block diagram of another PaaS management apparatus according to an embodiment of the present application.
- FIG. 5A is a block diagram of another PaaS management apparatus according to an embodiment of the present application.
- FIG. 5B is a block diagram of another PaaS management apparatus according to an embodiment of the present application.
- FIG. 1 is a schematic diagram of an NFV architecture provided by an embodiment of the present application.
- the NFV system architecture can be applied to various types of networks, for example, to an operator communication network or a local area network.
- the NFV architecture mainly includes a MANO entity 110, an NFVI 120, multiple VNFs 130, multiple Element Management (EM) 140, and an Operation Support System/Business Support System (Operation Support System/Business Support System). OSS/BSS) 150 and so on.
- the MANO entity 110 further includes a network function virtualization orchestrator (NFVO) 110a, one or more VNFMs 110b, and a virtualized infrastructure manager (VIM) 110c.
- NFVO network function virtualization orchestrator
- VNFMs 110b virtualized infrastructure manager
- NFVO 110a is used to implement Network Service Descriptors (NSD), and management and processing of VNF Forwarding Graph (VNFFG), management of network service life cycle, and VNFM to achieve VNF life cycle. Management and global view capabilities of virtual resources.
- NSD Network Service Descriptors
- VNFFG VNF Forwarding Graph
- VNFM VNF Management and global view capabilities of virtual resources.
- VNFM 110b is used to implement VNF lifecycle management, including management of virtualized network function descriptors (VNFD) files, instantiation of VNFs, and elastic scaling of VNF instances (including expansion of Scaling out/up and shrinking Scaling in). /down), healing of the VNF instance and the end of the VNF instance.
- VNFM also supports the elastic scaling mechanism delivered by NFVO to implement automated VNF elastic scaling.
- the VIM 110b is responsible for managing the infrastructure layer hardware resources, virtualized resources (including reservation and allocation), monitoring and fault reporting of virtual resource status, and providing virtualized resource pools for upper-layer applications.
- OSS/BSS 150 refers to the operator's existing operation and maintenance system OSS/BSS.
- the EM 140 is used to perform traditional fault, configuration, user, performance, and security management (Fault Management, Configuration Management, Account Management, Performance Management, Security Management, FCAPS) functions for the VNF 130.
- fault Management Configuration Management, Account Management, Performance Management, Security Management, FCAPS
- the VNF 130 corresponds to a Physical Network Function (PNF) in a traditional non-virtualized network, such as a virtualized 4G core network (Evolved Packet Core, EPC) EPC node, such as a Mobility Management Entity (MME). , Serving Gate Way (SGW), Packet Data Network Gateway (PGW), etc.
- PNF Physical Network Function
- EPC Evolved Packet Core
- MME Mobility Management Entity
- SGW Serving Gate Way
- PGW Packet Data Network Gateway
- VNF 130 can be composed of multiple VNF components (VNFCs). Therefore, in practical applications, one VNF 130 can be deployed on multiple virtual machines (VMs), each VM carrying a VNF component. The function. Of course, a VNF 130 can also be deployed on a VM.
- VNFCs VNF components
- NFVI 120 is composed of hardware resources and virtual resources and a virtualization layer. From the perspective of VNF 130, the virtualization layer and hardware resources appear to be a complete entity capable of providing the required virtual resources.
- the embodiment of the present application mainly implements a method for managing services on the PaaS. Therefore, the PaaS platform is also briefly introduced herein.
- PaaS is a business model that uses the server platform as a service. For example, providing a corresponding cloud computing platform or development environment in the cloud computing era as a service is a type of PaaS.
- the PaaS layer is between Software as a Service (SaaS) and Infrastructure as a Service (IaaS).
- the PaaS platform should have the following characteristics:
- Application running environment including distributed computing operating environment, multiple types of data storage, dynamic resource scaling.
- Application lifecycle support including software development kit (SDK), integrated development environment (IDE), etc. to accelerate the development, testing and deployment of applications.
- SDK software development kit
- IDE integrated development environment
- Public service Provides public services such as queue services, storage services, and cache services in the form of an Application Programming Interface (API).
- API Application Programming Interface
- Monitoring, management and metering Provide resource pool, application system management and monitoring functions, and accurately measure.
- Integrated, composite application building capabilities including connectivity services, integration services, messaging services, and process services.
- the original VNF representation based on the NFVI layer VM incorporates new features, supporting cloud-native VNF and cloud architecture that integrates PaaS platform services. Will become a new trend in the development of telecommunications clouds.
- the PaaS management method provided by the embodiment of the present application is applied to an NFV architecture deployed with PaaS.
- FIG. 2A is a schematic diagram of an NFV architecture deployed with PaaS according to an embodiment of the present application.
- the NVF architecture shown in FIG. 2A further includes a PaaS 160, which is included in the NFV architecture shown in FIG. 160 includes a plurality of services and PaaS management for managing the plurality of services.
- the VNF 130 in the NFV architecture can implement the instantiation of the VNF by calling a service in the PaaS 160.
- the NFV architecture can call the service in the PaaS, and other modules can also invoke the service in the PaaS.
- the modules that call the service in the PaaS are collectively referred to as the service tenant. That is, in the embodiment of the present application, the service tenant may be a VNF in the NFV architecture.
- the MANO entity in the PaaS and NFV architecture deployed in the NFV architecture is used to perform the PaaS management method provided by the embodiment of the present application.
- the application is implemented by the PaaS management in the PaaS and the MANO entity in the NFV architecture.
- the management method of PaaS provided by the embodiment.
- the PaaS management may also be referred to as a PaaS management entity or a PaaS management plane, and the MANO entity may specifically be a VNFM in the NFV architecture.
- FIG. 2B is a schematic structural diagram of a PaaS according to an embodiment of the present application.
- the function of PaaS in Fig. 2A can be realized by the computer device shown in Fig. 2B.
- the computer device includes at least one processor 201, a communication bus 202, a memory 203, and at least one communication interface 204.
- the processor 201 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present application. integrated circuit.
- CPU general purpose central processing unit
- ASIC application-specific integrated circuit
- Communication bus 202 can include a path for communicating information between the components described above.
- the memory 203 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
- the dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other medium accessed, but is not limited to this.
- Memory 203 may be present independently and coupled to processor 201 via communication bus 202.
- the memory 203 can also be integrated with the processor 201.
- the communication interface 204 uses a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), or Wireless Local Area Networks (WLAN). .
- a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), or Wireless Local Area Networks (WLAN).
- RAN Radio Access Network
- WLAN Wireless Local Area Networks
- processor 201 may include one or more CPUs, such as CPU0 and CPU1 shown in Figure 2B.
- a computer device can include multiple processors, such as processor 201 and processor 205 shown in FIG. 2B. Each of these processors can be a single-CPU processor or a multi-core processor.
- a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
- the computer device may further include an output device 206 and an input device 207.
- Output device 206 is in communication with processor 201 and can display information in a variety of ways.
- the output device 206 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector.
- Input device 207 is in communication with processor 201 and can receive user input in a variety of ways.
- input device 207 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
- the computer device described above may be a general purpose computer device or a special purpose computer device.
- the computer device may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, or an embedded device.
- PDA personal digital assistant
- the embodiments of the present application do not limit the type of computer equipment.
- the memory 203 is used to store program code for executing the solution of the present application, and is controlled by the processor 201 for execution.
- the processor 201 is configured to execute the program code 208 stored in the memory 203.
- One or more software modules may be included in program code 208.
- the embodiment of the present application also provides a structure of a MANO entity including at least one processor, a communication bus, a memory, and at least one communication interface.
- the functions of the processor, the communication bus, the memory, and the communication interface included in the MANO entity and the processor, the communication bus, the memory, and the communication interface in FIG. 2B are substantially the same, and will not be described in detail herein.
- FIG. 3 is a flowchart of a method for managing a PaaS according to an embodiment of the present application.
- the flowchart is applied to the NFV architecture deployed in the PaaS shown in FIG. 2A.
- FIG. 2A multiple services are deployed on the PaaS.
- the method includes the following steps:
- Step 301 The MANO entity sends a configuration request to the PaaS, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service.
- the management of the PaaS deployed in the NFV architecture mainly includes two aspects, the first aspect is the instantiation of the service deployed in the PaaS, and the second aspect is the deployment in the PaaS.
- the end of the service Steps 301 and 302 are used to expand the content of the first aspect, and steps 303 to 305 are used to expand the content of the second aspect.
- the MANO entity needs to go to the PaaS after obtaining the identity of the instance of the target service. And sending a configuration request, so that the PaaS carries the identifier of the instance of the target service tenant and the identifier of the instance of the target service according to the configuration request, and establishes a use binding relationship between the instance of the target service tenant and the instance of the target service.
- the identifier of the instance of the target service is used to uniquely identify an instance of the target service
- the identifier of the instance of the target service tenant is used to uniquely identify an instance of the target service tenant.
- the MANO entity sends the configuration request to the PaaS, in order to ensure that the instance of the target service tenant can smoothly invoke the instance of the target service, the MANO entity also needs to establish an instance between the target service tenant and the target service instance. Use binding relationships.
- the identity of the instance of the target service that the MANO entity obtains can be implemented by the following two possible implementations:
- the first possible implementation manner is: when the MANO entity determines that the target service tenant instance needs to invoke the target service, sending an instance obtaining request to the PaaS, the instance obtaining request carries the identifier of the target service; and the PaaS receiving the instance obtaining sent by the MANO entity Requesting, when the instance of the target service is currently present, sending a first response message to the MANO entity, the first response message is used to indicate that the target service has been instantiated, and the first response message carries an identifier of the instance of the target service .
- the service may have multiple instances, which may be occupied by instances of the service tenant, or some instances may not be occupied by instances of the service tenant. Therefore, when the MANO entity determines that the instance of the tenant of the target service needs to invoke the target service, the instance acquisition request for the target service may be first sent to the PaaS to determine whether there is an instance of the target service that is not occupied in the PaaS.
- the MANO entity when the MANO entity determines that the instance of the target service tenant needs to invoke the target service, the MANO entity sends an instance acquisition request for the target service to the PaaS, where the instance obtains the identifier of the target service. .
- the PaaS receives the instance acquisition request, it determines whether an instance of the target service exists currently according to the identifier of the target service, so as to send the identifier of the instance of the target service to the MANO entity according to the first possible implementation manner.
- the MANO entity when the MANO entity receives the first response message, since the MANO entity determines that the target service tenant instance needs to invoke the target service, the instance acquisition request is sent to the PaaS, so the MANO entity can be based on the first
- the identifier of the target service carried by the response message establishes a usage binding relationship between the instance of the target service tenant and the instance of the target service, so that the instance of the target service tenant can invoke the instance of the target service.
- the instance obtaining request may be a lifecycle state query request.
- the first response message carries a lifecycle state of the target service, and the lifecycle state is instantiated, and is used to indicate that the target service has an instance. And there is currently an instance of the target service.
- the MANO entity may further determine, in other manners, whether an instance of the target service exists in the PaaS, for example, determining whether an instance of the target service exists in the PaaS by using a subscription manner.
- the second possible implementation manner is: when the MANO entity determines that the target service tenant instance needs to invoke the target service, sending an instance acquisition request to the PaaS, where the instance obtains the identifier of the target service.
- the PaaS receives the instance acquisition request sent by the MANO entity, and when the instance of the target service does not exist, sends a second response message to the MANO entity, where the second response message is used to indicate that the target service is not instantiated.
- the MANO entity receives the second response message and sends a service instantiation request for the target service to the PaaS, the service instantiation request carrying the identity of the target service.
- the target service When the PaaS receives the service instantiation request sent by the MANO entity, the target service is instantiated based on the identifier of the target service, an instance of the target service is obtained, and an instantiation response message is sent to the MANO entity, and the instantiation is performed.
- the reply message carries the identity of the instance of the target service.
- the PaaS sends a second response message to the MANO entity, and the MANO entity determines that the current PaaS does not exist because the instance of the target service does not currently exist. An instance of the target service.
- the MANO entity may send a service instantiation request for the target service to the PaaS to obtain an instance of the target service.
- the second response message carries a lifecycle state of the target service, and the lifecycle state is uninstantiated, indicating that the target service is not instantiated, That is, there is currently no instance of the target service that is not occupied.
- the implementation of the target service by the PaaS may be: the PaaS obtains the descriptor file of the target service from the descriptor file of the stored service, and the descriptor file of the target service is used to describe the target. The information needed during the service instantiation process. The PaaS instantiates the target service according to the information required in the target service instantiation process in the descriptor file of the target service, and obtains an instance of the target service.
- the identifier of the target service carried in the instance obtaining request and the instantiation request is used to uniquely identify the target service.
- the identifier of the target service may be the name of the target service.
- the information required in the target service instantiation process is pre-set information, and the information required in the target service instantiation process mainly includes instance parameters, the number of instances, or the scale when the target service is initially deployed.
- the PaaS instantiates the target service that is, the PaaS completes the configuration of the target service and the allocation of resources according to the instance parameters, the number of instances, or the scale when the target service is initially deployed.
- a descriptor file corresponding to the service is stored in the PaaS, and when the service needs to be instantiated, the The service corresponding descriptor file instantiates the service.
- the PaaS is determined whether or not the instance of the target service is currently present.
- the identity of the instance of the target service is sent to the MANO entity to ensure that the instance of the target service tenant can invoke the instance of the target service.
- the identifier of the instance that the PaaS sends the target service to the MANO entity may be an identifier of an instance of the target service, or may be an identifier of multiple instances of the target service, that is, the PaaS may be assigned to the target according to the actual situation.
- the target service tenant is one or more instances of the target service, and the embodiment of the present application is not specifically limited herein.
- the MANO entity sends an instance acquisition request for the target service to the PaaS when determining that the target service tenant instance needs to invoke the target service.
- the MANO entity can determine that the target service tenant needs to invoke the target service.
- the following two scenarios may exist: that is, in the embodiment of the present application, the service in the PaaS may be instantiated in the following two scenarios:
- Scenario 1 The MANO entity creates an identifier of the instance of the target service tenant, and determines that the target service is included in the service list used by the target service tenant, and determines that the target service tenant instance needs to invoke the target service.
- any service tenant there is a descriptor file corresponding to the service tenant, and the descriptor file defines a user that the corresponding service tenant can invoke.
- the instance of the service tenant will invoke an instance of the service defined in the descriptor file during the subsequent instantiation.
- the MANO entity creates an identity of the instance of the target service tenant, it can indicate that the target service tenant needs to invoke an instance of the target service.
- the service that can be invoked by the target service tenant defined in the descriptor file is determined as the target service according to the descriptor file of the target service tenant, and An instance get request for the target service is sent to the PaaS.
- the identifier of the instance of the target service is sent to the MANO entity according to the two possible implementation manners, so that the identifier of the instance of the target service is received by the MANO entity according to step 301 to the PaaS.
- the target service tenant may be directly invoked according to the established use binding relationship.
- An instance of the target service corresponding to the instance to complete the instantiation process of the instance of the target service tenant.
- the MANO entity is a VNFM.
- the VNFM receives the instance identifier creation request of the target service tenant sent by the NFVO or the EM, the VNFM locally creates an instance identifier of the target service tenant, and describes from the target service tenant.
- the service file obtains an identifier of the target service that the target service tenant can invoke, and sends the foregoing instance acquisition request according to the identifier of the target service.
- the precondition for the MANO entity to send an instance acquisition request for the target service is that the target service has been registered in the PaaS, and the descriptor file is explicitly defined in the target service tenant's descriptor file. The service that the target service tenant can call.
- Scenario 2 When the MANO entity instantiates an instance of the target service tenant and determines that the target service is included in the service list used by the target service tenant, it is determined that the target service tenant instance needs to invoke the target service.
- the MANO entity when the MANO entity creates the identity of the instance of the target service tenant, it does not send an instance acquisition request to the PaaS to obtain an instance of the target service as in scenario one, but creates an identifier of the instance of the target service tenant. Then, in the process of instantiating the instance of the target service tenant, an instance acquisition request for the target service that the target service tenant can invoke is sent to the PaaS.
- the MANO entity creates the identity of the instance of the target service tenant
- the descriptor file of the target service tenant is determined, and the target defined in the descriptor file is determined.
- the service that the service tenant can call is determined to be the target service, and an instance acquisition request for the target service is sent to the PaaS.
- the identifier of the instance of the target service may be sent to the MANO entity according to the two possible implementation manners, so that the MANO entity receives the identifier of the instance of the target service according to step 301. Send a configuration request to the PaaS.
- the prerequisite for the MANO entity to send an instance acquisition request for the target service is that the target service has been registered in the PaaS, and the MANO entity has created the identity of the instance of the target service tenant, and the target is
- the service tenant's descriptor file clearly defines the services that the target service tenant can invoke.
- Step 302 The PaaS receives the configuration request, and establishes a binding relationship between the instance of the target service and the instance of the target service tenant based on the identifier of the instance of the target service tenant and the identifier of the instance of the target service carried by the configuration request. And when the target service tenant does not exist in the tenant list of the target service, the contract binding relationship between the target service tenant and the target service is established.
- the PaaS When the PaaS receives the configuration request, in order to ensure that the instance of the target service tenant can invoke the instance of the target service, the PaaS needs to establish a usage binding relationship between the instance of the target service and the instance of the target service tenant.
- an instance of the target service tenant is stored in both the PaaS and the MANO entity. A binding relationship between instances of the target service.
- PaaS creates the first one according to the target service tenant.
- PaaS needs to establish a contract binding relationship between the target service tenant and the target service.
- the target service tenant instantiates the target service for the second time, there is no need to establish a contract binding relationship between the target service tenant and the target service. That is, when there is a contract binding relationship between the service and the service tenant, it indicates that the service tenant can invoke the service.
- the PaaS receives the service configuration request and establishes a usage binding relationship between the instance of the target service and the instance of the target service tenant, it may be determined whether the instance of the target service is the target service tenant for the first time to the target service instance. The instance of the time, if it is, then the contract binding relationship between the target service tenant and the target service needs to be established at this time.
- the PaaS maintains a tenant list for the service, and the tenant list records the identifier of the service tenant that has called the service.
- the PaaS may determine whether the target service tenant exists in the tenant list of the target service according to the identifier of the target service tenant, if not Existence indicates that the target service tenant is the first to create an instance of the target service, and the contract binding relationship between the target service tenant and the target service is established.
- step 302 there are two different binding relationships in the embodiment of the present application, and the binding relationship and the contract binding relationship are used. To avoid confusion, the usage relationship and the contract binding relationship are performed here. explain:
- a correspondence between the service tenant and the service needs to be established; and in order to ensure that the instance of the service tenant can invoke the instance of the service, an instance between the service tenant and the instance of the service needs to be established.
- the correspondence between the service tenant and the service is called the contract binding relationship between the service tenant and the service
- the correspondence between the instance of the service tenant and the instance of the service is called an instance of the service tenant.
- a binding relationship with an instance of a service That is, a contract binding relationship is established between the service tenant and the service, and a binding relationship is established between the instance of the service tenant and the instance of the service.
- the contract binding relationship can only indicate that there is an instance of the service tenant instance calling the service, but it cannot indicate which instance of the service tenant is called.
- An instance of the service, and the use of a binding relationship can clearly indicate which instance of the service tenant invoked the instance of the service.
- the target service tenant if the target service tenant has three instances, namely A1, A2, and A3, the target service also has three instances, namely B1, B2, and B3, and the instance of the target service invoked by the current A1.
- the instance of the target service called for B1, A2 is B2, and the instance of the target service called by A3 is B3.
- there is only one contract binding relationship for the target service tenant and the target service that is, the contract binding relationship between the target service tenant and the target service.
- there are three binding relationships which are the binding relationship between A1 and B1, the usage relationship between A2 and B2, and the binding relationship between A3 and B3.
- steps 301 and 302 are used to describe the instantiation process of the service provided by the embodiment of the present application.
- the process of terminating the service provided by the embodiment of the present application is introduced in the following steps 303 to 305.
- Step 303 When the MANO entity determines that the target service tenant in the NFV architecture no longer invokes the target service, sends a service configuration request for the target service to the PaaS.
- the MANO entity in order to avoid the termination of the service due to the termination of the service tenant calling the service, when the MANO entity determines that the target service tenant no longer needs to invoke the target service, in order to terminate the target service, the MANO entity needs to The service configuration request for the target service is first sent to the PaaS, so that the PaaS decides whether the target service needs to be terminated according to the specific situation, so as to terminate the target service on demand.
- the MANO entity may determine that the target service tenant no longer needs to invoke the target service in the following two scenarios, that is, in the embodiment of the present application, the target service may be terminated in the following two scenarios. .
- Scenario 1 When the descriptor file of the target service tenant is updated, since the target service tenant's descriptor file defines the service that the target service tenant can invoke, when the target service tenant's descriptor file is updated, It may be necessary to terminate the services that the target service tenant can call.
- the MANO entity determines that the descriptor file of the target service tenant is updated, the descriptor file of the target service tenant after the update is obtained.
- the service configuration request is sent to the PaaS.
- the MANO entity needs to request the PaaS to release the target service tenant and the target. Contract binding relationship between services.
- the service configuration request carries a configuration type in order to distinguish service configuration requests in different scenarios. Therefore, in scenario 1, the configuration type carried by the service configuration request is a release contract, and the service configuration request further carries the identifier of the target service tenant and the identifier of the target service, so that the PaaS cancels the target service tenant according to the service configuration request. Contract binding relationship between target services.
- the identifier of the target service tenant is used to uniquely identify the target service tenant. Specifically, when the target service tenant is a VNF, the identifier of the target service tenant may be the name of the VNF.
- the VNFM determines that it is necessary to delete a service from the service list of the VNF according to the descriptor file after the update.
- the VNFM determines the service to be deleted as the target service, and sends the service configuration request in the scenario one to the PaaS.
- the service configuration request carries the configuration type, the identifier of the VNF, and the identifier of the service that needs to be deleted, where the configuration type is the contract cancellation.
- Scenario 2 When the MANO entity deletes the identifier of the target service tenant instance, it indicates that the target service tenant instance will no longer invoke the target service instance. Therefore, when deleting the target service tenant instance, the target may need to be terminated. service.
- the preset delay time is included in the descriptor file of the service tenant.
- the descriptor file of the target service tenant is obtained; the lag time is determined according to the descriptor file of the target service tenant, and the service configuration request is sent to the PaaS.
- the MANO entity since only the identifier of the instance of the target service tenant is to be deleted, it merely indicates that the instance of the target service tenant no longer calls the target service, but other instances of the target service tenant are not called to call the target service. Therefore, the MANO entity only needs to request the PaaS to release the binding relationship between the instance of the target service tenant and the instance of the target service.
- the configuration type carried by the service configuration request is de-use, and the service configuration request further carries an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and a lag time.
- the VNFM in the NFV architecture when the VNFM in the NFV architecture receives the instance ID deletion request sent by the NFVO or the EM for a certain VNF, the VNFM locally deletes the identifier of the instance of the VNF, and sends the identifier to the PaaS according to the service list of the VNF.
- VNF service configuration request carries a configuration type, an identifier of an instance of the VNF, an identifier of an instance of a service invoked by an instance of the VNF, and a lag time, wherein the configuration type is de-use.
- Step 304 The PaaS receives the service configuration request sent by the MANO entity for the target service, and cancels the contract binding relationship between the target service tenant and the target service based on the service configuration request.
- step 303 the MANO entity may send a service configuration request for the target service to the PaaS in two different scenarios, and accordingly, step 304 is also specifically divided into the following two cases:
- the PaaS when the PaaS receives the service configuration request of the target service, the configuration type carried by the service configuration request is a release contract, so the PaaS can identify the target service tenant carried according to the service configuration request and An identifier of the target service, searching for a contract binding relationship between the target service tenant and the target service that has been established, and releasing a contract binding relationship between the target service tenant and the target service.
- the PaaS After releasing the contract binding relationship between the target service tenant and the target service, the PaaS also needs to send a first type service configuration response message to the MANO entity, where the first type service configuration response message is used to indicate the target service and the target service.
- the contract binding relationship between tenants has been lifted.
- the MANO entity receives the first type of service configuration response message, it is determined that the PaaS has released the contract binding relationship between the target service and the target service tenant.
- the PaaS when the PaaS receives the service configuration request of the target service, the configuration type carried by the service configuration request is deactivated, so the PaaS can perform the instance of the target service tenant carried according to the service configuration request.
- the identifier of the instance of the identifier and the target service finds a usage binding relationship between the instance of the target service tenant that has been established and the instance of the target service, and releases the usage binding relationship.
- the PaaS After disabling the binding relationship between the instance of the target service tenant and the instance of the target service, the PaaS also needs to send a second type of service configuration response message to the MANO entity, and the second type of service configuration response message is used to indicate the target.
- the binding relationship between the instance of the service and the instance of the target service tenant has been removed.
- the MANO entity receives the second type of service configuration response message, it is determined that the PaaS has released the use binding relationship between the instance of the target service and the instance of the target service tenant.
- the MANO entity service configuration request further includes a lag time, after the PaaS releases the use binding relationship between the target service instance and the target service tenant instance, in order to avoid the PaaS immediately terminating the
- the target service causes the other instances of the target service tenant to continue to call the target service, and the PaaS can start timing.
- the time of the timing is the lag time, and it is determined during the lag time whether the target service tenant calls the target service again. If the target service tenant does not invoke the target service within the lag time after the current time, the PaaS may cancel the contract binding relationship between the target service tenant and the target service, and determine whether according to step 305 below. Need to end the target service.
- the PaaS does not need to release the contract binding relationship between the target service tenant and the target service, that is, the PaaS will The target service will not be terminated.
- Step 305 Terminate all instances of the target service when the PaaS determines that there is no contract binding relationship between the other service tenants in the NFV architecture and the target service.
- the instance of the service needs to be instantiated each time the service is invoked.
- the PaaS releases the contract binding relationship between the target service tenant and the target service according to step 304, the PaaS does not immediately terminate the target service, but first determines whether there are other service tenants who need to invoke the target service.
- the PaaS will not terminate the target service immediately, but will terminate the target service when the PaaS determines that there is no other service tenant that needs to invoke the target service.
- the PaaS may determine whether there is a service tenant that needs to invoke the target service by determining whether there is currently another service tenant that has a contract binding relationship with the target service, that is, when there is currently no service with the target service.
- the PaaS terminates the target service.
- PaaS will not terminate the target service.
- PaaS terminates the target service, that is, PaaS deletes all instances of the target service and releases resources occupied by all instances of the target service.
- multiple services are deployed on the PaaS, and when the MANO entity determines that the target service tenant no longer needs to invoke the target service, the service configuration request for the target service is sent to the PaaS. Based on the service configuration request, the PaaS releases the contract binding relationship between the target service tenant and the target service, and terminates the target service when determining that there is no contract binding relationship between the other service tenant and the target service. All instances. Therefore, the services provided in this application do not have to remain online as public services, resulting in resources that cannot be released by public services for a long time, enhancing the dynamic availability of resources on the PaaS platform, and the services provided by this application do not have to be proprietary. The service is terminated as the service tenant's instance ends, which improves the reusability of the service instance among multiple service tenants, greatly improving the efficiency of the PaaS platform's resource management for the service.
- an embodiment of the present application provides a PaaS management apparatus 400, which is applied to a PaaS deployed in an NFV architecture, where a plurality of services are deployed on the PaaS, and the apparatus 400 includes a first receiving module 401. , the release module 402 and the termination module 403:
- a first receiving module 401 configured to perform the step of receiving, by the PaaS in step 304 of the embodiment of FIG. 3, a service configuration request for the target service sent by the MANO entity;
- the releasing module 402 is configured to perform the step of canceling the contract binding relationship between the target service tenant and the target service based on the service configuration request in step 304 of the embodiment of FIG. 3;
- the termination module 403 is configured to perform step 305 of the embodiment of FIG. 3.
- the service configuration request carries a configuration type, an identifier of the target service tenant, and an identifier of the target service, where the configuration type is a contract cancellation.
- the apparatus 400 further includes:
- the third sending module is configured to send a first type of service configuration response message to the MANO entity, where the first type of service configuration response message is used to indicate that the contract binding relationship between the target service and the target service tenant has been released.
- the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and a lag time, and the configuration type is decommissioning;
- the releasing module 402 is specifically configured to:
- the contract binding relationship between the target service and the target service tenant is released.
- the apparatus 400 further includes:
- a fourth sending module configured to send a second type of service configuration response message to the MANO entity, where the second type of service configuration response message is used to indicate a binding relationship between the instance of the target service and the instance of the target service tenant Has been lifted.
- the apparatus 400 further includes a second receiving module 404 and an establishing module 405:
- a second receiving module 404 configured to perform the step of receiving, by the PaaS in step 302 of the embodiment of FIG. 3, the configuration request;
- the establishing module 405 is configured to perform the identifier of the instance of the target service tenant and the identifier of the target service carried in the step 302 of the embodiment of FIG. 3, and establish an instance of the target service and an instance of the target service tenant.
- the apparatus 400 further includes a third receiving module, a first sending module, and a second sending module:
- a third receiving module configured to receive an instance obtaining request sent by the MANO entity, where the instance obtains an identifier that carries the target service
- a first sending module configured to send a first response message to the MANO entity when the identifier of the target service is determined based on the identifier of the target service, where the first response message is used to indicate that the target service has been instantiated, and The first response message carries an identifier of an instance of the target service;
- a second sending module configured to send a second response message to the MANO entity when the identifier of the target service is determined to be absent based on the identifier of the target service, where the second response message is used to indicate that the target service is not instantiated and received a service instantiation request sent by the MANO entity, the service instantiation request carrying an identifier of the target service, instantiating the target service based on the identifier of the target service, obtaining an instance of the target service, and sending the target service instance to the MANO entity
- a reply message is instantiated that carries an identification of an instance of the target service.
- the second sending module is specifically configured to:
- the target service is instantiated according to the information required in the target service instantiation process in the descriptor file of the target service, and an instance of the target service is obtained.
- the MANO entity is a virtual network function manager VNFM in the NFV architecture.
- multiple services are deployed on the PaaS, and when the MANO entity determines that the target service tenant no longer needs to invoke the target service, the service configuration request for the target service is sent to the PaaS. Based on the service configuration request, the PaaS releases the contract binding relationship between the target service tenant and the target service, and terminates the target service when determining that there is no contract binding relationship between the other service tenant and the target service. All instances. Therefore, the services provided in this application do not have to remain online as public services, resulting in resources that cannot be released by public services for a long time, enhancing the dynamic availability of resources on the PaaS platform, and the services provided by this application do not have to be proprietary. The service is terminated as the service tenant's instance ends, which improves the reusability of the service instance among multiple service tenants, greatly improving the efficiency of the PaaS platform's resource management for the service.
- an embodiment of the present application provides another PaaS management apparatus 500, which is applied to a MANO entity in an NFV architecture.
- the NFV architecture is deployed with PaaS, and the apparatus 500 includes a first sending module 501:
- the first sending module 501 is configured to perform step 303 in the embodiment of FIG. 3;
- the service configuration request is used to indicate that the PaaS releases the contract binding relationship between the target service tenant and the target service based on the service configuration request, and determines that there is no contract binding relationship between the other service tenant and the target service. Terminates all instances of the target service, which is one of the multiple services.
- the first sending module 501 is specifically configured to:
- the service configuration request is sent to the PaaS, and the service configuration request carries the configuration type, The identity of the target service tenant and the identity of the target service.
- the configuration type is the contract cancellation.
- the apparatus 500 further includes a third receiving module:
- the third receiving module is configured to receive the first type of service configuration response message sent by the PaaS, where the first type of service configuration response message is used to indicate that the contract binding relationship between the target service and the target service tenant has been released.
- the first sending module 501 is specifically configured to:
- the service configuration request carrying a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and the lag time, the configuration type being decommissioning.
- the apparatus 500 further includes a fourth receiving module:
- a fourth receiving module configured to receive a second type of service configuration response message sent by the PaaS, where the second type of service configuration response message is used to indicate a binding relationship between the instance of the target service and an instance of the target service tenant Has been lifted.
- the apparatus 500 further includes a second sending module 502:
- the second sending module 502 is configured to perform step 301 in the embodiment of FIG. 3.
- the apparatus 500 further includes a third sending module, a first receiving module, and a second receiving module:
- a third sending module configured to send an instance obtaining request to the PaaS when the instance of the target service tenant needs to invoke the target service, where the instance obtaining request carries the identifier of the target service;
- a first receiving module configured to receive a first response message sent by the PaaS, where the first response message is used to indicate that the target service has been instantiated, and the first response message carries an identifier of an instance of the target service;
- a second receiving module configured to receive a second response message sent by the PaaS, where the second response message is used to indicate that the target service is not instantiated, and send a service instantiation request to the PaaS, where the service instantiation request carries the target An identifier of the service, receiving an instantiation response message sent by the PaaS, where the instantiated response message carries an identifier of an instance of the target service.
- the MANO entity is a virtual network function manager VNFM in the NFV architecture.
- multiple services are deployed on the PaaS, and when the MANO entity determines that the target service tenant no longer needs to invoke the target service, the service configuration request for the target service is sent to the PaaS. Based on the service configuration request, the PaaS releases the contract binding relationship between the target service tenant and the target service, and terminates the target service when determining that there is no contract binding relationship between the other service tenant and the target service. All instances. Therefore, the services provided in this application do not have to remain online as public services, resulting in resources that cannot be released by public services for a long time, enhancing the dynamic availability of resources on the PaaS platform, and the services provided by this application do not have to be proprietary. The service is terminated as the service tenant's instance ends, which improves the reusability of the service instance among multiple service tenants, greatly improving the efficiency of the PaaS platform's resource management for the service.
- the management device of the PaaS provided by the foregoing embodiment manages the service on the PaaS
- only the division of the foregoing functional modules is illustrated. In actual applications, the functions may be allocated differently according to requirements.
- the function module is completed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
- the management device of the PaaS provided by the foregoing embodiment is the same as the embodiment of the method for managing the PaaS in the embodiment of FIG. 3, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.
- the computer program product includes one or more computer instructions.
- the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
- the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
- the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
- the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital versatile disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)). )Wait.
- a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
- an optical medium for example, a digital versatile disc (DVD)
- DVD digital versatile disc
- SSD solid state disk
- a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
- the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- General Business, Economics & Management (AREA)
- Software Systems (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephonic Communication Services (AREA)
- Mobile Radio Communication Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The present application relates to the technical field of cloud computing and discloses a PaaS management method and device, and a storage medium. The method comprises: a MANO entity sending a service configuration request for a target service to a PaaS upon determining that a target service subscriber no longer needs to call a target service; the PaaS ending a binding contract between the target service subscriber and the target service on the basis of the service configuration request; and the PaaS ending all instances of the target service upon determining that there is no binding contract between other service subscribers and the target service. Therefore, services provided by the present application are different from exclusive services which terminate along with the end of instances of a service subscriber, thereby improving the reuse of instances of a service between a plurality of service subscribers, and greatly improving the efficiency of PaaS platform service resource management.
Description
本申请要求于2017年12月7日提交中国国家知识产权局、申请号为201711288701.X、发明名称为“PaaS的管理方法、装置及存储介质”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。This application claims the priority of the Chinese patent application submitted by the State Intellectual Property Office of China, application number 201711288701.X, and the invention name "PaaS management method, device and storage medium" on December 7, 2017. The citations are incorporated herein by reference.
本申请涉及云计算技术领域,特别涉及一种平台即服务(Platform as a Service,PaaS)的管理的方法、装置及存储介质。The present application relates to the field of cloud computing technologies, and in particular, to a method, an apparatus, and a storage medium for managing Platform as a Service (PaaS).
PaaS是指将服务器作为一种服务提供给用户,以使用户能够在互联网上实现开发、测试以及在线部署应用程序等网络功能。目前,主要是通过网络功能虚拟化(Network Function Virtualization,NFV)技术来实现PaaS,也即,将PaaS部署在NFV架构中,当该NFV架构中的虚拟网络功能(Virtualized Network Function,VNF)在实例化的过程中需要调用部署在PaaS上的服务时,通过实例化该服务以实现该服务对应的网络功能。其中,实例化是指通过NFV架构中的网络功能虚拟化基础设施(Network Function Virtualization Infrastructure,NFVI)为服务或VNF配置虚拟资源的过程。其中,调用某个服务的VNF可以称为该服务的服务租户。PaaS refers to providing the server as a service to users so that users can develop, test, and deploy applications such as applications online. At present, the implementation of PaaS is mainly through Network Function Virtualization (NFV) technology, that is, the PaaS is deployed in the NFV architecture, and the virtualized network function (VNF) in the NFV architecture is in the instance. When the service deployed on the PaaS needs to be invoked, the service is instantiated to implement the network function corresponding to the service. Among them, instantiation refers to the process of configuring virtual resources for services or VNFs through the Network Function Virtualization Infrastructure (NFVI) in the NFV architecture. Among them, the VNF that invokes a service can be called the service tenant of the service.
相关技术中,部署在PaaS上的服务分为两种,一种为公共服务,另一种为专有服务。其中,公共服务的生命周期和调用该公共服务的VNF的生命周期相互独立,也即,公共服务在实例化之后一直保持在线,当该NFV架构中的某个VNF在实例化的过程中需要调用该公共服务时,只需调用该公共服务对应的实例即可,并且该公共服务的实例并不随该VNF的实例的终结而终结。而专有服务的生命周期和调用该专有服务的VNF的生命周期密切相关,也即专有服务随着调用该专有服务的VNF的实例化而实例化,随着调用该专有服务的VNF的实例的终结而终结。In the related art, there are two types of services deployed on PaaS, one is a public service and the other is a proprietary service. The life cycle of the public service is independent of the life cycle of the VNF that invokes the public service, that is, the public service remains online after the instantiation, and a VNF in the NFV architecture needs to be invoked during the instantiation process. The public service only needs to invoke the instance corresponding to the public service, and the instance of the public service does not end with the termination of the instance of the VNF. The life cycle of a proprietary service is closely related to the life cycle of the VNF that invokes the proprietary service, that is, the proprietary service is instantiated with the instantiation of the VNF that invoked the proprietary service, with the call of the proprietary service The end of the VNF instance ends.
在上述PaaS的管理方法中,对于公共服务,无论是否存在VNF需要调用该公共服务,该公共服务的实例一直保持在线,增加了PaaS上的资源占用负担;而对于专有服务,由于该专有服务的实例将随着调用该专有服务的VNF的实例的终结而终结,因此每次调用该专有服务时,都需对该专有服务进行实例化,降低了该专有服务的应用灵活性。In the above PaaS management method, for a public service, whether or not a VNF needs to be invoked, the public service instance is kept online, which increases the resource occupation burden on the PaaS; and for the proprietary service, the proprietary service The instance of the service will be terminated with the termination of the instance of the VNF that invoked the proprietary service, so each time the proprietary service is invoked, the proprietary service needs to be instantiated, reducing the flexibility of the application of the proprietary service. Sex.
发明内容Summary of the invention
为了解决相关技术的专有服务应用灵活性低的问题,本申请提供了一种PaaS的管理方法、装置及存储介质。所述技术方案如下:In order to solve the problem of low flexibility of the proprietary service application of the related art, the present application provides a method, an apparatus, and a storage medium for managing a PaaS. The technical solution is as follows:
第一方面,提供了一种PaaS的管理方法,应用于部署在NFV架构中的PaaS,其特征在于,所述PaaS上部署有多个服务,所述方法包括:In a first aspect, a method for managing a PaaS is provided, which is applied to a PaaS deployed in an NFV architecture, where a plurality of services are deployed on the PaaS, and the method includes:
接收所述NFV架构中的管理与编排功能(Management and Orchestration,MANO) 实体发送的针对目标服务的服务配置请求,所述服务配置请求为所述MANO实体在确定所述NFV架构中的目标服务租户不再调用所述目标服务时发送的,所述目标服务为所述多个服务中的任一个;Receiving a service configuration request for a target service sent by a Management and Orchestration (MANO) entity in the NFV architecture, the service configuration request being a target service tenant in the determining the NFV architecture by the MANO entity And when the target service is no longer invoked, the target service is any one of the multiple services;
基于所述服务配置请求,解除所述目标服务租户与所述目标服务之间的合约绑定关系,所述合约绑定关系用于指示所述目标服务租户能够调用所述目标服务;Determining, by the service configuration request, a contract binding relationship between the target service tenant and the target service, where the contract binding relationship is used to indicate that the target service tenant can invoke the target service;
当确定不存在所述NFV架构中的其他服务租户与所述目标服务之间的合约绑定关系时,终结所述目标服务的所有实例。When it is determined that there is no contract binding relationship between other service tenants in the NFV architecture and the target service, all instances of the target service are terminated.
在本申请实施例中,当目标服务租户不再调用目标服务时,先解除目标服务租户与目标服务之间的合约绑定关系,并在确定不存在NFV架构中的其他服务租户与目标服务之间的合约绑定关系时,终结目标服务的所有实例,而不是在目标服务租户不再调用目标服务时,直接终结目标服务的所有实例。因此,本申请提供的服务不必像专有服务那样随着服务租户的实例的终结而终结,提高了PaaS上的服务的应用灵活性。In the embodiment of the present application, when the target service tenant no longer invokes the target service, the contract binding relationship between the target service tenant and the target service is first released, and other service tenants and target services in the NFV architecture are determined to be absent. When the contract binding relationship is terminated, all instances of the target service are terminated, instead of terminating all instances of the target service directly when the target service tenant no longer invokes the target service. Therefore, the service provided by the present application does not have to end with the end of the service tenant instance like the proprietary service, which improves the application flexibility of the service on the PaaS.
可选地,所述服务配置请求携带配置类型、所述目标服务租户的标识和所述目标服务的标识,所述配置类型为解除合约。Optionally, the service configuration request carries a configuration type, an identifier of the target service tenant, and an identifier of the target service, where the configuration type is a contract cancellation.
由于在某些场景中需要解除目标服务租户与目标服务之间的合约绑定关系,而在某些场景中需要解除目标服务租户的实例与目标服务的实例之间的使用绑定关系,因此,在本申请中,可以通过服务配置请求中携带的配置类型确定需要终结哪一种关系。Because in some scenarios, the contract binding relationship between the target service tenant and the target service needs to be dismissed, and in some scenarios, the use binding relationship between the target service tenant instance and the target service instance needs to be released. In this application, the type of configuration carried in the service configuration request can be used to determine which relationship needs to be terminated.
可选地,所述基于所述服务配置请求,解除所述目标服务租户与所述目标服务之间的合约绑定关系之后,还包括:Optionally, after the releasing the contract binding relationship between the target service tenant and the target service based on the service configuration request, the method further includes:
向所述MANO实体发送第一类服务配置应答消息,所述第一类服务配置应答消息用于指示所述目标服务与所述目标服务租户之间的合约绑定关系已经解除。Sending a first type of service configuration response message to the MANO entity, where the first type of service configuration response message is used to indicate that a contract binding relationship between the target service and the target service tenant has been released.
当PaaS解除目标服务租户与目标服务之间的合约绑定关系之后,需及时通知MANO实体该合约绑定关系已经解除。After the PaaS releases the contract binding relationship between the target service tenant and the target service, it is necessary to notify the MANO entity that the contract binding relationship has been released.
可选地,所述服务配置请求携带配置类型、所述目标服务租户的实例的标识、所述目标服务的实例的标识和迟滞时间,所述配置类型为解除使用;Optionally, the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and a lag time, where the configuration type is decommissioning;
相应地,所述基于所述服务配置请求,解除所述目标服务租户与所述目标服务之间的合约绑定关系,包括:Correspondingly, the canceling a contract binding relationship between the target service tenant and the target service based on the service configuration request includes:
基于所述配置类型、所述目标服务租户的实例的标识和所述目标服务的实例的标识,解除所述目标服务的实例与所述目标服务租户的实例之间的使用绑定关系;Deleting a use binding relationship between the instance of the target service and the instance of the target service tenant based on the configuration type, an identifier of an instance of the target service tenant, and an identifier of an instance of the target service;
当确定在当前时间之后的所述迟滞时间内所述目标服务租户没有再次调用所述目标服务时,解除所述目标服务与所述目标服务租户之间的合约绑定关系。When it is determined that the target service tenant does not invoke the target service again within the lag time after the current time, the contract binding relationship between the target service and the target service tenant is released.
具体地,当配置类型为解除使用时,表明MANO实体欲解除目标服务租户的实例与目标服务的实例之间的使用绑定关系,而PaaS在解除目标服务租户的实例与目标服务的实例之间的使用绑定关系之后,还可以通过上述方式解除目标服务租户与目标服务之间的合约绑定关系。Specifically, when the configuration type is decommissioning, it indicates that the MANO entity wants to release the use binding relationship between the target service tenant instance and the target service instance, and the PaaS is between the target service tenant instance and the target service instance. After the binding relationship is used, the contract binding relationship between the target service tenant and the target service can also be cancelled in the above manner.
可选地,所述解除所述目标服务的实例与所述目标服务租户的实例之间的使用绑定关系之后,还包括:Optionally, after the releasing the use binding relationship between the instance of the target service and the instance of the target service tenant, the method further includes:
向所述MANO实体发送第二类服务配置应答消息,所述第二类服务配置应答消息用 于指示所述目标服务的实例与所述目标服务租户的实例之间的使用绑定关系已经解除。Sending a second type of service configuration response message to the MANO entity, the second type of service configuration response message indicating that a usage binding relationship between the instance of the target service and an instance of the target service tenant has been released.
同样地,当PaaS解除目标服务租户的实例与目标服务的实例之间的使用绑定关系之后,需及时通知MANO实体该使用绑定关系已经解除。Similarly, after the PaaS releases the binding relationship between the instance of the target service tenant and the instance of the target service, the MANO entity needs to be notified in time that the binding relationship has been released.
可选地,所述接收所述NFV架构中的MANO实体发送的针对目标服务的服务配置请求之前,还包括:Optionally, before receiving the service configuration request for the target service sent by the MANO entity in the NFV architecture, the method further includes:
接收所述MANO实体发送的配置请求,所述配置请求携带所述目标服务租户的实例的标识和所述目标服务的实例的标识;Receiving a configuration request sent by the MANO entity, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service;
基于所述目标服务租户的实例的标识和所述目标服务的实例的标识,建立所述目标服务租户的实例与所述目标服务的实例之间的使用绑定关系,并在确定所述目标服务的租户列表中不存在所述目标服务租户时,建立所述目标服务租户与所述目标服务之间的合约绑定关系。Establishing a usage binding relationship between an instance of the target service tenant and an instance of the target service based on an identifier of an instance of the target service tenant and an identifier of an instance of the target service, and determining the target service Establishing a contract binding relationship between the target service tenant and the target service when the target service tenant does not exist in the tenant list.
具体地,在本申请中,PaaS可以在MANO实体发送配置请求时,建立目标服务租户的实例与目标服务的实例之间的使用绑定关系,并同时根据实际情况建立目标服务租户与目标服务之间的合约绑定关系。Specifically, in the present application, the PaaS may establish a binding relationship between the target service tenant instance and the target service instance when the MANO entity sends the configuration request, and establish the target service tenant and the target service according to actual conditions. Contract binding relationship between.
可选地,所述接收所述MANO实体发送的配置请求之前,还包括:Optionally, before receiving the configuration request sent by the MANO entity, the method further includes:
接收所述MANO实体发送的实例获取请求,所述实例获取请求携带所述目标服务的标识;Receiving an instance obtaining request sent by the MANO entity, where the instance obtaining request carries an identifier of the target service;
当基于所述目标服务的标识确定存在所述目标服务的实例时,向所述MANO实体发送第一应答消息,所述第一应答消息用于指示所述目标服务已经实例化,且所述第一应答消息携带所述目标服务的实例的标识;Sending a first response message to the MANO entity when the instance of the target service is determined to be present based on the identifier of the target service, the first response message is used to indicate that the target service has been instantiated, and the A response message carries an identifier of an instance of the target service;
当基于所述目标服务的标识确定不存在所述目标服务的实例时,向所述MANO实体发送第二应答消息,所述第二应答消息用于指示所述目标服务未实例化,接收所述MANO实体发送的服务实例化请求,所述服务实例化请求中携带所述目标服务的标识,基于所述目标服务的标识,对所述目标服务进行实例化,得到所述目标服务的实例,向所述MANO实体发送实例化应答消息,所述实例化应答消息携带所述目标服务的实例的标识。Sending a second response message to the MANO entity when the identifier of the target service is determined to be absent based on the identifier of the target service, the second response message is used to indicate that the target service is not instantiated, and receiving the a service instantiation request sent by the MANO entity, where the service instantiation request carries an identifier of the target service, and the target service is instantiated based on the identifier of the target service, and an instance of the target service is obtained. The MANO entity sends an instantiation response message, the instantiated response message carrying an identity of an instance of the target service.
具体地,MANO实体可以通过向PaaS发送实例获取请求来获取目标服务的实例的标识。其中,当PaaS确定当前不存在目标服务的实例时,还需向MANO实体反馈当前不存在目标服务的实例,以使MANO实体发送针对该目标服务的实例化请求。Specifically, the MANO entity can obtain the identity of the instance of the target service by sending an instance acquisition request to the PaaS. Wherein, when the PaaS determines that there is currently no instance of the target service, it also needs to feed back to the MANO entity an instance of the target service that does not currently exist, so that the MANO entity sends an instantiation request for the target service.
可选地,所述基于所述目标服务的标识,对所述目标服务进行实例化,得到所述目标服务的实例,包括:Optionally, the instantiating the target service based on the identifier of the target service, and obtaining an instance of the target service, including:
基于所述目标服务的标识,从存储的服务的描述符文件中获取所述目标服务的描述符文件,所述目标服务的描述符文件用于描述在所述目标服务实例化过程中所需要的信息;Obtaining a descriptor file of the target service from a descriptor file of the stored service, where the descriptor file of the target service is used to describe a required process in the target service instantiation process, based on the identifier of the target service information;
根据所述目标服务的描述符文件中所述目标服务实例化过程中所需要的信息,对所述目标服务进行实例化,得到所述目标服务的实例。And authenticating the target service according to the information required in the target service instantiation process in the descriptor file of the target service, to obtain an instance of the target service.
具体地,PaaS可以通过上述过程对目标服务进行实例化,以获取目标服务的实例。Specifically, the PaaS can instantiate the target service through the above process to obtain an instance of the target service.
可选地,所述MANO实体为所述NFV架构中的虚拟网络功能管理器(VNF Manager,VNFM)。Optionally, the MANO entity is a virtual network function manager (VNFM) in the NFV architecture.
其中,在本申请中,MANO实体可以为NFV架构中的VNFM。Among them, in the present application, the MANO entity may be a VNFM in the NFV architecture.
第二方面,提供了另一种PaaS的管理方法,应用于网络功能虚拟化NFV架构中的MANO实体,所述NFV架构中部署有PaaS,其特征在于,所述PaaS上部署有多个服务,所述方法包括:In a second aspect, another method for managing a PaaS is provided, which is applied to a MANO entity in a network function virtualization NFV architecture, where the NFV architecture is deployed with PaaS, wherein a plurality of services are deployed on the PaaS. The method includes:
当确定所述NFV架构中的目标服务租户不再调用目标服务时,向所述PaaS发送针对所述目标服务的服务配置请求;When it is determined that the target service tenant in the NFV architecture no longer invokes the target service, sending a service configuration request for the target service to the PaaS;
所述服务配置请求用于指示所述PaaS基于所述服务配置请求解除所述目标服务租户与所述目标服务之间的合约绑定关系,并在确定不存在其他服务租户与所述目标服务之间的合约绑定关系时终结所述目标服务的所有实例,所述目标服务为所述多个服务中的任一服务。The service configuration request is used to instruct the PaaS to cancel a contract binding relationship between the target service tenant and the target service based on the service configuration request, and determine that there is no other service tenant and the target service. Terminating all instances of the target service when the contract binding relationship is, the target service being any of the plurality of services.
在本申请实施例中,当目标服务租户不再调用目标服务时,MANO实体可以向PaaS发送服务配置请求,以使PaaS先解除目标服务租户与目标服务之间的合约绑定关系,并在确定不存在NFV架构中的其他服务租户与目标服务之间的合约绑定关系时,终结目标服务的所有实例,而不是在目标服务租户不再调用目标服务时,直接终结目标服务的所有实例。因此,本申请提供的服务不必像专有服务那样随着服务租户的实例的终结而终结,提高了PaaS上的服务的应用灵活性。In the embodiment of the present application, when the target service tenant no longer invokes the target service, the MANO entity may send a service configuration request to the PaaS, so that the PaaS first removes the contract binding relationship between the target service tenant and the target service, and determines When there is no contract binding relationship between other service tenants in the NFV architecture and the target service, all instances of the target service are terminated, instead of terminating all instances of the target service directly when the target service tenant no longer invokes the target service. Therefore, the service provided by the present application does not have to end with the end of the service tenant instance like the proprietary service, which improves the application flexibility of the service on the PaaS.
可选地,所述当确定所述NFV架构中的目标服务租户不再调用目标服务时,向所述PaaS发送针对所述目标服务的服务配置请求,包括:Optionally, when it is determined that the target service tenant in the NFV architecture no longer invokes the target service, sending a service configuration request for the target service to the PaaS, including:
当确定所述目标服务租户的描述符文件被更新时,获取更新之后的所述目标服务租户的描述符文件;When it is determined that the descriptor file of the target service tenant is updated, obtaining a descriptor file of the target service tenant after the update;
当根据更新之后的所述目标服务租户的描述符文件,确定需要将所述目标服务从所述目标服务租户使用的服务列表中删除时,向所述PaaS发送服务配置请求,所述服务配置请求携带配置类型、所述目标服务租户的标识和所述目标服务的标识,所述配置类型为解除合约。When it is determined that the target service needs to be deleted from the service list used by the target service tenant according to the descriptor file of the target service tenant after the update, sending a service configuration request to the PaaS, the service configuration request Carrying a configuration type, an identifier of the target service tenant, and an identifier of the target service, where the configuration type is a contract cancellation.
具体地,当目标服务租户的描述符文件被更新时,可以触发MANO实体向PaaS发送服务配置请求。Specifically, when the descriptor file of the target service tenant is updated, the MANO entity may be triggered to send a service configuration request to the PaaS.
可选地,所述向所述PaaS发送服务配置请求之后,还包括:Optionally, after the sending the service configuration request to the PaaS, the method further includes:
接收所述PaaS发送的第一类服务配置应答消息,所述第一类服务配置应答消息用于指示所述目标服务与所述目标服务租户之间的合约绑定关系已经解除。Receiving a first type of service configuration response message sent by the PaaS, where the first type of service configuration response message is used to indicate that a contract binding relationship between the target service and the target service tenant has been released.
当MANO实体接收到该第一类服务配置应答消息时,表明PaaS已经解除目标服务与目标服务租户之间的合约绑定关系。When the MANO entity receives the first type of service configuration response message, it indicates that the PaaS has released the contract binding relationship between the target service and the target service tenant.
可选地,所述当确定所述NFV架构中的目标服务租户不再调用目标服务时,向所述PaaS发送针对所述目标服务的服务配置请求,包括:Optionally, when it is determined that the target service tenant in the NFV architecture no longer invokes the target service, sending a service configuration request for the target service to the PaaS, including:
当删除所述目标服务租户的实例的标识时,获取所述目标服务租户的描述符文件;Obtaining a descriptor file of the target service tenant when deleting an identifier of an instance of the target service tenant;
根据所述目标服务租户的描述符文件,确定迟滞时间;Determining a lag time according to the descriptor file of the target service tenant;
向所述PaaS发送所述服务配置请求,所述服务配置请求携带配置类型、所述目标服务租户的实例的标识、所述目标服务的实例的标识和所述迟滞时间,所述配置类型为 解除使用。And sending, to the PaaS, the service configuration request, where the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and the lag time, where the configuration type is use.
具体地,当删除目标服务租户的实例的标识时,可以触发MANO实体向PaaS发送服务配置请求。Specifically, when the identifier of the instance of the target service tenant is deleted, the MANO entity may be triggered to send a service configuration request to the PaaS.
可选地,所述向所述PaaS发送服务配置请求之后,还包括:Optionally, after the sending the service configuration request to the PaaS, the method further includes:
接收所述PaaS发送的第二类服务配置应答消息,所述第二类服务配置应答消息用于指示所述目标服务的实例与所述目标服务租户的实例之间的使用绑定关系已经解除。Receiving a second type of service configuration response message sent by the PaaS, where the second type of service configuration response message is used to indicate that a usage binding relationship between the instance of the target service and an instance of the target service tenant has been released.
当MANO实体接收到该第二类服务配置应答消息时,表明PaaS已经解除目标服务的实例与目标服务租户的实例之间的使用绑定关系。When the MANO entity receives the second type of service configuration response message, it indicates that the PaaS has deactivated the use binding relationship between the instance of the target service and the instance of the target service tenant.
可选地,所述向所述PaaS发送针对所述目标服务的服务配置请求之前,还包括:Optionally, before the sending the service configuration request for the target service to the PaaS, the method further includes:
向所述PaaS发送配置请求,所述配置请求携带所述目标服务租户的实例的标识和所述目标服务的实例的标识,所述配置请求用于指示所述PaaS建立所述目标服务租户的实例与所述目标服务的实例之间的使用绑定关系。Sending a configuration request to the PaaS, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service, where the configuration request is used to instruct the PaaS to establish an instance of the target service tenant A binding relationship with the instance of the target service.
在本申请中,为了便于后续目标服务租户的实例能够调用目标服务的实例,MANO实体可以向PaaS发送配置请求,以使PaaS建立目标服务租户的实例与目标服务的实例之间的使用绑定关系。In the present application, in order to facilitate an instance of the target service tenant to invoke an instance of the target service, the MANO entity may send a configuration request to the PaaS to enable the PaaS to establish a binding relationship between the instance of the target service tenant and the instance of the target service. .
可选地,所述向所述PaaS发送配置请求之前,还包括:Optionally, before the sending the configuration request to the PaaS, the method further includes:
当确定所述目标服务租户的实例需要调用目标服务时,向所述PaaS发送实例获取请求,所述实例获取请求携带所述目标服务的标识;When it is determined that the instance of the target service tenant needs to invoke the target service, sending an instance obtaining request to the PaaS, where the instance obtaining request carries an identifier of the target service;
接收所述PaaS发送的第一应答消息,所述第一应答消息用于指示所述目标服务已经实例化,且所述第一应答消息携带所述目标服务的实例的标识;Receiving a first response message sent by the PaaS, where the first response message is used to indicate that the target service has been instantiated, and the first response message carries an identifier of an instance of the target service;
接收所述PaaS发送的第二应答消息,所述第二应答消息用于指示所述目标服务未实例化,向所述PaaS发送服务实例化请求,所述服务实例化请求中携带所述目标服务的标识,接收所述PaaS发送的实例化应答消息,所述实例化应答消息携带所述目标服务的实例的标识。Receiving a second response message sent by the PaaS, where the second response message is used to indicate that the target service is not instantiated, and send a service instantiation request to the PaaS, where the service instantiation request carries the target service And an identifier that is sent by the PaaS, where the instantiated response message carries an identifier of an instance of the target service.
具体地,MANO实体在发送配置请求之前,还可以通过上述两种方式获取目标服务的实例的标识。其中,当PaaS中不存在该目标服务的实例时,MANO实体还可以通过发送实例化请求的方式获取目标服务的实例的标识。Specifically, the MANO entity may obtain the identifier of the instance of the target service by using the foregoing two methods before sending the configuration request. The MANO entity may also obtain the identifier of the instance of the target service by sending an instantiation request when the instance of the target service does not exist in the PaaS.
可选地,所述MANO实体为所述NFV架构中的虚拟网络功能管理器VNFM。Optionally, the MANO entity is a virtual network function manager VNFM in the NFV architecture.
其中,在本申请中,MANO实体可以为NFV架构中的VNFM。Among them, in the present application, the MANO entity may be a VNFM in the NFV architecture.
第三方面,提供了一种PaaS的管理装置,所述PaaS的管理装置具有实现上述第一方面中PaaS的管理方法行为的功能。所述PaaS的管理装置包括至少一个模块,该至少一个模块用于实现上述第一方面所提供的PaaS的管理方法。According to a third aspect, there is provided a management apparatus for a PaaS, the management apparatus of the PaaS having a function of implementing a behavior of a management method of PaaS in the above first aspect. The management device of the PaaS includes at least one module for implementing the management method of the PaaS provided by the above first aspect.
第四方面,提供了另一种PaaS的管理装置,所述PaaS的管理装置具有实现上述第二方面中PaaS的管理方法行为的功能。所述PaaS的管理装置包括至少一个模块,该至少一个模块用于实现上述第二方面所提供的PaaS的管理方法。According to a fourth aspect, there is provided another management apparatus for a PaaS, the management apparatus of the PaaS having a function of implementing the behavior of the management method of the PaaS in the second aspect. The management device of the PaaS includes at least one module for implementing the management method of the PaaS provided by the second aspect.
第五方面,提供了另一种PaaS的管理装置,所述PaaS的管理装置的结构中包括处理器和存储器,所述存储器用于存储支持PaaS的管理装置执行上述第一方面所提供的PaaS的管理方法的程序,以及存储用于实现上述第一方面所提供的PaaS的管理方法所涉及的数据。所述处理器被配置为用于执行所述存储器中存储的程序。所述存储设备的操作装置还可以包括通信总线,该通信总线用于该处理器与存储器之间建立连接。According to a fifth aspect, there is provided another management apparatus for a PaaS, wherein the management device of the PaaS includes a processor and a memory, and the memory is configured to store a PaaS-enabled management device to perform the PaaS provided by the first aspect. A program for managing the method, and data related to the management method for implementing the PaaS provided by the first aspect described above. The processor is configured to execute a program stored in the memory. The operating device of the storage device may further include a communication bus for establishing a connection between the processor and the memory.
第六方面,提供了另一种PaaS的管理装置,所述PaaS的管理装置的结构中包括处理器和存储器,所述存储器用于存储支持PaaS的管理装置执行上述第二方面所提供的PaaS的管理方法的程序,以及存储用于实现上述第二方面所提供的PaaS的管理方法所涉及的数据。所述处理器被配置为用于执行所述存储器中存储的程序。所述存储设备的操作装置还可以包括通信总线,该通信总线用于该处理器与存储器之间建立连接。According to a sixth aspect, there is provided another management apparatus for a PaaS, wherein the management device of the PaaS includes a processor and a memory, and the memory is configured to store a PaaS-supporting management device to perform the PaaS provided by the second aspect. A program for managing the method, and data related to the management method for implementing the PaaS provided by the second aspect described above. The processor is configured to execute a program stored in the memory. The operating device of the storage device may further include a communication bus for establishing a connection between the processor and the memory.
第七方面,提供了一种计算机可读存储介质,所述计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机执行上述第一方面所述的PaaS的管理方法。According to a seventh aspect, there is provided a computer readable storage medium having stored therein instructions for causing a computer to execute the PaaS management method of the first aspect described above when it is run on a computer.
第八方面,提供了另一种计算机可读存储介质,所述计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机执行上述第二方面所述的PaaS的管理方法。According to an eighth aspect, there is provided another computer readable storage medium having stored therein instructions for causing a computer to execute the PaaS management method of the second aspect described above when it is run on a computer.
第九方面,提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述第一方面所述的PaaS的管理方法。According to a ninth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the PaaS management method of the first aspect described above.
第十方面,提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机执行上述第二方面所述的PaaS的管理方法。According to a tenth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of managing the PaaS described in the second aspect above.
上述第三方面、第五方面、第七方面和第九方面所获得的技术效果与第一方面中对应的技术手段获得的技术效果近似,在这里不再赘述。The technical effects obtained by the third aspect, the fifth aspect, the seventh aspect, and the ninth aspect are similar to those obtained by the corresponding technical means in the first aspect, and are not described herein again.
上述第四方面、第六方面、第八方面和第十方面所获得的技术效果与第二方面中对应的技术手段获得的技术效果近似,在这里不再赘述。The technical effects obtained by the fourth aspect, the sixth aspect, the eighth aspect, and the tenth aspect are similar to those obtained by the corresponding technical means in the second aspect, and are not described herein again.
本申请提供的技术方案带来的有益效果是:The beneficial effects brought by the technical solutions provided by the present application are:
在本申请中,在PaaS上部署有多个服务,当MANO实体在确定该目标服务租户不再需要调用该目标服务时,向PaaS发送针对该目标服务的服务配置请求。PaaS基于该服务配置请求,解除该目标服务租户与该目标服务之间的合约绑定关系,并在确定不存其他服务租户与该目标服务之间的合约绑定关系时,终结该目标服务的所有实例。因此,本申请中提供的服务不必像公共服务那样始终保持在线,从而导致公共服务占用的资源长时间不能释放,增强了PaaS平台上资源的动态可用性,同时本申请提供的服务也不必像专有服务那样随着服务租户的实例的终结而终结,提高了服务的实例在多个服务租户之间的可重用性,极大提升了PaaS平台对服务的资源管理的效率。In the present application, multiple services are deployed on the PaaS, and when the MANO entity determines that the target service tenant no longer needs to invoke the target service, it sends a service configuration request for the target service to the PaaS. Based on the service configuration request, the PaaS releases the contract binding relationship between the target service tenant and the target service, and terminates the target service when determining that there is no contract binding relationship between the other service tenant and the target service. All instances. Therefore, the services provided in this application do not have to remain online as public services, resulting in resources that cannot be released by public services for a long time, enhancing the dynamic availability of resources on the PaaS platform, and the services provided by this application do not have to be proprietary. The service is terminated as the service tenant's instance ends, which improves the reusability of the service instance between multiple service tenants, greatly improving the efficiency of the PaaS platform's resource management.
图1是本申请实施例提供的一种NFV架构示意图;1 is a schematic diagram of an NFV architecture provided by an embodiment of the present application;
图2A是本申请实施例提供的一种部署有PaaS的NFV架构示意图;2A is a schematic diagram of an NFV architecture deployed with PaaS according to an embodiment of the present application;
图2B是本申请实施例提供的一种PaaS的结构示意图;2B is a schematic structural diagram of a PaaS according to an embodiment of the present application;
图3是本申请实施例提供的一种PaaS的管理方法流程图;3 is a flowchart of a method for managing a PaaS according to an embodiment of the present application;
图4A是本申请实施例提供的一种PaaS的管理装置框图;4A is a block diagram of a management device for a PaaS according to an embodiment of the present application;
图4B是本申请实施例提供的另一种PaaS的管理装置框图;4B is a block diagram of another PaaS management apparatus according to an embodiment of the present application;
图5A是本申请实施例提供的另一种PaaS的管理装置框图;FIG. 5A is a block diagram of another PaaS management apparatus according to an embodiment of the present application; FIG.
图5B是本申请实施例提供的另一种PaaS的管理装置框图。FIG. 5B is a block diagram of another PaaS management apparatus according to an embodiment of the present application.
为使本申请的目的、技术方案和优点更加清楚,下面将结合附图对本申请实施方式作进一步地详细描述。In order to make the objects, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.
在对本申请实施例作进一步地详细描述之前,先对本申请实施例的应用场景进行介绍。Before the embodiments of the present application are further described in detail, the application scenarios of the embodiments of the present application are introduced.
由于本申请实施例的PaaS部署在NFV架构中,因此,在此先对NFV架构进行介绍。图1是本申请实施例提供的一种NFV架构示意图,该NFV***架构能够应用于各种类型的网络中,譬如,可以应用于运营商通信网络或局域网络中等。Since the PaaS of the embodiment of the present application is deployed in the NFV architecture, the NFV architecture is first introduced herein. FIG. 1 is a schematic diagram of an NFV architecture provided by an embodiment of the present application. The NFV system architecture can be applied to various types of networks, for example, to an operator communication network or a local area network.
如图1所示,该NFV架构主要包括有MANO实体110、NFVI 120、多个VNF 130、多个网元管理(Element Management,EM)140以及业务支持管理***(Operation Support System/Business Support System,OSS/BSS)150等。其中,该MANO实体110还包括有网络功能虚拟化编排器(NFV Orchestrator,NFVO)110a、一个或者多个VNFM110b以及虚拟化基础设施管理器(Virtualized Infrastructure Manager,VIM)110c。As shown in FIG. 1 , the NFV architecture mainly includes a MANO entity 110, an NFVI 120, multiple VNFs 130, multiple Element Management (EM) 140, and an Operation Support System/Business Support System (Operation Support System/Business Support System). OSS/BSS) 150 and so on. The MANO entity 110 further includes a network function virtualization orchestrator (NFVO) 110a, one or more VNFMs 110b, and a virtualized infrastructure manager (VIM) 110c.
为了后续便于说明,接下来对图1中NFV架构中的各个模块的功能进行介绍。For the convenience of the description, the functions of each module in the NFV architecture in FIG. 1 are introduced.
NFVO 110a用于实现网络服务描述符(Network Service Descriptors,NSD),以及虚拟网络功能转发图(VNF Forwarding Graph,VNFFG)的管理及处理、网络服务生命周期的管理、与VNFM配合实现VNF的生命周期管理和虚拟资源的全局视图功能。 NFVO 110a is used to implement Network Service Descriptors (NSD), and management and processing of VNF Forwarding Graph (VNFFG), management of network service life cycle, and VNFM to achieve VNF life cycle. Management and global view capabilities of virtual resources.
VNFM 110b用于实现VNF的生命周期管理,包括虚拟化网络功能描述符(VNF Descriptor,VNFD)文件的管理、VNF的实例化、VNF实例的弹性伸缩(包括扩容Scaling out/up和缩容Scaling in/down)、VNF实例的治愈(healing)以及VNF实例的终结。VNFM还支持接收NFVO下发的弹性伸缩(scaling)策略,实现自动化的VNF弹性伸缩。 VNFM 110b is used to implement VNF lifecycle management, including management of virtualized network function descriptors (VNFD) files, instantiation of VNFs, and elastic scaling of VNF instances (including expansion of Scaling out/up and shrinking Scaling in). /down), healing of the VNF instance and the end of the VNF instance. VNFM also supports the elastic scaling mechanism delivered by NFVO to implement automated VNF elastic scaling.
VIM 110b用于负责基础设施层硬件资源、虚拟化资源的管理(包括预留和分配)、虚拟资源状态的监控和故障上报、面向上层应用提供虚拟化资源池。The VIM 110b is responsible for managing the infrastructure layer hardware resources, virtualized resources (including reservation and allocation), monitoring and fault reporting of virtual resource status, and providing virtualized resource pools for upper-layer applications.
OSS/BSS 150是指运营商现有的运行维护***OSS/BSS。OSS/BSS 150 refers to the operator's existing operation and maintenance system OSS/BSS.
EM 140用于针对VNF 130执行传统的故障、配置、用户、性能和安全管理(Fault Management、Configuration Management、Account Management、Performance Management、Security Management,FCAPS)功能。The EM 140 is used to perform traditional fault, configuration, user, performance, and security management (Fault Management, Configuration Management, Account Management, Performance Management, Security Management, FCAPS) functions for the VNF 130.
VNF 130对应于传统非虚拟化网络中的物理网络功能(Physical Network Function,PNF),如虚拟化的4G核心网络(Evolved Packet Core,EPC)EPC节点,比如移动管理实体(Mobility Management Entity,MME)、服务网关(Serving Gate Way,SGW)、分组数据网关(Packet Data Network Gateway,PGW)等。其中,网络功能的功能性行为和状态与虚拟化与否无关,NFV技术的需求是希望VNF和PNF拥有相同的功能性行为和外部接口。The VNF 130 corresponds to a Physical Network Function (PNF) in a traditional non-virtualized network, such as a virtualized 4G core network (Evolved Packet Core, EPC) EPC node, such as a Mobility Management Entity (MME). , Serving Gate Way (SGW), Packet Data Network Gateway (PGW), etc. Among them, the functional behavior and state of network functions are not related to virtualization. The requirement of NFV technology is that VNF and PNF have the same functional behavior and external interfaces.
另外,VNF 130可以由多个VNF组件(VNF Component,VNFC)来组成,因此,实际应用中,一个VNF 130可以部署在多个虚拟机(Virtual Machine,VM)上,每个VM承载一个VNF组件的功能。当然,一个VNF 130也可以部署在一个VM上。In addition, the VNF 130 can be composed of multiple VNF components (VNFCs). Therefore, in practical applications, one VNF 130 can be deployed on multiple virtual machines (VMs), each VM carrying a VNF component. The function. Of course, a VNF 130 can also be deployed on a VM.
NFVI 120是由硬件资源和虚拟资源以及虚拟化层组成,从VNF 130的角度来说,虚拟化层和硬件资源看起来是一个能够提供所需虚拟资源的完整实体。 NFVI 120 is composed of hardware resources and virtual resources and a virtualization layer. From the perspective of VNF 130, the virtualization layer and hardware resources appear to be a complete entity capable of providing the required virtual resources.
另外,本申请实施例主要是实现对PaaS上的服务的管理方法,因此,在此对PaaS平台也进行简单介绍。In addition, the embodiment of the present application mainly implements a method for managing services on the PaaS. Therefore, the PaaS platform is also briefly introduced herein.
PaaS是将服务器平台作为一种服务的商业模式。比如,将云计算时代相应的云计算平台或者开发环境作为服务提供给用户,就是一种类型的PaaS。另外,在云计算的典型层级中,PaaS层介于软件即服务(Software as a Service,SaaS)与基础设施即服务(Infrastructure as a Service,IaaS)之间。PaaS is a business model that uses the server platform as a service. For example, providing a corresponding cloud computing platform or development environment in the cloud computing era as a service is a type of PaaS. In addition, in the typical level of cloud computing, the PaaS layer is between Software as a Service (SaaS) and Infrastructure as a Service (IaaS).
其中,PaaS平台应具备如下特点:Among them, the PaaS platform should have the following characteristics:
应用运行环境:包括分布式计算运行环境、多种类型的数据存储、动态资源伸缩功能。Application running environment: including distributed computing operating environment, multiple types of data storage, dynamic resource scaling.
应用全生命周期支持:包括提供软件开发工具包(Software Development Kit,SDK)、集成开发环境(Integrated Develop Environment,IDE)等加快应用的开发、测试和部署等。Application lifecycle support: including software development kit (SDK), integrated development environment (IDE), etc. to accelerate the development, testing and deployment of applications.
公共服务:以应用编程接口(Application Programming Interface,API)形式提供公共服务,如队列服务、存储服务和缓存服务等。Public service: Provides public services such as queue services, storage services, and cache services in the form of an Application Programming Interface (API).
监控、管理和计量:提供资源池、应用***的管理和监控功能,精确计量。Monitoring, management and metering: Provide resource pool, application system management and monitoring functions, and accurately measure.
集成、复合应用构建能力:包括连通***、整合服务、消息服务和流程服务等。Integrated, composite application building capabilities: including connectivity services, integration services, messaging services, and process services.
并且,随着NFV技术的不断发展,原有的构建在NFVI层VM基础上的VNF的呈现形态融入了新的特性,支持云原生(Cloud-native)的VNF和融合PaaS平台服务的云化架构将成为电信云发展的新趋势。本申请实施例提供的PaaS的管理方法就应用于部署有PaaS的NFV架构中。Moreover, with the continuous development of NFV technology, the original VNF representation based on the NFVI layer VM incorporates new features, supporting cloud-native VNF and cloud architecture that integrates PaaS platform services. Will become a new trend in the development of telecommunications clouds. The PaaS management method provided by the embodiment of the present application is applied to an NFV architecture deployed with PaaS.
图2A是本申请实施例提供的一种部署有PaaS的NFV架构示意图,如图2A所示,相对于图1所示的NFV架构,图2A所示的NVF架构中还包括PaaS 160,该PaaS 160中包括多个服务和用于管理该多个服务的PaaS管理。2A is a schematic diagram of an NFV architecture deployed with PaaS according to an embodiment of the present application. As shown in FIG. 2A, the NVF architecture shown in FIG. 2A further includes a PaaS 160, which is included in the NFV architecture shown in FIG. 160 includes a plurality of services and PaaS management for managing the plurality of services.
其中,NFV架构中的VNF 130可以通过调用PaaS 160中的服务的方式实现该VNF的实例化。The VNF 130 in the NFV architecture can implement the instantiation of the VNF by calling a service in the PaaS 160.
需要说明的是,NFV架构中除了VNF可以调用PaaS中的服务,其他模块也可以调用PaaS中的服务,为了后续便于说明,将调用PaaS中的服务的模块统称为服务租户。也即,在本申请实施例中,该服务租户可以为NFV架构中的VNF。It should be noted that, in addition to the VNF, the NFV architecture can call the service in the PaaS, and other modules can also invoke the service in the PaaS. For the convenience of description, the modules that call the service in the PaaS are collectively referred to as the service tenant. That is, in the embodiment of the present application, the service tenant may be a VNF in the NFV architecture.
另外,部署在NFV架构中的PaaS和NFV架构中的MANO实体用于执行本申请实施例提供的PaaS的管理方法,具体地,是由PaaS中的PaaS管理和NFV架构中的MANO实体执行本申请实施例提供的PaaS的管理方法。In addition, the MANO entity in the PaaS and NFV architecture deployed in the NFV architecture is used to perform the PaaS management method provided by the embodiment of the present application. Specifically, the application is implemented by the PaaS management in the PaaS and the MANO entity in the NFV architecture. The management method of PaaS provided by the embodiment.
其中,PaaS管理还可以被称为PaaS管理实体或者PaaS管理面,MANO实体具体可以为NFV架构中的VNFM。The PaaS management may also be referred to as a PaaS management entity or a PaaS management plane, and the MANO entity may specifically be a VNFM in the NFV architecture.
图2B是本申请实施例提供的一种PaaS的结构示意图。图2A中的PaaS的功能可以通过图2B所示的计算机设备来实现。参见图2B,该计算机设备包括至少一个处理器201,通信总线202,存储器203以及至少一个通信接口204。FIG. 2B is a schematic structural diagram of a PaaS according to an embodiment of the present application. The function of PaaS in Fig. 2A can be realized by the computer device shown in Fig. 2B. Referring to FIG. 2B, the computer device includes at least one processor 201, a communication bus 202, a memory 203, and at least one communication interface 204.
处理器201可以是一个通用中央处理器(Central Processing Unit,CPU)、微处理器、特定应用集成电路(application-specific integrated circuit,ASIC)、或一个或多个用于控制本申请方案程序执行的集成电路。The processor 201 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present application. integrated circuit.
通信总线202可包括一通路,在上述组件之间传送信息。 Communication bus 202 can include a path for communicating information between the components described above.
存储器203可以是只读存储器(read-only memory,ROM)或可存储静态信息和指令的其它类型的静态存储设备,随机存取存储器(random access memory,RAM)或者可存储信息和指令的其它类型的动态存储设备,也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory,EEPROM)、只读光盘(Compact Disc Read-Only Memory,CD-ROM)或其它光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其它磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其它介质,但不限于此。存储器203可以是独立存在,通过通信总线202与处理器201相连接。存储器203也可以和处理器201集成在一起。The memory 203 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions. The dynamic storage device can also be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other medium accessed, but is not limited to this. Memory 203 may be present independently and coupled to processor 201 via communication bus 202. The memory 203 can also be integrated with the processor 201.
通信接口204,使用任何收发器一类的装置,用于与其它设备或通信网络通信,如以太网、无线接入网(Radio Access Network,RAN)或无线局域网(Wireless Local Area Networks,WLAN)等。The communication interface 204 uses a device such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), or Wireless Local Area Networks (WLAN). .
在具体实现中,作为一种实施例,处理器201可以包括一个或多个CPU,例如图2B中所示的CPU0和CPU1。In a particular implementation, as an embodiment, processor 201 may include one or more CPUs, such as CPU0 and CPU1 shown in Figure 2B.
在具体实现中,作为一种实施例,计算机设备可以包括多个处理器,例如图2B中所示的处理器201和处理器205。这些处理器中的每一个可以是一个单核(single-CPU)处理器,也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。In a particular implementation, as an embodiment, a computer device can include multiple processors, such as processor 201 and processor 205 shown in FIG. 2B. Each of these processors can be a single-CPU processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
在具体实现中,作为一种实施例,计算机设备还可以包括输出设备206和输入设备207。输出设备206和处理器201通信,可以以多种方式来显示信息。例如,输出设备206可以是液晶显示器(liquid crystal display,LCD)、发光二级管(light emitting diode,LED)显示设备、阴极射线管(cathode ray tube,CRT)显示设备、或投影仪 (projector)等。输入设备207和处理器201通信,可以以多种方式接收用户的输入。例如,输入设备207可以是鼠标、键盘、触摸屏设备或传感设备等。In a specific implementation, as an embodiment, the computer device may further include an output device 206 and an input device 207. Output device 206 is in communication with processor 201 and can display information in a variety of ways. For example, the output device 206 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait. Input device 207 is in communication with processor 201 and can receive user input in a variety of ways. For example, input device 207 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
上述的计算机设备可以是一个通用计算机设备或者是一个专用计算机设备。在具体实现中,计算机设备可以是台式机、便携式电脑、网络服务器、掌上电脑(Personal Digital Assistant,PDA)、移动手机、平板电脑、无线终端设备、通信设备或者嵌入式设备。本申请实施例不限定计算机设备的类型。The computer device described above may be a general purpose computer device or a special purpose computer device. In a specific implementation, the computer device may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, or an embedded device. The embodiments of the present application do not limit the type of computer equipment.
其中,存储器203用于存储执行本申请方案的程序代码,并由处理器201来控制执行。处理器201用于执行存储器203中存储的程序代码208。程序代码208中可以包括一个或多个软件模块。The memory 203 is used to store program code for executing the solution of the present application, and is controlled by the processor 201 for execution. The processor 201 is configured to execute the program code 208 stored in the memory 203. One or more software modules may be included in program code 208.
本申请实施例还提供了MANO实体的结构,该MANO实体包括至少一个处理器,通信总线,存储器以及至少一个通信接口。其中,MANO实体包括的处理器、通信总线、存储器和通信接口和图2B中的处理器、通信总线、存储器和通信接口的功能基本相同,在此不再详细阐述。The embodiment of the present application also provides a structure of a MANO entity including at least one processor, a communication bus, a memory, and at least one communication interface. The functions of the processor, the communication bus, the memory, and the communication interface included in the MANO entity and the processor, the communication bus, the memory, and the communication interface in FIG. 2B are substantially the same, and will not be described in detail herein.
接下来对本申请实施例提供的PaaS的管理方法进行详细解释说明。Next, the management method of the PaaS provided by the embodiment of the present application is explained in detail.
图3是本申请实施例提供的一种PaaS的管理方法流程图,应用于图2A所示的部署有PaaS的NFV架构中,如图2A所示,该PaaS上部署有多个服务。具体地,如图3所示,该方法包括如下步骤:FIG. 3 is a flowchart of a method for managing a PaaS according to an embodiment of the present application. The flowchart is applied to the NFV architecture deployed in the PaaS shown in FIG. 2A. As shown in FIG. 2A, multiple services are deployed on the PaaS. Specifically, as shown in FIG. 3, the method includes the following steps:
步骤301:MANO实体向PaaS发送配置请求,该配置请求携带目标服务租户的实例的标识和目标服务的实例的标识。Step 301: The MANO entity sends a configuration request to the PaaS, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service.
在本申请实施例中,对部署在NFV架构中的PaaS进行管理主要包括两个方面的内容,第一方面是对部署在PaaS中的服务的实例化,第二方面是对部署在PaaS中的服务的终结。其中,步骤301和步骤302将用于对第一方面的内容展开说明,步骤303至步骤305用于对第二方面的内容展开说明。In the embodiment of the present application, the management of the PaaS deployed in the NFV architecture mainly includes two aspects, the first aspect is the instantiation of the service deployed in the PaaS, and the second aspect is the deployment in the PaaS. The end of the service. Steps 301 and 302 are used to expand the content of the first aspect, and steps 303 to 305 are used to expand the content of the second aspect.
需要说明的是,对于NFV架构中的目标服务租户,为了确保该目标服务租户的实例可以调用部署在PaaS上的目标服务的实例,MANO实体在得到该目标服务的实例的标识之后,需向PaaS发送配置请求,以使PaaS根据该配置请求携带目标服务租户的实例的标识和目标服务的实例的标识,建立目标服务租户的实例与目标服务的实例之间的使用绑定关系。It should be noted that, for the target service tenant in the NFV architecture, in order to ensure that the instance of the target service tenant can invoke the instance of the target service deployed on the PaaS, the MANO entity needs to go to the PaaS after obtaining the identity of the instance of the target service. And sending a configuration request, so that the PaaS carries the identifier of the instance of the target service tenant and the identifier of the instance of the target service according to the configuration request, and establishes a use binding relationship between the instance of the target service tenant and the instance of the target service.
其中,该目标服务的实例的标识用于唯一标识该目标服务的实例,该目标服务租户的实例的标识用于唯一标识该目标服务租户的实例。The identifier of the instance of the target service is used to uniquely identify an instance of the target service, and the identifier of the instance of the target service tenant is used to uniquely identify an instance of the target service tenant.
进一步地,在MANO实体向PaaS发送配置请求之后,为了确保该目标服务租户的实例可以顺利调用该目标服务的实例,MANO实体也需建立该目标服务租户的实例与该目标服务的实例之间的使用绑定关系。Further, after the MANO entity sends the configuration request to the PaaS, in order to ensure that the instance of the target service tenant can smoothly invoke the instance of the target service, the MANO entity also needs to establish an instance between the target service tenant and the target service instance. Use binding relationships.
另外,MANO实体得到该目标服务的实例的标识具体可以通过以下两种可能的实现方式实现:In addition, the identity of the instance of the target service that the MANO entity obtains can be implemented by the following two possible implementations:
第一种可能的实现方式:当MANO实体确定该目标服务租户的实例需要调用目标服 务时,向PaaS发送实例获取请求,该实例获取请求携带该目标服务的标识;PaaS接收MANO实体发送的实例获取请求,当当前存在该目标服务的实例时,向MANO实体发送第一应答消息,该第一应答消息用于指示该目标服务已经实例化,且该第一应答消息携带该目标服务的实例的标识。The first possible implementation manner is: when the MANO entity determines that the target service tenant instance needs to invoke the target service, sending an instance obtaining request to the PaaS, the instance obtaining request carries the identifier of the target service; and the PaaS receiving the instance obtaining sent by the MANO entity Requesting, when the instance of the target service is currently present, sending a first response message to the MANO entity, the first response message is used to indicate that the target service has been instantiated, and the first response message carries an identifier of the instance of the target service .
需要说明的是,对于部署在PaaS上的任一服务,该服务可以存在多个实例,该多个实例可能均被服务租户的实例占用,也可以存在部分实例未被服务租户的实例占用。因此,当MANO实体确定目标服务的租户的实例需要调用该目标服务时,可以先向PaaS发送针对该目标服务的实例获取请求,以确定PaaS中是否存在未被占用的该目标服务的实例。It should be noted that for any service deployed on the PaaS, the service may have multiple instances, which may be occupied by instances of the service tenant, or some instances may not be occupied by instances of the service tenant. Therefore, when the MANO entity determines that the instance of the tenant of the target service needs to invoke the target service, the instance acquisition request for the target service may be first sent to the PaaS to determine whether there is an instance of the target service that is not occupied in the PaaS.
也即,在本申请实施例中,当MANO实体确定目标服务租户的实例需要调用该目标服务时,MANO实体向PaaS发送针对该目标服务的实例获取请求,该实例获取请求携带该目标服务的标识。当PaaS接收到该实例获取请求时,根据该目标服务的标识,确定当前是否存在该目标服务的实例,以便根据第一种可能的实现方式向MANO实体发送该目标服务的实例的标识。That is, in the embodiment of the present application, when the MANO entity determines that the instance of the target service tenant needs to invoke the target service, the MANO entity sends an instance acquisition request for the target service to the PaaS, where the instance obtains the identifier of the target service. . When the PaaS receives the instance acquisition request, it determines whether an instance of the target service exists currently according to the identifier of the target service, so as to send the identifier of the instance of the target service to the MANO entity according to the first possible implementation manner.
另外,当MANO实体接收到该第一应答消息时,由于MANO实体是在确定目标服务租户的实例需要调用该目标服务时,向PaaS发送的实例获取请求,因此MANO实体此时可以根据该第一应答消息携带的该目标服务的实例的标识,建立该目标服务租户的实例与该目标服务的实例之间的使用绑定关系,以使该目标服务租户的实例可以调用该目标服务的实例。In addition, when the MANO entity receives the first response message, since the MANO entity determines that the target service tenant instance needs to invoke the target service, the instance acquisition request is sent to the PaaS, so the MANO entity can be based on the first The identifier of the target service carried by the response message establishes a usage binding relationship between the instance of the target service tenant and the instance of the target service, so that the instance of the target service tenant can invoke the instance of the target service.
具体地,该实例获取请求可以为生命周期状态查询请求,此时,该第一应答消息携带该目标服务的生命周期状态,且该生命周期状态为已实例化,用于指示该目标服务已经实例化,且当前存在该目标服务的实例。Specifically, the instance obtaining request may be a lifecycle state query request. At this time, the first response message carries a lifecycle state of the target service, and the lifecycle state is instantiated, and is used to indicate that the target service has an instance. And there is currently an instance of the target service.
可选地,MANO实体还可以通过其他的方式确定PaaS中是否存在该目标服务的实例,比如,通过订阅的方式确定PaaS中是否存在该目标服务的实例。Optionally, the MANO entity may further determine, in other manners, whether an instance of the target service exists in the PaaS, for example, determining whether an instance of the target service exists in the PaaS by using a subscription manner.
第二种可能的实现方式:当MANO实体确定该目标服务租户的实例需要调用目标服务时,向PaaS发送实例获取请求,该实例获取请求携带该目标服务的标识。PaaS接收该MANO实体发送的实例获取请求,当当前不存在该目标服务的实例时,向MANO实体发送第二应答消息,该第二应答消息用于指示该目标服务未实例化。MANO实体接收该第二应答消息,并向PaaS发送针对该目标服务的服务实例化请求,该服务实例化请求携带该目标服务的标识。当PaaS接收到该MANO实体发送的服务实例化请求时,基于该目标服务的标识,对该目标服务进行实例化,得到该目标服务的实例,并向MANO实体发送实例化应答消息,该实例化应答消息携带该目标服务的实例的标识。The second possible implementation manner is: when the MANO entity determines that the target service tenant instance needs to invoke the target service, sending an instance acquisition request to the PaaS, where the instance obtains the identifier of the target service. The PaaS receives the instance acquisition request sent by the MANO entity, and when the instance of the target service does not exist, sends a second response message to the MANO entity, where the second response message is used to indicate that the target service is not instantiated. The MANO entity receives the second response message and sends a service instantiation request for the target service to the PaaS, the service instantiation request carrying the identity of the target service. When the PaaS receives the service instantiation request sent by the MANO entity, the target service is instantiated based on the identifier of the target service, an instance of the target service is obtained, and an instantiation response message is sent to the MANO entity, and the instantiation is performed. The reply message carries the identity of the instance of the target service.
在第二种可能的实现方式中,由于当前不存在该目标服务的实例,因此,PaaS向MANO实体发送第二应答消息,当MANO实体接收到该第二应答消息时,确定当前PaaS中不存在该目标服务的实例。此时,为了使目标服务租户的实例可以调用该目标服务,MANO实体可以向PaaS发送针对该目标服务的服务实例化请求,以得到该目标服务的实例。In a second possible implementation manner, the PaaS sends a second response message to the MANO entity, and the MANO entity determines that the current PaaS does not exist because the instance of the target service does not currently exist. An instance of the target service. At this time, in order for the instance of the target service tenant to invoke the target service, the MANO entity may send a service instantiation request for the target service to the PaaS to obtain an instance of the target service.
比如,当该实例获取请求为生命周期状态查询请求时,该第二应答消息携带该目标 服务的生命周期状态,且该生命周期状态为未实例化,用于指示该目标服务未实例化,也即当前不存在未被占用的该目标服务的实例。For example, when the instance obtains a request for a lifecycle state query request, the second response message carries a lifecycle state of the target service, and the lifecycle state is uninstantiated, indicating that the target service is not instantiated, That is, there is currently no instance of the target service that is not occupied.
具体地,,PaaS对该目标服务进行实例化的实现方式可以为:PaaS从存储的服务的描述符文件中获取该目标服务的描述符文件,该目标服务的描述符文件用于描述在该目标服务实例化过程中所需要的信息。PaaS根据该目标服务的描述符文件中该目标服务实例化过程中所需要的信息,对该目标服务进行实例化,得到该目标服务的实例。Specifically, the implementation of the target service by the PaaS may be: the PaaS obtains the descriptor file of the target service from the descriptor file of the stored service, and the descriptor file of the target service is used to describe the target. The information needed during the service instantiation process. The PaaS instantiates the target service according to the information required in the target service instantiation process in the descriptor file of the target service, and obtains an instance of the target service.
其中,实例获取请求和实例化请求中携带的目标服务的标识用于唯一标识该目标服务,具体地,该目标服务的标识可以为该目标服务的名称。The identifier of the target service carried in the instance obtaining request and the instantiation request is used to uniquely identify the target service. Specifically, the identifier of the target service may be the name of the target service.
另外,该目标服务实例化过程中所需要的信息为预先设置的信息,该目标服务实例化过程中所需要的信息主要包括初始部署该目标服务时的实例参数、实例数量或规模。PaaS对该目标服务进行实例化,也即PaaS根据初始部署该目标服务时的实例参数、实例数量或规模,完成该目标服务的实例的配置和资源的分配。In addition, the information required in the target service instantiation process is pre-set information, and the information required in the target service instantiation process mainly includes instance parameters, the number of instances, or the scale when the target service is initially deployed. The PaaS instantiates the target service, that is, the PaaS completes the configuration of the target service and the allocation of resources according to the instance parameters, the number of instances, or the scale when the target service is initially deployed.
也即,在本申请实施例中,对于部署在PaaS上的任一服务,在该PaaS中均存储有与该服务对应的描述符文件,当需要对该服务进行实例化时,可以根据与该服务对应的描述符文件对该服务进行实例化。That is, in the embodiment of the present application, for any service deployed on the PaaS, a descriptor file corresponding to the service is stored in the PaaS, and when the service needs to be instantiated, the The service corresponding descriptor file instantiates the service.
由上述第一种可能的实现方式和第二种可能的实现方式可知,MANO实体在向PaaS发送针对目标服务的实例获取请求之后,无论当前是否存在该目标服务的实例,PaaS均是在确定出该目标服务的实例之后,再向MANO实体发送该目标服务的实例的标识,以确保该目标服务租户的实例可以调用该目标服务的实例。According to the first possible implementation manner and the second possible implementation manner, after the MANO entity sends an instance acquisition request for the target service to the PaaS, the PaaS is determined whether or not the instance of the target service is currently present. After the instance of the target service, the identity of the instance of the target service is sent to the MANO entity to ensure that the instance of the target service tenant can invoke the instance of the target service.
需要说明的是,PaaS向MANO实体发送该目标服务的实例的标识可以为目标服务的一个实例的标识,也可以为目标服务的多个实例的标识,也即,PaaS可以根据实际情况分配给该目标服务租户该目标服务的一个实例或多个实例,本申请实施例在此不做具体限定。It should be noted that the identifier of the instance that the PaaS sends the target service to the MANO entity may be an identifier of an instance of the target service, or may be an identifier of multiple instances of the target service, that is, the PaaS may be assigned to the target according to the actual situation. The target service tenant is one or more instances of the target service, and the embodiment of the present application is not specifically limited herein.
另外,由上述第一种可能的实现方式和第二种可能的实现方式可知,MANO实体均是在确定目标服务租户的实例需要调用目标服务时,向PaaS发送针对该目标服务的实例获取请求。In addition, it can be seen from the foregoing first possible implementation manner and the second possible implementation manner that the MANO entity sends an instance acquisition request for the target service to the PaaS when determining that the target service tenant instance needs to invoke the target service.
其中,MANO实体确定目标服务租户的实例需要调用目标服务可能存在以下两种场景,也即,在本申请实施例中,可以在以下两种场景中对PaaS中的服务进行实例化:The MANO entity can determine that the target service tenant needs to invoke the target service. The following two scenarios may exist: that is, in the embodiment of the present application, the service in the PaaS may be instantiated in the following two scenarios:
场景一,MANO实体创建该目标服务租户的实例的标识,且确定该目标服务租户使用的服务列表中包括目标服务时,确定该目标服务租户的实例需要调用目标服务。Scenario 1: The MANO entity creates an identifier of the instance of the target service tenant, and determines that the target service is included in the service list used by the target service tenant, and determines that the target service tenant instance needs to invoke the target service.
需要说明的是,对于任一个服务租户,都存在与该服务租户对应的描述符文件,该描述符文件中将定义对应的服务租户可以调用的用户。另外,MANO实体在创建一个服务租户的实例的标识之后,该服务租户的实例将在之后实例化的过程中调用描述符文件中定义的服务的实例。It should be noted that, for any service tenant, there is a descriptor file corresponding to the service tenant, and the descriptor file defines a user that the corresponding service tenant can invoke. In addition, after the MANO entity creates the identity of an instance of the service tenant, the instance of the service tenant will invoke an instance of the service defined in the descriptor file during the subsequent instantiation.
因此,当MANO实体在创建该目标服务租户的实例的标识时,可以表明该目标服务租户需要调用该目标服务的实例。Therefore, when the MANO entity creates an identity of the instance of the target service tenant, it can indicate that the target service tenant needs to invoke an instance of the target service.
也即,当MANO实体在创建该目标服务租户的实例的标识时,根据该目标服务租户的描述符文件,将该描述符文件中定义的该目标服务租户可以调用的服务确定为目标服 务,并向PaaS发送针对该目标服务的实例获取请求。That is, when the MANO entity creates an identifier of the instance of the target service tenant, the service that can be invoked by the target service tenant defined in the descriptor file is determined as the target service according to the descriptor file of the target service tenant, and An instance get request for the target service is sent to the PaaS.
当PaaS接收到该实例获取请求时,根据上述两种可能的实现方式向MANO实体发送针对该目标服务的实例的标识,以便于MANO实体在接收到该目标服务的实例的标识根据步骤301向PaaS发送配置请求。When the PaaS receives the instance acquisition request, the identifier of the instance of the target service is sent to the MANO entity according to the two possible implementation manners, so that the identifier of the instance of the target service is received by the MANO entity according to step 301 to the PaaS. Send a configuration request.
在场景一中,MANO实体在完成对目标服务租户的实例的标识的创建之后,当该目标服务租户的实例需要实例化时,可以根据建立的使用绑定关系,直接调用与该目标服务租户的实例对应的目标服务的实例,以完成该目标服务租户的实例的实例化过程。In scenario 1, after the MANO entity completes the creation of the identifier of the target service tenant instance, when the instance of the target service tenant needs to be instantiated, the target service tenant may be directly invoked according to the established use binding relationship. An instance of the target service corresponding to the instance to complete the instantiation process of the instance of the target service tenant.
具体地,该MANO实体为VNFM,当该VNFM接收到NFVO或EM发送的目标服务租户的实例标识创建请求时,VNFM在本地创建一个该目标服务租户的实例标识,并从该目标服务租户的描述服务文件中获取该目标服务租户可以调用的目标服务的标识,并根据该目标服务的标识发送上述实例获取请求。Specifically, the MANO entity is a VNFM. When the VNFM receives the instance identifier creation request of the target service tenant sent by the NFVO or the EM, the VNFM locally creates an instance identifier of the target service tenant, and describes from the target service tenant. The service file obtains an identifier of the target service that the target service tenant can invoke, and sends the foregoing instance acquisition request according to the identifier of the target service.
需要说明的是,在场景一中,MANO实体发送针对该目标服务的实例获取请求的前提条件为:该目标服务已经在PaaS中注册,且在该目标服务租户的描述符文件中明确定义了该目标服务租户可以调用的服务。It should be noted that, in scenario 1, the precondition for the MANO entity to send an instance acquisition request for the target service is that the target service has been registered in the PaaS, and the descriptor file is explicitly defined in the target service tenant's descriptor file. The service that the target service tenant can call.
场景二,当该MANO实体对该目标服务租户的实例进行实例化,且确定该目标服务租户使用的服务列表中包括目标服务时,确定该目标服务租户的实例需要调用目标服务。Scenario 2: When the MANO entity instantiates an instance of the target service tenant and determines that the target service is included in the service list used by the target service tenant, it is determined that the target service tenant instance needs to invoke the target service.
在场景二中,MANO实体在创建该目标服务租户的实例的标识时,并没有像场景一那样向PaaS发送实例获取请求以得到目标服务的实例,而是在创建该目标服务租户的实例的标识之后,在该目标服务租户的实例进行实例化的过程中,向PaaS发送针对该目标服务租户可以调用的目标服务的实例获取请求。In scenario 2, when the MANO entity creates the identity of the instance of the target service tenant, it does not send an instance acquisition request to the PaaS to obtain an instance of the target service as in scenario one, but creates an identifier of the instance of the target service tenant. Then, in the process of instantiating the instance of the target service tenant, an instance acquisition request for the target service that the target service tenant can invoke is sent to the PaaS.
也即,MANO实体在创建该目标服务租户的实例的标识之后,当该目标服务租户的实例当前需要实例化时,确定该目标服务租户的描述符文件,将该描述符文件中定义的该目标服务租户可以调用的服务确定为目标服务,并向PaaS发送针对该目标服务的实例获取请求。That is, after the MANO entity creates the identity of the instance of the target service tenant, when the instance of the target service tenant currently needs to be instantiated, the descriptor file of the target service tenant is determined, and the target defined in the descriptor file is determined. The service that the service tenant can call is determined to be the target service, and an instance acquisition request for the target service is sent to the PaaS.
当PaaS接收到该实例获取请求时,同样可以根据上述两种可能的实现方式向MANO实体发送针对该目标服务的实例的标识,以便于MANO实体在接收到该目标服务的实例的标识根据步骤301向PaaS发送配置请求。When the PaaS receives the instance acquisition request, the identifier of the instance of the target service may be sent to the MANO entity according to the two possible implementation manners, so that the MANO entity receives the identifier of the instance of the target service according to step 301. Send a configuration request to the PaaS.
显然,在场景二中,MANO实体发送针对该目标服务的实例获取请求的前提条件为:该目标服务已经在PaaS中注册,MANO实体已经创建了该目标服务租户的实例的标识,且在该目标服务租户的描述符文件中明确定义了该目标服务租户可以调用的服务。Obviously, in scenario 2, the prerequisite for the MANO entity to send an instance acquisition request for the target service is that the target service has been registered in the PaaS, and the MANO entity has created the identity of the instance of the target service tenant, and the target is The service tenant's descriptor file clearly defines the services that the target service tenant can invoke.
步骤302:PaaS接收该配置请求,基于该配置请求携带的目标服务租户的实例的标识和目标服务的实例的标识,建立该目标服务的实例与目标服务租户的实例之间的使用绑定关系,并在确定目标服务的租户列表中不存在该目标服务租户时,建立该目标服务租户与该目标服务之间的合约绑定关系。Step 302: The PaaS receives the configuration request, and establishes a binding relationship between the instance of the target service and the instance of the target service tenant based on the identifier of the instance of the target service tenant and the identifier of the instance of the target service carried by the configuration request. And when the target service tenant does not exist in the tenant list of the target service, the contract binding relationship between the target service tenant and the target service is established.
当PaaS接收到该配置请求时,为了确保目标服务租户的实例可以调用该目标服务的实例,PaaS需建立该目标服务的实例与目标服务租户的实例之间的使用绑定关系。When the PaaS receives the configuration request, in order to ensure that the instance of the target service tenant can invoke the instance of the target service, the PaaS needs to establish a usage binding relationship between the instance of the target service and the instance of the target service tenant.
也即,在PaaS向MANO实体发送该目标服务的实例的标识之后,为了确保该目标服务租户的实例可以调用该目标服务的实例,PaaS和MANO实体中均存储有该目标服务租 户的实例与该目标服务的实例之间的使用绑定关系。That is, after the PaaS sends the identifier of the instance of the target service to the MANO entity, in order to ensure that the instance of the target service tenant can invoke the instance of the target service, an instance of the target service tenant is stored in both the PaaS and the MANO entity. A binding relationship between instances of the target service.
值得注意的是,由于不同的服务租户可以调用同一个服务,因此,在本发明实例中,当目标服务租户首次对该目标服务进行实例化时,也即,PaaS根据该目标服务租户创建首个目标服务的实例时,PaaS需建立该目标服务租户与该目标服务之间的合约绑定关系。之后,该当目标服务租户第二次对该目标服务进行实例化时,无需再建立该目标服务租户与该目标服务之后的合约绑定关系。也即,当服务与服务租户之间存在合约绑定关系时,表明该服务租户可以调用该服务。It is worth noting that, since different service tenants can invoke the same service, in the example of the present invention, when the target service tenant first instantiates the target service, that is, PaaS creates the first one according to the target service tenant. When an instance of the target service is used, PaaS needs to establish a contract binding relationship between the target service tenant and the target service. Then, when the target service tenant instantiates the target service for the second time, there is no need to establish a contract binding relationship between the target service tenant and the target service. That is, when there is a contract binding relationship between the service and the service tenant, it indicates that the service tenant can invoke the service.
因此,当PaaS接收到服务配置请求,并建立该目标服务的实例与目标服务租户的实例之间的使用绑定关系时,可以确定该目标服务的实例是否是该目标服务租户首次对目标服务实例化时的实例,如果是,那么此时还需建立该目标服务租户与目标服务之间的合约绑定关系。Therefore, when the PaaS receives the service configuration request and establishes a usage binding relationship between the instance of the target service and the instance of the target service tenant, it may be determined whether the instance of the target service is the target service tenant for the first time to the target service instance. The instance of the time, if it is, then the contract binding relationship between the target service tenant and the target service needs to be established at this time.
需要说明的是,对于部署在PaaS上的任一服务,PaaS为该服务维持一个租户列表,该租户列表中记录有已经调用过该服务的服务租户的标识。It should be noted that for any service deployed on the PaaS, the PaaS maintains a tenant list for the service, and the tenant list records the identifier of the service tenant that has called the service.
因此,PaaS在建立该目标服务的实例与目标服务租户的实例之间的使用绑定关系时,还可以根据目标服务租户的标识,确定目标服务的租户列表中是否存在该目标服务租户,如果不存在,表明当前是目标服务租户首次创建该目标服务的实例,则建立该目标服务租户与目标服务之间的合约绑定关系。Therefore, when establishing a binding relationship between the instance of the target service and the instance of the target service tenant, the PaaS may determine whether the target service tenant exists in the tenant list of the target service according to the identifier of the target service tenant, if not Existence indicates that the target service tenant is the first to create an instance of the target service, and the contract binding relationship between the target service tenant and the target service is established.
另外需要说明的是,由步骤302可知,本申请实施例中存在两种不同的绑定关系,使用绑定关系和合约绑定关系,为了避免混淆,在此对使用关系和合约绑定关系进行解释说明:It should be noted that, as shown in step 302, there are two different binding relationships in the embodiment of the present application, and the binding relationship and the contract binding relationship are used. To avoid confusion, the usage relationship and the contract binding relationship are performed here. explain:
对于PaaS而言,为了确保服务租户可以调用服务,需建立服务租户与服务之间的对应关系;而为了确保服务租户的实例可以调用服务的实例,需建立服务租户的实例与服务的实例之间的对应关系。因此,为了便于说明,将服务租户与服务之间的对应关系称为服务租户与服务之间的合约绑定关系,将服务租户的实例与服务的实例之间的对应关系称为服务租户的实例与服务的实例之间的使用绑定关系。也即,服务租户与服务之间建立的是合约绑定关系,服务租户的实例与服务的实例之间建立的是使用绑定关系。For PaaS, in order to ensure that the service tenant can invoke the service, a correspondence between the service tenant and the service needs to be established; and in order to ensure that the instance of the service tenant can invoke the instance of the service, an instance between the service tenant and the instance of the service needs to be established. Correspondence. Therefore, for convenience of explanation, the correspondence between the service tenant and the service is called the contract binding relationship between the service tenant and the service, and the correspondence between the instance of the service tenant and the instance of the service is called an instance of the service tenant. A binding relationship with an instance of a service. That is, a contract binding relationship is established between the service tenant and the service, and a binding relationship is established between the instance of the service tenant and the instance of the service.
由于一个服务租户通常有多个实例,且一个服务也通常有多个实例,因此,合约绑定关系只能表明存在服务租户的实例调用服务的实例,但是不能表明具体是服务租户的哪个实例调用了服务的实例,而使用绑定关系可以明确表明是服务租户的哪个实例调用了服务的实例。Since a service tenant usually has multiple instances, and a service usually has multiple instances, the contract binding relationship can only indicate that there is an instance of the service tenant instance calling the service, but it cannot indicate which instance of the service tenant is called. An instance of the service, and the use of a binding relationship can clearly indicate which instance of the service tenant invoked the instance of the service.
比如,对于目标服务租户和目标服务,假如目标服务租户有三个实例,分别为A1、A2和A3,目标服务也有三个实例,分别为B1、B2和B3,且当前A1调用的目标服务的实例为B1,A2调用的目标服务的实例为B2,A3调用的目标服务的实例为B3。此时,在PaaS中,对于目标服务租户和目标服务,只存在一个合约绑定关系,即目标服务租户与目标服务之间的合约绑定关系。但是存在三个使用绑定关系,分别为A1与B1之间的使用绑定关系、A2与B2之间的使用关系、A3与B3之间的使用绑定关系。For example, for the target service tenant and the target service, if the target service tenant has three instances, namely A1, A2, and A3, the target service also has three instances, namely B1, B2, and B3, and the instance of the target service invoked by the current A1. The instance of the target service called for B1, A2 is B2, and the instance of the target service called by A3 is B3. At this time, in PaaS, there is only one contract binding relationship for the target service tenant and the target service, that is, the contract binding relationship between the target service tenant and the target service. However, there are three binding relationships, which are the binding relationship between A1 and B1, the usage relationship between A2 and B2, and the binding relationship between A3 and B3.
上述步骤301和步骤302用于对本申请实施例提供的服务的实例化过程进行介绍,下面将通过步骤303至步骤305对本申请实施例提供的服务的终结过程进行介绍。The foregoing steps 301 and 302 are used to describe the instantiation process of the service provided by the embodiment of the present application. The process of terminating the service provided by the embodiment of the present application is introduced in the following steps 303 to 305.
步骤303:当MANO实体确定NFV架构中的目标服务租户不再调用该目标服务时,向PaaS发送针对该目标服务的服务配置请求。Step 303: When the MANO entity determines that the target service tenant in the NFV architecture no longer invokes the target service, sends a service configuration request for the target service to the PaaS.
在本申请实施例中,为了避免因调用该服务的服务租户的终结而导致服务的终结,当MANO实体确定该目标服务租户不再需要调用该目标服务时,为了终结该目标服务,MANO实体需先向PaaS发送针对该目标服务的服务配置请求,以便由PaaS根据具体情况决定是否需要终结该目标服务,以实现按需终结该目标服务。In the embodiment of the present application, in order to avoid the termination of the service due to the termination of the service tenant calling the service, when the MANO entity determines that the target service tenant no longer needs to invoke the target service, in order to terminate the target service, the MANO entity needs to The service configuration request for the target service is first sent to the PaaS, so that the PaaS decides whether the target service needs to be terminated according to the specific situation, so as to terminate the target service on demand.
需要说明的是,MANO实体可能在以下两种场景中确定该目标服务租户不再需要调用该目标服务,也即,在本申请实施例中,可能在以下两种场景中需要对目标服务进行终结。It should be noted that the MANO entity may determine that the target service tenant no longer needs to invoke the target service in the following two scenarios, that is, in the embodiment of the present application, the target service may be terminated in the following two scenarios. .
场景一:当该目标服务租户的描述符文件被更新时,由于目标服务租户的描述符文件中定义了该目标服务租户可以调用的服务,因此,在该目标服务租户的描述符文件被更新时,可能需要终结该目标服务租户可以调用的服务。Scenario 1: When the descriptor file of the target service tenant is updated, since the target service tenant's descriptor file defines the service that the target service tenant can invoke, when the target service tenant's descriptor file is updated, It may be necessary to terminate the services that the target service tenant can call.
具体地,当MANO实体确定目标服务租户的描述符文件被更新时,获取更新之后的该目标服务租户的描述符文件。当MANO实体根据更新之后的目标服务租户的描述符文件,确定需要将该目标服务从目标服务租户使用的服务列表中删除时,向该PaaS发送服务配置请求。Specifically, when the MANO entity determines that the descriptor file of the target service tenant is updated, the descriptor file of the target service tenant after the update is obtained. When the MANO entity determines that the target service needs to be deleted from the service list used by the target service tenant according to the updated descriptor file of the target service tenant, the service configuration request is sent to the PaaS.
此时,由于需要将该目标服务从目标服务租户使用的服务列表中删除,也即,该目标服务租户将不会再次调用该目标服务,因此MANO实体需要请求PaaS解除该目标服务租户与该目标服务之间的合约绑定关系。At this time, since the target service needs to be deleted from the service list used by the target service tenant, that is, the target service tenant will not invoke the target service again, the MANO entity needs to request the PaaS to release the target service tenant and the target. Contract binding relationship between services.
实际应用中,为了区分不同场景下的服务配置请求,服务配置请求中携带有配置类型。因此,在场景一中,该服务配置请求携带的配置类型为解除合约,且服务配置请求还携带目标服务租户的标识和目标服务的标识,以便PaaS根据该服务配置请求解除该目标服务租户与该目标服务之间的合约绑定关系。In the actual application, the service configuration request carries a configuration type in order to distinguish service configuration requests in different scenarios. Therefore, in scenario 1, the configuration type carried by the service configuration request is a release contract, and the service configuration request further carries the identifier of the target service tenant and the identifier of the target service, so that the PaaS cancels the target service tenant according to the service configuration request. Contract binding relationship between target services.
其中,目标服务租户的标识用于唯一标识该目标服务租户,具体地,当该目标服务租户为VNF时,该目标服务租户的标识可以为该VNF的名称。The identifier of the target service tenant is used to uniquely identify the target service tenant. Specifically, when the target service tenant is a VNF, the identifier of the target service tenant may be the name of the VNF.
比如,当VNF厂商更新了VNF的描述符文件时,VNFM在获取该更新之后的描述符文件之后,若根据该更新之后的描述符文件确定需要将某个服务从该VNF的服务列表中删除时,VNFM将需要删除的服务确定为目标服务,并向PaaS发送场景一中的服务配置请求。该服务配置请求携带配置类型、该VNF的标识、需要删除的服务的标识,其中,配置类型为解除合约。For example, when the VNF vendor updates the descriptor file of the VNF, after obtaining the descriptor file after the update, the VNFM determines that it is necessary to delete a service from the service list of the VNF according to the descriptor file after the update. The VNFM determines the service to be deleted as the target service, and sends the service configuration request in the scenario one to the PaaS. The service configuration request carries the configuration type, the identifier of the VNF, and the identifier of the service that needs to be deleted, where the configuration type is the contract cancellation.
场景二:当MANO实体删除该目标服务租户的实例的标识时,表明该目标服务租户的实例将不再调用的目标服务的实例,因此当删除该目标服务租户的实例时,可能需要终结该目标服务。Scenario 2: When the MANO entity deletes the identifier of the target service tenant instance, it indicates that the target service tenant instance will no longer invoke the target service instance. Therefore, when deleting the target service tenant instance, the target may need to be terminated. service.
需要说明的是,在场景二中,由于仅仅是要删除该目标服务租户的实例的标识,只是表明该目标服务租户的这个实例不再调用目标服务,但是并不能代表该目标服务租户的其他实例不再调用该目标服务。因此,为了避免PaaS立即终结该目标服务导致该目标服务租户的其他实例不能继续调用该目标服务,对于该目标服务租户,还设置有迟滞时间,该迟滞时间为PaaS延迟解除该目标服务租户与目标服务之间的合约绑定关系的 时间。It should be noted that, in scenario 2, since only the identifier of the instance of the target service tenant is deleted, it merely indicates that the instance of the target service tenant no longer calls the target service, but does not represent other instances of the target service tenant. The target service is no longer called. Therefore, in order to prevent the PaaS from immediately terminating the target service, other instances of the target service tenant cannot continue to invoke the target service, and the target service tenant is further provided with a lag time, which is a PaaS delay to release the target service tenant and target. The time of the contract binding relationship between services.
其中,对于任一个服务租户,在该服务租户的描述符文件中均包括预先设置的迟滞时间。Wherein, for any service tenant, the preset delay time is included in the descriptor file of the service tenant.
因此,当MANO实体需删除该目标服务租户的实例的标识时,获取该目标服务租户的描述符文件;根据该目标服务租户的描述符文件,确定迟滞时间,并向PaaS发送服务配置请求。Therefore, when the MANO entity needs to delete the identifier of the instance of the target service tenant, the descriptor file of the target service tenant is obtained; the lag time is determined according to the descriptor file of the target service tenant, and the service configuration request is sent to the PaaS.
此时,由于仅仅是要删除该目标服务租户的实例的标识,只是表明该目标服务租户的这个实例不再调用目标服务,但是并不能代表该目标服务租户的其他实例不再调用该目标服务。因此,MANO实体只需要请求PaaS解除该目标服务租户的实例与该目标服务的实例之间的使用绑定关系。At this time, since only the identifier of the instance of the target service tenant is to be deleted, it merely indicates that the instance of the target service tenant no longer calls the target service, but other instances of the target service tenant are not called to call the target service. Therefore, the MANO entity only needs to request the PaaS to release the binding relationship between the instance of the target service tenant and the instance of the target service.
也即,在场景二中,该服务配置请求携带的配置类型为解除使用,且该服务配置请求还携带该目标服务租户的实例的标识、该目标服务的实例的标识和迟滞时间。That is, in scenario 2, the configuration type carried by the service configuration request is de-use, and the service configuration request further carries an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and a lag time.
比如,当NFV架构中的VNFM接收到NFVO或EM发送的针对某个VNF的实例标识删除请求时,VNFM在本地删除该VNF的实例的标识,并根据该VNF的服务列表,向PaaS发送针对该VNF的服务配置请求。该服务配置请求携带配置类型、该VNF的实例的标识、该VNF的实例调用的服务的实例的标识以及迟滞时间,其中,配置类型为解除使用。For example, when the VNFM in the NFV architecture receives the instance ID deletion request sent by the NFVO or the EM for a certain VNF, the VNFM locally deletes the identifier of the instance of the VNF, and sends the identifier to the PaaS according to the service list of the VNF. VNF service configuration request. The service configuration request carries a configuration type, an identifier of an instance of the VNF, an identifier of an instance of a service invoked by an instance of the VNF, and a lag time, wherein the configuration type is de-use.
步骤304:PaaS接收MANO实体发送的针对该目标服务的服务配置请求,并基于该服务配置请求,解除目标服务租户与目标服务之间的合约绑定关系。Step 304: The PaaS receives the service configuration request sent by the MANO entity for the target service, and cancels the contract binding relationship between the target service tenant and the target service based on the service configuration request.
由步骤303可知,MANO实体可能在两种不同的场景向PaaS发送针对该目标服务的服务配置请求,因此,相应地,步骤304也具体分为以下两种情况:It can be seen from step 303 that the MANO entity may send a service configuration request for the target service to the PaaS in two different scenarios, and accordingly, step 304 is also specifically divided into the following two cases:
针对步骤303中的场景一:当PaaS接收到该目标服务的服务配置请求时,由于该服务配置请求携带的配置类型为解除合约,因此PaaS可以根据该服务配置请求携带的目标服务租户的标识和目标服务的标识,查找已经建立的该目标服务租户与该目标服务之间的合约绑定关系,并解除该目标服务租户与该目标服务之间的合约绑定关系。For the scenario 1 in step 303: when the PaaS receives the service configuration request of the target service, the configuration type carried by the service configuration request is a release contract, so the PaaS can identify the target service tenant carried according to the service configuration request and An identifier of the target service, searching for a contract binding relationship between the target service tenant and the target service that has been established, and releasing a contract binding relationship between the target service tenant and the target service.
PaaS在解除该目标服务租户与该目标服务之间的合约绑定关系之后,还需向MANO实体发送第一类服务配置应答消息,该第一类服务配置应答消息用于指示目标服务与目标服务租户之间的合约绑定关系已经解除。After releasing the contract binding relationship between the target service tenant and the target service, the PaaS also needs to send a first type service configuration response message to the MANO entity, where the first type service configuration response message is used to indicate the target service and the target service. The contract binding relationship between tenants has been lifted.
也即,当MANO实体接收到该第一类服务配置应答消息时,确定PaaS已经将目标服务与目标服务租户之间的合约绑定关系解除。That is, when the MANO entity receives the first type of service configuration response message, it is determined that the PaaS has released the contract binding relationship between the target service and the target service tenant.
针对步骤303中的场景二:当PaaS接收到该目标服务的服务配置请求时,由于该服务配置请求携带的配置类型为解除使用,因此PaaS可以根据该服务配置请求携带的目标服务租户的实例的标识和目标服务的实例的标识,查找已经建立的该目标服务租户的实例与该目标服务的实例之间的使用绑定关系,并解除该使用绑定关系。For the scenario 2 in step 303, when the PaaS receives the service configuration request of the target service, the configuration type carried by the service configuration request is deactivated, so the PaaS can perform the instance of the target service tenant carried according to the service configuration request. The identifier of the instance of the identifier and the target service, finds a usage binding relationship between the instance of the target service tenant that has been established and the instance of the target service, and releases the usage binding relationship.
PaaS在解除该目标服务租户的实例与该目标服务的实例之间的使用绑定关系之后,还需向MANO实体发送第二类服务配置应答消息,该第二类服务配置应答消息用于指示目标服务的实例与目标服务租户的实例之间的使用绑定关系已经解除。After disabling the binding relationship between the instance of the target service tenant and the instance of the target service, the PaaS also needs to send a second type of service configuration response message to the MANO entity, and the second type of service configuration response message is used to indicate the target. The binding relationship between the instance of the service and the instance of the target service tenant has been removed.
也即,当MANO实体接收到该第二类服务配置应答消息时,确定PaaS已经将目标服务的实例与目标服务租户的实例之间的使用绑定关系解除。That is, when the MANO entity receives the second type of service configuration response message, it is determined that the PaaS has released the use binding relationship between the instance of the target service and the instance of the target service tenant.
由于在第二种场景中,MANO实体服务配置请求还包括一个迟滞时间,因此,PaaS在将目标服务的实例与目标服务租户的实例之间的使用绑定关系解除之后,为了避免PaaS立即终结该目标服务导致该目标服务租户的其他实例不能继续调用该目标服务,PaaS可以开始计时,该计时的时间即为迟滞时间,并在该迟滞时间内确定该目标服务租户是否再次调用该目标服务。若在当前时间之后的该迟滞时间内该目标服务租户不再调用该目标服务,此时PaaS可以解除该目标服务租户与该目标服务之间的合约绑定关系,并根据下述步骤305决定是否需要终结该目标服务。Since in the second scenario, the MANO entity service configuration request further includes a lag time, after the PaaS releases the use binding relationship between the target service instance and the target service tenant instance, in order to avoid the PaaS immediately terminating the The target service causes the other instances of the target service tenant to continue to call the target service, and the PaaS can start timing. The time of the timing is the lag time, and it is determined during the lag time whether the target service tenant calls the target service again. If the target service tenant does not invoke the target service within the lag time after the current time, the PaaS may cancel the contract binding relationship between the target service tenant and the target service, and determine whether according to step 305 below. Need to end the target service.
相应地,若在当前时间之后的该迟滞时间内该目标服务租户还在调用该目标服务,此时PaaS无需解除该目标服务租户与该目标服务之间的合约绑定关系,也即,PaaS将不会终结该目标服务。Correspondingly, if the target service tenant is still calling the target service within the lag time after the current time, the PaaS does not need to release the contract binding relationship between the target service tenant and the target service, that is, the PaaS will The target service will not be terminated.
步骤305:当PaaS确定不存在NFV架构中的其他服务租户与目标服务之间的合约绑定关系时,终结该目标服务的所有实例。Step 305: Terminate all instances of the target service when the PaaS determines that there is no contract binding relationship between the other service tenants in the NFV architecture and the target service.
在本申请实施例中,为了避免由于服务的实例随着调用该服务的VNF的实例的终结而终结,而导致每次调用该服务时,都需对该专有服务进行实例化的情况出现。当PaaS根据步骤304解除该目标服务租户与该目标服务之间的合约绑定关系时,PaaS并不是立即终结该目标服务,而是先判断是否存在需要调用该目标服务的其他服务租户。In the embodiment of the present application, in order to avoid termination due to the termination of the instance of the VNF that invokes the service, the instance of the service needs to be instantiated each time the service is invoked. When the PaaS releases the contract binding relationship between the target service tenant and the target service according to step 304, the PaaS does not immediately terminate the target service, but first determines whether there are other service tenants who need to invoke the target service.
若仍存在需要调用该目标服务的其他服务租户,假如此时直接终结该目标服务,将导致其他服务租户在继续调用该目标服务时,需重新对该目标服务实例化。因此,在本申请实施例中,PaaS将不立即终结该目标服务,而是在PaaS确定不存在需要调用该目标服务的其他服务租户时,才会终结该目标服务。If there are still other service tenants that need to call the target service, if the target service is directly terminated, the other service tenants will need to re-instantiate the target service when they continue to call the target service. Therefore, in the embodiment of the present application, the PaaS will not terminate the target service immediately, but will terminate the target service when the PaaS determines that there is no other service tenant that needs to invoke the target service.
具体地,PaaS可以通过判断当前是否存在与该目标服务存在合约绑定关系的其他服务租户,来实现确定是否存在需要调用该目标服务的服务租户,也即,当当前不存在与该目标服务存在合约绑定关系的其他服务租户时,确定不存在需要调用该目标服务的其他服务租户,此时PaaS终结该目标服务。Specifically, the PaaS may determine whether there is a service tenant that needs to invoke the target service by determining whether there is currently another service tenant that has a contract binding relationship with the target service, that is, when there is currently no service with the target service. When the other service tenants of the contract binding relationship determine that there are no other service tenants that need to call the target service, the PaaS terminates the target service.
相应地,当当前存在与该目标服务存在合约绑定关系的其他服务租户时,此时,PaaS将不会终结该目标服务。Accordingly, when there are currently other service tenants that have a contractual relationship with the target service, at this time, PaaS will not terminate the target service.
其中,PaaS终结该目标服务,也即,PaaS删除该目标服务的所有实例,并释放该目标服务的所有实例所占用的资源。Among them, PaaS terminates the target service, that is, PaaS deletes all instances of the target service and releases resources occupied by all instances of the target service.
在本申请实施例中,在PaaS上部署有多个服务,当MANO实体在确定该目标服务租户不再需要调用该目标服务时,向PaaS发送针对该目标服务的服务配置请求。PaaS基于该服务配置请求,解除该目标服务租户与该目标服务之间的合约绑定关系,并在确定不存其他服务租户与该目标服务之间的合约绑定关系时,终结该目标服务的所有实例。因此,本申请中提供的服务不必像公共服务那样始终保持在线,从而导致公共服务占用的资源长时间不能释放,增强了PaaS平台上资源的动态可用性,同时本申请提供的服务也不必像专有服务那样伴随服务租户的实例的终结而终结,提高了服务的实例在多个服务租户之间的可重用性,极大提升了PaaS平台对服务的资源管理的效率。In the embodiment of the present application, multiple services are deployed on the PaaS, and when the MANO entity determines that the target service tenant no longer needs to invoke the target service, the service configuration request for the target service is sent to the PaaS. Based on the service configuration request, the PaaS releases the contract binding relationship between the target service tenant and the target service, and terminates the target service when determining that there is no contract binding relationship between the other service tenant and the target service. All instances. Therefore, the services provided in this application do not have to remain online as public services, resulting in resources that cannot be released by public services for a long time, enhancing the dynamic availability of resources on the PaaS platform, and the services provided by this application do not have to be proprietary. The service is terminated as the service tenant's instance ends, which improves the reusability of the service instance among multiple service tenants, greatly improving the efficiency of the PaaS platform's resource management for the service.
参见图4A,本申请实施例提供了一种PaaS的管理装置400,应用于部署在NFV架 构中的PaaS,其特征在于,该PaaS上部署有多个服务,该装置400包括第一接收模块401、解除模块402和终结模块403:Referring to FIG. 4A, an embodiment of the present application provides a PaaS management apparatus 400, which is applied to a PaaS deployed in an NFV architecture, where a plurality of services are deployed on the PaaS, and the apparatus 400 includes a first receiving module 401. , the release module 402 and the termination module 403:
第一接收模块401,用于执行图3实施例的步骤304中的PaaS接收MANO实体发送的针对该目标服务的服务配置请求的步骤;a first receiving module 401, configured to perform the step of receiving, by the PaaS in step 304 of the embodiment of FIG. 3, a service configuration request for the target service sent by the MANO entity;
解除模块402,用于执行图3实施例的步骤304中的基于该服务配置请求,解除目标服务租户与目标服务之间的合约绑定关系的步骤;The releasing module 402 is configured to perform the step of canceling the contract binding relationship between the target service tenant and the target service based on the service configuration request in step 304 of the embodiment of FIG. 3;
终结模块403,用于执行图3实施例的步骤305。The termination module 403 is configured to perform step 305 of the embodiment of FIG. 3.
可选地,该服务配置请求携带配置类型、该目标服务租户的标识和该目标服务的标识,该配置类型为解除合约。Optionally, the service configuration request carries a configuration type, an identifier of the target service tenant, and an identifier of the target service, where the configuration type is a contract cancellation.
可选地,该装置400还包括:Optionally, the apparatus 400 further includes:
第三发送模块,用于向该MANO实体发送第一类服务配置应答消息,该第一类服务配置应答消息用于指示该目标服务与该目标服务租户之间的合约绑定关系已经解除。The third sending module is configured to send a first type of service configuration response message to the MANO entity, where the first type of service configuration response message is used to indicate that the contract binding relationship between the target service and the target service tenant has been released.
可选地,该服务配置请求携带配置类型、该目标服务租户的实例的标识、该目标服务的实例的标识和迟滞时间,该配置类型为解除使用;Optionally, the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and a lag time, and the configuration type is decommissioning;
相应地,该解除模块402,具体用于:Correspondingly, the releasing module 402 is specifically configured to:
基于该配置类型、该目标服务租户的实例的标识和该目标服务的实例的标识,解除该目标服务的实例与该目标服务租户的实例之间的使用绑定关系;Debinding the usage binding relationship between the instance of the target service and the instance of the target service tenant based on the configuration type, the identifier of the instance of the target service tenant, and the identifier of the instance of the target service;
当确定在当前时间之后的该迟滞时间内该目标服务租户没有再次调用该目标服务时,解除该目标服务与该目标服务租户之间的合约绑定关系。When it is determined that the target service tenant does not invoke the target service again within the lag time after the current time, the contract binding relationship between the target service and the target service tenant is released.
可选地,该装置400还包括:Optionally, the apparatus 400 further includes:
第四发送模块,用于向该MANO实体发送第二类服务配置应答消息,该第二类服务配置应答消息用于指示该目标服务的实例与该目标服务租户的实例之间的使用绑定关系已经解除。a fourth sending module, configured to send a second type of service configuration response message to the MANO entity, where the second type of service configuration response message is used to indicate a binding relationship between the instance of the target service and the instance of the target service tenant Has been lifted.
可选地,参见图4B,该装置400还包括第二接收模块404和建立模块405:Optionally, referring to FIG. 4B, the apparatus 400 further includes a second receiving module 404 and an establishing module 405:
第二接收模块404,用于执行图3实施例的步骤302中的PaaS接收该配置请求的步骤;a second receiving module 404, configured to perform the step of receiving, by the PaaS in step 302 of the embodiment of FIG. 3, the configuration request;
建立模块405,用于执行图3实施例的步骤302中的基于该配置请求携带的目标服务租户的实例的标识和目标服务的实例的标识,建立该目标服务的实例与目标服务租户的实例之间的使用绑定关系,并在确定目标服务的租户列表中不存在该目标服务租户时,建立该目标服务租户与该目标服务之间的合约绑定关系的步骤。The establishing module 405 is configured to perform the identifier of the instance of the target service tenant and the identifier of the target service carried in the step 302 of the embodiment of FIG. 3, and establish an instance of the target service and an instance of the target service tenant. The step of establishing a contract binding relationship between the target service tenant and the target service when the binding relationship is used and the target service tenant does not exist in the tenant list of the target service.
可选地,该装置400还包括第三接收模块、第一发送模块和第二发送模块:Optionally, the apparatus 400 further includes a third receiving module, a first sending module, and a second sending module:
第三接收模块,用于接收该MANO实体发送的实例获取请求,该实例获取请求携带该目标服务的标识;a third receiving module, configured to receive an instance obtaining request sent by the MANO entity, where the instance obtains an identifier that carries the target service;
第一发送模块,用于当基于该目标服务的标识确定存在该目标服务的实例时,向该MANO实体发送第一应答消息,该第一应答消息用于指示该目标服务已经实例化,且该第一应答消息携带该目标服务的实例的标识;a first sending module, configured to send a first response message to the MANO entity when the identifier of the target service is determined based on the identifier of the target service, where the first response message is used to indicate that the target service has been instantiated, and The first response message carries an identifier of an instance of the target service;
第二发送模块,用于当基于该目标服务的标识确定不存在该目标服务的实例时,向该MANO实体发送第二应答消息,该第二应答消息用于指示该目标服务未实例化,接收 该MANO实体发送的服务实例化请求,该服务实例化请求中携带该目标服务的标识,基于该目标服务的标识,对该目标服务进行实例化,得到该目标服务的实例,向该MANO实体发送实例化应答消息,该实例化应答消息携带该目标服务的实例的标识。a second sending module, configured to send a second response message to the MANO entity when the identifier of the target service is determined to be absent based on the identifier of the target service, where the second response message is used to indicate that the target service is not instantiated and received a service instantiation request sent by the MANO entity, the service instantiation request carrying an identifier of the target service, instantiating the target service based on the identifier of the target service, obtaining an instance of the target service, and sending the target service instance to the MANO entity A reply message is instantiated that carries an identification of an instance of the target service.
可选地,该第二发送模块,具体用于:Optionally, the second sending module is specifically configured to:
基于该目标服务的标识,从存储的服务的描述符文件中获取该目标服务的描述符文件,该目标服务的描述符文件用于描述在该目标服务实例化过程中所需要的信息;Obtaining, according to the identifier of the target service, a descriptor file of the target service from a descriptor file of the stored service, where the descriptor file of the target service is used to describe information required in the target service instantiation process;
根据该目标服务的描述符文件中该目标服务实例化过程中所需要的信息,对该目标服务进行实例化,得到该目标服务的实例。The target service is instantiated according to the information required in the target service instantiation process in the descriptor file of the target service, and an instance of the target service is obtained.
可选地,该MANO实体为该NFV架构中的虚拟网络功能管理器VNFM。Optionally, the MANO entity is a virtual network function manager VNFM in the NFV architecture.
在本申请实施例中,在PaaS上部署有多个服务,当MANO实体在确定该目标服务租户不再需要调用该目标服务时,向PaaS发送针对该目标服务的服务配置请求。PaaS基于该服务配置请求,解除该目标服务租户与该目标服务之间的合约绑定关系,并在确定不存其他服务租户与该目标服务之间的合约绑定关系时,终结该目标服务的所有实例。因此,本申请中提供的服务不必像公共服务那样始终保持在线,从而导致公共服务占用的资源长时间不能释放,增强了PaaS平台上资源的动态可用性,同时本申请提供的服务也不必像专有服务那样伴随服务租户的实例的终结而终结,提高了服务的实例在多个服务租户之间的可重用性,极大提升了PaaS平台对服务的资源管理的效率。In the embodiment of the present application, multiple services are deployed on the PaaS, and when the MANO entity determines that the target service tenant no longer needs to invoke the target service, the service configuration request for the target service is sent to the PaaS. Based on the service configuration request, the PaaS releases the contract binding relationship between the target service tenant and the target service, and terminates the target service when determining that there is no contract binding relationship between the other service tenant and the target service. All instances. Therefore, the services provided in this application do not have to remain online as public services, resulting in resources that cannot be released by public services for a long time, enhancing the dynamic availability of resources on the PaaS platform, and the services provided by this application do not have to be proprietary. The service is terminated as the service tenant's instance ends, which improves the reusability of the service instance among multiple service tenants, greatly improving the efficiency of the PaaS platform's resource management for the service.
参见图5A,本申请实施例提供了另一种PaaS的管理装置500,应用于NFV架构中的MANO实体,该NFV架构中部署有PaaS,该装置500包括第一发送模块501:Referring to FIG. 5A, an embodiment of the present application provides another PaaS management apparatus 500, which is applied to a MANO entity in an NFV architecture. The NFV architecture is deployed with PaaS, and the apparatus 500 includes a first sending module 501:
第一发送模块501,用于执行图3实施例中的步骤303;The first sending module 501 is configured to perform step 303 in the embodiment of FIG. 3;
该服务配置请求用于指示该PaaS基于该服务配置请求解除该目标服务租户与该目标服务之间的合约绑定关系,并在确定不存在其他服务租户与该目标服务之间的合约绑定关系时终结该目标服务的所有实例,该目标服务为该多个服务中的任一服务。The service configuration request is used to indicate that the PaaS releases the contract binding relationship between the target service tenant and the target service based on the service configuration request, and determines that there is no contract binding relationship between the other service tenant and the target service. Terminates all instances of the target service, which is one of the multiple services.
可选地,该第一发送模块501,具体用于:Optionally, the first sending module 501 is specifically configured to:
当确定该目标服务租户的描述符文件被更新时,获取更新之后的该目标服务租户的描述符文件;When it is determined that the descriptor file of the target service tenant is updated, obtaining a descriptor file of the target service tenant after the update;
当根据更新之后的该目标服务租户的描述符文件,确定需要将该目标服务从该目标服务租户使用的服务列表中删除时,向该PaaS发送服务配置请求,该服务配置请求携带配置类型、该目标服务租户的标识和该目标服务的标识,该配置类型为解除合约。When it is determined that the target service needs to be deleted from the service list used by the target service tenant according to the updated descriptor file of the target service tenant, the service configuration request is sent to the PaaS, and the service configuration request carries the configuration type, The identity of the target service tenant and the identity of the target service. The configuration type is the contract cancellation.
可选地,该装置500还包括第三接收模块:Optionally, the apparatus 500 further includes a third receiving module:
第三接收模块,用于接收该PaaS发送的第一类服务配置应答消息,该第一类服务配置应答消息用于指示该目标服务与该目标服务租户之间的合约绑定关系已经解除。The third receiving module is configured to receive the first type of service configuration response message sent by the PaaS, where the first type of service configuration response message is used to indicate that the contract binding relationship between the target service and the target service tenant has been released.
可选地,该第一发送模块501,具体用于:Optionally, the first sending module 501 is specifically configured to:
当删除该目标服务租户的实例的标识时,获取该目标服务租户的描述符文件;Obtaining a descriptor file of the target service tenant when deleting the identifier of the target service tenant instance;
根据该目标服务租户的描述符文件,确定迟滞时间;Determining the lag time according to the descriptor file of the target service tenant;
向该PaaS发送该服务配置请求,该服务配置请求携带配置类型、该目标服务租户的实例的标识、该目标服务的实例的标识和该迟滞时间,该配置类型为解除使用。Sending the service configuration request to the PaaS, the service configuration request carrying a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and the lag time, the configuration type being decommissioning.
可选地,该装置500还包括第四接收模块:Optionally, the apparatus 500 further includes a fourth receiving module:
第四接收模块,用于接收该PaaS发送的第二类服务配置应答消息,该第二类服务配置应答消息用于指示该目标服务的实例与该目标服务租户的实例之间的使用绑定关系已经解除。a fourth receiving module, configured to receive a second type of service configuration response message sent by the PaaS, where the second type of service configuration response message is used to indicate a binding relationship between the instance of the target service and an instance of the target service tenant Has been lifted.
可选地,参见图5B,该装置500还包括第二发送模块502:Optionally, referring to FIG. 5B, the apparatus 500 further includes a second sending module 502:
第二发送模块502,用于执行图3实施例中的步骤301。The second sending module 502 is configured to perform step 301 in the embodiment of FIG. 3.
可选地,该装置500还包括第三发送模块、第一接收模块和第二接收模块:Optionally, the apparatus 500 further includes a third sending module, a first receiving module, and a second receiving module:
第三发送模块,用于当确定该目标服务租户的实例需要调用目标服务时,向该PaaS发送实例获取请求,该实例获取请求携带该目标服务的标识;a third sending module, configured to send an instance obtaining request to the PaaS when the instance of the target service tenant needs to invoke the target service, where the instance obtaining request carries the identifier of the target service;
第一接收模块,用于接收该PaaS发送的第一应答消息,该第一应答消息用于指示该目标服务已经实例化,且该第一应答消息携带该目标服务的实例的标识;a first receiving module, configured to receive a first response message sent by the PaaS, where the first response message is used to indicate that the target service has been instantiated, and the first response message carries an identifier of an instance of the target service;
第二接收模块,用于接收该PaaS发送的第二应答消息,该第二应答消息用于指示该目标服务未实例化,向该PaaS发送服务实例化请求,该服务实例化请求中携带该目标服务的标识,接收该PaaS发送的实例化应答消息,该实例化应答消息携带该目标服务的实例的标识。a second receiving module, configured to receive a second response message sent by the PaaS, where the second response message is used to indicate that the target service is not instantiated, and send a service instantiation request to the PaaS, where the service instantiation request carries the target An identifier of the service, receiving an instantiation response message sent by the PaaS, where the instantiated response message carries an identifier of an instance of the target service.
可选地,该MANO实体为该NFV架构中的虚拟网络功能管理器VNFM。Optionally, the MANO entity is a virtual network function manager VNFM in the NFV architecture.
在本申请实施例中,在PaaS上部署有多个服务,当MANO实体在确定该目标服务租户不再需要调用该目标服务时,向PaaS发送针对该目标服务的服务配置请求。PaaS基于该服务配置请求,解除该目标服务租户与该目标服务之间的合约绑定关系,并在确定不存其他服务租户与该目标服务之间的合约绑定关系时,终结该目标服务的所有实例。因此,本申请中提供的服务不必像公共服务那样始终保持在线,从而导致公共服务占用的资源长时间不能释放,增强了PaaS平台上资源的动态可用性,同时本申请提供的服务也不必像专有服务那样伴随服务租户的实例的终结而终结,提高了服务的实例在多个服务租户之间的可重用性,极大提升了PaaS平台对服务的资源管理的效率。In the embodiment of the present application, multiple services are deployed on the PaaS, and when the MANO entity determines that the target service tenant no longer needs to invoke the target service, the service configuration request for the target service is sent to the PaaS. Based on the service configuration request, the PaaS releases the contract binding relationship between the target service tenant and the target service, and terminates the target service when determining that there is no contract binding relationship between the other service tenant and the target service. All instances. Therefore, the services provided in this application do not have to remain online as public services, resulting in resources that cannot be released by public services for a long time, enhancing the dynamic availability of resources on the PaaS platform, and the services provided by this application do not have to be proprietary. The service is terminated as the service tenant's instance ends, which improves the reusability of the service instance among multiple service tenants, greatly improving the efficiency of the PaaS platform's resource management for the service.
需要说明的是:上述实施例提供的PaaS的管理装置在对PaaS上的服务进行管理时,仅以上述各功能模块的划分进行举例说明,实际应用中,可以根据需要而将上述功能分配由不同的功能模块完成,即将设备的内部结构划分成不同的功能模块,以完成以上描述的全部或者部分功能。另外,上述实施例提供的PaaS的管理装置与图3实施例中的PaaS的管理方法实施例属于同一构思,其具体实现过程详见方法实施例,这里不再赘述。It should be noted that, when the management device of the PaaS provided by the foregoing embodiment manages the service on the PaaS, only the division of the foregoing functional modules is illustrated. In actual applications, the functions may be allocated differently according to requirements. The function module is completed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the management device of the PaaS provided by the foregoing embodiment is the same as the embodiment of the method for managing the PaaS in the embodiment of FIG. 3, and the specific implementation process is described in detail in the method embodiment, and details are not described herein again.
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意结合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所 述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如:同轴电缆、光纤、数据用户线(Digital Subscriber Line,DSL))或无线(例如:红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如:软盘、硬盘、磁带)、光介质(例如:数字通用光盘(Digital Versatile Disc,DVD))、或者半导体介质(例如:固态硬盘(Solid State Disk,SSD))等。In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital versatile disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)). )Wait.
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成,也可以通过程序来指令相关的硬件完成,所述的程序可以存储于一种计算机可读存储介质中,上述提到的存储介质可以是只读存储器,磁盘或光盘等。A person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium. The storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.
以上所述为本申请提供的实施例,并不用以限制本申请,凡在本申请的精神和原则之内,所作的任何修改、等同替换、改进等,均应包含在本申请的保护范围之内。The above description of the embodiments of the present application is not intended to limit the application, and any modifications, equivalents, improvements, etc. made within the spirit and principles of the present application are included in the scope of the present application. Inside.
Claims (22)
- 一种平台即服务PaaS的管理方法,应用于部署在网络功能虚拟化NFV架构中的PaaS,其特征在于,所述PaaS上部署有多个服务,所述方法包括:A platform-as-a-service PaaS management method is applied to a PaaS deployed in a network function virtualization NFV architecture, wherein a plurality of services are deployed on the PaaS, and the method includes:接收所述NFV架构中的管理与编排功能MANO实体发送的针对目标服务的服务配置请求,所述服务配置请求为所述MANO实体在确定所述NFV架构中的目标服务租户不再调用所述目标服务时发送的,所述目标服务为所述多个服务中的任一个;Receiving a service configuration request for the target service sent by the management and orchestration function MANO entity in the NFV architecture, where the service configuration request is that the target service tenant in the NFV architecture does not invoke the target The target service is sent by the service, and the target service is any one of the multiple services;基于所述服务配置请求,解除所述目标服务租户与所述目标服务之间的合约绑定关系,所述合约绑定关系用于指示所述目标服务租户能够调用所述目标服务;Determining, by the service configuration request, a contract binding relationship between the target service tenant and the target service, where the contract binding relationship is used to indicate that the target service tenant can invoke the target service;当确定不存在所述NFV架构中的其他服务租户与所述目标服务之间的合约绑定关系时,终结所述目标服务的所有实例。When it is determined that there is no contract binding relationship between other service tenants in the NFV architecture and the target service, all instances of the target service are terminated.
- 如权利要求1所述的方法,其特征在于,所述服务配置请求携带配置类型、所述目标服务租户的标识和所述目标服务的标识,所述配置类型为解除合约。The method of claim 1, wherein the service configuration request carries a configuration type, an identifier of the target service tenant, and an identifier of the target service, the configuration type being a contract cancellation.
- 如权利要求1所述的方法,其特征在于,所述服务配置请求携带配置类型、所述目标服务租户的实例的标识、所述目标服务的实例的标识和迟滞时间,所述配置类型为解除使用;The method of claim 1, wherein the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and a lag time, the configuration type being released use;相应地,所述基于所述服务配置请求,解除所述目标服务租户与所述目标服务之间的合约绑定关系,包括:Correspondingly, the canceling a contract binding relationship between the target service tenant and the target service based on the service configuration request includes:基于所述配置类型、所述目标服务租户的实例的标识和所述目标服务的实例的标识,解除所述目标服务的实例与所述目标服务租户的实例之间的使用绑定关系;Deleting a use binding relationship between the instance of the target service and the instance of the target service tenant based on the configuration type, an identifier of an instance of the target service tenant, and an identifier of an instance of the target service;当确定在当前时间之后的所述迟滞时间内所述目标服务租户没有再次调用所述目标服务时,解除所述目标服务与所述目标服务租户之间的合约绑定关系。When it is determined that the target service tenant does not invoke the target service again within the lag time after the current time, the contract binding relationship between the target service and the target service tenant is released.
- 如权利要求1所述的方法,其特征在于,所述接收所述NFV架构中的MANO实体发送的针对目标服务的服务配置请求之前,还包括:The method of claim 1, wherein before receiving the service configuration request for the target service sent by the MANO entity in the NFV architecture, the method further includes:接收所述MANO实体发送的配置请求,所述配置请求携带所述目标服务租户的实例的标识和所述目标服务的实例的标识;Receiving a configuration request sent by the MANO entity, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service;基于所述目标服务租户的实例的标识和所述目标服务的实例的标识,建立所述目标服务租户的实例与所述目标服务的实例之间的使用绑定关系,并在确定所述目标服务的租户列表中不存在所述目标服务租户时,建立所述目标服务租户与所述目标服务之间的合约绑定关系。Establishing a usage binding relationship between an instance of the target service tenant and an instance of the target service based on an identifier of an instance of the target service tenant and an identifier of an instance of the target service, and determining the target service Establishing a contract binding relationship between the target service tenant and the target service when the target service tenant does not exist in the tenant list.
- 如权利要求4所述的方法,其特征在于,所述接收所述MANO实体发送的配置请求之前,还包括:The method of claim 4, wherein before receiving the configuration request sent by the MANO entity, the method further includes:接收所述MANO实体发送的实例获取请求,所述实例获取请求携带所述目标服务的标识;Receiving an instance obtaining request sent by the MANO entity, where the instance obtaining request carries an identifier of the target service;当基于所述目标服务的标识确定存在所述目标服务的实例时,向所述MANO实体发送第一应答消息,所述第一应答消息用于指示所述目标服务已经实例化,且所述第一应答消息携带所述目标服务的实例的标识;Sending a first response message to the MANO entity when the instance of the target service is determined to be present based on the identifier of the target service, the first response message is used to indicate that the target service has been instantiated, and the A response message carries an identifier of an instance of the target service;当基于所述目标服务的标识确定不存在所述目标服务的实例时,向所述MANO实体发送第二应答消息,所述第二应答消息用于指示所述目标服务未实例化,接收所述MANO实体发送的服务实例化请求,所述服务实例化请求中携带所述目标服务的标识,基于所述目标服务的标识,对所述目标服务进行实例化,得到所述目标服务的实例,向所述MANO 实体发送实例化应答消息,所述实例化应答消息携带所述目标服务的实例的标识。Sending a second response message to the MANO entity when the identifier of the target service is determined to be absent based on the identifier of the target service, the second response message is used to indicate that the target service is not instantiated, and receiving the a service instantiation request sent by the MANO entity, where the service instantiation request carries an identifier of the target service, and the target service is instantiated based on the identifier of the target service, and an instance of the target service is obtained. The MANO entity sends an instantiation response message, the instantiated response message carrying an identification of an instance of the target service.
- 如权利要求5所述的方法,其特征在于,所述基于所述目标服务的标识,对所述目标服务进行实例化,得到所述目标服务的实例,包括:The method according to claim 5, wherein the instantiating the target service based on the identifier of the target service to obtain an instance of the target service comprises:基于所述目标服务的标识,从存储的服务的描述符文件中获取所述目标服务的描述符文件,所述目标服务的描述符文件用于描述在所述目标服务实例化过程中所需要的信息;Obtaining a descriptor file of the target service from a descriptor file of the stored service, where the descriptor file of the target service is used to describe a required process in the target service instantiation process, based on the identifier of the target service information;根据所述目标服务的描述符文件中所述目标服务实例化过程中所需要的信息,对所述目标服务进行实例化,得到所述目标服务的实例。And authenticating the target service according to the information required in the target service instantiation process in the descriptor file of the target service, to obtain an instance of the target service.
- 一种平台即服务PaaS的管理方法,应用于网络功能虚拟化NFV架构中的管理与编排功能MANO实体,所述NFV架构中部署有PaaS,其特征在于,所述PaaS上部署有多个服务,所述方法包括:A platform-as-a-service PaaS management method is applied to a network function virtualization MNV architecture management and orchestration function MANO entity, wherein the NFV architecture is deployed with PaaS, wherein the PaaS is deployed with multiple services. The method includes:当确定所述NFV架构中的目标服务租户不再调用目标服务时,向所述PaaS发送针对所述目标服务的服务配置请求;When it is determined that the target service tenant in the NFV architecture no longer invokes the target service, sending a service configuration request for the target service to the PaaS;所述服务配置请求用于指示所述PaaS基于所述服务配置请求解除所述目标服务租户与所述目标服务之间的合约绑定关系,并在确定不存在其他服务租户与所述目标服务之间的合约绑定关系时终结所述目标服务的所有实例,所述目标服务为所述多个服务中的任一服务。The service configuration request is used to instruct the PaaS to cancel a contract binding relationship between the target service tenant and the target service based on the service configuration request, and determine that there is no other service tenant and the target service. Terminating all instances of the target service when the contract binding relationship is, the target service being any of the plurality of services.
- 如权利要求7所述的方法,其特征在于,所述当确定所述NFV架构中的目标服务租户不再调用目标服务时,向所述PaaS发送针对所述目标服务的服务配置请求,包括:The method of claim 7, wherein when the target service tenant in the NFV architecture is determined to no longer invoke the target service, the service configuration request for the target service is sent to the PaaS, including:当确定所述目标服务租户的描述符文件被更新时,获取更新之后的所述目标服务租户的描述符文件;When it is determined that the descriptor file of the target service tenant is updated, obtaining a descriptor file of the target service tenant after the update;当根据更新之后的所述目标服务租户的描述符文件,确定需要将所述目标服务从所述目标服务租户使用的服务列表中删除时,向所述PaaS发送服务配置请求,所述服务配置请求携带配置类型、所述目标服务租户的标识和所述目标服务的标识,所述配置类型为解除合约。When it is determined that the target service needs to be deleted from the service list used by the target service tenant according to the descriptor file of the target service tenant after the update, sending a service configuration request to the PaaS, the service configuration request Carrying a configuration type, an identifier of the target service tenant, and an identifier of the target service, where the configuration type is a contract cancellation.
- 如权利要求7所述的方法,其特征在于,所述当确定所述NFV架构中的目标服务租户不再调用目标服务时,向所述PaaS发送针对所述目标服务的服务配置请求,包括:The method of claim 7, wherein when the target service tenant in the NFV architecture is determined to no longer invoke the target service, the service configuration request for the target service is sent to the PaaS, including:当删除所述目标服务租户的实例的标识时,获取所述目标服务租户的描述符文件;Obtaining a descriptor file of the target service tenant when deleting an identifier of an instance of the target service tenant;根据所述目标服务租户的描述符文件,确定迟滞时间;Determining a lag time according to the descriptor file of the target service tenant;向所述PaaS发送所述服务配置请求,所述服务配置请求携带配置类型、所述目标服务租户的实例的标识、所述目标服务的实例的标识和所述迟滞时间,所述配置类型为解除使用。And sending, to the PaaS, the service configuration request, where the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and the lag time, where the configuration type is use.
- 如权利要求7所述的方法,其特征在于,所述向所述PaaS发送针对所述目标服务的服务配置请求之前,还包括:The method of claim 7, wherein before the sending the service configuration request for the target service to the PaaS, the method further comprises:向所述PaaS发送配置请求,所述配置请求携带所述目标服务租户的实例的标识和所述目标服务的实例的标识,所述配置请求用于指示所述PaaS建立所述目标服务租户的实例与所述目标服务的实例之间的使用绑定关系。Sending a configuration request to the PaaS, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service, where the configuration request is used to instruct the PaaS to establish an instance of the target service tenant A binding relationship with the instance of the target service.
- 如权利要求10所述的方法,其特征在于,所述向所述PaaS发送配置请求之前,还包括:The method of claim 10, wherein before the sending the configuration request to the PaaS, the method further comprises:当确定所述目标服务租户的实例需要调用目标服务时,向所述PaaS发送实例获取请求,所述实例获取请求携带所述目标服务的标识;When it is determined that the instance of the target service tenant needs to invoke the target service, sending an instance obtaining request to the PaaS, where the instance obtaining request carries an identifier of the target service;接收所述PaaS发送的第一应答消息,所述第一应答消息用于指示所述目标服务已经实例化,且所述第一应答消息携带所述目标服务的实例的标识;Receiving a first response message sent by the PaaS, where the first response message is used to indicate that the target service has been instantiated, and the first response message carries an identifier of an instance of the target service;接收所述PaaS发送的第二应答消息,所述第二应答消息用于指示所述目标服务未实例化,向所述PaaS发送服务实例化请求,所述服务实例化请求中携带所述目标服务的标识,接收所述PaaS发送的实例化应答消息,所述实例化应答消息携带所述目标服务的实例的标识。Receiving a second response message sent by the PaaS, where the second response message is used to indicate that the target service is not instantiated, and send a service instantiation request to the PaaS, where the service instantiation request carries the target service And an identifier that is sent by the PaaS, where the instantiated response message carries an identifier of an instance of the target service.
- 一种平台即服务PaaS的管理装置,应用于部署在网络功能虚拟化NFV架构中的PaaS,其特征在于,所述PaaS上部署有多个服务,所述装置包括:A platform-as-a-service PaaS management device is applied to a PaaS deployed in a network function virtualization NFV architecture, wherein a plurality of services are deployed on the PaaS, and the device includes:第一接收模块,用于接收所述NFV架构中的管理与编排功能MANO实体发送的针对目标服务的服务配置请求,所述服务配置请求为所述MANO实体在确定所述NFV架构中的目标服务租户不再调用所述目标服务时发送的,所述目标服务为所述多个服务中的任一个;a first receiving module, configured to receive a service configuration request for a target service sent by a management and orchestration function MANO entity in the NFV architecture, where the service configuration request is a target service of the MANO entity in determining the NFV architecture When the tenant no longer invokes the target service, the target service is any one of the multiple services;解除模块,用于基于所述服务配置请求,解除所述目标服务租户与所述目标服务之间的合约绑定关系,所述合约绑定关系用于指示所述目标服务租户能够调用所述目标服务;a release module, configured to cancel a contract binding relationship between the target service tenant and the target service based on the service configuration request, where the contract binding relationship is used to indicate that the target service tenant can invoke the target service;终结模块,用于当确定不存在所述NFV架构中的其他服务租户与所述目标服务之间的合约绑定关系时,终结所述目标服务的所有实例。And a terminating module, configured to terminate all instances of the target service when it is determined that there is no contract binding relationship between the other service tenants in the NFV architecture and the target service.
- 如权利要求12所述的装置,其特征在于,所述服务配置请求携带配置类型、所述目标服务租户的标识和所述目标服务的标识,所述配置类型为解除合约。The apparatus according to claim 12, wherein the service configuration request carries a configuration type, an identifier of the target service tenant, and an identifier of the target service, and the configuration type is a contract cancellation.
- 如权利要求12所述的装置,其特征在于,所述服务配置请求携带配置类型、所述目标服务租户的实例的标识、所述目标服务的实例的标识和迟滞时间,所述配置类型为解除使用;The apparatus according to claim 12, wherein the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and a lag time, and the configuration type is use;相应地,所述解除模块,具体用于:Correspondingly, the releasing module is specifically configured to:基于所述配置类型、所述目标服务租户的实例的标识和所述目标服务的实例的标识,解除所述目标服务的实例与所述目标服务租户的实例之间的使用绑定关系;Deleting a use binding relationship between the instance of the target service and the instance of the target service tenant based on the configuration type, an identifier of an instance of the target service tenant, and an identifier of an instance of the target service;当确定在当前时间之后的所述迟滞时间内所述目标服务租户没有再次调用所述目标服务时,解除所述目标服务与所述目标服务租户之间的合约绑定关系。When it is determined that the target service tenant does not invoke the target service again within the lag time after the current time, the contract binding relationship between the target service and the target service tenant is released.
- 如权利要求12所述的装置,其特征在于,所述装置还包括:The device of claim 12, wherein the device further comprises:第二接收模块,用于接收所述MANO实体发送的配置请求,所述配置请求携带所述目标服务租户的实例的标识和所述目标服务的实例的标识;a second receiving module, configured to receive a configuration request sent by the MANO entity, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service;建立模块,用于基于所述目标服务租户的实例的标识和所述目标服务的实例的标识,建立所述目标服务租户的实例与所述目标服务的实例之间的使用绑定关系,并在确定所述目标服务的租户列表中不存在所述目标服务租户时,建立所述目标服务租户与所述目标服务之间的合约绑定关系。Establishing a module, configured to establish, according to an identifier of an instance of the target service tenant and an identifier of an instance of the target service, a binding relationship between an instance of the target service tenant and an instance of the target service, and When it is determined that the target service tenant does not exist in the tenant list of the target service, establishing a contract binding relationship between the target service tenant and the target service.
- 如权利要求15所述的装置,其特征在于,所述装置还包括:The device of claim 15 wherein said device further comprises:第三接收模块,用于接收所述MANO实体发送的实例获取请求,所述实例获取请求携带所述目标服务的标识;a third receiving module, configured to receive an instance obtaining request sent by the MANO entity, where the instance obtaining request carries an identifier of the target service;第一发送模块,用于当基于所述目标服务的标识确定存在所述目标服务的实例时,向所述MANO实体发送第一应答消息,所述第一应答消息用于指示所述目标服务已经实例化,且所述第一应答消息携带所述目标服务的实例的标识;a first sending module, configured to send a first response message to the MANO entity when determining that an instance of the target service exists based on an identifier of the target service, where the first response message is used to indicate that the target service has been Instantiating, and the first response message carries an identifier of an instance of the target service;第二发送模块,用于当基于所述目标服务的标识确定不存在所述目标服务的实例时,向所述MANO实体发送第二应答消息,所述第二应答消息用于指示所述目标服务未实例化, 接收所述MANO实体发送的服务实例化请求,所述服务实例化请求中携带所述目标服务的标识,基于所述目标服务的标识,对所述目标服务进行实例化,得到所述目标服务的实例,向所述MANO实体发送实例化应答消息,所述实例化应答消息携带所述目标服务的实例的标识。a second sending module, configured to send a second response message to the MANO entity when the instance of the target service does not exist based on the identifier of the target service, where the second response message is used to indicate the target service Not instantiating, receiving a service instantiation request sent by the MANO entity, carrying the identifier of the target service in the service instantiation request, instantiating the target service based on the identifier of the target service, obtaining a An instance of the target service, sending an instantiation response message to the MANO entity, the instantiated response message carrying an identifier of an instance of the target service.
- 如权利要求16所述的装置,其特征在于,所述第二发送模块,具体用于:The device according to claim 16, wherein the second sending module is specifically configured to:基于所述目标服务的标识,从存储的服务的描述符文件中获取所述目标服务的描述符文件,所述目标服务的描述符文件用于描述在所述目标服务实例化过程中所需要的信息;Obtaining a descriptor file of the target service from a descriptor file of the stored service, where the descriptor file of the target service is used to describe a required process in the target service instantiation process, based on the identifier of the target service information;根据所述目标服务的描述符文件中所述目标服务实例化过程中所需要的信息,对所述目标服务进行实例化,得到所述目标服务的实例。And authenticating the target service according to the information required in the target service instantiation process in the descriptor file of the target service, to obtain an instance of the target service.
- 一种平台即服务PaaS的管理装置,应用于网络功能虚拟化NFV架构中的管理与编排功能MANO实体,所述NFV架构中部署有PaaS,其特征在于,所述PaaS上部署有多个服务,所述装置包括:A platform-as-a-service PaaS management device is applied to a management and orchestration function MANO entity in a network function virtualization NFV architecture, wherein the NFV architecture is deployed with PaaS, wherein a plurality of services are deployed on the PaaS. The device includes:第一发送模块,用于当确定所述NFV架构中的目标服务租户不再调用目标服务时,向所述PaaS发送针对所述目标服务的服务配置请求;a first sending module, configured to send a service configuration request for the target service to the PaaS when determining that the target service tenant in the NFV architecture no longer invokes the target service;所述服务配置请求用于指示所述PaaS基于所述服务配置请求解除所述目标服务租户与所述目标服务之间的合约绑定关系,并在确定不存在其他服务租户与所述目标服务之间的合约绑定关系时终结所述目标服务的所有实例,所述目标服务为所述多个服务中的任一服务。The service configuration request is used to instruct the PaaS to cancel a contract binding relationship between the target service tenant and the target service based on the service configuration request, and determine that there is no other service tenant and the target service. Terminating all instances of the target service when the contract binding relationship is, the target service being any of the plurality of services.
- 如权利要求18所述的装置,其特征在于,所述第一发送模块,具体用于:The device according to claim 18, wherein the first sending module is specifically configured to:当确定所述目标服务租户的描述符文件被更新时,获取更新之后的所述目标服务租户的描述符文件;When it is determined that the descriptor file of the target service tenant is updated, obtaining a descriptor file of the target service tenant after the update;当根据更新之后的所述目标服务租户的描述符文件,确定需要将所述目标服务从所述目标服务租户使用的服务列表中删除时,向所述PaaS发送服务配置请求,所述服务配置请求携带配置类型、所述目标服务租户的标识和所述目标服务的标识,所述配置类型为解除合约。When it is determined that the target service needs to be deleted from the service list used by the target service tenant according to the descriptor file of the target service tenant after the update, sending a service configuration request to the PaaS, the service configuration request Carrying a configuration type, an identifier of the target service tenant, and an identifier of the target service, where the configuration type is a contract cancellation.
- 如权利要求18所述的装置,其特征在于,所述第一发送模块,具体用于:The device according to claim 18, wherein the first sending module is specifically configured to:当删除所述目标服务租户的实例的标识时,获取所述目标服务租户的描述符文件;Obtaining a descriptor file of the target service tenant when deleting an identifier of an instance of the target service tenant;根据所述目标服务租户的描述符文件,确定迟滞时间;Determining a lag time according to the descriptor file of the target service tenant;向所述PaaS发送所述服务配置请求,所述服务配置请求携带配置类型、所述目标服务租户的实例的标识、所述目标服务的实例的标识和所述迟滞时间,所述配置类型为解除使用。And sending, to the PaaS, the service configuration request, where the service configuration request carries a configuration type, an identifier of an instance of the target service tenant, an identifier of an instance of the target service, and the lag time, where the configuration type is use.
- 如权利要求18所述的装置,其特征在于,所述装置还包括:The device of claim 18, wherein the device further comprises:第二发送模块,用于向所述PaaS发送配置请求,所述配置请求携带所述目标服务租户的实例的标识和所述目标服务的实例的标识,所述配置请求用于指示所述PaaS建立所述目标服务租户的实例与所述目标服务的实例之间的使用绑定关系。a second sending module, configured to send a configuration request to the PaaS, where the configuration request carries an identifier of an instance of the target service tenant and an identifier of an instance of the target service, where the configuration request is used to indicate that the PaaS is established A binding relationship between the instance of the target service tenant and the instance of the target service.
- 如权利要求21所述的装置,其特征在于,所述装置还包括:The device of claim 21, wherein the device further comprises:第三发送模块,用于当确定所述目标服务租户的实例需要调用目标服务时,向所述PaaS发送实例获取请求,所述实例获取请求携带所述目标服务的标识;a third sending module, configured to send an instance obtaining request to the PaaS when the instance of the target service tenant needs to invoke the target service, where the instance obtaining request carries the identifier of the target service;第一接收模块,用于接收所述PaaS发送的第一应答消息,所述第一应答消息用于指示所述目标服务已经实例化,且所述第一应答消息携带所述目标服务的实例的标识;a first receiving module, configured to receive a first response message sent by the PaaS, where the first response message is used to indicate that the target service has been instantiated, and the first response message carries an instance of the target service Identification第二接收模块,用于接收所述PaaS发送的第二应答消息,所述第二应答消息用于指示所述目标服务未实例化,向所述PaaS发送服务实例化请求,所述服务实例化请求中携带所述目标服务的标识,接收所述PaaS发送的实例化应答消息,所述实例化应答消息携带所述目标服务的实例的标识。a second receiving module, configured to receive a second response message sent by the PaaS, where the second response message is used to indicate that the target service is not instantiated, and send a service instantiation request to the PaaS, where the service is instantiated The request carries an identifier of the target service, and receives an instantiation response message sent by the PaaS, where the instantiated response message carries an identifier of an instance of the target service.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201711288701.XA CN109905258B (en) | 2017-12-07 | 2017-12-07 | PaaS management method, device and storage medium |
CN201711288701.X | 2017-12-07 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019109948A1 true WO2019109948A1 (en) | 2019-06-13 |
Family
ID=66751302
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/119367 WO2019109948A1 (en) | 2017-12-07 | 2018-12-05 | Paas management method and device, and storage medium |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN109905258B (en) |
WO (1) | WO2019109948A1 (en) |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113127138B (en) * | 2019-12-31 | 2024-04-16 | 西安华为技术有限公司 | Virtualized network function deployment method, device and system |
CN111240868B (en) * | 2020-01-22 | 2024-04-02 | 阿里巴巴集团控股有限公司 | Instance processing and calling method, device, system and storage medium |
CN114040021B (en) * | 2021-11-05 | 2024-01-30 | 光大科技有限公司 | Development processing method and device for application program |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101794226A (en) * | 2010-03-08 | 2010-08-04 | 山东大学 | Service software construction method and system adapting to multiple business abstraction levels |
CN102333115A (en) * | 2011-09-01 | 2012-01-25 | 杭州湾云计算技术有限公司 | Method and device for transforming existing Web application into SaaS multi-tenant application |
CN103561310A (en) * | 2013-10-23 | 2014-02-05 | 深圳创维数字技术股份有限公司 | Method, device and system for data processing |
US8799898B2 (en) * | 2011-05-31 | 2014-08-05 | Adobe Systems Incorporated | Methods and apparatus for binding applications to a cloud computing environment |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9560078B2 (en) * | 2015-02-04 | 2017-01-31 | Intel Corporation | Technologies for scalable security architecture of virtualized networks |
CN105577779A (en) * | 2015-12-21 | 2016-05-11 | 用友网络科技股份有限公司 | Method and system for containerized deployment of large enterprise private cloud |
CN106254154B (en) * | 2016-09-19 | 2020-01-03 | 新华三技术有限公司 | Resource sharing method and device |
CN107404485B (en) * | 2017-08-02 | 2023-11-07 | 北京天翔睿翼科技有限公司 | Self-verification cloud connection method and system thereof |
-
2017
- 2017-12-07 CN CN201711288701.XA patent/CN109905258B/en active Active
-
2018
- 2018-12-05 WO PCT/CN2018/119367 patent/WO2019109948A1/en active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101794226A (en) * | 2010-03-08 | 2010-08-04 | 山东大学 | Service software construction method and system adapting to multiple business abstraction levels |
US8799898B2 (en) * | 2011-05-31 | 2014-08-05 | Adobe Systems Incorporated | Methods and apparatus for binding applications to a cloud computing environment |
CN102333115A (en) * | 2011-09-01 | 2012-01-25 | 杭州湾云计算技术有限公司 | Method and device for transforming existing Web application into SaaS multi-tenant application |
CN103561310A (en) * | 2013-10-23 | 2014-02-05 | 深圳创维数字技术股份有限公司 | Method, device and system for data processing |
Also Published As
Publication number | Publication date |
---|---|
CN109905258A (en) | 2019-06-18 |
CN109905258B (en) | 2020-11-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10701139B2 (en) | Life cycle management method and apparatus | |
CN110569101B (en) | Method and device for managing container service | |
CN111385114B (en) | VNF service instantiation method and device | |
WO2020228838A1 (en) | Containerized vnf deployment method and related device | |
WO2018024059A1 (en) | Method and device for service deployment in virtualized network | |
JP6614340B2 (en) | Network function virtualization management orchestration device, method and program | |
CN108984266B (en) | Virtual machine management method, device and system | |
EP3059900B1 (en) | Network service template management method and device | |
WO2018149263A1 (en) | Method and apparatus for instantiating network service | |
EP3584998B1 (en) | Method for virtual machine capacity expansion and reduction and virtual management device | |
WO2020103925A1 (en) | Method and apparatus for deploying containerization virtualized network function | |
WO2016121834A1 (en) | Method, system, device, and program for managing network function virtualization | |
CN109428764B (en) | Virtual network function instantiation method | |
WO2019109948A1 (en) | Paas management method and device, and storage medium | |
WO2019129118A1 (en) | Vnf service instantiation method and device | |
CN111835679B (en) | Tenant resource management method and device under multi-tenant scene | |
US20230221997A1 (en) | System and method for subscription management using composed systems | |
WO2018184504A1 (en) | Virtual resource allocation method, nfvo, and system | |
WO2017041650A1 (en) | Method and device for extending distributed consistency service | |
CN112015515B (en) | Instantiation method and device of virtual network function | |
CN112889247B (en) | VNF service instantiation method and device | |
WO2018120222A1 (en) | Vnffg management method, device and system | |
CN111045778A (en) | Virtual machine creating method and device, server and storage medium | |
JP7472677B2 (en) | Virtual network function management device, management system, management method, and program | |
WO2022095027A1 (en) | A method, device and system of container cluster scaling |
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: 18886828 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: 18886828 Country of ref document: EP Kind code of ref document: A1 |