CN114500268B - Method and device for deploying char resources, server and storage medium - Google Patents
Method and device for deploying char resources, server and storage medium Download PDFInfo
- Publication number
- CN114500268B CN114500268B CN202210049979.6A CN202210049979A CN114500268B CN 114500268 B CN114500268 B CN 114500268B CN 202210049979 A CN202210049979 A CN 202210049979A CN 114500268 B CN114500268 B CN 114500268B
- Authority
- CN
- China
- Prior art keywords
- resource
- target
- hart
- verification
- char
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The embodiment of the application discloses a method, a device, a server and a storage medium for deploying char resources, and relates to the technical field of computers. The method comprises the following steps: in response to receiving a verification instruction sent by a first terminal, verifying resource authority of a target hart resource, wherein the target hart resource is a hart resource uploaded by the first terminal, and different hart resources are used for realizing different hart services; setting the target hart resource to a deployable state in response to the target hart resource passing the resource permission check; and in response to receiving a deployment instruction for the target hart resource, deploying the target hart resource to a target cluster, wherein the target cluster comprises at least one second terminal for which the hart service is to be deployed. The server automatically executes the resource permission verification and the automatic deployment operation, so that the auditing period is shortened, and the verification accuracy and the deployment efficiency are improved.
Description
Technical Field
The embodiment of the application relates to the technical field of computers, in particular to a method, a device, a server and a storage medium for deploying char resources.
Background
In the Kubernetes cluster, an operator performs a char resource deployment by using a Helm package manager to update and maintain an application.
In the prior art, before application updating and maintenance are performed, the char resource needs to be manually checked, and after the manual check is passed, manual deployment is performed through the operation steps indicated by the deployment document.
Disclosure of Invention
The embodiment of the application provides a method, a device, a server and a storage medium for deploying char resources. The technical scheme is as follows:
in one aspect, an embodiment of the present application provides a method for deploying a char resource, where the method is used for a server in a cluster system, and the method includes:
in response to receiving a verification instruction sent by a first terminal, verifying resource authority of a target hart resource, wherein the target hart resource is the hart resource uploaded by the first terminal, and different hart resources are used for realizing different hart services;
setting the target hart resource to a deployable state in response to the target hart resource passing a resource permission check;
and in response to receiving a deployment instruction for the target hart resource, deploying the target hart resource to a target cluster, wherein the target cluster comprises at least one second terminal for which the hart service is to be deployed.
In another aspect, an embodiment of the present application provides a device for deploying a char resource, where the device is used for a server in a cluster system, and the device includes:
the verification module is used for responding to a verification instruction sent by the first terminal and verifying resource authority of a target hart resource, wherein the target hart resource is the hart resource uploaded by the first terminal, and different hart resources are used for realizing different hart services;
the setting module is used for responding to the target hart resource to pass the resource authority verification and setting the target hart resource into a deployable state;
the deployment module is used for deploying the target hart resource to a target cluster in response to receiving a deployment instruction of the target hart resource, wherein the target cluster comprises at least one second terminal for which the hart service is to be deployed.
In another aspect, embodiments of the present application provide a server including a processor and a memory; the memory stores at least one instruction for execution by the processor to implement the method of task execution in a heterogeneous system as described in the above aspects.
In another aspect, embodiments of the present application provide a computer readable storage medium having a computer program stored therein, where the computer program is loaded and executed by a processor to implement the method for deploying a char resource according to the above aspect.
In another aspect, embodiments of the present application provide a computer program product, the computer program product, or computer program comprising computer instructions 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 performs the method for deploying the char resource according to the above aspect.
The beneficial effects that technical scheme that this application embodiment provided include at least:
in the embodiment of the application, in the target char resource verification stage, the server automatically verifies the resource authority of the resource file of the target char resource by receiving the verification instruction sent by the first terminal, and the verification period is shortened and the accuracy of the resource authority verification is improved without relying on manual verification; in the deployment stage of the target char resource, after the server receives the deployment instruction, the server also automatically executes the deployment operation, manual deployment according to a deployment document is not needed, and in the maintenance stage, the cost input of maintenance is reduced, and the deployment efficiency is improved.
Drawings
FIG. 1 is a network topology of a cluster system provided in one exemplary embodiment of the present application;
FIG. 2 is a flow chart of a method of deploying a char resource provided by an exemplary embodiment of the present application;
FIG. 3 is a flow chart illustrating a method of deploying a char resource according to another example embodiment of the present application;
FIG. 4 is a flow chart illustrating a method of deploying a char resource according to another example embodiment of the present application;
FIG. 5 illustrates an interface diagram of a char resource management interface provided by an exemplary embodiment of the present application;
FIG. 6 illustrates an interface diagram of a Chart resource management interface provided by an exemplary embodiment of the present application;
FIG. 7 illustrates an interface diagram of a Helm Chart management interface provided by an exemplary embodiment of the present application;
FIG. 8 is a block diagram of a mechanism for deploying char resources provided by an example embodiment of the present application;
fig. 9 shows a block diagram of a server according to an exemplary embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
References herein to "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
Clustering: clusters (clusters) are a group of independent computers interconnected through a high-speed network that form a group and are managed in a single system mode. When a client interacts with a cluster, the cluster appears as an independent server. Cluster configuration is used to increase availability and scalability. The cluster technology is a newer technology, through which relatively high gains in terms of performance, reliability, and flexibility can be obtained at a lower cost, and task scheduling is the core technology in the cluster system.
Kubernetes: kubernetes, abbreviated as K8s, is an abbreviation that replaces the 8 characters "ubennee" with 8. Is an open source for managing containerized applications on multiple hosts in a cloud platform, and 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 mode is to install the application through a plug-in or script. The disadvantage of this is that the running, configuration, management, all lifecycle of the application will be tied to the current operating system, which is not beneficial for the upgrade update/rollback etc. operations of the application, although some functions may be implemented by creating a virtual machine, which is very heavy and not beneficial for portability. The new mode is realized by deploying containers, each container is isolated from each other, each container has a file system, processes among the containers cannot affect each other, and computing resources can be distinguished. Compared with a virtual machine, the container can be rapidly deployed, and can migrate among different cloud and different version operating systems due to decoupling of the container from underlying facilities and machine file systems. The container occupies less resources and is quick to deploy, each application can be packaged into a container mirror image, the container is further advantageous due to the fact that each application is in one-to-one relation with the container, the container mirror image can be created for the application in the build or release stage by using the container, and because each application does not need to be combined with the rest of application stacks and does not depend on a production environment infrastructure, a consistent environment can be provided from research, development to testing and production.
Helm: helm is a packet manager of Kubernetes, and is also a client tool based on command lines. The method is mainly used for creating, packaging, publishing, and creating and managing the local and remote Chart warehouse of the Kubernetes application program Chart. In the embodiment of the application, when the char resource is deployed, the char resource is deployed by calling the Helm package manager.
In the related art, when developing and deploying the char resource through the Kubernetes cluster, a developer or an operation and maintenance person needs to manually check the resource authority; in addition, in the deployment stage of the char resource, an operation and maintenance personnel is usually required to manually execute according to the operation instruction of the deployment document, and when the operation steps are wrong, the inspection is required to be carried out again, so that the deployment efficiency is low.
In the embodiment of the application, when the resource authority of the uploaded target hart needs to be checked, the server can be used for automatically checking without manual verification, and when the hart resource is deployed, the preposed check and preposed update of the hart resource can be automatically realized, the manual verification is not dependent on the deployment document, the labor cost can be saved, and the efficiency of the checksum deployment can be improved.
Fig. 1 shows a network topology diagram of a cluster system according to an embodiment of the present application. The network topology map includes: a first terminal 110, a server 120, and a second terminal 130.
The first terminal 110 in the network topology is at least one of electronic devices such as a mobile phone, a desktop computer, a tablet computer, a multimedia playing device, and a laptop portable computer, the first terminal 110, the server 120, and the second terminal operate in the same Kubernetes cluster, the first terminal 110 is a terminal that publishes and deploys the char resource in the clustered system, and the first terminal 110 is installed with a Helm client through which the char resource is transmitted to the server 120. In addition, the first terminal 110 may also display the lifecycle of the char resource, and send a verification instruction and a deployment instruction to the server 120.
The server 120 is a device for providing data storage and a hart service in the cluster system, a hart resource and a database for running the hart service are stored in the server 120, the server 120 is further configured to receive a verification instruction of the first terminal 110, perform resource permission verification on the uploaded hart resource, and in addition, the server 120 is further configured to receive a deployment instruction of the first terminal 110, and provide the hart service to the second terminal 130.
The second terminal 130 is at least one of electronic devices such as a cellular phone, a desktop computer, a tablet computer, a multimedia playing device, and a laptop portable computer, the second terminal 130 is a terminal to which a char resource is to be deployed in the target cluster, and the second terminal 130 is installed with a Helm client through which a communication connection is established with the first terminal 110 and the server 120. Optionally, the second terminal 130 may also feed back deployment information to the server 120.
Those skilled in the art will appreciate that the number of the first and second terminals may be greater or lesser. For example, the second terminal may be only one, or the terminals may be tens or hundreds, or more. The number of terminals and the device type are not limited in the embodiment of the present application.
Fig. 2 is a flowchart of a method for deploying a char resource according to an exemplary embodiment of the present application, and this embodiment is described by taking the method for the server shown in fig. 1 as an example. The method comprises the following steps:
in step 201, in response to receiving a verification instruction sent by the first terminal, resource permission verification is performed on a target hart resource, where the target hart resource is a hart resource uploaded by the first terminal, and different hart resources are used to implement different hart services.
The server in the cluster system stores the hart resource uploaded by the first terminal, the hart resource is written by a developer, the hart resource comprises a group of YAML files related to the defined Kubernetes resource, the YAML files are stored in the server in a compressed package in TAR or GZ format, and the hart resource can be used for deploying at least one hart service, such as downloading and installing an application program through the hart resource, complete HTTP service and the like.
When a developer compiles and finishes the hart resource and needs to deploy the hart resource into a corresponding Kubernetes cluster, a verification instruction is sent to a server through a first terminal, and after the server receives the verification instruction sent by the first terminal, resource authority verification is automatically carried out on the target hart resource uploaded by the first terminal. The purpose of the resource authority verification is to ensure the validity and correctness of the resource file in the target hart resource and realize the corresponding hart service. In the prior art, the resource permission verification process is usually manually verified by operation and maintenance personnel of a Kubernetes platform, the manual verification period is long, and the verification accuracy is low. According to the scheme, the resource permission verification step is transplanted to the server, the verification instruction triggers the server to automatically execute, the verification period is greatly shortened, the cost investment of manual verification is reduced, and the accuracy of resource permission verification is improved.
Step 202, in response to the target hart resource passing the resource permission check, setting the target hart resource to a deployable state.
When the result of the resource authority verification meets the deployment requirement of the cluster system, the server sets the target char resource to be in a deployable state. In general, a cluster system includes a plurality of terminals, and the plurality of terminals and a server operate in the same cluster system, and for a deployable target part resource, the server pushes the deployable target part resource to the cluster system.
Illustratively, taking the downloading and installing of the target hart implementation application program as an example, for the deployable target hart resource, the server sends a loading notification of the target hart resource to other terminals of the cluster system in a message reminding manner, so that the other terminals can conveniently purchase the hart resource and the corresponding hart service, and the hart service comprises application program installation, application program updating and maintenance, background service for providing the application program and the like.
In step 203, in response to receiving the deployment instruction for the target char resource, the target char resource is deployed to a target cluster, where the target cluster includes at least one second terminal to be deployed.
All database resources and configuration information for realizing the hart service are stored in the server, and when the server receives a deployment instruction sent by the first terminal, the first terminal is required to deploy the target hart resources to the target cluster so as to provide the corresponding hart service for the target cluster. In the prior art, the process of deploying the char resources requires operation and maintenance personnel to perform manual deployment operation according to deployment documents, including operations such as information auditing of a target cluster, checking of database configuration of the target char resources, updating of databases and the like. In the scheme, the deployment instruction is used as a trigger mechanism in the process, and after the server receives the deployment instruction, the server automatically executes the deployment operation and is not executed through manual deployment.
Taking the above-mentioned hart service as an example, when the target cluster needs to use the hart service corresponding to the target hart resource, the corresponding fee can be paid to purchase the hart service, and then the hart resource is deployed through the first terminal. The target cluster comprises at least one second terminal to be deployed, for example, the second terminal purchases the communication service of the social application program, the first terminal sends a deployment instruction to the server by calling the Helm package manager, downloads the mirror image installation package of the social application program to the second terminal for installation, and provides corresponding communication service.
Further, in the subsequent maintenance stage of the hart service, if the version of the application program is updated or other verification rules for the resource file are added, only the target hart resource is required to be updated correspondingly, and then the target hart resource is deployed to the target cluster, a deployment document is not required to be rewritten, and the manual deployment is performed again in a manual auditing mode, so that the maintenance cost input is reduced, and the deployment efficiency is improved.
In summary, in the technical solution provided in the embodiments of the present application, in the target char resource verification stage, the server automatically performs resource permission verification on the resource file of the target char resource by receiving the verification instruction sent by the first terminal, without relying on manual verification, thereby shortening the verification period and improving the accuracy of the resource permission verification; in the deployment stage of the target char resource, after the server receives the deployment instruction, the server also automatically executes the deployment operation, manual deployment according to a deployment document is not needed, and in the maintenance stage, the cost input of maintenance is reduced, and the deployment efficiency is improved.
Fig. 3 illustrates a flowchart of a method for deploying a char resource according to an exemplary embodiment of the present application. This embodiment is described by taking the method for the server 120 shown in fig. 1 as an example, and the method includes the following steps:
step 301, in response to receiving a verification instruction of the target char resource, acquiring an account identifier of the first terminal and a resource identifier of the target char resource included in the verification instruction.
In the development stage of the hart resources, a developer writes target hart resources through the first terminal, wherein the target hart resources comprise resource files for realizing hart services, such as default configuration files of hart, other dependent hart resources, basic information of hart, deployment file template catalogues and the like.
After the developer compiles and packages the developer into TAR or GZ compressed packages, the TAR or GZ compressed packages are uploaded to a hart warehouse in the server through the first terminal, and the hart warehouse is specially used for storing uploaded hart resources. Optionally, the hart warehouse uses the user account as a unit, and stores all hart resources under the same account in the hart warehouse, so that the hart resources in the hart warehouse can be managed later.
In one possible implementation manner, a local hart warehouse may be set at the first terminal, and is used for storing various resource files temporarily written by a developer, and further uploading the packaged target hart resources to the hart warehouse after the writing is completed.
Before verifying the resource authority, the first terminal needs to select a target hart resource needing to be verified at a hart resource management interface, and after determining the target hart resource needing to be verified, a verification instruction is sent to the server. After receiving the verification instruction sent by the first terminal, the server acquires an account identifier and a resource identifier of the target hart resource, which are contained in the verification instruction, so that the target hart resource can be conveniently determined from the hart warehouse.
Step 302, based on the resource identifier, acquiring target hart resources from a hart warehouse, where the hart warehouse includes all hart resources uploaded by the first terminal.
After receiving the verification instruction, the server determines an account identifier corresponding to the first terminal and a resource identifier corresponding to the target char resource. When the part warehouse contains a plurality of candidate part resources uploaded by the first terminal, the server can determine a target part resource needing to be subjected to resource permission verification from the plurality of candidate part resources based on the resource identification.
And 303, acquiring verification information corresponding to the first terminal based on the account identifier.
Because the hart resources uploaded to the hart warehouse by the first terminal are stored in the form of compressed packets, the resources comprise a plurality of resource files, and deployment operation can be performed only after the resource attribute of each resource file is ensured to meet the target hart resource deployment condition. The verification information is used for verifying the resource attribute of the target hart resource and the writing specification of the target hart resource so as to ensure that the target hart resource can be deployed in the cluster system.
And step 304, verifying the resource authority of the target char resource based on the verification information.
After the server acquires the verification information corresponding to the first terminal, the server starts to verify the resource authority of the target char resource. Because the target char resource includes a plurality of resource files, different resource files all correspond to respective attribute information, such as attribute information of a resource type (Kind), a resource Name (Name), a space Name (Namespace) and the like of the resource file, and the server needs to verify the attribute information. In addition, the server also needs to write the specification for each resource file, check the storage space in the target char resource, and the like. As shown in fig. 4, the process specifically includes the steps of:
step 304A, based on the first resource attribute in the verification information, performing 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 hart from the hart warehouse, the target hart needs to be analyzed, all the resource files contained in the target hart are obtained, and the resource types of the resource files are determined. In the native Kubernetes cluster, the cluster system may support multiple types of resource files such as Deployment, service and Route, where different types of resource files are used to implement corresponding functions, such as Service resource files are used to provide network services, route resource files are used to provide storage services, and so on. In addition, the cluster system can also customize the resource types of the resource files according to the requirements, and for different cluster systems, the types of the resource files which can be supported by the cluster system can be different, and when the resource attribute of the resource file in the target char resource does not belong to the resource attribute supported by the cluster system, the cluster system can not correctly identify or read the data information in the resource attribute. Therefore, after the server obtains the resource attribute of each resource file, the server needs to obtain the first resource attribute of the cluster system from the configuration center, and verify the resource file in the target char resource.
Schematically, the first resource attribute supported by the cluster system includes type a, type B and type C, and the resource attribute of the resource file in the target char resource includes type a, type B, type C and type D, and since the cluster system does not support the resource file of type D, it cannot be deployed into the cluster system, and at this time, prompt information should be fed back to the first terminal, so that the developer modifies the unrecognizable resource attribute.
And step 304B, writing compliance verification is carried out on the resource file in the target chart resource based on the resource file writing rule in the verification information.
From the above, it can be known that the resource name and the space assignment of each resource file in the target char resource are written by a developer, and the developer cannot ensure that the name and the writing specification of the resource file completely meet the deployment requirement of the cluster system, for example, templates in the char resource define the resource type of the resource file, and appVersion defines the version information of the target char resource. When the names of the files cannot be matched, the server cannot determine the resource type, version information and the like. Therefore, after the server analyzes the target hart resource, writing compliance verification is performed on the resource file in the target hart resource according to the resource file writing rule in the verification information.
In addition, system keywords such as data type keywords, control statement keywords and storage type keywords are also defined in the cluster system, and a developer should avoid using the system keywords when writing resource files so as not to influence the identification of data. Therefore, the character length of the resource name and the space name, the keyword and the like can be defined in the resource file writing rule, and prompt information is timely fed back to the first terminal when the character length of the resource name or the control name is detected to exceed a set threshold value or the keyword is detected.
And step 304C, in response to the fact that the compliance verification is written through the first resource attribute verification sum, performing second resource attribute verification on the resource file in the target char resource based on the second resource attribute in the verification information, wherein the second resource attribute is the resource attribute with the deployment authority of the first terminal.
And after the target char resource passes the first resource attribute check and the writing compliance check, checking the authority information of the first terminal is also needed. The cluster system essentially belongs to an open source system, and developers can upload and deploy the char resources through the cluster system, but in order to better maintain the cluster system, deployment rights with different resource attributes need to be given to different developers. When the second resource attribute verification is carried out, the server acquires the second resource attribute of the first terminal from the right center according to the account identification, namely, the resource attribute of the first terminal with the deployment right, and then matches with the resource attribute of the resource file in the target char resource.
Schematically, the second resource attribute indicates that the first terminal has the Deployment authority for deploying the resource files of the replyment and Service types, and the target char resource contains the resource file of the Route type.
It should be noted that, in the foregoing illustrative example, deployment, service and Route types are merely taken as examples, in an actual clustered system, since different clustered systems can customize resource types, the clustered system needs to assign deployment rights of corresponding resource types according to identities or post responsibilities of different developers, and this embodiment of specific resource types is not limited thereto.
Step 304D, determining a remaining storage space based on the total storage space and the occupied storage space in the check information, where the total storage space is a maximum available space for the first terminal to deploy the char resource, and the occupied storage space is a space occupied by the deployed char resource 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 hart resource, but also needs to perform storage space verification on the target hart resource.
In a clustered system, deployed char resources are stored in a Namespace (Namespace), which is an abstract collection of a set of resources and objects, such as may be used to partition the objects within the system into different project groups or user groups. Common pos, services, replication controllers, and depoyments etc. all belong to a single Namespace. Different Namespaces are logically isolated from each other to enable efficient management of the char resources. When the first terminal deploys the char resources, the corresponding Namespace occupies a certain storage space, so that when the server performs resource permission verification, the total storage space of the first terminal and the space occupied by the deployed char resources need to be obtained according to the account identification, and the remaining storage space is further determined according to the total storage space and the occupied storage space.
Step 305E, performing storage space verification on the target char resource based on the remaining storage space and the target occupation space of the target char resource.
Because Namespace needs to be created in the cluster system when the target hart resource is deployed, after determining the storage space required by the deployment of the target hart resource, the server compares the remaining storage space with the storage space required by the deployment of the target hart resource. When the residual storage space is larger than the storage space required by deploying the target hart resource, determining that the target hart resource meets the deployment requirement of the cluster system, and deploying the target hart resource into the cluster system.
It should be noted that, the storage space verification on the target char resource may also be performed before the steps 304A and 304B, and the server may further perform the steps 304A and 304B if it is determined that the storage space verification passes. The embodiment of the application does not limit the sequence of the storage space verification.
In step 305, in response to the target hart resource passing the resource permission check, the target hart resource is set to a deployable state.
Under the condition that the server determines that the first resource attribute check, the second resource attribute check, the writing compliance check and the storage space are all passed, determining that the target hart resource passes the resource authority check, setting the target hart resource into a deployable state, and pushing the target hart resource to the cluster system.
After the server sets the target hart resource to a deployable state, the server may also feed back a resource authority verification result to the first terminal, as shown in fig. 5, where the hart resource management interface 510 is displayed on the first terminal, and before the first terminal does not send a verification instruction, the lifecycle of the hart resource is displayed as developing; after the user clicks the verification control 511 of the target char resource, the first terminal sends a verification instruction to the server, and further updates the life cycle into audit, which indicates that the server is performing resource permission verification on the target char resource; when the server passes the resource authority verification of the target char resource, the resource authority verification result is fed back to the first terminal, and the life cycle of the target char resource is displayed as on shelf.
Step 306, in response to receiving the deployment instruction for the target char resource, acquiring the cluster identifier of the target cluster and the resource identifier of the target char resource included in the deployment instruction.
When the first terminal needs to deploy the target hart resource to a target cluster in the cluster system, a deployment instruction is further sent to the server by selecting a resource identifier of the target hart resource and a cluster identifier of the target cluster. The cluster identity is used to determine the name of the target char resource as well as version information, such as abchart, V2.0. After receiving a deployment instruction sent by a first terminal, a server firstly acquires a cluster identifier of a target cluster and a resource identifier of a target hart resource contained in a verification instruction, and then determines the target hart resource according to the resource identifier.
Step 307, based on the resource identification, obtaining the target hart resource from the hart warehouse.
The implementation of this step may refer to step 302, and this embodiment is not described herein.
Step 308, updating the configuration parameters of the target char resource based on the cluster identification.
Because the cluster system generally comprises more terminal devices, different devices can form a plurality of clusters, for example, a cluster is built by taking an enterprise as a unit, and a second terminal in the target cluster is all terminal devices in the enterprise. In addition, for the same target char resource, there may be a difference between target clusters, such as a middle cluster and a singapore cluster, and since the regional difference and the compliance standard are different, the configuration parameters need to be updated according to the cluster identifier when deployment is performed. The process specifically comprises the following steps:
Step 308A, based on the cluster identification, obtains cluster configuration information of the target cluster from the configuration center.
Before the first terminal sends the deployment instruction, the target cluster is established in advance according to the second terminal, and a database for providing the char service for the target cluster is provided.
In one possible implementation, after the enterprise purchases the target chat resource and the corresponding chat service, the operation and maintenance personnel needs to establish a target cluster for the enterprise through the first terminal, and allocate an account number, a login key, and the like of the chat service for the target cluster. In addition, the method also comprises the steps of setting the cluster identification of the target cluster and the cluster configuration information (config) of the target cluster, such as a working region, a Hadoop component version, an instance node specification and the like. The higher the specification of the example node is, the larger the capacity is, the faster the cluster running speed is, the stronger the analysis processing capacity is, and the corresponding cost is also higher. The cluster configuration information and the cluster identification are stored in a configuration center of the server in an associated mode. When deployment is performed, the configuration parameters of the target char resources are required to be determined according to the target clusters which are actually required to be deployed.
Step 308B, updating the configuration parameters of the target char resource based on the cluster configuration information.
In one possible implementation, the configuration parameters related to the target cluster are marked in the target char resource, and after the cluster configuration information of the target cluster is obtained, the configuration parameters are replaced. If the instance node in the target char resource is set to N before the update is performed, the updated instance node is set to 16, which represents 16 1-core SSD nodes. In addition, the updated configuration parameters may further include the number of MPP data partitions, a default Language (Language), and the like, which is not limited in the embodiment of the present application.
Step 309, performing pre-verification on the updated target char resource, where the pre-verification includes verification on database configuration, verification on memory resource, and verification on connection status.
After the server updates the configuration parameters of the target char resource, the pre-verification of the target char resource is further needed. The pre-verification includes configuration verification, memory resource verification and connection status verification of the database, so as to ensure that the database can provide service for the target cluster. The process specifically comprises the following steps:
step 309A, based on the cluster identity, obtains a pre-verification rule for the target cluster from the configuration center.
The pre-verification rule at least comprises information such as an access address of a database, an account number of the char service, a login key and the like. In addition, the pre-verification rule also comprises memory resources, domain name information and the like of the target cluster, and the memory resources, the domain name information and the like are stored in the configuration center in association with the cluster identification of the target cluster. When the server needs to perform pre-verification on the target cluster, the pre-verification rule of the target cluster is firstly obtained from the configuration center, and then pre-verification is performed on the updated target char resource.
Step 309B, performing a pre-verification on the updated target chart resource based on the pre-verification rule.
After the server acquires the pre-verification rule, verifying whether the access address of the database is valid, verifying whether the account number and the login key of the char service are matched, verifying whether the memory resource of the target cluster is sufficient, and the like. In addition, the server needs to determine whether the network bandwidth of the cluster system and the network connection with the target cluster are normal, so as to ensure that the service can be provided to the target cluster.
In response to passing the pre-check, a pre-execution is performed on the target char resource, step 310.
When the target char resource passes the pre-verification, the server further needs to perform pre-execution on the target char resource, where the pre-execution includes updating a database of the target char resource. The database is maintained by operation and maintenance personnel, when the operation and maintenance personnel adds and deletes data or modifies data content in the database, if the database content is not updated in time, the database can directly provide data service for the target cluster, and errors can occur in the process of deploying target char resources to the target cluster or corresponding functions can not be realized by application programs. Therefore, the server needs to perform data update on the database once every time the target hart resource is deployed, so as to ensure the real-time performance of the database.
In addition, the pre-execution process may further include updating a service configuration center, where adjustment parameters for implementing the char service are stored in the service configuration center, including relevant configurations such as display time setting, current limiting policy, background color setting, and display hanging element. These service configurations do not have a fixed format and therefore need to be stored by a separate service configuration center, which can be modified by the operator according to the actual requirements. The updating modes are generally two, namely a pull mode, and the server regularly pulls the data of the service configuration center; in push mode, the service is always connected to the service configuration center, and once the configuration change is detected, the modified adjustment parameters are automatically pushed to the target cluster.
Step 311, in response to executing through the preamble, deploys the target char resource to the target cluster.
And after the target hart resource is executed through the front end, deploying the target hart resource part into the target cluster to realize the provision of hart service to the second terminal in the target cluster.
Taking the installation application program as an example, after the first terminal selects the target cluster and the target char resource, a deployment instruction is sent to the server. Because the second terminal and the server in the target cluster operate in the same cluster system, the second terminal automatically downloads the mirror image installation package of the application program from the cluster system through the Helm package manager for installation and establishes connection with the database.
In order to obtain the deployment state of the target cluster, the server monitors and receives the deployment information fed back by the second terminal in real time in the deployment process, and generates a corresponding log file for storage.
Schematically, as shown in fig. 6, the first terminal displays a hart resource management interface 610, after a user selects a target hart resource and a target cluster, a deployment command is sent to the server by clicking a deployment control 611, and in a deployment stage, a deployment state and a deployment progress of the target hart resource are displayed through a deployment state column 612.
In addition, as shown in fig. 7, a hart resource management interface 710 may be displayed on the first terminal, and the lifecycle of each hart resource, the version information of the hart resource, etc. may be displayed on the hart resource management interface 710, where the lifecycle of the hart resource that is not verified by the resource authority is displayed as being under development; for the char resource for verifying the resource authority, the life cycle is displayed as in the auditing; for the char resource with the completed resource authority verification, the life cycle is displayed as on-shelf; for a char resource that is out of maintenance, its lifecycle is shown as off-shelf.
In step 312, in response to receiving the update instruction for the target hart resource, version information of the target hart resource in the update instruction is obtained, and the target hart resource is updated based on the version information.
After the target char resource deployment is completed, the second terminal installs and completes the application program installation and uses the related functions of the application program. In the maintenance stage of the application program, if the application program needs to be updated or version-up, the first terminal needs to update the target char resource and then deploy the target char resource into the cluster system. After receiving the update instruction for the target hart resource, the server acquires version information of the target hart resource stored in the update instruction, updates the target hart resource based on the version information, and further automatically performs resource permission verification on the target hart resource after version update to complete version update of the application program.
In the embodiment of the application, after receiving the verification instruction of the target hart resource, the server automatically acquires verification information according to the account identification contained in the verification instruction and the resource identification of the target hart resource; further, according to the first resource attribute in the verification information, verifying the first resource attribute of the target char resource; according to the resource file writing rule in the verification information, writing compliance verification is carried out on the resource file in the target hart resource file, and under the condition that the first resource attribute verification and the resource file writing rule are passed, second resource attribute verification is carried out on the resource file in the target hart resource, so that the first terminal is ensured to have deployment authority for deploying the corresponding resource file;
In addition, the server also needs to perform storage space verification on the target hart resources to ensure that the residual storage space of the first terminal in the cluster system is enough to deploy the target hart resources, and compared with a manual verification mode, the verification period is shortened and the accuracy of the verification of the resource rights is improved because the verification step of the resource rights is automatically executed by the server;
after receiving a deployment instruction of a first terminal, a server automatically updates configuration parameters of a target char resource and performs a pre-verification and pre-execution step on the target char resource according to a cluster identifier of a target cluster and a resource identifier of the target char resource in the deployment instruction;
further, under the condition that the pre-verification and the pre-execution are passed, the target hart resources are deployed into the target cluster so that the target cluster can realize corresponding hart service, and in the subsequent maintenance stage, after receiving an update instruction for the target hart resources, the server automatically carries out version update on the application program, and compared with the mode of manually deploying according to deployment documents, the method not only reduces maintenance cost input, but also improves deployment efficiency.
Fig. 8 is a block diagram of a mechanism for deploying char resources according to one embodiment of the present application.
A verification module 801, configured to perform resource permission verification on a target portion resource in response to receiving a verification instruction sent by a first terminal, where the target portion resource is a portion resource uploaded by the first terminal, and different portion resources are used to implement different portion services;
a setting module 802, configured to set the target char resource to a deployable state in response to the target char resource passing a resource permission check;
the deployment module 803 is configured to deploy the target hart resource to a target cluster in response to receiving a deployment instruction for the target hart resource, where the target cluster includes at least one second terminal to which the hart service is to be deployed.
Optionally, the verification module 801 includes:
the first acquisition unit is used for responding to the verification instruction of the target hart resource and acquiring an account identifier of the first terminal and a resource identifier of the target hart resource, wherein the account identifier of the first terminal and the resource identifier are contained in the verification instruction;
the second acquisition unit is used for acquiring the target hart resources from a hart warehouse based on the resource identification, wherein the hart warehouse contains all hart resources uploaded by the first terminal;
The third acquisition unit is used for acquiring verification information corresponding to the first terminal based on the account identifier;
and the verification unit is used for verifying the resource authority of the target char resource based on the verification information.
Optionally, the verification unit is configured to:
performing first resource attribute verification on the resource file in the target char resource based on the first resource attribute in the verification information, wherein the first resource attribute is a resource attribute supported by the cluster system;
and writing compliance verification is carried out on the resource file in the target char resource based on the resource file writing rule in the verification information.
Optionally, the verification unit is further configured to:
responding to the first resource attribute check and the writing compliance check, and performing second resource attribute check on a resource file in the target char resource based on a second resource attribute in the check information, wherein the second resource attribute is a resource attribute with deployment authority of the first terminal;
determining a residual storage space based on the total storage space and an occupied storage space in the verification information, wherein the total storage space is the maximum available space for the first terminal to deploy the chart resource, and the occupied storage space is the space occupied by the first terminal to deploy the chart resource;
And verifying the storage space in the target hart resource based on the residual storage space and the target occupied space of the target hart resource.
Optionally, the deployment module 803 includes:
a fourth obtaining unit, configured to obtain, in response to receiving the deployment instruction for the target char resource, a cluster identifier of the target cluster and a resource identifier of the target char resource, where the cluster identifier is included in the deployment instruction;
a fifth obtaining unit, configured to obtain the target hart resource from a hart warehouse based on the resource identifier;
the updating unit is used for updating the configuration parameters of the target char resources based on the cluster identification;
the pre-verification unit is used for pre-verifying the updated target char resource, and the pre-verification comprises database configuration verification, memory resource verification and connection state verification;
the pre-execution unit is used for responding to the pre-execution of the target char resource through the pre-verification;
and the deployment unit is used for deploying the target char resource to the target cluster in response to the pre-execution.
Optionally, the updating unit is configured to:
Based on the cluster identification, acquiring cluster configuration information of the target cluster from a configuration center;
updating the configuration parameters of the target char resources based on the cluster configuration information;
optionally, the row pre-verification is configured to:
based on the cluster identification, acquiring a pre-verification rule of the target cluster from the configuration center;
and carrying out the pre-verification on the updated target char resource based on the pre-verification rule.
Optionally, the apparatus further includes:
and the updating module is used for responding to the received updating instruction of the target hart resource, acquiring the version information of the target hart resource in the updating instruction and updating the target hart resource based on the version information.
Fig. 9 shows a schematic structural diagram of a server according to an exemplary embodiment of the present application. Specifically, the present invention relates to a method for manufacturing a semiconductor device. 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 an Input/Output (I/O) system 906 for transferring information between various devices within 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, keyboard, or the like, for user input of information. Wherein both the display 908 and the input device 909 are coupled to the central processing unit 901 via an input output controller 910 coupled 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, the input-output controller 910 also provides output to a display screen, a printer, or other type of output device.
The mass storage device 907 is connected to the central processing unit 901 through a mass storage controller (not shown) connected to the system bus 905. The mass storage device 907 and its associated computer-readable media provide non-volatile storage for the server 900. That is, the mass storage device 907 may include a computer-readable medium (not shown), such as a hard disk or drive.
Computer readable media may include computer storage media and communication media without loss of generality. 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 includes random access Memory (RAM, random Access Memory), read Only Memory (ROM), flash Memory or other solid state Memory technology, compact disk (CD-ROM), digital versatile disk (Digital Versatile Disc, DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will recognize that computer storage media are not limited to the ones described above. The system memory 904 and mass storage device 907 described above may be collectively referred to as memory.
The memory stores one or more programs configured to be executed by the one or more central processing units 901, the one or more programs containing instructions for implementing the methods described above, and the central processing unit 901 executing the one or more programs implements the method for deploying the char resources provided by the respective method embodiments described above.
According to various embodiments of the present application, server 900 may also operate by a remote computer connected to the network through a network, such as the Internet. I.e., the server 900 may be connected to the network 912 through a network interface unit 911 coupled to the system bus 905, or other types of networks or remote computer systems (not shown) may be coupled using the network interface unit 911.
The memory also includes one or more programs, one or more programs stored in the memory, the one or more programs including steps for performing the methods provided by the embodiments of the present application as performed by the server.
In addition, those skilled in the art will appreciate that the structure of the server shown in the above figures is not limiting of the server, and that the server may include more or fewer components than shown, or may combine certain components, or may be a different arrangement of components. For example, the server further includes components such as a radio frequency circuit, an input unit, a sensor, a server, a power supply, and the like, which are not described herein.
The application provides a computer readable storage medium, wherein 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 method for deploying the char resource provided by each method embodiment.
The present application also provides a 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 method for deploying the char resource of any of the above embodiments.
The foregoing embodiment numbers of the present application are merely for describing, and do not represent advantages or disadvantages of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program for instructing relevant hardware, where the program may be stored in a computer readable storage medium, and the storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
The foregoing is illustrative of the present invention and is not to be construed as limiting thereof, but rather as being included within the spirit and principles of the present invention.
Claims (8)
1. A method for deploying a char resource, the method being for a server in a cluster system, the method comprising:
responding to a verification instruction of a target hart resource, and acquiring an account identifier of a first terminal and a resource identifier of the target hart resource, which are contained in the verification instruction;
based on the resource identification, acquiring the target hart resource from a hart warehouse, wherein the hart warehouse contains all hart resources uploaded by the first terminal;
acquiring verification information corresponding to the first terminal based on the account identifier;
performing first resource attribute verification on the resource file in the target char resource based on the first resource attribute in the verification information, wherein the first resource attribute is a resource attribute supported by the cluster system;
writing compliance verification is carried out on the resource file in the target hart resource based on the resource file writing rule in the verification information, wherein the target hart resource is the hart resource uploaded by the first terminal, and different hart resources are used for realizing different hart services;
setting the target hart resource to a deployable state in response to the target hart resource passing a resource permission check;
And in response to receiving a deployment instruction for the target hart resource, deploying the target hart resource to a target cluster, wherein the target cluster comprises at least one second terminal for which the hart service is to be deployed.
2. The method of claim 1, wherein the verifying the resource rights for the target char resource based on the verification information comprises:
responding to the first resource attribute check and the writing compliance check, and performing second resource attribute check on a resource file in the target char resource based on a second resource attribute in the check information, wherein the second resource attribute is a resource attribute with deployment authority of the first terminal;
determining a residual storage space based on the total storage space and an occupied storage space in the verification information, wherein the total storage space is the maximum available space for the first terminal to deploy the chart resource, and the occupied storage space is the space occupied by the first terminal to deploy the chart resource;
and verifying the storage space in the target hart resource based on the residual storage space and the target occupied space of the target hart resource.
3. The method of claim 1 or 2, wherein the deploying the target hart resource to a target cluster in response to receiving a deploy instruction for the target hart resource comprises:
in response to receiving the deployment instruction for the target hart resource, acquiring a cluster identifier of the target cluster and a resource identifier of the target hart resource, which are contained in the deployment instruction;
acquiring the target hart resource from a hart warehouse based on the resource identifier;
updating the configuration parameters of the target char resources based on the cluster identification;
performing pre-verification on the updated target char resource, wherein the pre-verification comprises database configuration verification, memory resource verification and connection state verification;
performing pre-execution on the target char resource in response to passing the pre-verification;
deploying the target char resource to the target cluster in response to executing through the preamble;
wherein the pre-execution includes: and updating the database of the target char resource or updating the service configuration center.
4. The method of claim 3, wherein updating the configuration parameters of the target char resource based on the cluster identification comprises:
Based on the cluster identification, acquiring cluster configuration information of the target cluster from a configuration center;
updating the configuration parameters of the target char resources based on the cluster configuration information;
the pre-checking the updated target char resource includes:
based on the cluster identification, acquiring a pre-verification rule of the target cluster from the configuration center;
and carrying out the pre-verification on the updated target char resource based on the pre-verification rule.
5. The method of claim 1 or 2, wherein after the deploying the target char resource to a target cluster, the method further comprises:
and responding to receiving an update instruction of the target hart resource, acquiring version information of the target hart resource in the update instruction, and updating the target hart resource based on the version information.
6. A deployment apparatus for a char resource, the apparatus being for a server in a cluster system, the apparatus comprising:
the verification module is used for responding to a verification instruction of a target hart resource, and acquiring an account identifier of a first terminal and a resource identifier of the target hart resource, wherein the account identifier of the first terminal and the resource identifier are contained in the verification instruction; based on the resource identification, acquiring the target hart resource from a hart warehouse, wherein the hart warehouse contains all hart resources uploaded by the first terminal; acquiring verification information corresponding to the first terminal based on the account identifier; performing first resource attribute verification on the resource file in the target char resource based on the first resource attribute in the verification information, wherein the first resource attribute is a resource attribute supported by the cluster system; writing compliance verification is carried out on the resource file in the target hart resource based on the resource file writing rule in the verification information, wherein the target hart resource is the hart resource uploaded by the first terminal, and different hart resources are used for realizing different hart services;
The setting module is used for responding to the target hart resource to pass the resource authority verification and setting the target hart resource into a deployable state;
the deployment module is used for deploying the target hart resource to a target cluster in response to receiving a deployment instruction of the target hart resource, wherein the target cluster comprises at least one second terminal for which the hart service is to be deployed.
7. A server, wherein the server comprises a processor and a memory; the memory stores at least one instruction for execution by the processor to implement the method of deploying char resources of any of claims 1 to 5.
8. A computer readable storage medium storing at least one instruction for execution by a processor to implement the method of deploying char resources of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210049979.6A CN114500268B (en) | 2022-01-17 | 2022-01-17 | Method and device for deploying char resources, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210049979.6A CN114500268B (en) | 2022-01-17 | 2022-01-17 | Method and device for deploying char resources, server and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114500268A CN114500268A (en) | 2022-05-13 |
| CN114500268B true CN114500268B (en) | 2023-07-21 |
Family
ID=81511518
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210049979.6A Active CN114500268B (en) | 2022-01-17 | 2022-01-17 | Method and device for deploying char resources, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114500268B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111008023A (en) * | 2019-12-06 | 2020-04-14 | 无锡华云数据技术服务有限公司 | Instance deployment method and system |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108737416A (en) * | 2018-05-16 | 2018-11-02 | 北京握奇智能科技有限公司 | Trusted application management method and trusted application management server |
| US11074091B1 (en) * | 2018-09-27 | 2021-07-27 | Juniper Networks, Inc. | Deployment of microservices-based network controller |
| US11941021B2 (en) * | 2019-10-25 | 2024-03-26 | Accenture Global Solutions Limited | Automatic creation of blockchain network infrastructures |
| CN110753121A (en) * | 2019-10-25 | 2020-02-04 | 北京浪潮数据技术有限公司 | Mirror image warehouse deployment method, device, equipment and medium |
| CN110990025B (en) * | 2019-12-06 | 2024-02-06 | 无锡华云数据技术服务有限公司 | Instance deployment method and system |
| CN111142881B (en) * | 2019-12-27 | 2023-10-27 | 浪潮云信息技术股份公司 | Kubernetes-based system and kubernetes-based method for automatic deployment of orchestration charts |
| US11403401B2 (en) * | 2020-06-17 | 2022-08-02 | International Business Machines Corporation | Preventing unauthorized package deployment in clusters |
| CN112558987A (en) * | 2020-12-16 | 2021-03-26 | 中盈优创资讯科技有限公司 | Helm-based automatic deployment method and device |
-
2022
- 2022-01-17 CN CN202210049979.6A patent/CN114500268B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111008023A (en) * | 2019-12-06 | 2020-04-14 | 无锡华云数据技术服务有限公司 | Instance deployment method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114500268A (en) | 2022-05-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107370786B (en) | General information management system based on micro-service architecture | |
| JP7011737B2 (en) | Systems and methods for connector development and integrated channel deployment | |
| CN107967159B (en) | Method for configuring file application and server | |
| CN108287694B (en) | Application program construction method, system, computer device and storage medium | |
| CN108829409B (en) | Distributed system rapid deployment method and system | |
| US20180101371A1 (en) | Deployment manager | |
| CN107818112B (en) | Big data analysis operating system and task submitting method | |
| US20200348921A1 (en) | Microservice update system | |
| CN109656538A (en) | Generation method, device, system, equipment and the medium of application program | |
| CN107783816A (en) | The method and device that creation method and device, the big data cluster of virtual machine create | |
| CN109120678A (en) | The method and apparatus of service tray for distributed memory system | |
| CN111984269A (en) | Method for providing application construction service and application construction platform | |
| US10025630B2 (en) | Operating programs on a computer cluster | |
| CN111984270A (en) | Application deployment method and system | |
| US10146519B2 (en) | Generation and deployment of scripts for large scale processing framework services | |
| CN111176818B (en) | Distributed prediction method, device, system, electronic equipment and storage medium | |
| CN110673923A (en) | XWIKI system configuration method, system and computer equipment | |
| CN110704749A (en) | Recommendation engine customization system, recommendation method, recommendation system and electronic equipment | |
| CN113641591A (en) | Test case generation method and device and test method and device | |
| CN117693734A (en) | Front-end item processing method, device, equipment, management system and storage medium | |
| CN110727575B (en) | Information processing method, system, device and storage medium | |
| CN114546563A (en) | Multi-tenant page access control method and system | |
| CN111831567B (en) | Application test environment configuration method, device, system and medium | |
| CN114500268B (en) | Method and device for deploying char resources, server and storage medium | |
| US20130262845A1 (en) | Method and system for generating a standardized system build file |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |