CN116931961A

CN116931961A - Service operation method and device

Info

Publication number: CN116931961A
Application number: CN202310920651.1A
Authority: CN
Inventors: 王国炎; 朱继永; 刘莹皓; 李俊; 王高原; 许梦龙; 郑紫焰; 沈起帆; 朱恒; 刘雨生; 陈晨
Original assignee: Hundsun Technologies Inc
Current assignee: Hundsun Technologies Inc
Priority date: 2023-07-25
Filing date: 2023-07-25
Publication date: 2023-10-24

Abstract

The specification provides a service operation method and a device, wherein the service operation method comprises the following steps: responding to an operation instruction of a target service, and acquiring target object information and a target service operation component which are pre-deployed and set for the target service; responding to an associated file deployment instruction of a target service, calling a preset customized script, rendering based on target object information to obtain a target object instance, and obtaining a service identifier of the target object instance; and calling a target service operation component, acquiring service data corresponding to the target service based on the service identifier, and operating the target service based on the target object instance and the service data. The method and the device realize that when the service is deployed, the rendering of the target object instance is completed in a tangent plane mode, and the target service is operated based on the target object instance and service data obtained by tangent plane rendering, so that repeated change of an operation logic code of the operation target service is avoided, and the repeatability and maintainability of service operation are improved.

Description

Service operation method and device

Technical Field

The present disclosure relates to the field of internet technologies, and in particular, to a service operation method and apparatus.

Background

With the development of internet technology, services or applications are containerized and deployed on a service platform cluster. Isolation between services is realized, and the services are operated through corresponding object instances and service data. The method realizes the automatic deployment, large-scale scalable expansion, unified management and load balancing of the service, such as K8s platform cluster (Kubernetes platform cluster).

At present, with the expansion of service scale, the function of the running logic code of the service is difficult to timely and accurately adapt to new service demands, and the running logic code deployed on the service platform cluster needs to be changed, however, the running logic code on the service platform cluster is frequently changed according to the new service demands, so that the running logic code on the service platform cluster becomes chaotic, the subsequent running and management are difficult, the service is difficult to uniformly manage, and the repeatability and maintainability of service running are affected. Therefore, a service operation method and device with high repeatability and high maintainability are needed.

Disclosure of Invention

In view of this, the embodiments of the present specification provide a service operation method. The present disclosure also relates to a business operation device, a computing device, and a computer-readable storage medium, which solve the technical drawbacks in the prior art.

Responding to an operation instruction of a target service, and acquiring target object information and a target service operation component which are pre-deployed and set for the target service;

responding to an associated file deployment instruction of a target service, calling a preset customized script, rendering based on target object information to obtain a target object instance, and obtaining a service identifier of the target object instance;

and calling a target service operation component, acquiring service data corresponding to the target service based on the service identifier, and operating the target service based on the target object instance and the service data.

According to a second aspect of embodiments of the present specification, there is provided a service running apparatus, including:

the acquisition module is used for responding to the operation instruction of the target service and acquiring the pre-deployed target object information and the target service operation assembly set for the target service;

the rendering module is configured to respond to the associated file deployment instruction of the target service, call a preset custom script, render the target object instance based on the target object information, and obtain the service identifier of the target object instance;

the operation module is configured to call the target service operation component, acquire service data corresponding to the target service based on the service identifier, and operate the target service based on the target object instance and the service data.

According to a third aspect of embodiments of the present specification, there is provided a computing device comprising:

a memory and a processor;

the memory is configured to store computer executable instructions, and the processor is configured to execute the computer executable instructions to implement the steps of the business operation method described above.

According to a fourth aspect of embodiments of the present specification, there is provided a computer readable storage medium storing computer executable instructions which, when executed by a processor, implement the steps of the business operation method described above.

In one or more embodiments of the present disclosure, in response to an operation instruction of a target service, target object information and a target service operation component set for the target service that are deployed in advance are obtained; responding to an associated file deployment instruction of a target service, calling a preset customized script, rendering based on target object information to obtain a target object instance, and obtaining a service identifier of the target object instance; and calling a target service operation component, acquiring service data corresponding to the target service based on the service identifier, and operating the target service based on the target object instance and the service data. In response to an operation instruction of a target service, target object information and a target service operation component which are arranged in advance and are set for the target service are obtained, a preset custom script is called to render to obtain a target object instance, the purpose that the rendering of the target object instance is completed in a tangent plane mode when the service is deployed is achieved, the service operation component is called, service data corresponding to the target service is obtained based on a service identifier, the target service is operated based on the target object instance and the service data, the purpose that the target service is operated based on the target object instance and the service data obtained by tangent plane rendering when the service is executed is achieved, repeated change of operation logic codes of the operation target service is avoided, and repeatability and maintainability of service operation are improved.

Drawings

FIG. 1 is a flow chart of a method for operating a service according to an embodiment of the present disclosure;

FIG. 2 is a process flow diagram of a method for service operation in a service platform service application orchestration sequence initiation control scenario according to one embodiment of the present disclosure;

fig. 3 is a schematic flow chart of a service operation method applied to a service platform service application arrangement sequence starting control scenario according to an embodiment of the present disclosure;

fig. 4 is a schematic structural diagram of a service running device according to an embodiment of the present disclosure;

fig. 5 is a block diagram of a computing device according to an embodiment of the present disclosure.

Detailed Description

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. This description may be embodied in many other forms than described herein and similarly generalized by those skilled in the art to whom this disclosure pertains without departing from the spirit of the disclosure and, therefore, this disclosure is not limited by the specific implementations disclosed below.

The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that, although the terms first, second, etc. may be used in one or more embodiments of this specification to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first may also be referred to as a second, and similarly, a second may also be referred to as a first, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

