CN114500268B - Deployment method, device, server and storage medium of chart resources - Google Patents

Abstract

The embodiment of the present application discloses a chart resource deployment method, device, server and storage medium, and relates to the field of computer technology. The method includes: in response to receiving a verification instruction sent by the first terminal, performing resource permission verification on the target chart resource, the target chart resource is a chart resource uploaded by the first terminal, and different chart resources are used to implement different chart services; in response to the target chart resource passing the resource permission verification, setting the target chart resource to a deployable state; in response to receiving a deployment instruction for the target chart resource, deploying the target chart resource to a target cluster, and the target cluster includes at least one second terminal to be deployed. The server automatically executes resource permission verification and automatic deployment operations, which not only shortens the review cycle, but also improves the accuracy of verification and deployment efficiency.

Description

Deployment method, device, server and storage medium of chart resources

technical field

The embodiments of the present application relate to the field of computer technology, and in particular to a method, device, server, and storage medium for deploying chart resources.

Background technique

In the Kubernetes cluster, the operation and maintenance personnel use the Helm package manager to deploy chart resources to implement application update and maintenance.

In the prior art, before updating and maintaining the application, it is necessary to manually verify the chart resources. After the manual verification is passed, manual deployment is performed through the operation steps indicated in the deployment document.

Contents of the invention

Embodiments of the present application provide a chart resource deployment method, device, server, and storage medium. Described technical scheme is as follows:

On the one hand, the embodiment of the present application provides a method for deploying chart resources, the method is used for servers in a cluster system, and the method includes:

In response to receiving the verification instruction sent by the first terminal, performing resource authority verification on the target chart resource, the target chart resource is a chart resource uploaded by the first terminal, and different chart resources are used to implement different chart services;

In response to the target chart resource passing the resource permission check, setting the target chart resource to a deployable state;

In response to receiving a deployment instruction for the target chart resource, deploy the target chart resource to a target cluster, where the target cluster includes at least one second terminal of the chart service to be deployed.

On the other hand, the embodiment of the present application provides a device for deploying chart resources, the device is used for servers in a cluster system, and the device includes:

A verification module, configured to perform resource authority verification on a target chart resource in response to receiving a verification instruction sent by the first terminal, where the target chart resource is a chart resource uploaded by the first terminal, and different chart resources are used to implement different chart services;

A setting module, configured to set the target chart resource to a deployable state in response to the target chart resource passing the resource permission check;

The deployment module is configured to, in response to receiving a deployment instruction for the target chart resource, deploy the target chart resource to a target cluster, and the target cluster includes at least one second terminal of the chart service to be deployed.

On the other hand, an embodiment of the present application provides a server, the server includes a processor and a memory; the memory stores at least one instruction, and the at least one instruction is used to be executed by the processor to implement the task execution method in the heterogeneous system described in the above aspect.

On the other hand, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and the computer program is loaded and executed by a processor to implement the chart resource deployment method described in the above aspect.

On the other hand, an embodiment of the present application provides a computer program product, where the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the chart resource deployment method described in the above aspects.

The beneficial effects brought by the technical solutions provided by the embodiments of the present application at least include:

In the embodiment of the present application, in the target chart resource verification stage, the server automatically performs resource permission verification on the resource file of the target chart resource by receiving the verification command sent by the first terminal, no longer relying on manual review, shortening the review cycle, and improving the accuracy of resource permission verification; in the deployment stage of the target chart resource, when the server receives the deployment instruction, the server also performs the deployment operation automatically, without manual deployment according to the deployment document. In the maintenance stage, not only the maintenance cost investment is reduced, but also the deployment efficiency is improved.

Description of drawings

Fig. 1 is a network topology diagram of a cluster system provided by an exemplary embodiment of the present application;

Fig. 2 is a flowchart of a deployment method of chart resources provided by an exemplary embodiment of the present application;

Fig. 3 is a flowchart of a deployment method of chart resources shown in another exemplary embodiment of the present application;

FIG. 4 is a flowchart of a method for deploying chart resources shown in another exemplary embodiment of the present application;

FIG. 5 shows a schematic interface diagram of a chart resource management interface provided by an exemplary embodiment of the present application;

FIG. 6 shows a schematic interface diagram of a Chart resource management interface provided by an exemplary embodiment of the present application;

FIG. 7 shows a schematic interface diagram of the Helm Chart management interface provided by an exemplary embodiment of the present application;

Fig. 8 is a structural block diagram of a device for deploying chart resources provided by an exemplary embodiment of the present application;

Fig. 9 shows a structural block diagram of a server provided by an exemplary embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the implementation manners of the present application will be further described in detail below in conjunction with the accompanying drawings.

The "plurality" mentioned herein means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B may indicate: A exists alone, A and B exist simultaneously, and B exists independently. The character "/" generally indicates that the contextual objects are an "or" relationship.

Cluster: A cluster is a group of independent computers interconnected through a high-speed network. They form a group and are managed as a single system. When a client interacts with the cluster, the cluster behaves like a stand-alone server. Cluster configurations are used to improve availability and scalability. Cluster technology is a relatively new technology. Through cluster technology, relatively high benefits in terms of performance, reliability, and flexibility can be obtained at a low cost. Its task scheduling is the core technology in the cluster system.

Kubernetes: Kubernetes is referred to as K8s, which is an abbreviation formed by replacing the 8 characters "ubernete" with 8. It is an open source, used to manage containerized applications on multiple hosts in the cloud platform. The goal of Kubernetes is to make deploying containerized applications simple and efficient. Kubernetes provides a mechanism for application deployment, planning, updating and maintenance. The traditional application deployment method is to install the application through plug-ins or scripts. The disadvantage of this is that the operation, configuration, management, and all life cycles of the application will be bound to the current operating system, which is not conducive to the application upgrade/rollback and other operations. Of course, some functions can also be realized by creating a virtual machine, but the virtual machine is very heavy, which is not conducive to portability. The new method is implemented by deploying containers. Each container is isolated from each other, and each container has its own file system. The processes between containers will not affect each other, and computing resources can be distinguished. Compared with virtual machines, containers can be quickly deployed. Because containers are decoupled from underlying facilities and machine file systems, they can be migrated between different clouds and operating systems of different versions. Containers occupy less resources and are faster to deploy. Each application can be packaged into a container image. The one-to-one relationship between each application and container also gives containers a greater advantage. Using containers can create container images for applications during the build or release phase, because each application does not need to be combined with the rest of the application stack and does not depend on the infrastructure of the production environment. This enables a consistent environment from R&D to testing and production.

Helm: Helm is a package manager for Kubernetes and a client tool based on the command line. It is mainly used for the creation, packaging, and release of the Kubernetes application Chart, as well as the creation and management of local and remote Chart warehouses. In the embodiment of this application, when deploying the chart resource, the chart resource is deployed by calling the Helm package manager.

In related technologies, when developers or operation and maintenance personnel develop and deploy chart resources through Kubernetes clusters, they need to manually verify resource permissions; moreover, in the deployment stage of chart resources, operation and maintenance personnel usually need to manually execute according to the operation instructions of the deployment document. When the operation steps are wrong, they need to check again, and the deployment efficiency is not high.

In the embodiment of this application, when it is necessary to verify the resource authority of the uploaded target chart, the verification can be performed automatically through the server without manual review. During the deployment phase, pre-verification and pre-update of the chart resources can also be automatically performed, and manual review is no longer dependent on the deployment document. This can not only save labor costs, but also improve the efficiency of verification and deployment.

FIG. 1 shows a network topology diagram of a cluster system provided by an embodiment of the present application. The network topology diagram includes: a first terminal 110 , a server 120 and a second terminal 130 .

The first terminal 110 in the network topology diagram is at least one of electronic devices such as mobile phones, desktop computers, tablet computers, multimedia playback devices, and laptop computers. The first terminal 110, the server 120, and the second terminal run in the same Kubernetes cluster. The first terminal 110 is a terminal for publishing chart resources and deploying chart resources in the cluster system. The first terminal 110 is installed with a Helm client, and the chart resources are sent to the server 120 through the Helm client. In addition, the first terminal 110 can also display the life cycle of the chart resource, and send a verification instruction and a deployment instruction to the server 120 .

The server 120 is a device that provides data storage and chart services in the cluster system. The server 120 stores chart resources and a database for running chart services. The server 120 is also used to receive verification instructions from the first terminal 110 and perform resource authority verification on uploaded chart resources. In addition, the server 120 is also used to receive deployment instructions from the first terminal 110 and provide chart services to the second terminal 130.

The second terminal 130 is at least one of electronic equipment such as a mobile phone, a desktop computer, a tablet computer, a multimedia player, and a laptop computer. The second terminal 130 is a terminal to be deployed with chart resources in the target cluster. The second terminal 130 is installed with a Helm client, and establishes a communication connection with the first terminal 110 and the server 120 through the Helm client. Optionally, the second terminal 130 may also feed back deployment information to the server 120 .

Those skilled in the art may know that the number of the above-mentioned first terminals and second terminals may be more or less. For example, there may be only one second terminal, or there may be tens or hundreds of terminals, or more. The embodiment of the present application does not limit the number of terminals and device types.

FIG. 2 is a flow chart of a method for deploying chart resources provided by an exemplary embodiment of the present application. This embodiment uses the server shown in FIG. 1 as an example for illustration. The method includes:

Step 201, in response to receiving a verification instruction sent by the first terminal, perform resource authority verification on the target chart resource, the target chart resource is a chart resource uploaded by the first terminal, and different chart resources are used to implement different chart services.

The server in the cluster system stores the chart resource uploaded by the first terminal. The chart resource is written by the developer. It includes a set of YAML files that define Kubernetes resources and is stored in the server as a compressed package in TAR or GZ format. The chart resource can deploy at least one chart service, such as providing application download and installation through the chart resource, complete HTTP service, etc.

When the developer finishes writing the chart resource and needs to deploy the chart resource to the corresponding Kubernetes cluster, the first terminal sends a verification instruction to the server. After the server receives the verification instruction sent by the first terminal, it automatically performs resource permission verification on the target chart resource uploaded by the first terminal. The purpose of resource permission verification is to ensure the legitimacy and correctness of the resource files in the target chart resource and to realize the corresponding chart service. In the prior art, the resource permission verification process is usually manually reviewed by the operation and maintenance personnel of the Kubernetes platform. The manual review period is long and the review accuracy is not high. This solution transplants the resource permission verification steps to the server, and the server is automatically executed by the verification command, which greatly shortens the review cycle, reduces the cost of manual review, and improves the accuracy of resource permission verification.

Step 202, in response to the target chart resource passing the resource permission check, setting the target chart resource to a deployable state.

When the resource permission verification result meets the deployment requirements of the cluster system, the server sets the target chart resource to a deployable state. Usually, the cluster system contains multiple terminals, and the multiple terminals and the server run in the same cluster system, and the server pushes the deployable target chart resources to the cluster system.

Schematically, taking the download and installation of the target chart as an example, for a target chart resource that can be deployed, the server sends a notification of the launch of the target chart resource to other terminals in the cluster system in the form of a message reminder, so that other terminals can purchase the chart resource and the corresponding chart service. The chart service includes installing the application program, updating and maintaining the application program, and providing background services for the application program.

Step 203, in response to receiving a deployment instruction for the target chart resource, deploy the target chart resource to the target cluster, where the target cluster includes at least one second terminal to be deployed.

The server stores all the database resources and configuration information for realizing the chart service. When the server receives the deployment command sent by the first terminal, it indicates that the first terminal needs to deploy the target chart resource to the target cluster in order to provide the target cluster with the corresponding chart service. In the prior art, the process of deploying chart resources requires operation and maintenance personnel to perform manual deployment operations according to the deployment documents, including information review of the target cluster, checking the database configuration of the target chart resources, and updating the database. However, in this solution, the deployment command is used as the trigger mechanism for this process. After the server receives the deployment command, the server automatically executes the deployment operation instead of manual deployment.

Taking the above chart service as an example, when the target cluster needs to use the chart service corresponding to the target chart resource, the corresponding fee can be paid to purchase the chart service, and then the chart resource can be deployed through the first terminal. The target cluster includes at least one second terminal to be deployed. If the second terminal purchases the communication service of the social application program, the first terminal will call the Helm package manager to send a deployment command to the server, download the image installation package of the social application program to the second terminal for installation, and provide corresponding communication services.

Furthermore, in the subsequent maintenance phase of the chart service, such as updating the version of the application program or adding other verification rules for resource files, it is only necessary to update the target chart resource accordingly, and then deploy it to the target cluster without rewriting the deployment document. Manual deployment is performed again through manual review, which not only reduces the cost of maintenance, but also improves deployment efficiency.

To sum up, in the technical solution provided by the embodiment of the present application, in the target chart resource verification stage, the server automatically performs resource permission verification on the resource file of the target chart resource by receiving the verification command sent by the first terminal, no longer relying on manual review, shortening the review cycle, and improving the accuracy of resource permission verification; in the deployment stage of the target chart resource, when the server receives the deployment instruction, the server also automatically executes the deployment operation without manual deployment according to the deployment document.

Fig. 3 shows a flowchart of a chart resource deployment method provided by an exemplary embodiment of the present application. In this embodiment, the method is described by using the server 120 shown in FIG. 1 as an example. The method includes the following steps:

Step 301 , in response to receiving the verification instruction of the target chart resource, acquire the account identifier of the first terminal contained in the verification instruction and the resource identifier of the target chart resource.

In the development stage of the chart resource, the developer writes the target chart resource through the first terminal. The target chart resource contains the resource files to realize the chart service, such as the default configuration file of the chart, other dependent chart resources, the basic information of the chart, and the deployment file template directory.

After the developer finishes writing and packaging it into a TAR or GZ compressed package, upload it to the chart warehouse in the server through the first terminal. The chart warehouse is specially used to store the uploaded chart resources. Optionally, the chart warehouse takes the user account as the unit, stores all chart resources under the same account in the chart warehouse, and facilitates subsequent management of the chart resources in the chart warehouse.

In a possible implementation, a local chart warehouse can be set on the first terminal to store various resource files temporarily written by developers, and then upload the packaged target chart resources to the chart warehouse after the writing is completed.

Before performing resource permission verification, the first terminal needs to select a target chart resource that needs to be verified on the chart resource management interface, and after determining the target chart resource that needs to be verified, send a verification instruction to the server. After receiving the verification instruction sent by the first terminal, the server obtains the account identifier contained in the verification instruction and the resource identifier of the target chart resource, so as to determine the target chart resource from the chart warehouse.

Step 302, based on the resource identifier, acquire the target chart resource from the chart warehouse, which contains all the chart resources uploaded by the first terminal.

After receiving the verification instruction, the server determines the account identifier corresponding to the first terminal and the resource identifier corresponding to the target chart resource. When the chart repository contains multiple candidate chart resources uploaded by the first terminal, the server may determine the target chart resource that needs resource permission verification from the multiple candidate chart resources based on the resource identifier.

Step 303: Obtain verification information corresponding to the first terminal based on the account identifier.

Since the chart resource uploaded by the first terminal to the chart warehouse is stored in the form of a compressed package, which includes multiple resource files, the deployment operation can only be performed after ensuring that the resource attributes of each resource file meet the deployment conditions of the target chart resource. The verification information is used to verify the resource attributes of the target chart resource and the writing specification of the target chart resource, so as to ensure that the target chart resource can be deployed in the cluster system.

Step 304, based on the verification information, perform resource permission verification on the target chart resource.

After obtaining the verification information corresponding to the first terminal, the server starts to verify the resource authority of the target chart resource. Since the target chart resource contains multiple resource files, different resource files correspond to their own attribute information, such as the resource type (Kind), resource name (Name), and space name (Namespace) of the resource file. The server needs to verify the attribute information. In addition, the server also needs to write specifications for each resource file and verify the storage space in the target chart resource. As shown in Figure 4, the process specifically includes the following steps:

Step 304A, based on the first resource attribute in the verification information, perform a first resource attribute verification on the resource file in the target chart resource, where the first resource attribute is a resource attribute supported by the cluster system.

After the server obtains the target chart from the chart warehouse, it needs to parse it, obtain all resource files contained in it, and determine the resource type of each resource file. In a native Kubernetes cluster, the cluster system can support multiple types of resource files such as Deployment, Service, and Route. Different types of resource files are used to implement corresponding functions. For example, Service resource files are used to provide network services, and Route resource files are used to provide storage services. In addition, the cluster system can also customize the resource type of the resource file according to the requirements. For different cluster systems, the types of resource files it can support will vary. When the resource attributes of the resource files in the target chart resource do not belong to the resource attributes supported by the cluster system, the cluster system may not be able to correctly identify or read the data information in it. Therefore, after the server obtains the resource attributes of each resource file, it needs to obtain the first resource attribute of the cluster system from the configuration center, and verify the resource files in the target chart resource.

Schematically, the first resource attributes supported by the cluster system include type A, type B, and type C, and the resource attributes of the resource files in the target chart resource include type A, type B, type C, and type D. Since the cluster system does not support resource files of type D, it cannot be deployed to the cluster system. At this time, a prompt message should be fed back to the first terminal so that developers can modify unrecognized resource attributes.

Step 304B, based on the resource file writing rules in the verification information, check the writing compliance of the resource files in the target chart resource.

It can be seen from the above that the resource name and space name of each resource file in the target chart resource are written by the developer, and the developer cannot guarantee that the name and writing specification of the resource file fully meet the deployment requirements of the cluster system. For example, templates in the chart resource defines the resource type of the resource file, and appVersion defines the version information of the target chart resource. When the names of the files do not match, the server cannot determine the resource type, version information, etc. Therefore, after the server parses the target chart resource, it also needs to verify the writing compliance of the resource file in the target chart resource according to the resource file writing rules in the verification information.

In addition, system keywords are defined in the cluster system, such as data type keywords, control statement keywords, and storage class keywords. Developers should avoid using system keywords when writing resource files, so as not to affect data identification. Therefore, the resource file writing rules can also define the character length and keywords of the resource name and space name, and when it is detected that the character length of the resource name or control name exceeds the set threshold, or when a keyword is detected, prompt information is fed back to the first terminal in time.

Step 304C, in response to passing the first resource attribute verification and writing compliance verification, based on the second resource attribute in the verification information, perform a second resource attribute verification on the resource file in the target chart resource, and the second resource attribute is a resource attribute that the first terminal has deployment authority.

After the target chart resource passes the first resource attribute verification and writing compliance verification, it is also necessary to verify the permission information of the first terminal. The cluster system is an open source system in nature. Developers can upload and deploy chart resources through the cluster system. However, in order to better maintain the cluster system, different developers need to be given deployment permissions of different resource attributes. When verifying the second resource attribute, the server obtains the second resource attribute of the first terminal from the authority center according to the account identifier, that is, the resource attribute for which the first terminal has deployment authority, and then matches it with the resource attribute of the resource file in the target chart resource.

Schematically, the second resource attribute indicates that the first terminal has the deployment authority to deploy resource files of the Deployment and Service types, and the target chart resource contains resource files of the Route type. Since the cluster system does not grant the first terminal the deployment authority to deploy resource files of the Route type, it cannot pass the resource authority check. Correspondingly, a prompt message can be fed back to the first terminal.

It should be noted that the above schematic examples only use Deployment, Service, and Route types as examples. In an actual cluster system, since different cluster systems can customize resource types, the cluster system needs to grant deployment permissions to corresponding resource types according to the identity or job responsibilities of different developers. The specific resource types are not limited in this embodiment.

Step 304D, determine the remaining storage space based on the total storage space and the occupied storage space in the verification information, the total storage space is the maximum available space for deploying the chart resources of the first terminal, and the occupied storage space is the space occupied by the deployed chart resources of the first terminal.

The server not only needs to perform first resource attribute verification, second resource attribute verification, and writing compliance verification on the target chart resource, but also needs to perform storage space verification on the target chart resource.

In the cluster system, the deployed chart resources are stored in the namespace (Namespace). Namespace is an abstract collection of a group of resources and objects. For example, it can be used to divide the objects in the system into different project groups or user groups. Common pods, services, replication controllers and deployments all belong to a certain Namespace. Different Namespaces are logically isolated from each other to achieve efficient management of chart resources. After the first terminal deploys chart resources, the corresponding Namespace will occupy a certain amount of storage space. Therefore, when the server performs resource permission verification, it needs to obtain the total storage space of the first terminal and the space occupied by the deployed chart resources according to the account ID, and then determine the remaining storage space according to the total storage space and the occupied storage space.

Step 305E, based on the remaining storage space and the target occupied space of the target chart resource, check the storage space of the target chart resource.

Since a Namespace needs to be created in the cluster system when deploying target chart resources, after the server determines the storage space required for deploying target chart resources, it compares the remaining storage space with the storage space required for deploying target chart resources. When the remaining storage space is greater than the storage space required for deploying the target chart resource, it is determined that the target chart resource meets the deployment requirements of the cluster system, and then it is deployed in the cluster system.

It should be noted that the storage space verification of the target chart resource can also be performed before step 304A and step 304B, and the server executes steps 304A and 304B after determining that the storage space verification passes. The embodiment of the present application does not limit the sequence of storage space verification.

Step 305, in response to the target chart resource passing the resource permission check, setting the target chart resource to a deployable state.

When the server determines that the first resource attribute verification, the second resource attribute verification, the writing compliance verification and the storage space all pass, it determines that the target chart resource has passed the resource permission verification, and then sets the target chart resource to a deployable state, and pushes the target chart resource to the cluster system.

After the server sets the target chart resource to a deployable state, it can also feed back the resource permission verification result to the first terminal. As shown in Figure 5, the chart resource management interface 510 is displayed on the first terminal. Before the first terminal sends a verification command, the life cycle of the chart resource is displayed as under development; when the user clicks the verification control 511 of the target chart resource, the first terminal sends a verification command to the server, and then updates the life cycle to being under review, indicating that the server is verifying the resource permission of the target chart resource; The terminal feeds back the resource permission verification result, and the life cycle of the target chart resource is displayed as being released.

Step 306, in response to receiving the deployment instruction for the target chart resource, acquire the cluster identifier of the target cluster and the resource identifier of the target chart resource included in the deployment instruction.

When the first terminal needs to deploy the target chart resource to the target cluster in the cluster system, it sends a deployment instruction to the server by selecting the resource identifier of the target chart resource and the cluster identifier of the target cluster. The cluster identifier is used to determine the name and version information of the target chart resource, such as AbcChart, V2.0. After receiving the deployment instruction sent by the first terminal, the server first obtains the cluster identifier of the target cluster and the resource identifier of the target chart resource contained in the verification instruction, and then determines the target chart resource according to the resource identifier.

Step 307, based on the resource identifier, obtain the target chart resource from the chart warehouse.

For the implementation manner of this step, reference may be made to step 302, and details are not described here in this embodiment.

Step 308, based on the cluster identifier, the configuration parameters of the target chart resource are updated.

Since the cluster system usually includes many terminal devices, multiple clusters can be formed between different devices. For example, if a cluster is established by an enterprise, the second terminal in the target cluster is all terminal devices within the enterprise. In addition, for the same target chart resource, there will be differences between the target clusters. For example, for the Chinese cluster and the Singapore cluster, due to regional differences and different standards, configuration parameters need to be updated according to the cluster ID when deploying. The process specifically includes the following steps:

Step 308A, based on the cluster identifier, acquire cluster configuration information of the target cluster from the configuration center.

Before the first terminal sends the deployment command, the target cluster should be established in advance according to the second terminal, and a database providing chart service for the target cluster should be established.

In a possible implementation, after the enterprise purchases the target chart resource and the corresponding chart service, the operation and maintenance personnel need to establish the target cluster for the enterprise through the first terminal, and assign the account and login key of the chart service to the target cluster. In addition, it also includes setting the cluster ID of the target cluster and the cluster configuration information (config) of the target cluster, such as the working region, Hadoop component version, and instance node specifications. The higher the instance node specifications, the larger the capacity, the faster the cluster runs, the stronger the analysis and processing capabilities, and the higher the corresponding cost. The cluster configuration information and the cluster ID are associated and stored in the configuration center of the server. When deploying, the configuration parameters of the target chart resource need to be determined according to the target cluster that actually needs to be deployed.

In step 308B, the configuration parameters of the target chart resource are updated based on the cluster configuration information.

In a possible implementation manner, the configuration parameters related to the target cluster are marked in the target chart resource, and the configuration parameters are replaced after the cluster configuration information of the target cluster is obtained. If the instance node in the target chart resource is set to N before the update, the updated instance node is set to 16, indicating 16 1-core SSD nodes. In addition, the updated configuration parameters may also include the number of MPP data partitions and a default language (Language), which are not limited in this embodiment of the present application.

Step 309, perform pre-verification on the updated target chart resource, the pre-verification includes verification of database configuration, memory resource verification and connection status verification.

After the server updates the configuration parameters of the target chart resource, it needs to perform pre-verification on the target chart resource. Pre-verification includes verification of database configuration, memory resources, and connection status to ensure that the database can provide services to the target cluster. The process specifically includes the following steps:

Step 309A, based on the cluster identifier, obtain the pre-verification rules of the target cluster from the configuration center.

The pre-verification rules include at least the access address of the database, the account number and login key of the chart service, and other information. In addition, the pre-verification rules include the memory resources and domain name information of the target cluster, which are associated with the cluster ID of the target cluster and stored in the configuration center. When the server needs to pre-verify the target cluster, it should first obtain the pre-verification rules of the target cluster from the configuration center, and then perform pre-verification on the updated target chart resource.

Step 309B, perform pre-verification on the updated target chart resource based on pre-verification rules.

After the server obtains the pre-verification rules, it verifies whether the access address of the database is valid, verifies whether the account number and login key of the chart service match, and whether the memory resources of the target cluster are sufficient, etc. In addition, the server also needs to judge whether the network bandwidth of the cluster system and the network connection with the target cluster are normal, so as to ensure that services can be provided to the target cluster.

Step 310, in response to passing the pre-verification, perform pre-execution on the target chart resource.

When the target chart resource passes the pre-verification, the server needs to further pre-execute the target chart resource, and the pre-execution includes updating the database of the target chart resource. The database is maintained by the operation and maintenance personnel. When the operation and maintenance personnel add or delete data or modify the data content in the database, if the database content is not updated in time and the data service is directly provided to the target cluster, an error will be reported during the deployment of the target chart resource to the target cluster or the application program will not be able to achieve the corresponding functions. Therefore, the server needs to perform a data update on the database every time the target chart resource is deployed, so as to ensure the real-time performance of the database.

In addition, the pre-execution process may also include updating the service configuration center, which stores adjustment parameters for implementing chart services, including display time settings, current limiting policies, background color settings, and display widgets. These service configurations do not have a fixed format, so they need to be stored in an independent service configuration center, and operation and maintenance personnel can modify them according to actual needs. There are generally two ways to update it. In the pull mode, the server regularly pulls the data from the service configuration center; in the push mode, the service is always connected to the service configuration center. Once a configuration change is detected, the modified adjustment parameters are automatically pushed to the target cluster.

Step 311 , deploying the target chart resource to the target cluster in response to passing the pre-execution.

After the target chart resource is pre-executed, the target chart resource is deployed to the target cluster, so as to provide chart services to the second terminal in the target cluster.

Taking installing an application program as an example, after the first terminal selects a target cluster and a target chart resource, it sends a deployment instruction to the server. Since the second terminal and the server in the target cluster run in the same cluster system, the second terminal automatically downloads the image installation package of the application program from the cluster system through the Helm package manager for installation and establishes a connection with the database.

In order to obtain the deployment status of the target cluster, the server monitors and receives the deployment information fed back by the second terminal in real time during the deployment process, and generates a corresponding log file for storage.

Schematically, as shown in FIG. 6, the first terminal displays a Chart resource management interface 610. After the user selects a target chart resource and a target cluster, the user clicks on the deployment control 611 to send a deployment command to the server. In the deployment phase, the deployment status and deployment progress of the target chart resource are displayed through the deployment status bar 612.

In addition, as shown in FIG. 7 , the Chart resource management interface 710 can also be displayed on the first terminal, and the life cycle of each chart resource and the version information of the chart resource are displayed on the Chart resource management interface 710. For a chart resource that has not been verified for resource permissions, the life cycle is displayed as under development; for a chart resource that has been verified for resource permissions, the life cycle is displayed as being reviewed;

Step 312, in response to receiving an update instruction for the target chart resource, obtain version information of the target chart resource in the update instruction, and update the target chart resource based on the version information.

After the deployment of the target chart resource is completed, the second terminal installation completes the installation of the application program and the use of related functions of the application program. In the maintenance phase of the application program, if the application program needs to be updated or version upgraded, the first terminal needs to update the target chart resource, and then deploy it to the cluster system. When the server receives the update command for the target chart resource, it obtains the version information of the target chart resource saved in the update command, updates the target chart resource based on the version information, and then automatically checks the resource permissions of the updated target chart resource to complete the version update of the application.

In the embodiment of the present application, after receiving the verification instruction of the target chart resource, the server automatically obtains the verification information according to the account ID contained in the verification instruction and the resource ID of the target chart resource; then, according to the first resource attribute in the verification information, the first resource attribute verification is performed on the target chart resource; according to the resource file writing rules in the verification information, the writing compliance verification of the resource files in the target chart resource file is performed, and when the first resource attribute verification and the resource file writing rules are passed, the second resource attribute verification is performed on the resource files in the target chart resource to ensure that the first terminal has deployment capabilities The deployment permission of the corresponding resource file;

In addition, the server also needs to verify the storage space of the target chart resource to ensure that the remaining storage space of the first terminal in the cluster system is sufficient to deploy the target chart resource. Since the resource permission verification step is automatically performed by the server, compared with manual review, the review period is shortened and the accuracy of resource permission verification is improved;

When the server receives the deployment command from the first terminal, it automatically updates the configuration parameters of the target chart resource and performs pre-check and pre-execution steps on the target chart resource according to the cluster ID of the target cluster and the resource ID of the target chart resource in the deployment command;

Furthermore, when both the pre-verification and pre-execution pass, the target chart resource is deployed to the target cluster, so that the target cluster can realize the corresponding chart service. In the subsequent maintenance phase, after the server receives the update command for the target chart resource, it automatically updates the version of the application. Compared with manual deployment according to the deployment document, it not only reduces the cost of maintenance, but also improves the deployment efficiency.

FIG. 8 shows a structural block diagram of an apparatus for deploying chart resources provided by an embodiment of the present application.

The verification module 801 is configured to perform resource authority verification on a target chart resource in response to receiving a verification instruction sent by the first terminal, where the target chart resource is a chart resource uploaded by the first terminal, and different chart resources are used to implement different chart services;

A setting module 802, configured to set the target chart resource to a deployable state in response to the target chart resource passing the resource permission check;

The deployment module 803 is configured to, in response to receiving a deployment instruction for the target chart resource, deploy the target chart resource to a target cluster, where the target cluster includes at least one second terminal of the chart service to be deployed.

Optionally, the verification module 801 includes:

A first obtaining unit, configured to, in response to receiving the verification instruction of the target chart resource, obtain the account identifier of the first terminal contained in the verification instruction and the resource identifier of the target chart resource;

The second obtaining unit is configured to obtain the target chart resource from a chart warehouse based on the resource identifier, and the chart warehouse contains all the chart resources uploaded by the first terminal;

a third obtaining unit, configured to obtain verification information corresponding to the first terminal based on the account identifier;

A verification unit, configured to perform resource permission verification on the target chart resource based on the verification information.

Optionally, the verification unit is used for:

Based on the first resource attribute in the verification information, perform a first resource attribute verification on the resource file in the target chart resource, where the first resource attribute is a resource attribute supported by the cluster system;

Based on the resource file writing rules in the verification information, write compliance verification is performed on the resource files in the target chart resource.

Optionally, the verification unit is also used for:

In response to passing the first resource attribute verification and the writing compliance verification, based on the second resource attribute in the verification information, perform a second resource attribute verification on the resource file in the target chart resource, the second resource attribute is a resource attribute that the first terminal has deployment authority;

Determine the remaining storage space based on the total storage space and the occupied storage space in the verification information, the total storage space is the maximum available space for the first terminal to deploy chart resources, and the occupied storage space is the space occupied by the first terminal that has deployed chart resources;

Based on the remaining storage space and the target occupied space of the target chart resource, check the storage space in the target chart resource.

Optionally, the deployment module 803 includes:

A fourth acquiring unit, configured to acquire the cluster identifier of the target cluster and the resource identifier of the target chart resource contained in the deployment instruction in response to receiving the deployment instruction for the target chart resource;

A fifth acquiring unit, configured to acquire the target chart resource from the chart warehouse based on the resource identifier;

An updating unit, configured to update configuration parameters of the target chart resource based on the cluster identifier;

A pre-verification unit, configured to perform pre-verification on the updated target chart resource, the pre-verification includes database configuration verification, memory resource verification and connection status verification;

a pre-execution unit, configured to perform pre-execution on the target chart resource in response to passing the pre-check;

A deployment unit, configured to deploy the target chart resource to the target cluster in response to passing the pre-execution.

Optionally, the updating unit is used for:

Obtaining cluster configuration information of the target cluster from a configuration center based on the cluster identifier;

updating the configuration parameters of the target chart resource based on the cluster configuration information;

Optionally, the pre-verification of the line is used for:

Based on the cluster identifier, acquire the pre-verification rules of the target cluster from the configuration center;

The pre-check is performed on the updated target chart resource based on the pre-check rule.

Optionally, the device also includes:

An update module, configured to, in response to receiving an update instruction for the target chart resource, acquire version information of the target chart resource in the update instruction, and update the target chart resource based on the version information.

Fig. 9 shows a schematic structural diagram of a server provided by an exemplary embodiment of the present application. Specifically: the server includes a central processing unit (Central Processing Unit, CPU) 901, a system memory 904 including a random access memory 902 and a read-only memory 903, and a system bus 905 connecting the system memory 904 and the central processing unit 901. The server 900 also includes a basic input/output system (Input/Output, I/O system) 906 for transferring information between various devices in the computer, and a mass storage device 907 for storing an operating system 913, application programs 914 and other program modules 915.

The basic input/output system 906 includes a display 908 for displaying information and an input device 909 such as a mouse and a keyboard for a user to input information. Both the display 908 and the input device 909 are connected to the central processing unit 901 through the input and output controller 910 connected to the system bus 905 . The basic input/output system 906 may also include an input output controller 910 for receiving and processing input from a number of other devices such as a keyboard, mouse, or electronic stylus. Similarly, input output controller 910 also provides output to a display screen, printer, or other type of output device.

Mass storage device 907 is connected to central processing unit 901 through a mass storage controller (not shown) connected to system bus 905 . Mass storage device 907 and its associated computer-readable media provide non-volatile storage for server 900 . That is, mass storage device 907 may include a computer-readable medium (not shown) such as a hard disk or drive.

Without loss of generality, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media include random access memory (RAM, Random Access Memory), read-only memory (ROM, Read Only Memory), flash memory or other solid-state storage technologies, compact disc read-only memory (CD-ROM), digital versatile disc (Digital Versatile Disc, DVD) or other optical storage, tape cassettes, tapes, magnetic disk storage or other magnetic storage devices. Certainly, those skilled in the art know that the computer storage medium is not limited to the above-mentioned ones. The above-mentioned system memory 904 and mass storage device 907 may be collectively referred to as memory.

The memory stores one or more programs, the one or more programs are configured to be executed by one or more central processing units 901, the one or more programs include instructions for implementing the above method, and the central processing unit 901 executes the one or more programs to implement the chart resource deployment method provided by the above method embodiments.

According to various embodiments of the present application, the server 900 can also run on a remote computer connected to the network through a network such as the Internet. That is to say, the server 900 can be connected to the network 912 through the network interface unit 911 connected to the system bus 905, or can use the network interface unit 911 to connect to other types of networks or remote computer systems (not shown).

The memory also includes one or more programs, the one or more programs are stored in the memory, and the one or more programs include the steps executed by the server in the method provided by the embodiment of the present application.

In addition, those skilled in the art can understand that the structure of the server shown in the above figures does not constitute a limitation on the server, and the server may include more or less components than those shown in the figure, or combine some components, or arrange different components. For example, the server also includes components such as a radio frequency circuit, an input unit, a sensor, a server, and a power supply, which will not be repeated here.

The present application provides a computer-readable storage medium, at least one instruction is stored in the storage medium, and the at least one instruction is loaded and executed by a processor to implement the chart resource deployment method provided by the above method embodiments.

The present application also provides a computer program product or computer program, the computer program product or computer program comprising computer instructions stored in a computer-readable storage medium. The processor of the server reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the server executes the chart resource deployment method in any one of the above embodiments.

The serial numbers of the above embodiments of the present application are for description only, and do not represent the advantages and disadvantages of the embodiments.

Those of ordinary skill in the art can understand that all or part of the steps of implementing the above-mentioned embodiments can be completed by hardware, and can also be completed by instructing related hardware through a program. The program can be stored in a computer-readable storage medium. The above-mentioned storage medium can be a read-only memory, a magnetic disk or an optical disk, etc.

The above are only optional embodiments of the present application, and are not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application shall be included within the protection scope of the present application.

Claims (8)

1. A method for deploying chart resources, characterized in that, the method is used for a server in a cluster system, and the method includes: In response to receiving the verification instruction of the target chart resource, acquire the account identifier of the first terminal contained in the verification instruction and the resource identifier of the target chart resource; Based on the resource identifier, the target chart resource is obtained from a chart warehouse, and the chart warehouse includes all chart resources uploaded by the first terminal; Acquiring verification information corresponding to the first terminal based on the account identifier; Based on the first resource attribute in the verification information, perform a first resource attribute verification on the resource file in the target chart resource, where the first resource attribute is a resource attribute supported by the cluster system; Based on the resource file writing rules in the verification information, perform writing compliance verification on the resource files in the target chart resource, the target chart resource is a chart resource uploaded by the first terminal, and different chart resources are used to implement different chart services; In response to the target chart resource passing the resource permission check, setting the target chart resource to a deployable state; In response to receiving a deployment instruction for the target chart resource, deploy the target chart resource to a target cluster, where the target cluster includes at least one second terminal of the chart service to be deployed. 2. The method according to claim 1, wherein the resource permission verification of the target chart resource based on the verification information includes: In response to passing the first resource attribute verification and the writing compliance verification, based on the second resource attribute in the verification information, perform a second resource attribute verification on the resource file in the target chart resource, the second resource attribute is a resource attribute that the first terminal has deployment authority; Determine the remaining storage space based on the total storage space and the occupied storage space in the verification information, the total storage space is the maximum available space for the first terminal to deploy chart resources, and the occupied storage space is the space occupied by the first terminal that has deployed chart resources; Based on the remaining storage space and the target occupied space of the target chart resource, check the storage space in the target chart resource. 3. The method according to claim 1 or 2, wherein the deploying the target chart resource to the target cluster in response to receiving a deployment instruction for the target chart resource comprises: In response to receiving the deployment instruction for the target chart resource, acquire the cluster identifier of the target cluster and the resource identifier of the target chart resource included in the deployment instruction; Obtaining the target chart resource from a chart warehouse based on the resource identifier; updating configuration parameters of the target chart resource based on the cluster identifier; Carrying out pre-verification on the updated target chart resource, the pre-verification includes database configuration verification, memory resource verification and connection status verification; In response to passing the pre-check, perform pre-execution on the target chart resource; In response to passing the pre-execution, deploying the target chart resource to the target cluster; Wherein, the pre-execution includes: updating the database of the target chart resource, or updating the service configuration center. 4. The method according to claim 3, wherein the updating the configuration parameters of the target chart resource based on the cluster identifier comprises: Obtaining cluster configuration information of the target cluster from a configuration center based on the cluster identifier; updating the configuration parameters of the target chart resource based on the cluster configuration information; The pre-verification of the updated target chart resource includes: Based on the cluster identifier, acquire the pre-verification rules of the target cluster from the configuration center; The pre-check is performed on the updated target chart resource based on the pre-check rule. 5. The method according to claim 1 or 2, wherein after the target chart resource is deployed to the target cluster, the method further comprises: In response to receiving an update instruction for the target chart resource, acquire version information of the target chart resource in the update instruction, and update the target chart resource based on the version information. 6. A device for deploying chart resources, characterized in that the device is used for servers in a cluster system, and the device includes: A verification module, configured to, in response to receiving a verification instruction of a target chart resource, obtain the account identifier of the first terminal included in the verification instruction and the resource identifier of the target chart resource; based on the resource identifier, obtain the target chart resource from a chart warehouse, the chart warehouse including all chart resources uploaded by the first terminal; obtain verification information corresponding to the first terminal based on the account identifier; perform a first resource attribute verification on a resource file in the target chart resource based on a first resource attribute in the verification information, and the first resource attribute is supported by the cluster system resource attributes; based on the resource file writing rules in the verification information, writing compliance verification is performed on the resource files in the target chart resource, the target chart resource is a chart resource uploaded by the first terminal, and different chart resources are used to implement different chart services; A setting module, configured to set the target chart resource to a deployable state in response to the target chart resource passing the resource permission check; The deployment module is configured to, in response to receiving a deployment instruction for the target chart resource, deploy the target chart resource to a target cluster, and the target cluster includes at least one second terminal of the chart service to be deployed. 7. A server, characterized in that the server comprises a processor and a memory; the memory stores at least one instruction, and the at least one instruction is used to be executed by the processor to implement the chart resource deployment method according to any one of claims 1 to 5. 8. A computer-readable storage medium, wherein at least one instruction is stored in the storage medium, and the at least one instruction is used to be executed by a processor to implement the chart resource deployment method according to any one of claims 1 to 5.