CN111666080B - Micro service cluster deployment method and device, computer equipment and storage medium - Google Patents
Micro service cluster deployment method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111666080B CN111666080B CN202010351614.XA CN202010351614A CN111666080B CN 111666080 B CN111666080 B CN 111666080B CN 202010351614 A CN202010351614 A CN 202010351614A CN 111666080 B CN111666080 B CN 111666080B
- Authority
- CN
- China
- Prior art keywords
- target
- cluster
- micro
- name
- service cluster
- 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 36
- 238000003860 storage Methods 0.000 title claims abstract description 16
- 241000380131 Ammophila arenaria Species 0.000 claims abstract description 66
- 238000004519 manufacturing process Methods 0.000 claims abstract description 9
- 238000004590 computer program Methods 0.000 claims description 14
- 238000009434 installation Methods 0.000 claims description 4
- 238000010276 construction Methods 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000011900 installation process Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 238000013515 script Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 244000035744 Hura crepitans Species 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- 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
-
- 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)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method, a device, computer equipment and a storage medium for deploying a micro-service cluster, wherein the method comprises the following steps: receiving a micro service cluster deployment instruction, and acquiring a micro service cluster deployment file; storing the target environment configuration package into a local warehouse, manufacturing the target environment configuration package into a Docker image file through a Docker tool, associating the Docker image file with the environment configuration package name, and uploading the Docker image file to a Docker registration machine; querying whether an environment cluster name consistent with the target environment cluster name exists in a Kubernetes cluster container through a Helm tool; creating a first micro service cluster consistent with the target environment cluster name; installing a target environment configuration package to a first target host through a Helm tool, and pushing a Docker image file to all first target nodes; and setting up the environment configuration of the first micro service cluster through a Helm tool. The invention realizes the automatic configuration of the clusters under the Kubernetes cluster container, reduces the manual configuration and improves the construction efficiency.
Description
Technical Field
The present invention relates to the field of micro-service architecture, and in particular, to a method and apparatus for deploying a micro-service cluster, a computer device, and a storage medium.
Background
In the prior art, kubernetes cluster container scheduling technology is that by dividing resources managed by a single operating system into separate groups, the Kubernetes cluster container scheduling technology can be understood as a sandbox, running one application within each container, the different containers being isolated from each other, but a communication mechanism can be established between the containers. However, manual configuration is required for building the Kubernetes cluster, labor is consumed, production operation and maintenance efficiency is low, and as iteration version up is more and more frequent, labor cost is more and more consumed, and particularly when a historical version of service application on the Kubernetes cluster needs to be rolled back due to abnormality is encountered, a rollback function is not supported due to the original of the Kubernetes. The rollback function of Helm needs to be used for specially inquiring the history version through command line operation, the environment where the application is located cannot be distinguished, the consumed labor cost is higher, and the operation and maintenance efficiency is lower.
Disclosure of Invention
The invention provides a deployment method, a deployment device, computer equipment and a storage medium for a micro-service cluster, which realize automatic configuration of one cluster under a Kubernetes cluster container, reduce complicated steps of manual configuration, improve construction efficiency and reduce cost.
A method of micro-service cluster deployment, comprising:
Receiving a micro-service cluster deployment instruction, and acquiring a micro-service cluster deployment file contained in the micro-service cluster deployment instruction; the micro-service cluster deployment file comprises a target environment cluster name, a target list and a target environment configuration package associated with the environment configuration package name; the target list comprises a target main IP address and at least one target node IP address;
storing the target environment configuration package into a local warehouse, manufacturing the target environment configuration package into a Docker image file by the local warehouse through a Docker tool, associating the Docker image file with the environment configuration package name, and uploading the Docker image file into a Docker registration machine;
After the micro-service cluster deployment file is sent to a Kubernetes cluster container, inquiring whether an environment cluster name consistent with the target environment cluster name exists in the Kubernetes cluster container through a Helm tool;
If the environment cluster name consistent with the target environment cluster name does not exist in the Kubernetes cluster container, a first micro-service cluster consistent with the target environment cluster name is created, a target machine in the Kubernetes cluster container matched with the target main IP address is determined to be a first target host of the first micro-service cluster, and a target machine in the Kubernetes cluster container matched with the target node IP address is determined to be a first target node of the first micro-service cluster;
Installing the target environment configuration package to a first target host through a Helm tool, and pushing the Docker image file associated with the environment configuration package name from the Docker registry to all the first target nodes;
And setting up the environment configuration of the first micro service cluster through a Helm tool, and determining that the deployment of the micro service cluster deployment file is completed.
A micro-service cluster deployment apparatus, comprising:
The receiving module is used for receiving a micro service cluster deployment instruction and acquiring a micro service cluster deployment file contained in the micro service cluster deployment instruction; the micro-service cluster deployment file comprises a target environment cluster name, a target list and a target environment configuration package associated with the environment configuration package name; the target list comprises a target main IP address and at least one target node IP address;
The storage module is used for storing the target environment configuration package into a local warehouse, the local warehouse makes the target environment configuration package into a Docker image file through a Docker tool, associates the Docker image file with the environment configuration package name, and uploads the Docker image file to a Docker registration machine;
the query module is used for querying whether an environment cluster name consistent with the target environment cluster name exists in the Kubernetes cluster container through a Helm tool after the micro-service cluster deployment file is sent to the Kubernetes cluster container;
The creation module is used for creating a first micro-service cluster consistent with the target environment cluster name if the environment cluster name consistent with the target environment cluster name does not exist in the Kubernetes cluster container, determining a target machine in the Kubernetes cluster container matched with the target main IP address as a first target host of the first micro-service cluster, and determining a target machine in the Kubernetes cluster container matched with the target node IP address as a first target node of the first micro-service cluster;
The installation module is used for installing the target environment configuration package to a first target host through a Helm tool, and pushing the Docker image file associated with the environment configuration package name from the Docker registry to all the first target nodes;
The determining module is used for setting up the environment configuration of the first micro service cluster through a Helm tool and determining that the deployment of the micro service cluster deployment file is completed.
A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the micro-server cluster deployment method described above when the computer program is executed.
A computer readable storage medium storing a computer program which when executed by a processor implements the steps of the micro-service cluster deployment method described above.
The invention obtains the micro-service cluster deployment file contained in the micro-service cluster deployment instruction; the micro-service cluster deployment file comprises a target environment cluster name, a target list and a target environment configuration package associated with the environment configuration package name; storing the target environment configuration package into a local warehouse, manufacturing the target environment configuration package into a Docker image file by the local warehouse through a Docker tool, associating the Docker image file with the environment configuration package name, and uploading the Docker image file into a Docker registration machine; creating a first micro service cluster consistent with the target environment cluster name, determining a target machine in the Kubernetes cluster container matched with the target main IP address as a first target host of the first micro service cluster, and determining a target machine in the Kubernetes cluster container matched with the target node IP address as a first target node of the first micro service cluster; installing the target environment configuration package to a first target host through a Helm tool, and pushing the Docker image file associated with the environment configuration package name from the Docker registry to all the first target nodes; setting up the environment configuration of the first micro-service cluster through a Helm tool, determining that the deployment of the micro-service cluster deployment file is completed, thus, obtaining a target environment configuration package in the micro-service cluster deployment file, storing the target environment configuration package in a local warehouse, making a Docker mirror image file through a Docker tool, uploading the Docker mirror image file to a Docker registry, creating the first micro-service cluster, installing the target environment configuration package to a first target host in the first micro-service cluster through the Helm tool, pushing the Docker mirror image file from the Docker registry to all the first target nodes, and setting up the environment configuration of the first micro-service cluster, and therefore, automatically configuring one cluster under a Kubernetes cluster container, reducing complicated steps of manual configuration, improving setting up efficiency and reducing cost.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the description of the embodiments of the present invention will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic view of an application environment of a micro-service cluster deployment method according to an embodiment of the present invention;
FIG. 2 is a flow chart of a method for deploying a micro-service cluster in accordance with one embodiment of the present invention;
FIG. 3 is a flowchart of step S60 of a micro service cluster deployment method according to an embodiment of the present invention;
FIG. 4 is a flow chart of a method of micro-service cluster deployment in accordance with yet another embodiment of the present invention;
FIG. 5 is a flowchart of step S80 of a micro-service cluster deployment method according to an embodiment of the present invention;
FIG. 6 is a flowchart of step S60 of a micro-service cluster deployment method in accordance with yet another embodiment of the present invention;
FIG. 7 is a functional block diagram of a micro-service cluster deployment device in accordance with one embodiment of the present invention;
FIG. 8 is a functional block diagram of a determination module in a micro-server cluster deployment device in accordance with one embodiment of the present invention;
FIG. 9 is a schematic diagram of a computer device in accordance with an embodiment of the invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The micro-service cluster deployment method provided by the invention can be applied to an application environment as shown in fig. 1, wherein a client (computer equipment) communicates with a server through a network. Among them, clients (computer devices) include, but are not limited to, personal computers, notebook computers, smartphones, tablet computers, cameras, and portable wearable devices. The server may be implemented as a stand-alone server or as a server cluster composed of a plurality of servers.
In one embodiment, as shown in fig. 2, a method for deploying a micro service cluster is provided, and the technical scheme mainly includes the following steps S10-S60:
s10, receiving a micro service cluster deployment instruction, and acquiring a micro service cluster deployment file contained in the micro service cluster deployment instruction; the micro-service cluster deployment file comprises a target environment cluster name, a target list and a target environment configuration package associated with the environment configuration package name; the destination list includes a destination primary IP address and at least one destination node IP address.
Understandably, the micro-service cluster deployment instruction refers to an instruction triggered when a target micro-service cluster needs to be deployed, the target micro service cluster is a cluster formed by using a plurality of node servers or computers under a micro service architecture, the micro-service cluster deployment instruction comprises the target micro-service cluster deployment file, the micro-service cluster deployment file is obtained after the micro-service cluster deployment instruction is received, the micro service cluster deployment file is a related file required for the deployment of the target micro service cluster, the micro-service cluster deployment file includes the target environment cluster name, the target manifest and the target environment configuration package, the target environment cluster name is a unique code for naming the target micro service cluster, the target list is a unique address (i.e. IP address) corresponding to all involved node servers or computers in the target micro service cluster, the destination list includes a destination primary IP address and at least one destination node IP address, the target main IP address is the IP address corresponding to a server or a computer in charge of managing resources to all node servers or computers in the target micro-service cluster to be deployed, the target node IP address is the IP address corresponding to all the related node servers or computers except the target main IP address in the target micro service cluster to be deployed, the target environment configuration package is a file of a set of code required to deploy the target micro service cluster, the target environment configuration package is associated with the target environment configuration package name, and the target environment configuration package name is the name for naming the target environment configuration package.
The server comprises a Kubernetes cluster container, and the Kubernetes cluster container provides convenience for large-scale containerized cluster management for a containerized cluster management system based on a Docker.
In an embodiment, the target environment configuration package name includes a chart directory name, a target environment name, and a target version name, where the target environment name is obtained by abbreviation according to a file name corresponding to a configuration file under the target environment configuration package associated with the environment configuration package name, and the target version name is an iteratively updated version number, and uniqueness of the environment configuration package name is determined according to the chart directory name, the target environment name, and the target version name.
Understandably, the target environment configuration package name includes the chart directory name, the target environment name, and the target version name, for example: the name of the target environment configuration package is "chart_ EGLW _1.0.0", the unique environment configuration package can be determined through the chart directory name, the target environment name and the target version name, the target environment name is formed by splicing abbreviations of file names corresponding to configuration files under the target environment configuration package, the target version name is an iteratively updated version number, and the format of the target version name can be set according to requirements, for example, the format of the target version name is XX.XX.XX.
Therefore, the Kubernetes cluster container can allow the catalog files with the same char catalog name to have different versions in different clusters through the target environment configuration package name, the defect that the catalog files with the same char catalog name in the Kubernetes cluster container have only one version is overcome, and the catalog files with the same char catalog name among clusters are separated from each other.
S20, storing the target environment configuration package into a local warehouse, manufacturing the target environment configuration package into a Docker image file by the local warehouse through a Docker tool, associating the Docker image file with the environment configuration package name, and uploading the Docker image file to a Docker registration machine.
The method comprises the steps of creating a target environment configuration package into a dock image file by a dock tool, wherein the dock image file is a file which is completely consistent with the target environment configuration package, the target environment configuration package can be operated as a developer can operate the target environment configuration package after receiving the dock image file, the target environment configuration package does not need to be configured one by one manually, a local warehouse is a server or a computer for storing the target environment configuration package and a historical environment configuration package, the historical environment configuration package is the target environment configuration package received before the target environment configuration package, a dock registrar is a tool for managing the received dock image file to be pushed to a designated registered target machine, and the dock tool is a visual management tool which is convenient for the developer to write Shell command lines or scripts, so that the threshold of the developer can be reduced, the time for writing the Shell command lines or scripts can be reduced, and the development efficiency can be improved.
S30, after the micro-service cluster deployment file is sent to a Kubernetes cluster container, whether the environment cluster name consistent with the target environment cluster name exists in the Kubernetes cluster container is inquired through a Helm tool.
Understandably, the microservice cluster deployment file is sent to the Kubernetes cluster container, and the environment cluster names consistent with the target environment cluster names are queried from the Kubernetes cluster container through the Helm tool, wherein the Kubernetes cluster container comprises a plurality of environment cluster names.
Wherein the Helm tool is a tool for providing powerful functions such as software deployment, deletion, upgrading, rollback application and the like on the Kubernetes, and is convenient for a user to search, install, upgrade and uninstall application programs in a simple way,
And S40, if the environment cluster name consistent with the target environment cluster name does not exist in the Kubernetes cluster container, a first micro-service cluster consistent with the target environment cluster name is created, a target machine in the Kubernetes cluster container matched with the target main IP address is determined to be a first target host of the first micro-service cluster, and a target machine in the Kubernetes cluster container matched with the target node IP address is determined to be a first target node of the first micro-service cluster.
It is understood that if the environment cluster name consistent with the target environment cluster name is not queried in the Kubernetes cluster container, the first micro service cluster is created, the first micro service cluster is the target micro service cluster with the same target environment cluster name, the target machine in the Kubernetes cluster container matched with the target main IP address is determined to be the first target host of the first micro service cluster, the target machine is a server or a computer which has a unique IP address in the Kubernetes cluster container and completes registration on the Docker registration machine, the registration is an operation mode of registering on the Docker registration machine and uploading the corresponding state of the target machine at a fixed time, the target machine in the kuberes cluster container matched with the target node IP address is determined to be the first target node of the first micro service cluster, namely, all target machines except the first target node in the kuberes cluster container are determined to be the target node IP address of the first micro service cluster, the target machine is queried to be one of the target nodes, and the target machine is determined to be the target node.
S50, installing the target environment configuration package to a first target host through a Helm tool, and pushing the Docker image file associated with the environment configuration package name from the Docker registrar to all the first target nodes.
It can be understood that the target environment configuration package can be installed into the first target host by the Helm tool, and the installation process is completely completed by the Helm tool without manual operation, so that the Docker image file associated with the environment configuration package name can be pushed from the Docker registry to all the first target nodes, and the pushing mode is a point-to-multipoint sending mode.
S60, setting up the environment configuration of the first micro service cluster through a Helm tool, and determining that the deployment of the micro service cluster deployment file is completed.
Understandably, the Docker image file is installed to all the first target nodes through a Helm tool, so that the first micro service cluster is built, the environment configuration of the first micro service cluster is completed, and further it is determined that the deployment file of the micro service cluster is deployed.
The invention obtains the micro-service cluster deployment file contained in the micro-service cluster deployment instruction; the micro-service cluster deployment file comprises a target environment cluster name, a target list and a target environment configuration package associated with the environment configuration package name; storing the target environment configuration package into a local warehouse, manufacturing the target environment configuration package into a Docker image file by the local warehouse through a Docker tool, associating the Docker image file with the environment configuration package name, and uploading the Docker image file into a Docker registration machine; creating a first micro service cluster consistent with the target environment cluster name, determining a target machine in the Kubernetes cluster container matched with the target main IP address as a first target host of the first micro service cluster, and determining a target machine in the Kubernetes cluster container matched with the target node IP address as a first target node of the first micro service cluster; installing the target environment configuration package to a first target host through a Helm tool, and pushing the Docker image file associated with the environment configuration package name from the Docker registry to all the first target nodes; and setting up the environment configuration of the first micro service cluster through a Helm tool, and determining that the deployment of the micro service cluster deployment file is completed.
The method and the device realize that the target environment configuration package in the micro-service cluster deployment file is obtained and stored in a local warehouse, the Docker mirror image file is manufactured through the Docker tool and uploaded to the Docker registration machine, the first micro-service cluster is created, the target environment configuration package is installed to the first target host in the first micro-service cluster through the Helm tool, meanwhile, the Docker mirror image file is pushed to all the first target nodes from the Docker registration machine, and the environment configuration of the first micro-service cluster is built, so that one cluster under the Kubernetes cluster container is automatically configured, complicated steps of manual configuration are reduced, the building efficiency is improved, and the cost is reduced.
In an embodiment, as shown in fig. 3, in the step S60, that is, the setting up the environment configuration of the first micro service cluster by using the Helm tool, the determining that the deployment of the micro service cluster deployment file is completed includes:
s601, acquiring a part directory name in the target environment configuration package and a part directory name in the environment configuration package name.
It is understandable that the target environment configuration package is searched for a directory file identical to the hart directory name in the environment configuration package name, and the directory file is usually stored in a file form in order to manage the file directory under the hart directory name.
S602, through a Helm tool, the Kubernetes cluster container executes resource declaration of a catalog file associated with a chart catalog name in the target environment configuration package in the first micro service cluster, and completes environment configuration of the first micro service cluster.
Understandably, the Helm tool also operates on the directory file associated with the hart directory name, performs resource declaration on the directory file associated with the hart directory name in the first micro service cluster, that is, indicates that the directory file is enabled, and enables the file under the hart directory name, that is, enables the related file of the hart directory name.
Therefore, the invention can rapidly and completely declare the resource of the catalog file associated with the char catalog name through the Helm tool, and reduces the manual complicated operation.
In an embodiment, as shown in fig. 4, after the step S30, that is, after querying whether the environment cluster name consistent with the target environment cluster name exists in the Kubernetes cluster container, the method further includes:
S70, if the environment cluster names consistent with the target environment cluster names exist in the Kubernetes cluster container, marking the clusters with the environment cluster names consistent with the target environment cluster names as second micro-service clusters; the second micro service cluster includes a second target host and at least one second target node.
It is understood that if an environment cluster name consistent with the target environment cluster name exists in the Kubernetes cluster container, a cluster in which the environment cluster name is consistent with the target environment cluster name is determined as the second micro-service cluster, the second target host is a server or a computer associated with the second micro-service cluster and managing resources to all second target nodes under the second micro-service cluster, and the second target node is all node servers or computers under the second micro-service cluster except the second target host.
And S80, updating the second target hosts and all second target nodes of the second micro service cluster according to the target list.
Understandably, the second target hosts and all the second target nodes in the second micro service cluster are refreshed, that is, the second target hosts and all the second target nodes of the second micro service cluster are redetermined, according to the target primary IP address and the target node IP address in the target list.
In one embodiment, as shown in fig. 5, in the step S80, the updating the second target hosts and all the second target nodes of the second micro service cluster according to the target list includes:
S801, canceling the association of the second micro service cluster and the second target host, and canceling the association of the second micro service cluster and the second target node.
Understandably, the second target host and the second micro service cluster have an association relationship, and connection is established through a timing monitoring mode and an interactive communication mode, and the association between the second micro service cluster and the second target host is canceled, namely, the connection between the second micro service cluster and the second target host is canceled; and the second target node and the second micro service cluster have an association relationship, connection is established through a timing monitoring mode and an interactive communication mode, and the association of the second micro service cluster and the second target node is canceled, namely the connection of the second micro service cluster and the second target node is canceled.
S802, determining a target machine in the Kubernetes cluster container matched with the target main IP address as the second target host after updating, and determining a target machine in the Kubernetes cluster container matched with the target node IP address as the second target node after updating.
Understandably, establishing an association relationship between the target machine in the Kubernetes cluster container matched with the target main IP address and the second micro-service cluster, and recording the target machine in the Kubernetes cluster container matched with the target main IP address as the second target host after updating; and establishing an association relation between the target machines in the Kubernetes cluster container matched with the IP address of the target node and the second micro-service cluster, and recording the target machines in the Kubernetes cluster container matched with the IP address of the target node as the updated second target nodes, wherein the second micro-service cluster has association with a plurality of second target nodes.
S90, installing the target environment configuration package to the second target host after updating through a Helm tool, and pushing the Docker image file associated with the environment configuration package name from the Docker registry to all the second target nodes after updating.
It can be understood that the target environment configuration package can be installed into the second target host after updating by the Helm tool, and the installation process is completed by the Helm tool without manual operation, so that the Docker image file associated with the environment configuration package name can be pushed from the Docker registry to all the second target nodes at the same time, and the pushing mode is a point-to-multipoint sending mode.
S100, setting up the environment configuration of the second micro service cluster through a Helm tool, and determining that the deployment of the micro service cluster deployment file is completed.
Understandably, the Docker image file is installed to all the second target nodes through a Helm tool, so that the second micro-service cluster is built, the environment configuration of the second micro-service cluster is completed, and further it is determined that the deployment file of the micro-service cluster is deployed.
The invention realizes that the target environment configuration package in the micro-service cluster deployment file is obtained and stored in a local warehouse, the Docker mirror image file is manufactured through the Docker tool and is uploaded to the Docker registration machine, the second micro-service cluster is updated according to the target list, the target environment configuration package is installed to a second target host after updating in the second micro-service cluster through the Helm tool, meanwhile, the Docker mirror image file is pushed to all updated second target nodes from the Docker registration machine, and the environment configuration of the second micro-service cluster is built, so that the invention provides a method for updating the cluster existing in the Kubernetes cluster container, and the environment configuration of the cluster is iteratively updated through the Helm tool and the Docker tool, thereby realizing the labor cost of cluster building and improving the building efficiency.
In an embodiment, as shown in fig. 6, after the step S60, that is, after the environment configuration of the first micro service cluster is built by the Helm tool, it is determined that the deployment of the micro service cluster deployment file is completed, the method includes:
s110, receiving a micro-service cluster rollback deployment instruction, and acquiring a micro-service cluster rollback deployment file contained in the micro-service cluster rollback deployment instruction; the micro-service cluster rollback deployment file comprises a rollback environment cluster name, a rollback list and a rollback version name; the rollback list includes one rollback primary IP address and at least one rollback node IP address.
Understandably, the micro service cluster rollback deployment instruction refers to an instruction triggered when a target micro service cluster which has been deployed and exists needs to be rolled back to a certain version of history, the micro service cluster rollback deployment instruction includes the micro service cluster rollback deployment file, and the micro service cluster rollback deployment file includes a rollback environment cluster name, a rollback list and a rollback version name; the rollback list comprises a rollback main IP address and at least one rollback node IP address, the rollback environment cluster name is a name with a unique code corresponding to a target micro service cluster needing to execute environment rollback operation, the rollback list is a unique address (i.e. IP address) corresponding to all related node servers or computers in the target micro service cluster needing to execute environment rollback operation, the rollback list comprises a rollback main IP address and at least one rollback node IP address, the rollback main IP address is an IP address corresponding to a server or computer in the target micro service cluster needing to execute environment rollback operation, the rollback node IP address is an IP address corresponding to all related node servers or computers in the target micro service cluster needing to execute environment rollback operation, the rollback version is one of environment configuration package names related to history environment configuration packages, the rollback version can be configured as one of environment configuration package names related to history environment configuration packages, the environment configuration package can be manually queried through a context configuration box, and the context configuration package can be queried or manually.
S120, determining an environment configuration package name which is matched with the rollback version name and is configured, acquiring an environment configuration package associated with the matched environment configuration package name from the local warehouse, manufacturing the environment configuration package into a rollback Docker image file by the local warehouse through a Docker tool, associating the rollback Docker image file with the rollback version name, and uploading the rollback Docker image file to the Docker registration machine.
Understandably, the environment configuration package names (i.e. the environment configuration package names associated with the historical environment configuration packages) which are matched with the rollback version names and are configured are obtained, all the historical environment configuration packages are stored in the local warehouse, each historical environment configuration package is associated with a corresponding environment configuration package name, the local warehouse manages all the environment configuration packages, the environment configuration package associated with the matched environment configuration package name is obtained from the local warehouse, the environment configuration package is made into the rollback Docker image file through the Docker tool, the relationship between the rollback Docker image file and the rollback version names is established, and the rollback Docker image file is sent to the Docker registration machine.
S130, marking the cluster with the environment cluster name consistent with the rollback environment cluster name as a third micro-service cluster; and updating the third target hosts and all third target nodes of the third micro service cluster according to the rollback list.
Understandably, determining a cluster with an environment cluster name consistent with the rollback environment cluster name as the third micro-service cluster, the third target host being a server or computer associated with the third micro-service cluster and managing resources to all third target nodes under the third micro-service cluster, the third target nodes being all node servers or computers under the third micro-service cluster except the third target host; and refreshing the third target hosts and all the third target nodes in the third micro service cluster according to the rollback main IP address and the rollback node IP address in the rollback list, namely, redefining the third target hosts and all the third target nodes of the third micro service cluster.
And S140, installing the environment configuration package to the updated third target host through a Helm tool, and pushing the rollback Docker image file from the Docker registry to all updated third target nodes.
It can be understood that the environment configuration package can be installed into the third target host after updating by the Helm tool, and the installation process is completely completed by the Helm tool without manual operation, so that the rolled-back Docker image file can be pushed from the Docker registry to all the third target nodes, and the pushing mode is a point-to-multipoint sending mode.
And S150, setting up the environment configuration of the third micro service cluster through a Helm tool, and determining that the deployment of the micro service cluster deployment file is completed.
Understandably, the rollback Docker image file is installed to all the third target nodes through a Helm tool, so that the third micro service cluster is built, the environment configuration of the third micro service cluster is completed, and further it is determined that the deployment file of the micro service cluster is deployed.
According to the invention, the environment configuration package corresponding to the rollback version name can be quickly obtained in the local warehouse, and the third micro-service cluster is quickly rolled back to the environment configuration of any version of the history through the Docker tool and the Helm tool, so that the environment configuration of the third micro-service cluster is quickly built, the manual configuration operation is greatly reduced, the rollback limitation of the Kubernetes cluster container is solved, and the cluster under the Kubernetes cluster container can be quickly rolled back to the environment configuration of any version of the history.
In an embodiment, a micro service cluster deployment device is provided, where the micro service cluster deployment device corresponds to the micro service cluster deployment method in the above embodiment one by one. As shown in fig. 7, the micro service cluster deployment apparatus includes a receiving module 11, a storing module 12, a querying module 13, a creating module 14, an installing module 15, and a determining module 16. The functional modules are described in detail as follows:
The receiving module 11 is configured to receive a micro service cluster deployment instruction, and obtain a micro service cluster deployment file contained in the micro service cluster deployment instruction; the micro-service cluster deployment file comprises a target environment cluster name, a target list and a target environment configuration package associated with the environment configuration package name; the target list comprises a target main IP address and at least one target node IP address;
The storage module 12 is configured to store the target environment configuration package into a local repository, where the local repository makes the target environment configuration package into a Docker image file through a Docker tool, associates the Docker image file with the environment configuration package name, and uploads the Docker image file to a Docker registration machine;
the query module 13 is configured to query, through a Helm tool, whether an environment cluster name consistent with the target environment cluster name exists in the Kubernetes cluster container after the microservice cluster deployment file is sent to the Kubernetes cluster container;
A creating module 14, configured to create a first micro service cluster consistent with the target environment cluster name if there is no environment cluster name consistent with the target environment cluster name in the Kubernetes cluster container, determine a target machine in the Kubernetes cluster container that matches the target main IP address as a first target host of the first micro service cluster, and determine a target machine in the Kubernetes cluster container that matches the target node IP address as a first target node of the first micro service cluster;
An installation module 15, configured to install the target environment configuration package to a first target host through a Helm tool, and push the Docker image file associated with the environment configuration package name from the Docker registry to all the first target nodes;
the determining module 16 is configured to build an environment configuration of the first micro service cluster through a Helm tool, and determine that deployment of the deployment file of the micro service cluster is completed.
In an embodiment, the target environment configuration package name includes a chart directory name, a target environment name, and a target version name, where the target environment name is obtained by abbreviation according to a file name corresponding to a configuration file under the target environment configuration package associated with the environment configuration package name, and the target version name is an iteratively updated version number, and uniqueness of the environment configuration package name is determined according to the chart directory name, the target environment name, and the target version name.
In one embodiment, as shown in fig. 8, the determining module 16 includes:
an obtaining unit 61, configured to obtain a chart directory name in the target environment configuration package and a chart directory name in the environment configuration package name;
And the executing unit 62 is configured to execute, by using a Helm tool, a resource declaration of a directory file associated with a chart directory name in the target environment configuration package in the first micro service cluster by using the Kubernetes cluster container, so as to complete environment configuration of the first micro service cluster.
In one embodiment, the query module 13 includes:
The marking unit is used for marking the cluster with the environment cluster name consistent with the target environment cluster name as a second micro-service cluster if the environment cluster name consistent with the target environment cluster name exists in the Kubernetes cluster container; the second micro service cluster comprises a second target host and at least one second target node;
the updating unit is used for updating the second target hosts and all second target nodes of the second micro service cluster according to the target list;
An installation unit, configured to install the target environment configuration package to the updated second target host through a Helm tool, and push the Docker image file associated with the environment configuration package name from the Docker registry to all updated second target nodes;
The deployment unit is used for constructing the environment configuration of the second micro service cluster through a Helm tool and determining that the deployment of the micro service cluster deployment file is completed.
In an embodiment, the updating unit comprises:
A cancellation subunit, configured to cancel association of the second micro service cluster with the second target host, and cancel association of the second micro service cluster with the second target node at the same time;
And the association subunit is used for determining the target machine in the Kubernetes cluster container matched with the target main IP address as the second target host after updating, and determining the target machine in the Kubernetes cluster container matched with the target node IP address as the second target node after updating.
In one embodiment, the determining module 16 further includes:
The rollback receiving unit is used for receiving a rollback deployment instruction of the micro service cluster and acquiring a rollback deployment file of the micro service cluster contained in the rollback deployment instruction of the micro service cluster; the micro-service cluster rollback deployment file comprises a rollback environment cluster name, a rollback list and a rollback version name; the rollback list comprises a rollback main IP address and at least one rollback node IP address;
A rollback making unit, configured to determine an environment configuration package name which is matched with the rollback version name and is configured, obtain an environment configuration package associated with the matched environment configuration package name from the local repository, make the environment configuration package into a rollback Docker image file through a Docker tool, associate the rollback Docker image file with the rollback version name, and upload the rollback Docker image file to the Docker registration machine;
the rollback marking unit is used for marking the cluster with the environment cluster name consistent with the rollback environment cluster name as a third micro-service cluster; updating a third target host and all third target nodes of the third micro service cluster according to the rollback list;
A rollback darkness transferring unit, configured to install the environment configuration package to the updated third target host through a Helm tool, and push the rollback Docker image file from the Docker registry to all updated third target nodes at the same time;
The rollback deployment unit is used for constructing the environment configuration of the third micro service cluster through a Helm tool and determining to finish the deployment of the micro service cluster deployment file.
For specific limitations of the micro service cluster deployment apparatus, reference may be made to the above limitation of the micro service cluster deployment method, and no further description is given here. The modules in the micro-service cluster deployment device may be implemented in whole or in part by software, hardware, or a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 9. 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 includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements a micro-service cluster deployment method.
In one embodiment, a computer device is provided that includes a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the micro-service cluster deployment method of the above embodiments when executing the computer program.
In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, which when executed by a processor implements the micro-service cluster deployment method of the above embodiment.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided herein may include non-volatile and/or volatile memory. The nonvolatile 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 (SYNCHLINK) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions.
The above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention, and are intended to be included in the scope of the present invention.
Claims (9)
1. A method for deploying a micro service cluster, comprising:
Receiving a micro-service cluster deployment instruction, and acquiring a micro-service cluster deployment file contained in the micro-service cluster deployment instruction; the micro-service cluster deployment file comprises a target environment cluster name, a target list and a target environment configuration package associated with the environment configuration package name; the target list comprises a target main IP address and at least one target node IP address;
storing the target environment configuration package into a local warehouse, manufacturing the target environment configuration package into a Docker image file by the local warehouse through a Docker tool, associating the Docker image file with the environment configuration package name, and uploading the Docker image file into a Docker registration machine;
After the micro-service cluster deployment file is sent to a Kubernetes cluster container, inquiring whether an environment cluster name consistent with the target environment cluster name exists in the Kubernetes cluster container through a Helm tool;
If the environment cluster name consistent with the target environment cluster name does not exist in the Kubernetes cluster container, a first micro-service cluster consistent with the target environment cluster name is created, a target machine in the Kubernetes cluster container matched with the target main IP address is determined to be a first target host of the first micro-service cluster, and a target machine in the Kubernetes cluster container matched with the target node IP address is determined to be a first target node of the first micro-service cluster;
Installing the target environment configuration package to a first target host through a Helm tool, and pushing the Docker image file associated with the environment configuration package name from the Docker registry to all the first target nodes;
setting up the environment configuration of the first micro service cluster through a Helm tool, and determining that the deployment of the micro service cluster deployment file is completed;
the setting up the environment configuration of the first micro service cluster through a Helm tool, after determining that the deployment of the micro service cluster deployment file is completed, includes:
Receiving a micro-service cluster rollback deployment instruction, and acquiring a micro-service cluster rollback deployment file contained in the micro-service cluster rollback deployment instruction; the micro-service cluster rollback deployment file comprises a rollback environment cluster name, a rollback list and a rollback version name; the rollback list comprises a rollback main IP address and at least one rollback node IP address;
determining an environment configuration package name which is matched with the rollback version name and is configured, acquiring an environment configuration package associated with the matched environment configuration package name from the local warehouse, manufacturing the environment configuration package into a rollback Docker image file by the local warehouse through a Docker tool, associating the rollback Docker image file with the rollback version name, and uploading the rollback Docker image file to the Docker registrar;
Marking the cluster with the environment cluster name consistent with the rollback environment cluster name as a third micro-service cluster; updating a third target host and all third target nodes of the third micro service cluster according to the rollback list;
installing the environment configuration package to the updated third target host through a Helm tool, and pushing the rollback Docker image file from the Docker registry to all updated third target nodes at the same time;
And setting up the environment configuration of the third micro service cluster through a Helm tool, and determining that the deployment of the micro service cluster deployment file is completed.
2. The method of deploying micro-service clusters according to claim 1, wherein the target environment configuration package name includes a chart directory name, a target environment name, and a target version name, the target environment name is obtained by abbreviation according to a file name corresponding to a configuration file under the target environment configuration package associated with the environment configuration package name, the target version name is an iteratively updated version number, and uniqueness of the environment configuration package name is determined according to the chart directory name, the target environment name, and the target version name.
3. The method for deploying a micro service cluster according to claim 1, wherein the setting up the environment configuration of the first micro service cluster by using a Helm tool, determining that the deployment of the micro service cluster deployment file is completed, comprises:
Acquiring a char directory name in the target environment configuration package and the environment configuration package name;
And executing resource declaration of a catalog file associated with a chart catalog name in the target environment configuration package in the first micro service cluster by the Kubernetes cluster container through a Helm tool, and completing environment configuration of the first micro service cluster.
4. The method of deploying micro-service clusters according to claim 1, further comprising, after querying from the Kubernetes cluster container whether there is an environment cluster name consistent with the target environment cluster name:
If the environment cluster names consistent with the target environment cluster names exist in the Kubernetes cluster container, marking the clusters with the environment cluster names consistent with the target environment cluster names as second micro-service clusters; the second micro service cluster comprises a second target host and at least one second target node;
Updating a second target host and all second target nodes of the second micro service cluster according to the target list;
Installing the target environment configuration package to the updated second target host by a Helm tool, and pushing the Docker image file associated with the environment configuration package name from the Docker registry to all updated second target nodes;
And setting up the environment configuration of the second micro service cluster through a Helm tool, and determining that the deployment of the micro service cluster deployment file is completed.
5. The method of micro-service cluster deployment of claim 4, wherein updating the second target hosts and all second target nodes of the second micro-service cluster according to the target manifest comprises:
canceling the association of the second micro service cluster with the second target host while canceling the association of the second micro service cluster with the second target node;
And determining a target machine in the Kubernetes cluster container matched with the target main IP address as the second target host after updating, and determining a target machine in the Kubernetes cluster container matched with the target node IP address as the second target node after updating.
6. A micro-service cluster deployment apparatus, comprising:
The receiving module is used for receiving a micro service cluster deployment instruction and acquiring a micro service cluster deployment file contained in the micro service cluster deployment instruction; the micro-service cluster deployment file comprises a target environment cluster name, a target list and a target environment configuration package associated with the environment configuration package name; the target list comprises a target main IP address and at least one target node IP address;
The storage module is used for storing the target environment configuration package into a local warehouse, the local warehouse makes the target environment configuration package into a Docker image file through a Docker tool, associates the Docker image file with the environment configuration package name, and uploads the Docker image file to a Docker registration machine;
the query module is used for querying whether an environment cluster name consistent with the target environment cluster name exists in the Kubernetes cluster container through a Helm tool after the micro-service cluster deployment file is sent to the Kubernetes cluster container;
The creation module is used for creating a first micro-service cluster consistent with the target environment cluster name if the environment cluster name consistent with the target environment cluster name does not exist in the Kubernetes cluster container, determining a target machine in the Kubernetes cluster container matched with the target main IP address as a first target host of the first micro-service cluster, and determining a target machine in the Kubernetes cluster container matched with the target node IP address as a first target node of the first micro-service cluster;
The installation module is used for installing the target environment configuration package to a first target host through a Helm tool, and pushing the Docker image file associated with the environment configuration package name from the Docker registry to all the first target nodes;
The determining module is used for setting up the environment configuration of the first micro service cluster through a Helm tool and determining that the deployment of the micro service cluster deployment file is completed;
The determination module further includes:
The rollback receiving unit is used for receiving a rollback deployment instruction of the micro service cluster and acquiring a rollback deployment file of the micro service cluster contained in the rollback deployment instruction of the micro service cluster; the micro-service cluster rollback deployment file comprises a rollback environment cluster name, a rollback list and a rollback version name; the rollback list comprises a rollback main IP address and at least one rollback node IP address;
A rollback making unit, configured to determine an environment configuration package name which is matched with the rollback version name and is configured, obtain an environment configuration package associated with the matched environment configuration package name from the local repository, make the environment configuration package into a rollback Docker image file through a Docker tool, associate the rollback Docker image file with the rollback version name, and upload the rollback Docker image file to the Docker registration machine;
the rollback marking unit is used for marking the cluster with the environment cluster name consistent with the rollback environment cluster name as a third micro-service cluster; updating a third target host and all third target nodes of the third micro service cluster according to the rollback list;
A rollback darkness transferring unit, configured to install the environment configuration package to the updated third target host through a Helm tool, and push the rollback Docker image file from the Docker registry to all updated third target nodes at the same time;
The rollback deployment unit is used for constructing the environment configuration of the third micro service cluster through a Helm tool and determining to finish the deployment of the micro service cluster deployment file.
7. The micro-service cluster deployment apparatus of claim 6, comprising:
an obtaining unit, configured to obtain a char directory name in the target environment configuration package and a char directory name in the environment configuration package name;
And the execution unit is used for executing the resource declaration of the directory file associated with the chart directory name in the target environment configuration package in the first micro service cluster by the Kubernetes cluster container through a Helm tool, and completing the environment configuration of the first micro service cluster.
8. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the micro-service cluster deployment method according to any of claims 1 to 5 when executing the computer program.
9. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the micro service cluster deployment method according to any one of claims 1 to 5.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010351614.XA CN111666080B (en) | 2020-04-28 | 2020-04-28 | Micro service cluster deployment method and device, computer equipment and storage medium |
| PCT/CN2020/099554 WO2021217871A1 (en) | 2020-04-28 | 2020-06-30 | Method and apparatus for deploying micro service cluster, computer device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010351614.XA CN111666080B (en) | 2020-04-28 | 2020-04-28 | Micro service cluster deployment method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111666080A CN111666080A (en) | 2020-09-15 |
| CN111666080B true CN111666080B (en) | 2024-05-03 |
Family
ID=72383005
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010351614.XA Active CN111666080B (en) | 2020-04-28 | 2020-04-28 | Micro service cluster deployment method and device, computer equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111666080B (en) |
| WO (1) | WO2021217871A1 (en) |
Families Citing this family (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112181439A (en) * | 2020-09-24 | 2021-01-05 | 中国建设银行股份有限公司 | Micro-service deployment method and device, electronic equipment and readable storage medium |
| CN112241314B (en) * | 2020-10-29 | 2022-08-09 | 浪潮通用软件有限公司 | Multi-Kubernetes cluster management method and device and readable medium |
| CN112363806B (en) * | 2020-11-23 | 2023-09-22 | 北京信安世纪科技股份有限公司 | Cluster management method and device, electronic equipment and storage medium |
| CN112463304A (en) * | 2020-12-03 | 2021-03-09 | 金蝶软件（中国）有限公司 | Rollback method and apparatus for container mirror image, computer device, and storage medium |
| CN112749085B (en) * | 2020-12-31 | 2023-10-24 | 北京知因智慧科技有限公司 | Cross-cluster task publishing method and device, electronic equipment and storage medium |
| CN112769947A (en) * | 2021-01-20 | 2021-05-07 | 浪潮云信息技术股份公司 | Method for managing micro-service engine instances based on tenant-side container cluster |
| CN113157339B (en) * | 2021-04-23 | 2023-07-18 | 东云睿连(武汉)计算技术有限公司 | Application service extension method, system, storage medium and device based on OSB |
| CN113190327B (en) * | 2021-04-30 | 2023-02-03 | 平安证券股份有限公司 | Micro-service deployment method, device, equipment and storage medium |
| CN113553075A (en) * | 2021-07-28 | 2021-10-26 | 用友汽车信息科技（上海）股份有限公司 | Deployment method, deployment system, computer device and storage medium for micro-services |
| CN113741909B (en) * | 2021-08-31 | 2024-04-12 | 平安国际智慧城市科技股份有限公司 | Micro-service deployment method and device, electronic equipment and storage medium |
| CN114157658B (en) * | 2021-12-06 | 2024-03-01 | 京东科技信息技术有限公司 | Mirror warehouse deployment method, apparatus, electronic device and computer readable medium |
| CN114047938B (en) * | 2022-01-11 | 2023-05-26 | 北京向量栈科技有限公司 | Method, device, equipment and readable storage medium for constructing mirror image |
| CN114840225B (en) * | 2022-04-26 | 2023-09-19 | 光大科技有限公司 | Application deployment method and device, storage medium and electronic device |
| CN115145604A (en) * | 2022-07-18 | 2022-10-04 | 国能信控互联技术有限公司 | Containerized electric power marketing system deployment method |
| CN116643846B (en) * | 2023-06-01 | 2024-02-20 | 北京首都在线科技股份有限公司 | Timed task processing method and device based on container cluster arrangement management platform |
| CN116661811B (en) * | 2023-07-31 | 2023-10-20 | 明阳时创(北京)科技有限公司 | Closed-loop containerized controllable service cluster construction method and service cluster device |
| CN117033325B (en) * | 2023-10-08 | 2023-12-26 | 恒生电子股份有限公司 | Mirror image file preheating and pulling method and device |
| CN117331578B (en) * | 2023-12-01 | 2024-03-26 | 之江实验室 | Cluster mirror image deployment method and system for microminiature data center |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108809722A (en) * | 2018-06-13 | 2018-11-13 | 郑州云海信息技术有限公司 | A kind of method, apparatus and storage medium of deployment Kubernetes clusters |
| CN109634621A (en) * | 2018-11-30 | 2019-04-16 | 武汉烽火信息集成技术有限公司 | Openstack Platform deployment method, storage medium, electronic equipment and system |
| CN110012088A (en) * | 2019-03-29 | 2019-07-12 | 山东浪潮云信息技术有限公司 | A kind of Redis principal and subordinate's cluster automatically dispose scheme based on Kubernets |
| CN110532101A (en) * | 2019-09-03 | 2019-12-03 | 中国联合网络通信集团有限公司 | The deployment system and method for micro services cluster |
| CN110806880A (en) * | 2019-11-04 | 2020-02-18 | 紫光云技术有限公司 | High-reliability, high-performance and high-efficiency container cluster deployment method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10379835B2 (en) * | 2016-12-19 | 2019-08-13 | International Business Machines Corporation | Optimized creation of distributed storage and distributed processing clusters on demand |
| CN110752947B (en) * | 2019-10-18 | 2022-11-18 | 北京浪潮数据技术有限公司 | K8s cluster deployment method and device, and deployment platform |
-
2020
- 2020-04-28 CN CN202010351614.XA patent/CN111666080B/en active Active
- 2020-06-30 WO PCT/CN2020/099554 patent/WO2021217871A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108809722A (en) * | 2018-06-13 | 2018-11-13 | 郑州云海信息技术有限公司 | A kind of method, apparatus and storage medium of deployment Kubernetes clusters |
| CN109634621A (en) * | 2018-11-30 | 2019-04-16 | 武汉烽火信息集成技术有限公司 | Openstack Platform deployment method, storage medium, electronic equipment and system |
| CN110012088A (en) * | 2019-03-29 | 2019-07-12 | 山东浪潮云信息技术有限公司 | A kind of Redis principal and subordinate's cluster automatically dispose scheme based on Kubernets |
| CN110532101A (en) * | 2019-09-03 | 2019-12-03 | 中国联合网络通信集团有限公司 | The deployment system and method for micro services cluster |
| CN110806880A (en) * | 2019-11-04 | 2020-02-18 | 紫光云技术有限公司 | High-reliability, high-performance and high-efficiency container cluster deployment method |
Non-Patent Citations (1)
| Title |
|---|
| 基于OpenStack和Kubernetes的双向部署技术研究;杜磊;;电脑知识与技术;20200105(01);10-12 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111666080A (en) | 2020-09-15 |
| WO2021217871A1 (en) | 2021-11-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111666080B (en) | Micro service cluster deployment method and device, computer equipment and storage medium | |
| CN107515776B (en) | Method for upgrading service continuously, node to be upgraded and readable storage medium | |
| US10007499B2 (en) | Decoupled installation of data management systems | |
| CN110012088B (en) | Kubernets-based Redis master-slave cluster automatic deployment scheme | |
| US9250672B2 (en) | Cloning target machines in a software provisioning environment | |
| CN111782232A (en) | Cluster deployment method and device, terminal equipment and storage medium | |
| WO2011069730A1 (en) | A method and system for managing configurations of system management agents in a distributed environment | |
| CN107483241B (en) | Method and device for downloading upgrade mirror image version in network element upgrading process | |
| US20140122860A1 (en) | Cloud system and boot deployment method for the cloud system | |
| US11991094B2 (en) | Metadata driven static determination of controller availability | |
| CN111984269A (en) | Method for providing application construction service and application construction platform | |
| CN112882729A (en) | Application image upgrading method and device, computer equipment and storage medium | |
| US20230060053A1 (en) | Method and apparatus of deploying a cluster, and storage medium | |
| CN115048205B (en) | ETL scheduling platform, deployment method thereof and computer-readable storage medium | |
| Nikolov | Research firmware update over the air from the cloud | |
| CN111984270A (en) | Application deployment method and system | |
| CN113407208A (en) | Edge device function online configuration method based on remote deployment | |
| CN113296805A (en) | Method and device for realizing hot upgrade of auxiliary container | |
| CN101877655A (en) | Network management system, network management server and method | |
| US20220237090A1 (en) | Autonomous organization and role selection of homogenous workers | |
| US11900089B2 (en) | Automatically configuring and deploying a software operator in a distributed computing environment from a package | |
| CN114356504A (en) | Data migration method and device in cluster, electronic equipment and storage medium | |
| EP4162649B1 (en) | Stable references for network function life cycle management automation | |
| JP2024501005A (en) | Management method and device for container clusters | |
| JP2015099547A (en) | Software update method, software update apparatus, software update program, and software update system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 40032350 Country of ref document: HK |
|
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |