CN111274000A - Service arranging method and device, electronic equipment and storage medium - Google Patents

Abstract

The application discloses a service arranging method, a service arranging device, an electronic device and a computer readable storage medium, wherein the method comprises the following steps: when a service arranging command is received, determining a template of a target assembly corresponding to the service arranging command; wherein the target components include a storage component, a workload component, and a service component; acquiring parameter values of parameters in each template, and acquiring association relations among the target components in the visual components; wherein the incidence relation comprises an incidence relation between the storage component and the work load component and an incidence relation between the work load component and the service component; and creating a chart component template corresponding to each target component by using the parameter values and the association relation, and combining all the chart component templates into a chart template. Therefore, the service arranging method simplifies the service arranging process in the container.

Description

A service orchestration method, device, electronic device and storage medium

technical field

The present application relates to the field of computer technologies, and more particularly, to a service orchestration method and apparatus, an electronic device, and a computer-readable storage medium.

Background technique

Container cloud technology is the latest and hottest technology, and it is more and more widely used. With Google's open source Kubernetes, and the original docker technology, it is more convenient to deploy applications. However, users still need to spend time learning and researching some terms and related technologies of Kubernetes in order to quickly deploy and use containers. To deploy and publish an application on the Kubernetes container cloud platform, the traditional method requires at least first deploying application components, service components, and storage components, and associating applications, services, and storage. The steps are cumbersome. When an application needs to rely on multiple components of Kubernetes, it needs to create deployments, stateful loads, services, storage, etc. step by step. The steps are cumbersome and error prone.

Therefore, how to simplify the service orchestration process in the container is a technical problem that needs to be solved by those skilled in the art.

SUMMARY OF THE INVENTION

The purpose of the present application is to provide a service orchestration method and apparatus, an electronic device and a computer-readable storage medium, which simplify the service orchestration process in a container.

To achieve the above purpose, the present application provides a service orchestration method, including:

When a service orchestration command is received, a template of a target component corresponding to the service orchestration command is determined; wherein, the target component includes a storage component, a workload component, and a service component;

Obtain parameter values of parameters in each of the templates, and obtain an association relationship between each of the target components in the visualization component; wherein the association relationship includes the relationship between the storage component and the workload component. an association relationship, an association relationship between the workload component and the service component;

A chart component template corresponding to each target component is created by using the parameter value and the association relationship, and all the chart component templates are combined into a chart template.

Wherein, creating a chart component template corresponding to each target component by using the parameter value and the association relationship includes:

Using the parsing method corresponding to each parameter to parse each of the parameters to obtain a target parameter value corresponding to each of the target components;

Create a chart component template corresponding to the storage component using the target parameter value corresponding to the storage component;

Create a chart component template corresponding to the workload component by using the target parameter value corresponding to the workload component and the association relationship between the storage component and the workload component;

A chart component template corresponding to the service component is created by using the target parameter value corresponding to the service component and the association relationship between the service component and the workload component.

Wherein, the parameters in each of the templates include mandatory parameters and custom parameters; the use of the parsing method corresponding to each parameter is used to parse each of the parameters to obtain a target parameter value corresponding to each of the target components ,include:

Use the parsing method corresponding to each of the required parameters to parse each of the required parameters, and obtain the target parameter value corresponding to each of the required parameters;

Each of the custom parameters is parsed by using a general parsing method to obtain a target parameter value corresponding to each of the custom parameters.

Wherein, after obtaining the association relationship between each of the target components in the visualization component, the method further includes:

storing the association relationship in a relationship queue;

Correspondingly, after creating the chart component template corresponding to the storage component by using the target parameter value corresponding to the storage component, the method further includes:

The association relationship between the storage component and the workload component, and the association relationship between the workload component and the service component are acquired from the relationship queue.

Wherein, acquiring the parameter value of each of the parameters in the template, and acquiring the association relationship between each of the target components in the visualization component, includes:

Obtain the parameter value of each of the parameters in the template through the input interface, and obtain the association relationship between each of the target components in the visualization component;

The parameter value and the association relationship are encapsulated as yaml data.

Wherein, creating a chart component template corresponding to each target component by using the parameter value and the association relationship includes:

Verify that the yaml data meets the yaml format requirements;

If so, execute the step of creating a chart component template corresponding to each target component by using the parameter value and the association relationship.

Wherein, after all the chart component templates are combined into a chart template, the method further includes:

Upload the chart template to the harbor repository.

To achieve the above purpose, the present application provides a service orchestration device, including:

a determining module, configured to determine, when a service orchestration command is received, a template of a target component corresponding to the service orchestration command; wherein the target component includes a storage component, a workload component and a service component;

an acquisition module, configured to acquire parameter values of parameters in each of the templates, and acquire the association relationship between each of the target components in the visualization component; wherein the association relationship includes the storage component and the work an association relationship between load components, an association relationship between the workload component and the service component;

The creation module is configured to create a chart component template corresponding to each target component by using the parameter value and the association relationship, and combine all the chart component templates into a chart template.

To achieve the above purpose, the present application provides an electronic device, including:

memory for storing computer programs;

The processor is configured to implement the steps of the above-mentioned service orchestration method when executing the computer program.

To achieve the above object, the present application provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above-mentioned service orchestration method are implemented.

It can be seen from the above solutions that a service orchestration method provided by the present application includes: when a service orchestration command is received, determining a template of a target component corresponding to the service orchestration command; wherein the target component includes a storage component, a workload components and service components; obtain parameter values of parameters in each of the templates, and obtain the association relationship between each of the target components in the visualization component; wherein, the association relationship includes the storage component and the work The association relationship between load components, the association relationship between the workload component and the service component; use the parameter value and the association relationship to create a chart component template corresponding to each target component, and put all the The chart component templates are combined into chart templates.

In the service orchestration method provided by this application, the user can drag and drop the template of each component in the visual component, input the parameters in the template, deploy multiple components, and associate the relationship between the multiple components to quickly generate a chart template. It can be seen that the service orchestration method provided by this application can quickly create a corresponding component template and quickly deploy the corresponding component without knowing the cloud platform, and the component can be quickly upgraded as long as some parameters are modified, so that the The use value of cloud platform is higher. The present application also discloses a service orchestration device, an electronic device, and a computer-readable storage medium, which can also achieve the above technical effects.

It is to be understood that the foregoing general description and the following detailed description are exemplary only and do not limit the application.

Description of drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the accompanying drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort. The accompanying drawings are used to provide a further understanding of the present disclosure, and constitute a part of the specification, and together with the following detailed description, are used to explain the present disclosure, but not to limit the present disclosure. In the attached image:

FIG. 1 is a flowchart of a service orchestration method according to an exemplary embodiment;

FIG. 2 is a flowchart of another service orchestration method according to an exemplary embodiment;

3 is a flowchart of a method for defining a component template provided by an application embodiment of the present application;

4 is a flow chart of generating a chart template provided by an application embodiment of the present application;

FIG. 5 is a structural diagram of a service orchestration apparatus according to an exemplary embodiment;

FIG. 6 is a structural diagram of an electronic device according to an exemplary embodiment.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of the present application.

The embodiment of the present application discloses a service orchestration method, which simplifies the service orchestration process in a container.

Referring to FIG. 1 , a flowchart of a service orchestration method according to an exemplary embodiment, as shown in FIG. 1 , includes:

S101: When a service orchestration command is received, determine a template of a target component corresponding to the service orchestration command; wherein the target component includes a storage component, a workload component, and a service component;

In this embodiment, the user can select the desired template of the target component in the visualization component, and can encapsulate the identifier of the target component as a service orchestration command and send it to the back end of the cloud platform. The templates of each component are defined on the backend of the cloud platform, and the components here include storage components, workload components, and service components required to deploy an application. Write a basic template for each component at the back end of the cloud platform, including the minimum startup parameters of each component, that is, the necessary parameters for each component. Users can also add custom parameters to the basic template, which are not specifically limited here.

S102: Acquire parameter values of parameters in each of the templates, and acquire an association relationship between each of the target components in a visualization component; wherein the association relationship includes the relationship between the storage component and the workload component The association relationship between, the association relationship between the workload component and the service component;

In this step, the visual component obtains the template of each component defined in the backend of the cloud platform through the interface on the UI side and displays it. The user can drag and drop multiple components to generate the relationship between components, and fill in the component template information, that is, fill in The parameter value of the parameter in the template.

It can be understood that there is a one-to-many relationship between workload components and storage components, that is, one workload component corresponds to multiple storage components, and service components and workload components have a many-to-one relationship, that is, multiple service components correspond to one job. load components.

S103: Create a chart component template corresponding to each target component by using the parameter value and the association relationship, and combine all the chart component templates into a chart template.

In this step, a chart component template corresponding to each target component is created by using the parameter values obtained from the visual components and the association relationship between the components. Specifically, this step may include: analysing each of the parameters using a parsing method corresponding to each parameter to obtain a target parameter value corresponding to each of the target components; and using the target parameter value corresponding to the storage component to create the creating a chart component template corresponding to the storage component; using the target parameter value corresponding to the workload component and the association relationship between the storage component and the workload component to create a chart component template corresponding to the workload component; using the A chart component template corresponding to the service component is created based on the target parameter value corresponding to the service component and the association relationship between the service component and the workload component. In the specific implementation, the required and inherent parameters in the template are parsed by their corresponding parsing methods, and the user-defined parameters are parsed by the general parsing method, that is, the parsing method corresponding to each parameter is used to parse each parameter. The step of parsing the parameters to obtain the target parameter value corresponding to each of the target components includes: using a parsing method corresponding to each of the required parameters to parse each of the required parameters, and obtain each of the required parameters. Select the target parameter value corresponding to the parameter; use a general analysis method to parse each of the self-defined parameters to obtain the target parameter value corresponding to each of the self-defined parameters, and the above analysis method can be understood as the checksum standardization of the parameters deal with. Add the association relationship between the storage component and the workload component to the template corresponding to the workload component to create a chart component template corresponding to the workload component, and add the association relationship between the service component and the workload component to the template corresponding to the service component , to create the chart component template corresponding to the service component.

Preferably, after acquiring the association relationship between each of the target components in the visualization component, the method further includes: storing the association relationship in a relationship queue; correspondingly, using the target parameter value corresponding to the storage component After creating the chart component template corresponding to the storage component, the method further includes: acquiring the association relationship between the storage component and the workload component, the relationship between the workload component and the service component from the relationship queue association relationship. After this step, the method further includes: uploading the chart template to the harbor warehouse. In the specific implementation, upload the chart template to the harbor warehouse, call the helm side through the command, and deploy the application

In the service orchestration method provided by the embodiment of the present application, the user can drag and drop the templates of each component in the visual component, input the parameters in the template, deploy multiple components, and associate the relationships between the multiple components to quickly generate a chart template. It can be seen that the service orchestration method provided by the embodiment of the present application can quickly create a corresponding component template without knowing the cloud platform, quickly deploy the corresponding component for use, and quickly upgrade the component only by modifying some parameters , making the cloud platform more valuable.

The embodiment of the present application discloses a service orchestration method. Compared with the previous embodiment, the present embodiment further describes and optimizes the technical solution. specific:

Referring to FIG. 2 , a flowchart of another service orchestration method according to an exemplary embodiment, as shown in FIG. 2 , includes:

S201: When receiving a service orchestration command, determine a template of a target component corresponding to the service orchestration command; wherein, the target component includes a storage component, a workload component, and a service component;

S202: Obtain parameter values of parameters in each of the templates through an input interface, and obtain an association relationship between each of the target components in a visualization component;

S203: Encapsulate the parameter value and the association relationship into yaml data.

S204: Verify whether the yaml data meets the yaml format requirements; if so, enter S205;

In this embodiment, the visualization component can encapsulate the parameter values of the parameters in the template and the association relationship between the components into yaml data. The yaml data parsing module verifies whether the data conforms to the yaml format, parses the required and inherent parameters in the template using the corresponding parsing method, and parses the user-defined parameters using the general parsing method. Checksum normalization.

S205: Create a chart component template corresponding to each target component by using the parameter value and the association relationship, and combine all the chart component templates into a chart template.

It can be seen that this embodiment automatically defines templates and parameters for each component through the back-end initialization, and the front-end drags the visual component interaction module to generate component relationships, fill in component parameters, generate yaml format transmission data, and back-end yaml data parsing module Parse the data, pass parameters into the custom template, convert the custom template into a chart template, and deploy the choreographed application through the command deployment module.

An application embodiment provided by the present application is introduced below, which may specifically include the following steps:

Step 1: The cloud platform backend writes a chart template for each component. The chart template contains the minimum startup parameters, as well as component association selectors, etc., and generates a custom template. Define parameters to write a general parsing method, as shown in Figure 3;

Step 2: The UI page provides visual components, where the visual component data is obtained through the backend, the component relationship can be generated by dragging and dropping, and the component parameters are filled in to generate the yaml transmission data;

Step 3: The yaml data parsing module contains the parsing methods for the required and inherent parameters in the template. The yaml data parsing module verifies whether the data is not and in yaml format. Parse the required parameters, and use the general parsing method to parse the user-defined parameters. Generate a storage custom template from the storage component, and put the storage relationship into the relationship queue; get the storage relationship from the relationship queue and put it into the workload, generate a workload custom template, and put the workload dependency into the relationship queue; from the relationship The queue obtains the workload relationship and puts it into the service to generate a service custom template; combine all the custom templates to generate the corresponding chart template, as shown in Figure 4, upload the chart template to the harbor warehouse;

Step 4: The user selects the corresponding template, fills in the basic information, and deploys the application. The deployment module calls the helm side through commands to deploy the application.

A service orchestration apparatus provided by an embodiment of the present application is introduced below, and a service orchestration apparatus described below and a service orchestration method described above may be referred to each other.

Referring to FIG. 5, a structural diagram of a service orchestration apparatus according to an exemplary embodiment, as shown in FIG. 5, includes:

A determination module 501, configured to determine a template of a target component corresponding to the service orchestration command when a service orchestration command is received; wherein the target component includes a storage component, a workload component and a service component;

Obtaining module 502, configured to obtain parameter values of parameters in each of the templates, and obtain an association relationship between each of the target components in a visualization component; wherein the association relationship includes the storage component and the The association relationship between workload components, the association relationship between the workload component and the service component;

The creating module 503 is configured to create a chart component template corresponding to each target component by using the parameter value and the association relationship, and combine all the chart component templates into a chart template.

In the service orchestration device provided by the embodiment of the present application, the user can drag and drop the template of each component in the visual component, input the parameters in the template, deploy multiple components, and associate the relationship between the multiple components to quickly generate a chart template. It can be seen that the service orchestration device provided by the embodiment of the present application can quickly create a corresponding component template and quickly deploy the corresponding component without knowing the cloud platform, and the component can be quickly upgraded only by modifying some parameters , making the cloud platform more valuable.

On the basis of the foregoing embodiment, as a preferred implementation manner, the creation module 503 includes:

a parsing unit, configured to parse each of the parameters by using the parsing method corresponding to each parameter to obtain a target parameter value corresponding to each of the target components;

a first creating unit, used to create a chart component template corresponding to the storage component by utilizing the target parameter value corresponding to the storage component;

a second creating unit, configured to create a chart component template corresponding to the workload component by using the target parameter value corresponding to the workload component and the association relationship between the storage component and the workload component;

