WO2023045552A1 - 服务部署方法、服务部署系统、电子设备及存储介质 - Google Patents

服务部署方法、服务部署系统、电子设备及存储介质 Download PDF

Info

Publication number
WO2023045552A1
WO2023045552A1 PCT/CN2022/108333 CN2022108333W WO2023045552A1 WO 2023045552 A1 WO2023045552 A1 WO 2023045552A1 CN 2022108333 W CN2022108333 W CN 2022108333W WO 2023045552 A1 WO2023045552 A1 WO 2023045552A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
cloud platform
deployment
service deployment
type
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/108333
Other languages
English (en)
French (fr)
Inventor
施捷
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of WO2023045552A1 publication Critical patent/WO2023045552A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
    • 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
    • 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/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
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services

Definitions

  • the present application relates to the technical field of cloud platform service deployment, and in particular to a service deployment method, a service deployment system, electronic equipment, and a storage medium.
  • IAAS Infrastructure as a Service
  • PAAS Platform as a Service
  • users evaluate and screen multiple cloud platform service types through manual evaluation to select the target cloud platform service type.
  • the above method not only requires a long evaluation implementation cycle, but also is prone to evaluation errors during the evaluation process, which will affect the service launch process.
  • Embodiments of the present application provide a service deployment method, a service deployment system, electronic equipment, and a storage medium.
  • the embodiment of the present application provides a service deployment method, including: acquiring a service deployment type and a service deployment condition; determining a plurality of candidate cloud platform service types according to the service deployment type; wherein, the candidate cloud platform service The type includes candidate resource information; from the candidate cloud platform service types, it is determined that the candidate cloud platform service type whose candidate resource information meets the service deployment condition is the target cloud platform service type.
  • the embodiment of the present application also provides a service deployment system, including: an acquisition module configured to acquire the service deployment type and service deployment conditions; a service deployment module configured to determine multiple candidate clouds according to the service deployment type Platform service type; wherein, the candidate cloud platform service type includes candidate resource information; and is configured to, from the candidate cloud platform service types, determine the candidate cloud platform whose candidate resource information meets the service deployment condition
  • the service type is the target cloud platform service type.
  • the embodiment of the present application further provides an electronic device, including: at least one processor; at least one memory configured to store at least one program; when the at least one program is executed by the at least one processor, The at least one processor is made to implement the service deployment method as described in the first aspect.
  • the embodiment of the present application also provides a computer-readable storage medium, which stores processor-executable instructions, wherein the processor-executable instructions are used to implement the following when executed by a processor: The service deployment method described in the second aspect.
  • FIG. 1 is a schematic flow chart of a service deployment method provided by an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a service deployment method provided by another embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a service deployment method provided by another embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a service deployment method provided by another embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a service deployment system provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of the workflow of the service deployment system provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of the workflow of the service deployment system provided by another embodiment of the present application.
  • FIG. 8 is a schematic diagram of a hardware structure of an electronic device provided by an embodiment of the present application.
  • Cloud platform also known as cloud computing management system, refers to a one-stop service that realizes the full service cycle by building IAAS (Infrastructure as a Service), PAAS (Platform as a Service) and SAAS (Software as a Service), forming a multi-level , All-round cloud computing management system.
  • IAAS Infrastructure as a Service
  • PAAS Plate as a Service
  • SAAS Software as a Service
  • IAAS Infrastructure as a Service
  • PAAS Platform as a Service
  • SAAS Software as a Service
  • Users do not need to purchase software, but can rent web-based software from the provider to manage the business activities of cloud enterprises.
  • NFV Network Function Virtualization
  • the operation and maintenance personnel After the operation and maintenance personnel obtain the above information, they calculate and evaluate the overall planning of service deployment, utilization rate and other factors, and finally determine the service deployment platform and method (that is, determine the cloud platform service type).
  • the above evaluation process requires a long evaluation cycle, and human evaluation errors are prone to occur during the evaluation process, which will affect the service launch process.
  • the embodiment of the present application proposes a service deployment method, a service deployment system, an electronic device, and a storage medium, which can be based on the service deployment type and service deployment conditions, as well as the resource conditions of various cloud platform service types provided by the cloud platform , calculate the cloud platform service type that is suitable for the service to be deployed, thereby avoiding the risk of error in manual evaluation, and thus speeding up the service launch process to a certain extent.
  • the embodiment of the present application provides a service deployment method
  • the service deployment method includes steps:
  • the service deployment requirement model imported by the user through interface design or communication transmission methods such as ports, and trigger the service deployment strategy generation step according to the service deployment requirement model, so as to obtain the service deployment requirement model that matches the service deployment requirement model according to the service deployment strategy generation step Cloud platform service type, and then perform service deployment operations on the adapted cloud platform service type according to the service deployment requirement model.
  • the cloud platform service type adaptation process of the service to be deployed is completed, as well as the service deployment operation when the service goes online.
  • the step of generating a service deployment policy includes: parsing the service deployment requirement model to obtain the service deployment type and service deployment conditions.
  • the service deployment type indicates the cloud platform service type supported by the service to be deployed;
  • the service deployment condition indicates the filter condition correspondingly generated according to the service deployment requirements of the service to be deployed.
  • the undetermined cloud platform service types provided by the cloud platform are screened according to the service deployment type to obtain multiple candidate cloud platform service types.
  • the candidate cloud platform service type includes candidate resource information.
  • the candidate resource information corresponding to multiple candidate types is screened to obtain the candidate cloud platform service types that meet the service deployment conditions, and the selected candidate cloud platform service types are marked as the target cloud platform service types, so that Perform a service deployment operation on the service to be deployed according to the service type of the target cloud platform.
  • the target cloud platform service type suitable for the service to be deployed is selected from the multiple undetermined cloud platform service types provided by the cloud platform according to the service deployment type and service deployment conditions, so that the target cloud platform service type can be selected according to the The service type of the target cloud platform performs a service deployment operation on the service to be deployed. Therefore, the above-mentioned embodiments of the present application can realize the rapid deployment of the service to be deployed, and avoid the risk of manual evaluation errors, thereby speeding up the process of launching the service to a certain extent.
  • step S110 includes sub-steps:
  • the service deployment type is parsed from the service deployment requirement model, that is, the cloud platform service type supported by the service to be deployed is parsed. Obtain multiple pending cloud platform service types in the connected platform, and filter multiple pending cloud platform service types according to the service deployment type to filter out the pending cloud platform service types that match the service deployment type, and filter out The undetermined cloud platform service type of is marked as the candidate cloud platform service type.
  • “matching" in this embodiment of the present application means that the service provided by the selected candidate cloud platform service type is the same as the service represented by the service deployment type, and/or means that the selected candidate cloud platform service type The scope of the service provided is greater than that indicated by the service deployment type.
  • performance screening needs to be performed according to the service deployment requirements of the service to be deployed, so as to screen out infrastructure, existing remaining resources, and other eligible services from multiple candidate cloud platform service types Deploy the required candidate cloud platform service type, and mark the selected candidate cloud platform service type as the target cloud platform service type, and then perform service deployment operations on the service to be deployed according to the target cloud platform service type.
  • the screening of candidate cloud platform service types will be described in detail in combination with the features of the above-mentioned embodiments.
  • the service deployment condition includes a capacity requirement condition, wherein the capacity requirement condition includes at least one of virtual machine resources, port resources, network bandwidth resources, disk resources, or image resources not less than a preset requirement resource threshold .
  • step S130 includes a sub-step: from the candidate cloud platform service types, determine the candidate cloud platform service type whose resource information meets the capacity requirement condition as the target cloud platform service type.
  • the service deployment condition indicates the filter condition correspondingly generated according to the service deployment requirement of the service to be deployed, that is, the service deployment requirement includes the capacity deployment requirement, and the capacity deployment requirement includes at least A sort of.
  • obtain candidate resource information corresponding to the above service deployment requirements for example: for IAAS (Infrastructure as a Service), the obtained candidate resource information includes virtual machine information, port information, network bandwidth information, disk Information and mirroring information, etc.; for CAAS (communication as a service), the obtained candidate resource information Boakai mirroring information, etc.
  • the candidate resource information of different candidate cloud platform service types is judged to be consistent with the service deployment conditions, and the candidate cloud platform service types that can support the deployment requirements of the service capacity to be deployed are selected, and the selected candidate cloud platform service types are calibrated It is the target cloud platform service type.
  • Step S130 includes sub-steps:
  • the operating environment condition is that at least one of the service reliability index, service importance index, resource sharing level or resource isolation index is not lower than the preset operating environment threshold.
  • the service deployment condition indicates the filtering condition correspondingly generated according to the service deployment requirement of the service to be deployed, that is, the service deployment requirement includes the operating environment deployment requirement and the capacity deployment requirement.
  • Operating environment deployment requirements include at least one of service reliability indicators, service importance indicators, resource sharing levels, or resource isolation indicators; capacity deployment requirements include virtual machine resources, port resources, network bandwidth resources, disk resources, or mirror resources. at least one. Obtain candidate resource information corresponding to the above-mentioned operating environment deployment requirements, so as to filter out the calibrated cloud platform service type from multiple candidate cloud platform service types.
  • the service reliability index represents the evaluation index generated according to the data jitter and request packet loss of the candidate cloud platform service type
  • the service importance index represents the server level to which the candidate cloud platform service type belongs, and the level of the computer room to which the server belongs (including core computer room and basic computer room, etc.), server location (including core location and basic location, etc.), server maintainability and other evaluation indicators generated
  • resource sharing level indicates the sharing attribute according to the candidate cloud platform service type (including Shareable and non-shareable) and other evaluation indicators generated
  • resource isolation indicators represent the evaluation indicators generated according to the exclusivity of candidate cloud platform service types, physical nodes, container nodes, etc.
  • the above-mentioned evaluation indicators can include first-level, second-level, third-level, etc., and the higher the level, the more reliable, important, non-sharable and isolated the better.
  • the services to be deployed include payment services and product display services.
  • the core of the payment service is the security of payment and the reliability of payment data, that is, the payment service pays more attention to the monitoring, backup, disaster recovery and other functions of the candidate cloud platform service type.
  • the core of product display service is the stability of product display, that is, product display service pays more attention to data jitter and data packet loss of candidate cloud platform service types. Therefore, when the service to be deployed is a payment service, it is necessary to select the calibrated cloud platform service type with a higher service importance index from multiple candidate deployment types, that is, the service importance index should be selected to be greater than or equal to three levels, and the remaining indicators should be selected.
  • calibrated cloud platform service types that are less than three levels or not limited.
  • the service to be deployed is a commodity display service
  • the service reliability index should be selected to be greater than or equal to three levels
  • the remaining indicators Including service importance indicators, resource sharing level indicators, and resource isolation indicators
  • a higher operating environment threshold should be set for the resource sharing level and resource isolation index of the candidate cloud platform service type.
  • the target cloud platform service type is selected from multiple calibrated cloud platform service types according to the capacity requirement conditions, so that the service deployment operation is performed on the service to be deployed according to the target cloud platform service type.
  • the manner of screening out target cloud platform service types from multiple calibrated cloud platform service types according to capacity requirement conditions is the same as that of screening target cloud platform service types from multiple candidate deployment types according to capacity requirement conditions in the above embodiment
  • the types and methods are basically the same, so the embodiment of this application will not repeat them.
  • the service deployment method further includes the steps of:
  • a target cloud platform service type is screened out from a plurality of target cloud platform service types according to strategies such as preset priority (that is, the preset threshold Set to 1), and the filtered target cloud platform service type is marked as the operation cloud platform service type.
  • the service type of the operation cloud platform and the corresponding operation resource information are sent to the user through the interface, port, etc., thereby realizing the pre-operation of the service deployment operation, that is, only pre-judging which kind of undetermined cloud platform the service to be deployed will be deployed to Cloud platform service type, no final service deployment operation is performed.
  • the service deployment method further includes the step of: sending an instantiation request including an operation cloud platform service type to the virtual network function management module, so that the virtual network function management module performs service deployment operations according to the instantiation request.
  • the service deployment method provided by the embodiment of the present application is a deployment mechanism based on the NFV structure, that is, the deployment mechanism of the embodiment of the present application is established on NFVO (life cycle management unit or life cycle management module), VNFM (virtual network Function management module) already has the ability to manage resources for different types of cloud platform services. Therefore, after the pre-operation result (that is, the operation cloud platform service type) is returned to the user according to the above embodiment, the actual service deployment operation can also be performed.
  • NFVO life cycle management unit or life cycle management module
  • VNFM virtual network Function management module
  • an instantiation request is sent to the virtual network function management module, wherein the instantiation request carries the service deployment requirements described in the above embodiments and the selected operation cloud platform service type, so that the virtual network function management module can deploy the service according to the service deployment requirements Perform service deployment operations on the corresponding operation cloud platform service types on the cloud platform.
  • an embodiment of the present application provides a service deployment system.
  • the service deployment system includes an acquisition module 510 and a service deployment module 520 .
  • the obtaining module 510 is configured to obtain service deployment type and service deployment condition.
  • the service deployment module 520 is configured to determine a plurality of candidate cloud platform service types according to the service deployment type; wherein, the candidate cloud platform service types include candidate resource information; the service deployment module 520 is also configured to determine candidate cloud platform service types from the candidate cloud platform service types The candidate cloud platform service type whose resource information meets the service deployment conditions is the target cloud platform service type.
  • the acquisition module 510 acquires the service deployment requirement module imported by the user through interface design or communication transmission methods such as ports, and the service deployment module 520 triggers the service deployment strategy according to the service deployment requirement model Generation step, so as to obtain the cloud platform service type adapted to the service deployment requirement model according to the service deployment strategy generation step, and then perform service deployment operations on the adapted cloud platform service type according to the service deployment requirement model.
  • the cloud platform service type adaptation process of the service to be deployed is completed, as well as the service deployment operation when the service goes online.
  • the step of generating the service deployment strategy includes: the service deployment module 520 analyzes the service deployment requirement model to obtain the service deployment type and service deployment conditions.
  • the service deployment type indicates the cloud platform service type supported by the service to be deployed;
  • the service deployment condition indicates the filter condition correspondingly generated according to the service deployment requirements of the service to be deployed.
  • the undetermined cloud platform service types provided by the cloud platform are screened according to the service deployment type to obtain multiple candidate cloud platform service types.
  • the candidate cloud platform service type includes candidate resource information.
  • the candidate resource information corresponding to multiple candidate types is screened to obtain the candidate cloud platform service types that meet the service deployment conditions, and the selected candidate cloud platform service types are marked as the target cloud platform service types, so that Perform a service deployment operation on the service to be deployed according to the service type of the target cloud platform.
  • NFVO can be deployed integrated with the service deployment module (as shown in FIG. 6 ), or NFVO and the service deployment module can be deployed independently (as shown in FIG. 7 ).
  • the acquisition module, the service deployment module, and other modules of the service deployment system will be specifically described for these two embodiments and in combination with the service deployment method described in the above embodiments. It can be understood that, in addition to integrating with NFVO, the service deployment module can also be integrated with other systems such as OSS (service provider's management function).
  • OSS service provider's management function
  • the acquisition module includes a type acquisition unit, a capacity requirement acquisition unit, or includes a type acquisition unit, a capacity requirement acquisition unit, and an operating environment acquisition unit.
  • the service deployment module includes a deployment type confirmation unit and a lifecycle management unit (ie, NFVO).
  • the type obtaining unit is configured to obtain the service deployment type imported or designed by the user
  • the capacity requirement obtaining unit is configured to obtain the capacity requirement condition imported or designed by the user
  • the operating environment obtaining unit is configured to obtain the operating environment imported or designed by the user condition.
  • the deployment confirmation unit is configured to obtain multiple undetermined cloud platform service types that have been connected to the platform, and is configured to match the service deployment type parsed from the service deployment requirement model with the multiple undetermined cloud platform service types to A plurality of candidate cloud platform service types matching the service deployment type are determined among the plurality of undetermined cloud platform service types.
  • the deployment type confirming unit obtains candidate resource information, and compares the candidate resource information with the capacity requirement condition, so as to obtain a target cloud platform service type that meets the capacity requirement condition from multiple candidate cloud platform service types.
  • the acquisition module includes an operating environment acquisition unit, first compare the candidate resource information with the operating environment conditions, obtain the calibration cloud platform service type that meets the operating environment conditions from multiple candidate cloud platform service types, and then calibrate the cloud platform The calibration resource information of the service type is compared with the capacity requirement conditions to obtain the service type of the target cloud platform.
  • the deployment type confirmation unit is further configured to select an operational cloud platform service type from the multiple target cloud platform service types according to preset policies such as priority.
  • the life cycle management unit sends an instantiation request to the VNFM.
  • the instantiation request carries the service type of the operating cloud platform and the service deployment requirements corresponding to the services to be deployed, so that the VNFM can deploy the cloud platform according to the service deployment requirements.
  • the corresponding operation cloud platform service type in the service deployment operation is basically the same as the description of the service deployment method above, and will not be repeated here.
  • the service deployment module when NFVO and the service deployment module are independently deployed, the service deployment module includes a deployment type confirmation unit, and the service deployment system also includes NFVO (life cycle management module) and VNFM (virtual network function management module).
  • NFVO sends an instantiation request including the service deployment requirement model to the service deployment module, so that the deployment type confirmation unit parses the service deployment type and service deployment condition from the service deployment requirement model, and obtains the operation according to the service deployment method described in the above embodiment Cloud platform service type.
  • the NFVO is also configured to send an instantiation request including the operation cloud platform service type and service deployment requirements to the VNFM, so that the VNFM performs service deployment operations on the corresponding operation cloud platform service types in the cloud platform according to the service deployment requirements.
  • an embodiment of the present application provides an electronic device, the electronic device includes:
  • the processor 801 can be implemented by a general-purpose CPU (central processing unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is configured to execute related programs to implement the implementation of the present application.
  • a general-purpose CPU central processing unit
  • ASIC application-specific integrated circuit
  • the memory 802 may be implemented in the form of a ROM (read only memory), a static storage device, a dynamic storage device, or a RAM (random access memory).
  • the memory 802 can store operating systems and other application programs.
  • the relevant program codes are stored in the memory 802 and called by the processor 801 to execute the implementation of the present application. example service deployment method;
  • the input/output interface 803 is configured to realize information input and output
  • the communication interface 804 is configured to realize the communication interaction between the device and other devices, and the communication can be realized through a wired method (such as USB, network cable, etc.), or can be realized through a wireless method (such as a mobile network, Wi-Fi, Bluetooth, etc.) ;and
  • a bus 805 which transmits information between various components of the device (such as a processor 801, a memory 802, an input/output interface 803, and a communication interface 804);
  • the processor 801 , the memory 802 , the input/output interface 803 and the communication interface 804 are connected to each other within the device through the bus 805 .
  • the embodiment of the present application also provides a storage medium, the storage medium is a computer-readable storage medium, and the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to cause a computer to execute the above service deployment method.
  • memory can be used to store non-transitory software programs and non-transitory computer-executable programs.
  • the memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage devices.
  • the memory may include memory located remotely from the processor, which remote memory may be connected to the processor through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the service deployment method, service deployment system, electronic device, and storage medium provided in the embodiments of the present application select and select the services to be deployed from the multiple undetermined cloud platform service types provided by the cloud platform according to the service deployment type and service deployment conditions.
  • the matching target cloud platform service type so that the service deployment operation can be performed on the service to be deployed according to the target cloud platform service type. Therefore, according to the above-mentioned embodiment, the present application can realize the rapid deployment of the service to be deployed, and avoid the risk of manual evaluation errors, thereby speeding up the process of launching the service to a certain extent.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种服务部署方法、服务部署系统、电子设备及存储介质，该服务部署方法包括：获取服务部署类型和服务部署条件（S110）；根据所述服务部署类型确定多个候选云平台服务类型（S120）；其中，所述候选云平台服务类型包括候选资源信息；从所述候选云平台服务类型中，确定所述候选资源信息符合所述服务部署条件的所述候选云平台服务类型为目标云平台服务类型（S130）。

Description

服务部署方法、服务部署系统、电子设备及存储介质
相关申请的交叉引用
本申请基于申请号为202111136324.4、申请日为2021年09月27日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及云平台服务部署技术领域，尤其涉及一种服务部署方法、服务部署系统、电子设备及存储介质。
背景技术
目前，为了满足用户定制化、差异化的服务需求，运营商会在云平台上同时提供IAAS(基础设施即服务)、PAAS(平台即服务)等多种云平台服务类型。
在一些情形下，根据服务部署需求，用户通过人工评估的方式对多种云平台服务类型进行评估筛选，以选取出目标云平台服务类型。然而，上述方法不仅需要较长的评估实施周期，而且在评估过程中容易出现评估误差，从而对服务上线进程造成影响。
发明内容
本申请实施例提供了一种服务部署方法、服务部署系统、电子设备及存储介质。
第一方面，本申请实施例提供了一种服务部署方法，包括：获取服务部署类型和服务部署条件；根据所述服务部署类型确定多个候选云平台服务类型；其中，所述候选云平台服务类型包括候选资源信息；从所述候选云平台服务类型中，确定所述候选资源信息符合所述服务部署条件的所述候选云平台服务类型为目标云平台服务类型。
第二方面，本申请实施例还提供了一种服务部署系统，包括：获取模块，被配置为获取服务部署类型和服务部署条件；服务部署模块，被配置为根据服务部署类型确定多个候选云平台服务类型；其中，所述候选云平台服务类型包括候选资源信息；并被配置为从所述候选云平台服务类型中，确定所述候选资源信息符合所述服务部署条件的所述候选云平台服务类型为目标云平台服务类型。
第三方面，本申请实施例还提供了一种电子设备，包括：至少一个处理器；至少一个存储器，被配置为存储至少一个程序；当所述至少一个程序被所述至少一个处理器执行，使得所述至少一个处理器实现如第一方面所述的服务部署方法。
第四方面，本申请实施例还提供了一种计算机可读存储介质，其中存储有处理器可执行指令，其特征在于，所述处理器可执行的指令在由处理器执行时用于实现如第二方面所述的服务部署方法。
附图说明
图1是本申请一实施例提供的服务部署方法流程示意图；
图2是本申请另一实施例提供的服务部署方法流程示意图；
图3是本申请另一实施例提供的服务部署方法流程示意图；
图4是本申请另一实施例提供的服务部署方法流程示意图；
图5是本申请一实施例提供的服务部署系统结构示意图；
图6是本申请一实施例提供的服务部署系统工作流程示意图；
图7是本申请另一实施例提供的服务部署系统工作流程示意图；
图8是本申请一实施例提供的电子设备硬件结构示意图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
需要说明的是，虽然在装置示意图中进行了功能模块划分，在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于装置中的模块划分，或流程图中的顺序执行所示出或描述的步骤。说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
对本申请进行进一步详细说明之前，对本申请实施例中涉及的名词和术语进行说明，本申请实施例中涉及的名词和术语适用于如下解释。
云平台，也称为云计算管理系统，是指通过构建IAAS(基础设施即服务)、PAAS(平台即服务)和SAAS(软件即服务)来实现全服务周期的一站式服务，形成多层级、全方位的云计算管理系统。
其中，IAAS(基础设施即服务)是指用户通过网络可以从完善的计算机基础设施获得服务；PAAS(平台即服务)是指将软件研发的平台作为一种服务，以SAAS的模式提交给用户；SAAS(软件即服务)是指通过网络提供软件的模式，用户无需购买软件，而可以向提供商租用基于Web的软件来管理上云企业的经营活动。
NFV(网络功能虚拟化)，是使用虚拟化技术的网络结构概念，将整个类别的网络节点功能虚拟化为构建可以连接或链接在一起的通信服务。
在一些情形下，为了实现对待部署服务的服务部署操作，一方面需要考虑待部署服务本身的服务部署需求，另一方面需要评估云平台上不同云平台服务类型的能力、资源使用情况等，以得到适配待部署服务的最优云平台服务类型。例如，某地区需要完成某第三方厂商的服务部署，通常情况下需要人工确认以下内容：
1.服务部署的运维方式，以及相关平台的适配情况；
2.待部署服务的基础设施需求，以及相关平台的支持能力；
3.相关平台现有剩余资源情况，是否能够支撑待部署服务的服务部署操作，以及是否需要手工扩容或进行其他处理等。
运维人员获得上述信息后，结合服务部署整体规划、利用率等因素进行计算和评估，最终确定服务部署平台和方式(即确定云平台服务类型)。但是，上述评估过程需要花费较长的评估周期，且评估过程中容易出现人为评估误差，从而对服务上线进程造成影响。
基于此，本申请实施例提出了一种服务部署方法、服务部署系统、电子设备及存储介质， 能够根据服务部署类型和服务部署条件，以及云平台所提供的多种云平台服务类型的资源情况，计算得到与待部署服务相适配的云平台服务类型，从而避免了人工评估的错误风险，进而在一定程度上加快了服务上线进程。
参照图1，本申请实施例提供了一种服务部署方法，该服务部署方法包括步骤：
S110、获取服务部署类型和服务部署条件；
S120、根据服务部署类型确定多个候选云平台服务类型；
S130、从候选云平台服务类型中，确定候选资源信息符合服务部署条件的候选云平台服务类型为目标云平台服务类型。
获取用户通过界面设计、或通过端口等通信传输方式导入的服务部署需求模型，根据该服务部署需求模型触发服务部署策略生成步骤，从而根据服务部署策略生成步骤得到与服务部署需求模型相适配的云平台服务类型，进而根据服务部署需求模型对适配得到的云平台服务类型进行服务部署操作。以上，即完成了一次对待部署服务的云平台服务类型适配过程，以及服务上线时的服务部署操作。
在一些实施例中，服务部署策略生成步骤包括：对服务部署需求模型进行解析，以得到服务部署类型和服务部署条件。其中，服务部署类型表示待部署服务支持的云平台服务类型；服务部署条件表示根据待部署服务的服务部署需求对应生成的筛选条件。根据服务部署类型对云平台所提供的待定云平台服务类型进行筛选，以得到多个候选云平台服务类型。其中，候选云平台服务类型包括候选资源信息。根据服务部署条件对多个候选类型对应的候选资源信息进行筛选，以得到符合服务部署条件的候选云平台服务类型，将筛选出的候选云平台服务类型标定为目标云平台服务类型，从而即可根据该目标云平台服务类型对待部署服务进行服务部署操作。
本申请上述实施例中，根据服务部署类型和服务部署条件从云平台所提供的多个待定云平台服务类型中，筛选出与待部署服务相适配的目标云平台服务类型，从而即可根据该目标云平台服务类型对待部署服务进行服务部署操作。因此，本申请上述实施例能够实现对待部署服务的快速部署，并避免人工评估错误的风险，进而在一定程度上加快了服务上线进程。
参照图2，在一些实施例中，步骤S110包括子步骤：
S210、获取多个待定云平台服务类型；
S220、将服务部署类型与多个待定云平台服务类型进行匹配操作，在多个待定云平台服务类型中确定与服务部署类型相匹配的多个候选云平台服务类型。
从服务部署需求模型中解析得到服务部署类型，即解析得到待部署服务支持的云平台服务类型。获取已接入平台中的多个待定云平台服务类型，根据服务部署类型对多个待定云平台服务类型进行筛选，以筛选出与服务部署类型相匹配的待定云平台服务类型，并将筛选出的待定云平台服务类型标定为候选云平台服务类型。可以理解的是，本申请实施例中“相匹配”表示筛选出的候选云平台服务类型所提供的服务与服务部署类型所表示的服务相同，和/或表示筛选出的候选云平台服务类型所提供的服务范围大于服务部署类型所表示的服务范围。
根据上述实施例将候选云平台服务类型筛选出后，还需根据待部署服务的服务部署需求进行性能筛选，以从多个候选云平台服务类型中筛选出基础设施、现有剩余资源等符合服务部署需求的候选云平台服务类型，并将筛选出的候选云平台服务类型标定为目标云平台服务类型，进而根据该目标云平台服务类型对待部署服务进行服务部署操作。以下，结合上述实 施例的特征，对候选云平台服务类型的筛选进行具体说明。
在一些实施例中，服务部署条件包括容量需求条件，其中，容量需求条件包括虚拟机资源、端口资源、网络带宽资源、磁盘资源或镜像资源中的至少一种不少于预设的需求资源阈值。
在一些实施例中，步骤S130包括子步骤：从候选云平台服务类型中，确定候选资源信息符合容量需求条件的候选云平台服务类型为目标云平台服务类型。服务部署条件表示根据待部署服务的服务部署需求对应生成的筛选条件，即服务部署需求包括容量部署需求，容量部署需求包括虚拟机资源、端口资源、网络带宽资源、磁盘资源或镜像资源中的至少一种。根据候选云平台服务类型的不同，获取与上述服务部署需求对应的候选资源信息，例如：对于IAAS(基础设施即服务)，获取的候选资源信息包括虚拟机信息、端口信息、网络带宽信息、磁盘信息和镜像信息等；对于CAAS(通信即服务)，获取的候选资源信息博阿凯镜像信息等。将不同的候选云平台服务类型的候选资源信息分别与服务部署条件进行符合性判断，筛选出能够支持待部署服务容量部署需求的候选云平台服务类型，并将筛选出的候选云平台服务类型标定为目标云平台服务类型。
参照图3，在另一些实施例中，服务部署条件包括运行环境条件和容量需求条件。步骤S130包括子步骤：
S310、从候选云平台服务类型中，确定候选资源信息符合运行环境条件的候选云平台服务类型为标定云平台服务类型；
S320、从标定云平台服务类型中，确定标定资源信息符合容量需求条件的标定云平台服务类型为目标云平台服务类型。
其中，运行环境条件为服务可靠性指标、服务重要性指标、资源共享等级或资源隔离指标中的至少一种不低于预设的运行环境阈值。
服务部署条件表示根据待部署服务的服务部署需求对应生成的筛选条件，即服务部署需求包括运行环境部署需求和容量部署需求。运行环境部署需求包括服务可靠性指标、服务重要性指标、资源共享等级或资源隔离指标中的至少一种；容量部署需求包括虚拟机资源、端口资源、网络带宽资源、磁盘资源或镜像资源中的至少一种。获取与上述运行环境部署需求对应的候选资源信息，以从多个候选云平台服务类型中筛选出标定云平台服务类型。
其中，服务可靠性指标表示根据候选云平台服务类型的数据抖动情况、请求丢包情况等生成的评价指标；服务重要性指标表示根据候选云平台服务类型所归属的服务器级别、服务器所属机房的级别(包括核心机房和基础机房等)、服务器所处地段(包括核心地段和基础地段等)、服务器的可维护性等生成的评价指标；资源共享等级表示根据候选云平台服务类型的共享属性(包括可共享和不可共享)等生成的评价指标；资源隔离指标表示根据候选云平台服务类型的可独占性、物理节点、容器节点等生成的评价指标。其中，上述评价指标均可包括一级、二级、三级等，等级越高表示越可靠、越重要、不可共享和隔离性越好。
以电商领域为例，待部署服务包括支付服务和商品展示服务两种类型。其中，支付服务的核心为支付的安全性，以及支付数据的可靠性，即支付服务更关注候选云平台服务类型的监听、备份、容灾等功能。商品展示服务的核心为商品展示的稳定性，即商品展示服务更关注候选云平台服务类型的数据抖动、数据丢包等情况。因此，当待部署服务为支付服务时，需从多个候选部署类型中筛选出服务重要性指标更高的标定云平台服务类型，即应选取出服 务重要性指标大于或等于三级、其余指标(包括服务可靠性指标、资源共享等级指标、资源隔离指标)为小于三级或不作限定的标定云平台服务类型。当待部署服务为商品展示服务时，需从多个候选部署类型中筛选出服务可靠性指标更高的标定云平台服务类型，即应选取出服务可靠性指标大于或等于三级、其余指标(包括服务重要性指标、资源共享等级指标、资源隔离指标)为小于三级或不作限定的标定云平台服务类型。
其次，对于不同的服务部署需求，当待部署服务需要对服务器进行独占时，应对候选云平台服务类型的资源共享等级和资源隔离指标设置更高的运行环境阈值，即应从候选云平台服务类型中选取出资源共享等级、资源隔离指标均大于或等于三级的标定云平台服务类型。可以理解的是，上述实施例中所描述的运行环境条件和容量需求条件的具体内容，以及所列举的服务可靠性指标、服务重要性指标、资源共享等级、资源隔离指标的具体内容仅为示例性的，本申请实施例对此不作具体限定。
根据上述描述，从多个候选云平台服务类型中筛选出符合待部署服务性能、资源、基础设施等条件的标定云平台服务类型。而后，根据容量需求条件从多个标定云平台服务类型中筛选出目标云平台服务类型，从而根据目标云平台服务类型对待部署服务进行服务部署操作。可以理解的是，根据容量需求条件从多个标定云平台服务类型中筛选出目标云平台服务类型的方式，与上述实施例中根据容量需求条件从多个候选部署类型中筛选中目标云平台服务类型的方式基本一致，因此本申请实施例不再赘述。
参照图4，在一些实施例中，服务部署方法还包括步骤：
S410、确定目标云平台服务类型的数量；
S420、若目标云平台服务类型的数量大于预设阈值，对目标云平台服务类型进行筛选，得到操作云平台服务类型。
当根据上述实施例筛选出的目标云平台服务类型的数量包括多个时，根据预设的优先级等策略从多个目标云平台服务类型中筛选出一个目标云平台服务类型(即将预设阈值设定为1)，并筛选出的目标云平台服务类型标定为操作云平台服务类型。将该操作云平台服务类型以及对应的操作资源信息通过界面、端口等方式发送给用户，从而实现了服务部署操作的预操作，即只预先判断待部署服务会部署至云平台中的哪种待定云平台服务类型，不进行最终的服务部署操作。
在一些实施例中，服务部署方法还包括步骤：向虚拟网络功能管理模块发送包括操作云平台服务类型的实例化请求，使得虚拟网络功能管理模块根据实例化请求进行服务部署操作。
需要说明的是，本申请实施例所提供的服务部署方法为基于NFV结构的部署机制，即本申请实施例的部署机制建立在NFVO(生命周期管理单元或生命周期管理模块)、VNFM(虚拟网络功能管理模块)已经具备对不同云平台服务类型进行资源管理能力的基础上。因此，当根据上述实施例向用户回传预操作结果(即回传操作云平台服务类型)后，还可以进行实际的服务部署操作。即向虚拟网络功能管理模块发送实例化请求，其中，实例化请求携带有上述实施例所描述的服务部署需求和筛选出的操作云平台服务类型，以使虚拟网络功能管理模块根据该服务部署需求对云平台上对应的操作云平台服务类型进行服务部署操作。
以下，对本申请实施例所提供的服务部署方法与NFV结构的结合进行具体说明。
参照图5，本申请实施例提供了一种服务部署系统。该服务部署系统包括获取模块510和服务部署模块520。获取模块510被配置为获取服务部署类型和服务部署条件。服务部署 模块520被配置为根据服务部署类型确定多个候选云平台服务类型；其中，候选云平台服务类型包括候选资源信息；服务部署模块520还被配置为从候选云平台服务类型中，确定候选资源信息符合服务部署条件的候选云平台服务类型为目标云平台服务类型。
参照图5和图6，在一些实施例中，获取模块510获取用户通过界面设计、或通过端口等通信传输方式导入的服务部署需求模块，服务部署模块520根据该服务部署需求模型触发服务部署策略生成步骤，从而根据服务部署策略生成步骤得到与服务部署需求模型相适配的云平台服务类型，进而根据服务部署需求模型对适配得到的云平台服务类型进行服务部署操作。以上，即完成了一次对待部署服务的云平台服务类型适配过程，以及服务上线时的服务部署操作。
服务部署策略生成步骤包括：服务部署模块520对服务部署需求模型进行解析，以得到服务部署类型和服务部署条件。其中，服务部署类型表示待部署服务支持的云平台服务类型；服务部署条件表示根据待部署服务的服务部署需求对应生成的筛选条件。根据服务部署类型对云平台所提供的待定云平台服务类型进行筛选，以得到多个候选云平台服务类型。其中，候选云平台服务类型包括候选资源信息。根据服务部署条件对多个候选类型对应的候选资源信息进行筛选，以得到符合服务部署条件的候选云平台服务类型，将筛选出的候选云平台服务类型标定为目标云平台服务类型，从而即可根据该目标云平台服务类型对待部署服务进行服务部署操作。
在一些实施例中，NFVO可以与服务部署模块进行集成部署(如图6所示)，或NFVO和服务部署模块进行独立部署(如图7所示)。以下，针对这两种实施例，并结合上述实施例所描述的服务部署方法，对获取模块、服务部署模块，以及服务部署系统的其他模块进行具体说明。可以理解的是，服务部署模块除与NFVO集成以外，还可以与OSS(服务提供商的管理功能)等其他系统进行集成。
参照图6，在一些实施例中，获取模块包括类型获取单元、容量需求获取单元，或包括类型获取单元、容量需求获取单元和运行环境获取单元。当NFVO与服务部署模块进行集成部署时，服务部署模块包括部署类型确认单元和生命周期管理单元(即NFVO)。其中，类型获取单元被配置为获取用户导入或设计的服务部署类型，容量需求获取单元被配置为获取用户导入或设计的容量需求条件，运行环境获取单元被配置为获取用户导入或设计的运行环境条件。部署确认单元被配置为获取已接入平台的多个待定云平台服务类型，并被配置为将从服务部署需求模型中解析得到的服务部署类型与多个待定云平台服务类型进行匹配处理，以在多个待定云平台服务类型中确定与服务部署类型相匹配的多个候选云平台服务类型。
而后，部署类型确认单元获取候选资源信息，并将候选资源信息与容量需求条件进行比较，以从多个候选云平台服务类型中得到符合容量需求条件的目标云平台服务类型。或，当获取模块包括运行环境获取单元时，先将候选资源信息与运行环境条件进行比较，从多个候选云平台服务类型中得到符合运行环境条件的标定云平台服务类型，再将标定云平台服务类型的标定资源信息与容量需求条件进行比较，以得到目标云平台服务类型。当筛选出的目标云平台服务类型包括多个时，部署类型确认单元还被配置为根据预设的优先级等策略从多个目标云平台服务类型中筛选出一个操作云平台服务类型。将该操作云平台服务类型传回至界面或端口，并进一步传回给用户，从而完成一次预操作，即只预先判断待部署服务会部署至云平台中的哪种待定云平台服务类型，不进行最终的服务部署操作。当需进行服务部署操作 中，生命周期管理单元向VNFM发送实例化请求，该实例化请求携带有操作云平台服务类型和待部署服务对应的服务部署需求，以使VNFM根据服务部署需求对云平台中对应的操作云平台服务类型进行服务部署操作。可以理解的是，运行环境条件、容量需求条件的比较方法与上述服务部署方法的描述基本一致，在此不再赘述。
参照图7，与上述实施例相区别的是，当NFVO与服务部署模块进行独立部署时，服务部署模块包括部署类型确认单元，服务部署系统还包括NFVO(生命周期管理模块)和VNFM(虚拟网络功能管理模块)。NFVO向服务部署模块发送包括服务部署需求模型的实例化请求，使得部署类型确认单元从服务部署需求模型中解析得到服务部署类型和服务部署条件，并根据上述实施例所描述的服务部署方法得到操作云平台服务类型。NFVO还被配置为向VNFM发送包括操作云平台服务类型和服务部署需求的实例化请求，以使VNFM根据服务部署需求对云平台中对应的操作云平台服务类型进行服务部署操作。
参照图8，本申请实施例提供了一种电子设备，电子设备包括：
处理器801，可以采用通用的CPU(中央处理器)、微处理器、应用专用集成电路(ASIC)、或者一个或多个集成电路等方式实现，被配置为执行相关程序，以实现本申请实施例所提供的技术方案；
存储器802，可以采用ROM(只读存储器)、静态存储设备、动态存储设备或者RAM(随机存取存储器)等形式实现。存储器802可以存储操作系统和其他应用程序，在通过软件或者固件来实现本申请实施例所提供的技术方案时，相关的程序代码保存在存储器802中，并由处理器801来调用执行本申请实施例的服务部署方法；
输入/输出接口803，被配置为实现信息输入及输出；
通信接口804，被配置为实现本设备与其他设备的通信交互，可以通过有线方式(例如USB、网线等)实现通信，也可以通过无线方式(例如移动网络、Wi-Fi、蓝牙等)实现通信；和
总线805，在设备的各个组件(例如处理器801、存储器802、输入/输出接口803和通信接口804)之间传输信息；
其中处理器801、存储器802、输入/输出接口803和通信接口804通过总线805实现彼此之间在设备内部的通信连接。
本申请实施例还提供了一种存储介质，该存储介质是计算机可读存储介质，该计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令用于使计算机执行上述服务部署方法。
存储器作为一种非暂态计算机可读存储介质，可用于存储非暂态软件程序以及非暂态性计算机可执行程序。此外，存储器可以包括高速随机存取存储器，还可以包括非暂态存储器，例如至少一个磁盘存储器件、闪存器件、或其他非暂态固态存储器件。在一些实施方式中，存储器可包括相对于处理器远程设置的存储器，这些远程存储器可以通过网络连接至该处理器。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本申请实施例所提供的服务部署方法、服务部署系统、电子设备及存储介质，根据服务部署类型和服务部署条件从云平台所提供的多个待定云平台服务类型中，筛选出与待部署服务相适配的目标云平台服务类型，从而即可根据该目标云平台服务类型对待部署服务进行服务部署操作。因此，本申请根据上述实施例能够实现对待部署服务的快速部署，并避免人工 评估错误的风险，进而在一定程度上加快了服务上线进程。
本申请实施例描述的实施例是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域技术人员可知，随着技术的演变和新应用场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
以上参照附图说明了本申请实施例的若干实施例，并非因此局限本申请实施例的权利范围。本领域技术人员不脱离本公开实施例的范围和实质内所作的任何修改、等同替换和改进，均应在本公开实施例的权利范围之内。

Claims (15)

  1. 服务部署方法，包括：
    获取服务部署类型和服务部署条件；
    根据所述服务部署类型确定多个候选云平台服务类型；其中，所述候选云平台服务类型包括候选资源信息；
    从所述候选云平台服务类型中，确定所述候选资源信息符合所述服务部署条件的所述候选云平台服务类型为目标云平台服务类型。
  2. 根据权利要1所述的服务部署方法，其中，所述根据所述服务部署类型确定多个候选云平台服务类型，包括：
    获取多个待定云平台服务类型；
    将所述服务部署类型与所述多个待定云平台服务类型进行匹配处理，在所述多个待定云平台服务类型中确定与所述服务部署类型相匹配的多个所述候选云平台服务类型。
  3. 根据权利要求2所述的服务部署方法，其中，所述服务部署条件包括容量需求条件；
    其中，所述容量需求条件为虚拟机资源、端口资源、网络带宽资源、磁盘资源或镜像资源中的至少一种不少于预设的需求资源阈值。
  4. 根据权利要求3所述的服务部署方法，其中，所述服务部署条件还包括运行环境条件；
    所述从所述候选云平台服务类型中，确定所述候选资源信息符合所述服务部署条件的所述候选云平台服务类型为目标云平台服务类型，包括：
    从所述候选云平台服务类型中，确定所述候选资源信息符合所述运行环境条件的所述候选云平台服务类型为标定云平台服务类型；其中，所述标定云平台服务类型包括标定资源信息；
    从所述标定云平台服务类型中，确定所述标定资源信息符合所述容量需求条件的所述标定云平台服务类型为所述目标云平台服务类型；
    其中，所述运行环境条件为服务可靠性指标、服务重要性指标、资源共享等级或资源隔离指标中的至少一种不低于预设的运行环境阈值。
  5. 根据权利要求1至4任一项所述的服务部署方法，其中，所述服务部署方法还包括：
    确定所述目标云平台服务类型的数量；
    若所述目标云平台服务类型的数量大于预设阈值，对所述目标云平台服务类型进行筛选，得到操作云平台服务类型；其中，所述操作云平台服务类型用于进行服务部署操作。
  6. 根据权利要求5所述的服务部署方法，其中，所述服务部署方法还包括：
    向虚拟网络功能管理模块发送包括所述操作云平台服务类型的实例化请求，使得所述虚拟网络功能管理模块根据所述实例化请求进行服务部署操作。
  7. 服务部署系统，包括：
    获取模块，被配置为获取服务部署类型和服务部署条件；
    服务部署模块，被配置为根据服务部署类型确定多个候选云平台服务类型；其中，所述候选云平台服务类型包括候选资源信息；并被配置为从所述候选云平台服务类型中，确定所述候选资源信息符合所述服务部署条件的所述候选云平台服务类型为目标云平台服务类型。
  8. 根据权利要求7所述的服务部署系统，其中，所述获取模块包括：类型获取单元，被 配置为获取所述服务部署类型；
    所述服务部署模块包括：部署类型确认单元，被配置为获取多个待定云平台服务类型；并被配置为将所述服务部署类型与所述多个待定云平台服务类型进行匹配处理，在所述多个待定云平台服务类型中确定与所述服务部署类型相匹配的多个所述候选云平台服务类型。
  9. 根据权利要求8所述的服务部署系统，其中，所述服务部署条件包括容量需求条件；
    所述获取模块还包括：容量需求获取单元，被配置为获取所述容量需求条件；其中，所述容量需求条件为虚拟机资源、端口资源、网络带宽资源、磁盘资源、镜像资源或容器资源中的至少一种不少于预设的需求资源阈值。
  10. 根据权利要求9所述的服务部署系统，其中，所述服务部署条件还包括运行环境条件；
    所述获取模块还包括：运行环境获取单元，被配置为获取所述运行环境条件；其中，所述运行环境条件为服务可靠性指标、服务重要性指标、资源共享等级或资源隔离指标中的至少一种不低于预设的运行环境阈值。
  11. 根据权利要求8至10任一项所述的服务部署系统，其中，所述服务部署模块还被配置为确定目标云平台服务类型的数量；若所述目标云平台服务类型的数量大于预设阈值，对所述目标云平台服务类型进行筛选，以得到操作云平台服务类型；其中，所述操作云平台服务类型用于进行服务部署操作。
  12. 根据权利要求11所述的服务部署系统，其中，所述服务部署模块还包括：生命周期管理单元，被配置为发送包括所述操作云平台服务类型的实例化请求；
    所述服务部署系统还包括：虚拟网络功能管理模块，被配置为根据所述实例化请求进行服务部署操作。
  13. 根据权利要求11所述的服务部署系统，其中，所述服务部署系统还包括：
    生命周期管理模块，被配置为发送包括所述操作云平台服务类型的实例化请求；
    虚拟网络功能管理模块，被配置为根据所述实例化请求进行服务部署操作。
  14. 电子设备，包括：
    至少一个处理器；
    至少一个存储器，被配置为存储至少一个程序；
    当所述至少一个程序被所述至少一个处理器执行，使得所述至少一个处理器实现如权利要求1至6中任一项所述的服务部署方法。
  15. 计算机可读存储介质，其中存储有处理器可执行指令，其中，所述处理器可执行的指令在由处理器执行时用于实现如权利要求1至6中任一项所述的服务部署方法。
PCT/CN2022/108333 2021-09-27 2022-07-27 服务部署方法、服务部署系统、电子设备及存储介质 Ceased WO2023045552A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111136324.4 2021-09-27
CN202111136324.4A CN115883310A (zh) 2021-09-27 2021-09-27 服务部署方法、服务部署系统、电子设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023045552A1 true WO2023045552A1 (zh) 2023-03-30

Family

ID=85720011

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/108333 Ceased WO2023045552A1 (zh) 2021-09-27 2022-07-27 服务部署方法、服务部署系统、电子设备及存储介质

Country Status (2)

Country Link
CN (1) CN115883310A (zh)
WO (1) WO2023045552A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116723114A (zh) * 2023-08-07 2023-09-08 国网信息通信产业集团有限公司 一种面向多云环境的多云接口适配方法
CN117155804A (zh) * 2023-10-27 2023-12-01 腾讯科技（深圳）有限公司 一种云服务器的部署方法及相关装置
WO2025020505A1 (zh) * 2023-07-24 2025-01-30 华为云计算技术有限公司 业务部署方法、云管理平台和相关装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106453646A (zh) * 2016-11-29 2017-02-22 上海有云信息技术有限公司 一种安全服务平台的资源调度方法和装置
CN109714423A (zh) * 2018-12-29 2019-05-03 浪潮电子信息产业股份有限公司 一种OpenStack部署方法、装置、设备及介质
CN111770477A (zh) * 2020-06-08 2020-10-13 中天通信技术有限公司 一种mec网络的保护资源的部署方法及相关装置
CN112583861A (zh) * 2019-09-27 2021-03-30 阿里巴巴集团控股有限公司 服务部署方法、资源配置方法、系统、装置及服务器
US20210112141A1 (en) * 2019-10-15 2021-04-15 Hewlett Packard Enterprise Development Lp Selecting a cloud service provider for deploying a cloud service

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106453646A (zh) * 2016-11-29 2017-02-22 上海有云信息技术有限公司 一种安全服务平台的资源调度方法和装置
CN109714423A (zh) * 2018-12-29 2019-05-03 浪潮电子信息产业股份有限公司 一种OpenStack部署方法、装置、设备及介质
CN112583861A (zh) * 2019-09-27 2021-03-30 阿里巴巴集团控股有限公司 服务部署方法、资源配置方法、系统、装置及服务器
US20210112141A1 (en) * 2019-10-15 2021-04-15 Hewlett Packard Enterprise Development Lp Selecting a cloud service provider for deploying a cloud service
CN111770477A (zh) * 2020-06-08 2020-10-13 中天通信技术有限公司 一种mec网络的保护资源的部署方法及相关装置

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025020505A1 (zh) * 2023-07-24 2025-01-30 华为云计算技术有限公司 业务部署方法、云管理平台和相关装置
CN116723114A (zh) * 2023-08-07 2023-09-08 国网信息通信产业集团有限公司 一种面向多云环境的多云接口适配方法
CN116723114B (zh) * 2023-08-07 2023-12-29 国网信息通信产业集团有限公司 一种面向多云环境的多云接口适配方法
CN117155804A (zh) * 2023-10-27 2023-12-01 腾讯科技（深圳）有限公司 一种云服务器的部署方法及相关装置
CN117155804B (zh) * 2023-10-27 2024-01-09 腾讯科技（深圳）有限公司 一种云服务器的部署方法及相关装置

Also Published As

Publication number Publication date
CN115883310A (zh) 2023-03-31

Similar Documents

Publication Publication Date Title
JP6686910B2 (ja) ネットワーク機能仮想化管理およびオーケストレーション方法と装置とプログラム
CN112513813B (zh) 在按需网络代码执行系统中执行辅助功能
US10554508B2 (en) Updating a topology graph representing a distributed computing system by monitoring predefined parameters with respect to predetermined performance threshold values and using predetermined rules to select a combination of application, storage and database server nodes to meet at least one service level objective (SLO)
CN105027108B (zh) 实例主机配置
US10545779B2 (en) Network functions virtualization management and orchestration method, network functions virtualization management and orchestration system, and program
WO2023045552A1 (zh) 服务部署方法、服务部署系统、电子设备及存储介质
EP2989543B1 (en) Method and device for updating client
US10630556B2 (en) Discovering and publishing device changes in a cloud environment
US10848366B2 (en) Network function management method, management unit, and system
EP3901770A1 (en) Method and device for instantiating virtualized network function
JP2016525757A (ja) 分散型クラウドにおける作業負荷移動に基づくプロファイルベースのｓｌａ保証
WO2017147800A1 (zh) 资源配置方法、虚拟网络功能管理器和网元管理系统
JP2017143452A (ja) 管理装置、および、ネットワークサービス管理方法
CN108074076A (zh) 基于esb的服务提供方法、装置、设备及可读存储介质
CN107491371A (zh) 一种监控部署的方法以及装置
CN110506257B (zh) 在云服务代理系统中创建和分配集成连接器的方法
US9021479B2 (en) Enforcing machine deployment zoning rules in an automatic provisioning environment
US10205545B2 (en) Resource creation method and apparatus
CN110933152B (zh) 一种预热方法、装置、系统及电子设备
CN109076027B (zh) 网络服务请求
CN114579398A (zh) 一种日志的存储方法、装置、设备及存储介质
CN105519055A (zh) 一种I/O通道QoS动态均衡方法及装置
US20210286819A1 (en) Method and System for Operation Objects Discovery from Operation Data
US20200244531A1 (en) System and method for out of the box solution-level configuration and diagnostic logging and reporting
CN114816520B (zh) 流程处理方法、装置及网络设备

Legal Events

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

Ref document number: 22871610

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

Country of ref document: EP

Kind code of ref document: A1