First, terms related to one or more embodiments of the present specification will be explained.

K8s platform cluster (Kubernetes platform cluster): k8s is a widely applied business application package management platform, and solves the problem of large-scale deployment after business containerization. Two types of nodes are arranged on the K8s platform cluster: and at least one packet (Pod) is deployed on any Node, at least one service data is operated on any service application packet, and service operation is realized based on the corresponding object instance and the corresponding service data.

CR (user resource object, customResource): the user customizes the resource object, extends the kuberneteseapi, or allows the custom API to be introduced into the resource object of the Kubernetes platform cluster. Defined by a user resource object definition, the execution is controlled by a user resource object Controller (Controller).

CRD (customer resource object definition): the resource object of the Kubernetes platform cluster for operating the user definition is a type definition (Class) comprising the naming, the operation mode, the operation logic and the like of the user resource object. Through the type definition in the CRD, the corresponding service requirement is satisfied.

Operators: the system is a business operation component for a custom resource object, and a control component for the custom resource, which is developed by a developer, comprises a plurality of user resource object controllers, and controls the custom resource object to operate in a desired operation state under the condition that the component is called. The Operator monitors the corresponding resource object instance, obtains the deployment resource object of the corresponding service according to the related information of the resource object instance, and adjusts (adds, deletes and checks) the resource object to meet the service logic requirement. The Operator is also a package in nature with self-management and self-expansion capabilities that automatically update and expand the containers in the package for deploying highly extensible applications.

Helm packet: the method is a management tool of service application packages on a Kubernetes platform cluster, and corresponding processing is completed through operation instructions of Helm packages.

Helm instrument: and the installation operation instruction of the Helm packet is used for installing the Helm packet.

Kustmize: a tool for customizing the Kubernetes platform cluster configuration. It provides the following functional features to accomplish service deployment and operation: generating a resource object, setting a Cross-Cutting field for the resource object, organizing and customizing a resource set. Kustmize may be used as a script path to render a resource object to obtain a resource object instance.

Shell: and when the service deployment is carried out, the called appointed script finishes parameter input.

Kubectl: the instructions provided on Kubernetes are used directly to interoperate with the clusters. kubectl is a resource package tool for creating, updating, and deleting various resource object instances in K8s clusters, such as Job, deployment, service, etc. The following operations can be conveniently performed using Kubectl: creating and deleting resource object instances in the K8s cluster, such as Job, deployment, service and the like; updating and deleting resource object instances in the K8s cluster; configuring and managing various resource object instances in the K8s cluster, such as network, storage and the like; checking and monitoring cluster states; and managing multiple users. In general, kubectl is a very important tool, and can conveniently operate and manage the K8s cluster, so that the reliability and the expandability of the K8s cluster are improved.

kubectliAN_SNly: the deployment instruction of the Kubectl application is a deployment operation instruction of a K8s resource package.

Script path: for describing the location of scripts or programs to be run in a computer system.

Examples: by creating corresponding executable objects for Class (Class) definitions, the result is called an instance.

Workload: such generic resource objects are referred to as Deployment, job, and include user resource objects.

Service application package: refers to a Helm package or YAML file of a stack of resource objects.

At present, the service application on the service platform cluster is realized by adopting a mode of modifying the service code when each function iterates, and one or more embodiments of the present specification provide a method for dynamically expanding the service application function, which reduces the modification of the service code, and independently deposits the technical realization to the bottom layer, thereby improving the simple and convenient performance of the function iterate of the service application.

In the present specification, a service operation method is provided, and the present specification relates to a service operation apparatus, a computing device, and a computer-readable storage medium, which are described in detail in the following embodiments one by one.

Fig. 1 shows a flowchart of a service operation method according to an embodiment of the present disclosure, including the following specific steps:

step 102: and responding to the running instruction of the target service, and acquiring the pre-deployed target object information and the target service running component set for the target service.

The embodiment of the specification is applied to a service platform with service deployment and service execution functions, the service platform forms a service platform cluster by deploying a plurality of nodes, distributed service deployment is realized, and the service platform is realized by sending corresponding operation instructions under the condition of deploying or executing the service, for example, a K8s service platform cluster, a Docker service platform cluster and the like, and the embodiment of the specification takes the K8s service platform cluster as an example. The request end realizes the management of each node on the service platform cluster through the application programming interface of the service platform cluster.

The service is a service application pre-deployed on the service platform cluster and is deployed in the form of a service application package, wherein the service application package comprises a service application framework, a service application interface, a service application routine, service application data and the like, and the service application has corresponding codes. The target service is a service application to be operated. The target service is correspondingly provided with different resource object examples, the corresponding call of the resources on the service platform cluster is completed through the resource object examples, and the different resource object examples are correspondingly provided with different service operation logics. The resource object instance is defined by corresponding object information, the target object information is resource object information corresponding to target business logic, the resource object information comprises naming, running mode, running logic and the like of the target object instance, and the target object information is expressed by YAML format on a K8s business platform cluster.

The service operation component is a resource control component for service operation on the service platform cluster, and the resource object is controlled to process service data according to the object instance so as to realize service operation. The service operation component has the functions of service operation, service data acquisition, object instance monitoring and the like. In the embodiment of the present disclosure, the service operation component takes the controller of the service operation logic, which is an Operator as an example, to implement monitoring and operation of service data of each service on the service platform cluster, including but not limited to: statefulSet, replicaSet, daemonSet, job and user resource objects, etc.

The method comprises the following steps of obtaining target object information and a target service operation component which are pre-deployed and are set for the target service, wherein the specific mode is as follows: and acquiring target object information and a target service operation component which are pre-deployed on a service platform cluster and are set for the target service.

