CN114064083A - Method for deploying cloud native application through self-defined template in configuration center and application - Google Patents

Method for deploying cloud native application through self-defined template in configuration center and application Download PDF

Info

Publication number
CN114064083A
CN114064083A CN202111388702.8A CN202111388702A CN114064083A CN 114064083 A CN114064083 A CN 114064083A CN 202111388702 A CN202111388702 A CN 202111388702A CN 114064083 A CN114064083 A CN 114064083A
Authority
CN
China
Prior art keywords
file
configuration center
deploying
application
template
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.)
Pending
Application number
CN202111388702.8A
Other languages
Chinese (zh)
Inventor
徐冬
顾欣
杨波
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jiangsu Anchao Cloud Software Co Ltd
Original Assignee
Jiangsu Anchao Cloud Software Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Jiangsu Anchao Cloud Software Co Ltd filed Critical Jiangsu Anchao Cloud Software Co Ltd
Priority to CN202111388702.8A priority Critical patent/CN114064083A/en
Publication of CN114064083A publication Critical patent/CN114064083A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/48Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806Task transfer initiation or dispatching
    • G06F9/4843Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485Task life-cycle, e.g. stopping, restarting, resuming execution
    • G06F9/4856Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The invention discloses a method for deploying cloud native application by self-defining a template in a configuration center and application thereof, wherein the method comprises the following steps: deploying a self-defined software format definition file in a configuration center; the file format of the application file is analyzed through a software format definition file in the configuration center, and a template file is generated; and deploying the cloud native application according to the template file generated by the configuration center. The method can define the file through the custom software format and deploy the file in the configuration center to realize the deployment of different types of cloud native applications, and can analyze different application files according to the requirements of cloud resources so as to complete the deployment of the cloud native applications.

Description

Method for deploying cloud native application through self-defined template in configuration center and application
Technical Field
The invention relates to the field of cloud computing, in particular to a method for deploying cloud native application through a custom template in a configuration center and application.
Background
With the continuous development of the technology in the software industry and the continuous maturation of the cloud computing technology, the micro-service technology, the container clustering technology, the automatic deployment technology and the agile development concept are developed and fall to the ground gradually, and the containers and Kubernets become cornerstones of cloud native application. Among them, the cloud native application refers to a software application developed specifically to run in a cloud computing environment.
The configuration center is an declarative, continuous integration tool for kubernets, GitOps. GitOps is a fast, secure method for development or maintenance personnel to maintain and update complex applications running in the Kubernets or other declarative orchestration frameworks.
After the cloud-based era, the infrastructure, system architecture and operation and maintenance modes of products are greatly changed. Therefore, the GitOps expands the concept of the DevOps, absorbs ideas of collaboration, experiment, quick feedback, continuous improvement and the like in DevOps culture, and uses Git as a source of facts and a bridge for linkage, so as to simplify the deployment and management mode of infrastructure and application programs in the cloud native era and realize faster, more frequent and more stable delivery of products.
The information disclosed in this background section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.
Disclosure of Invention
The invention aims to provide a method and application for deploying cloud native application in a configuration center custom template, and solves the problem that the cloud native application cannot be deployed on the configuration center in a mode of using an application file provided by kubevela in some specific scenes.
To achieve the above object, embodiments of the present invention provide a method for deploying a cloud native application through a custom template in a configuration center.
In one or more embodiments of the invention, the method comprises: deploying a self-defined software format definition file in a configuration center; the file format of the application file is analyzed through a software format definition file in the configuration center, and a template file is generated; and deploying the cloud native application according to the template file generated by the configuration center.
In one or more embodiments of the present invention, the deploying a custom software format definition file in a configuration center includes: deploying the software format definition file to a plug-in, and registering the use mode of the plug-in the configuration center, thereby generating a configuration file of the configuration center; and deploying the plug-in a server of the configuration center.
In one or more embodiments of the present invention, defining a file format of a file parsing application file by a software format in the configuration center, and generating a template file includes: configuring an analysis file in a server of the configuration center, then calling the plug-in, and analyzing the file format of the application file through a software format definition file deployed in the plug-in; and generating a template file for deploying the application and the server according to the analysis result.
In one or more embodiments of the invention, the method further comprises: and after the configuration file of the configuration center is generated, updating the recovery service of the server of the configuration center.
In another aspect of the invention, an apparatus for deploying a cloud native application through a custom template in a configuration center is provided, which includes a custom module, a parsing module and a deployment module.
And the self-defining module is used for deploying a self-defining software format definition file in the configuration center.
And the analysis module is used for analyzing the file format of the application file through the software format definition file in the configuration center and generating a template file.
And the deployment module is used for deploying the cloud native application according to the template file generated by the configuration center.
In one or more embodiments of the present invention, the customization module is further configured to: deploying the software format definition file to a plug-in, and registering the use mode of the plug-in the configuration center, thereby generating a configuration file of the configuration center; and deploying the plug-in a server of the configuration center.
In one or more embodiments of the present invention, the parsing module is further configured to: configuring an analysis file in a server of the configuration center, then calling the plug-in, and analyzing the file format of the application file through a software format definition file deployed in the plug-in; and generating a template file for deploying the application and the server according to the analysis result.
In one or more embodiments of the present invention, the customization module is further configured to: and after the configuration file of the configuration center is generated, updating the recovery service of the server of the configuration center.
In another aspect of the present invention, there is provided an electronic device including: at least one processor; and a memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform the method for deploying cloud-native applications by customizing templates at a configuration center as described above.
In another aspect of the invention, a computer readable storage medium is provided, having stored thereon a computer program which, when executed by a processor, carries out the steps of deploying a cloud-native application method by customizing templates at a configuration center as described.
Compared with the prior art, according to the method and the application for deploying the cloud native application in the configuration center through the custom template, the files can be defined through the custom software format and deployed in the configuration center, deployment of different types of cloud native applications is achieved, different application files can be analyzed according to the requirements of cloud resources, and deployment of the cloud native application is achieved.
According to the method and the application for deploying the cloud native application in the configuration center custom template, the requirement of the application format of the application file which needs to be customized in the cloud native field can be met, various cloud native application formats can be supported at the same time, and a user can control the cloud native application format according to the required function. The method can be used in cloud native application migration or different kubernets versions, the problem of deployed version configuration is avoided, and the universality is higher.
According to the method and the application for deploying the cloud native application in the configuration center custom template, the required application format can be customized in the cloud native field. And a plurality of application formats are supported, and when a plurality of scenes are deployed on the configuration center, the application format of one application file is difficult to meet the current requirements of various cloud resources, so that a plurality of analysis modes can be conveniently provided by customizing the software format definition file. When the application is migrated, if a self-defined software format definition file is used, the migration and deployment can be flexibly performed among kubernets of different versions and clusters. The method only needs to modify and upgrade the plug-in, and solves the problem that the deployment configuration file depends on kubernets to a certain extent.
Drawings
FIG. 1 is a flow diagram of a method for deploying a cloud-native application through custom templates in a configuration center according to an embodiment of the invention;
FIG. 2 is a detailed flow diagram of a method for deploying a cloud-native application through custom templates in a configuration center according to an embodiment of the invention;
FIG. 3 is a timing diagram of a method for deploying a cloud-native application through custom templates in a configuration center according to an embodiment of the invention;
FIG. 4 is an architecture diagram of a method for deploying a cloud-native application through custom templates in a configuration center, according to an embodiment of the invention;
FIG. 5 is a block diagram of an apparatus for deploying cloud-native applications through custom templates in a configuration center according to an embodiment of the invention;
FIG. 6 is a hardware block diagram of a computing device deploying a cloud-native application through custom templates in a configuration center according to an embodiment of the invention.
Detailed Description
The following detailed description of the present invention is provided in conjunction with the accompanying drawings, but it should be understood that the scope of the present invention is not limited to the specific embodiments.
Throughout the specification and claims, unless explicitly stated otherwise, the word "comprise", or variations such as "comprises" or "comprising", will be understood to imply the inclusion of a stated element or component but not the exclusion of any other element or component.
The technical solutions provided by the embodiments of the present invention are described in detail below with reference to the accompanying drawings.
Example 1
Referring to fig. 1, a method for deploying a cloud native application by customizing a template in a configuration center according to an embodiment of the present invention is described, which includes the following steps.
Some concepts related to the embodiments of the present invention are described below.
GitOps is a fast, secure method for development or maintenance personnel to maintain and update complex applications running in the Kubernets or other declarative orchestration frameworks. When changes to infrastructure code are submitted using Git, the automated delivery pipeline will apply the changes to the actual infrastructure of the application. But the idea of GitOps is far from this, it also uses tools to compare the actual production state of the entire application with the infrastructure source code, and then it tells the cluster which infrastructure source code does not match the actual environment. Deployment and release automation is the basis for applications to implement GitOps and make the delivery pipeline work. Not only is the GitOps guaranteed that when a developer updates a configuration file set through the Git, the GitOps pipeline automatically updates the online environment according to the latest configuration file state, but the GitOps also needs to be capable of comparing the latest state of the configuration file set in the Git library with the latest state of the online environment in real time to keep consistent. The advantages of GitOps mainly include: (1) a secure cloud-native CI/CD pipeline model, (2) faster average deployment and recovery times, (3) stable and reproducible rollback (e.g., according to Git recovery/rollback/fork), (4) in conjunction with monitoring and visualization tools, full monitoring of already deployed applications.
The configuration center (Argo CD) is an asserted, continuous integration tool of GitOps to kubernets. Argo CD follows the GitOps schema, which uses the Git repository as the real source defining the required application state.
In step S101, a custom software format definition file is deployed in the configuration center.
In some specific scenarios, the deployment of cloud native applications cannot be satisfied by a specified application file, and a load balancer type or a server type needs to be added.
In this embodiment, the configuration center may be an Argo CD, since an Argo CD is implemented as a kubernets controller that continuously monitors running applications and compares the current active state with the desired target state (specified in the Git repository). Argo CD reports and visualizes discrepancies while providing the ability to automatically or manually synchronize real-time status back to a desired target status. Any modifications made to the desired target state in the Git store can be automatically applied and reflected in the specified target environment.
The software format definition file of the cloud native application to be deployed is customized and deployed to the configuration center before the cloud native application is deployed, and the deployment of the cloud native application in a specific scene can be met. Because the configuration center can automatically deploy the required application program state in the specified target environment, and the configuration center can directly realize the CRD of Kubernets, wherein the CRD is a Kubernets resource object and represents the deployed application program instance in the target environment. Compared with the conventional method, the method for deploying the user-defined software format definition file in the configuration center does not need to additionally increase external CRD resources and supports functions of file mounting and the like.
The software format definition file may be a schema, which is used to define the mapping of each field of the cloud-native application and the file format of the specific application file. When different applications are deployed in different scenes, the deployment of the cloud native applications can be realized only by compiling corresponding application files according to the software format definition file.
In step S102, the file format of the application file is parsed by the software format definition file in the configuration center, and a template file is generated.
The configuration center has strong GitOps capability, so that the file formats of various different cloud native applications can be analyzed through the customized software format definition file deployed in the configuration center, and corresponding template files are generated.
GitOps is a continuous delivery method, and the core idea of the GitOps is to store the declarative infrastructure of the application system and the application program in a Git version library. With Git as the core of the delivery pipeline, each developer can submit a Pull Request (Pull Request) and use Git to speed up and simplify kubernets' application deployment and operation and maintenance tasks.
The advantages of the configuration center's GitOps functionality mainly include: (1) a secure cloud-native CI/CD pipeline model; (2) faster average deployment time and average recovery time; (3) stable and reproducible rollback (e.g., resume/rollback/fork according to Git); (4) and the monitoring and visualization tool is combined to monitor the deployed application in an all-around way.
In the embodiment, the deployment speed of the cloud native application can be increased according to the advantages of the GitOps of the configuration center, and the deployed cloud native application can be monitored.
In step S103, the cloud native application is deployed according to the template file generated by the configuration center.
The template file is obtained by analyzing an application file according to a self-defined software format definition file registered on a server of the configuration center, and the template file is used for deploying cloud native applications in Kubernets.
According to the method and the application for deploying the cloud native application in the configuration center custom template, the required application format can be customized in the cloud native field. And a plurality of application formats are supported, and when a plurality of scenes are deployed on an Argo CD, the application format of one application file is difficult to meet the requirements of various current cloud resources, so that a plurality of analysis modes can be conveniently provided through a customized software format definition file (schema). When the application is migrated, if a self-defined software format definition file is used, the migration and deployment can be flexibly performed among kubernets of different versions and clusters. The method only needs to modify and upgrade the plug-in, and solves the problem that the deployment configuration file depends on kubernets to a certain extent.
Example 2
As shown in fig. 2 to 4, a method for deploying a cloud native application by customizing a template in a configuration center according to another embodiment of the present invention is introduced, which includes the following steps.
In step S201, a software format definition file is deployed to a plug-in.
The software format definition file is used for defining the mapping of each field of the cloud native application and the file format of the specific application file. When different applications are deployed in different scenes, the deployment of the cloud native applications can be realized only by compiling corresponding application files according to the software format definition file.
The software format definition file needs to be deployed on a plug-in to be further deployed to a configuration center. In this embodiment, the plug-in may be a kubegenerate plug-in, the software format definition file is written in the kubegenerate plug-in, and then the kubegenerate plug-in is registered in the configuration center, so that the configuration center can be used correctly.
Using Cloudusite as an example, the mapping of each field and the file format of a particular application file are defined in a software format definition file. Specifically, a specific configuration file type generated in the configuration center is written in the type, and the type of the configuration file is a type of the parsed cloud native application, which may be a default. The Map module defines the field configuration (mapping relationship) of each field mapped to the application file in the deployment, and shows that the specific field is mapped to the configuration type. The software format definition defines a specific file format of the application file for verification of the application service. Other fields in the application file do not specify default configuration for use by default.
In step S202, the usage of the plug-ins is registered in the configuration center, and a configuration file of the configuration center is generated.
The server of the configuration center needs to configure necessary configuration files for service, and the configuration files of the configuration center register the relevant use mode of the kubemenerate plugin containing the software format definition file into the configuration center when the cloud native application is deployed, so that the configuration files of the configuration center are generated and used for the configuration center to analyze the application files when the cloud native application is deployed.
In step S203, the recycle service of the configuration center server is updated.
In this embodiment, the recycle service of the configuration center server may be Argo CD-replay-server, and the recycle service of the configuration center server calls the kubeegenerate plug-in to parse the application file according to the provided command, and then deploys the application in kubeenetes according to the deployment application obtained by parsing and the template file of the server. Argo CD-repo-server may maintain a local cache of the Git repository holding application manifests and is responsible for generating and returning Kubernets manifests.
After the configuration center generates the configuration file, the pod plugin is updated, which is a mechanism inside the configuration center, in other words, after the kubegenerate plugin is deployed by the configuration center server, the configuration center server updates itself.
In step S204, an analysis file is configured in the server of the configuration center, and a plug-in is called, and the file format of the application file is analyzed by the software format definition file deployed in the plug-in.
After the server of the configuration center completes updating, the parsing file (default. yaml file) needs to be changed in order to enable the server of the configuration center to correctly use the kubemenate plug-in registered in the configuration center to parse the software format definition file.
The configuration center can monitor whether the code base is changed, when a yaml file of a declaration pod or other types of resources is changed, the configuration center can use the changed yaml file to compare with a yaml file stored in the kubernets service, and if the yaml file is different, the configuration center can run the yaml file after the kubecect deployment is changed.
In this embodiment, when different cloud-native applications are deployed, the configuration center may change the yaml file for multiple times in order to analyze different application files, and the configuration center may change the yaml file by itself each time the applications are deployed, so that the server of the configuration center can correctly call the kubegenerate plug-in to analyze the file format of the application file.
In step S205, a template file for deploying the application and the server is generated according to the parsing result.
When the cloud native application is deployed, the deployment method generally needs to jointly use the deployment agent and the service, and at the moment, the file is defined by adopting a custom software format, so that the problem can be conveniently solved, and only the application file needs to be written. The configuration center can analyze the corresponding application file according to the software format definition file so as to generate a template file for deploying the application and the server (deployment & service), and deploy the cloud native application according to the template file.
In step S206, the cloud native application is deployed according to the template file generated by the configuration center.
The template file is obtained by analyzing an application file according to a self-defined software format definition file registered on a server of the configuration center, and the template file is used for deploying cloud native applications in Kubernets.
Taking deployment of the ARMP application as an example, writing a software format definition file in a kubemenate plug-in, and customizing the mapping of each field of the ARMP application and the file format of a specific application file; and deploying the written kubegenerate plug-in to a configuration center. The user writes an application file corresponding to the ARMP application according to a software format definition file in the kubeegenerate plug-in, the configuration center compares the application file corresponding to the ARMP application with the software format definition file, if the comparison is passed, a template file of the corresponding default & service is generated, so that the analysis is completed, and the analyzed ARMP application is deployed on the cloud resource.
When the application is migrated, only the kubemenate plug-in with the corresponding software format definition file needs to be modified and upgraded, the upgraded kubemenate plug-in is deployed in a configuration center, and the application file of the migrated application is analyzed and deployed, so that the application migration is completed.
According to the method and the application for deploying the cloud native application in the configuration center custom template, the requirement of the application format of the application file needing to be customized in the cloud native field can be met, various cloud native application formats can be supported at the same time, and a user can control the cloud native application format according to the required function. The method can be used in cloud native application migration or different kubernets versions, the problem of deployed version configuration is avoided, and the universality is higher.
Referring to fig. 5, an apparatus for deploying a cloud-native application by customizing a template in a configuration center according to an embodiment of the present invention is described.
In the embodiment of the invention, the device for deploying the cloud native application by customizing the template in the configuration center comprises a customization module 501, a parsing module 502 and a deployment module 503.
The self-defining module 501 is used for deploying a self-defining software format definition file in the configuration center.
The parsing module 502 is configured to parse the file format of the application file through the software format definition file in the configuration center, and generate a template file.
The deployment module 503 is configured to deploy the cloud native application according to the template file generated by the configuration center.
The custom module 501 is further configured to: deploying a software format definition file to the plug-ins, and registering the use modes of the plug-ins in a configuration center so as to generate a configuration file of the configuration center; and deploying the plug-in a server of the configuration center.
The parsing module 502 is further configured to: configuring an analysis file in a server of a configuration center, calling a plug-in, and defining a file format of an application file by a software format deployed in the plug-in; and generating a template file for deploying the application and the server according to the analysis result.
The custom module 501 is further configured to: and after the configuration file of the configuration center is generated, updating the recovery service of the server of the configuration center.
Fig. 6 illustrates a hardware architecture diagram of a computing device 60 for deploying cloud-native applications through custom templates in a configuration center according to an embodiment of the present description. As shown in fig. 6, computing device 60 may include at least one processor 601, storage 602 (e.g., non-volatile storage), memory 603, and a communication interface 604, and the at least one processor 601, storage 602, memory 603, and communication interface 604 are connected together via a bus 605. The at least one processor 601 executes at least one computer readable instruction stored or encoded in the memory 602.
It should be appreciated that the computer-executable instructions stored in the memory 602, when executed, cause the at least one processor 601 to perform the various operations and functions described above in connection with fig. 1-6 in the various embodiments of the present description.
In embodiments of the present description, computing device 60 may include, but is not limited to: personal computers, server computers, workstations, desktop computers, laptop computers, notebook computers, mobile computing devices, smart phones, tablet computers, cellular phones, Personal Digital Assistants (PDAs), handheld devices, messaging devices, wearable computing devices, consumer electronics, and so forth.
According to one embodiment, a program product, such as a machine-readable medium, is provided. A machine-readable medium may have instructions (i.e., elements described above as being implemented in software) that, when executed by a machine, cause the machine to perform various operations and functions described above in connection with fig. 1-6 in the various embodiments of the present specification. Specifically, a system or apparatus may be provided which is provided with a readable storage medium on which software program code implementing the functions of any of the above embodiments is stored, and causes a computer or processor of the system or apparatus to read out and execute instructions stored in the readable storage medium.
According to the method and the application for deploying the cloud native application in the configuration center through the custom template, the file can be defined through the custom software format and deployed in the configuration center, deployment of different types of cloud native applications is achieved, different application files can be analyzed according to the requirements of cloud resources, and deployment of the cloud native application is achieved.
According to the method and the application for deploying the cloud native application in the configuration center custom template, the requirement of the application format of the application file which needs to be customized in the cloud native field can be met, various cloud native application formats can be supported at the same time, and a user can control the cloud native application format according to the required function. The method can be used in cloud native application migration or different kubernets versions, the problem of deployed version configuration is avoided, and the universality is higher.
According to the method and the application for deploying the cloud native application in the configuration center custom template, the required application format can be customized in the cloud native field. And a plurality of application formats are supported, and when a plurality of scenes are deployed on an Argo CD, the application format of one application file is difficult to meet the requirements of various current cloud resources, so that a plurality of analysis modes can be conveniently provided through a customized software format definition file (schema). When the application is migrated, if a self-defined software format definition file is used, the migration and deployment can be flexibly performed among kubernets of different versions and clusters. The method only needs to modify and upgrade the plug-in, and solves the problem that the deployment configuration file depends on kubernets to a certain extent.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing descriptions of specific exemplary embodiments of the present invention have been presented for purposes of illustration and description. It is not intended to limit the invention to the precise form disclosed, and obviously many modifications and variations are possible in light of the above teaching. The exemplary embodiments were chosen and described in order to explain certain principles of the invention and its practical application to enable one skilled in the art to make and use various exemplary embodiments of the invention and various alternatives and modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims and their equivalents.

Claims (10)

1. A method for deploying a cloud native application through a custom template in a configuration center, the method comprising:
deploying a self-defined software format definition file in a configuration center;
the file format of the application file is analyzed through a software format definition file in the configuration center, and a template file is generated; and
and deploying the cloud native application according to the template file generated by the configuration center.
2. The method for deploying the cloud-native application through the custom template in the configuration center according to claim 1, wherein deploying the custom software format definition file in the configuration center comprises:
deploying the software format definition file to a plug-in, and registering the use mode of the plug-in the configuration center, thereby generating a configuration file of the configuration center; and
deploying the plug-in a server of the configuration center.
3. The method of deploying cloud-native applications by customizing templates in a configuration center according to claim 1, wherein parsing a file format of an application file through a software format definition file in the configuration center and generating a template file comprises:
configuring an analysis file in a server of the configuration center, calling the plug-in, and analyzing the file format of the application file through a software format definition file deployed in the plug-in; and
and generating a template file for deploying the application and the server according to the analysis result.
4. The method of deploying a cloud-native application by customizing a template in a configuration center according to claim 2, further comprising:
and after the configuration file of the configuration center is generated, updating the recovery service of the configuration center server.
5. An apparatus for deploying a cloud-native application by customizing a template in a configuration center, the apparatus comprising:
the self-defining module is used for deploying a self-defining software format definition file in the configuration center;
the analysis module is used for analyzing the file format of the application file through a software format definition file in the configuration center and generating a template file; and
and the deployment module is used for deploying the cloud native application according to the template file generated by the configuration center.
6. The apparatus for deploying a cloud-native application by customizing a template in a configuration center of claim 5, wherein the customization module is further configured to:
deploying the software format definition file to a plug-in, and registering the use mode of the plug-in the configuration center, thereby generating a configuration file of the configuration center; and
deploying the plug-in a server of the configuration center.
7. The apparatus for deploying a cloud-native application by customizing a template in a configuration center according to claim 5, wherein the parsing module is further configured to:
configuring an analysis file in a server of the configuration center, then calling the plug-in, and analyzing the file format of the application file through a software format definition file deployed in the plug-in; and
and generating a template file for deploying the application and the server according to the analysis result.
8. The apparatus for deploying a cloud-native application by customizing a template in a configuration center of claim 6, wherein the customization module is further configured to:
and after the configuration file of the configuration center is generated, updating the recovery service of the configuration center server.
9. An electronic device, comprising:
at least one processor; and
a memory storing instructions that, when executed by the at least one processor, cause the at least one processor to perform the method of deploying cloud-native applications by customizing templates in a configuration center according to any of claims 1 to 4.
10. A computer-readable storage medium, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, carries out the steps of the method of deploying a cloud-native application by customizing a template in a configuration center according to any one of claims 1 to 4.
CN202111388702.8A 2021-11-22 2021-11-22 Method for deploying cloud native application through self-defined template in configuration center and application Pending CN114064083A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111388702.8A CN114064083A (en) 2021-11-22 2021-11-22 Method for deploying cloud native application through self-defined template in configuration center and application

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111388702.8A CN114064083A (en) 2021-11-22 2021-11-22 Method for deploying cloud native application through self-defined template in configuration center and application

Publications (1)

Publication Number Publication Date
CN114064083A true CN114064083A (en) 2022-02-18

Family

ID=80278962

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111388702.8A Pending CN114064083A (en) 2021-11-22 2021-11-22 Method for deploying cloud native application through self-defined template in configuration center and application

Country Status (1)

Country Link
CN (1) CN114064083A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115396304A (en) * 2022-09-15 2022-11-25 科讯嘉联信息技术有限公司 System and method for automatically deploying cloud native application based on deployment planning table
CN116107560A (en) * 2023-04-12 2023-05-12 昆仑数智科技有限责任公司 Pipeline arrangement method, device and system based on DevOps

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180373551A1 (en) * 2017-03-21 2018-12-27 Aaron Christensen Systems and methods for using dynamic templates to create application containers
CN111897622A (en) * 2020-06-10 2020-11-06 中国科学院计算机网络信息中心 High-throughput computing method and system based on container technology
CN113596110A (en) * 2021-07-08 2021-11-02 交通银行股份有限公司太平洋信用卡中心 Heterogeneous cloud-oriented cloud native micro-service platform

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180373551A1 (en) * 2017-03-21 2018-12-27 Aaron Christensen Systems and methods for using dynamic templates to create application containers
CN111897622A (en) * 2020-06-10 2020-11-06 中国科学院计算机网络信息中心 High-throughput computing method and system based on container technology
CN113596110A (en) * 2021-07-08 2021-11-02 交通银行股份有限公司太平洋信用卡中心 Heterogeneous cloud-oriented cloud native micro-service platform

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
阿里云云栖号: ""KubeVela:标准化的云原生平台构建引擎"", 《HTTPS://BAIJIAHAO.BAIDU.COM/S?ID=1690894848443091226》 *
阿里云开发者: ""ArgoCD + KubeVela:以开发者为中心的 GitOps"", 《HTTPS://BLOG.CSDN.NET/ALITECH2017/ARTICLE/DETAILS/113643974》 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115396304A (en) * 2022-09-15 2022-11-25 科讯嘉联信息技术有限公司 System and method for automatically deploying cloud native application based on deployment planning table
CN115396304B (en) * 2022-09-15 2023-08-08 科讯嘉联信息技术有限公司 System and method for automatically deploying cloud native application based on deployment planning table
CN116107560A (en) * 2023-04-12 2023-05-12 昆仑数智科技有限责任公司 Pipeline arrangement method, device and system based on DevOps

Similar Documents

Publication Publication Date Title
US10241778B2 (en) Microservices version state visualization
CN110928529B (en) Method and system for assisting operator development
US20180113799A1 (en) Model generation for model-based application testing
US9032373B1 (en) End to end testing automation and parallel test execution
US10146599B2 (en) System and method for a generic actor system container application
EP2972821B1 (en) Application compatibility checking in a distributed computing environment
US11327726B2 (en) Workflow engine tool
CN110673853B (en) Compiling method, device and system
US10936309B2 (en) Development project blueprint and package generation
EP3030969A1 (en) Automated application test system
US10140355B2 (en) Compiling extract, transform, and load job test data cases
CN114064083A (en) Method for deploying cloud native application through self-defined template in configuration center and application
US10372112B2 (en) System and method for legacy level 1 controller virtualization
WO2024002243A1 (en) Application management method, application subscription method, and related device
CN111158743B (en) Big data operation and maintenance management platform
CN115454869A (en) Interface automation test method, device, equipment and storage medium
US10572247B2 (en) Prototype management system
CN111651219A (en) Method and equipment for managing multi-module project configuration file
WO2023087764A1 (en) Algorithm application element packaging method and apparatus, device, storage medium, and computer program product
US20130117749A1 (en) Provisioning and Managing an Application Platform
CN110806891A (en) Method and device for generating software version of embedded equipment
CN110908644A (en) Configuration method and device of state node, computer equipment and storage medium
CN110275731B (en) Information processing method, information processing apparatus, storage medium, and electronic device
CN110069417B (en) A/B test method and device
CN114115821A (en) Application development method and platform, application deployment method and node, system and equipment

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
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20220218