A service construction method, related device and computer readable storage medium

By providing a combination of visual orchestration and approval processes for multiple service components in the cloud computing framework, the cumbersome problem of cloud service construction process is solved, efficiency and user experience are improved, and the enterprise organization process is adapted to.

CN114268659BActive Publication Date: 2024-11-29HUAWEI CLOUD COMPUTING TECHNOLOGIES CO LTD
View PDF 12 Cites 0 Cited by

Patent Information

Application Number
CN202011007061.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-09-22
Publication Date
2024-11-29
Estimated Expiration
2040-09-22

AI Technical Summary

Technical Problem

The existing cloud computing framework requires a combination of multiple resources when building cloud services, which leads to a cumbersome combination process and high threshold, which affects user experience. Especially the lack of enterprise organization processes leads to slow service application efficiency.

Method used

Through the design interface, users can visually orchestrate the target service components, automatically generate service instances, and combine the approval process to reduce application steps and improve service construction efficiency and user experience.

Benefits of technology

It has achieved the efficiency and user experience improvement of service construction, simplified the application process of cloud services, adapted to enterprise organization processes, and reduced user steps.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114268659B_ABST
    Figure CN114268659B_ABST
Patent Text Reader

Abstract

The embodiment of the present application provides a service construction method, a related device and a computer-readable storage medium, the method comprising: obtaining a target service component arranged by a user in a design interface, wherein the design interface provides multiple service components, the multiple service components including a computing component, a storage component and a network component; the target service component is one or more of the multiple service components; a service instance is constructed according to the target service component, the service instance is used for a user device to use resources corresponding to the target service component. The use of the embodiment of the present application can improve the efficiency of service construction.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on September 14, 2020, with application number 2020109627150 and application name “Method, device, server and storage medium for building services”, the entire contents of which are incorporated by reference in this application. Technical Field

[0002] The present application relates to the field of cloud computing technology, and in particular to a service construction method, related devices and computer-readable storage media. Background Art

[0003] With the improvement of software maturity in various industries and the development of network technology, cloud computing has been applied in different industries. Cloud computing is a computing service model based on the Internet, which brings together a large amount of storage resources and processing resources stored on personal computers, servers or other computing devices, manages them uniformly and works together. It breaks the boundaries of software and hardware resources and only requires a small amount of management interaction to quickly provide a large amount of resources.

[0004] However, in most cloud computing frameworks, multiple resources are needed to build cloud services. These resources are combined after users apply for services from cloud computing providers. However, the process of combining services requires multiple connections, so the combination process is cumbersome and has a high threshold, which affects the user experience. For example, if Department A needs to run a web service, it needs to apply for computing resources (servers), storage resources (for storing data) and load balancing resources and then use them together. Since web services usually involve multiple service interactions, the process of combining services requires a lot of energy, and the efficiency of service construction is low, which affects the user experience. Summary of the invention

[0005] The embodiments of the present application disclose a service construction method, related devices and computer-readable storage medium, which can improve the efficiency of service construction.

[0006] In a first aspect, an embodiment of the present application discloses a service construction method, including:

[0007] Acquire a target service component arranged by a user in a design interface, wherein the design interface provides a plurality of service components, the plurality of service components including a computing component, a storage component, and a network component; the target service component is one or more of the plurality of service components;

[0008] A service instance is constructed according to the target service component, and the service instance is used for user equipment to use resources corresponding to the target service component.

[0009] In an embodiment of the present application, a plurality of service components are provided in the design interface, and these service components correspond to resources. Users can visually arrange these service components to obtain target service components that meet their own needs. The service builder obtains the target service components arranged by the user, and builds service instances through the target service components, so that the atomic services can be built into combined service instances for use by user devices. In this way, it is only necessary to arrange the multiple service components required for the service instance in the design interface, and the service builder can automatically generate a service instance containing multiple service components without the need for the user to apply for resources separately and then combine them, thereby improving the efficiency of service construction. On the other hand, users can arrange service components according to their own needs, so as to obtain customized service instances through the service builder, which meets the user's needs for diversified service instances and improves the user experience.

[0010] Furthermore, the multiple service components include computing components, storage components and network components. When it is necessary to build a service suitable for running a web page (website or simply web) application (hereinafter referred to as a web service or web service), the architecture of the web service can be quickly obtained by quickly combining the computing components, storage components and network components, thereby improving the efficiency of building the web service.

[0011] In a possible implementation of the first aspect, the multiple service components further include a cross-cloud orchestration component.

[0012] The cross-cloud orchestration component is used to orchestrate public cloud resources. The cross-cloud orchestration component can be used as a container, and users can define the corresponding service components of public cloud resources in the cross-cloud orchestration component. In this way, public cloud resources (such as servers in the public cloud, storage resources in the public cloud) and private cloud resources (such as databases in the private cloud) can be combined in the same service instance according to business scenarios to achieve cross-cloud orchestration, improve the compatibility and diversity of services, and meet the needs of users to connect public cloud resources and private cloud resources.

[0013] In yet another possible implementation of the first aspect, the multiple service components further include information technology IT service components.

[0014] Among them, IT services refer to services such as hardware integration, software applications or hardware and software integration solutions provided by service providers in the field of information technology to their users. It can be seen that by taking IT services as service components, the IT capabilities provided by cloud service providers can be built into online services and applied to cloud computing, enriching the IT capability service ecosystem.

[0015] In another possible implementation of the first aspect, the method further includes:

[0016] Receiving IT service information input by a user, wherein the IT service information includes application program interface (API) information;

[0017] The IT service component is generated according to the information of the IT service.

[0018] In another possible implementation of the first aspect, the computing component specifically includes one or more of an elastic cloud server component, a bare metal server, and the like; the storage component includes a cloud hard disk component, and the like; the network component includes an elastic load balancing component and an elastic Internet Protocol EIP component, and the like.

[0019] In another possible implementation of the first aspect, the target service components specifically include a web server component, a database component, a reverse proxy server component, an elastic load balancing ELB component, and an elastic internet interconnection protocol EIP component; wherein the web server component, the database component, and the reverse proxy server component are obtained based on the computing component, and the elastic load balancing component and the elastic internet interconnection protocol belong to the network component.

[0020] In one possible design, the user can deploy a reverse proxy server program (such as Nginx program) in the elastic cloud server component to obtain a reverse proxy server component. In another possible design, the user can deploy a web service program in the elastic cloud server to obtain a web server.

[0021] In another possible implementation of the first aspect, the constructing a service instance according to the target service component includes:

[0022] Determine configuration information of the service instance; the configuration information includes specification data of the service instance, and parameter data of the service instance or definition rules of parameter data;

[0023] The service instance is constructed according to the target service component and the configuration information of the service instance.

[0024] The configuration information may specifically include specification information and parameter information. The data value corresponding to the specification information is called specification data, and the data value corresponding to the parameter information is called parameter data. Optionally, a set of data provided for selection is the specification information, such as image, specification, available partition, system disk size, etc. Usually a set of data is provided for selection, so it is called specification parameters. The information that can be freely defined by the configuration node or user device is called parameter information, such as the virtual machine user name, password, subnet information, etc. are called parameter information.

[0025] In another possible implementation of the first aspect, the definition rule of the parameter data is one of a plurality of definition rules; the plurality of definition rules include administrator definition, user device definition and approval node definition.

[0026] Specifically, the definition rule is a parameter defined by the administrator, and the parameter data is filled in when the administrator builds the service. For example, the virtual machine name can be included in the information when building the service. Furthermore, the definition rule can also include whether to hide the parameter, thereby shielding the parameters that the user does not care about, thereby reducing the complexity of the page when the user applies for the service.

[0027] The definition rule is the parameter of the user's device, and the parameter data is filled in when the user applies for the service. For example, the password required to use the service.

[0028] Define the parameters defined by the rules for the approval node, and fill in the parameter values ​​during the approval process. Furthermore, when the approval process includes multiple approval nodes, you can also specify a specific approval node to determine the parameter value. For example: the second-level approval node in the second-level approval determines the subnet information associated with the network card.

[0029] In another possible implementation of the first aspect, the method further includes:

[0030] The service instance is associated with a first approval process, where the approval process is used to approve a request for using the service instance.

[0031] Currently, there is a lack of enterprise organizational processes in cloud computing services, resulting in the inability to adapt to enterprise organizational processes during use. For example, Department A of Enterprise needs to use a computing resource with 8G of memory to run a program. It needs to apply for a process internally and wait for approval before applying for or purchasing computing resources from the cloud computing provider. This method of using cloud services is relatively cumbersome and the efficiency of applying for services is slow, which affects the user experience. In an embodiment of the present application, a service instance is associated with a first approval process. When a user submits a request to apply for the use of a service instance, the request can be pushed to the approval node. When the request for the service instance is approved, the instance can be deployed for user use, thereby combining the service application process with the approval process, reducing the steps for users to apply for services, and improving the user experience.

[0032] In a second aspect, an embodiment of the present application provides a service construction method, including:

[0033] The design node obtains multiple service components from the management node; the multiple service components include computing components, storage components and network components;

[0034] The design node orchestrates a target service component for constructing a service instance based on the multiple service components;

[0035] The design node submits the target service component to the management node;

[0036] The configuration node determines the target service component on which the service instance is based, the configuration information of the service instance, and the first approval process associated with the service instance, and submits the configuration information of the service instance and the information indicating the first approval process to the management node; the configuration information includes specification data of the service instance, and parameter data of the service instance or definition rules of parameter data;

[0037] The management node constructs the service instance based on the target service component, the configuration information of the service instance and the information indicating the first approval process, so that the user equipment can use the resources corresponding to the target service component.

[0038] In the embodiment of the present application, the design node provides multiple service components in the design interface. These service components correspond to resources. Users can visually arrange these service components in the design node to obtain target service components that meet their needs. The management node builds service instances through target service components and configuration information, so that atomic services can be built into combined service instances for use by user devices. In this way, you only need to arrange multiple service components required for the service instance in the design interface to automatically generate a service instance containing multiple service components, without having to apply for resources separately and then combine them, which improves the efficiency of service construction.

[0039] Furthermore, the service instance is associated with a first approval process. When a user submits a request to apply for the use of a service instance, the request can be pushed to an approval node. When the request for the service instance is approved, the instance can be deployed for user use, thereby combining the service application process and the approval process, reducing the steps for users to apply for services and improving user experience.

[0040] In a possible implementation of the second aspect, the multiple service components further include a cross-cloud orchestration component.

[0041] The cross-cloud orchestration component is used to orchestrate public cloud resources. The cross-cloud orchestration component can be used as a container, and users can define the corresponding service components of public cloud resources in the cross-cloud orchestration component. In this way, public cloud resources (such as servers in the public cloud) and private cloud resources (such as databases in the private cloud) can be combined in the same service instance according to business scenarios to achieve cross-cloud orchestration, improve the compatibility and diversity of services, and meet the needs of users to connect public cloud resources and private cloud resources.

[0042] In yet another possible implementation of the second aspect, the multiple service components further include an IT service component.

[0043] Among them, IT services are services such as hardware integration, software applications, and hardware and software integration solutions provided by service providers in the field of information technology to their users. It can be seen that by taking IT services as service components, the IT capabilities provided by cloud service providers can be built into online services and applied to cloud computing, enriching the IT capability service ecosystem.

[0044] In another possible implementation manner of the second aspect, the method further includes:

[0045] The management node obtains IT service information input by the user, wherein the IT service information includes application program interface API information;

[0046] The management node generates the IT service component according to the information of the IT service.

[0047] In another possible implementation of the second aspect, the computing component specifically includes one or more of an elastic cloud server component, a bare metal server component, etc.; the storage component includes a cloud hard disk component, etc.; the network component includes an elastic load balancing component and an elastic Internet Protocol EIP component, etc.

[0048] In another possible implementation of the second aspect, the target service components specifically include a web server component, a database component, a reverse proxy server component, an elastic load balancing ELB component, and an elastic internet interconnection protocol EIP component; wherein the web server component, the database component, and the reverse proxy server component are obtained based on the computing component, and the elastic load balancing component and the elastic internet interconnection protocol belong to the network component.

[0049] In one possible design, the user can deploy a reverse proxy server program (such as Nginx program) in the elastic cloud server component to obtain a reverse proxy server component. In another possible design, the user can deploy a web service program in the elastic cloud server to obtain a web server.

[0050] In yet another possible implementation manner of the second aspect, after the design node orchestrates the target service component for constructing the service instance based on the multiple service components, the design node further includes:

[0051] The design node determines a configuration item of the target service component, where the configuration item is used to describe a property for constructing the target service component;

[0052] The design node determines a first service template, where the first service template includes the target service component and configuration items of the target service component.

[0053] In another possible implementation of the second aspect, the configuration node determines the target service component based on the service instance, the configuration information of the service instance, and the first approval process associated with the service instance, including:

[0054] The configuration node obtains information of at least one service template and at least one process from the management node; the at least one service template includes the first service template; the at least one process information includes the information for indicating the first approval process;

[0055] The configuration node determines, from the at least one service template, to construct a service instance based on the first service template, wherein the first service template includes the target service component and a configuration item of the target service component;

[0056] The configuration node receives input configuration information of the service instance and a first approval process associated with the first service.

[0057] In yet another possible implementation of the second aspect, after the management node constructs the service instance based on the target service component, the configuration information of the service instance, and the information indicating the first approval process, the method further includes:

[0058] The management node receives a request sent by the user equipment to apply for using the service instance;

[0059] The management node sends the request to the approval node for approval;

[0060] After approval, the management node deploys the service instance for use by the user equipment.

[0061] In yet another possible implementation of the second aspect, after the management node sends the request to the approval node for approval by the approval node and before the management node deploys the service instance, the method further includes:

[0062] The management node receives the approval result from the approval node;

[0063] The management node determines, based on the approval result, that the request for using the service instance is approved.

[0064] In a third aspect, the embodiment of the present application further provides a service construction device, including:

[0065] A communication unit, configured to obtain a target service component arranged by a user in a design interface, wherein the design interface provides a plurality of service components, the plurality of service components including a computing component, a storage component, and a network component; the target service component is one or more of the plurality of service components;

[0066] A processing unit is used to construct a service instance according to the target service component, and the service instance is used for user equipment to use resources corresponding to the target service component.

[0067] In an embodiment of the present application, the above-mentioned device provides multiple service components in the design interface. These service components correspond to resources, and users can visually arrange these service components to obtain target service components that meet their own needs. The above-mentioned device obtains the target service components arranged by the user, and builds service instances through the target service components, so that the atomic services can be built into combined service instances for use by user devices. In this way, it is only necessary to arrange the multiple service components required for the service instance in the design interface, and the above-mentioned device can automatically generate a service instance containing multiple service components without the need for users to apply for resources separately and then combine them, thereby improving the efficiency of service construction. On the other hand, users can arrange service components according to their own needs, so as to obtain customized service instances through the service builder, meet the user's needs for diversified service instances, and improve the user experience.

[0068] Furthermore, the multiple service components include computing components, storage components and network components. When it is necessary to build a service suitable for running a web page (website or simply web) application (hereinafter referred to as a web service or web service), the architecture of the web service can be quickly obtained by quickly combining the computing components, storage components and network components, thereby improving the efficiency of building the web service.

[0069] In a possible implementation of the third aspect, the multiple service components further include a cross-cloud orchestration component.

[0070] The cross-cloud orchestration component is used to orchestrate public cloud resources. The cross-cloud orchestration component can be used as a container, and users can define the corresponding service components of public cloud resources in the cross-cloud orchestration component. In this way, public cloud resources (such as servers in the public cloud) and private cloud resources (such as databases in the private cloud) can be combined in the same service instance according to business scenarios to achieve cross-cloud orchestration, improve the compatibility and diversity of services, and meet the needs of users to connect public cloud resources and private cloud resources.

[0071] In yet another possible implementation of the third aspect, the multiple service components further include an IT service component.

[0072] Among them, IT services are services such as hardware integration, software applications, and hardware and software integration solutions provided by service providers in the field of information technology to their users. It can be seen that by taking IT services as service components, the IT capabilities provided by cloud service providers can be built into online services and applied to cloud computing, enriching the IT capability service ecosystem.

[0073] In yet another possible implementation of the third aspect, the communication unit is further configured to receive IT service information input by a user, wherein the IT service information includes application program interface API information;

[0074] The processing unit is further configured to generate the IT service component according to the information of the IT service.

[0075] In another possible implementation of the third aspect, the computing component specifically includes one or more of an elastic cloud server component, a bare metal server, and the like; the storage component includes a cloud hard disk component, and the like; the network component includes an elastic load balancing component and an elastic Internet Protocol EIP component, and the like.

[0076] In another possible implementation of the third aspect, the target service components specifically include a web server component, a database component, a reverse proxy server component, an elastic load balancing ELB component, and an elastic internet interconnection protocol EIP component; wherein the web server component, the database component, and the reverse proxy server component are obtained based on the computing component, and the elastic load balancing component and the elastic internet interconnection protocol belong to the network component.

[0077] In one possible design, the user can deploy a reverse proxy server program (such as Nginx program) in the elastic cloud server component to obtain a reverse proxy server component. In another possible design, the user can deploy a web service program in the elastic cloud server to obtain a web server.

[0078] In yet another possible implementation manner of the third aspect, the processing unit is further configured to:

[0079] Determine configuration information of the service instance; the configuration information includes specification data of the service instance, and parameter data of the service instance or definition rules of parameter data;

[0080] The service instance is constructed according to the target service component and the configuration information of the service instance.

[0081] The configuration information may specifically include specification information and parameter information. The data value corresponding to the specification information is called specification data, and the data value corresponding to the parameter information is called parameter data. Optionally, a set of data provided for selection is the specification information, such as image, specification, available partition, system disk size, etc. Usually a set of data is provided for selection, so it is called specification parameters. The information that can be freely defined by the configuration node or user device is called parameter information, such as the virtual machine user name, password, subnet information, etc. are called parameter information.

[0082] In another possible implementation of the third aspect, the definition rule of the parameter data is one of a plurality of definition rules; the plurality of definition rules include administrator definition, user device definition and approval node definition.

[0083] Specifically, the definition rule is a parameter defined by the administrator, and the parameter data is filled in when the administrator builds the service. For example, the virtual machine name can be included in the information when building the service. Furthermore, the definition rule can also include whether to hide the parameter, thereby shielding the parameters that the user does not care about, thereby reducing the complexity of the page when the user applies for the service.

[0084] The definition rule is the parameter of the user's device, and the parameter data is filled in when the user applies for the service. For example, the password required to use the service.

[0085] Define the parameters defined by the rules for the approval node, and fill in the parameter values ​​during the approval process. Furthermore, when the approval process includes multiple approval nodes, you can also specify a specific approval node to determine the parameter value. For example: the second-level approval node in the second-level approval determines the subnet information associated with the network card.

[0086] In yet another possible implementation manner of the third aspect, the processing unit is further configured to:

[0087] The service instance is associated with a first approval process, where the approval process is used to approve a request for using the service instance.

[0088] Currently, there is a lack of enterprise organizational processes in cloud computing services, resulting in the inability to adapt to enterprise organizational processes during use. For example, Department A of Enterprise needs to use a computing resource with 8G of memory to run a program. It needs to apply for a process internally and wait for approval before applying for or purchasing computing resources from the cloud computing provider. This method of using cloud services is relatively cumbersome and the efficiency of applying for services is slow, which affects the user experience. In an embodiment of the present application, a service instance is associated with a first approval process. When a user submits a request to apply for the use of a service instance, the request can be pushed to the approval node. When the request for the service instance is approved, the instance can be deployed for user use, thereby combining the service application process with the approval process, reducing the steps for users to apply for services, and improving the user experience.

[0089] In a fourth aspect, the embodiment of the present application further provides a service construction system, including:

[0090] Designing a node, used to obtain multiple service components from a management node; the multiple service components include computing components, storage components and network components;

[0091] The design node is further used to orchestrate a target service component for constructing a service instance based on the multiple service components;

[0092] The design node is further used to submit the target service component to the management node;

[0093] The configuration node is used to determine the target service component on which the service instance is based, the configuration information of the service instance and the first approval process associated with the service instance, and submit the configuration information of the service instance and the information indicating the first approval process to the management node; the configuration information includes specification data of the service instance, and parameter data of the service instance or definition rules of parameter data;

[0094] The management node is used to construct the service instance based on the target service component, the configuration information of the service instance and the information indicating the first approval process, so that the user equipment can use the resources corresponding to the target service component.

[0095] In the embodiment of the present application, the design node provides multiple service components in the design interface. These service components correspond to resources. Users can visually arrange these service components in the design node to obtain target service components that meet their needs. The management node builds service instances through target service components and configuration information, so that atomic services can be built into combined service instances for use by user devices. In this way, you only need to arrange multiple service components required for the service instance in the design interface to automatically generate a service instance containing multiple service components, without having to apply for resources separately and then combine them, which improves the efficiency of service construction.

[0096] Furthermore, the service instance is associated with a first approval process. When a user submits a request to apply for the use of a service instance, the request can be pushed to an approval node. When the request for the service instance is approved, the instance can be deployed for user use, thereby combining the service application process and the approval process, reducing the steps for users to apply for services and improving user experience.

[0097] In a possible implementation of the fourth aspect, the multiple service components further include a cross-cloud orchestration component.

[0098] The cross-cloud orchestration component is used to orchestrate public cloud resources. The cross-cloud orchestration component can be used as a container, and users can define the corresponding service components of public cloud resources in the cross-cloud orchestration component. In this way, public cloud resources (such as servers in the public cloud) and private cloud resources (such as databases in the private cloud) can be combined in the same service instance according to business scenarios to achieve cross-cloud orchestration, improve the compatibility and diversity of services, and meet the needs of users to connect public cloud resources and private cloud resources.

[0099] In yet another possible implementation of the fourth aspect, the multiple service components further include an IT service component.

[0100] Among them, IT services are services such as hardware integration, software applications, and hardware and software integration solutions provided by service providers in the field of information technology to their users. It can be seen that by taking IT services as service components, the IT capabilities provided by cloud service providers can be built into online services and applied to cloud computing, enriching the IT capability service ecosystem.

[0101] In yet another possible implementation manner of the fourth aspect, the management node is further configured to obtain IT service information input by a user, where the IT service information includes application program interface API information;

[0102] The management node is further used to generate the IT service component according to the information of the IT service.

[0103] In another possible implementation of the fourth aspect, the computing component specifically includes one or more of an elastic cloud server component, a bare metal server component, etc.; the storage component includes a cloud hard disk component, etc.; the network component includes an elastic load balancing component and an elastic Internet Protocol EIP component, etc.

[0104] In another possible implementation of the fourth aspect, the target service components specifically include a web server component, a database component, a reverse proxy server component, an elastic load balancing ELB component, and an elastic internet interconnection protocol EIP component; wherein the web server component, the database component, and the reverse proxy server component are obtained based on the computing component, and the elastic load balancing component and the elastic internet interconnection protocol belong to the network component.

[0105] In one possible design, the user can deploy a reverse proxy server program (such as Nginx program) in the elastic cloud server component to obtain a reverse proxy server component. In another possible design, the user can deploy a web service program in the elastic cloud server to obtain a web server.

[0106] In yet another possible implementation manner of the fourth aspect, the design node is specifically used to:

[0107] Determine a configuration item of the target service component, wherein the configuration item is used to describe a property of building the target service component;

[0108] A first service template is determined, where the first service template includes the target service component and configuration items of the target service component.

[0109] In yet another possible implementation manner of the fourth aspect, the configuration node is specifically configured to:

[0110] Acquire information of at least one service template and at least one process from the management node; the at least one service template includes the first service template; the at least one process information includes the information for indicating the first approval process;

[0111] Determine, from the at least one service template, to build a service instance based on the first service template, where the first service template includes the target service component and a configuration item of the target service component;

[0112] The configuration information of the service instance and the first approval process associated with the first service are obtained.

[0113] In yet another possible implementation manner of the fourth aspect, the construction device further includes an approval node, and the management unit is further configured to:

[0114] Receiving a request from a user device for using the service instance;

[0115] Sending the request to an approval node for approval by the approval node;

[0116] After approval, the service instance is deployed for use by the user device.

[0117] In yet another possible implementation manner of the fourth aspect, the management node is further configured to:

[0118] Receive approval results from the approval node;

[0119] It is determined that the request for using the service instance is approved according to the approval result.

[0120] In the fifth aspect, an embodiment of the present application discloses a service construction device, which includes a processor and a memory; the processor is used to execute computer instructions stored in the memory, so that the configuration node implements the method described in the first aspect or a possible implementation method of the first aspect.

[0121] In a sixth aspect, an embodiment of the present application discloses a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to implement the method described in the first aspect or any possible implementation of the first aspect; or to implement the method described in the second aspect or any possible implementation of the second aspect; or to implement the method described in the third aspect or any possible implementation of the third aspect.

[0122] In the seventh aspect, an embodiment of the present application discloses a computer program product, which is used to implement the method described in the first aspect or any possible implementation of the first aspect; or to implement the method described in the second aspect or any possible implementation of the second aspect; or to implement the method described in the third aspect or any possible implementation of the third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0123] The following is an introduction to the drawings used in the embodiments of the present application.

[0124] Figure 1 This is a schematic diagram of a use scenario of a cloud computing service provided by an embodiment of the present application;

[0125] Figure 2 It is a schematic diagram of the architecture of a service construction system provided in an embodiment of the present application;

[0126] Figure 3It is a flowchart of a service construction method provided in an embodiment of the present application;

[0127] Figure 4 It is a schematic diagram of an interface of a design page provided in an embodiment of the present application;

[0128] Figure 5 is a schematic diagram of a target service component provided in an embodiment of the present application;

[0129] Figure 6 is a schematic diagram of another target service component provided in an embodiment of the present application;

[0130] Figure 7 This is a schematic diagram of an interface for accessing IT services provided by an embodiment of the present application;

[0131] Figure 8 This is a schematic diagram of an interface of configuration information provided in an embodiment of the present application;

[0132] Fig. 9 It is a schematic diagram of an approval process provided in an embodiment of the present application;

[0133] Fig.10 This is a schematic diagram of an interface for obtaining a function description provided in an embodiment of the present application;

[0134] Fig.11 This is a schematic diagram of an interface for obtaining an application scenario provided in an embodiment of the present application;

[0135] Fig.12 It is a schematic diagram of an introduction page of a service example provided in an embodiment of the present application;

[0136] Fig.13 This is a schematic diagram of the architecture of another service construction system provided in an embodiment of the present application;

[0137] Fig.14 It is a flowchart of another service construction method provided in an embodiment of the present application;

[0138] Fig.15 This is a schematic diagram of an interface for saving a service template provided in an embodiment of the present application;

[0139] Fig.16 It is a structural diagram of a service construction device provided in an embodiment of the present application;

[0140] Fig.17 It is a structural diagram of another service construction device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0141] The embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application.

[0142] See also Figure 1 , Figure 1 This is a schematic diagram of a possible use scenario of a cloud computing service provided by the implementation of this application. Cloud computing service 101 includes multiple services (or also called resources), such as application software services, hardware services, virtual machine services, container services, etc. These services are atomic. Since the services required by users usually include multiple services, they need to be combined after applying for resources in cloud computing service 101. However, the process of combining services requires multiple connections, so the combination process is cumbersome and has a high threshold, which affects the user experience. For example, Department A needs to run a web service system 102. The web service system requires computing services (such as servers), storage resources (such as hard disks) and elastic loads. They need to be applied for separately and then combined for use. Since the web service system usually involves multiple service interactions, the process of connecting and combining services requires a lot of energy, and the efficiency of service construction is low, which affects the user experience.

[0143] See also Figure 2 , Figure 2 This is a schematic diagram of the architecture of a possible service construction system 20 provided in an embodiment of the present application, referring to area 201. The service construction system 20 can implement page definition, process definition, resource orchestration and automatic orchestration of service instances in terms of front-end functions. In this way, users can input parameters through the interface provided by the system to define processes, orchestrate resources, etc.

[0144] Referring to area 202, the service construction system 20 includes one or more of a resource management module, a cloud service portal module, an interface rendering engine, a process engine, a resource orchestration engine, and a model management template, etc. Among them, the resource management template can realize the management of resources, such as the management of script resources and template resources. The cloud service portal is used to launch cloud services, or to introduce and display cloud services, etc., to facilitate users to apply for cloud services. The interface rendering engine can render pages or dynamically load components, etc. The process engine is used to support the aforementioned process definition. The resource orchestration engine is used to support the aforementioned resource orchestration and automated orchestration. The model management module is used to manage cloud service models, user interface (uesrinterface, UI) component models, process component models, and service components (also called resource models in department scenarios).

[0145] Referring to area 203, the service construction system 20 may include resources in Huawei Cloud Service Platform (HiCloud), OpenStack (a cloud computing platform), platform as a service (plat as a service), public cloud, and may also include IT capabilities. Among them, the public cloud may be Huawei public cloud, Amazon Web Services (AWS), etc.

[0146] See also Figure 3 , Figure 3 This is a service construction method provided by the embodiment of the present application. Optionally, the method can be based on Figure 2 The architecture shown is implemented. Figure 3 The service construction method shown includes at least the following steps:

[0147] Step S301: the service builder obtains the target service component arranged by the user in the design interface.

[0148] The design interface provides multiple service components, including one or more of computing components, storage components, network components, elastic scaling components, etc., and the target service component is one or more of the multiple service components. Optionally, the computing component specifically includes one or more of elastic cloud servers, bare metal servers, etc., the storage component includes cloud hard disk components, etc.; the network component includes elastic load balancing (ELB) components and elastic Internet Protocol (EIP) components, etc.; the elastic scaling component specifically includes resource group components and scaling group components, etc.

[0149] Furthermore, each service component can be combined to obtain a new service component. For example, one or more elastic cloud server components can be added to the scaling group component in the elastic scaling component. After being deployed as a service instance, the scaling group can adjust the bandwidth resources between elastic cloud servers, etc. For another example, the cloud hard disk component can be mounted in the computing component (such as the virtual machine component or elastic cloud server, etc.) to provide storage for the computing component.

[0150] Specifically, among the multiple service components provided by the design interface, each service component corresponds to a service (or resource), and the user can visually arrange these service components to obtain the target service component that meets their needs. Correspondingly, the service builder obtains the target service component arranged by the user in the design interface. For example, see Figure 4 , Figure 4is a schematic diagram of a possible design interface provided by an embodiment of the present application, wherein referring to area 401, a variety of service components are provided in the design page, and the user can drag (or pull) the service components to arrange the service components. Figure 4 , the user can drag the elastic cloud server component (or other computing components), elastic load balancing component, and EIP component to the "Overview" canvas shown in area 402, so that the service builder can obtain the target service component orchestrated by the user. Among them, the web server, database, and reverse proxy server in area 402 are obtained based on the elastic cloud server (or other computing components, such as virtual machine components, etc.), for example, the functions of the elastic cloud service configuration when used are obtained. Service components with various functions.

[0151] In one possible design, the user can deploy a reverse proxy server program (such as Nginx program) in the elastic cloud server component to obtain a reverse proxy server component, wherein Nginx (also known as engine x) is a high-performance hypertext transfer protocol (HTTP) and reverse proxy technology, and the service component configured with the Nginx program is called a reverse proxy server component. In another possible design, the user can deploy a web service program in the elastic cloud server to obtain a web server component.

[0152] For example, participate Figure 5 , Figure 5 It is a schematic diagram of a possible target service component provided by an embodiment of the present application, and the target service component includes an EIP component 501, an ELB component 502, an Nginx cluster (obtained according to the resource group component in the elastic scaling component) 503, a Web server group (obtained according to the scaling group component in the elastic scaling component) 504, and a database (database, DB) master-slave component 505. The Nginx cluster 503 includes one or more computing components configured with Nginx (for example, an elastic cloud server or virtual machine configured with Nginx, etc.). The Web server group includes one or more computing components configured with Web services. The DB master-slave component is obtained by combining one or more storage components configured with a database (specifically also including storage components coupled thereto, such as a cloud hard disk).

[0153] It can be seen that users can arrange service components according to their own needs, and thus obtain customized service instances through the service builder, meeting users' needs for diversified service instances and improving user experience. When it is necessary to build a service suitable for running web applications, the architecture of the web service can be quickly obtained by combining computing components, storage components, and network components, which can improve the efficiency of building web services.

[0154] Furthermore, when a service component is determined, the service builder can also dynamically load the configuration items of the service component, where the configuration items are used to describe the properties of building the target service component. Figure 4 In the example, when the user drags the "database" service component to the "Overview" canvas shown in area 402, the service builder can load the configuration items shown in area 403 (which can be called attribute information in the specific implementation scenario). The configuration items are used to describe the attributes corresponding to the service component. For example, the configuration items shown in area 303 are used to describe the resource node where the "database" service component is located (corresponding to the name of the component), the name of the virtual machine (the name of the virtual machine on which the database is based), the available partition, etc. (this is an example and does not limit the specific configuration items). Optionally, for network resources, the configuration items can be the intranet address, the subnet, the listening port, etc.

[0155] In a possible design, the service builder receives the information of the configuration item edited by the user, and the information of the configuration item includes the name and description of the configuration item, etc. For example, the name and description corresponding to the configuration item can be determined by the received input operation or selection operation. For another example, referring to area 404, the configuration item can be edited as "user parameters" or "fixed parameters", wherein the user parameters are filled in by the user when subsequently creating an instance or the user applying for the service, and the fixed parameters are fixed by the administrator when determining the service component.