The service platform cluster is a K8s platform cluster, the target service is a service application 1 and a service application 2, and the initial service logic is: starting the service application 1 and simultaneously starting the service application 2, and updating the service logic as follows: the service application 2 is started within N seconds after the service application 1 is started. Responding to an operation instruction of a target service, and acquiring target object information CRD corresponding to updated service logic, which is preset on a K8s platform cluster and aims at the service application 1 and the service application 2: "apiVersion: apps/v1 … … spec: containers: … … "and a target service running component Operator, wherein the target object information CRD contains definitions of service identification replyuid and replyorder fields and a definition of a status field phase of the update service logic.

And responding to the operation instruction of the target service, acquiring pre-deployed target object information and a target service operation component set for the target service, wherein the target object information lays an information foundation for obtaining a target object instance for subsequent rendering, and the target service operation component is subsequent.

Step 104: and responding to the associated file deployment instruction of the target service, calling a preset customized script, rendering based on the target object information to obtain a target object instance, and obtaining the service identification of the target object instance.

The association file of the target service is an association file of the running target service, and comprises a management packet of the target service, a resource packet of the target service and the like, wherein the management packet of the target service comprises: the Helm packet, the resource packet of the target business includes: k8s resource package (resource set YAML file). The relevant file deployment instruction of the target service is a deployment instruction for deploying relevant files of the target service on a service platform cluster, and comprises a management package deployment instruction of the target service and a resource package deployment instruction of the target service, wherein the management package deployment instruction of the target service comprises a HelmInstall instruction, and the resource package deployment instruction of the target service comprises a Kubectl Apply instruction.

The preset customized script is a preset rendering script for rendering the resource object instance, and the preset customized script finishes the corresponding instance rendering in a parameter input mode, so that the field adjustment of the corresponding resource of the service platform cluster is realized. The preset custom script is called in response to the deployment instruction, so that the rendering of the resource object instance is completed in a tangent plane mode. On the K8s service platform cluster, the preset custom script is realized by combining the Kustmize and Shell.

The object instance is a resource object instance in the service platform cluster, which represents an actual physical resource, such as a Pod, a Container (Container), a database instance, etc. Each resource object instance has a corresponding service identifier, which is used for implementing management and monitoring of resource objects in the service platform cluster, for example, the object instance is a corresponding service identifier of a reployuid and/or reployorder. The target object instance is a resource object instance corresponding to the target business logic. The service identifier of the target object instance is used for managing and monitoring the target resource object in the service platform cluster, and can accurately correspond to the service data corresponding to the service on the service platform cluster through the service identifier, wherein the service identifier is predefined in the target object information.

Responding to an associated file deployment instruction of a target service, calling a preset customized script, rendering based on target object information to obtain a target object instance, and obtaining a service identifier of the target object instance, wherein the specific mode is as follows: and responding to the associated file deployment instruction of the target service, calling a preset customized script, rendering based on the target object information through a corresponding script path to obtain a target object instance, and marking the service identifier of the target object instance for the target object instance.

Illustratively, in response to a management package deployment instruction (helm instrument) of the service application 1 and the service application 2, kustmize and Shell are called, a target object instance CR is rendered based on the target object information CRD, and service identifications replyuid and replyorder are marked for the target object instance CR.

And responding to the deployment instruction of the target service, calling a preset customized script, rendering based on the target object information to obtain a target object instance, and obtaining the service identification of the target object instance. Rendering of the target object instance is completed in a tangent plane mode, service identification is obtained, and an index is provided for accurately obtaining service data corresponding to the target service subsequently.

Step 106: and calling a target service operation component, acquiring service data corresponding to the target service based on the service identifier, and operating the target service based on the target object instance and the service data.

The service data corresponding to the target service is operation data of the target service deployed on the service platform cluster, including workload of the target service, data source of the target service, naming space of the target service, external interface of the target service, and the like.

Calling a service operation component, and acquiring service data corresponding to a target service based on a service identifier, wherein the specific mode is as follows: and calling a service operation component, and acquiring service data corresponding to the target service from the service platform cluster based on the service identification. Further, a target service application package is determined from the service platform cluster, and corresponding service data is acquired from the target service application package.

The target business is operated based on the target object instance and the business data, and the specific mode is as follows: and processing the service data based on the target object instance to realize the operation of the target service based on the target service logic.

Illustratively, an Operator component is invoked, a service application package 1 and a service application package 2 are determined from a service platform cluster based on service identifications (replyUId and replyorder), and corresponding service data is acquired from the service application package 1 and the service application package 2: workload 1, workload 2, and workload 3, and based on target object instance CR, workload 1, workload 2, and workload 3 are processed to implement running business application 1 and business application 2 based on updated business logic (starting business application 2 within N seconds after starting business application 1).

In the embodiment of the specification, in response to an operation instruction of a target service, target object information and a target service operation component which are arranged in advance and are set for the target service are obtained; responding to an associated file deployment instruction of a target service, calling a preset customized script, rendering based on target object information to obtain a target object instance, and obtaining a service identifier of the target object instance; and calling a target service operation component, acquiring service data corresponding to the target service based on the service identifier, and operating the target service based on the target object instance and the service data. In response to an operation instruction of a target service, target object information and a target service operation component which are arranged in advance and are set for the target service are obtained, a preset custom script is called to render to obtain a target object instance, the purpose that the rendering of the target object instance is completed in a tangent plane mode when the service is deployed is achieved, the service operation component is called, service data corresponding to the target service is obtained based on a service identifier, the target service is operated based on the target object instance and the service data, the purpose that the target service is operated based on the target object instance and the service data obtained by tangent plane rendering when the service is executed is achieved, repeated change of operation logic codes of the operation target service is avoided, and repeatability and maintainability of service operation are improved.

In an optional embodiment of the present disclosure, the step 106 of calling the target service operation component, and obtaining service data corresponding to the target service based on the service identifier includes the following specific steps:

and calling a target service operation component, and acquiring service data corresponding to the target service from service data corresponding to each service on the service platform cluster based on the service identification.

Each service is distributed and deployed on a service platform cluster, corresponding service application packages are deployed on a plurality of nodes in the cluster, and the service identifier is the unique identifier of the service application package on the service platform cluster. The service identifier can determine the service data corresponding to the target service in the service data of each service on the service platform cluster, namely, the service data of each service application packet in the service platform cluster is searched to complete the corresponding query of the service data.

Invoking a target service operation component, and acquiring service data corresponding to a target service from service data corresponding to each service on a service platform cluster based on a service identifier, wherein the specific mode is as follows: and calling a target service operation component, determining a service application package of a target service from service application packages of all services on the service platform cluster based on the service identification, and acquiring service data corresponding to the target service from the service package of the target service. Wherein, the Label can finish the inquiry search (Label Selector) through the Label selection component.

Illustratively, an Operator component is invoked, a service application package 1 and a service application package 2 of a service application 1 are determined from service application packages of each service on a service platform cluster based on service identifications (reployuid and reployorder), and corresponding service data is acquired from the service application package 1 and the service application package 2: workload 1, workload 2, and workload 3.

And calling a target service operation component, and acquiring service data corresponding to the target service from service data corresponding to each service on the service platform cluster based on the service identification. The service data corresponding to the target service is more accurately obtained, and the follow-up accurate operation of the target service is ensured.

In an alternative embodiment of the present disclosure, before step 106, the following specific steps are further included:

storing the target object instance into an object instance queue;

accordingly, step 106 includes the following specific steps:

calling a target service operation component to monitor the execution state of each object instance in the object instance queue;

and under the condition that the execution state of the target object instance is to be executed, acquiring service data corresponding to the target service based on the service identifier, and running the target service based on the target object instance and the service data.

Typically, object instances are pre-stored in an object instance queue and executed sequentially in a "first in first out" manner.

The object instance queue is an execution queue of resource object instances on the service platform cluster. And (3) following the sequential execution rule of first-in first-out, and completing unified management and monitoring of each service on the service platform cluster.

The execution state of the target object instance is the state that the target object instance is executed by the target service execution component in the object instance queue, and is obtained through monitoring of the object instance queue by the target service execution component, including to-be-executed and not-to-be-executed. Wherein the to-be-executed characterizing object instance is to be executed, waiting to be executed on the dequeue. The unexecuted token object instance is unexecuted and is also unexecuted in the queue.

Under the condition that the execution state of the target object instance is to be executed, service data corresponding to the target service is acquired based on the service identifier, and the target service is operated based on the target object instance and the service data, wherein the specific mode is as follows: and under the condition that the execution state of the target object instance is monitored to be executed, calling a target service operation component, acquiring service data corresponding to the target service based on the service identifier, and operating the target service based on the target object instance and the service data. Further, under the condition that the execution state of the target object instance is monitored to be executed, the target service operation component is called, service data corresponding to the target service is obtained from the service platform cluster based on the service identification, and the service data is processed based on the target object instance, so that the target service is operated based on the target service logic. Further, under the condition that the execution state of the target object instance is monitored to be executed, the target service operation component is called, a service application package of the target service is determined from the service platform cluster, and service data corresponding to the initial object instance is obtained from the service application package of the target service based on the service identification.

The target object instance CR is stored in an object instance queue, an Operator component is called to monitor the execution state of each object instance in the object instance queue, and when the execution state of the target object instance CR is monitored to be executed, service application packages 1 and 2 of the service application 1 and 2 are determined from service application packages of each service based on service identifiers (replyuic and replyorder), and service data corresponding to the initial object instance CR' is acquired from the service application packages 1 and 2: workload 1, workload 2, and workload 3. Based on the target object instance CR, the workload 1, the workload 2, and the workload 3 are processed, so that the business application 1 and the business application 2 are operated based on the updated business logic (the business application 2 is started within N seconds after the business application 1 is started).

Storing the target object instance into an object instance queue; calling a target service operation component to monitor the execution state of each object instance in the object instance queue; and under the condition that the execution state of the target object instance is to be executed, acquiring service data corresponding to the target service based on the service identifier, and running the target service based on the target object instance and the service data. Through the object instance queue, unified management and monitoring of each service on the service platform cluster are completed, service data acquisition and service operation are realized based on the unified management and monitoring, and the accuracy of service data and the stability of service operation are improved.

In an alternative embodiment of the present specification, the running of the target service based on the target object instance and the service data in step 106 includes the following specific steps:

and calling a target service operation component, adjusting service data based on the target object instance and the target service logic, and operating the target service based on the adjusted service data.

An object instance is essentially an instance that performs dynamic operations on business data through a resource object, and is implemented at the bottom by adjusting the business data. It should be noted that, in the embodiment of the present disclosure, the adjustment is performed on the service data, and not on the running logic code. For example, if the target object instance determines that the state of the target service is "Running", the target service Running component may be invoked to adjust the state of the target service to run based on the target object instance, if the target object instance determines that the state of the target service is "packed", the target service Running component may be invoked to adjust the state of the target service to pause based on the target object instance, and finally, save the change. This completes the state update for the target service without changing the running logic code.

Illustratively, the Operator component is invoked to adjust the business data based on the target object instance CR and the target business logic (starting the business application 2 within N seconds after starting the business application 1), adjust the running states (phase), copy numbers (animation) of the workload 1, the workload 2, and the workload 3, and run the business application 1 and the business application 2 based on the adjusted workload 1, workload 2, and workload 3.

And calling a target service operation component, adjusting service data based on the target object instance and the target service logic, and operating the target service based on the adjusted service data. The business data is adjusted based on the target object instance and the target business logic, and then the operation of the target business is realized based on the adjusted business data, so that the accuracy and the repeatability of the business operation are ensured.

In an alternative embodiment of the present disclosure, step 104 includes the following specific steps:

and responding to the associated file deployment instruction of the target service, calling a preset customized script, and rendering a preset object instance template of the target service based on the target object information to obtain a target object instance.

The preset object instance template of the target service is a template for specifying the implementation class definition and attribute of the resource object. Each resource object has a unique service identifier and a plurality of other attributes, and the other attributes are correspondingly selected from the selectable values and are used for rendering to obtain a target object instance. For example, for one Pod resource object, the following templates may be used: copy code; apiVersion: apps/v1; pod: pod; metadata: name: my-pod; spec: the contacts; name, my-container; image: my-image: last; ports: containerPort:8080. the preset object instance template defines a resource object class named Pod, which has the following properties: name, spec and metadata. name is the name of the Pod object, spec is the configuration of the Pod object, metadata is optional metadata that will be passed to the creation and execution operations of the Pod object.

Responding to an associated file deployment instruction of a target service, calling a preset customized script, and rendering a preset object instance template of the target service based on target object information to obtain a target object instance, wherein the specific mode is as follows: and responding to the associated file deployment instruction of the target service, calling a preset customized script, adjusting the numerical value of the corresponding attribute in the preset object instance template of the target service based on the target object information, and rendering to obtain a target object instance.

Illustratively, in response to a management package deployment instruction (helm instrument) of the service application 1 and the service application 2, kustmize and Shell are called, values (configuration and metadata) of corresponding definition attributes in a preset instance template of the target service are adjusted based on target object information CRD, and CR is rendered.

And responding to the associated file deployment instruction of the target service, calling a preset customized script, and rendering a preset object instance template of the target service based on the target object information to obtain a target object instance. The rendering efficiency is improved, and the feasibility of the obviously obtained target object instance is improved.

In an alternative embodiment of the present disclosure, in response to an associated file deployment instruction of a target service, invoking a preset customized script, and rendering a preset object instance template of the target service based on target object information to obtain a target object instance, including the following specific steps:

And responding to the associated file deployment instruction of the target service, calling a preset customized script, and rendering a preset object instance template of the target service based on the target object information through a script path corresponding to the associated file deployment instruction to obtain a target object instance.

The associated file deployment instruction can have multiple types of operation instructions, and different types of operation instructions need to complete rendering of the object instance through different script paths. The operation instructions of various types comprise a management packet of the target service, a resource packet of the target service and the like. On the K8s platform cluster, the management package of the target service comprises: the Helm packet, the resource packet of the target business includes: k8s resource package (resource set YAML file). The relevant file deployment instruction of the target service is a deployment instruction for deploying relevant files of the target service on a service platform cluster, and comprises a management package deployment instruction of the target service and a resource package deployment instruction of the target service, wherein the management package deployment instruction of the target service comprises a HelmInstall instruction, and the resource package deployment instruction of the target service comprises a KubectlApply instruction. Each operation instruction has a script path of a corresponding type, and each script path is used as a rendering entry for rendering a resource object instance, and is embodied by unloading parameters in a preset customized script, including but not limited to: the script path corresponding to the management package deployment instruction of the target service and the script path corresponding to the resource package deployment instruction of the target service. On the K8s platform cluster, a script path corresponding to a management package deployment instruction HelmInstalling instruction of the target service is Post-render, and a script path corresponding to a resource package deployment instruction KubectlApply instruction of the target service is Kustmize.

Responding to an associated file deployment instruction of a target service, calling a preset customized script, and rendering a preset object instance template of the target service based on target object information through a script path corresponding to the associated file deployment instruction to obtain a target object instance, wherein the specific mode is as follows: and calling a preset customized script in response to the associated file deployment instruction of the target service, correspondingly adjusting the numerical value of the corresponding attribute in the preset object instance template of the target service based on the target object information through a script path corresponding to the associated file deployment instruction, and rendering to obtain a target object instance.

Illustratively, in response to the associated file deployment instruction of the service application 1 and the service application 2, the numerical value (configuration and metadata) of the corresponding definition attribute in the preset instance template of the target service is adjusted based on the target object information CRD through the script path corresponding to the operation instruction, and the CR is rendered.

And responding to the associated file deployment instruction of the target service, calling a preset customized script, and rendering a preset object instance template of the target service based on the target object information through a script path corresponding to the associated file deployment instruction to obtain a target object instance. Different operation instructions are called, corresponding rendering is completed through corresponding script paths, and suitability and diversity of rendering are improved.

In an alternative embodiment of the present disclosure, in response to an associated file deployment instruction of a target service, a preset customized script is called, and a preset object instance template of the target service is rendered based on target object information through a script path corresponding to the associated file deployment instruction, so as to obtain a target object instance, including the following specific steps:

and responding to the management package deployment instruction of the target service, calling a preset customized script, and rendering a preset object instance template of the target service based on the target object information through a script path corresponding to the management package deployment instruction to obtain a target object instance.

The management package deployment instruction of the target service is an operation instruction for deploying a management package for managing and monitoring the target service. The management package of the target service is used for managing and monitoring the running state of the target service, monitoring the performance and availability of the target service, and can be used for deploying, upgrading and maintaining the target service. For example, in the K8s platform cluster, the management packet of the target service is a hell packet, the management packet deployment instruction of the target service may be a hell instruction, and the script path corresponding to the hell instruction of the management packet deployment instruction of the target service is a Post-render.

Responding to a management package deployment instruction of a target service, calling a preset customized script, and rendering a preset object instance template of the target service based on target object information through a script path corresponding to the management package deployment instruction to obtain a target object instance, wherein the specific mode is as follows: and calling a preset customized script in response to a management package deployment instruction of the target service, correspondingly adjusting the numerical value of the corresponding attribute in a preset object instance template of the target service based on the target object information through a script path corresponding to the management package deployment instruction, and rendering to obtain a target object instance.

Illustratively, in response to a management package deployment instruction (helm instrument) of the service application 1 and the service application 2, values (configuration and metadata) of corresponding definition attributes in a preset instance template of the target service are adjusted based on the target object information CRD through corresponding Post-render script paths, and rendering is performed to obtain the CR.

And responding to the management package deployment instruction of the target service, calling a preset customized script, and rendering a preset object instance template of the target service based on the target object information through a script path corresponding to the management package deployment instruction to obtain a target object instance. And responding to the management package deployment instruction of the target service, and realizing the example rendering under the corresponding rendering entrance through the script path, thereby improving the flexibility of the target object instance obtained by rendering.

In an optional embodiment of the present disclosure, in response to an associated file deployment instruction of a target service, an operation instruction in a preset customized script is invoked, and a preset object instance template of the target service is rendered based on target object information through a script path corresponding to the operation instruction, so as to obtain a target object instance, including the following specific steps:

and responding to the resource package deployment instruction of the target service, calling a preset customized script, and rendering a preset object instance template of the target service based on the target object information through a script path corresponding to the resource package deployment instruction to obtain a target object instance.

The resource package deployment instruction of the target service is an operation instruction for managing and monitoring resource object instances on the service platform cluster. For example, in the K8s platform cluster, the operation instruction of the service platform cluster may be a kubectliapply instruction, that is, the resource object is configured or created through the target object information, and the script path corresponding to the kubectliapply instruction is kustmize.

Responding to a resource package deployment instruction of a target service, calling a preset customized script, and rendering a preset object instance template of the target service based on target object information through a script path corresponding to the resource package deployment instruction to obtain a target object instance, wherein the specific mode is as follows: and calling a preset customized script in response to a resource package deployment instruction of the target service, correspondingly adjusting the numerical value of the corresponding attribute in a preset object instance template of the target service based on the target object information through a script path corresponding to the resource package deployment instruction, and rendering to obtain a target object instance.

Illustratively, in response to resource package deployment instructions (kubectliAN_SNly) of the service application 1 and the service application 2, values (configuration and metadata) of corresponding definition attributes in a preset instance template of the target service are adjusted based on the target object information CRD through corresponding kustopize script paths, and the CR is rendered.

And responding to the resource package deployment instruction of the target service, calling a preset customized script, and rendering a preset object instance template of the target service based on the target object information through a script path corresponding to the resource package deployment instruction to obtain a target object instance. And responding to the resource package deployment instruction of the target service, completing rendering through a script path, and improving the pertinence of the target object instance obtained by rendering.

In an alternative embodiment of the present disclosure, before step 102, the following specific steps are further included:

and deploying the target object information and the target service operation component set for the target service on the service platform cluster.

The target service running component may be self-developed by the request end, or may be a running component multiplexing other resource object instances, which is not limited herein.

Illustratively, the target object information CRD and Operator components are deployed on a business platform cluster.

And deploying the target object information and the service operation component on the service platform cluster. The method lays a foundation for rendering the target object instance and lays a foundation for running the target business.

The following is a further explanation of the service operation method provided in the present specification, taking an example of an application of the service operation method to start a control scenario in a service platform service application arrangement sequence with reference to fig. 2. Fig. 2 shows a process flow chart of a service operation method applied to a service platform service application arrangement sequence starting control scene according to an embodiment of the present disclosure, including the following specific steps:

step 202: and deploying target object information CRD and target service operation components Operator on the K8s platform cluster, and adding preset custom scripts Kustmize and Shell on the deployment application side.

Step 204: deploying two target business application packages on a platform layout: business application package 1 and business application package 2, and configure the initial object instance as: firstly, a service application packet 1 is started, and then a service application packet 2 is started.

Step 206: the platform deployment side deploys two target service application packages and transmits corresponding service identifiers replyUId, wherein replyOrder is respectively as follows: xxx:1, xxx:2.

Step 208: and calling preset custom scripts Kustmize and Shell in response to a management package deployment instruction HelmInstalls for deploying two target service application packages, and rendering to obtain corresponding target object instances CR1 and CR2 and corresponding service identifiers replyUid and replyOrder based on target object information CRD, wherein the workload in the service application package 1 is normal, and the workload in the service application package 2 is 0.

The method comprises the steps of calling preset custom scripts Kustmize and Shell to render, wherein the specific modes are as follows:

step 1: the service identifier replyUId corresponding to the rendering service application is rendered to all workloads (Statefulset) of the Helm package in a form of label by the replyOrder. Step 2: rendering and generating a target object instance CR corresponding to the target object information CRD, and recording service identifiers deltayUId and deltayorder corresponding to the Helm packet. Step 3: for the case where the replyorder is not 1, the duplicate number of all workloads (replsets, statefulset) is set to 0, and its original value is saved to the annotation field. (this would result in a normal deployment launch for a business application with a depth order of 1, but all workloads for a business application deployment with a depth order of not 1 are 0).

Step 210: and (3) calling a target business operation component Operator, detecting that the replyorder of the target object instance CR1 is 1, and inquiring all the workloads in the business application package 1 based on the business identification replyUId and the replyorder through a LabelSelecter.

Step 212: and judging whether all the workloads in the business application package 1 are completely started or not.

Step 214: if yes, finishing the starting condition of the workload to phase of the target object instance CR1, and ending.

Step 216: if not, the target object instance CR1 delays reentering the object instance queue.

Step 218: and calling a target service operation component Operator, detecting that the depth order of the target object instance CR1 is 2, and inquiring the target object instance CR1 of the service application package 1 through the depth Uid.

Step 220: by means of the state field phase on the target object instance CR1, it is determined whether all the workloads in the service application package 2 are all started.

Step 222: if not, the target object instance CR2 delays reentering the object instance queue.

Step 224: if so, inquiring all workloads in the business application package 2 based on the business identification reployUId and reployorder through LabelSelecter, and judging whether the number of the workload copies is different from that of the annotation field section record.

Step 226: if yes, the copy number of the annotation field animation records is updated to the workload, the state field phase corresponding to the target object instance is updated, and the target object instance CR2 delays reentering the object instance queue.

Step 228: if not, the state field phase corresponding to the target object instance is updated, and the target object instance CR2 delays reentering the object instance queue.

In the embodiment of the specification, under the condition that the service codes on the K8s platform cluster are not modified, the iterative updating of the service platform service application arrangement sequence starting control function is completed, and the capability of the service platform cluster is integrated.

Fig. 3 is a flow chart of a service operation method in a service platform service application arrangement sequence start control scenario according to an embodiment of the present disclosure, where the flow chart is shown in fig. 3:

the original platform functions as follows: a service application package 1 and a service application package 2 are deployed on the K8s platform cluster; the method comprises the steps of respectively deploying workloads for a business application package 1 and a business application package 2, wherein business data of the business application package 1 comprises a workload 1 and a workload 2, and business data of the business application package 2 comprises a workload 3.

The start function for the service orchestration sequence is as follows: respectively rendering to obtain a target resource object instance corresponding to the service application package 1 and a target resource object instance corresponding to the service application package 2; calling a target service operation component Operator to monitor the target resource object instance and storing the target resource object instance into a resource object instance queue; circularly obtaining a target resource object instance from the queue; processing target resource object instance: judging whether the depth order is 1; if the replyOrder is 1, inquiring through replyUid and replyOrder to obtain a workload; judging whether all the work loads are started; if yes, updating a state field corresponding to the target resource object instance, and ending the processing; if not, updating the state field corresponding to the target resource object instance; storing the delay preset time length into a resource object instance queue; if the depth order is not 1, inquiring the target resource object instance with the same depth Uid and the depth order not being 1; judging whether the workload is completed or not through a status field on the target resource object instance; if not, storing the delay preset time length into a resource object instance queue; if so, obtaining a workload through replyUId and replyOrder query; judging whether the number of the workload copies is different from that of the comment field record; if the state fields are the same, updating the state fields corresponding to the target resource object instance, and storing the delay preset time length into a resource object instance queue; if the number of copies of the annotation field records is different, updating the state field corresponding to the target resource object instance to the workload, and storing the delay preset time length into a resource object instance queue.

Corresponding to the method embodiment, the present disclosure further provides an embodiment of a service operation device, and fig. 4 shows a schematic structural diagram of a service operation device provided in an embodiment of the present disclosure. As shown in fig. 4, the apparatus includes:

an obtaining module 402, configured to obtain, in response to an operation instruction of a target service, target object information and a target service operation component set for the target service that are deployed in advance;

the rendering module 404 is configured to respond to the associated file deployment instruction of the target service, call a preset custom script, render the target object instance based on the target object information, and obtain the service identifier of the target object instance;

the operation module 406 is configured to invoke the target service operation component, obtain service data corresponding to the target service based on the service identifier, and operate the target service based on the target object instance and the service data.

Optionally, the run module 406 is further configured to:

Optionally, the apparatus further comprises:

a queue storage module configured to store a target object instance into an object instance queue;

Accordingly, the run module 406 is further configured to:

calling a target service operation component to monitor the execution state of each object instance in the object instance queue; and under the condition that the execution state of the target object instance is to be executed, acquiring service data corresponding to the target service based on the service identifier, and running the target service based on the target object instance and the service data.

Optionally, the run module 406 is further configured to:

Optionally, the rendering module 404 is further configured to:

Optionally, the apparatus further comprises:

and the deployment module is configured to deploy the target object information and the target service operation component set for the target service on the service platform cluster.

The foregoing is a schematic solution of a service running apparatus of this embodiment. It should be noted that, the technical solution of the service operation device and the technical solution of the service operation method belong to the same conception, and details of the technical solution of the service operation device, which are not described in detail, can be referred to the description of the technical solution of the service operation method.

FIG. 5 illustrates a block diagram of a computing device provided by one embodiment of the present description. The components of the computing device 500 include, but are not limited to, a memory 510 and a processor 520. Processor 520 is coupled to memory 510 via bus 530 and database 550 is used to hold data.

Computing device 500 also includes access device 540, access device 540 enabling computing device 500 to communicate via one or more networks 560. Examples of such networks include a public switched telephone Network (PSTN, publicSwitchedTelephone Network), a local area Network (LAN, localAreaNetwork), a wide area Network (WAN, wideAreaNetwork), a personal area Network (PAN, personalAreaNetwork), or a combination of communication networks such as the internet. The access device 540 may include one or more of any type of network interface, wired or wireless, such as a Network Interface Card (NIC), such as an IEEE802.11 wireless local area network (WLAN, wirelessLocalAreaNetwork) wireless interface, a worldwide interoperability for microwave access (Wi-MAX, worldwideInteroperabilityforMicrowaveAccess) interface, an ethernet interface, a universal serial bus (USB, universalSerialBus) interface, a cellular network interface, a bluetooth interface, a near-field communication (NFC, nearFieldCommunication).

In one embodiment of the present description, the above-described components of computing device 500, as well as other components not shown in FIG. 5, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device shown in FIG. 5 is for exemplary purposes only and is not intended to limit the scope of the present description. Those skilled in the art may add or replace other components as desired.

Computing device 500 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smart phone), wearable computing device (e.g., smart watch, smart glasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or personal computer (PC, personalComputer). Computing device 500 may also be a mobile or stationary server.

Wherein the processor 520 is configured to execute computer-executable instructions that, when executed by the processor, perform the steps of the business operation method described above.

The foregoing is a schematic illustration of a computing device of this embodiment. It should be noted that, the technical solution of the computing device and the technical solution of the service operation method belong to the same concept, and details of the technical solution of the computing device, which are not described in detail, can be referred to the description of the technical solution of the service operation method.

An embodiment of the present disclosure also provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the business operation method described above.

The above is an exemplary version of a computer-readable storage medium of the present embodiment. It should be noted that, the technical solution of the storage medium and the technical solution of the service operation method belong to the same concept, and details of the technical solution of the storage medium which are not described in detail can be referred to the description of the technical solution of the service operation method.

An embodiment of the present disclosure further provides a computer program, where the computer program, when executed in a computer, causes the computer to perform the steps of the service operation method described above.

The above is an exemplary version of a computer program of the present embodiment. It should be noted that, the technical solution of the computer program and the technical solution of the service operation method belong to the same conception, and details of the technical solution of the computer program, which are not described in detail, can be referred to the description of the technical solution of the service operation method.

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The computer instructions include computer program code that may be in source code form, object code form, executable file or some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a Read-only memory (ROM), a random access memory (RAM, randomAccessMemory), an electrical carrier signal, a telecommunication signal, a software distribution medium, and so forth. It should be noted that the content of the computer readable medium can be increased or decreased appropriately according to the requirements of the patent practice, for example, in some areas, according to the patent practice, the computer readable medium does not include an electric carrier signal and a telecommunication signal.

It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of combinations of actions, but it should be understood by those skilled in the art that the embodiments are not limited by the order of actions described, as some steps may be performed in other order or simultaneously according to the embodiments of the present disclosure. Further, those skilled in the art will appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily all required for the embodiments described in the specification.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to the related descriptions of other embodiments.

The preferred embodiments of the present specification disclosed above are merely used to help clarify the present specification. Alternative embodiments are not intended to be exhaustive or to limit the invention to the precise form disclosed. Obviously, many modifications and variations are possible in light of the teaching of the embodiments. The embodiments were chosen and described in order to best explain the principles of the embodiments and the practical application, to thereby enable others skilled in the art to best understand and utilize the invention. This specification is to be limited only by the claims and the full scope and equivalents thereof.

Claims

1. A method for operating a service, comprising:

responding to the associated file deployment instruction of the target service, calling a preset custom script, rendering based on the target object information to obtain a target object instance, and obtaining a service identifier of the target object instance;

And calling the target service operation component, acquiring service data corresponding to the target service based on the service identifier, and operating the target service based on the target object instance and the service data.

2. The method of claim 1, wherein the invoking the target service execution component to obtain service data corresponding to the target service based on the service identification comprises:

and calling the target service operation component, and acquiring service data corresponding to the target service from service data corresponding to each service on a service platform cluster based on the service identification.

3. The method of claim 1, further comprising, prior to said invoking said target service execution component, obtaining service data corresponding to said target service based on said service identification and executing said target service based on said target object instance and said service data:

storing the target object instance into an object instance queue;

the calling the target service operation component, acquiring service data corresponding to the target service based on the service identifier, and operating the target service based on the target object instance and the service data, including:

Invoking the target service operation component to monitor the execution state of each object instance in the object instance queue;

4. A method according to any of claims 1-3, wherein the running the target service based on the target object instance and the service data comprises:

and calling the target service operation component, adjusting the service data based on the target object instance and target service logic, and operating the target service based on the adjusted service data.

5. The method according to claim 1, wherein the calling a preset custom script in response to the associated file deployment instruction of the target service, and rendering the target object instance based on the target object information, comprises:

6. The method according to claim 5, wherein the responding to the associated file deployment instruction of the target service calls a preset customized script, and based on the target object information, renders a preset object instance template of the target service to obtain a target object instance, including:

7. The method according to claim 6, wherein the responding to the associated file deployment instruction of the target service calls a preset customized script, and the rendering of the preset object instance template of the target service based on the target object information through the script path corresponding to the associated file deployment instruction to obtain a target object instance includes:

8. The method according to claim 6, wherein the responding to the associated file deployment instruction of the target service calls an operation instruction in a preset customized script, renders a preset object instance template of the target service based on the target object information through a script path corresponding to the operation instruction, and obtains a target object instance, including:

9. The method of claim 1, further comprising, prior to said obtaining pre-deployed target object information and target service execution components set for said target service:

and deploying the target object information and the target service operation component set for the target service on a service platform cluster.

10. A service execution apparatus, comprising:

the acquisition module is used for responding to an operation instruction of a target service and acquiring target object information and a target service operation component which are arranged in advance and are set for the target service;

and the operation module is configured to call the target service operation component, acquire service data corresponding to the target service based on the service identifier, and operate the target service based on the target object instance and the service data.

11. A computing device, comprising:

a memory and a processor;

the memory is configured to store computer executable instructions and the processor is configured to execute the computer executable instructions to implement the steps of the business operation method of any one of claims 1 to 9.

12. A computer readable storage medium, characterized in that it stores computer instructions which, when executed by a processor, implement the steps of the business operation method of any of claims 1 to 9.