a third creating unit, configured to create a chart component template corresponding to the service component by using the target parameter value corresponding to the service component and the association relationship between the service component and the workload component;

A combining unit for combining all the chart component templates into a chart template.

On the basis of the above embodiment, as a preferred implementation, the parameters in each of the templates include mandatory parameters and custom parameters; the parsing unit specifically uses the parsing method corresponding to each of the mandatory parameters Analyze each of the required parameters to obtain the target parameter value corresponding to each of the required parameters; use a general analysis method to parse each of the self-defined parameters to obtain the corresponding value of each of the self-defined parameters. The unit of target parameter value.

On the basis of the above embodiment, as a preferred implementation, it also includes:

a storage module, configured to store the association relationship in a relationship queue;

An extraction module, configured to acquire the association relationship between the storage component and the workload component, and the association relationship between the workload component and the service component from the relationship queue.

On the basis of the above-mentioned embodiment, as a preferred implementation manner, the obtaining module 502 specifically obtains the parameter values of the parameters in each of the templates through the input interface, and obtains the parameter values of each of the target components in the visual component. The relationship between the parameter values and the relationship is encapsulated as a module of yaml data.

On the basis of the above embodiment, as a preferred implementation, it also includes:

The verification module is used to verify whether the yaml data meets the requirements of the yaml format; if so, start the workflow of the creation module 503 .

On the basis of the above embodiment, as a preferred implementation, it also includes:

The upload module is used to upload the chart template to the harbor warehouse.

Regarding the apparatus in the above-mentioned embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be described in detail here.

The present application further provides an electronic device. Referring to FIG. 6 , a structural diagram of an electronic device 600 provided by an embodiment of the present application, as shown in FIG. 6 , may include a processor 11 and a memory 12 . The electronic device 600 may also include one or more of a multimedia component 13 , an input/output (I/O) interface 14 , and a communication component 15 .

Wherein, the processor 11 is used to control the overall operation of the electronic device 600 to complete all or part of the steps in the above-mentioned service orchestration method. The memory 12 is used to store various types of data to support operations on the electronic device 600, such data may include, for example, instructions for any application or method operating on the electronic device 600, and application-related data, Such as contact data, messages sent and received, pictures, audio, video, and so on. The memory 12 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (Static Random Access Memory, SRAM for short), electrically erasable programmable read-only memory ( Electrically Erasable Programmable Read-Only Memory (EEPROM for short), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), read-only Memory (Read-Only Memory, ROM for short), magnetic memory, flash memory, magnetic disk or optical disk. Multimedia components 13 may include screen and audio components. Wherein the screen can be, for example, a touch screen, and the audio component is used for outputting and/or inputting audio signals. For example, the audio component may include a microphone for receiving external audio signals. The received audio signal may be further stored in the memory 12 or transmitted via the communication component 15 . The audio assembly also includes at least one speaker for outputting audio signals. The I/O interface 14 provides an interface between the processor 11 and other interface modules, and the above-mentioned other interface modules may be a keyboard, a mouse, a button, and the like. These buttons can be virtual buttons or physical buttons. The communication component 15 is used for wired or wireless communication between the electronic device 600 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC for short), 2G, 3G or 4G, or a combination of one or more of them, so the corresponding communication component 15 may include: Wi-Fi -Fi module, bluetooth module, NFC module.

In an exemplary embodiment, the electronic device 600 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (Digital Signal Processing) Processing Device (DSPD for short), Programmable Logic Device (PLD for short), Field Programmable Gate Array (FPGA for short), controller, microcontroller, microprocessor or other electronic components , which is used to execute the above-mentioned service orchestration method.

In another exemplary embodiment, there is also provided a computer-readable storage medium comprising program instructions, the program instructions implementing the steps of the above-mentioned service orchestration method when executed by a processor. For example, the computer-readable storage medium can be the above-mentioned memory 12 including program instructions, and the above-mentioned program instructions can be executed by the processor 11 of the electronic device 600 to implement the above-mentioned service orchestration method.

The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same and similar parts between the various embodiments can be referred to each other. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant part can be referred to the description of the method. It should be pointed out that for those of ordinary skill in the art, without departing from the principles of the present application, several improvements and modifications can also be made to the present application, and these improvements and modifications also fall within the protection scope of the claims of the present application.

It should also be noted that, in this specification, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply these entities or operations. There is no such actual relationship or sequence between operations. Moreover, the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article or device that includes a list of elements includes not only those elements, but also includes not explicitly listed or other elements inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element.

Claims (10)

1. A method of service orchestration, comprising:

when a service arranging command is received, determining a template of a target assembly corresponding to the service arranging command; wherein the target components include a storage component, a workload component, and a service component;

acquiring parameter values of parameters in each template, and acquiring association relations among the target components in the visual components; wherein the incidence relation comprises an incidence relation between the storage component and the work load component and an incidence relation between the work load component and the service component;

and creating a chart component template corresponding to each target component by using the parameter values and the association relation, and combining all the chart component templates into a chart template.

2. The service orchestration method according to claim 1, wherein the creating a chart component template corresponding to each target component by using the parameter values and the association relationship comprises:

analyzing each parameter by using an analysis method corresponding to each parameter to obtain a target parameter value corresponding to each target component;

creating a chart component template corresponding to the storage component by using the target parameter value corresponding to the storage component;

creating a chart component template corresponding to the workload component by using the target parameter value corresponding to the workload component and the incidence relation between the storage component and the workload component;

and creating a chart component template corresponding to the service component by using the target parameter value corresponding to the service component and the incidence relation between the service component and the workload component.

3. The service orchestration method according to claim 2, wherein the parameters in each template comprise mandatory and custom parameters; the analyzing each parameter by using the analyzing method corresponding to each parameter to obtain the target parameter value corresponding to each target component includes:

analyzing each requisite parameter by using an analysis method corresponding to each requisite parameter to obtain a target parameter value corresponding to each requisite parameter;

and analyzing each user-defined parameter by using a general analysis method to obtain a target parameter value corresponding to each user-defined parameter.

4. The service orchestration method according to claim 2, wherein after obtaining the association relationship between each of the target components in the visualization component, the method further comprises:

storing the incidence relation into a relation queue;

correspondingly, after the creating the chart component template corresponding to the storage component by using the target parameter value corresponding to the storage component, the method further includes:

and acquiring the association relationship between the storage component and the workload component and the association relationship between the workload component and the service component from the relationship queue.

5. The service orchestration method according to claim 1, wherein the obtaining parameter values of the parameters in each of the templates and obtaining the association relationship between each of the target components in a visualization component comprises:

acquiring parameter values of parameters in each template through an input interface, and acquiring association relations among the target components in the visual components;

and packaging the parameter values and the association relationship into yaml data.

6. The service orchestration method according to claim 5, wherein the creating a chart component template corresponding to each target component by using the parameter values and the association relationship comprises:

verifying whether the yaml data meets the requirements of the yaml format;

and if so, executing the step of creating the chart component template corresponding to each target component by using the parameter values and the association relation.

7. The service orchestration method according to claim 1, wherein after combining all of the chart component templates into a chart template, further comprising:

uploading the chart template to a hardor warehouse.

8. A service orchestration device, comprising:

the determining module is used for determining a template of a target component corresponding to a service arranging command when the service arranging command is received; wherein the target components include a storage component, a workload component, and a service component;

the acquisition module is used for acquiring parameter values of parameters in each template and acquiring the association relation between each target component in the visual components; wherein the incidence relation comprises an incidence relation between the storage component and the work load component and an incidence relation between the work load component and the service component;

and the creating module is used for creating a chart component template corresponding to each target component by using the parameter values and the association relation, and combining all the chart component templates into a chart template.

9. An electronic device, comprising:

a memory for storing a computer program;

a processor for implementing the steps of the service orchestration method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the service orchestration method according to any one of claims 1 to 7.

Images