CN117806662A

CN117806662A - Application deployment method, device, equipment and medium

Info

Publication number: CN117806662A
Application number: CN202311754114.0A
Authority: CN
Inventors: 胡瑜渊; 王亮; 李宝军; 周明伟; 台德莉
Original assignee: Zhejiang Dahua Technology Co Ltd
Current assignee: Zhejiang Dahua Technology Co Ltd
Priority date: 2023-12-19
Filing date: 2023-12-19
Publication date: 2024-04-02

Abstract

The application discloses an application deployment method, an application deployment device, application deployment equipment and an application deployment medium, which are used for decoupling an association relation between application development and application use, and avoiding the influence of an application development environment on an application use process, so that user experience is improved. The application deployment method provided by the application deployment method comprises the following steps: when an application needs to be published, basic information of the application to be published is determined, and based on the basic information of the application to be published, when no container corresponding to the basic information of the application to be published is determined, a configuration file of the application to be published is rendered; creating a container of the application to be distributed in a container cloud based on the configuration file of the application to be distributed; and determining the definition data information of the application to be distributed, and loading the definition data information of the application to be distributed into a container of the application to be distributed.

Description

Application deployment method, device, equipment and medium

Technical Field

The present application relates to the field of low-code applications, and in particular, to an application deployment method, device, apparatus, and medium.

Background

The Low Code is a visual application program development mode of zero codes or a small number of codes, and the Low Code platform is a digital technology tool platform utilizing the Low Code development mode, and the Low Code application is quickly constructed based on visual and efficient modes such as image drag and parameter configuration, so that the limitations of long development period, high technical threshold and the like of the traditional application software are overcome.

Disclosure of Invention

The embodiment of the application provides an application deployment method, device, equipment and medium, which are used for decoupling the association relation between application development and use, and avoiding the influence of an application development environment on the application use process, so that the user experience is improved.

The application deployment method provided by the embodiment of the application comprises the following steps:

when an application needs to be published, basic information of the application to be published is determined, and based on the basic information of the application to be published, when no container corresponding to the basic information of the application to be published is determined, a configuration file of the application to be published is rendered;

creating a container of the application to be distributed in a container cloud based on the configuration file of the application to be distributed;

and determining the definition data information of the application to be distributed, and loading the definition data information of the application to be distributed into a container of the application to be distributed.

According to the method provided by the embodiment of the application, when the application needs to be published, the basic information of the application to be published is determined, and based on the basic information of the application to be published, when the fact that the container corresponding to the basic information of the application to be published does not exist is determined, the configuration file of the application to be published is rendered; then creating a container of the application to be distributed in a container cloud based on the configuration file of the application to be distributed; and determining the definition data information of the application to be distributed, and loading the definition data information of the application to be distributed into a container of the application to be distributed. Therefore, when a user uses the application, the application can be directly realized based on the independent container in the container cloud, and is irrelevant to the application development process, namely, the development of other applications involves other containers, so that the beneficial effects of decoupling the association relationship between the application development and the application are achieved, the influence of the application development environment on the application use process is avoided, and the user experience is improved.

In some embodiments, the method further comprises:

and when determining that the container corresponding to the basic information of the application to be distributed exists, determining definition data information of the application to be distributed, and loading the definition data information of the application to be distributed into the container of the application to be distributed.

In some embodiments, the method further comprises:

when the application to be distributed needs to be previewed, determining a working directory space corresponding to the application to be distributed based on basic information of the application to be distributed; the working catalog space comprises definition data information of the application to be distributed, and different applications correspond to different working catalog spaces;

and acquiring the definition data information of the application to be distributed from the working directory space, loading the definition data information of the application to be distributed by using an application rendering engine, and responding to the preview operation of the application to be distributed.

In some embodiments, the method further comprises:

when the release of the released application is required to be canceled, determining a configuration resource corresponding to the application to be canceled according to the identification of the application to be canceled;

deleting the configuration resources corresponding to the application to be unpublished; when the undeleted successful resource exists, recording the undeleted successful resource information; and releasing the resources corresponding to the undeleted successful resource information by using a preset timing task.

In some embodiments, the method further comprises:

aiming at the successfully published application, a Helm package and a mirror image are led out, and an application product package is generated; the Helm package is exported by packing the configuration file of the successfully published application according to the Helm package definition specification.

In some embodiments, the method further comprises:

when an application to be imported exists, basic information is created for the application to be imported;

acquiring a product package of the application to be imported, wherein the product package comprises a Helm package and a mirror image, and acquiring a configuration file of the application to be imported from the Helm package when the Helm package is successfully acquired by decompressing the product package and accords with a Helm package definition specification;

creating a container of the application to be imported in a container cloud based on the configuration file of the application to be imported;

and determining the definition data information of the application to be imported, and loading the definition data information of the application to be imported into a container of the application to be imported.

In some embodiments, the method further comprises:

and receiving an application access request of a user through an external gateway of the container cloud, and providing service for the application access request.

An application deployment device provided in an embodiment of the present application includes:

a first unit, configured to determine basic information of an application to be published when the application needs to be published, and render a configuration file of the application to be published when it is determined that there is no container corresponding to the basic information of the application to be published based on the basic information of the application to be published;

a second unit, configured to create a container of the application to be distributed in a container cloud based on the configuration file of the application to be distributed;

and the third unit is used for determining the definition data information of the application to be distributed and loading the definition data information of the application to be distributed into the container of the application to be distributed.

Another embodiment of the present application provides an electronic device, including a memory, where the memory is configured to store program instructions, and a processor configured to invoke the program instructions stored in the memory, and execute any of the methods according to the obtained program.

Another embodiment of the present application provides a computer-readable storage medium storing computer-executable instructions for causing a computer to perform any of the methods described above.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of an application deployment system architecture provided in an embodiment of the present application;

fig. 2 is a specific flowchart of a method for publishing an application in application deployment according to an embodiment of the present application;

fig. 3 is a specific flowchart of a method for canceling application release in application deployment according to an embodiment of the present application;

fig. 4 is a flow chart of an application importing method in application deployment according to an embodiment of the present application;

fig. 5 is a general flow diagram of an application deployment method according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of an application deployment device according to an embodiment of the present application.

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

The method, the device, the apparatus, the medium and the medium are based on the same application conception, and because the method, the device, the apparatus and the medium have similar principles for solving the problems, the implementation of the device, the apparatus, the medium and the method can be referred to each other, and the repetition is omitted.

The terms first, second and the like in the description and in the claims of the embodiments and in the above-described figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The following examples and embodiments are to be construed as illustrative only. Although the specification may refer to "an", "one", or "some" example or embodiment(s) at several points, this does not mean that each such reference is related to the same example or embodiment, nor that the feature is applicable to only a single example or embodiment. Individual features of different embodiments may also be combined to provide further embodiments. Furthermore, terms such as "comprising" and "including" should be understood not to limit the described embodiments to consist of only those features already mentioned; such examples and embodiments may also include features, structures, units, modules, etc. that are not specifically mentioned.

Various embodiments of the present application are described in detail below with reference to the drawings attached hereto. It should be noted that, the display sequence of the embodiments of the present application only represents the sequence of the embodiments, and does not represent the advantages or disadvantages of the technical solutions provided by the embodiments.

The low-code platform has core problems of resource isolation, access control, deployment operation and maintenance and the like among different applications, among different users and among different developers to be solved specifically.

The embodiment of the application relates to the following technical terms:

component (component): basic elements constituting a User Interface (UI) can be divided into four major categories according to functional complexity, such as basic components including input boxes, text boxes, buttons, dialog boxes, etc., and the components include attributes, style configurations, event triggers, response configurations, etc.

Data source (data-source): the source of page dynamic data is a channel for applications to exchange data with other services, which contains a set of related methods, each of which exchanges data with other services in a certain protocol.

Editor (editor): the application specifically displays the visual operation and configuration page of the content, and the user can drag the operations of the component, the configuration component, the application page configuration, the application preview, the application release, the application cancel release and the like on the visual operation and the configuration page.

Application (application): for an average user, applications in the low code platform have the general meaning of an application program. For a platform developer, the platform developer refers to an entity after the application is released after the development is completed; the application, i.e. the definition data of the application, which can be processed by the editor, is generally referred to as schema.

Preview (preview): application preview, aiming at the application in development or after development, the final display form is checked immediately, so that a developer can correct the unreasonable display or configuration of the application immediately and correctly.

Publication (published): and finally, the step of application release and application development completion represents that the application development is completed, the online is formally deployed, the user is oriented to provide the functional service of the application, the application can be released for a plurality of times, and the application in the service can be updated to the current configuration form after each release.

Unpublished (unpublished): the application is released in a cancel mode, namely the application stops being online, the application in deployment is canceled, and a user cannot access the service provided by the application later.

The overall system structure provided in the embodiment of the present application is shown in fig. 1, for example. The whole low-code platform shown in fig. 1, including applications created by the low-code platform, are all deployed based on the same container cloud base, and the low-code platform is split into front-end (web), interior gateway (gateway), application preview (run), low-code platform service (platform), application release (devops) and other service modules according to functions, and a public middleware service module, wherein each module is an independent service instance (POD), accords with a micro-service oriented principle of a cloud native architecture, and can perform operations such as load balancing, elastic expansion and rolling upgrade through K8 s. The service instance is the most core resource object of a container cloud (Kubernetes, abbreviated as K8 s), and is the smallest scheduling unit. The POD is the most basic element of the whole Kubernetes platform, the purpose of application deployment is to run an application program, and the running of each POD is a service instance which needs to be provided for an external user to use. Further, the POD is a logical container of a set of container instances and is the smallest unit of Kubernetes to schedule, so after an application is deployed into the POD on the Kubernetes platform (i.e., an open source low code platform for managing containers), kubernetes can manage a set of container instances as a whole through this logical object of the POD.

Specifically:

the front end (web) comprises application components and a page rendering engine (also called the application rendering engine, which can be realized based on Vue. Js, angular. Js and real. Js technical frameworks) and an application editor, and corresponding application page UI, event response trigger among the components and the like are rendered and configured according to the schema information of the specific application;

the internal gateway is mainly used for filtering interception, routing skip, access control and the like of the low-code platform;

the low-code platform service is a main service module of the low-code platform and is responsible for service functions such as user management, authority management, application management, data source management and the like;

the application preview module can be used for a developer to instantly check the specific effect of application construction, and an application rendering engine is also contained in the application preview module, and the principle is that an independent working directory space (mainly storing the schema information of the application and the calling information of a data source method) of the application is created based on different application identifications of different applications, and then the application rendering engine loads configuration information and pulls up an independent working process for responding to the preview page operation of the developer. If the developer exits the preview page or does not operate the preview page for a long time, the work process can be reclaimed, and resources are released. Because only the working catalog space, the scheme information issuing of the application and the engine rendering operation are opened, the application preview can immediately respond to the preview request of the developer, and the developer is facilitated to quickly construct the application;

The application publishing module is a core module of low-code platform related application deployment, is responsible for core functions of application publishing, canceling publishing, exporting, importing, state detecting and the like, and is a service module directly facing to interaction of a bottom container cloud interface.

The middleware is an important component of the system, and authentication, service discovery, data storage and message notification of the low-code platform are realized based on the middleware, wherein the middleware specifically comprises:

database (mysql): is responsible for the persistent storage of schema data and the like;

configuration center (Apollo): the distributed service configuration center is used for configuring specific configuration information of each service in the same management mode;

registry (Nacos): providing functions of service registration, service discovery and the like, wherein each service needs to be registered, and then can call each other service interface;

message center (Kafka): message middleware, which is responsible for the message transmission center between services;

timing database (Influxdb): for storing log data relating to operations of the developer and the user;

and (3) a unified authentication center: is responsible for authentication, interception and other functions.

That is, the embodiment of the application proposes a low-code application deployment scheme based on Yun Yuansheng architecture, and a developer pulls components or templates into an application page editor by using components and templates built in a low-code platform, configures properties and styles of the components, and further builds and configures applications quickly.

After the application is developed, a developer can directly click an application release button, an application release service of the platform immediately calls a container cloud interface according to definition data information of the application and basic information of the application, a corresponding service instance (POD) is created, the service instance is registered on an external service gateway (Ingress) of the container cloud, an access address of the application is returned, an ordinary user can directly access the application service through the address, and the developer can also continue developing and releasing the application.

As shown in fig. 1, from the developer's perspective:

the developer accesses the front end (web) of the low-code platform through the external gateway, performs drag operation on the components in the front end service, completes the construction and configuration of the application, and forwards the operations to persistent storage in the platform service module (platform) through the internal gateway (gateway) route in a network request mode.

After the application is built, a developer can execute preview operation through an application preview module to check the specific effect of the application. Specifically, the internal gateway forwards a preview request from a developer to an application preview module (specifically loaded onto a runtime service), the application preview module finds a platform service module through a registry (nacos), queries schema information of a specific application, and responds to the service request after loading the schema information of the application.

After the application preview is passed, the developer needs to provide the application to the user to use the application, and then the publishing process is executed, and similarly, the interior gateway forwards the publishing request from the developer to the application publishing service (devops) module, the devops finds the platform service module through the registry (nacos), queries the schema information of the specific application, calls the container cloud service interface according to the schema information of the application and the configuration file of the application, and creates the specific application, for example, application 0 to application 3 are created.

In addition, the developer can also import and export application product packages (including Helm packages and images) through the container cloud low-code platform, wherein the Helm packages can be understood as installation description files of the application, and the images are application specific program files.

From the user's perspective: after the developer successfully publishes the application, the user can directly access the specific application service through the external gateway agent.

The following is an example of a specific flow of application deployment related to the application publishing service module.

1. The specific process of application release comprises the following steps:

referring to fig. 2, the process of application publishing, i.e., application deployment, includes three phases, resource preparation, container creation, and container loading. Specifically:

S201, a developer issues an application through a front-end browser;

s202, a platform service module inquires basic information of the application and provides the basic information to an application release service module;

s203, an application release service module judges whether a container corresponding to the application exists, if so, the step S204 is executed, otherwise, the step S205 is executed;

that is, in the embodiment of the present application, for new application release, a corresponding container needs to be created in the container cloud separately, so that when a user uses an application, the application can be directly implemented based on an independent container in the container cloud, and is irrelevant to an application development process (other containers are involved in development of other applications), thereby achieving the beneficial effect of decoupling the association relationship between application development and use.

S204, an application release service module inquires a container corresponding to the application;

s205, an application release service module renders a configuration file of the application.

For example, the application release service module renders a configuration file required by the application on the bottom layer of the container cloud based on a preset and standard resource template file and combined with basic information of the application;

the resource template file is a mode of K8s for describing resource configuration, for example, the resource template file can be in a yaml file format, such as ingress.

The basic information of the application includes, for example: name, identification, description, icon, page information;

the configuration file of the application defines specific information such as the instance configuration of the SateFulSet, the Service configuration, the Volume persistence Volume configuration, the external gateway (Ingress) configuration and the like of the application. Wherein StatefulSet runs a set of Pod and maintains a stable identity for each Pod. The SateFulSet instance configuration includes a configuration for each Pod container in the SateFulSet.

S206, an application release service module creates a container of the application;

specifically, the application publishing service module calls the K8s interface, and creates SatefulSet, service, volume and external gateway (Ingress) resources in sequence according to the configuration file of the application.

After K8s completes the creation of all SatefulSet, service, volume and external gateway (Ingress) resources, the creation of the application container and the starting of the application rendering engine are completed. The bottom core of the container cloud is a management scheduling low-code platform of Kubernetes, a tool low-code platform for creating and deleting applications, and an application rendering engine is used for understanding that after the application Pod container is created, a service is operated in the container, and the service is responsible for responding and rendering the operation behaviors of users on the applications.

S207, an application release service module inquires and acquires scheme information of an application through a platform service module;

and S208, the application release service module loads the scheme information of the application into the due container in the container cloud Kubernetes.

S209, the front-end application rendering engine loads the schema information of the application based on the container of the application, and the application can provide services to the outside.

In addition, the developer can issue the schema information of the application again to the container of the application through the application issue service module, the application rendering engine reloads the schema information, and the user can use the latest application service.

2. The specific process of canceling release is as follows:

referring to fig. 3, unpublishing is a process of application destruction, i.e., an inverse process of creating a container at K8s, specifically including:

s301, an application release Service (release) module queries an identifier of an application to be released (for example, application 1 in FIG. 1), thereby determining a StatefulSet resource, a Service resource, a Volumn resource, an information resource and the like configured for the application to be released.

S302, an application release service module deletes StatefulSet resources to which an application to be released is to be canceled by calling a container cloud interface;

S303, the application release Service module deletes Service resources to which the application to be released is to be canceled by calling the container cloud interface;

s304, the application release service module deletes the Volumn resource to which the application to be released is to be canceled by calling the container cloud interface;

s305, the application release service module deletes the Ingress resource to which the application to be released is to be canceled by calling the container cloud interface;

s306, after the operation of deleting all the resources occupied by the application is executed, the resource information is put in a warehouse for the resources which are failed to be deleted, and a timed task scan list retry is performed later so as to ensure that the resources associated with the application can be completely released.

3. The specific flow of application export:

application export, i.e., exporting of published applications, generates an application product package that includes a Helm package and an image. Wherein Helm is a package administration tool for Kubernetes applications. The mirror image may be understood as a file, and the container is a process. The container is created based on the image, i.e., the process in the container relies on files in the image (the image is the system file of the container) including executable files, dependent software, library files, configuration files, etc. required for the process to run.

The method comprises the steps of receiving a first data packet, receiving a second data packet, wherein the first data packet is a compressed packet which is formed by exporting a published application into a format of tgz and the like, and the first data packet is a compressed packet which is formed by exporting a YAML configuration file rendered during application deployment according to a first data packet definition specification, wherein the exported first data packet can be exported by being packaged according to the first data packet definition specification, and the first data packet can be deployed into a Kubernetes application instance by using a first data packet on any general container cloud, so that the diversification of application deployment forms is realized.

4. The specific process of application import comprises the following steps:

referring to fig. 4, the application import is to import an application product package (for example, the product package of the application 2 shown in fig. 1, including a Helm package and a mirror image) exported by the low-code platform, or other application product packages conforming to the Helm package specification, into the low-code platform, and issue an independent application instance (for example, the application 0 shown in fig. 1), so as to further promote the diversified forms of application deployment by the application release service module devots.

S401, a developer conducts application importing through a front-end browser;

the developer accesses the web end service of the low-code application low-code platform on the browser through the external gateway proxy, performs application import operation, and the operation request is routed to the platform service module through the internal gateway to be executed, and the platform service module calls the interface of the application release service module, and the application release service module essentially calls the K8s service interface of the container cloud low-code platform to create the application.

S402, after receiving an application import request sent by a browser, a platform service module creates basic information of an application;

for example, after creating information such as application names, icons, descriptions and the like on the platform service module, the schema information is put in storage.

S403, the application publishing service module decompresses and verifies whether the Helm package of the application meets the specification based on the basic information of the application, if so, the step S404 is executed, otherwise, the application publishing service module sends specific error exception information when the analysis of the application package fails or the verification of the Helm file fails, thereby prompting a developer that the application package is incorrect or the format is incorrect, and ending the import operation (not shown in FIG. 4).

Specifically, the application publishing service module reads the application package through the code, decompresses the application package, loads the corresponding Helm file, and analyzes and verifies whether the specific configuration content of the Helm file meets the specification.

S404, an application release service module acquires a configuration file of the application;

s405, after the application release service module obtains the configuration file of the application, creating an application container and starting an application rendering engine according to the configuration file;

s406, the application release service module acquires the schema information of the application;

S407, the application release service module loads the scheme information of the application into the due container in the container cloud Kubernetes;

s408, the application rendering engine at the front end loads the schema information of the application, and the application can provide services to the outside.

Therefore, the technical scheme provided by the embodiment of the application further realizes more standardized and generalized application import and export. The low-code platform supports packing, compressing and exporting the application according to the Helm specification, so that the application can be deployed and used on other container cloud low-code platforms, the application range and the difficulty of operation and maintenance deployment are expanded, and the application deployment forms are diversified.

In summary, referring to fig. 5, an application deployment method provided in the embodiment of the present application includes:

s501, when an application needs to be published, basic information of the application to be published is determined, and based on the basic information of the application to be published, when no container corresponding to the basic information of the application to be published is determined, a configuration file of the application to be published is rendered;

the basic information of the application to be published includes, for example: the name, identification, description, icon, and page information of the application to be published.

S502, creating a container of the application to be distributed in a container cloud based on the configuration file of the application to be distributed;

the configuration file of the application to be deployed includes, for example: information such as sateshalset instance configuration, service configuration, volume persistence Volume configuration, external gateway (Ingress) configuration, etc.

S503, determining definition data information (namely Schema information) of the application to be distributed, and loading the definition data information of the application to be distributed into a container of the application to be distributed.

In the application publishing process, the embodiment of the application deploys the application by creating the independent container instance through the container cloud, so that the association relationship between application development and application use is decoupled.

In some embodiments, for secondary publications, the method further comprises:

As can be seen, the embodiments of the present application provide a more rational deployment pattern for applications. The application deployment environment and the development environment are not shared, and the developer and the common user do not influence each other. The developer can deploy the application into independent Kubernetes examples by clicking the release button, each application is an independent POD example, the advantages of self-healing, efficient scheduling, resource isolation and the like of the container cloud are fully exerted, and the availability and the independence of the application are ensured; the developer can release the application for multiple times, the original deployment environment can be reused by secondary release, only the application Schema configuration information is updated, and the application is released in a lighter weight mode.

In some embodiments, for application previews, the method further comprises:

Therefore, the embodiment of the application can realize higher efficient application development efficiency and resource utilization rate. The application development in the embodiment of the application can be rendered based on the same engine in the preview service, but the embodiment of the application opens up different working catalog spaces for different applications, and ensures the isolation of development data, so that a developer does not need to apply an independent development environment, and the development effect of the application can be checked in real time through previewing, thereby greatly improving the development efficiency of the developer; in addition, if the developer exits from the preview page or does not operate the preview page for a long time, the work process can be recycled to release resources, so that the preview service can also uniformly manage and recycle the work process of the preview application of the developer, the utilization rate of the engine is improved, and the condition that the resources are idle is avoided.

In some embodiments, the method further comprises, for an application, unpublishing:

In some embodiments, for application derivation, the method further comprises:

It can be seen that the Helm package exported by the embodiments of the present application can be deployed as a Kubernetes application instance using Helm commands on any generic container cloud, that is, the low code platform supports packing applications, compressing exports, enabling applications to be deployed for use in other container cloud low code platforms, the application method not only expands the application range and the difficulty of operation and maintenance deployment, but also realizes the diversification of application deployment forms.

In some embodiments, for application importation, the method further comprises:

Therefore, the low-code platform provided by the embodiment of the application supports importing the application according to the Helm specification, so that more standardized and generalized application importing is realized.

In some embodiments, for a user to access an application, the method further comprises:

Therefore, after the application is released, the embodiment of the application provides the routing service to the outside through the external gateway of the container cloud, so that the service access of the application is ensured not to be limited by the interference of the low-code platform

In summary, the embodiment of the application provides a corresponding technical scheme in terms of the development mode and the deployment mode of the application.

For the development mode, in the embodiment of the application, because the application preview module is arranged in the low-code platform, after the developer finishes application dragging configuration, when the application construction effect is checked through the application preview module preview operation, each application can create an independent folder on the application preview module. Therefore, different working directory spaces are opened up for different applications to supply the application-related working process loading schema, and further, the data isolation among the applications and the rendering capability of the multiplexing engine are ensured.

Further, in the embodiment of the application, the development condition is verified by using the preview environment, that is, all application preview operations are to open up an independent folder in an application preview module (run time service) in a low code platform, place an application-specific configuration file, and load the application-specific configuration file by using a rendering engine.

Further, the deployment application (release or cancel release) of the embodiment of the application can call the container cloud to create a new container environment, and the external gateway (Ingress) of the container cloud provides route forwarding for the access address of the application, so that after the application is successfully released, the user can access the successfully released application through the external gateway (Ingress) proxy. Therefore, the independence of the development environment and the deployment environment is ensured, the associated use between the application and the low-code platform is greatly decoupled, and the external service providing of the application is not influenced even if the low-code platform stops the service.

The following describes a device or apparatus provided in the embodiments of the present application, where explanation or illustration of the same or corresponding technical features as those described in the above method is omitted herein.

An electronic device provided in an embodiment of the present application, referring to fig. 6, for example, includes:

the processor 600, configured to read the program in the memory 620, performs the following procedures:

In some embodiments, the processor 600 is further configured to read the program in the memory 620, and perform the following procedure:

A transceiver 610 for receiving and transmitting data under the control of the processor 600.

Wherein in fig. 6, a bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by processor 600 and various circuits of memory represented by memory 620, linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 610 may be a number of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over transmission media, including wireless channels, wired channels, optical cables, etc. The user interface 630 may also be an interface capable of interfacing with an inscribed desired device for different user devices, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 600 in performing operations.

In some embodiments, the processor 600 may be a CPU (Central processing Unit), ASIC (Application Specific Integrated Circuit ), FPGA (Field-Programmable Gate Array, field programmable Gate array) or CPLD (Complex Programmable Logic Device ), and the processor may also employ a multicore architecture.

The processor is configured to execute any of the methods provided in the embodiments of the present application by invoking a computer program stored in a memory in accordance with the obtained executable instructions. The processor and the memory may also be physically separate.

It should be noted that, the above device provided in this embodiment of the present application can implement all the method steps implemented in the method embodiment and achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those of the method embodiment in this embodiment are omitted.

Referring to fig. 7, an application deployment apparatus provided in an embodiment of the present application includes:

a first unit 11, configured to determine basic information of an application to be published when the application needs to be published, and render a configuration file of the application to be published when it is determined that there is no container corresponding to the basic information of the application to be published based on the basic information of the application to be published;

A second unit 12, configured to create a container of the application to be published in a container cloud based on the configuration file of the application to be published;

and a third unit 13, configured to determine the definition data information of the application to be distributed, and load the definition data information of the application to be distributed into a container of the application to be distributed.

The first unit 11, the second unit 12, and the third unit 13 may be specific refinements of the application publishing service module shown in fig. 1.

In some embodiments, the first unit 11 is further configured to: and when determining that the container corresponding to the basic information of the application to be distributed exists, determining definition data information of the application to be distributed, and loading the definition data information of the application to be distributed into the container of the application to be distributed.

The application deployment device provided by the embodiment of the application may be an application deployment system shown in fig. 1, so that the device may further include a front end, an interior gateway, an application preview module, a platform service module, and the like.

Thus, in some embodiments, the apparatus further comprises an application preview module for:

In some embodiments, the apparatus further comprises a unpublishing unit to:

In some embodiments, the apparatus further comprises a export release unit for:

In some embodiments, the apparatus further comprises an import distribution unit for:

In some embodiments, the apparatus further comprises a user access service unit for:

It should be noted that, in the embodiment of the present application, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice. In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution, in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Any of the devices or apparatuses provided in the embodiments of the present application may be specifically a desktop computer, a portable computer, a smart phone, a tablet computer, a personal digital assistant (Personal Digital Assistant, PDA), or the like. May include a central processing unit (Center Processing Unit, CPU), memory, input/output devices, etc., which may include a keyboard, mouse, touch screen, etc., and output devices may include a display device, such as a liquid crystal display (Liquid Crystal Display, LCD), cathode Ray Tube (CRT), etc.

The memory may include Read Only Memory (ROM) and Random Access Memory (RAM) and provides the processor with program instructions and data stored in the memory. In the embodiments of the present application, the memory may be used to store a program of any of the methods provided in the embodiments of the present application.

The processor is configured to execute any of the methods provided in the embodiments of the present application according to the obtained program instructions by calling the program instructions stored in the memory.

Embodiments of the present application also provide a 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 of any of the above embodiments. The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The present embodiments provide a computer readable storage medium for storing computer program instructions for use with an apparatus provided in the embodiments of the present application described above, which includes a program for executing any one of the methods provided in the embodiments of the present application described above. The computer readable storage medium may be a non-transitory computer readable medium.

The computer-readable storage medium can be any available medium or data storage device that can be accessed by a computer, including, but not limited to, magnetic storage (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), and semiconductor storage (e.g., ROM, EPROM, EEPROM, nonvolatile storage (NAND FLASH), solid State Disk (SSD)), etc.

It should be understood that:

the access technology via which an entity in the communication network communicates traffic may be any suitable current or future technology, such as WLAN (wireless local access network), wiMAX (worldwide interoperability for microwave access), LTE-a, 5G, bluetooth, infrared, etc. may be used; in addition, embodiments may also apply wired technologies, e.g., IP-based access technologies, such as wired networks or fixed lines.

Embodiments suitable for implementation as software code or portions thereof and for execution using a processor or processing function are software code independent and may be specified using any known or future developed programming language, such as a high-level programming language, such as an objective-C, C, C ++, c#, java, python, javascript, other scripting languages, etc., or a low-level programming language, such as a machine language or assembler.

The implementation of the embodiments is hardware-independent and may be implemented using any known or future developed hardware technology or any hybrid thereof, such as microprocessors or CPUs (central processing units), MOS (metal oxide semiconductors), CMOS (complementary MOS), biMOS (bipolar MOS), biCMOS (bipolar CMOS), ECL (emitter coupled logic), and/or TTL (transistor-transistor logic).

Embodiments may be implemented as a single device, apparatus, unit, component, or function, or in a distributed fashion, e.g., one or more processors or processing functions may be used or shared in a process, or one or more processing segments or portions may be used and shared in a process where one physical processor or more than one physical processor may be used to implement one or more processing portions dedicated to a particular process as described.

The apparatus may be implemented by a semiconductor chip, a chipset, or a (hardware) module comprising such a chip or chipset.

Embodiments may also be implemented as any combination of hardware and software, such as an ASIC (application specific IC (integrated circuit)) component, an FPGA (field programmable gate array) or CPLD (complex programmable logic device) component, or a DSP (digital signal processor) component.

Embodiments may also be implemented as a computer program product comprising a computer usable medium having a computer readable program code embodied therein, the computer readable program code adapted to perform a process as described in the embodiments, wherein the computer usable medium may be a non-transitory medium.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

Claims

1. An application deployment method, the method comprising:

2. The method according to claim 1, wherein the method further comprises:

3. The method according to claim 1, wherein the method further comprises:

4. The method according to claim 1, wherein the method further comprises:

5. The method according to claim 1, wherein the method further comprises:

6. The method according to claim 1, wherein the method further comprises:

7. The method according to claim 1, wherein the method further comprises:

8. An application deployment apparatus, the apparatus comprising:

9. An electronic device, comprising:

a memory for storing program instructions;

a processor for invoking program instructions stored in said memory to perform the method of any of claims 1-7 in accordance with the obtained program.

10. A computer-readable storage medium storing computer-executable instructions for causing a computer to perform the method of any one of claims 1 to 7.