[go: up one dir, main page]

CN108958927B - Deployment method and device of container application, computer equipment and storage medium - Google Patents

Deployment method and device of container application, computer equipment and storage medium Download PDF

Info

Publication number
CN108958927B
CN108958927B CN201810550654.XA CN201810550654A CN108958927B CN 108958927 B CN108958927 B CN 108958927B CN 201810550654 A CN201810550654 A CN 201810550654A CN 108958927 B CN108958927 B CN 108958927B
Authority
CN
China
Prior art keywords
application
code
target
container
configuration parameters
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810550654.XA
Other languages
Chinese (zh)
Other versions
CN108958927A (en
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.)
Kangjian Information Technology Shenzhen Co Ltd
Original Assignee
Kangjian Information Technology Shenzhen 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 Kangjian Information Technology Shenzhen Co Ltd filed Critical Kangjian Information Technology Shenzhen Co Ltd
Priority to CN201810550654.XA priority Critical patent/CN108958927B/en
Publication of CN108958927A publication Critical patent/CN108958927A/en
Application granted granted Critical
Publication of CN108958927B publication Critical patent/CN108958927B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5045—Making service definitions prior to deployment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/45562—Creating, deleting, cloning virtual machine instances
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application relates to a deployment method and device of a container application, a computer device and a storage medium. The method comprises the following steps: receiving an application deployment request sent by a terminal; the application deployment request contains a code identification; pulling a corresponding code file in a code warehouse according to the code identification; analyzing the code file, determining configuration parameters required by a target application corresponding to the deployment request of the deployment application, and creating a target mirror image according to the configuration parameters; adding the code file to a target mirror image to generate a target mirror image file; and generating a container application by starting the target image file, acquiring an access address of the container application, and returning the access address to the terminal. By adopting the method, the deployment threshold of the container application can be reduced, and the deployment efficiency of the container application is improved.

Description

Deployment method and device of container application, computer equipment and storage medium
Technical Field
The present application relates to the field of computer technologies, and in particular, to a deployment method and apparatus for a container application, a computer device, and a storage medium.
Background
The advent of container technology has transformed the way traditional applications, particularly web-based B/S (browser/server) applications, are deployed and managed. Application virtualization based on container technology enables packaging and deployment of applications in an extremely fast manner. However, there is a high technical threshold for application deployment and management based on container technology, so that only a few users with relevant professional backgrounds can make application deliveries based on container technology.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a container application deployment method, apparatus, computer device, and storage medium, which can reduce the deployment threshold of the container application and improve the deployment efficiency of the container application.
A method of deploying a container application, the method comprising: receiving an application deployment request sent by a terminal; the application deployment request contains a code identification; pulling a corresponding code file in a code warehouse according to the code identifier; analyzing the code file, determining configuration parameters required by deploying a target application corresponding to the application deployment request, and creating a target mirror image according to the configuration parameters; adding the code file to the target mirror image to generate a target mirror image file; and generating a container application by starting the target image file, acquiring an access address of the container application, and returning the access address to the terminal.
In one embodiment, the code file has a corresponding code description; analyzing the code file, determining configuration parameters required by deploying a target application corresponding to the application deployment request, and creating a target image according to the configuration parameters, wherein the steps of: determining an application type of the target application based on the code description; acquiring fixed configuration parameters corresponding to the application types; analyzing the code file, and determining variable configuration parameters required by deploying the application; and creating a target image according to the fixed configuration parameters and the variable configuration parameters.
In one embodiment, the variable configuration parameters comprise load balancing configuration parameters; the parsing the code file and determining the variable configuration parameters required for deploying the application includes: extracting domain name information from the code file, and determining domain name configuration parameters based on the domain name information; calculating the code quantity of the code file, and determining a resource quota parameter based on the code quantity; determining a plurality of service nodes corresponding to the application according to the application type and the resource quota parameter; monitoring performance indexes of a plurality of service nodes in a monitoring period; and generating load balancing configuration parameters according to the performance indexes and the domain name configuration parameters.
In one embodiment, the code files include a front end code file and a back end code file; the target image comprises a first directory and a second directory; adding the code file to the target mirror image to generate a target mirror image file, including: storing the front-end code file to the first directory, and deploying a reverse service agent in the first directory; storing the back-end code file to the second directory, and deploying a back-end service component in the second directory; and packaging the target image with the reverse service agent and the back-end service component to generate the target image file.
In one embodiment, the method further comprises: capturing a data change event triggered by the container application, and generating an operation statement corresponding to the data change event; analyzing the operation statement to generate a corresponding reset statement; and if a data resetting request for the container application sent by the terminal is received, acquiring the resetting statement, and withdrawing the change of the data in the container application by operating the resetting statement.
In one embodiment, after returning the access address to the terminal, the method further includes: receiving an access request for a container application; the access request contains a target access address; starting a main process and an auxiliary process of a corresponding container application according to the target access address, wherein the main process and the auxiliary process share a memory; when the main process is abnormally closed, the auxiliary process is kept in a running state; when the main process is started again, obtaining a memory address from the auxiliary process; and writing the acquired memory address into the restarted main process, and enabling the main process to recover the container application data according to the written memory address.
In one embodiment, the method further comprises: receiving an application migration request; the application migration request comprises an application identifier; checking whether the application to be migrated corresponding to the application identification belongs to a migratable application; if the application belongs to the migratable application, acquiring a start script and an application name corresponding to the application identifier; updating the start script based on the application name, and recompiling the updated start script; adding the start script obtained after recompilation to the template mirror image to generate a migration mirror image file; and migrating the application to be migrated to a container by starting the migration image file.
A deployment apparatus for a container application, the apparatus comprising: the code acquisition module is used for receiving an application deployment request sent by a terminal; the application deployment request includes a code identification; pulling a corresponding code file in a code warehouse according to the code identifier; the mirror image generation module is used for analyzing the code file, determining configuration parameters required by deploying the target application corresponding to the application deployment request, and creating a target mirror image according to the configuration parameters; adding the code file to the target mirror image to generate a target mirror image file; and the container deployment module is used for generating a container application by starting the target image file, acquiring an access address of the container application and returning the access address to the terminal.
A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program: receiving an application deployment request sent by a terminal; the application deployment request contains a code identification; pulling a corresponding code file in a code warehouse according to the code identifier; analyzing the code file, determining configuration parameters required by deploying a target application corresponding to the application deployment request, and creating a target mirror image according to the configuration parameters; adding the code file to the target mirror image to generate a target mirror image file; and generating a container application by starting the target image file, acquiring an access address of the container application, and returning the access address to the terminal.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of: receiving an application deployment request sent by a terminal; the application deployment request contains a code identification; pulling a corresponding code file in a code warehouse according to the code identification; analyzing the code file, determining configuration parameters required by deploying a target application corresponding to the application deployment request, and creating a target mirror image according to the configuration parameters; adding the code file to the target mirror image to generate a target mirror image file; and generating a container application by starting the target image file, acquiring an access address of the container application, and returning the access address to the terminal.
According to the deployment method and device of the container application, the computer equipment and the storage medium, the terminal only needs to send the application deployment request carrying the code identifier to the server, and the server can pull the code file corresponding to the code identifier in the code warehouse; by analyzing the code file, configuration parameters required by deploying the target application corresponding to the application deployment request can be determined; according to the configuration parameters, a target image can be created; adding the code file to the target mirror image to obtain a target mirror image file; and returning the access address of the container application to the terminal by starting the target image file, namely finishing the deployment of the container application. Because the code file is automatically analyzed and the needed configuration parameters are determined, the user configuration operation is reduced, so that the user only needs to provide the code identification of the application corresponding to the code file, the automatic deployment of the container application can be realized, and the application threshold of the container technology is reduced.
Drawings
FIG. 1 is a diagram of an application scenario illustrating a method for deploying a container application in one embodiment;
FIG. 2 is a flow diagram that illustrates a method for deploying a container application, according to one embodiment;
FIG. 3 is a flowchart illustrating the steps of generating a target image file according to one embodiment;
FIG. 4 is a block diagram of a deployment apparatus for a container application in one embodiment;
FIG. 5 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The deployment method of the container application provided by the application can be applied to the application environment shown in fig. 1. Wherein the terminal 102 and the server 104 communicate via a network. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented by an independent server or a server cluster formed by multiple servers. A container application management platform is deployed on the server 104. The user can access the container application management platform through the terminal 102, and perform container application deployment and management based on the container application management platform. After a user develops a software application (hereinafter referred to as a "target application"), the user stores a code file of the target application in a code repository, and sends an application deployment request to the server 104 through the terminal 102. The code file has a corresponding code identification and code description. The application deployment request contains a code identification. The server 104 pulls the corresponding code file in the code repository according to the code identifier, determines the application type of the target application based on the code description, and obtains the fixed configuration parameters corresponding to the application type. Server 104 parses the code file to determine the variable configuration parameters needed to deploy the software application. The server 104 creates a target image according to the fixed configuration parameters and the variable configuration parameters, adds the code file to the target image, and generates a target image file. The server 104 generates a container application by starting the target image file, acquires an access address of the container application, and returns the access address to the terminal 102. In the application deployment process, the user can automatically determine the configuration parameters required by the deployment application only by providing the code identifiers of the code files corresponding to the target application, and then the container application is automatically deployed based on the configuration parameters, so that the manual participation is reduced, and the application threshold of the container technology is reduced.
In an embodiment, as shown in fig. 2, a method for deploying a container application is provided, which is described by taking the method as an example for being applied to a server in fig. 1, and includes the following steps:
step 202, receiving an application deployment request sent by a terminal; the application deployment request includes a code identification.
A container application management platform is deployed on the server. The container application management platform itself may also be deployed based on container technology. When a user needs to deploy a certain target Application in a container manner, the code file corresponding to the target Application may be stored in a code repository, and the target Application may be an APP (Application program) or a Web (World Wide Web, global Wide area network) Application. The code file includes a plurality of code subfiles, such as js (JavaScript, interpreted scripting language) files, css (Cascading Style Sheets) files, html (hypertext markup language) files, business logic script files, database management script files, and the like. In another embodiment, the code files also include other files that support the running of the target application.
The code file has a corresponding code identification. The code identification may be obtained by hashing a code file. Specifically, the terminal performs hash operation on the plurality of code subfiles respectively to obtain a hash value corresponding to each code subfile. The hash operation may be md5 (Message Digest Algorithm, fifth edition) Algorithm, or the like. The corresponding hash value may be an md5 check code or the like. It is easy to understand that the terminal may also perform other operations on the code subfile to obtain other result values, for example, obtain a hash value corresponding to the code subfile through a hash operation, which is not limited in this respect.
And the terminal stores the hash values corresponding to all the code subfiles into an intermediate file, such as a sumlist file. The terminal performs hash operation on the intermediate file to generate a hash value corresponding to the intermediate file, and independently writes the hash value corresponding to the intermediate file into a target file, such as a Checksum file, as a code identifier of the code file. The server may read the code identification of the code file from the Checksum file. In another embodiment, the code identification may be a version identification of the corresponding container application.
And step 204, pulling a corresponding code file in the code warehouse according to the code identification.
And the user sends an application deployment request to the container application management platform through the terminal. The application deployment request carries the code identification of the code file corresponding to the target application. And the container application management platform pulls the corresponding code file from the code warehouse according to the code identification.
And step 206, analyzing the code file, determining configuration parameters required by the target application corresponding to the deployment request of the deployment application, and creating a target mirror image according to the configuration parameters.
And the container application management platform analyzes the code file and extracts the configuration parameters required by the deployment of the target application from the code file according to the required configuration items. The configuration parameters include fixed configuration parameters and variable configuration parameters. The fixed configuration parameters can reduce repeated configuration operation and improve the parameter configuration efficiency. The variable configuration parameters vary from target application to target application, so that the method can be adapted to different target applications. In other words, the container application management plane can temporarily generate corresponding configuration parameters according to specific applications, and adaptability is high.
And the container application management platform creates a target image based on the open source images such as the Ngnix (a reverse proxy server) and the like according to the configuration parameters. The target image includes a plurality of storage directories. Different storage directories store different files, such as an operating system basic image file, the code file and the like.
In one embodiment, the code file has a corresponding code description; analyzing the code file, determining configuration parameters required by the target application corresponding to the deployment request of the deployment application, and creating a target mirror image according to the configuration parameters, wherein the steps comprise: determining an application type of the target application based on the code description; acquiring fixed configuration parameters corresponding to the application types; analyzing the code file, and determining variable configuration parameters required by deployment application; and creating the target image according to the fixed configuration parameters and the variable configuration parameters.
The code file includes a code description. The code description can be a descriptive file added by a code file developer according to development requirements and code logic at the later stage, and can also be code comments and the like corresponding to a plurality of code statements in the code file respectively. The container application management platform may determine an application type of the target application based on the code description.
The server prestores different application types and sets corresponding fixed configuration parameters. And the container application management platform acquires the corresponding fixed configuration parameters according to the application type of the target application. The container application management platform analyzes the extracted code file, and further obtains variable configuration parameters, such as domain name configuration parameters, user access authority configuration parameters, resource quota configuration parameters and the like, required by deploying the target application. The configuration parameters are obtained through automatic analysis according to the code files, configuration operations of a user can be reduced, and therefore the technical threshold is lowered.
And step 208, adding the code file to the target mirror image to generate a target mirror image file.
The target image has a corresponding directory structure. And the container application management platform calls the release system interface to add the code file to the corresponding storage directory according to the standard directory. The container application management platform generates a Docker Build command, and packs the target image into a Docker image file (hereinafter referred to as a target image file) based on the Docker Build command, so as to pack the target application and other files dependent on the operation of the target application into a portable container. In another embodiment, the container application management platform uploads the target image file to a private image warehouse or a public warehouse (hereinafter collectively referred to as "image warehouse") through a Docker Push command, so as to be downloaded and used by a user.
Step 210, generating a container application by starting the target image file, acquiring an access address of the container application, and returning the access address to the terminal.
The container application management platform applies for a corresponding number of service nodes from the private cloud according to the physical resources needed by the deployment of the target application. The service node may be a stand-alone server or may be a virtual machine on a server. When a prompt that resource allocation is completed, which is returned by the private cloud, is received, the container application management platform issues a corresponding initialization instruction to the applied service node by using salt (an automatic virtual machine management software). Through the initialization instruction, the container application management platform installs a container management agent, such as a ran cher agent or a swap agent, on one of the service nodes.
And the container application management platform calls container cluster management interfaces such as a sender and a sweep to form a cluster by the initialized multiple service nodes. Specifically, the container application management platform sends a cluster creation request to a container cluster management server such as a ranker server or a swap server by calling a container cluster management interface, so that the container cluster management server creates a virtual server cluster according to the cluster creation request. And the container application management platform sends a cluster packaging request to the container cluster management server, so that the container cluster management server adds the node identification corresponding to the applied service node in the server cluster according to the cluster packaging request. The applied plurality of scattered service nodes are configured into a logical server cluster, so that the container application is convenient to manage and use.
The container application management platform starts the target image file on the service node where the container management agent is deployed. Specifically, the server sends a request for starting the target image file to the container cluster management server by calling the container cluster management interface. The container cluster management server translates the request for starting the target image file, converts the request into a request for starting the container, and sends the request for starting the container to the container management agent. Since the container management agent is deployed on the service node in advance through the initialization instruction, the service node can receive the request for starting the target image file sent by the container cluster management server. The container management agent sends a request for starting a container to a container daemon, such as a docker daemon, that is started in advance. And the container daemon process pulls the corresponding target image file from a preset image warehouse, and starts the target image file on the applied service node by adjusting the relevant configuration parameters, so that the deployment of the container application is realized. The configuration parameter may be a port number, a volume map (data volume map), or the like.
And the container application management platform returns the access address of the container application to the terminal. The access address may be a server address and port number, such as 192.168.1.1:8001. the access address generation rule can be freely set based on actual needs. When a user needs to access the container application, the user only needs to download a corresponding target image file in the image warehouse, start the target image file through a preset instruction, and input a corresponding access address in a browser of the terminal to directly access the container application.
Because the target image file integrates all other files on which the target image file runs in advance, the container application can run independently without depending on other components, so that a user does not need to care about the version compatibility of the current browser or the support problem of depending on a library when installing and deploying the container application, and the installation operation is greatly simplified.
In this embodiment, the terminal only needs to send the application deployment request carrying the code identifier to the server, and the server can pull the code file corresponding to the code identifier from the code repository; the code file is analyzed, so that the configuration parameters needed by the target application corresponding to the deployment request of the deployment application can be determined; according to the configuration parameters, a target image can be created; adding the code file to the target mirror image to obtain a target mirror image file; and returning the access address of the container application to the terminal by starting the target image file, namely finishing the deployment of the container application. Because the code file is automatically analyzed and determined to obtain the required configuration parameters, the user configuration operation is reduced, so that the user only needs to provide the code identification of the application corresponding to the code file, the automatic deployment of the container application can be realized, and the application threshold of the container technology is reduced.
In one embodiment, the variable configuration parameters include load balancing configuration parameters; analyzing the code file, and determining variable configuration parameters required by the deployment application, wherein the variable configuration parameters comprise: extracting domain name information from the code file, and determining domain name configuration parameters based on the domain name information; calculating the code quantity of the code file, and determining a resource quota parameter based on the code quantity; determining a plurality of service nodes corresponding to the application according to the application type and the resource quota parameter; monitoring performance indexes of a plurality of service nodes in a monitoring period; and generating load balancing configuration parameters according to the performance indexes and the domain name configuration parameters.
The variable configuration parameters comprise domain name configuration parameters, user access authority configuration parameters, resource quota configuration parameters and the like. The container application management platform extracts domain name information in the code file. The domain name information includes a domain name (or IP address) and a port number for accessing the target application. The container application management platform determines domain name configuration parameters based on the domain name information. And the container application management platform extracts the user authority information in the code file. The user permission information comprises a plurality of user types, and permission information is correspondingly carried out on each user type, for example, a tester is set to have a read permission (pull) to the container application, and a developer has a read-write permission (push/pull) to the container application. The container application management platform determines access permission configuration parameters based on the user permission information. And the container application management platform calculates the code amount of the code file and determines a resource quota parameter based on the code amount. The resource quota parameter includes the capacity of physical resources such as CPU and memory required for deploying the container application.
And the container application management platform determines a plurality of service nodes corresponding to the application according to the application type and the resource quota parameter. Specifically, the container application management platform applies for a corresponding number of service nodes from the private cloud according to the physical resources required for deploying the target application. The service node may be a stand-alone server or may be a virtual machine on a server. And the container application management platform receives a prompt of resource allocation completion returned by the private cloud. The prompt of the completion of the resource allocation comprises node identifications corresponding to one or more service nodes respectively.
The container application management platform uses salt (an automatic virtual machine management software) to issue a corresponding initialization instruction to the applied service node. Through the initialization instruction, the container application management platform installs the monitoring component on each service node. And the container application management platform calls the monitoring component to monitor the current performance index of each service node to generate a monitoring result. The performance index includes utilization rate of physical resources such as CPU utilization rate, memory utilization rate and disk utilization rate. The performance indicators may be qualitative or quantitative performance indicators.
The performance indicators also include load amounts. Other container applications may have been deployed on the service node, and the deployed container applications occupy the service node resources and affect the performance of the service node. The traditional container application management platform monitors the load of each service node based on the number of links, namely, the existing number of connections between the application nodes and the service nodes is monitored. However, the link exists in two directions, and the application node must maintain the link state through heartbeat or request result, which increases the service implementation cost of the service node.
In order to solve the above problem, the container application management platform in this embodiment monitors the load of each service node based on the number of the service requests that are successfully transmitted in the monitoring period. Specifically, the container application management platform allocates service requests to the service nodes according to a preset load balancing strategy in a monitoring period, and records the transmission result of each service request. And the container application management platform counts the number of Http requests which are sent to different service nodes within the monitoring time period and have transmission results of successful transmission, and records the number as the number of successful requests. Whether the service request is transmitted successfully is judged not by heartbeat in the traditional scheme but by a status code returned by a network layer in a TCP protocol of a home terminal of the container application management platform. For example, status code "00" indicates a successful transmission; returning the other status code (hereinafter "error code") indicates a transmission failure. And the service nodes judge the load of each service node in the monitoring period based on the successful number of the requests. It is readily understood that a greater number of successful requests indicates a greater amount of load being carried by the corresponding service node.
And the container application management platform generates load balancing configuration parameters such as initial weight corresponding to each service node according to the performance indexes and the domain name configuration parameters.
In this embodiment, performance indexes of the plurality of service nodes are monitored in real time, and corresponding load balancing configuration parameters are dynamically generated according to the performance indexes, so that the load balancing strategy has strong adaptability. The load capacity of each service node is monitored based on the number of the service requests successfully transmitted in the monitoring period, so that the service implementation cost of the service nodes can be reduced, and the occupation of resources of each service node is reduced.
In one embodiment, the code files include a front end code file and a back end code file; the target image includes a first directory and a second directory. As shown in fig. 3, the step of adding the code file to the target image and generating the target image file, that is, generating the target image file, includes:
step 302, storing the front-end code file to a first directory, and deploying a reverse service agent in the first directory.
And step 304, storing the back-end code file to a second directory, and deploying the back-end service component in the second directory.
And step 306, packaging the target image with the reverse service agent and the back-end service component to generate a target image file.
The target application to be deployed may be a single page Web application (SPA). The single-page Web application realizes page loading in a single-page mode, and does not reload pages during use. When a page is loaded for the first time, the single-page Web application loads page resources of all pages for caching, and then the cache is pulled through a js script to realize page switching. The single page mode can significantly improve the page switching speed compared to the conventional multi-page mode. The front-end code files and the back-end code files of a single-page Web application are usually developed by different development teams. For example, the development of the front-end code file is carried out based on the first terminal; and developing a back-end code file based on the second terminal. For maintenance, the front-end code file and the back-end code file are usually deployed on different servers or different virtual machines of the same server. In other words, single-page Web applications are typically deployed front-end and back-end separately.
The front-end and back-end separated deployment causes the problem that the version of the front-end code file is not compatible with that of the back-end code file in the single-page Web application. For example, assuming that only the front-end code file is updated, when the new version front-end code file calls the old version background resource interface, there may be a problem that the interface does not exist or the function is not matched; or, assuming that only the back-end code file is updated, an interface is newly added, and the old front-end code file cannot know the existence and calling mode of the interface, which causes the problem of interface resource waste.
In order to solve the above problem, the container application management platform detects whether the front-end code file and the back-end code file belong to the cooperative release when the code repository pulls the code file. The cooperative release means that the release time difference between the front-end code file and the back-end code file is lower than a threshold value. If the file belongs to the matched release, the container application management platform respectively stores the front-end code file and the back-end code file to different directories of the target mirror image, and if the front-end code file is stored to the first directory, the back-end code file is stored to the second directory. The first directory may be/usr/src/front, the second directory may be/usr/src/svc, etc.
And the container application management platform deploys a reverse service agent for providing service for the first directory in the target mirror image, and configures the reverse service agent according to preset configuration information. The reverse service agent may be Nginx (a type of load balancing software). The reverse service proxy is used as an HTTP request inlet of the whole single-page Web application and is used for providing HTTP service for the front-end code file. The server deploys a backend service component serving the second directory at the target image. The back-end service component is used for providing an Http service for the back-end code file, and may be django (Http service framework based on python) and the like.
After deployment of the reverse service agent and the back-end service component is completed, the container application management platform generates a Docker Build command, and a target image containing the first directory and the second directory is packaged into a target image file based on the Docker Build command.
In this embodiment, the front-end code file and the back-end code file are deployed in different directories of the same target image, and different service components are adopted to provide services for the front-end code file and the back-end code file respectively, so that the front-end code file and the back-end code file can be issued to different servers respectively in a simulated traditional manner. In other words, the single-page Web application implementation method provided by the application can continue the advantage that independent maintenance of the front-end code file and the back-end code file is facilitated when the front end and the back end are separately deployed in a traditional mode, and can solve the problem that versions of the front end and the back end are not matched due to the fact that the front end and the back end are separately deployed in the traditional mode.
In one embodiment, the method further comprises: capturing a data change event triggered by the container application, and generating an operation statement corresponding to the data change event; analyzing the operation statement to generate a corresponding reset statement; and if a data resetting request for the container application sent by the terminal is received, acquiring a resetting statement, and withdrawing the change of the data in the container application by operating the resetting statement.
The container application deploys a corresponding database. The user can access the container application through the terminal, and change the data in the database in the container application. It should be noted that the terminal initiating the application deployment request and the terminal triggering the configuration change event may be the same terminal or different terminals. The traditional method needs manual remedy when error data change operation occurs, namely, the modified and changed data are played back to the database manually, and the efficiency is low.
In order to solve the above problem, the container application management platform of the present embodiment monitors data change operations that occur in the database corresponding to the container application. Specifically, the terminal captures a data change event generated in the database based on a preset buried point, reports the captured data change event to the server, and the server records the data change operation in the form of an SQL statement (hereinafter referred to as "REDO"), that is, generates an operation statement corresponding to the data change operation. The server parses the operation statement pair REDO to generate a corresponding reset statement (hereinafter "UNDO"), thereby causing each data change operation to have a corresponding UNDO. The server stores the UNDO for each table update operation.
When a subsequent user needs to reset the data which is added or deleted by mistake, the corresponding data table does not need to be opened, the corresponding reset statement can be triggered to be executed only based on the data reset management item on the container application, the corresponding data change operation is automatically withdrawn, the database returns to the state before the data change occurs, and the data reset operation is simplified.
In the embodiment, data change events started by a user at any time are monitored and recorded, and corresponding reset statements are automatically generated, so that the data change operation of the user with the smallest fine-grained rollback error can be helped, the user can restore data without opening a corresponding data table, and the data reset operation is simplified.
In one embodiment, after returning the access address to the terminal, the method further includes: receiving an access request for a container application; the access request contains a target access address; starting a main process and an auxiliary process of the corresponding container application according to the target access address, wherein the main process and the auxiliary process share a memory; when the main process is abnormally closed, the auxiliary process is kept in a running state; when the main process is started again, obtaining the memory address from the auxiliary process; and writing the acquired memory address into the restarted main process, so that the main process recovers the container application data according to the written memory address.
And the server receives an access request for the container application sent by the terminal, and starts a main process and an auxiliary process of the corresponding container application according to a target access address carried by the access request. It should be noted that the terminal that initiates the application deployment request and the terminal that initiates the access request may be the same terminal or different terminals. The server sets the same address space identification in the main process and the auxiliary process. In other words, the memory addresses in the address spaces of the main process and the auxiliary process are the same, and the main process and the auxiliary process share the memory space corresponding to the memory address through the same memory address. The main process performs data processing on the container application data in the shared memory, and the auxiliary process does not perform any data processing on the container application data in the shared memory.
And during the container application access of the terminal, the server monitors whether the main process is abnormally closed or not in real time. Specifically, when the closing of the main process is monitored, the process parameters corresponding to the main process are obtained, the obtained process parameters are compared with the process parameters corresponding to the main process and within the normal range, and whether the main process is abnormally closed or not is determined through parameter comparison. For example, the process parameter may be a number of threads or processor occupancy, etc.
When the abnormal closing of the main process is monitored, the server does not perform any processing on the auxiliary process, and the auxiliary process is kept in the running state. It should be noted that, when the secondary process is in the running state, the container application data in the memory shared by the primary process and the secondary process is not lost, but is still stored in the shared memory. The server monitors whether the main process is started again within a preset time period. And when the situation that the main process is started again is monitored, the server determines the address space of the auxiliary process and acquires the memory address from the address space of the auxiliary process. The memory address is a unique identifier corresponding to a memory space for storing the application data of the container.
And the server writes the acquired memory address into the re-opened main process, so that the main process accesses the memory space according to the written memory address, acquires the container application data before the abnormal closing of the main process from the accessed memory space, and restores the application page of the container before the abnormal closing of the main process according to the acquired container application data.
In this embodiment, when the main process of the container application is abnormally closed, the auxiliary process is kept in the running state, so that it can be ensured that the container application data in the memory space corresponding to the memory address is not lost. When the application main process is opened again, the memory address in the auxiliary process is written into the reopened main process, so that data recovery can be realized, the condition that the container application data is lost due to abnormal closing of the container application is avoided, and the safety of the container application data is improved.
In one embodiment, the method further comprises: receiving an application migration request; the application migration request contains an application identifier; checking whether the application to be migrated corresponding to the application identifier belongs to a migratable application; if the application belongs to the migratable application, acquiring an application name corresponding to the start script and the application identifier; updating the start script based on the application name, and recompiling the updated start script; adding the start script obtained after recompilation to the template mirror image to generate a migration mirror image file; and migrating the application to be migrated to the container by starting the migration image file.
The container application management platform also supports one-touch migration of legacy applications to the container environment. Traditional applications refer to software applications that are deployed on servers in a non-containerized manner. Specifically, the container application management platform receives an application migration request sent by a terminal. The application migration request contains an application identification of a legacy application to be migrated (hereinafter referred to as "application to be migrated"). The container application management platform obtains the application to be migrated corresponding to the application identifier based on an antx interface (Antenna interface). The container application management platform calls an SCM interface (a software configuration management interface) to query the application type and application name of the application to be migrated. The application types include stateless applications and stateful applications. The stateless application refers to an application that does not depend on resources such as a fixed IP address, such as a microservice. Stateful applications are applications that need to rely on fixed resources. Stateless applications belong to migratable applications. And the container application management platform checks whether the application type of the application to be migrated is stateless application.
And if the application belongs to the migratable application, the container application management platform acquires a pre-stored start script, and updates the start script based on the acquired application name of the application to be migrated so as to be compatible with different containers to start simultaneously. The start script may be a service. sh script is a script that starts or stops running common to all legacy applications. And calling the issuing system interface by the container application management platform to recompile the updated start script, adding the recompiled start script to the template mirror image, and generating a migration mirror image file. The container application management platform can migrate the application to be migrated to the container environment by starting the migration mirror image file.
It should be noted that the terminal that initiates the application deployment request and the terminal that initiates the application migration request may be the same terminal or different terminals.
In this embodiment, the learning cost of the container technology is reduced, and the containerization of the conventional application can be completed by simple modification.
It should be understood that although the steps in the flowcharts of fig. 2 and 3 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not limited to being performed in the exact order illustrated and, unless explicitly stated herein, may be performed in other orders. Moreover, at least some of the steps in fig. 2 and 3 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed alternately or alternately with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 4, there is provided a deployment apparatus for a container application, comprising: a code acquisition module 402, an image generation module 404, and a container deployment module 406, wherein:
a code obtaining module 402, configured to receive an application deployment request sent by a terminal; the application deployment request includes a code identification; and pulling the corresponding code file in the code warehouse according to the code identification.
The mirror image generation module 404 is configured to analyze the code file, determine a configuration parameter required by the target application corresponding to the deployment request of the deployment application, and create a target mirror image according to the configuration parameter; and adding the code file to the target mirror image to generate a target mirror image file.
The container deployment module 406 is configured to generate a container application by starting the target image file, acquire an access address of the container application, and return the access address to the terminal.
In one embodiment, the code file has a corresponding code description; the image generation module 404 is further configured to determine an application type of the target application based on the code description; acquiring fixed configuration parameters corresponding to the application types; analyzing the code file, and determining variable configuration parameters required by deployment application; and creating the target image according to the fixed configuration parameters and the variable configuration parameters.
In one embodiment, the variable configuration parameters include load balancing configuration parameters; the mirror image generation module 404 is further configured to extract domain name information from the code file, and determine domain name configuration parameters based on the domain name information; calculating the code quantity of the code file, and determining a resource quota parameter based on the code quantity; determining a plurality of service nodes corresponding to the application according to the application type and the resource quota parameter; monitoring performance indexes of a plurality of service nodes in a monitoring period; and generating load balancing configuration parameters according to the performance indexes and the domain name configuration parameters.
In one embodiment, the code files include a front end code file and a back end code file; the target image comprises a first directory and a second directory; the mirror image generation module 404 is further configured to store the front-end code file in a first directory, and deploy a reverse service agent in the first directory; storing the back-end code file to a second directory, and deploying a back-end service component in the second directory; and packaging the target image with the reverse service agent and the back-end service component to generate a target image file.
In one embodiment, the apparatus further includes a data resetting module 408, configured to capture a data change event triggered by the container application, and generate an operation statement corresponding to the data change event; analyzing the operation statement to generate a corresponding reset statement; and if a data reset request for the container application sent by the terminal is received, acquiring a reset statement, and withdrawing the change of the data in the container application by operating the reset statement.
In one embodiment, the apparatus further comprises a data recovery module 410 for receiving an access request for the container application; the access request contains a target access address; starting a main process and an auxiliary process of the corresponding container application according to the target access address, wherein the main process and the auxiliary process share a memory; when the main process is abnormally closed, the auxiliary process is kept in a running state; when the main process is started again, acquiring a memory address from the auxiliary process; and writing the acquired memory address into the restarted main process, so that the main process recovers the container application data according to the written memory address.
In one embodiment, the apparatus further comprises an application migration module 412 to receive an application migration request; the application migration request comprises an application identifier; verifying whether the application to be migrated corresponding to the application identifier belongs to the migratable application; if the application belongs to the migratable application, acquiring an application name corresponding to the start script and the application identifier; updating the start script based on the application name, and recompiling the updated start script; adding the start script obtained after recompilation to the template mirror image to generate a migration mirror image file; and migrating the application to be migrated to the container by starting the migration image file.
For specific definition of the deployment apparatus of the container application, reference may be made to the above definition of the deployment method of the container application, which is not described herein again. The various modules in the deployment apparatus of the container application described above may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 5. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing operation data and the like applied to the container. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method of deployment of a container application.
Those skilled in the art will appreciate that the architecture shown in fig. 5 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, there is provided a computer device comprising a memory storing a computer program and a processor implementing the following steps when the processor executes the computer program: receiving an application deployment request sent by a terminal; the application deployment request includes a code identification; pulling a corresponding code file in a code warehouse according to the code identification; analyzing the code file, determining configuration parameters required by a target application corresponding to the deployment request of the deployment application, and creating a target mirror image according to the configuration parameters; adding the code file to a target mirror image to generate a target mirror image file; and generating a container application by starting the target image file, acquiring an access address of the container application, and returning the access address to the terminal.
In one embodiment, the code file has a corresponding code description; the processor when executing the computer program further realizes the following steps: determining an application type of the target application based on the code description; acquiring fixed configuration parameters corresponding to the application types; analyzing the code file, and determining variable configuration parameters required by deployment application; and creating the target image according to the fixed configuration parameters and the variable configuration parameters.
In one embodiment, the variable configuration parameters include load balancing configuration parameters; the processor, when executing the computer program, further performs the steps of: extracting domain name information from the code file, and determining domain name configuration parameters based on the domain name information; calculating the code amount of the code file, and determining a resource quota parameter based on the code amount; determining a plurality of service nodes corresponding to the application according to the application type and the resource quota parameter; monitoring performance indexes of a plurality of service nodes in a monitoring period; and generating load balancing configuration parameters according to the performance indexes and the domain name configuration parameters.
In one embodiment, the code files include a front end code file and a back end code file; the target image comprises a first directory and a second directory; the processor when executing the computer program further realizes the following steps: storing the front-end code file to a first directory, and deploying a reverse service agent in the first directory; storing the back-end code file to a second directory, and deploying a back-end service component in the second directory; and packaging the target mirror image with the reverse service agent and the back-end service component to generate a target mirror image file.
In one embodiment, the processor, when executing the computer program, further performs the steps of: capturing a data change event triggered by the container application, and generating an operation statement corresponding to the data change event; analyzing the operation statement to generate a corresponding reset statement; and if a data resetting request for the container application sent by the terminal is received, acquiring a resetting statement, and withdrawing the change of the data in the container application by operating the resetting statement.
In one embodiment, the processor, when executing the computer program, further performs the steps of: receiving an access request for a container application; the access request contains a target access address; starting a main process and an auxiliary process of the corresponding container application according to the target access address, wherein the main process and the auxiliary process share a memory; when the main process is abnormally closed, the auxiliary process is kept in a running state; when the main process is started again, obtaining the memory address from the auxiliary process; and writing the acquired memory address into the restarted main process, so that the main process recovers the container application data according to the written memory address.
In one embodiment, the processor when executing the computer program further performs the steps of: receiving an application migration request; the application migration request contains an application identifier; checking whether the application to be migrated corresponding to the application identifier belongs to a migratable application; if the application belongs to the migratable application, acquiring an application name corresponding to the start script and the application identifier; updating the start script based on the application name, and recompiling the updated start script; adding the start script obtained after recompilation to the template mirror image to generate a migration mirror image file; and migrating the application to be migrated to the container by starting the migration image file.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: receiving an application deployment request sent by a terminal; the application deployment request includes a code identification; pulling a corresponding code file in a code warehouse according to the code identifier; analyzing the code file, determining configuration parameters required by a target application corresponding to the deployment request of the deployment application, and creating a target mirror image according to the configuration parameters; adding the code file to a target mirror image to generate a target mirror image file; and generating a container application by starting the target image file, acquiring an access address of the container application, and returning the access address to the terminal.
In one embodiment, the code file has a corresponding code description; the computer program when executed by the processor further realizes the steps of: determining an application type of the target application based on the code description; acquiring fixed configuration parameters corresponding to the application types; analyzing the code file, and determining variable configuration parameters required by deployment application; and creating the target image according to the fixed configuration parameters and the variable configuration parameters.
In one embodiment, the variable configuration parameters include load balancing configuration parameters; the computer program when executed by the processor further realizes the steps of: extracting domain name information from the code file, and determining domain name configuration parameters based on the domain name information; calculating the code quantity of the code file, and determining a resource quota parameter based on the code quantity; determining a plurality of service nodes corresponding to the application according to the application type and the resource quota parameter; monitoring performance indexes of a plurality of service nodes in a monitoring period; and generating load balancing configuration parameters according to the performance indexes and the domain name configuration parameters.
In one embodiment, the code files include a front end code file and a back end code file; the target image comprises a first directory and a second directory; the computer program when executed by the processor further realizes the steps of: storing the front-end code file to a first directory, and deploying a reverse service agent in the first directory; storing the back-end code file to a second directory, and deploying a back-end service component in the second directory; and packaging the target image with the reverse service agent and the back-end service component to generate a target image file.
In one embodiment, the computer program when executed by the processor further performs the steps of: capturing a data change event triggered by the container application, and generating an operation statement corresponding to the data change event; analyzing the operation statement to generate a corresponding reset statement; and if a data reset request for the container application sent by the terminal is received, acquiring a reset statement, and withdrawing the change of the data in the container application by operating the reset statement.
In one embodiment, the computer program when executed by the processor further performs the steps of: receiving an access request for a container application; the access request contains a target access address; starting a main process and an auxiliary process of the corresponding container application according to the target access address, wherein the main process and the auxiliary process share a memory; when the main process is abnormally closed, the auxiliary process is kept in a running state; when the main process is started again, acquiring a memory address from the auxiliary process; and writing the acquired memory address into the restarted main process, so that the main process recovers the container application data according to the written memory address.
In one embodiment, the computer program when executed by the processor further performs the steps of: receiving an application migration request; the application migration request contains an application identifier; checking whether the application to be migrated corresponding to the application identifier belongs to a migratable application; if the application belongs to the migratable application, acquiring an application name corresponding to the start script and the application identifier; updating the start script based on the application name, and recompiling the updated start script; adding the start script obtained after recompilation to the template mirror image to generate a migration mirror image file; and migrating the application to be migrated to the container by starting the migration image file.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware related to instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), rambus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
All possible combinations of the technical features in the above embodiments may not be described for the sake of brevity, but should be considered as being within the scope of the present disclosure as long as there is no contradiction between the combinations of the technical features.
The above examples only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims (10)

1. A method of deploying a container application, the method comprising:
receiving an application deployment request sent by a terminal; the application deployment request contains a code identification;
pulling a corresponding code file in a code warehouse according to the code identifier;
analyzing the code file, determining configuration parameters required by deploying a target application corresponding to the application deployment request, and creating a target mirror image according to the configuration parameters;
adding the code file to the target mirror image to generate a target mirror image file;
and generating a container application by starting the target image file, acquiring an access address of the container application, and returning the access address to the terminal.
2. The method of claim 1, wherein the code file has a corresponding code description; analyzing the code file, determining configuration parameters required by deploying a target application corresponding to the application deployment request, and creating a target image according to the configuration parameters, wherein the steps of:
determining an application type of the target application based on the code description;
acquiring fixed configuration parameters corresponding to the application type;
analyzing the code file, and determining variable configuration parameters required by deploying the target application;
and creating a target image according to the fixed configuration parameters and the variable configuration parameters.
3. The method of claim 2, wherein the variable configuration parameters comprise load balancing configuration parameters; the analyzing the code file and determining the variable configuration parameters required by deploying the target application comprises:
extracting domain name information from the code file, and determining domain name configuration parameters based on the domain name information;
calculating the code quantity of the code file, and determining a resource quota parameter based on the code quantity;
determining a plurality of service nodes corresponding to the target application according to the application type and the resource quota parameter;
monitoring performance indexes of a plurality of service nodes in a monitoring period;
and generating the load balancing configuration parameters according to the performance indexes and the domain name configuration parameters.
4. The method of claim 1, wherein the code files comprise a front-end code file and a back-end code file; the target image comprises a first directory and a second directory; adding a code file to the target mirror image to generate a target mirror image file, including:
storing the front-end code file to the first directory, and deploying a reverse service agent in the first directory;
storing the back-end code file to the second directory, and deploying a back-end service component in the second directory;
and packaging the target image with the reverse service agent and the back-end service component to generate the target image file.
5. The method of claim 1, further comprising:
capturing a data change event triggered by the container application, and generating an operation statement corresponding to the data change event;
analyzing the operation statement to generate a corresponding reset statement;
and if a data resetting request for the container application is received, acquiring the resetting statement, and withdrawing the change of the data in the container application by operating the resetting statement.
6. The method of claim 1, wherein after returning the access address to the terminal, further comprising:
receiving an access request for a container application; the access request comprises a target access address;
starting a main process and an auxiliary process of a corresponding container application according to the target access address, wherein the main process and the auxiliary process share a memory;
when the main process is abnormally closed, the auxiliary process is kept in a running state;
when the main process is started again, acquiring a memory address from the auxiliary process;
and writing the acquired memory address into the restarted main process, so that the main process performs container application data recovery according to the written memory address.
7. The method of claim 1, further comprising:
receiving an application migration request; the application migration request comprises an application identifier;
verifying whether the application to be migrated corresponding to the application identifier belongs to migratable applications;
if the application belongs to the migratable application, acquiring a start script and an application name corresponding to the application identifier;
updating the start script based on the application name, and recompiling the updated start script;
adding the start script obtained after recompilation to the template mirror image to generate a migration mirror image file;
and migrating the application to be migrated to a container by starting the migration image file.
8. A deployment device for a container application, the device comprising:
the code acquisition module is used for receiving an application deployment request sent by a terminal; the application deployment request contains a code identification; pulling a corresponding code file in a code warehouse according to the code identifier;
the mirror image generation module is used for analyzing the code file, determining configuration parameters required by deploying the target application corresponding to the application deployment request, and creating a target mirror image according to the configuration parameters; adding the code file to the target mirror image to generate a target mirror image file;
and the container deployment module is used for generating a container application by starting the target image file, acquiring an access address of the container application and returning the access address to the terminal.
9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor when executing the computer program performs the steps of the method according to any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
CN201810550654.XA 2018-05-31 2018-05-31 Deployment method and device of container application, computer equipment and storage medium Active CN108958927B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810550654.XA CN108958927B (en) 2018-05-31 2018-05-31 Deployment method and device of container application, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810550654.XA CN108958927B (en) 2018-05-31 2018-05-31 Deployment method and device of container application, computer equipment and storage medium

Publications (2)

Publication Number Publication Date
CN108958927A CN108958927A (en) 2018-12-07
CN108958927B true CN108958927B (en) 2023-04-18

Family

ID=64492741

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810550654.XA Active CN108958927B (en) 2018-05-31 2018-05-31 Deployment method and device of container application, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN108958927B (en)

Families Citing this family (142)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109634655A (en) * 2018-12-10 2019-04-16 江苏满运软件科技有限公司 Variable configuration method based on heat deployment, device, electronic equipment, storage medium
CN109819014B (en) * 2018-12-14 2022-10-25 平安普惠企业管理有限公司 Project deployment method and device, computer equipment and storage medium
CN111352689B (en) * 2018-12-21 2023-04-07 中国电信股份有限公司 Method and device for realizing seamless migration of application containerized deployment
CN111382136B (en) * 2018-12-29 2024-03-15 华为技术有限公司 File system mirror image and file request method
CN111381867B (en) * 2018-12-30 2023-05-09 贝壳技术有限公司 Packaging deployment method and device supporting service reconfiguration
CN111427949B (en) * 2019-01-09 2023-10-20 杭州海康威视数字技术股份有限公司 Method and device for creating big data service
US11061718B2 (en) * 2019-02-15 2021-07-13 International Business Machines Corporation Pattern-based artificial intelligence planner for computer environment migration
CN109976872B (en) * 2019-02-21 2021-05-18 北京达佳互联信息技术有限公司 Data processing method and device, electronic equipment and storage medium
CN110007948A (en) * 2019-02-22 2019-07-12 贵州力创科技发展有限公司 A kind of O&M method, apparatus and storage medium
CN109936571B (en) * 2019-02-22 2020-05-29 全球能源互联网研究院有限公司 Mass data sharing method, open sharing platform and electronic device
CN110096304A (en) * 2019-03-16 2019-08-06 平安城市建设科技(深圳)有限公司 Task construction method, device, equipment and storage medium based on Jenkins
CN110333954B (en) * 2019-04-04 2024-02-23 平安科技（深圳）有限公司 Interface call recording method, device, equipment and storage medium based on django framework
CN109992354B (en) * 2019-04-09 2021-02-19 腾讯科技（深圳）有限公司 Container processing method, device, main body server, system and storage medium
CN110134455B (en) * 2019-04-12 2025-01-21 深圳平安医疗健康科技服务有限公司 Application management system and method
CN110096333B (en) * 2019-04-18 2021-06-29 华中科技大学 A non-volatile memory-based container performance acceleration method
CN110333930A (en) * 2019-04-29 2019-10-15 中国联合网络通信集团有限公司 Digital platform system
CN110138776B (en) * 2019-05-14 2020-04-28 重庆天蓬网络有限公司 Docker intrusion detection method, device and medium based on command monitoring
CN110262873B (en) * 2019-05-17 2023-07-28 平安科技（深圳）有限公司 Configuration modification method and device for container application, computer equipment and storage medium
CN110221859A (en) * 2019-06-05 2019-09-10 软通智慧科技有限公司 Deployment online management method, device, equipment and storage medium of application
CN110399134A (en) * 2019-06-28 2019-11-01 绿漫科技有限公司 A kind of quick deployment method and system based on container
CN112148419B (en) * 2019-06-28 2024-01-02 杭州海康威视数字技术股份有限公司 Mirror image management method, device and system in cloud platform and storage medium
CN110333877A (en) * 2019-07-09 2019-10-15 西安点告网络科技有限公司 Visualized container configuring management method, apparatus and system based on application
CN112204520A (en) * 2019-07-11 2021-01-08 深圳市大疆创新科技有限公司 Configuration method, physical device, server, and computer-readable storage medium
CN110413288B (en) * 2019-07-31 2023-05-09 新华三大数据技术有限公司 Application deployment method, device, server and storage medium
CN110531984B (en) * 2019-08-08 2023-06-23 金蝶软件（中国）有限公司 Code compiling method, device, system, computer equipment and storage medium
CN110609732B (en) * 2019-08-13 2023-02-07 平安普惠企业管理有限公司 Application program deployment method and device, computer equipment and storage medium
CN110704156A (en) * 2019-08-16 2020-01-17 北京奇艺世纪科技有限公司 Docker mirror image construction method and device
CN110531995B (en) * 2019-08-23 2022-06-17 济南浪潮数据技术有限公司 Management platform deployment method, device, equipment and computer readable storage medium
WO2021035553A1 (en) * 2019-08-27 2021-03-04 西门子股份公司 Application program development and deployment method and apparatus, and computer readable medium
CN110502268A (en) * 2019-08-29 2019-11-26 恩亿科(北京)数据科技有限公司 Application program update method, apparatus, server and storage medium
CN110851144B (en) * 2019-09-06 2023-09-29 北京京东尚科信息技术有限公司 Cloud host deployment method and device and computer storage medium
CN110753088B (en) * 2019-09-18 2022-10-18 平安科技（深圳）有限公司 System deployment method and device
CN112532674B (en) * 2019-09-19 2023-07-28 贵州白山云科技股份有限公司 Creation method, device and medium of network edge computing system
CN112532668B (en) * 2019-09-19 2022-08-02 贵州白山云科技股份有限公司 Network edge computing method, device and medium
CN110750242B (en) * 2019-09-19 2023-05-02 北京字节跳动网络技术有限公司 File deployment method, system, medium and electronic equipment
CN110855739B (en) * 2019-09-25 2022-11-08 烽火通信科技股份有限公司 Container technology-based remote and heterogeneous resource unified management method and system
CN110647332A (en) * 2019-09-30 2020-01-03 北京百度网讯科技有限公司 Software deployment method and device based on container cloud
CN112579099B (en) * 2019-09-30 2024-11-29 北京国双科技有限公司 Code deployment method and device, storage medium and electronic equipment
CN110780888A (en) * 2019-10-09 2020-02-11 北京市天元网络技术股份有限公司 Method for deploying cloud database
CN112650662A (en) * 2019-10-10 2021-04-13 上海哔哩哔哩科技有限公司 Test environment deployment method and device
CN110837612B (en) * 2019-11-01 2023-05-12 腾讯科技（深圳）有限公司 Uniform Resource Identifier (URI) data acquisition method and device and storage medium
CN110830571A (en) * 2019-11-05 2020-02-21 许继集团有限公司 Business data backup and extraction method and computer readable medium
CN111176782B (en) * 2019-11-08 2023-11-03 腾讯云计算（北京）有限责任公司 Online experiment method and device
CN110958138B (en) * 2019-11-14 2022-03-25 新华三大数据技术有限公司 Container expansion method and device
CN110865840B (en) * 2019-11-18 2023-11-03 义乌中国小商品城大数据有限公司 Application management method, device, server and storage medium
CN110995480B (en) * 2019-11-25 2022-09-20 百度在线网络技术（北京）有限公司 Block chain network deployment method, device, electronic equipment and medium
CN111090823B (en) * 2019-12-23 2024-02-09 广州市百果园信息技术有限公司 Page application integration system, application access method, device and equipment
CN111273965B (en) * 2020-02-17 2021-10-29 支付宝(杭州)信息技术有限公司 Container application starting method, system and device and electronic equipment
CN111399897A (en) * 2020-02-21 2020-07-10 北京值得买科技股份有限公司 Application issuing method and system based on kubernets
CN111367658B (en) * 2020-02-24 2023-05-26 广州市百果园信息技术有限公司 Live broadcast service system and process management method
CN111355793A (en) * 2020-02-26 2020-06-30 山东爱城市网信息技术有限公司 Large file uploading method based on HTML5 and Python
CN113360160B (en) * 2020-03-05 2025-07-15 北京沃东天骏信息技术有限公司 Method, device, electronic device and storage medium for deploying application
CN111385304B (en) * 2020-03-16 2022-09-30 深信服科技股份有限公司 System deployment method, device, computer storage medium and fusion system
CN111459610B (en) * 2020-03-19 2024-03-26 网宿科技股份有限公司 A model deployment method and device
CN111580926A (en) * 2020-03-25 2020-08-25 中国平安财产保险股份有限公司 Model publishing method, model deployment method, apparatus, device and storage medium
CN113296873B (en) * 2020-05-15 2024-08-06 阿里巴巴集团控股有限公司 Mirror image construction method and device, terminal equipment and computer storage medium
CN111596928B (en) * 2020-05-19 2021-08-13 吉林大学 An application control method, device and electronic device
CN111611054B (en) * 2020-05-21 2023-05-16 网宿科技股份有限公司 Application deployment method and device
CN111625222B (en) * 2020-05-26 2023-08-04 北京互金新融科技有限公司 Online verification system and method for front-end codes
CN111756804B (en) * 2020-05-27 2022-05-31 苏州浪潮智能科技有限公司 Method and device for configuring web request
CN111625320B (en) * 2020-05-27 2022-05-17 苏州浪潮智能科技有限公司 An image management method, system, device and medium
CN111736818A (en) * 2020-05-28 2020-10-02 浪潮电子信息产业股份有限公司 Application creation method, device, electronic device and storage medium based on container cloud
CN111679888B (en) * 2020-06-04 2025-01-24 深圳前海微众银行股份有限公司 A method and device for deploying a proxy container
CN111679887A (en) * 2020-06-04 2020-09-18 深圳前海微众银行股份有限公司 Method and device for configuring proxy container
CN111722866B (en) * 2020-06-19 2022-06-17 浪潮电子信息产业股份有限公司 OpenStack code repairing method, device, equipment and storage medium
CN111736956B (en) * 2020-06-29 2023-01-10 苏州浪潮智能科技有限公司 Container service deployment method, device, equipment and readable storage medium
CN111857797B (en) * 2020-06-29 2022-04-22 浪潮电子信息产业股份有限公司 Mirror image construction method, system and related device
CN111966445B (en) * 2020-06-30 2023-07-25 北京百度网讯科技有限公司 Processing method and device for invoking application program interface
CN111881470B (en) * 2020-07-20 2024-07-12 易通星云（北京）科技发展有限公司 Data access method and device and computer readable storage medium
CN113760442B (en) * 2020-10-19 2024-12-03 北京沃东天骏信息技术有限公司 A method, device and equipment for running and accessing an application
CN112379892A (en) * 2020-10-29 2021-02-19 远光软件股份有限公司 Ammonia spraying prediction code processing method and device, storage medium and terminal equipment
US12056511B2 (en) * 2020-11-09 2024-08-06 International Business Machines Corporation Container image creation and deployment using a manifest
CN112363802A (en) * 2020-11-12 2021-02-12 中国人寿保险股份有限公司 Application deployment method and device
CN114036223A (en) * 2020-11-13 2022-02-11 武汉联影医疗科技有限公司 Medical information management method, system, apparatus, computer equipment and storage medium
CN112230946B (en) * 2020-11-18 2025-02-28 浪潮云信息技术股份公司 A container-based application system deployment method and related device
CN112468337A (en) * 2020-11-19 2021-03-09 安徽江淮汽车集团股份有限公司 Deployment method, device, equipment and storage medium of Internet of vehicles microservice
CN114546434B (en) * 2020-11-26 2025-09-02 腾讯科技（深圳）有限公司 Application updating method, device, electronic device and storage medium
CN112395363B (en) * 2020-12-04 2024-03-26 北京有竹居网络技术有限公司 Data synchronization method, device, equipment and readable storage medium
CN112667998B (en) * 2020-12-08 2024-03-01 中国科学院信息工程研究所 Safe access method and system for container mirror image warehouse
CN112600931B (en) * 2020-12-22 2022-05-24 新华三云计算技术有限公司 A kind of API gateway deployment method and device
CN112667350B (en) * 2020-12-23 2024-09-27 广州三七互娱科技有限公司 Configuration scheduling method, device and system
CN112631730A (en) * 2020-12-30 2021-04-09 中国建设银行股份有限公司 Model processing method and device, equipment and computer readable storage medium
US11720345B2 (en) 2021-01-20 2023-08-08 Red Hat, Inc. Pull based inner-loop code deployment
CN112817691B (en) * 2021-01-27 2024-02-02 北京迈格威科技有限公司 Resource allocation method, device, equipment and medium
CN113760308B (en) * 2021-02-05 2025-08-19 北京沃东天骏信息技术有限公司 Method and device for constructing DSP system, electronic equipment and storage medium
CN112860645B (en) * 2021-02-09 2024-10-15 恒安嘉新（北京）科技股份公司 Processing method, device, computer equipment and medium for offline compressed file
CN112817615B (en) * 2021-02-24 2023-12-26 共达地创新技术(深圳)有限公司 File processing method, device, system and storage medium
CN114968267B (en) * 2021-02-26 2025-03-25 京东方科技集团股份有限公司 Service deployment method, device, electronic device and storage medium
CN115190034B (en) * 2021-04-07 2023-11-03 上海荟诚信息系统有限公司 Service deployment method based on edge cloud computing
CN113162944B (en) * 2021-04-29 2022-08-02 杭州安恒信息安全技术有限公司 Network communication method, device and device for security operation platform and security component
CN113238762B (en) * 2021-05-10 2024-07-02 深圳前海微众银行股份有限公司 Remote deployment method, device and equipment for java application
CN113590305B (en) * 2021-05-14 2022-12-09 西安交通大学 A deployment method of edge computing application capabilities based on k3s
CN113448686B (en) * 2021-06-22 2024-05-24 深信服科技股份有限公司 Resource deployment method and device, electronic equipment and storage medium
CN113448594B (en) * 2021-06-29 2024-06-18 京东科技控股股份有限公司 Service processing method, device, computer equipment and storage medium
CN113434254B (en) * 2021-06-30 2023-03-07 深圳平安智汇企业信息管理有限公司 Client deployment method, client deployment apparatus, computer device, and storage medium
CN113672337B (en) * 2021-07-16 2024-02-13 广东浪潮智慧计算技术有限公司 Application migration method, device, equipment and computer readable storage medium
CN113485795B (en) * 2021-07-26 2024-03-26 四川万益能源科技有限公司 Automatic container starting method based on multiple types of items
CN113596162B (en) * 2021-07-30 2024-08-02 北京快乐茄信息技术有限公司 Mirror image file processing method and device, network equipment and storage medium
CN113608872B (en) * 2021-08-05 2024-08-16 北京沃东天骏信息技术有限公司 Information processing method and device and storage medium
CN113608838A (en) * 2021-08-09 2021-11-05 吉首大学 Deployment method and device of application image file, computer equipment and storage medium
CN113590336B (en) * 2021-08-11 2024-08-06 上海仁童电子科技有限公司 Algorithm management method and device for edge computing equipment
CN114116117A (en) * 2021-08-23 2022-03-01 网宿科技股份有限公司 Service deployment method, electronic device and storage medium
CN113641373B (en) * 2021-08-30 2024-06-18 北京京东乾石科技有限公司 Mirror image deployment method, device and storage medium
CN113867778B (en) * 2021-09-18 2024-08-16 苏州浪潮智能科技有限公司 Image file generation method and device, electronic equipment and storage medium
CN114090111B (en) * 2021-10-18 2024-04-05 荣耀终端有限公司 Application starting method, device, terminal, medium and product
CN114089973B (en) * 2021-11-17 2025-05-20 抖音视界有限公司 A startup method, device, computer equipment and storage medium
CN114257413B (en) * 2021-11-19 2023-10-03 南方电网数字平台科技(广东)有限公司 Reaction blocking method and device based on application container engine and computer equipment
CN114237686B (en) * 2021-11-19 2025-05-23 北京百度网讯科技有限公司 Installation package generation method, device, electronic device and storage medium
CN114115968A (en) * 2021-11-24 2022-03-01 北京睿芯高通量科技有限公司 Operation method and device for container incremental upgrading, electronic equipment and storage medium
CN114090183B (en) * 2021-11-25 2023-07-21 抖音视界有限公司 Application starting method and device, computer equipment and storage medium
CN114116499A (en) * 2021-11-30 2022-03-01 北京百度网讯科技有限公司 Method, apparatus, device and storage medium for evaluating code quality
CN114253556A (en) * 2021-12-06 2022-03-29 青岛海尔科技有限公司 Model deployment method, identification method and device and electronic equipment
CN114168188B (en) * 2021-12-14 2025-09-09 浙江百应科技有限公司 Front-end project packaging method and device, electronic equipment and storage medium
CN114416109B (en) * 2021-12-15 2023-01-10 广州市玄武无线科技股份有限公司 Program deployment method and device, computer device, and storage medium
CN114296871B (en) * 2021-12-22 2025-08-19 华人运通(上海)云计算科技有限公司 Container-based continuous integration method, device, system, working node and medium
CN114416112B (en) * 2021-12-29 2025-02-11 中国电信股份有限公司 Project deployment method and device
CN114356426B (en) * 2022-01-05 2024-12-03 中国建设银行股份有限公司 System initialization method and related device based on agent technology
CN114385952A (en) * 2022-01-13 2022-04-22 平安壹钱包电子商务有限公司 Page function item management method and device, computer equipment and readable storage medium
CN114064155A (en) * 2022-01-17 2022-02-18 深圳市华付信息技术有限公司 Container-based algorithm calling method, device, equipment and storage medium
CN114527993A (en) * 2022-02-10 2022-05-24 富途网络科技(深圳)有限公司 Application deployment method, device, equipment and medium
CN114461399B (en) * 2022-02-11 2024-07-02 浙江大华技术股份有限公司 Resource allocation method and device, storage medium and electronic device
CN114661412B (en) * 2022-02-25 2025-08-19 北京砍石高科技有限公司 Algorithm model deployment method and device, readable medium and electronic equipment
CN114721728A (en) * 2022-03-07 2022-07-08 阿里巴巴（中国）有限公司 Processing method based on cloud application, electronic equipment and storage medium
CN114281371A (en) * 2022-03-08 2022-04-05 中电云数智科技有限公司 Front-end application deployment method and device
CN114996117B (en) * 2022-03-28 2024-02-06 湖南智擎科技有限公司 Client GPU application evaluation system and method for SaaS model
CN114817049A (en) * 2022-05-07 2022-07-29 中国工商银行股份有限公司 Bytecode acquisition method, computer equipment, storage medium and program product
CN114895922A (en) * 2022-05-10 2022-08-12 中国农业银行股份有限公司 Deployment method and device of application system and electronic equipment
CN114860307A (en) * 2022-05-28 2022-08-05 平安银行股份有限公司 Configuration method of software product and related device
CN115080420A (en) * 2022-06-27 2022-09-20 腾讯音乐娱乐科技（深圳）有限公司 A test environment deployment method and related device
CN115129359A (en) * 2022-06-28 2022-09-30 北京金山云网络技术有限公司 Method and device for deploying packaged item, storage medium and electronic equipment
CN115373727B (en) * 2022-08-08 2024-08-09 深圳安巽科技有限公司 HTTP application and background script deployment method, system and storage medium
CN115129429B (en) * 2022-09-01 2023-06-13 南京翼辉爱智物联技术有限公司 Container application management method and device, electronic equipment and storage medium
CN115828231B (en) * 2022-10-28 2024-07-02 广州汽车集团股份有限公司 Application program running method, device, vehicle and storage medium
CN115665172B (en) * 2022-10-31 2023-04-28 北京凯思昊鹏软件工程技术有限公司 Management system of embedded terminal equipment
CN116560804B (en) * 2023-07-10 2023-09-05 中国人民解放军国防科技大学 A method and device for jointly running containers using multiple container images
CN116954616A (en) * 2023-07-14 2023-10-27 魔方医药科技(苏州)有限公司 Application publishing method, device, computer equipment and computer-readable storage medium
CN116974615B (en) * 2023-09-25 2023-12-15 厦门她趣信息技术有限公司 Method, device and equipment for improving compiling and packing speed of software
CN117076431B (en) * 2023-10-13 2024-03-12 云筑信息科技(成都)有限公司 Method for migrating system upgrade data
CN117648100B (en) * 2024-01-30 2024-04-30 北京盛邦赛云科技有限公司 Application deployment method, device, equipment and storage medium
CN118860651B (en) * 2024-07-16 2025-05-30 上海迪维欧电子设备有限公司 AI application distributed container management method and system based on K8s
CN118885215B (en) * 2024-09-26 2024-11-29 北京比格大数据有限公司 Desktop application migration method and system
CN119271246B (en) * 2024-12-09 2025-02-25 中航(成都)无人机系统股份有限公司 Software warehousing method, device, equipment and storage medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105117293A (en) * 2015-09-01 2015-12-02 茂名市群英网络有限公司 Windows system environment automatic deployment method and automatic deployment system
CN107547250A (en) * 2017-06-26 2018-01-05 新华三云计算技术有限公司 The method and apparatus that database is disposed in cloud computing management platform

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7467391B2 (en) * 2002-10-30 2008-12-16 International Business Machines Corporation Allowing client applications to programmatically access web sites
US20130290542A1 (en) * 2012-04-30 2013-10-31 Racemi, Inc. Server Image Migrations Into Public and Private Cloud Infrastructures

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105117293A (en) * 2015-09-01 2015-12-02 茂名市群英网络有限公司 Windows system environment automatic deployment method and automatic deployment system
CN107547250A (en) * 2017-06-26 2018-01-05 新华三云计算技术有限公司 The method and apparatus that database is disposed in cloud computing management platform

Also Published As

Publication number Publication date
CN108958927A (en) 2018-12-07

Similar Documents

Publication Publication Date Title
CN108958927B (en) Deployment method and device of container application, computer equipment and storage medium
CN108959455B (en) Single-page Web application implementation method and device, computer equipment and storage medium
US11567755B2 (en) Integration of containers with external elements
CN106991035B (en) Host monitoring system based on micro-service architecture
US8924954B2 (en) Application software installation method and application software installation apparatus
US10284416B2 (en) Workload deployment with infrastructure management agent provisioning
KR102236522B1 (en) Method and apparatus for processing information
US20210048998A1 (en) Container-based server environments
US10305962B1 (en) Unit testing clients of web services
EP2765508A1 (en) Installation method and installation device for application software
CN108132826B (en) Image management method, device and server for cross-cloud server
US9229758B2 (en) Passive monitoring of virtual systems using extensible indexing
WO2014209359A1 (en) Hook framework
US9501344B2 (en) Data dump for a memory in a data processing system
CN112860645B (en) Processing method, device, computer equipment and medium for offline compressed file
US20130111018A1 (en) Passive monitoring of virtual systems using agent-less, offline indexing
CN105512044A (en) Method and system for updating object base used for keyword drive test
CN112068902A (en) Plug-in calling method and device, electronic equipment and storage medium
CN115129348A (en) Resource updating method, device and equipment of application program and readable storage medium
CN113595832A (en) Network data acquisition system and method
CN116225617A (en) Management migration method and device for container instance, electronic equipment and storage medium
CN109939441B (en) Application multi-disk verification processing method and system
CN114185866B (en) Data local storage control method and medical data storage system
CN115543486A (en) Cold start delay optimization method, device and equipment for serverless computing
CN118409785B (en) Application compatibility evaluation method and computing device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant