CN111857951A

CN111857951A - Containerized deployment platform and deployment method

Info

Publication number: CN111857951A
Application number: CN202010647833.2A
Authority: CN
Inventors: 黎韦
Original assignee: Haier Uplus Intelligent Technology Beijing Co Ltd
Current assignee: Haier Uplus Intelligent Technology Beijing Co Ltd
Priority date: 2020-07-07
Filing date: 2020-07-07
Publication date: 2020-10-30

Abstract

The invention provides a containerized deployment platform and a deployment method, wherein the containerized deployment platform comprises: the system comprises a container management module, a deployment object and a service management module, wherein the container management module is used for configuring resources for the deployment object, and the resources at least comprise port resources and container resources; and the container module comprises one or more containers and is used for deploying the deployment object through the container corresponding to the container resource. The invention can solve the problems of unstable system work and higher system risk caused by port conflict of the mixed deployment application in the running environment in the related technology, thereby achieving the effect of enabling the ports of the mixed deployment application in the running environment to be consistent.

Description

Containerized deployment platform and deployment method

Technical Field

The invention relates to the field of software engineering, in particular to a containerization deployment platform and a deployment method.

Background

Virtualization technology is widely used at present, and many applications are deployed on a line through a container docker in a deployment process at present. However, in order to increase the utilization rate of resources during the deployment process, it is often the case that multiple nodes of different types of applications are deployed on one server, even multiple types of applications are deployed on one server, and the like.

The above-mentioned multiple application mixed deployment mode can easily cause the port conflict in the operating environment; the phenomenon of inconsistent port allocation in the operating environment of the deployed application further causes confusion of application and port management in the operating environment, so that system work in the operating environment is not maintained, and great system risk is caused.

For the above problems of unstable system operation and high system risk caused by port conflict in the running environment of the hybrid deployment application in the related art, no effective solution has been proposed in the related art.

Disclosure of Invention

The embodiment of the invention provides a containerization deployment platform and a containerization deployment method, which are used for at least solving the problems of unstable system work and high system risk caused by port conflict of mixed deployment application in a running environment in the related technology.

According to an embodiment of the present invention, there is provided a containerized deployment platform applied to a server, the platform including:

the system comprises a container management module, a deployment object and a service management module, wherein the container management module is used for configuring resources for the deployment object, and the resources at least comprise port resources and container resources;

and the container module comprises one or more containers and is used for deploying the deployment object through the container corresponding to the container resource.

According to another embodiment of the present invention, there is also provided a deployment method applied to a server, the method including:

configuring resources for the deployment object through a container management module, wherein the resources at least comprise port resources and container resources;

and deploying the deployment object through a container corresponding to the container resource.

According to another embodiment of the present invention, a computer-readable storage medium is also provided, in which a computer program is stored, wherein the computer program is configured to perform the steps of any of the above-described method embodiments when executed.

According to another embodiment of the present invention, there is also provided an electronic device, including a memory in which a computer program is stored and a processor configured to execute the computer program to perform the steps in any of the above method embodiments.

According to the invention, resources can be configured for the deployment object through the container management module in the containerization deployment platform, wherein the resources at least comprise port resources and container resources; and enabling the container module to deploy the deployment object through the container corresponding to the container resource. In the deployment process, the corresponding port resources and container resources can be configured by the container management module by taking the container management module as a deployment object in advance, such as an application to be deployed, so that the port allocation is not required to be carried out at any stage after each application is deployed to the operating environment, and the consistent port configuration of the application is maintained; by performing the above operation on each application or each node of the application in the operating environment through the containerized deployment platform, unified management on the port resources and the container resources can be realized, so that the problem of port conflict possibly existing in the process of deploying the applications in a mixed manner is effectively avoided. Therefore, the invention can solve the problems of unstable system work and higher system risk caused by port conflict of the mixed deployment application in the running environment in the related technology, so as to achieve the effect of enabling the ports of the mixed deployment application in the running environment to be consistent.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:

FIG. 1 is a system architecture diagram of a containerized deployment platform operating system provided in accordance with an embodiment of the present invention;

FIG. 2 is a functional schematic diagram (one) of a containerized deployment platform provided in accordance with an embodiment of the present invention;

FIG. 3 is a functional diagram of a containerized deployment platform provided in accordance with an embodiment of the present invention;

FIG. 4 is a functional schematic diagram (III) of a containerized deployment platform provided in accordance with an embodiment of the present invention;

FIG. 5 is a schematic structural diagram of a containerized deployment platform provided in accordance with an embodiment of the present invention;

fig. 6 is a flowchart of a deployment method provided in accordance with an embodiment of the present invention.

Detailed Description

The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.

To further illustrate the containerized deployment platform and the deployment method in the embodiments of the present invention, an application scenario of the containerized deployment platform and the deployment method in the embodiments of the present invention is described below:

fig. 1 is a system architecture diagram of a containerized deployment platform operating system according to an embodiment of the present invention, and as shown in fig. 1, the containerized deployment platform may include a hardware layer and a software layer, which are described below.

The hardware layer may include, but is not limited to: processor 001, memory 002, hard disk 003 and network card 004. The processor 001, the memory 002, the hard disk 003 and the network card 004 can be connected through an internal connection path (for example, a bus). It should be noted that the present invention does not limit the configuration of the hardware layer, and for example, the hardware layer may be an X86 server, an advanced reduced instruction set computing (ARM) server, or a heterogeneous server.

The software layer may include an operating system 005. It should be noted that the operating system 005 is not limited in the present invention, and for example, the operating system may be a Linux operating system or a windows operating system. Operating system 005 runs on drive 006 and container 007.

Among them, the container 007 is an operating system level virtualization technology. A container is an abbreviation of container as a service (CaaS), which is a specific type of platform as a service (PaaS) service. The container technology isolates different processes through operating system isolation technologies, such as CGroup and NameSpace under Linux, so that application services and dependent items thereof can be run in one resource-isolated process. The container technology is different from hardware virtualization (hypervisor) technology, and has no virtual hardware, no operating system inside and only a process. Therefore, compared with a virtual machine, the container is lighter in weight and more convenient to manage. A container provides a virtual execution environment, which can bind a specific Central Processing Unit (CPU) and a memory node, allocate specific proportions of CPU time and input/output (IO) time, limit the size of usable memory, provide device access control, and the like. Compared with a virtual machine, the container has the characteristics of lighter weight, easier distribution, higher performance, less loss and the like.

The container is an instance created based on a container image, the container image provides programs, libraries, resources and configurations required by the container operation, does not contain any dynamic data, is a read-only special file, and the container image comprises one or more of the following information: information, applications and drivers of the user. The container image is a hierarchical structure comprising multiple layers of read-only data, including one or more of the following layers: a basic mirror layer, an application layer, a user-defined layer and the like. Multiple read-only layers can be integrated into one container mirror image by Unified File System (UFS) technology.

For a container, the instance is an object that includes the user configuration and running configuration needed to implement the functionality of the container image. The container mirror image-based container issuing may be to add a read-write layer on the basis of a read-only layer of the container mirror image, and integrate the read-write layers and the read-write layers into one container by a joint installation (UM) technology. The containers are classified into application containers and system containers according to application scenarios. The application container is mainly used for arranging and scheduling stateless applications, and the application container mirror image comprises the applications and the running environment configuration. The system container is oriented to the arrangement and scheduling of computing resources such as a CPU, a memory, a storage and the like, has a full Operating System (OS) environment, supports state application and can provide dynamic resource allocation.

The operating system 005 may have a plurality of containers 007 running thereon, each container 007 may run one sub-operating system, and the sub-operating systems running in different containers 007 may be the same or different, for example, an Android operating system.

The driver 006 may enable communication between components in the software layer and the hardware layer. Note that the driver 006 is related to the type of the operating system 005, and the operating system 005 differs and the driver 006 also differs.

It should be noted that the containerized deployment platform in the embodiment of the present invention is implemented in the system architecture, and the containerized deployment platform in the embodiment of the present invention may expand the relevant management modules in the deployment process of the container on the basis of the system architecture shown in fig. 1, so as to solve the problems of unstable system operation and high system risk caused by port conflict of the hybrid deployment application in the operating environment in the related art, so as to achieve the effect of making the ports of the hybrid deployment application in the operating environment consistent.

In the following description of the containerization deployment platform and the deployment method in the embodiments of the present invention, it should be noted that the term "module" used below may implement a combination of software and/or hardware for a predetermined function. Although the means described in the following embodiments are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated:

example 1

Fig. 2 is a functional schematic diagram (one) of a containerized deployment platform provided according to an embodiment of the present invention, and as shown in fig. 2, the containerized deployment platform in this embodiment includes:

The container management module 102 is configured to configure resources for the deployment object, where the resources at least include port resources and container resources;

the container module 104, which includes one or more containers 1042, is configured to deploy the deployment object through a container corresponding to the container resource by the container module 104.

It should be further explained that the deployment object in this embodiment is generally an application, or a certain node in the application.

With the containerized deployment platform in this embodiment, resources may be configured for the deployment object through a container management module in the containerized deployment platform, where the resources at least include port resources and container resources; and enabling the container module to deploy the deployment object through the container corresponding to the container resource. In the deployment process of the containerized deployment platform in this embodiment, the container management module may configure corresponding port resources and container resources for a deployment object in advance, such as an application to be deployed, so that each application does not need to allocate ports at any stage after being deployed to an operating environment, thereby maintaining consistent port configuration for the application; by performing the above operations on each application or each node of the application in the operating environment through the containerized deployment platform, unified management on the port resources and the container resources can be realized, so as to effectively avoid the port conflict problem possibly existing in the process of hybrid deployment of the application, and further solve the problems of unstable system work and high system risk caused by the port conflict of the hybrid deployment application in the operating environment in the related art, so as to achieve the effect of making the ports of the hybrid deployment application in the operating environment consistent, and ensure the port uniformity and the dimensional stability of the application nodes.

In an optional embodiment, the container management module 102 is further configured to:

determining the state of a port in a server, wherein the state of the port comprises an occupied port and an idle port;

and allocating idle ports as port resources of the deployment object for the deployment object according to a preset sequence.

It should be further explained that, in the optional embodiment, during the process of configuring the port resource, the container management module may first determine an occupation situation of the port in the server, identify an idle port in an idle state according to the state of the port, and then use the idle port as the port resource of the deployment object according to a preset sequence to allocate to the deployment object. The preset sequence may be a label sequence of the ports, or other assignment sequences, which is not limited in the present invention. The following is illustrated by specific examples:

the port section of the server is set to 10000 to 20000, and two ports are needed when a certain application is deployed. When the container management module detects that all the ports are idle, that is, each port is an idle port, the port 10000 and the next port 100001 may be allocated to the currently deployed application according to the label sequence of the ports, that is, the port 10000 and the next port 100001 may be used as the port resources of the application. When the container management module detects that the port 10000 is occupied by other applications or objects, the port is skipped, and the port 10001 and the port 100002 are used as port resources of the currently deployed application, and so on. And at any stage after the deployed application is deployed to the operating environment, the port resource determined by the container management module is used as the port of the deployed application. Therefore, no matter how many types of deployment objects are deployed by the containerized deployment platform in this embodiment, the port resources determined by the container management module are used as the ports of the containerized deployment platform in the subsequent stage, and the ports determined by the containerized deployment platform are determined according to whether the current port is idle, so that the port resources among different deployment objects are different, and possible port conflicts are effectively avoided.

and configuring container resources for the deployment object according to the preset technology stack type of the deployment object.

In an alternative embodiment, fig. 3 is a functional schematic diagram (two) of a containerized deployment platform provided according to an embodiment of the present invention, and as shown in fig. 3, the containerized deployment platform in this embodiment further includes:

the platform management module 106 is used for managing resources, services and permissions of the server and the containerized deployment platform;

a configuration module 108, configured to configure the deployment object;

a monitoring module 110, configured to monitor an operating state of the deployment object;

and the storage module 112 is used for storing the running logs of the server and the containerized deployment platform.

It should be further noted that, in the above optional embodiment, the platform management module may serve as an entrance of the containerized deployment platform in this embodiment, so as to perform unified management on the resources, services, rights, and the like of the server and the containerized deployment platform.

It should be further explained that, the monitoring module may deploy an Agent unit in the containerized deployment platform in this embodiment, and collect, by the Agent unit, corresponding data in the running process of the deployment object, specifically, collect data of a container on a host of the container corresponding to the deployment object. The monitoring module may be implemented by tools such as DockerStats, CAdvisor, Scout, and the like, which is not limited in the present invention.

In an alternative embodiment, the platform management module 106 is further configured to,

registering a deployment object and determining information of the deployment object; wherein the information of the deployment object comprises at least one of: type of the deployment object, code of the deployment object, version of the deployment object.

It should be further noted that, in the above optional embodiment, the platform management module may register the deployment object before the deployment object is deployed and resource configuration is performed, so as to record the relevant information of the deployment object in the platform, thereby implementing unified management on the deployment object.

and under the condition that the first service in the deployment object calls the second service in the deployment object abnormally, the first service calls the third service in the deployment object in the platform management module according to a preset sequence.

It should be further noted that, in the above-mentioned alternative embodiment, the first service, the second service, and the third service are respectively used for indicating any three different services in the deployment object (the second service and the third service generally have the same service type); in the case that the first service in the deployment object calls the second service in the deployment object, for example, the second service in the deployment object fails and cannot be called, since the related information of the deployment object is registered in the platform management module, the platform management module may call, according to a preset order, for example, a sorting order of different types of services, the third service in the deployment object to replace the second service and be called by the first service. Through the technical scheme described in the optional embodiment, the system stability in the operation process of the deployment object can be further improved.

In an alternative embodiment, fig. 4 is a functional schematic diagram (three) of a containerized deployment platform provided according to an embodiment of the present invention, and as shown in fig. 4, the containerized deployment platform in this embodiment further includes:

a Continuous Integration (CI)/Continuous Deployment (CD) module 114, configured to send a Deployment object registered in the platform management module to the repository module;

a warehouse module 116 for managing the container modules; the warehouse module is further configured to determine, from the container resources, a corresponding container for deploying the deployment object;

an Elastic Computing Service (ECS)/Elastic computing cloud (EC 2) module 118 for providing computing resources for the containerized deployment platform.

In an optional embodiment, the monitoring module 110 is further configured to monitor the operation status of the container module, the ECS/EC2 module and the deployment object through the Agent unit.

The CI/CD module can realize the CI function and the CD function; the CI function can continuously submit and integrate the construction or modification of the deployment object, such as correspondingly updated code, by the deployment personnel in the deployment object; the CD function can deploy the integrated deployment object in a class production environment on the basis of the CI, test and verify the deployment object through a test tool, and deploy the deployment object to the platform after confirming that no error exists. The CI/CD module may be implemented by tools such as Drone, gillab-CI, Jenkins, etc., which are not limited in the present invention.

The warehouse module can manage the container module, and specifically, the warehouse module generates a corresponding image file from the deployment object through storage and sends the image file to the container module to create a corresponding container. The warehouse module comprises a plurality of warehouses and a warehouse server, each warehouse is used for storing a type of mirror image, and the warehouse server is used for managing one or more warehouses. The warehouse in this embodiment may be a public warehouse or a private warehouse, which is not limited in this disclosure.

The ECS/EC2 module may be implemented by a cloud computing platform to integrate physical resources with different structures into a logical resource pool for use, and the ECS/EC2 module may be implemented by using tools such as Amazon EC2, gotrid xen, and Citrix. Through the ECS/EC2 module, computer processing resources, memory resources, storage resources, network resources and the like can be rapidly expanded or reduced in the container deployment process, so that the requirements of different stages or different deployment objects in the container deployment process are met, and the capacity plan and the engineering design of the consumption peak in the container deployment process are adapted.

The ECS/EC2 module may be controlled by the monitoring module, that is, the ECS/EC2 module adjusts the computer processing resources, memory resources, storage resources, network resources, and the like in real time according to the running state of the deployment object monitored by the monitoring module, so that the allocated resource amount may be matched with the actually required resource amount without interrupting the operation.

Fig. 5 is a schematic structural diagram of a containerized deployment platform provided according to an embodiment of the present invention, where the structure of each module in the containerized deployment platform is shown in fig. 5; by the containerization deployment platform formed by the modules described in this embodiment and each optional embodiment, a unified state and node management are formed for deployment objects, such as applications, and further, the instability of the system in the operating environment and possible system risks can be greatly reduced.

On the basis, the containerized deployment platform supports mixed deployment of traditional applications and containerized applications, can reduce writing of deployment scripts, and is convenient for expanding the number of nodes of the application container. The operation of the containerized deployment platform of this embodiment is further described below by way of specific embodiments:

DETAILED DESCRIPTION OF EMBODIMENT (S) OF INVENTION

In this embodiment, development of a dubbo-based interface application is taken as an example.

And S1, registering the application A through the platform management module, and determining relevant information such as application types, application codes, application versions and the like which need to be confirmed when the registered application is developed.

S2, after the development is completed, the configuration of the application A is completed through the configuration module, and the submitted code of the application A is integrated through the CI function in the CI/CD module; and packages the application A to a test environment for testing through the CD function in the CI/CD module.

And S3, after the test is finished, the application A is issued to the warehouse module through the CD function in the CI/CD module, and meanwhile, the production configuration is issued in the configuration module.

And S4, issuing a production release application and confirming the number of online copies.

S5, deployment is carried out on the application, and operation and maintenance personnel can send instructions to the container management module to enable the container management platform to receive the instructions and automatically determine resource configuration including port resources and container resources for the application according to the instructions.

The port segment of the server is set to 10000 to 20000, and the application a is set to use a plurality of ports. When the container management module detects that each port is idle in the port segments 10000 to 20000, the port 10000 can be allocated to the currently deployed application a according to the label sequence of the port, that is, the port 10000 and the next port 100001 are used as the port resources of the application a. And after the allocation of the port resources and the container resources is completed, instantiating a deployment script for the application A.

S6, the container management module sends a deployment instruction to the target server.

S7, the target server receives the deployment script, downloads the container, downloads the application A, pulls the configuration and starts the application; the target server is provided with computing resources by the ECS/EC2 module.

And S8, the monitoring module monitors the running of the application A through the Agent unit discovery application.

And S9, registering the application B through the platform management module, and determining relevant information such as application types, application codes, application versions and the like which need to be confirmed when the registered application is developed.

S10, after the development is completed, the configuration of the application B is completed through the configuration module, and the submitted code of the application B is integrated through the CI function in the CI/CD module; and packages the application B to a test environment for testing through the CD function in the CI/CD module.

And S11, after the test is finished, the application B is issued to the warehouse module through the CD function in the CI/CD module, and meanwhile, the production configuration is issued in the configuration module.

And S12, issuing a production release application and confirming the number of online copies.

S13, deployment is carried out on the application, and operation and maintenance personnel can send instructions to the container management module to enable the container management platform to receive the instructions and automatically determine resource configuration including port resources and container resources for the application according to the instructions.

Setting the application B requires a large number of ports. When the container management module detects that the port 10000 to the port 10001 are occupied by the application a in the port segments 10000 to 20000, the port 10000 and the port 10001 are skipped over to allocate the currently deployed application B from the port 10002, that is, the port 10002 and the next port 100003 are used as the port resources of the application B. And after the allocation of the port resources and the container resources is completed, instantiating a deployment script for the application B.

S14, the container management module sends a deployment instruction to the target server.

S15, the target server receives the deployment script, downloads the container, downloads the application B, pulls the configuration and starts the application; the target server is provided with computing resources by the ECS/EC2 module.

And S16, the monitoring module monitors the running of the application A and the application B through Agent unit discovery application.

It should be noted that, the modules in this embodiment may be implemented by software or hardware, and for the latter, the following may be implemented, but is not limited to this: the modules are all positioned in the same processor; alternatively, the modules are respectively located in different processors in any combination.

Example 2

The present embodiment provides a deployment method applied to a server, and fig. 6 is a flowchart of a deployment method provided according to an embodiment of the present invention, as shown in fig. 6, the deployment method in the present embodiment includes:

s202, configuring resources for the deployment object through a container management module, wherein the resources at least comprise port resources and container resources;

and S204, deploying the deployment object through the container corresponding to the container resource.

It should be further explained that the remaining optional embodiments and technical effects in this embodiment all correspond to the deployment method described in embodiment 1, and therefore, no further description is given here.

In an optional embodiment, in step S202, configuring, by the container management module, a resource for the deployment object includes:

In an optional embodiment, the deployment method in this embodiment further includes:

managing resources, services and permissions of the server and the containerized deployment platform through a platform management module;

configuring the deployment object through a configuration module;

monitoring the running state of the deployment object through a monitoring module;

and storing the running logs of the server and the containerized deployment platform through the storage module.

In an optional embodiment, the managing resources, services, and permissions of the server and the containerized deployment platform by the platform management module further includes:

registering a deployment object through a platform management module, and determining the information of the deployment object; wherein the information of the deployment object comprises at least one of: type of the deployment object, code of the deployment object, version of the deployment object.

In an optional embodiment, the registering, by the platform management module, the deployment object and determining the information of the deployment object further include:

the deployment object registered in the platform management module is sent to the warehouse module through the CI/CD module;

managing the container module through a warehouse module, and determining a corresponding container for deploying the deployment object according to the container resource;

computing resources are provided for the containerized deployment platform by the ECS/EC2 module.

In an optional embodiment, the monitoring the operating state of the deployment object by the monitoring module further includes: the running states of the container module, the ECS/EC2 module and the deployment object are monitored by the Agent unit.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.

Example 3

Embodiments of the present invention also provide a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to perform the steps of any of the above-mentioned method embodiments when executed.

Alternatively, in the present embodiment, the computer-readable storage medium may be configured to store a computer program for executing the computer program in the above-described embodiment.

Optionally, in this embodiment, the computer-readable storage medium may include, but is not limited to: various media capable of storing computer programs, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.

Example 4

Embodiments of the present invention also provide an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the steps of any of the above method embodiments.

Optionally, the electronic apparatus may further include a transmission device and an input/output device, wherein the transmission device is connected to the processor, and the input/output device is connected to the processor.

Alternatively, in this embodiment, the processor may be configured to execute the steps in the above embodiments through a computer program.

Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation manners, and this embodiment is not described herein again.

It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A containerized deployment platform for use with a server, the platform comprising:

2. The platform of claim 1, wherein the container management module is further to:

and distributing the idle ports as the port resources of the deployment object according to a preset sequence for the deployment object.

3. The platform of claim 1, wherein the container management module is further to:

and configuring the container resource for the deployment object according to the preset technology stack type of the deployment object.

4. A platform as claimed in any one of claims 1 to 3, further comprising:

the platform management module is used for managing resources, services and permissions of the server and the containerized deployment platform;

The configuration module is used for configuring the deployment object;

the monitoring module is used for monitoring the running state of the deployment object;

and the storage module is used for storing the running logs of the server and the containerized deployment platform.

5. The platform of claim 4, wherein the platform management module is further to,

registering the deployment object and determining the information of the deployment object; wherein the information of the deployment object comprises at least one of: a type of the deployment object, a code of the deployment object, a version of the deployment object.

6. The platform of claim 5, wherein the platform management module is further to,

and under the condition that the first service in the deployment object calls the second service in the deployment object and the exception exists, the first service calls a third service in the deployment object in the platform management module according to a preset sequence.

7. The platform of claim 5, further comprising:

the continuous integration CI/continuous deployment CD module is used for sending the deployment object registered in the platform management module to the warehouse module;

The warehouse module is used for managing the container module; the warehouse module is further configured to determine, from the container resources, the corresponding containers for deploying the deployment objects;

an Elastic Computing Service (ECS)/elastic computing cloud (EC 2) module for providing computing resources for the containerized deployment platform.

8. The platform of claim 5, wherein the monitoring module is further configured to monitor the operational status of the container module, the ECS/EC2 module, and the deployment object via a proxy Agent unit.

9. A method for deployment, applied to a server, the method comprising:

10. The method of claim 9, wherein configuring resources for the deployment object via the container management module comprises:

11. The method of claim 9, wherein configuring resources for the deployment object via the container management module comprises:

12. A computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to carry out the method of any one of claims 9 to 11 when executed.

13. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, and wherein the processor is arranged to execute the computer program to perform the method of any of claims 9 to 11.