CN112084008B - Method for rapidly deploying cloud pipe system based on container technology - Google Patents
Method for rapidly deploying cloud pipe system based on container technology Download PDFInfo
- Publication number
- CN112084008B CN112084008B CN202010950090.6A CN202010950090A CN112084008B CN 112084008 B CN112084008 B CN 112084008B CN 202010950090 A CN202010950090 A CN 202010950090A CN 112084008 B CN112084008 B CN 112084008B
- Authority
- CN
- China
- Prior art keywords
- program
- service
- version
- code
- container
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 238000005516 engineering process Methods 0.000 title claims abstract description 18
- 238000007726 management method Methods 0.000 claims abstract description 79
- 238000004519 manufacturing process Methods 0.000 claims abstract description 7
- 238000013507 mapping Methods 0.000 claims abstract description 6
- 238000002347 injection Methods 0.000 claims description 12
- 239000007924 injection Substances 0.000 claims description 12
- 230000008569 process Effects 0.000 claims description 11
- 238000012360 testing method Methods 0.000 claims description 11
- 238000010276 construction Methods 0.000 claims description 9
- 230000001419 dependent effect Effects 0.000 claims description 9
- 238000003032 molecular docking Methods 0.000 claims description 7
- 238000013439 planning Methods 0.000 claims description 6
- 238000012795 verification Methods 0.000 claims description 6
- 230000000694 effects Effects 0.000 claims description 4
- 238000004806 packaging method and process Methods 0.000 claims description 4
- 230000003044 adaptive effect Effects 0.000 claims description 3
- 238000009826 distribution Methods 0.000 claims description 3
- 230000003993 interaction Effects 0.000 claims description 3
- 238000011177 media preparation Methods 0.000 claims description 3
- 238000004886 process control Methods 0.000 claims description 3
- 230000009466 transformation Effects 0.000 claims description 3
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000012423 maintenance Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000012384 transportation and delivery Methods 0.000 description 2
- 238000013024 troubleshooting Methods 0.000 description 2
- 241000109539 Conchita Species 0.000 description 1
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method for rapidly deploying a cloud pipe system based on a container technology, which relates to the technical field of containers and comprises the following implementation contents: s1, splitting a code program of a cloud management system into atomic service according to three types of a front-end program, a middleware program and a back-end program; s2, respectively manufacturing the split atomic services into independently operated container mirror images; s3, the number of copies started by the container is adopted by each type of atomic service, and a double-active load deployment mode of the service components is realized; and S4, recording the mapping relation between the code version of each type of atomic service and the attribute information in the mirror image, realizing the standardization of the version management of the cloud management system, uploading the container mirror image corresponding to the version management system to a physical machine to be deployed, and deploying the cloud management system. The method can shorten the deployment period and realize the high-availability HA function of the atomic service mode.
Description
Technical Field
The invention relates to the technical field of containers, in particular to a method for rapidly deploying a cloud pipe system based on a container technology.
Background
In a government affair cloud project, in order to provide management service for customers, a cloud management system is required to be deployed at the upper layer of a cloud platform, the cloud management system comprises management functions of a full-flow life cycle such as resource opening, resource monitoring, resource changing, resource destroying and the like, and is generally deployed in a platform management area of a cloud center, so that resource objects of physical resources, platform resources, virtual resources and the like of a government affair outer network area and an internet area in the network area can be simultaneously managed, and the customers can perform operation management of resource application, resource changing, resource deleting, resource monitoring and the like on a unified console management system. Since each government affair cloud project needs to be provided with one cloud management system, the workload of the deployment task is large. In the face of such a large number of deployment tasks of the cloud management system, how to simplify the deployment link and quickly complete the workload of system deployment is an urgent problem to be solved and processed.
At present, a manner of deploying a cloud management platform system by a plurality of government affair cloud projects is comprehensively researched, and in a deployment stage, deployment operations of the following links are manually executed:
(1) Initializing a node basic environment, installing database service, installing tomcat component service and the like;
(2) Program start of tomcat service is done manually using commands;
(3) the configuration of the ip address before the normal starting of the tomcat service program is completed by manually modifying address parameters;
(4) After the tomcat service is started, the API docking of the management platform and the virtualization platform is completed by manually modifying the fields of the database;
(5) The joint debugging test verification among all functional components of the platform is the verification of the joint debugging test completed by using a postman tool manually;
(6) Modifying a configuration file corresponding to the functional component;
(7) The database initializes the modification of the value of the fields of the table.
The deployment time during manual execution is long, problem troubleshooting work caused by misoperation is easy to occur, the time and labor cost consumed by the problem troubleshooting work are high, and the problem that deployment progress is delayed due to wrong configuration is easy to occur.
Disclosure of Invention
Aiming at the requirements and the defects of the prior art development, the invention provides a method for rapidly deploying a cloud management system based on a container technology.
The invention discloses a method for rapidly deploying a cloud pipe system based on a container technology, which adopts the following technical scheme for solving the technical problems:
a method for rapidly deploying a cloud management system based on container technology comprises the following steps:
s1, according to three types of a front-end program, a middleware program and a back-end program, splitting an atomic service for a code program of a cloud management system,
s2, respectively manufacturing the split atomic services into independently operated container mirror images,
s3, adopting the copy quantity started by the container for each type of atomic service to realize the double-activity load deployment mode of the service components,
and S4, recording the mapping relation between the code version of each type of atomic service and the attribute information in the mirror image, realizing the standardization of the version management of the cloud management system, uploading the container mirror image corresponding to the version management system to a physical machine needing to be deployed, and deploying the cloud management system.
Optionally, the front-end program is used to start the front-end web program, and the number of copies of the front-end program is set to 2;
the middleware program comprises a DB service program and a rabbitmq service program, and the copy number of the DB service program is set to be 3;
the back-end program comprises an interface program, an acquisition service program, a timing task service program, a task scheduling service program, a supervision and docking service program and an alarm service program, wherein the number of copies of the back-end program is set to be 2, the number of copies of the interface program is set to be 2, the number of copies of the acquisition service program is set to be 2, the number of copies of the timing task service program is set to be 2, the number of copies of the task scheduling service program is set to be 2, the number of copies of the supervision and docking service program is set to be 2, and the number of copies of the alarm service program is set to be 3.
Further, step S2 is executed, the split atomic service is made into an independently operating container mirror image, and the specific operation flow is as follows:
s2.1, starting a container: selecting an adaptive version of the operating system environment;
s2.2, starting service: after a container of the basic mirror image is started, logging in the container, and executing copying and standardized starting work of a program;
s2.3, standardization treatment: program debugging and file configuration are carried out in the container, so that the aims of standardization and immobilization are achieved;
s2.4, service checking and verification: for a program started in the container, checking and verifying operation called by an interface is carried out from the outside;
s2.5, mirror image transformation: and performing mirror image production on the container started by the container mirror image warehouse and the formed fixed configuration and standard program by using the command operation of the container, outputting and storing to form a fixed container mirror image, naming according to requirements, and storing and archiving for subsequent use.
Further, step S4 is executed, a mapping relationship between the code version of each type of atomic service and the attribute information in the mirror image is recorded, so as to realize standardization of version management of the cloud management system, and the specific operation flow is as follows:
s4.1, logging in a management tool git: through the code path: "{ { gitlab. Address } }/gcp/atomic service name.git";
s4.2, downloading version codes: logging in a git warehouse, inquiring the version number required to be used according to the requirement, and downloading the full code file of the corresponding version;
s4.3, initializing a template file: the injection operation of the basic parameters is carried out according to the environment of the actual site, and comprises the following steps: IP address planning, node role, network vlan information injection and initialization configuration;
s4.4, constructing a code: according to the initialized template, executing the construction of a version code;
s4.5, program packaging: downloading a main program package and a dependent program package according to the constructed codes and version numbers, and completing program packaging operation;
s4.6, uploading a program: and transmitting the packaged program tar packet to a project environment, and executing a version deployment task by using a mirror image file in a supporting medium.
Further, in the process of executing steps S1-S4, for different types of requirements, the code programs related to different atomic services may be modified, and after the code programs related to the atomic services are modified, the internal start-related functions related to the atomic services of the modified code programs and the functions of mutual call interaction between the atomic services are verified through testing.
Furthermore, after the code program related to the atomic service is tested, only the version management information of the atomic service related to the modified code program needs to be updated, and after the atomic service is modified, only the operation of version upgrading needs to be performed on the atomic service.
Furthermore, after testing the code program related to the atomic service, only the version management information of the atomic service related to the modified code program needs to be updated, and the specific operation flow is as follows:
a.1, downloading codes: logging in a git warehouse, inquiring a version number required to be used according to requirements, and downloading an incremental code file of a corresponding version;
a.2, template file initialization: the injection operation of the basic parameters is carried out according to the environment of the actual site, and comprises the following steps: IP address planning, node role, network vlan information injection and initialization configuration;
a.3, constructing a code: inquiring the code branch version number of the increment according to the initialized template, and executing the construction of the corresponding increment version code;
and a.4, program packaging: downloading a main program package and a dependent program package according to the constructed code and the incremental version number to be upgraded, and completing program packaging operation;
a.5, uploading a program: and transmitting the packaged program tar packet to a project environment, and executing an incremental version upgrading deployment task by using a mirror image file in a supporting medium.
Further, step S4 is executed to deploy the cloud management system, and the specific operation flow is as follows:
s4.A.1, preparing a node: 2, preparing physical machine servers, installing an operating system, and configuring a required network according to requirements;
s4.A.2, medium preparation: transmitting an image file required by the operation of the program container to a medium and transmitting the image file to 1 physical server of the project environment;
s4.A.3, template initialization: pulling the template of the deployment file from the environment center warehouse, and completing the configuration of the initialized network address and the node distribution role of the template according to the relevant actual information of the environment center
S4.A.4, constructing an execution code: inquiring a code branch version number according to the initialized template, and executing construction of a corresponding version code;
s4.A.5, packaging a code program: downloading a main program package and a dependent program package according to the constructed code and the version number to be deployed, and completing program packaging operation;
s4.A.6, uploading a deployment program: transmitting the packaged program tar packet to a project environment, and executing a version upgrading deployment task by using a mirror image file in a matching medium;
s4.A.7, deployment process control: tracking the process state of the deployment task through the log of the container, and checking a deployment result through the log;
s4.A.8, generating a deployment report: after the deployment task is completed, a service program for deployment check is started, the deployed cloud management system is subjected to deployment check, including version information check, service availability check and environment parameter check, and after the check is completed, a deployment report is generated.
Further preferably, after the deployment program is uploaded, the deployment program does not need to use one node independently and can be multiplexed with other nodes.
Further preferably, after the cloud management system is deployed, an administrator account admin may be used to log in and check the availability of the interface, and the administrator account may also be configured with authority to perform account management and allocation for operators with different roles.
Compared with the prior art, the method for rapidly deploying the cloud pipe system based on the container technology has the following beneficial effects:
1) On one hand, the method and the system perform atomic service splitting on a code program of the cloud management system, and respectively manufacture the split atomic services into independently-operated container mirror images, so that the configuration of an initialization program and parameters is fixed in the container-started mirror image, the parameters and the management service program do not need to be manually configured again, and the deployment period is greatly shortened; on the other hand, the invention adopts the copy number started by the container for each type of atomic service to realize the dual-active load deployment mode of the service components, when one service program in the running of the cloud management system cannot provide the service because of service interruption caused by faults, the other copy of the service program can continue to provide the service, and the high-availability HA function of the atomic service mode is realized; when a local code program of the cloud management system is modified, in the deployment process, testing and verification are not needed to be carried out on other code programs, the testing range is reduced, the atomic service related to the modified code can be verified more importantly, the processing link of the whole program replacement upgrading operation caused by code change is greatly improved, the workload brought by version upgrading is reduced, the delivery efficiency of the cloud management system operation and maintenance upgrading version is improved, the subsequent upgrading process is more flexible, and the upgrading and deployment operation is simpler.
Drawings
Fig. 1 is a schematic structural diagram of a cloud management system according to a first embodiment of the present invention after a code program is split into atomic services;
FIG. 2 is a flow chart illustrating operations for creating a container mirror image according to a first embodiment of the present invention;
fig. 3 is an operation flowchart for implementing standardization of version management of a cloud management system in the first embodiment of the present invention;
FIG. 4 is a flowchart illustrating operation of cloud management system deployment according to an embodiment of the present invention;
fig. 5 is a flowchart of an operation of version upgrade of an atomic service according to an embodiment of the present invention.
Detailed Description
In order to make the technical scheme, the technical problems to be solved and the technical effects of the present invention more clearly apparent, the following technical scheme of the present invention is clearly and completely described with reference to the specific embodiments.
The first embodiment is as follows:
the embodiment provides a method for rapidly deploying a cloud management system based on a container technology, which includes the following implementation contents:
s1, performing atomic service splitting on a code program of the cloud management system according to three types of a front-end program, a middleware program and a back-end program.
With reference to fig. 1, in this embodiment, the front-end program gcp-front is used to start the front-end web program, the middleware program includes gcp-DB service program and rabbitmq service program, and the back-end program gcp-service includes interface program gcp-interface, collection service program gcp-collect, timing task service program gcp-timer, task scheduling service program gcp-scheduler, supervisory docking service program gcp-monitor, and alarm service program gcp-alert.
Step S2, the split atomic services are respectively made into independently operated container mirror images, and the specific operation flow is as follows in combination with the attached figure 2:
s2.1, starting a container: selecting an operating system environment with an adaptive version, which is generally centros 7.X or ubuntu18.X, and is a fixed basic operating system image in a docker container image warehouse;
s2.2, starting service: after the container of the basic mirror image is started, logging in the container, and executing copying and standardized starting work of a program;
s2.3, standardization treatment: program debugging and file configuration are carried out in the container, so that the aims of standardization and immobilization are achieved;
s2.4, service checking and verification: for a program started in the container, checking and verifying operation called by an interface is performed from the outside;
s2.5, mirror image transformation: and performing mirror image production on the container started by the container mirror image warehouse and the formed fixed configuration and standard program by using the command operation of the container, outputting and storing to form a fixed container mirror image, naming according to requirements, and storing and archiving for subsequent use.
And S3, adopting the copy quantity started by the container for each type of atomic service to realize the double-activity load deployment mode of the service components.
In this embodiment, the number of copies of the front-end program gcp-front is set to 2, the number of copies of the gcp-DB service program is set to 3, the number of copies of the back-end program gcp-service is set to 2, the number of copies of the interface program gcp-interface is set to 2, the number of copies of the collection service program gcp-collect is set to 2, the number of copies of the timed task service program gcp-timer is set to 2, the number of copies of the task scheduling service program gcp-scheduler is set to 2, the number of copies of the supervisory docking service program gcp-monitor is set to 2, and the number of copies of the alarm service program gcp-alert is set to 3.
And S4, recording the mapping relation between the code version of each type of atomic service and the attribute information in the mirror image, realizing the standardization of the version management of the cloud management system, uploading the container mirror image corresponding to the version management system to a physical machine needing to be deployed, and deploying the cloud management system.
In this step, standardization of cloud management system version management is realized, and with reference to fig. 3, the specific operation flow is as follows:
s4.1, logging in a management tool git: through the code path: "{ { gitlab. Address } }/gcp/atomic service name.git";
s4.2, downloading version codes: logging in a git warehouse, inquiring the version number required to be used according to the requirement, and downloading the full code file of the corresponding version;
s4.3, template file initialization: the injection operation of the basic parameters is carried out according to the environment of the actual site, and comprises the following steps: IP address planning, node role, network vlan information injection and initialization configuration;
s4.4, constructing a code: according to the initialized template, executing the construction of a version code;
s4.5, program packaging: downloading a main program package and a dependent program package according to the constructed codes and version numbers, and completing program packaging operation;
s4.6, uploading a program: and transmitting the packaged program tar packet to a project environment, and executing a version deployment task by using a mirror image file in a supporting medium.
In this step, the cloud management system is deployed, and with reference to fig. 4, the specific operation flow is as follows:
s4.A.1, preparing a node: preparing 2 physical machine servers, installing an operating system, and configuring a required network according to requirements;
s4.A.2, medium preparation: transmitting an image file required by the operation of the program container to a medium and transmitting the image file to 1 physical server of the project environment;
s4.A.3, template initialization: pulling the template of the deployment file from the environment center warehouse, and completing the configuration of the initialized network address and the node distribution role of the template according to the relevant actual information of the environment center
S4.A.4, constructing an execution code: inquiring a code branch version number according to the initialized template, and executing construction of a corresponding version code;
s4.A.5, packaging code programs: downloading a main program package and a dependent program package according to the constructed code and the version number to be deployed, and finishing the program packaging operation;
s4.A.6, uploading a deployment program: transmitting the packaged program tar packet to a project environment, and executing a version upgrading deployment task by using a mirror image file in a matching medium;
s4.A.7, deployment process control: tracking the process state of the deployment task through the log of the container, and checking the deployment result through the log;
s4.A.8, generating a deployment report: after the deployment task is completed, a service program for deployment check is started, the deployed cloud management system is subjected to deployment check, including version information check, service availability check and environment parameter check, and after the check is completed, a deployment report is generated.
In the above steps, after the deployment program is uploaded, the deployment program does not need to use one node alone, and can be multiplexed with other nodes.
In this embodiment, in the process of executing steps S1 to S4, for different types of requirements, code programs related to different atomic services may be modified, and after the code programs related to the atomic services are modified, functions related to internal start of the modified code programs related to the atomic services and functions related to mutual call interaction between the atomic services are verified through testing. After testing the code program related to the atomic service, only the version management information of the atomic service related to the modified code program needs to be updated, and after modification, only the operation of version upgrade needs to be performed on the atomic service. With reference to fig. 5, the specific operation flow is as follows:
a.1, downloading codes: logging in a git warehouse, inquiring a version number required to be used according to requirements, and downloading an incremental code file of a corresponding version;
a.2, template file initialization: the injection operation of the basic parameters is carried out according to the environment of the actual site, which comprises the following steps: IP address planning, node role, network vlan information injection and initialization configuration;
a.3, constructing a code: inquiring the code branch version number of the increment according to the initialized template, and executing the construction of the corresponding increment version code;
and a.4, program packaging: downloading a main program package and a dependent program package according to the constructed code and the incremental version number to be upgraded, and completing program packaging operation;
a.5, uploading a program: and transmitting the packaged program tar packet to a project environment, and executing an incremental version upgrading deployment task by using a mirror image file in a supporting medium.
In this embodiment, after the deployment of the cloud management system is completed by adopting the steps S1 to S4, an administrator account admin may be used to log in, check the availability of the interface, and also use the authority configuration to perform account management and allocation for operators with different roles.
In conclusion, by adopting the method for rapidly deploying the cloud management system based on the container technology, on one hand, parameters and management service programs do not need to be manually configured, so that the deployment period is greatly shortened, on the other hand, when a local code program of the cloud management system is modified, other code programs do not need to be tested and verified in the deployment process, the test range is shortened, and the delivery efficiency of the operation, maintenance and upgrading version of the cloud management system is improved.
The principles and embodiments of the present invention have been described in detail using specific examples, which are provided only to aid in understanding the core technical content of the present invention. Based on the above embodiments of the present invention, those skilled in the art should make any improvements and modifications to the present invention without departing from the principle of the present invention, and all such modifications and modifications should fall within the scope of the present invention.
Claims (9)
1. A method for rapidly deploying a cloud management system based on a container technology is characterized by comprising the following steps:
s1, according to three types of a front-end program, a middleware program and a back-end program, splitting a code program of a cloud management system into atomic service;
s2, respectively manufacturing the split atomic services into independently operated container mirror images;
s3, adopting the copy quantity started by the container for each type of atomic service to realize a load deployment mode of double activities of the service components;
s4, recording the mapping relation between the code version of each type of atomic service and the attribute information in the mirror image, realizing the standardization of the version management of the cloud management system, uploading the container mirror image corresponding to the mapping relation to a physical machine needing to be deployed, and deploying the cloud management system, wherein in the process, the specific operation flow for realizing the standardization of the version management of the cloud management system is as follows:
s4.1, logging in a management tool git: through the code path: "{ { gitlab. Address } }/gcp/atomic service name. Git",
s4.2, downloading version codes: logging in a git warehouse, inquiring the version number required to be used according to the requirement, downloading the full code file of the corresponding version,
s4.3, template file initialization: the injection operation of the basic parameters is carried out according to the environment of the actual site, which comprises the following steps: IP address planning, node role, network vlan information injection and initialization configuration,
s4.4, constructing a code: according to the initialized template, executing the construction of version code,
s4.5, packaging programs: the main program package and the dependent program package are downloaded according to the constructed codes and version numbers, and the program packaging operation is completed,
s4.6, uploading a program: and transmitting the packaged program tar packet to a project environment, and executing a version deployment task by using a mirror image file in a supporting medium.
2. The method for rapidly deploying the cloud management system based on the container technology according to claim 1, wherein the front-end program is used for starting a front-end web program, and the number of copies of the front-end program is set to be 2;
the middleware program comprises a DB service program and a rabbitmq service program, and the copy number of the DB service program is set to be 3;
the back-end program comprises an interface program, a collection service program, a timing task service program, a task scheduling service program, a supervision and docking service program and an alarm service program, wherein the number of copies of the back-end program is set to be 2, the number of copies of the interface program is set to be 2, the number of copies of the collection service program is set to be 2, the number of copies of the timing task service program is set to be 2, the number of copies of the task scheduling service program is set to be 2, the number of copies of the supervision and docking service program is set to be 2, and the number of copies of the alarm service program is set to be 3.
3. The method for rapidly deploying the cloud pipe system based on the container technology according to claim 1, wherein the step S2 is executed to make the split atomic service into an independently operated container mirror image, and the specific operation flow is as follows:
s2.1, starting a container: selecting an operating system environment of an adaptive version;
s2.2, starting service: after the container of the basic mirror image is started, logging in the container, and executing copying and standardized starting work of a program;
s2.3, standardization treatment: program debugging and file configuration are carried out in the container, so as to achieve the aims of standardization and immobilization;
s2.4, service checking and verification: for a program started in the container, checking and verifying operation called by an interface is carried out from the outside;
s2.5, mirror image transformation: and performing mirror image production on the container started by the container mirror image warehouse and the formed fixed configuration and standard program by using the command operation of the container, outputting and storing to form a fixed container mirror image, naming according to requirements, and storing and archiving for subsequent use.
4. The method for rapidly deploying the cloud management system based on the container technology as claimed in claim 3, wherein in the process of executing the steps S1 to S4, for different types of requirements, code programs related to different atomic services can be modified, and after the code programs related to the atomic services are modified, functions related to internal start of the modified code programs related to the atomic services and functions related to mutual call interaction between the atomic services are verified through testing.
5. The method for rapidly deploying the cloud management system based on the container technology according to claim 4, wherein after the code program related to the atomic service is tested, only version management information of the atomic service related to the modified code program needs to be updated, and after the atomic service is modified, only the operation of version upgrade needs to be performed on the atomic service.
6. The method for rapidly deploying the cloud management system based on the container technology according to claim 5, wherein after testing the code program related to the atomic service, only version management information of the atomic service related to the modified code program needs to be updated, and a specific operation flow thereof is as follows:
a.1, downloading codes: logging in a git warehouse, inquiring a version number required to be used according to the requirement, and downloading an incremental code file of a corresponding version;
a.2, template file initialization: the injection operation of the basic parameters is carried out according to the environment of the actual site, which comprises the following steps: IP address planning, node role, network vlan information injection and initialization configuration;
a.3, constructing a code: inquiring the code branch version number of the increment according to the initialized template, and executing the construction of the corresponding increment version code;
and a.4, program packaging: downloading a main program package and a dependent program package according to the constructed codes and the incremental version numbers to be upgraded, and finishing the program packaging operation;
a.5, uploading a program: and transmitting the packaged program tar packet to a project environment, and executing an incremental version upgrading deployment task by using a mirror image file in a supporting medium.
7. The method for rapidly deploying the cloud management system based on the container technology according to any one of claims 1 to 6, wherein the step S4 is executed to deploy the cloud management system, and the specific operation process comprises the following steps:
s4.A.1, preparing a node: preparing 2 physical machine servers, installing an operating system, and configuring a required network according to requirements;
s4.A.2, medium preparation: transmitting an image file required by the operation of the program container to a medium and transmitting the image file to 1 physical server of the project environment;
s4.A.3, template initialization: pulling a template of the deployment file from an environment center warehouse, and completing configuration of an initialized network address and a node distribution role of the template according to relevant actual information of the environment center;
s4.A.4, constructing an execution code: inquiring a code branch version number according to the initialized template, and executing construction of a corresponding version code;
s4.A.5, packaging code programs: downloading a main program package and a dependent program package according to the constructed code and the version number to be deployed, and finishing the program packaging operation;
s4.A.6, uploading a deployment program: transmitting the packaged program tar packet to a project environment, and executing a version upgrading deployment task by using a mirror image file in a matching medium;
s4.A.7, deployment process control: tracking the process state of the deployment task through the log of the container, and checking a deployment result through the log;
s4.A.8, generating a deployment report: after the deployment task is completed, a service program for deployment check is started, the deployed cloud management system is subjected to deployment check, including version information check, service availability check and environment parameter check, and after the check is completed, a deployment report is generated.
8. The method of claim 7, wherein after the deployment program is uploaded, the deployment program can be reused with other nodes without using a node alone.
9. The method for rapidly deploying the cloud management system based on the container technology as claimed in claim 7, wherein after deployment of the cloud management system is completed, an administrator account admin may be used for login, checking availability of an interface, and also account management and allocation may be performed on operators with different roles by using authority configuration.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010950090.6A CN112084008B (en) | 2020-09-10 | 2020-09-10 | Method for rapidly deploying cloud pipe system based on container technology |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010950090.6A CN112084008B (en) | 2020-09-10 | 2020-09-10 | Method for rapidly deploying cloud pipe system based on container technology |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112084008A CN112084008A (en) | 2020-12-15 |
| CN112084008B true CN112084008B (en) | 2023-02-17 |
Family
ID=73737390
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010950090.6A Active CN112084008B (en) | 2020-09-10 | 2020-09-10 | Method for rapidly deploying cloud pipe system based on container technology |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112084008B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112799692A (en) * | 2021-02-07 | 2021-05-14 | 的卢技术有限公司 | Tomcat application deployment method and application based on docker technology |
| CN113014445B (en) * | 2021-02-08 | 2022-11-11 | 中国工商银行股份有限公司 | Operation and maintenance method, device and platform for server and electronic equipment |
| US11556332B2 (en) * | 2021-02-23 | 2023-01-17 | International Business Machines Corporation | Application updating in a computing environment using a function deployment component |
| CN114189512B (en) * | 2021-12-14 | 2023-07-14 | 南京欧珀软件科技有限公司 | Baseline code downloading method, device, terminal equipment and storage medium |
| CN114756464B (en) * | 2022-04-18 | 2024-04-26 | 中国电信股份有限公司 | Code checking configuration method, device and storage medium |
| CN115567392B (en) * | 2022-10-10 | 2023-08-15 | 浙江保融科技股份有限公司 | Automatic deployment upgrading method for customer internal service system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108279892A (en) * | 2018-02-27 | 2018-07-13 | 郑州云海信息技术有限公司 | It is a kind of to split the method, apparatus and equipment that large-scale application service is micro services |
| CN110134519A (en) * | 2019-05-21 | 2019-08-16 | 中国太平洋保险（集团）股份有限公司 | A kind of control method and device for realizing portal management based on container platform |
| CN110825399A (en) * | 2019-11-07 | 2020-02-21 | 郑州悉知信息科技股份有限公司 | Deployment method and device of application program |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130290542A1 (en) * | 2012-04-30 | 2013-10-31 | Racemi, Inc. | Server Image Migrations Into Public and Private Cloud Infrastructures |
-
2020
- 2020-09-10 CN CN202010950090.6A patent/CN112084008B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108279892A (en) * | 2018-02-27 | 2018-07-13 | 郑州云海信息技术有限公司 | It is a kind of to split the method, apparatus and equipment that large-scale application service is micro services |
| CN110134519A (en) * | 2019-05-21 | 2019-08-16 | 中国太平洋保险（集团）股份有限公司 | A kind of control method and device for realizing portal management based on container platform |
| CN110825399A (en) * | 2019-11-07 | 2020-02-21 | 郑州悉知信息科技股份有限公司 | Deployment method and device of application program |
Non-Patent Citations (1)
| Title |
|---|
| 基于Docker的运维平台设计;张延冬等;《计算机时代》;20180415(第04期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112084008A (en) | 2020-12-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112084008B (en) | Method for rapidly deploying cloud pipe system based on container technology | |
| CA2457440C (en) | System and method for the automatic installation and configuration of an operating system | |
| US8464246B2 (en) | Automation of mainframe software deployment | |
| CN107463362A (en) | The method and system of lasting deployment based on multiple Jenkins | |
| US20090144743A1 (en) | Mailbox Configuration Mechanism | |
| CN109753430A (en) | A kind of interface test method of Ground Data Processing System | |
| CN113779477A (en) | Assembly line publishing method and system based on PaaS cloud platform | |
| CN112711397A (en) | Method and system for establishing system based on micro-service and top-level design | |
| CN114995835A (en) | Application automation deployment method, system, equipment and readable storage medium | |
| CN110795105A (en) | Automatic compiling and deploying method and system for power distribution automation master station system | |
| CN112527468A (en) | Alliance chain one-stop type automatic deployment and test method and system | |
| CN117539791A (en) | Automatic test system of embedded software | |
| CN110764785B (en) | Cloud platform tool chain and cloud platform operation and maintenance method for power industry based on open source assembly | |
| CN110018846B (en) | Automatic operation and maintenance system and operation method thereof | |
| CN115357258B (en) | Application deployment method and device, storage medium and electronic device | |
| CN114327600A (en) | All-environment integrated CICD application deployment platform | |
| CN113485720A (en) | Off-line upgrading method for micro-service system | |
| CN110347447A (en) | One kind is declared dutiable goods environment bulk management method and system | |
| CN112836220B (en) | Cloud center environment inspection method | |
| CN116225464B (en) | Rapid deployment method of platform | |
| CN110213127B (en) | Automated testing system and method fusing virtualization multitasks | |
| CN117560281A (en) | Cluster automation deployment method and system based on ansable | |
| Kulaga et al. | Large-Scale Upgrade Campaigns of SCADA Systems at CERN-Organisation, Tools and Lessons Learned | |
| CN115291892A (en) | Method and system for deploying micro service based on Ansible | |
| Kulaga et al. | JACoW: Large-scale upgrade campaigns of SCADA systems at CERN-organisation, tools and lessons learned |
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 |