[0156] Optionally, the service builder may generate a first service template based on the target service component, wherein the service template includes the target service component (and may further include configuration items corresponding to the target service component). In this way, the target service component may be saved in the form of a service template. Figure 3 The design interface shown is a possible interface provided for the purpose of conveniently explaining the existence of multiple components in the interface. Other interfaces and other parameters may also be included in the specific implementation process.

[0157] Optionally, the multiple service components provided by the service builder also include a cross-cloud orchestration component, which is used to orchestrate public cloud resources. The cross-cloud orchestration component is used to orchestrate public cloud resources, and can be implemented in the following two ways:

[0158] Implementation 1: Define the components corresponding to the public cloud resources in the cross-cloud orchestration component, connect the cross-cloud orchestration component to the resources of the private cloud, and thus orchestrate the public cloud resources.

[0159] Implementation 2: Connect public cloud resources and private cloud resources through cross-cloud orchestration components to orchestrate public cloud resources.

[0160] For the implementation method described in Implementation 1, this application cites an implementation scenario, see Figure 6 , Figure 6 is a schematic diagram of another possible target service component provided by an embodiment of the present application, wherein the cross-cloud encoding component 601 defines a service component corresponding to one or more public cloud resources ( Figure 6 In the figure, the public cloud computing resource components and the public cloud storage resource components are taken as examples, which is not intended to limit the components corresponding to these two resources. The elastic cloud server 602 and the DB server 603 are private cloud resources. Therefore, the cross-cloud orchestration component can be used as a container, and the user can define the corresponding service components of the public cloud resources in the cross-cloud orchestration component. In this way, the resources of the public cloud can be orchestrated. Furthermore, the resources of the public cloud (such as servers in the public cloud) and the resources of the private cloud (such as databases in the private cloud) can be combined in the same service instance according to the business scenario to achieve cross-cloud orchestration, improve the compatibility and diversity of the service, and meet the needs of users to connect public cloud resources and private cloud resources.

[0161] Optionally, the design interface provides multiple service components including information technology (IT) service components, where IT services are services such as hardware integration, software applications, and software and hardware integration solutions provided by service providers in the field of information technology to their users. It can be seen that by using IT services as service components, the IT capabilities provided by cloud service providers can be built into online services and applied to cloud computing, enriching the IT capability service ecosystem.

[0162] Further optionally, the service builder receives IT service information input by the user, wherein the IT service information includes application programming interface (API) information. The service builder generates the IT service component according to the IT service information. For example, see Figure 7 , Figure 7 701 is a possible interface diagram for determining IT service components provided by an embodiment of the present application. In the participation area 701, the user can access (or input) IT services ( Figure 7In the example of the credit information service developed in the enterprise), the basic information of the IT service is the basic information filled in by the user when accessing the IT service. The basic information includes one or more of the name, description, IP, port, client certificate, server certificate, protocol, and password. Referring to area 702, the IT service information may include the API information of the IT service. The API information includes the API name, Uniform Resource Locator (URL), request type (including two request types, post and get), etc. The service builder can also receive API information input by the user. For example, the user clicks on the page control 703 (a control for importing files) to import the API file. Referring to area 704, the user can define the corresponding service component according to the IT service information. For example, the user can click on the "Add" control shown in area 705 to enter the resource name (i.e., the name of the service component) and description. Furthermore, the service builder generates the service component of the application resource according to the basic information, API information, and resource name of the application service.

[0163] Step S302: The service builder builds a service instance according to the target service component.

[0164] The service instance is used for the user device to use the resources corresponding to the target service component. The service builder constructs the service instance through the target service component, so that the atomic service can be constructed into a composite service instance for the user device to use.

[0165] Specifically, the service (or resource) in the service instance is the service (or resource) indicated by the target service component. For example, if the service template includes a web server component and a reverse proxy server component, the generated service instance includes a web server and a reverse proxy server.

[0166] For example, if the target service component is Figure 5 Taking the target service component shown as an example, the generated service instance can be a composite service of WordPress (a platform developed based on the PHP language). The service instance of the composite service of WordPress includes a group of elastic cloud servers deployed with WordPress, a group of elastic cloud services deployed with database nodes, a server deployed with Nginx, and related network resources of ELP and EIP.

[0167] In a possible design, the service builder determines the configuration information of the service instance, and builds the service instance according to the target service component and the configuration information of the service instance. The configuration information may be a default one, or may be received from a user input, or may be obtained from a network side device through a communication interface. The configuration information includes specification data of the service instance, and parameter data of the service instance or definition rules of parameter data.

[0168] Optionally, the configuration information may specifically include specification information and parameter information. The data value corresponding to the specification information is called specification data, and the data value corresponding to the parameter information is called parameter data. Optionally, a set of data provided for selection is the specification information, such as image, specification, available partition, system disk size, etc. Usually a set of data is provided for selection, so it is called specification parameters. The information that can be freely defined by the configuration node or user device is called parameter information, such as the virtual machine user name, password, subnet information, etc. are called parameter information.

[0169] Further optionally, the definition rule of the parameter data is used to indicate the user (or user role) who defines the parameter or the device that defines the parameter. For example, the present application provides three definition rules as examples: administrator definition, user device definition, and approval node definition. Specifically, the definition rule is the parameter defined by the administrator, and the parameter data is filled in when the administrator builds the service instance. For example: the virtual machine name can be included in the configuration information when building the service instance. The definition rule is the parameter of the user device, and the parameter data is filled in with the parameter value when the user applies for the service. For example, the password entered when using the service instance. The definition rule is the parameter defined by the approval node, and the parameter value can be filled in by the approval node during the approval process. Furthermore, when the approval process includes multiple approval nodes, a specific approval node can also be specified to determine the parameter value. For example: the second-level approval node in the secondary approval determines the subnet information associated with the network card.

[0170] Optionally, the service builder may associate the service instance with a first approval process, and the approval process is used to approve a request to use the service instance. When the service instance is associated with the first approval process, when a user submits a request to use the service instance, the request can be pushed to the approval node. When the request for the service instance is approved, the instance can be deployed for the user to use, thereby combining the service application process with the approval process, reducing the steps for users to apply for services and improving the user experience.

[0171] In a possible design, the service builder can output a page on which the administrator can input or select an operation. Correspondingly, the service builder receives the input or selection operation and determines the configuration information of the service instance. For example, see Figure 8 , Figure 8801 is a schematic diagram of an interface for determining configuration information of a service instance provided in an embodiment of the present application. An administrator (or a service provider) can enter or select configuration information through this page. See area 801. The configuration information can specifically include basic information, such as a service name (the name of the service instance provided), a service provider (who provides the service instance), a service type (which can be a computing service, a storage service, a database service, a web service, or a pre-configured service type), a service responsible person, a description, and version information (used to describe the version of the service instance. Figure 8 ), service support personnel (also referred to as support personnel, used to describe personnel who provide technical support for the service instance, Figure 8 ), the region to which it belongs (indicating the region described by the provider of the service instance, Figure 8 Not shown), attribution items ( Figure 8 Not shown in the figure) etc.

[0172] In a possible design, the configuration information may also include a usage policy. Referring to area 802, the present application cites two possible usage policies: usage scope and associated process, wherein the usage scope is used to indicate one or more of the regions, companies, departments, personnel, etc. that have the authority to use the service instance, and the associated process is used to associate the request for using the service instance with a certain process. For example, referring to Fig. 9 , Fig. 9 This is a schematic diagram of a possible approval process 80 provided in an embodiment of the present application. The process is used to approve requests for using a service instance. When a user applies to use a service instance, the "Initiate Application" step is entered. The application can be pushed to the approver, who approves the request. If approved, the request is further transferred to the data management department (the department that manages service resources, also called the Data Management Bureau in some scenarios). After the service is deployed, the user can use the service instance.

[0173] Referring to area 803, the configuration information may also include specification settings for determining specification data, which may include specification name, virtual machine specifications (e.g., 1U2G, 2U4G, etc., where "1U2U" may refer to a central processing unit and 2GB of memory. In addition, in some implementation scenarios, 1U is a unit representing the height or thickness of the external dimensions of a server, and 1U is an abbreviation of unit. In some specific implementation scenarios, 1U = 4.445 cm, depending on the subsequent definition of the specifications for the computing unit), disk size (e.g., 32GB, 100GB, etc.), available partition (e.g., "AZ01" partition), specification description (not shown in the figure), etc. Optionally, if the target service component includes multiple components, the specifications of multiple service components may be set to obtain a set of specification data. For example, if the target service component includes a web server and a reverse proxy server, the specifications of the web server and the reverse proxy server are set to obtain specification data, which may be provided to the user for selection when the user subsequently applies for a service instance.

[0174] Referring to area 804, the configuration information also includes definition rules for parameter data, and details can be found in the above description of definition rules.

[0175] pass Figure 8 After filling in the configuration information on the page shown, the service builder generates the corresponding service instance based on the filled in configuration information for the user to apply for. Specifically, the service builder can save the service instance in the database and provide it to the user in the form of a service instance list. The user browses the list and selects the corresponding service instance to apply for according to his own needs. Correspondingly, the service builder receives the user's request to apply for the service instance and deploys the service instance for the user to use (in the case of an associated approval process, the service builder needs to confirm the approval before deploying the service instance).

[0176] Optionally, the service builder can also receive the introduction information of the service instance input by the user and output the introduction page of the service instance to facilitate the user to apply for the service. The introduction information of the service instance includes the function description and application scenario description of the service instance. Fig.10 , Fig.10 This is a possible interface diagram for obtaining a function description provided in an embodiment of the present application. The service builder can output Fig.10 In the interface shown, the user can enter or select a functional description of the service in area 1001. For example, the user can add a function icon in area 1002, enter a function name in area 1003, and enter a description of the function in area 1004. After the user submits the functional description, the service builder obtains the functional description of the service instance entered by the user.

[0177] See also Fig.11 , Fig.11 This is a possible interface diagram for obtaining an application scenario provided in an embodiment of the present application. The service builder can output Fig.11 In the interface shown, the user can enter or select a scenario for the service in area 1101. For example, the user can add an application scenario icon in area 1102, enter an application scenario name in area 1103, and describe the application scenario in area 1104. After the user submits the application scenario, the service builder obtains the description of the application scenario of the service instance entered by the user.

[0178] See also Fig.12 , Fig.12 This is a schematic diagram of the interface of an introduction page 1201 generated by a service builder provided in an embodiment of the present application. Referring to area 1202, the name and description of the service instance are displayed (here, the elastic cloud service is used as an example for description, and the specific implementation corresponds to the name of the service instance). Area 1204 displays the functional description of the service instance, which is the same as the functional description of the service instance. Fig.10 Area 1205 displays the application scenario, which corresponds to the functional description information defined in the interface shown. Fig.11 The application scenario defined in the interface shown corresponds to this. In this way, the user browses the introduction page and can apply for a service instance according to his or her own needs. The user clicks the control corresponding to area 1203 to subscribe to the service instance.

[0179] It should be noted that the multiple interfaces provided in the various embodiments of the present application are a possible interface provided for the convenience of explaining the elements existing in the interface. The specific implementation process may also include other forms of interfaces, or the interface may also include other elements.

[0180] exist Figure 3 In the described method, multiple service components are provided in the design interface, and these service components correspond to resources. Users can visually arrange these service components to obtain target service components that meet their own needs. The service builder obtains the target service components arranged by the user, and builds service instances through the target service components, so that the atomic services can be built into combined service instances for use by user devices. In this way, it is only necessary to arrange multiple service components required for the service instance in the design interface, and the service builder can automatically generate a service instance containing multiple service components without the user having to apply for resources separately and then combine them, thereby improving the efficiency of service construction. On the other hand, users can arrange service components according to their own needs, so as to obtain customized service instances through the service builder, which meets the user's needs for diversified service instances and improves the user experience.

[0181] Furthermore, the multiple service components include computing components, storage components and network components. When it is necessary to build a service suitable for running a web page (website or simply web) application (hereinafter referred to as a web service or web service), the architecture of the web service can be quickly obtained by quickly combining the computing components, storage components and network components, thereby improving the efficiency of building the web service.

[0182] See also Fig.13 , Fig.13 1 is a schematic diagram of the structure of a service construction system 130 provided in an embodiment of the present application, the system includes a design node 1301, a management node 1302 and a configuration node 1303, and further includes an approval node 1304 and a user device 1305. Among them:

[0183] The design node 1301 is an electronic device with data processing capability and data receiving and sending capability, which can be a physical device such as a host, a notebook, a mobile phone, etc., or a virtual device such as a virtual machine, a container, etc., and is used to determine the target service component of the user to build a service instance. Among them, the target service component is one or more of the multiple service components provided by the design node. Further, the service components provided by the design node may include one or more of the computing component, the storage component, the network component, the elastic scaling component, the cross-cloud orchestration component, the IT service component, etc.

[0184] In a possible implementation, the design node 1301 is used to create a first service template, which includes a target service component and configuration items of the target service component, and the configuration items of the target service component can also be referred to as attribute information of the service component. For example, when the service component is a computing component, the configuration items can be resource nodes, partitions, virtual machine names, etc. where the service component is located. Optionally, the design node 1301 can output a design interface, and after an administrator or a user of the design node arranges the service components and inputs or selects configuration items, the design node 1302 generates the first service template according to the arranged service components and configuration items.

[0185] The design node 1301 may submit the target service component (or the first service template) to the management node.

[0186] The management node 1302 is an electronic device with data processing capability and data receiving and sending capability, which can be a physical device such as a host, a rack server, a blade server, etc., or a virtual device such as a virtual machine, a container, etc. Further, the management node 1302 can be a server, or a server cluster composed of multiple servers. The management node is used to manage the process of building a service, such as receiving the first service template submitted by the design node 1301, receiving the configuration information submitted by the configuration node 1303, pushing the application for using the service instance to the approval node, etc. Optionally, different modules can be deployed in the management node to implement different functions. For example, the management node includes a template management module, which is used to manage the target service component (or the first service template) submitted by the design node (for example, to implement one or more functions of saving, querying, deleting, modifying, etc.). For another example, the management node includes a service management module, which is used to manage the configuration information submitted by the configuration node (for example, to generate a service instance according to the configuration information, save the service instance, register the operation link of the service, launch the service, etc.).

[0187] Optionally, the management node can save the information submitted by the design node 1301, the configuration node 1303 and the approval node 1304. Further, the management node 1302 can have storage capabilities, such as memory (including random access memory (RAM), read-only memory (ROM), erasable programmable read only memory (EPROM), etc.) in the management node 1302, and disks (including portable random access memory (CD-RAM), hard disks, etc.). Or optionally, the management node can communicate with a device with storage capabilities, such as a network attached storage (NAS) server, etc.

[0188] The configuration node 1303 is an electronic device with data processing capability and data transceiving capability, and may be a physical device such as a host, a rack server, a blade server, etc., or a virtual device such as a virtual machine, a container, etc. The configuration node is used to configure a service instance according to the first service template, and the service instance can be used by the user to use the service (or resource) corresponding to the service component in the service instance.

[0189] For example, the design node 1301 submits a first service template to the management node 1302, and the first service template includes the target service component and the configuration items of the target service component. The configuration node 1303 can obtain the first service template from the management node 1302, determine the configuration information according to the target service component and the configuration items of the target service component, and configure the service instance. The service (or resource) in the service instance is the service (or resource) indicated by the target service component. For example, the target service component includes a web server component and a reverse proxy server component, and the generated service instance includes a web server and a reverse proxy server. The configuration information can specifically include specification information and parameter information. The data value corresponding to the specification information is called specification data, and the data value corresponding to the parameter information is called parameter data. Optionally, a set of data provided for selection is specification information, such as: image, specification, available partition, system disk size, etc., and a set of data is usually provided for selection, so it is called specification parameters. The information that can be freely defined by the configuration node or user device is called parameter information, for example: virtual machine user name, password, subnet information, etc. are called parameter information.

[0190] Optionally, the configuration node may submit the service template and configuration information based on the service instance to the management node 1302, and the management node 1302 saves the service instance (for example, the management node 1302 may save the service instance in a database).

[0191] User device 1305 is a terminal with data processing capability and data receiving and sending capability, such as a mobile phone, a computer host, a portable computer, a cloud computer, a wearable device (smart watch, smart glasses, etc.). User devices can apply to use service instances, and accordingly, management node 1302 receives user requests to apply to use service instances and deploys services for users. Specifically, in a possible implementation, the management node can send a list of service instances to user device 1305, and the user of user device 1305 browses the list and selects the corresponding service instance to apply for according to his own needs. Accordingly, management node 1302 receives user device 1305's request to apply for service instances and deploys service instances for users to use (in the case of an associated approval process, the service builder needs to confirm approval before deploying the service instance).

[0192] Optionally, the service construction system 130 further includes an approval node 1304, which approves the request for applying to use the first service. In a possible implementation, the management node 1302 receives a request for applying to use a service instance sent by the user device 1302, pushes the request to the approval node 1304, and the approval node approves the request and returns an approval result (information indicating whether the approval is passed) to the management node 1302. After the management node 1302 determines that the approval is passed according to the approval result, it deploys the service instance for the user.

[0193] Furthermore, the design node 1301, the management node 1302, the configuration node 1303, and the approval node 1304 may be the same device or different devices.

[0194] For example, the service construction system 130 can be a B / S (Browser / Server, browser and server architecture mode, that is, the user work interface is implemented through the browser, part of the business logic is implemented on the front end (Browser), but the main business logic is implemented on the server side (Server)) architecture system. A browser is installed on a host, and the host can realize the functions completed by the design node 1301, the configuration node 1303, and the approval node 1304 by outputting different user interfaces.

[0195] For another example, user A creates a first service template in the design node 1301, and the service template can be authorized by user A to user B for use. Therefore, user B configures the service instance according to the first service template in the configuration node 1303. At this time, the design node 1301 and the configuration node 1303 are different devices.

[0196] For another example, the user implements the B / S architecture system through a local web program in the local host, so the host can not only complete the function of the management node, but also output a variety of interfaces to complete the functions of the design node 1301, the configuration node 1303, and the approval node 1304.

[0197] Optional, Fig.13 The communication links between the nodes in the network may include various types of connection media, such as wired links (such as optical fibers, system bus links, etc.), wireless links, or a combination of wired links and wireless links, etc., which are not limited in this application.

[0198] See also Fig.14 , Fig.14 is a flow chart of a service construction method provided in an embodiment of the present application. The service construction method can be based on Fig.13 The method is implemented by the architecture shown in the figure, and the method comprises at least the following steps:

[0199] Step S1401: Designing node orchestration to construct target service components of a service instance.

[0200] Specifically, the design node can receive input operations such as user selection or dragging, and arrange the target service components for building the service instance according to the input operations. Alternatively, the design node can automatically establish the connection relationship between multiple service components according to the components required by the service instance required by the user, and obtain the target service components for building the service instance.

[0201] Optionally, the design interface provides multiple service components, including one or more of computing components, storage components, network components, elastic scaling components, cross-cloud orchestration components, IT service components, etc., and the target service component is one or more of the multiple service components. Optionally, the computing component specifically includes one or more of elastic cloud servers, bare metal servers, etc., the storage component includes cloud hard disk components, etc.; the network component includes elastic load balancing (ELB) components and elastic Internet Protocol (EIP) components, etc.; the elastic scaling component specifically includes resource group components and scaling group components, etc.

[0202] Furthermore, each service component can be combined to obtain a new service component. For example, one or more elastic cloud server components can be added to the scaling group component in the elastic scaling component. After being deployed as a service instance, the scaling group can adjust the bandwidth resources between elastic cloud servers, etc. For another example, the cloud hard disk component can be mounted in the computing component (such as the virtual machine component or elastic cloud server, etc.) to provide storage for the computing component.

[0203] In one possible design, the cross-cloud orchestration component is used to orchestrate public cloud resources. The cross-cloud orchestration component can be used as a container, and users can define the corresponding service components of public cloud resources in the cross-cloud orchestration component. In this way, public cloud resources (such as servers in the public cloud) and private cloud resources (such as databases in the private cloud) can be combined in the same service instance according to business scenarios to achieve cross-cloud orchestration, improve the compatibility and diversity of services, and meet the needs of users to connect public cloud resources and private cloud resources. For details, please refer to step S301 about Figure 6 The description of this is not repeated here.

[0204] Optionally, the design interface provides multiple service components including information technology (IT) service components, where IT services are services such as hardware integration, software applications, and software and hardware integration solutions provided by service providers in the field of information technology to their users. It can be seen that by using IT services as service components, the IT capabilities provided by cloud service providers can be built into online services and applied to cloud computing, enriching the IT capability service ecosystem.

[0205] Further optionally, the service builder receives IT service information input by the user, wherein the IT service information includes API information. The service builder generates the IT service component according to the IT service information. For details, see step S601. Figure 7 The relevant description of this application will not be repeated here.

[0206] Specifically, Figure 4 As shown, among the multiple service components provided by the design interface, each service component corresponds to a service (or resource), and the user can visually arrange these service components to obtain the target service component that meets their needs. For a detailed description, please refer to step S301 for Figure 4 The description of , this application will not repeat it again.

[0207] Optionally, the design node can also generate a first service template based on the target service component and the configuration items of the target service component. Furthermore, when the design node saves the template, the configuration items of the target service component can be classified, for example, into specification items and parameter items. Among them, a group of configuration items provided for external selection is a specification item, and the specification name is defined. For example: images, specifications, available partitions, system disk size, etc. are classified as specifications. Configuration items associated with business significance are called parameters, for example: virtual machine usernames and passwords are classified as account information groups. Further optionally, when saving the template, the name, description, icon, etc. of the template can also be defined. See Fig.15 , Fig.15 This is a possible interface diagram for saving a template provided by an embodiment of the present application. In area 1501, the design node can receive user input, selection and other operations, and define the name, description, icon and the like of the template according to the user's input operation. Referring to areas 1502 and 1503, the design node can receive user input, selection and other operations, and determine the specification items and parameter items of the configuration items according to the user's input operations.

[0208] Optionally, the service construction method further includes step S1402, which is as follows:

[0209] Step S1402: The design node submits the target service component to the management node. The optional here can be understood as the design node can perform this step or not, for example, the design node can submit the target service component to the service template database, and the management node can also pull the target service component from the service template database.

[0210] Specifically, the design node can send the target service component to the management node through the communication interface, and can also copy the target service component to the management node through a readable storage medium. Correspondingly, the management node receives the target service component submitted by the design node.

[0211] Optionally, the design node may send a first service template to the management node, where the first service template includes a target service component. Accordingly, the management node receives the first service template, thereby acquiring the target service component.

[0212] Step S1403: The configuration node determines the target service component on which the service instance is based, the configuration information of the service instance, and the first approval process.

[0213] Specifically, the configuration node may obtain the target service component from the management node, select the target service component by default to generate the service instance, or receive a user input (or selection) operation to determine to generate the service instance according to the target service component.

[0214] Optionally, the management node may send at least one template to the configuration node, wherein the at least one template includes a first service template, and the first service template includes a target service component. The configuration node may further determine, from the at least one service template, to construct a service instance based on the first service template. For example, the configuration node provides the multiple templates to the user, and the user selects a template based on which the service instance to be constructed is based according to his or her own needs; the configuration node receives the user's selection operation for the first service template, thereby determining to construct a service instance based on the first service template.

[0215] The configuration information of the service instance can be default, or it can be received from user input, or it can be obtained from the network side device through the communication interface. The configuration information includes the specification data of the service instance, and the parameter data of the service instance or the definition rules of the parameter data. The data value corresponding to the specification information is called specification data, and the data value corresponding to the parameter information is called parameter data. Optionally, a set of data provided for selection is specification information, such as: image, specification, available partition, system disk size, etc., and a set of data is usually provided for selection, so it is called specification parameters. The information that can be freely defined by the configuration node or user device is called parameter information, for example: virtual machine user name, password, subnet information, etc. are called parameter information.

[0216] Further optionally, the definition rule of the parameter data is used to indicate the user (or user role) who defines the parameter or the device that defines the parameter. For example, the present application provides three definition rules as examples: administrator definition, user device definition, and approval node definition. Specifically, the definition rule is the parameter defined by the administrator, and the parameter data is filled in when the administrator builds the service instance. For example: the virtual machine name can be included in the configuration information when building the service instance. The definition rule is the parameter of the user device, and the parameter data is filled in with the parameter value when the user applies for the service. For example, the password entered when using the service instance. The definition rule is the parameter defined by the approval node, and the parameter value can be filled in by the approval node during the approval process. Furthermore, when the approval process includes multiple approval nodes, a specific approval node can also be specified to determine the parameter value. For example: the second-level approval node in the secondary approval determines the subnet information associated with the network card.

[0217] Optionally, the configuration node may associate the service instance with a first approval process, and the approval process is used to approve a request to use the service instance. When the service instance is associated with the first approval process, when a user submits a request to use the service instance, the request can be pushed to the approval node. When the request for the service instance is approved, the instance can be deployed for the user to use, thereby combining the service application process with the approval process, reducing the steps for users to apply for services and improving the user experience.

[0218] Further optionally, the configuration node may obtain information of at least one approval process, wherein the information of the at least one approval process includes information of the first approval process. The configuration node may receive a selection operation for the first approval process determined by the user from multiple approval processes, thereby associating the service instance with the first approval process.

[0219] The interface provided by the configuration node can be found in Figure 8 For related description, please refer to step S302. Figure 8 The corresponding description is not repeated here.

[0220] Optionally, the configuration node may also receive the user's introduction information or description information of the service instance, and generate an introduction page or description page for the service instance. Further, the introduction page or description page may also serve as an entry for the user to apply for the service instance. For details, see step S202. Fig.10 , Fig.11 as well as Fig.12 The description is not repeated here.

[0221] Step S1404: the configuration node submits the configuration information and the information indicating the first approval process to the management node.

[0222] Specifically, the configuration node may send the configuration information and the information indicating the first approval process to the management node through the communication interface, and may also copy the configuration information and the information indicating the first approval process to the management node through a readable storage medium. Accordingly, the management node receives the configuration information and the information indicating the first approval process submitted by the configuration node. Of course, if the service instance has no associated process, the information indicating the first approval process is not included in the information submitted by the configuration node.

[0223] Optionally, the information indicating the first approval process may be a name, number or identification (ID) of the first approval process.

[0224] Optionally, the configuration node may also send indication information of the target service component to the management node, so that the management node can determine the target service component based on the service instance. Further optionally, the configuration node may send indication information of the first service template to the management node, so that the server can determine the first service template based on the service instance.

[0225] Step S1405: The management node constructs a service instance based on the target service component, configuration information and the first approval process.

[0226] The service instance is used for the user device to use the resources corresponding to the target service component. Specifically, the management node constructs the service instance through the target service component, so that the atomic service can be constructed into a combined service instance for the user device to use.

[0227] Specifically, the service (or resource) in the service instance is the service (or resource) indicated by the target service component. For example, if the service template includes a web server component and a reverse proxy server component, the generated service instance includes a web server and a reverse proxy server.

[0228] For example, if the target service component is Figure 4 Taking the target service component shown as an example, the generated service instance can be a composite service of WordPress (a platform developed based on the PHP language). The service instance of the composite service of WordPress includes a group of elastic cloud servers deployed with WordPress, a group of elastic cloud services deployed with database nodes, a server deployed with Nginx, and related network resources of ELP and EIP.

[0229] Optionally, after the management node receives the target service component on which the service instance is based and the configuration information of the service instance (or also includes information indicating the first approval process), the management node can store the aforementioned information and register the operation link of the service instance (when there is information indicating the first approval process, the first approval process needs to be associated). Furthermore, the service instance is put online in the service directory, that is, the service instance is added to the list of service instances for easy user access.

[0230] Optionally, the service construction method further includes part or all of steps S1406 to S1409, and steps S1406 to S1409 are specifically as follows:

[0231] Step S1406: The management node receives a request from the user equipment to apply for using a service instance.

[0232] Specifically, the user device can apply for the use of the service instance, and the management node receives the user's request for the use of the service instance and deploys the service for the user. Optionally, the management node can send a list of service instances to the user device, and the user of the user device browses the list and selects the corresponding service instance to apply for according to his own needs. The management node receives the user device's request for the service instance and deploys the service instance for the user to use (in the case of an associated approval process, the service builder needs to confirm the approval before deploying the service instance).

[0233] In a possible implementation, the user device outputs a page containing multiple service instances, or outputs a list of multiple service instances, and receives the service instance selected or input by the user to apply for. Further, the user submits a request to confirm the application for the service instance to the management node, and the management node receives the request to apply for the service instance.

[0234] Optionally, the request may also include other information, for example, information related to the application filled in by the user through the user device, such as: application department, application application, applicant, etc. Further, the user selects specifications according to business requirements through the user device, for example: the web server selects specification 1 (e.g. 1U2G, disk 32GB).

[0235] Optionally, the request may also include parameter data input or selected by the user (for example, the parameter may be a user-defined type of parameter defined by the rule), such as a virtual machine password. The user device may also support the user to input other information, such as supporting uploading a screenshot of the email from the IT department agreeing to apply for the service instance, a description of the purpose of use, etc.

[0236] Step S1407: the management node sends the request to the approval node.

[0237] Specifically, the management node receives a request from a user device to apply for a service instance, and pushes the request to the approval node. Correspondingly, the approval node receives the request sent by the management node, approves the request, and returns an approval result (information indicating whether the approval is passed) to the management node.

[0238] Step S1408: The approval node feeds back the approval result to the management node.

[0239] Specifically, the approval node feeds back the approval result to the management node, and correspondingly, the management node receives the approval result fed back by the approval node.

[0240] In a possible design, the approval result can be indicated by a field in the message. The value of the field is "1" indicating that the approval is passed, and the value of the field is "0" indicating that the approval is not passed.

[0241] Optionally, the approval node also receives the parameters entered during the approval process filled in by the approver. For example, the approver selects a subnet allocation IP suitable for the department based on the applicant's department and the evidence screenshot. Furthermore, the approval node submits the parameters entered during the approval process to the management node.

[0242] Step S1409: After approval, the management node deploys the service instance for use by the user equipment.

[0243] Optionally, the management node may determine whether the approval is passed according to the approval result, thereby deploying the service instance for use by the user device.

[0244] For example, after approval, the management node provides the entry of the deployed service instance to the user device, and the user device can use the deployed service instance through the entry provided by the management node.

[0245] exist Fig.14 In the illustrated embodiment, the design node provides multiple service components in the design interface. These service components correspond to resources. Users can visually arrange these service components in the design node to obtain target service components that meet their needs. The management node constructs service instances through target service components and configuration information, so that atomic services can be constructed into combined service instances for use by user devices. In this way, you only need to arrange multiple service components required for the service instance in the design interface to automatically generate a service instance containing multiple service components, without having to apply for resources separately and then combine them, which improves the efficiency of service construction.

[0246] Furthermore, the service instance is associated with a first approval process. When a user submits a request to apply for the use of a service instance, the request can be pushed to an approval node. When the request for the service instance is approved, the instance can be deployed for user use, thereby combining the service application process and the approval process, reducing the steps for users to apply for services and improving user experience.

[0247] The method of the embodiment of the present application is described in detail above, and the device of the embodiment of the present application is provided below.

[0248] See also Fig.16 , Fig.16 is a schematic diagram of the structure of a service construction device 160 provided in an embodiment of the present application. The service construction device 160 may be Figure 3 The service builder in the illustrated embodiment may also be a module in the service builder, such as a chip or an integrated circuit. The service building device 130 is used to implement the aforementioned service building method, such as Figure 3 The illustrated embodiment describes a method for constructing a service.

[0249] Further, the service construction device 160 may include a communication unit 1601 and a processing unit 1602, wherein each unit is described in detail as follows:

[0250] The communication unit 1601 is used to obtain a target service component arranged by a user in a design interface, wherein the design interface provides multiple service components, and the multiple service components include a computing component, a storage component, and a network component; the target service component is one or more of the multiple service components;

[0251] The processing unit 1602 is configured to construct a service instance according to the target service component, where the service instance is used for the user equipment to use resources corresponding to the target service component.

[0252] In an embodiment of the present application, the above-mentioned device 160 provides multiple service components in the design interface. These service components correspond to resources, and users can visually arrange these service components to obtain target service components that meet their own needs. The above-mentioned device obtains the target service components arranged by the user, and builds service instances through the target service components, so that the atomic services can be built into combined service instances for use by user devices. In this way, it is only necessary to arrange the multiple service components required for the service instance in the design interface, and the above-mentioned device 160 can automatically generate a service instance containing multiple service components, without the need for users to apply for resources separately and then combine them, thereby improving the efficiency of service construction. On the other hand, users can arrange service components according to their own needs, so as to obtain customized service instances through the service builder, meet the user's needs for diversified service instances, and improve the user experience.

[0253] Furthermore, the multiple service components include computing components, storage components and network components. When it is necessary to build a service suitable for running a web page (website or simply web) application (hereinafter referred to as a web service or web service), the architecture of the web service can be quickly obtained by quickly combining the computing components, storage components and network components, thereby improving the efficiency of building the web service.

[0254] In a possible implementation, the multiple service components further include a cross-cloud orchestration component.

[0255] The cross-cloud orchestration component is used to orchestrate public cloud resources. The cross-cloud orchestration component can be used as a container, and users can define the corresponding service components of public cloud resources in the cross-cloud orchestration component. In this way, public cloud resources (such as servers in the public cloud) and private cloud resources (such as databases in the private cloud) can be combined in the same service instance according to business scenarios to achieve cross-cloud orchestration, improve the compatibility and diversity of services, and meet the needs of users to connect public cloud resources and private cloud resources.

[0256] In yet another possible implementation, the multiple service components further include IT service components.

[0257] Among them, IT services are services such as hardware integration, software applications, and hardware and software integration solutions provided by service providers in the field of information technology to their users. It can be seen that by taking IT services as service components, the IT capabilities provided by cloud service providers can be built into online services and applied to cloud computing, enriching the IT capability service ecosystem.

[0258] In yet another possible implementation, the communication unit is further configured to receive IT service information input by a user, wherein the IT service information includes application program interface API information;

[0259] The processing unit is further configured to generate the IT service component according to the information of the IT service.

[0260] In another possible implementation, the computing component specifically includes one or more of an elastic cloud server component, a bare metal server component, etc.; the storage component includes a cloud hard disk component, etc.; the network component includes an elastic load balancing component and an elastic Internet Protocol EIP component, etc.

[0261] In another possible implementation, the target service components specifically include a web server component, a database component, a reverse proxy server component, an elastic load balancing ELB component, and an elastic internet protocol EIP component; wherein the web server component, the database component, and the reverse proxy server component are obtained based on the computing component, and the elastic load balancing component and the elastic internet protocol belong to the network component.

[0262] In one possible design, the user can deploy a reverse proxy server program (such as Nginx program) in the elastic cloud server component to obtain a reverse proxy server component. In another possible design, the user can deploy a web service program in the elastic cloud server to obtain a web server.

[0263] In yet another possible implementation, the processing unit 1602 is further configured to:

[0264] Determine configuration information of the service instance; the configuration information includes specification data of the service instance, and parameter data of the service instance or definition rules of parameter data;

[0265] The service instance is constructed according to the target service component and the configuration information of the service instance.

[0266] The configuration information may specifically include specification information and parameter information. The data value corresponding to the specification information is called specification data, and the data value corresponding to the parameter information is called parameter data. Optionally, a set of data provided for selection is the specification information, such as image, specification, available partition, system disk size, etc. Usually a set of data is provided for selection, so it is called specification parameters. The information that can be freely defined by the configuration node or user device is called parameter information, such as the virtual machine user name, password, subnet information, etc. are called parameter information.

[0267] In yet another possible implementation, the definition rule of the parameter data is one of a plurality of definition rules; the plurality of definition rules include administrator definition, user device definition, and approval node definition.

[0268] Specifically, the definition rule is a parameter defined by the administrator, and the parameter data is filled in when the administrator builds the service. For example, the virtual machine name can be included in the information when building the service. Furthermore, the definition rule can also include whether to hide the parameter, thereby shielding the parameters that the user does not care about, thereby reducing the complexity of the page when the user applies for the service.

[0269] The definition rule is the parameter of the user's device, and the parameter data is filled in when the user applies for the service. For example, the password required to use the service.

[0270] Define the parameters defined by the rules for the approval node, and fill in the parameter values ​​during the approval process. Furthermore, when the approval process includes multiple approval nodes, you can also specify a specific approval node to determine the parameter value. For example: the second-level approval node in the second-level approval determines the subnet information associated with the network card.

[0271] In yet another possible implementation, the processing unit 1602 is further configured to:

[0272] The service instance is associated with a first approval process, where the approval process is used to approve a request for using the service instance.

[0273] Currently, there is a lack of enterprise organizational processes in cloud computing services, resulting in the inability to adapt to enterprise organizational processes during use. For example, Department A of Enterprise needs to use a computing resource with 8G of memory to run a program. It needs to apply for a process internally and wait for approval before applying for or purchasing computing resources from the cloud computing provider. This method of using cloud services is relatively cumbersome and the efficiency of applying for services is slow, which affects the user experience. In an embodiment of the present application, a service instance is associated with a first approval process. When a user submits a request to apply for the use of a service instance, the request can be pushed to the approval node. When the request for the service instance is approved, the instance can be deployed for user use, thereby combining the service application process with the approval process, reducing the steps for users to apply for services, and improving the user experience.

[0274] It can be understood that in the various device embodiments of the present application, the division of multiple units or modules is only a logical division based on function, and is not intended to limit the specific structure of the device. In a specific implementation, some functional modules may be subdivided into more small functional modules, and some functional modules may be combined into one functional module, but regardless of whether these functional modules are subdivided or combined, the general process executed in the service construction process is the same. For example, the communication unit in the above-mentioned device 160 can also be specifically divided into a receiving unit and a sending unit, the receiving unit is used to implement the function of receiving data in communication, and the sending unit is used to implement the function of sending data in communication. Usually, each unit corresponds to its own program code (or program instruction), and when the program code corresponding to each of these units runs on the processor, the unit is controlled by the processing unit to execute the corresponding process to achieve the corresponding function.

[0275] See also Fig.17 , Fig.171 is a schematic diagram of the structure of a service construction device 170 provided in an embodiment of the present application. The service construction device 170 may include at least one memory 1701, at least one processor 1702, and a communication interface 1704. Optionally, a bus 1703 may also be included, wherein the memory 1701, the processor 1702, and the communication interface 1704 are connected via the bus 1703.

[0276] The memory 1701 is used to provide a storage space, and the storage space can store data such as an operating system and computer instructions. The memory 1701 can be a random access memory (RAM), a read-only memory (ROM), an erasable programmable read only memory (EPROM), or a portable read only memory (compact disc read-only memory, CD-ROM), etc., or a combination of multiple thereof.

[0277] Processor 1702 is a module that performs arithmetic operations and / or logical operations, and may specifically be a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor unit (MPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a complex programmable logic device (CPLD), or a combination of one or more of the processing modules.

[0278] The communication interface 1704 is used to receive data sent externally and / or send data externally, and may be a wired link interface including an Ethernet cable, etc., or a wireless link interface (Wi-Fi, Bluetooth, general wireless transmission, vehicle-mounted short-range communication technology, etc.). Optionally, the communication interface 1304 may also include a transmitter (such as a radio frequency transmitter, an antenna, etc.) coupled to the interface, or a receiver, etc.

[0279] The processor 1702 in the service construction device 170 is used to read the computer instructions stored in the memory 1701 to execute the aforementioned service construction method, for example Figure 3 The service construction method described in the illustrated embodiment.

[0280] For example, the service construction device 170 may be Figure 3 In the service builder of the illustrated embodiment, the processor 1702 in the service building device 170 is used to read the computer instructions stored in the memory 1701, and to perform the following operations:

[0281] Acquire a target service component arranged by a user in a design interface, wherein the design interface provides a plurality of service components, the plurality of service components including a computing component, a storage component, and a network component; the target service component is one or more of the plurality of service components;

[0282] A service instance is constructed according to the target service component, and the service instance is used for user equipment to use resources corresponding to the target service component.

[0283] In an embodiment of the present application, the above-mentioned device provides multiple service components in the design interface. These service components correspond to resources, and users can visually arrange these service components to obtain target service components that meet their own needs. The above-mentioned device obtains the target service components arranged by the user, and builds service instances through the target service components, so that the atomic services can be built into combined service instances for use by user devices. In this way, it is only necessary to arrange the multiple service components required for the service instance in the design interface, and the above-mentioned device can automatically generate a service instance containing multiple service components without the need for users to apply for resources separately and then combine them, thereby improving the efficiency of service construction. On the other hand, users can arrange service components according to their own needs, so as to obtain customized service instances through the service builder, meet the user's needs for diversified service instances, and improve the user experience.

[0284] Furthermore, the multiple service components include computing components, storage components and network components. When it is necessary to build a service suitable for running a web page (website or simply web) application (hereinafter referred to as a web service or web service), the architecture of the web service can be quickly obtained by quickly combining the computing components, storage components and network components, thereby improving the efficiency of building the web service.

[0285] In a possible implementation, the multiple service components further include a cross-cloud orchestration component.

[0286] The cross-cloud orchestration component is used to orchestrate public cloud resources. The cross-cloud orchestration component can be used as a container, and users can define the corresponding service components of public cloud resources in the cross-cloud orchestration component. In this way, public cloud resources (such as servers in the public cloud) and private cloud resources (such as databases in the private cloud) can be combined in the same service instance according to business scenarios to achieve cross-cloud orchestration, improve the compatibility and diversity of services, and meet the needs of users to connect public cloud resources and private cloud resources.

[0287] In yet another possible implementation, the multiple service components further include IT service components.

[0288] Among them, IT services are services such as hardware integration, software applications, and hardware and software integration solutions provided by service providers in the field of information technology to their users. It can be seen that by taking IT services as service components, the IT capabilities provided by cloud service providers can be built into online services and applied to cloud computing, enriching the IT capability service ecosystem.

[0289] In yet another possible implementation, the processor 1702 is further configured to:

[0290] Receiving IT service information input by a user through the communication interface 1704, wherein the IT service information includes application program interface API information;

[0291] The IT service component is generated according to the information of the IT service.

[0292] In another possible implementation, the computing component specifically includes one or more of an elastic cloud server component, a bare metal server component, etc.; the storage component includes a cloud hard disk component, etc.; the network component includes an elastic load balancing component and an elastic Internet Protocol EIP component, etc.

[0293] In another possible implementation, the target service components specifically include a web server component, a database component, a reverse proxy server component, an elastic load balancing ELB component, and an elastic internet protocol EIP component; wherein the web server component, the database component, and the reverse proxy server component are obtained based on the computing component, and the elastic load balancing component and the elastic internet protocol belong to the network component.

[0294] In one possible design, the user can deploy a reverse proxy server program (such as Nginx program) in the elastic cloud server component to obtain a reverse proxy server component. In another possible design, the user can deploy a web service program in the elastic cloud server to obtain a web server.

[0295] In yet another possible implementation, the processor 1702 is further configured to:

[0296] Determine configuration information of the service instance; the configuration information includes specification data of the service instance, and parameter data of the service instance or definition rules of parameter data;

[0297] The service instance is constructed according to the target service component and the configuration information of the service instance.

[0298] The configuration information may specifically include specification information and parameter information. The data value corresponding to the specification information is called specification data, and the data value corresponding to the parameter information is called parameter data. Optionally, a set of data provided for selection is the specification information, such as image, specification, available partition, system disk size, etc. Usually a set of data is provided for selection, so it is called specification parameters. The information that can be freely defined by the configuration node or user device is called parameter information, such as the virtual machine user name, password, subnet information, etc. are called parameter information.

[0299] In yet another possible implementation, the definition rule of the parameter data is one of a plurality of definition rules; the plurality of definition rules include administrator definition, user device definition, and approval node definition.

[0300] Specifically, the definition rule is a parameter defined by the administrator, and the parameter data is filled in when the administrator builds the service. For example, the virtual machine name can be included in the information when building the service. Furthermore, the definition rule can also include whether to hide the parameter, thereby shielding the parameters that the user does not care about, thereby reducing the complexity of the page when the user applies for the service.

[0301] The definition rule is the parameter of the user's device, and the parameter data is filled in when the user applies for the service. For example, the password required to use the service.

[0302] Define the parameters defined by the rules for the approval node, and fill in the parameter values ​​during the approval process. Furthermore, when the approval process includes multiple approval nodes, you can also specify a specific approval node to determine the parameter value. For example: the second-level approval node in the second-level approval determines the subnet information associated with the network card.

[0303] In yet another possible implementation, the processor 1702 is further configured to:

[0304] The service instance is associated with a first approval process, where the approval process is used to approve a request for using the service instance.

[0305] Currently, there is a lack of enterprise organizational processes in cloud computing services, resulting in the inability to adapt to enterprise organizational processes during use. For example, Department A of Enterprise needs to use a computing resource with 8G of memory to run a program. It needs to apply for a process internally and wait for approval before applying for or purchasing computing resources from the cloud computing provider. This method of using cloud services is relatively cumbersome and the efficiency of applying for services is slow, which affects the user experience. In an embodiment of the present application, a service instance is associated with a first approval process. When a user submits a request to apply for the use of a service instance, the request can be pushed to the approval node. When the request for the service instance is approved, the instance can be deployed for user use, thereby combining the service application process with the approval process, reducing the steps for users to apply for services, and improving the user experience.

[0306] The present application also provides a computer-readable storage medium in which computer instructions are stored. When the computer instructions are executed on one or more processors, Figure 3 or Fig.14 The service construction method described in the illustrated embodiment.

[0307] The embodiment of the present application also provides a chip system, which includes at least one processor, a memory and an interface circuit, wherein the interface circuit is used to provide information input / output for at least one processor, and the at least one memory stores computer instructions, and when the computer instructions are executed on one or more processors, the chip system is realized. Figure 3 or Fig.14 The service construction method described in the illustrated embodiment.

[0308] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer instruction product. The computer instruction product includes one or more computer instructions. When the computer instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application can be implemented 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 instruction can be stored in a computer-readable storage medium or transmitted via a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrations. Available media can be magnetic media, (e.g., floppy disk, hard disk, tape), optical media (e.g., DVD), or semiconductor media (e.g., solid state disk (SSD)), etc.

[0309] The steps in the method embodiments of the present application can be adjusted in order, combined, and deleted according to actual needs.

[0310] The modules in the device embodiment of the present application can be merged, divided and deleted according to actual needs.

Claims

1. A service construction method, characterized in that: include: Obtaining a target service component arranged by a user in a design interface, wherein the design interface provides multiple service components, the multiple service components including a computing component, a storage component, and a network component; the target service component is one or more of the multiple service components; Determining configuration information of a service instance, the configuration information including definition rules of parameter data of the service instance, the definition rules of the parameter data being used to indicate a user or device that defines parameters of the service instance, the definition rules including one of administrator definition, user definition, and approval node definition; Constructing a service instance according to the target service component and the configuration information of the service instance, wherein the service instance is used for allowing the user device to use resources corresponding to the target service component; The service instance is associated with a first approval process, where the first approval process is used to approve a request for using the service instance, and the first approval process is approved at the approval node.

2. The method according to claim 1, wherein The multiple service components also include a cross-cloud orchestration component and an information technology (IT) service component; wherein the cross-cloud orchestration component is used to orchestrate public cloud resources.

3. The method according to claim 2, characterized in that The method further comprises: Receiving IT service information input by a user, wherein the IT service information includes application program interface (API) information; The IT service component is generated according to the information of the IT service.

4. The method according to any one of claims 1 to 3, characterized in that The target service components specifically include a web server component, a database component, a reverse proxy server component, an elastic load balancing ELB component and an elastic internetworking protocol EIP component; wherein the web server component, the database component and the reverse proxy server component are obtained based on the computing component, and the elastic load balancing component and the elastic internetworking protocol belong to the network component.

5. The method according to any one of claims 1 to 3, characterized in that The configuration information also includes specification data of the service instance and parameter data of the service instance.

6. A service construction method, characterized in that: include: Design nodes to obtain multiple service components from management nodes; The plurality of service components include a computing component, a storage component, and a network component; The design node orchestrates a target service component for constructing a service instance based on the multiple service components; The design node submits the target service component to the management node; The configuration node determines the target service component on which the service instance is based, configuration information of the service instance, and a first approval process associated with the service instance, and submits the configuration information of the service instance and information indicating the first approval process to the management node; the configuration information includes specification data of the service instance, and parameter data of the service instance or definition rules of the parameter data, the definition rules of the parameter data are used to indicate a user or device that defines parameters of the service instance, the definition rules include one of administrator definition, user definition, and approval node definition, and the first approval process is approved at the approval node; The management node constructs the service instance based on the target service component, the configuration information of the service instance, and the information indicating the first approval process, so that the user equipment can use resources corresponding to the target service component.

7. The method according to claim 6, characterized in that The multiple service components also include a cross-cloud orchestration component and an information technology (IT) service component; wherein the cross-cloud orchestration component is used to orchestrate public cloud resources.

8. The method according to claim 7, characterized in that The method further comprises: The management node obtains IT service information input by the user, wherein the IT service information includes application program interface (API) information; The management node generates the IT service component according to the information of the IT service.

9. The method according to any one of claims 6 to 8, characterized in that: The target service components specifically include a web server component, a database component, a reverse proxy server component, an elastic load balancing ELB component and an elastic internetworking protocol EIP component; wherein the web server component, the database component and the reverse proxy server component are obtained based on the computing component, and the elastic load balancing component and the elastic internetworking protocol belong to the network component.

10. The method according to any one of claims 6 to 8, characterized in that: After the design node orchestrates a target service component for constructing a service instance based on the multiple service components, the design node further includes: The design node determines the configuration items of the target service component, where the configuration items are used to describe properties for constructing the target service component; The design node determines a first service template, where the first service template includes the target service component and configuration items of the target service component.

11. The method according to claim 10, characterized in that The configuration node determines the target service component based on the service instance, the configuration information of the service instance, and the first approval process associated with the service instance, including: The configuration node obtains at least one service template and indication information of at least one process from the management node; the at least one service template includes the first service template; the indication information of the at least one process includes information for indicating the first approval process; The configuration node determines, from the at least one service template, to construct a service instance based on the first service template, where the first service template includes the target service component and configuration items of the target service component; The configuration node receives input configuration information of the service instance and a first approval process associated with the first service.

12. The method according to any one of claims 6 to 8, characterized in that After the management node constructs the service instance based on the target service component, the configuration information of the service instance, and the information indicating the first approval process, the method further includes: The management node receives a request sent by the user equipment to apply for using the service instance; The management node sends the request to the approval node for approval; After approval, the management node deploys the service instance for use by the user equipment.

13. A service construction device, characterized in that: include: a communication unit, configured to obtain a target service component arranged by a user in a design interface, wherein the design interface provides a plurality of service components, the plurality of service components including a computing component, a storage component, and a network component; and the target service component is one or more of the plurality of service components; A processing unit for: Determining configuration information of a service instance, the configuration information including definition rules of parameter data of the service instance, the definition rules of the parameter data being used to indicate a user or device that defines parameters of the service instance, the definition rules including one of administrator definition, user definition, and approval node definition; Constructing a service instance according to the target service component and the configuration information of the service instance, wherein the service instance is used for allowing the user device to use resources corresponding to the target service component; The service instance is associated with a first approval process, where the first approval process is used to approve a request for using the service instance, and the first approval process is approved at the approval node.

14. The device according to claim 13, characterized in that The multiple service components also include a cross-cloud orchestration component and an information technology (IT) service component; wherein the cross-cloud orchestration component is used to orchestrate public cloud resources.

15. The device according to claim 13, characterized in that The target service components specifically include a web server component, a database component, a reverse proxy server component, an elastic load balancing ELB component and an elastic internetworking protocol EIP component; wherein the web server component, the database component and the reverse proxy server component are obtained based on the computing component, and the elastic load balancing component and the elastic internetworking protocol belong to the network component.

16. The device according to claim 14, characterized in that The communication unit is further configured to receive IT service information input by a user, wherein the IT service information includes application program interface (API) information; The processing unit is further configured to generate the IT service component according to the IT service information.

17. The device according to any one of claims 13 to 16, characterized in that The configuration information also includes specification data of the service instance and parameter data of the service instance.

18. A service construction system, characterized in that: The service construction system includes: Design a node, configured to obtain multiple service components from a management node; the multiple service components include computing components, storage components, and network components; The design node is further configured to orchestrate a target service component for constructing a service instance based on the multiple service components; The design node is further configured to submit the target service component to the management node; a configuration node, configured to determine the target service component on which the service instance is based, configuration information of the service instance, and a first approval process associated with the service instance, and submit the configuration information of the service instance and information indicating the first approval process to the management node; the configuration information includes specification data of the service instance, and parameter data of the service instance or definition rules of the parameter data, the definition rules of the parameter data are used to indicate a user or device that defines parameters of the service instance, the definition rules include one of administrator definition, user definition, and approval node definition, and the first approval process is approved at the approval node; The management node is configured to construct the service instance based on the target service component, the configuration information of the service instance, and the information indicating the first approval process, so that the user equipment can use the resources corresponding to the target service component.

19. The system according to claim 18, characterized in that The multiple service components also include a cross-cloud orchestration component and an information technology (IT) service component; wherein the cross-cloud orchestration component is used to orchestrate public cloud resources.

20. The system according to claim 19, wherein: The management node is further configured to: Acquire IT service information input by the user, wherein the IT service information includes application program interface (API) information; The IT service component is generated according to the information of the IT service.

21. The system according to any one of claims 18 to 20, characterized in that: The target service components specifically include web server components, database components, reverse proxy server components, elastic load balancing ELB components and elastic internetworking protocol EIP components; The web server component, the database component and the reverse proxy server component are obtained based on the computing component, and the elastic load balancing component and the elastic internetworking protocol belong to the network component.

22. The system according to any one of claims 18 to 20, characterized in that The design node is also used to: The design node determines the configuration items of the target service component, where the configuration items are used to describe properties for constructing the target service component; The design node determines a first service template, where the first service template includes the target service component and configuration items of the target service component.

23. The system according to claim 22, wherein: The configuration node is specifically used to: Acquire information of at least one service template and at least one process from the management node; the at least one service template includes the first service template; the at least one process information includes the information indicating the first approval process; Determining, from the at least one service template, to construct a service instance based on the first service template, where the first service template includes the target service component and configuration items of the target service component; Receive input configuration information of the service instance and a first approval process associated with the first service.

24. The system according to any one of claims 18 to 20, characterized in that The construction device further includes an approval node, and the management node is further configured to: receiving a request from the user equipment to apply for using the service instance; Sending the request to an approval node for approval; After approval, the service instance is deployed for use by the user equipment.

25. A service builder, characterized in that: The service builder includes a processor and a memory; the processor is configured to execute computer instructions stored in the memory, so that the service builder implements the method according to any one of claims 1 to 5.

26. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to implement the method according to any one of claims 1 to 12.

Citation Information

Patent Citations

  • Service orchestration system and method under cloud operating system

    CN104202416A

  • Network service providing, strategy rule evaluating and service component selecting method and device

    CN105282195A

  • Method and system for implementing configurable process approval

    CN107038533A

  • Service chain scheduling method and device, server and storage medium

    CN108563505A

  • Method for realizing visual kubernets micro service choreography

    CN108681451A