CN114090022A - System deployment method, device, equipment and computer storage medium - Google Patents
System deployment method, device, equipment and computer storage medium Download PDFInfo
- Publication number
- CN114090022A CN114090022A CN202111440008.6A CN202111440008A CN114090022A CN 114090022 A CN114090022 A CN 114090022A CN 202111440008 A CN202111440008 A CN 202111440008A CN 114090022 A CN114090022 A CN 114090022A
- Authority
- CN
- China
- Prior art keywords
- version
- service
- node
- configuration item
- nodes
- 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.)
- Pending
Links
Images
Classifications
-
- 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/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
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 embodiment of the application provides a system deployment method, a system deployment device, system deployment equipment and a computer storage medium. The method comprises the following steps: setting a blue-green version configuration item, wherein the blue-green version configuration item comprises a first configuration item; determining that a service cluster node with a first version is deployed to correspond to a first node of a registry and a service cluster node without the first version is not deployed to correspond to a second node of the registry based on an expanded load balancing strategy; and deploying the service of the second version to the cluster node corresponding to the second node of the registry through the first configuration item. According to the system deployment method, deployment of different versions can be achieved on different registration nodes of the same registration center, and resource waste is avoided.
Description
Technical Field
The present application relates to the field of distributed system technologies, and in particular, to a system deployment method, apparatus, device, and computer storage medium.
Background
At present, with the rapid development of services, the traditional single application cannot be satisfied, and thus a distributed architecture appears. In a distributed architecture, different services are distributed in different application services, and when upgrading operation is performed, the change of an interface protocol between the application services needs to control that applications of different versions cannot be mutually called, otherwise, the problem of errors caused by protocol mismatching can occur.
When the existing technical scheme is used for upgrading a distributed system, only application services of the same version can be mutually called by adopting a blue-green deployed upgrading strategy. Specifically, a new registry is deployed while a new version application service is deployed, and the new version application service is deployed on the new registry, so that the isolation of applications of different versions is realized, and the problem of errors caused by mutual calling of the applications of different versions is avoided. However, the above method not only needs to perform new service resource allocation, but also needs twice of server resources, which causes resource waste.
Disclosure of Invention
Embodiments of the present application provide a system deployment method, apparatus, device, computer storage medium, and computer program product, which can implement service nodes under different nodes of the same registry to deploy services of different versions through an extended load balancing policy, thereby reducing resource waste.
In a first aspect, an embodiment of the present application provides a system deployment method, including:
setting a blue-green version configuration item, wherein the blue-green version configuration item comprises a first configuration item;
determining that a service cluster node with a first version is deployed to correspond to a first node of a registry and a service cluster node without the first version is not deployed to correspond to a second node of the registry based on an expanded load balancing strategy;
deploying a second version of service to a cluster node corresponding to a second node of the registry through the first configuration item;
wherein the second version is higher than the first version.
According to one aspect of the application, the blue-green version configuration items further include a second configuration item; and offline all the nodes of the service cluster of the first version corresponding to the first node of the registry through the second configuration item.
According to an aspect of the present application, deploying a second version of service to a service cluster node corresponding to a second node of a registry through a first configuration item further includes:
when the flow of the first version service is lower than a preset threshold value, the first preset number of nodes of the first version service cluster nodes are offline through the second configuration item;
deploying second version services for cluster nodes of a first preset number of second nodes of the registry through the first configuration items, wherein the cluster nodes of the first preset number of the second nodes of the registry are nodes of a first preset number of first version service clusters;
the nodes of the second preset number of the first version service cluster are offline through the second configuration items;
deploying a second version service for a second preset number of cluster nodes of a second node of the registry through the first configuration item;
the sum of the first preset number and the second preset number is the number of cluster nodes deploying the first version service.
According to one aspect of the application, the method further comprises:
suspending service of the first version of the service cluster node;
the service of the second version of the service cluster node is initiated.
In a second aspect, an embodiment of the present application provides a system deployment apparatus, where the apparatus includes:
the setting module is used for setting blue-green version configuration items, and the blue-green version configuration items comprise first configuration items;
the determining module is used for determining that the service cluster node which deploys the first version corresponds to a first node of the registry and the service cluster node which does not deploy the first version corresponds to a second node of the registry based on the expanded load balancing strategy;
the deployment module is used for deploying the service of the second version to the cluster node corresponding to the second node of the registration center through the first configuration item;
wherein the second version is higher than the first version.
According to one aspect of the application, the setting module is used for setting a blue-green version configuration item, the blue-green version configuration item comprises a first configuration item, and the blue-green version configuration item further comprises a second configuration item;
and the offline module is used for offline all the nodes of the service cluster of the first version corresponding to the first node of the registry through the second configuration item.
According to an aspect of the present application, a deployment module, configured to deploy, through a first configuration item, a second version of a service to a cluster node corresponding to a second node of a registry, includes:
the offline module is used for offline a first preset number of nodes of the first version service cluster nodes through the second configuration items when the flow of the first version service is lower than a preset threshold;
the deployment module is used for deploying second version services to a first preset number of cluster nodes of a second node of the registry through a first configuration item, wherein the first preset number of cluster nodes of the second node of the registry is the first preset number of nodes of a first version service cluster;
the offline module is further used for offline a second preset number of nodes of the first version service cluster through the second configuration items;
the deployment module is further used for deploying a second version service to a second preset number of cluster nodes of a second node of the registry through the first configuration item;
the sum of the first preset number and the second preset number is the number of cluster nodes deploying the first version service.
According to one aspect of the application, the apparatus further comprises:
a suspension module for suspending a service of a first version of a service cluster node;
and the starting module is used for starting the service of the service cluster node of the second version.
In a third aspect, an embodiment of the present application provides a system deployment apparatus, where the apparatus includes:
a processor, and a memory storing computer program instructions;
the processor reads and executes the computer program instructions to implement the system deployment method of the first aspect.
In a fourth aspect, embodiments of the present application provide a computer storage medium having computer program instructions stored thereon, where the computer program instructions, when executed by a processor, implement the system deployment method of the first aspect.
In a fifth aspect, the present application provides a computer program product, wherein instructions in the computer program product, when executed by a processor of an electronic device, cause the electronic device to perform the system deployment method of the first aspect.
According to the system deployment method, the device, the equipment, the computer storage medium and the computer program product, the configuration items are set, and the service cluster nodes of different versions corresponding to different registration centers are determined based on the expanded load balancing strategy, so that the service cluster nodes of different versions can deploy services of different versions in different nodes of the same registration center, and resource waste caused when different versions of services are deployed in different registration centers is avoided.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments of the present application will be briefly described below, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flow chart of a method for deploying a system according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a system deployment method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a system deployment method according to an embodiment of the present application;
FIG. 4 is a schematic diagram of a system deployment method according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a system deployment method according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a system deployment apparatus according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a system deployment apparatus according to an embodiment of the present application.
Detailed Description
Features and exemplary embodiments of various aspects of the present application will be described in detail below, and in order to make objects, technical solutions and advantages of the present application more apparent, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are intended to be illustrative only and are not intended to be limiting. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present application by illustrating examples thereof.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The existing blue-green deployment for the distributed architecture refers to that two versions of applications are operated at the same time, under the condition that old version services are not stopped, new version services are directly deployed, and after the new version services are operated, all traffic is switched to the new version services. When the new version service is deployed, a new registry is required to be deployed, and the new version service is registered on the new registry. The nodes of different versions of services can be isolated by registering the services of different versions on the two registration centers, and the services cannot be mutually called. However, the above method requires twice service resources in the upgrade process, which results in resource waste.
In order to solve the problems in the prior art, embodiments of the present application provide a system deployment method, apparatus, device, computer storage medium, and computer program product. First, a system deployment method provided in the embodiments of the present application will be described below.
Fig. 1 shows a flow chart of a system deployment method provided by an embodiment of the present application. As shown in fig. 1, the method may include the steps of:
s110, setting a blue-green version configuration item, wherein the blue-green version configuration item comprises a first configuration item.
In an Apollo (Apollo) configuration center, setting a first configuration item for the blue-green version, the setting the first configuration item for the blue-green version comprising: the values of the blue-green version configuration items are modified. For example, the original configuration item "version ═ 1" is modified to "version ═ 2", and the modified "version ═ 2" is the first configuration item, and the value of the first configuration item becomes effective after the service program is restarted. And the configuration item is used for the application service to carry out configuration setting according to the value of the configuration item.
S120, determining that the service cluster node with the first version corresponds to a first node of the registry and the service cluster node without the first version corresponds to a second node of the registry based on the expanded load balancing strategy.
The method comprises the steps that service nodes of the same version can be obtained through filtering based on an expanded load balancing strategy, service cluster nodes with the deployed first version correspond to first nodes of a registry, service cluster nodes without the deployed first version correspond to second nodes of the registry, and the first nodes of the registry and the second nodes of the registry are two nodes of the same registry; the expanded load balancing strategy corresponds to a load balancing strategy class.
In one example, the extended load balancing policy is "discover predicate" and the corresponding load balancing policy class is "discover rule". Service nodes of the same version can be obtained by filtering through the discovery predicate
The default load balancing strategy used in the distributed system deployment is 'ZoneAvoidenule', and the strategy carries out node filtering through a 'ZoneAvoideceredicate' method. In this strategy, the nodes served by the filter are available nodes. The extended load balancing policy "discovery predicate" defined in the embodiment of the present application is used as a default load balancing policy for all application services of the entire system, and the service nodes of the same version are obtained through filtering. The specific implementation mode is as follows: the blue-green version information of the service node is configured into the metadata of the node by means of a Spring configuration item "eruka. When a node registers with the registry, the request carries the full amount of information of the node, including metadata. When the service node and the registration center synchronize the service list, the metadata information of all the nodes can be obtained, so that the blue-green version of each service node can be known, and the version can be compared with the version of the service node when the service node and the registration center are called.
S130, deploying a second version of service to a cluster node corresponding to a second node of the registry through the first configuration item; wherein the second version is higher than the first version.
And deploying the service of the second version at the cluster node under the second node of the registry, and deploying the service of the second version through the first configuration item, namely setting a configuration value corresponding to the application service according to the configuration item value. The second version is higher than the first version, which is equivalent to that the service of the second version is a new service, and the service of the first version is an old service.
In one example, as shown in fig. 2 for the way of deploying the second version of the service, all traffic is directed to the first version of the service, the first version of the service cluster includes a server 1 and a server 2, the server 1 includes a node 1 of an application a and a node 1 of an application B, and the server 2 includes a node 2 of an application a and a node 2 of an application B. Wherein the node 1 of the application A and the node 1 of the application B, and the node 1 of the application A and the node 2 of the application B have a mutual calling relationship; node 2 of application a and node 1 of application B, node 2 of application a and node 2 of application B have a mutual calling relationship. When it is confirmed through nginx that all traffic points to the first version of the service cluster, the second version of the service is deployed on a new server where the first version of the service is not deployed, that is, the second version of the service cluster comprises a server 3 and a server 4, the server 3 comprises a node 1 of an application A and a node 1 of an application B, and the server 4 comprises a node 2 of the application A and a node 2 of the application B. Wherein the node 1 of the application A and the node 1 of the application B, and the node 1 of the application A and the node 2 of the application B have a mutual calling relationship; node 2 of application a and node 1 of application B, node 2 of application a and node 2 of application B have a mutual calling relationship. The first version service cluster realizes registration and pulling of the service list through a first node of a registration center, and the second version service cluster realizes registration and pulling of the service list through a second node of the registration center, wherein the first node of the registration center and the second node of the registration center belong to the same registration center cluster. Wherein all traffic directed to the first version of the service cluster specifically means that the first version of the service cluster provides all services of the server.
The system deployment method provided by the embodiment of the application can realize that the service cluster nodes under different nodes of the same registry deploy services of different versions through an expanded load balancing strategy, and avoids resource waste caused when different registries deploy services of different versions.
In some embodiments, the blue-green version configuration items further comprise a second configuration item; and offline all the nodes of the service cluster of the first version corresponding to the first node of the registry through the second configuration item. The Apollo configuration center further comprises a second configuration item, and the second configuration item corresponds to the configuration of the service cluster node of the first version. After the second version of service is deployed, the cluster nodes of the deployed first version of service are offline, and at the moment, the registry only runs the second version of service.
In one example, the second configuration item is "version-v 1", the modified first configuration item is "version-2", that is, the first version of the service is v1, and the second version of the service is v 2.
In some embodiments, the configuration item name and value may be customized when setting the configuration item, such as "version ═ v 1". According to the configuration item "eureka.instance.metadata-map" provided by Spring, one more configuration item "eureka.instance.metadata-map" version "v 1" is added. When the service node sends a registration request to the registry, a key-value pair under "origin. When other service nodes synchronize service lists with the registration center, metadata information of all the nodes can be obtained, so that the blue-green version of each service node can be known and can be compared with the version of the service node when being called.
In some embodiments, before taking the cluster node of the deployed first version of service offline, the deployed second version of service needs to be verified, that is, the deployed second version of service is started, and after the deployed second version of service can normally operate, the deployed cluster node of the first version of service is taken offline. And if the deployed second version service cannot normally run, switching to the first version service, completing upgrade rollback, and re-deploying the second version service.
In some embodiments, deploying, by the first configuration item, a second version of the service to a service cluster node corresponding to a second node of the registry further includes: when the flow of the first version of service is lower than a preset threshold value, offline a first preset number of nodes of the first version of service cluster nodes through a second configuration item; deploying second version services for cluster nodes of a first preset number of second nodes of the registry through the first configuration item, wherein the cluster nodes of the first preset number of the second nodes of the registry are nodes of the first preset number of service clusters of the first version; offline a second preset number of nodes of the service cluster of the first version through a second configuration item; deploying a second version service for a second preset number of cluster nodes of a second node of the registry through the first configuration item; the sum of the first preset number and the second preset number is the number of cluster nodes deploying the first version of service. When the traffic of the first version of service is lower than the preset threshold, which is a traffic low peak period, the first preset number of nodes of the first version of service cluster nodes are offline, and all traffic points to the first version of service. And deploying the second version service at the nodes of the first preset number of offline nodes, and then, downloading the nodes of the first version of offline and the second preset number of offline nodes. And deploying the second version service at a second preset number of nodes of the offline first version, wherein the second version service is deployed at the moment.
In one embodiment, all traffic is directed to the first version of the service, the first version of the service cluster comprises server 1 and server 2, node 1 of application a and node 1 of application B are included in server 1, and node 2 of application a and node 2 of application B are included in server 2. Wherein the node 1 of the application A and the node 1 of the application B, and the node 1 of the application A and the node 2 of the application B have a mutual calling relationship; node 2 of application a and node 1 of application B, node 2 of application a and node 2 of application B have a mutual calling relationship. As shown in fig. 3, in the second version of service deployment manner, half of the nodes of the service cluster of the first version are offline, that is, the nodes of the server 2 are offline, all traffic points to the remaining half of the nodes, that is, the nodes of the server 1, and the second version of service is deployed at the offline half of the nodes, and at this time, deployment of half of the nodes of the second version of service is completed. Then, as shown in fig. 4, the remaining half number of nodes of the first version of the service are down-lined, and all traffic is now directed to the half number of nodes where the second version of the service has been deployed. As shown in fig. 5, the second version of service is deployed on the remaining half of the number of nodes, at which time the second version of service completes deployment and all traffic is directed to all nodes of the second version of service.
In some embodiments, the method further comprises: suspending service of the first version of the service cluster node; the service of the second version of the service cluster node is initiated. After the deployment of the second version service is finished, suspending the service of the service cluster node of the first version; and starting the service of the service cluster node of the second version, and finishing the initialization of the application through the first configuration item when the service of the second version is started.
According to the system deployment method provided by the embodiment of the application, the service cluster nodes of different versions are determined through the expanded load balancing strategy, the service cluster nodes of different versions correspond to different registry nodes, deployment of new version services is achieved through configuration items, a scheme of blue-green deployment can be completed in one registry, and resource waste is reduced.
Fig. 6 is a schematic structural diagram of an apparatus according to an embodiment of the present disclosure. As shown in fig. 6, the apparatus 600 may include a setup module 610, a determination module 620, and a deployment module 630.
A setting module 610 for setting a blue-green version configuration item, the blue-green version configuration item including a first configuration item.
The determining module 620 is configured to determine, based on the extended load balancing policy, that the service cluster node deployed with the first version corresponds to a first node of the registry, and that the service cluster node not deployed with the first version corresponds to a second node of the registry.
And the deploying module 630 is configured to deploy, through the first configuration item, the service of the second version to the cluster node corresponding to the second node of the registry.
Wherein the second version is higher than the first version.
The system deployment device 600 provided by the embodiment of the application can implement that the service cluster nodes under different nodes of the same registry deploy services of different versions through an extended load balancing strategy, thereby avoiding resource waste caused when different registries deploy services of different versions.
In some embodiments, the setup module 610 is configured to setup a blue-green version configuration item, the blue-green version configuration item comprising a first configuration item, the blue-green version configuration item further comprising a second configuration item; and the offline module 640 is configured to offline all nodes of the service cluster of the first version corresponding to the first node of the registry through the second configuration item.
In some embodiments, the deploying module 630 is configured to deploy, through the first configuration item, the second version of the service to the cluster node corresponding to the second node of the registry, and includes: the offline module 640 is configured to offline a first preset number of nodes of the first version service cluster node through the second configuration item when the traffic of the first version service is lower than a preset threshold; a deployment module 630, configured to deploy, by using the first configuration item, the second version service to the first preset number of cluster nodes of the second node of the registry, where the first preset number of cluster nodes of the second node of the registry is the first preset number of nodes of the first version service cluster; the offline module 640 is further configured to offline a second preset number of nodes of the first version service cluster through the second configuration item; the deployment module 630 is further configured to deploy, through the first configuration item, a second version service to a second preset number of cluster nodes of a second node of the registry; the sum of the first preset number and the second preset number is the number of cluster nodes deploying the first version service.
In some embodiments, the apparatus further comprises: a suspending module 650 for suspending the service of the first version of the service cluster node; a starting module 660, configured to start the service of the service cluster node of the second version.
The system deployment device provided by the embodiment of the application can enable service nodes of different versions not to be mutually called based on the expanded load balancing strategy, further realize isolation of services of different versions, enable the services of different versions to correspond to different nodes of the same registry cluster, and deploy the services of a second version, so that resource waste is reduced.
Each module in the apparatus shown in fig. 6 has a function of implementing each step executed by the system deployment method in fig. 1, and can achieve its corresponding technical effect, and for brevity, it is not described herein again.
Fig. 7 shows a hardware structure diagram of a system deployment device provided in an embodiment of the present application.
The system deployment device may comprise a processor 701 and a memory 702 storing computer program instructions.
Specifically, the processor 701 may include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement the embodiments of the present Application.
In one example, memory 702 may include Read Only Memory (ROM), Random Access Memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical/tangible memory storage devices. Thus, in general, the memory 702 comprises one or more tangible (non-transitory) computer-readable storage media (e.g., a memory device) encoded with software comprising computer-executable instructions and when the software is executed (e.g., by one or more processors), it is operable to perform operations described with reference to the methods according to an aspect of the present application.
The processor 701 reads and executes the computer program instructions stored in the memory 702 to implement the methods/steps S110 to S130 in the embodiment shown in fig. 1, and achieve the corresponding technical effects achieved by the embodiment shown in fig. 1 executing the methods/steps thereof, which are not described herein again for brevity.
In one example, the system deployment device may also include a communication interface 703 and a bus 710. As shown in fig. 7, the processor 701, the memory 702, and the communication interface 703 are connected by a bus 710 to complete mutual communication.
The communication interface 703 is mainly used for implementing communication between modules, apparatuses, units and/or devices in this embodiment of the application.
The system deployment device may execute the system deployment method in the embodiment of the present application based on the extended load balancing policy, thereby implementing the system deployment method described in conjunction with fig. 1.
In addition, in combination with the system deployment method in the foregoing embodiments, the embodiments of the present application may be implemented by providing a computer storage medium. The computer storage medium having computer program instructions stored thereon; the computer program instructions, when executed by a processor, implement any of the system deployment methods of the embodiments described above.
In addition, the present application embodiment may provide a computer program product in combination with the system deployment method in the foregoing embodiment. The instructions in the computer program product, when executed by a processor of an electronic device, cause the electronic device to perform any of the system-deployment methods of the embodiments described above.
It is to be understood that the present application is not limited to the particular arrangements and instrumentality described above and shown in the attached drawings. A detailed description of known methods is omitted herein for the sake of brevity. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present application are not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications, and additions or change the order between the steps after comprehending the spirit of the present application.
The functional blocks shown in the above structural block diagrams may be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic Circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, plug-in, function card, or the like. When implemented in software, the elements of the present application are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine-readable medium or transmitted by a data signal carried in a carrier wave over a transmission medium or a communication link. A "machine-readable medium" may include any medium that can store or transfer information. Examples of a machine-readable medium include electronic circuits, semiconductor memory devices, ROM, flash memory, Erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, Radio Frequency (RF) links, and so forth. The code segments may be downloaded via computer networks such as the internet, intranet, etc.
It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, may be performed in an order different from the order in the embodiments, or may be performed simultaneously.
Aspects of the present application are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware for performing the specified functions or acts, or combinations of special purpose hardware and computer instructions.
As will be apparent to those skilled in the art, for convenience and brevity of description, the specific working processes of the systems, modules and units described above may refer to corresponding processes in the foregoing method embodiments, and are not described herein again. It should be understood that the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present application, and these modifications or substitutions should be covered within the scope of the present application.
Claims (11)
1. A method of system deployment, comprising:
setting a blue-green version configuration item, wherein the blue-green version configuration item comprises a first configuration item;
determining that a service cluster node with a first version is deployed to correspond to a first node of a registry and a service cluster node without the first version is not deployed to correspond to a second node of the registry based on an expanded load balancing strategy;
deploying a second version of service to a cluster node corresponding to a second node of the registry through the first configuration item;
wherein the second version is higher than the first version.
2. The method of claim 1, wherein the blue-green version configuration items further comprise a second configuration item; and offline all the nodes of the service cluster of the first version corresponding to the first node of the registry through the second configuration item.
3. The method of claim 2, wherein deploying the second version of the service to the service cluster node corresponding to the second node of the registry through the first configuration item further comprises:
when the flow of the first version service is lower than a preset threshold value, the first preset number of nodes of the first version service cluster nodes are offline through the second configuration item;
deploying second version services to a first preset number of cluster nodes of a second node of a registry through a first configuration item, wherein the first preset number of cluster nodes of the second node of the registry are the first preset number of nodes of a first version service cluster;
offline a second preset number of nodes of the first version service cluster through a second configuration item;
deploying a second version service for a second preset number of cluster nodes of a second node of the registry through the first configuration item;
the sum of the first preset number and the second preset number is the number of cluster nodes deploying the first version service.
4. The method of claim 1, further comprising:
suspending service of the first version of the service cluster node;
the service of the second version of the service cluster node is initiated.
5. A system deployment apparatus, the apparatus comprising:
the device comprises a setting module, a setting module and a control module, wherein the setting module is used for setting blue-green version configuration items, and the blue-green version configuration items comprise a first configuration item;
the determining module is used for determining that the service cluster node which deploys the first version corresponds to a first node of the registry and the service cluster node which does not deploy the first version corresponds to a second node of the registry based on the expanded load balancing strategy;
the deployment module is used for deploying the service of the second version to the cluster node corresponding to the second node of the registration center through the first configuration item;
wherein the second version is higher than the first version.
6. The apparatus of claim 5, wherein the setup module is configured to setup a blue-green version configuration item, the blue-green version configuration item comprising a first configuration item, the blue-green version configuration item further comprising a second configuration item;
and the offline module is used for offline all the nodes of the service cluster of the first version corresponding to the first node of the registry through the second configuration item.
7. The apparatus of claim 6, wherein the deploying module is configured to deploy the second version of the service to a cluster node corresponding to a second node of the registry through the first configuration item, and comprises:
the offline module is used for offline a first preset number of nodes of the first version service cluster nodes through a second configuration item when the flow of the first version service is lower than a preset threshold;
the deployment module is used for deploying second version services to a first preset number of cluster nodes of a second node of a registry through a first configuration item, wherein the first preset number of cluster nodes of the second node of the registry is the first preset number of nodes of the first version service cluster;
the offline module is further configured to offline a second preset number of nodes of the first version service cluster through a second configuration item;
the deployment module is further configured to deploy a second version service to a second preset number of cluster nodes of a second node of the registry through the first configuration item;
the sum of the first preset number and the second preset number is the number of cluster nodes deploying the first version service.
8. The apparatus of claim 5, further comprising:
a suspension module for suspending a service of a first version of a service cluster node;
and the starting module is used for starting the service of the service cluster node of the second version.
9. A system deployment device, the system deployment device comprising: a processor, and a memory storing computer program instructions;
the processor reads and executes the computer program instructions to implement the system deployment method of any one of claims 1-4.
10. A computer storage medium having computer program instructions stored thereon that, when executed by a processor, implement the system deployment method of any one of claims 1-4.
11. A computer program product, wherein instructions in the computer program product, when executed by a processor of an electronic device, cause the electronic device to perform the system deployment method of any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111440008.6A CN114090022A (en) | 2021-11-30 | 2021-11-30 | System deployment method, device, equipment and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111440008.6A CN114090022A (en) | 2021-11-30 | 2021-11-30 | System deployment method, device, equipment and computer storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114090022A true CN114090022A (en) | 2022-02-25 |
Family
ID=80305685
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111440008.6A Pending CN114090022A (en) | 2021-11-30 | 2021-11-30 | System deployment method, device, equipment and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114090022A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115378808A (en) * | 2022-08-16 | 2022-11-22 | 广州骏伯网络科技有限公司 | Method for realizing blue-green release by using iptables |
-
2021
- 2021-11-30 CN CN202111440008.6A patent/CN114090022A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115378808A (en) * | 2022-08-16 | 2022-11-22 | 广州骏伯网络科技有限公司 | Method for realizing blue-green release by using iptables |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108876619B (en) | Processing method, device, equipment and medium based on block chain intelligent contract | |
| CN114090022A (en) | System deployment method, device, equipment and computer storage medium | |
| CN111837374A (en) | Method and apparatus for registering API provider domain functional entities on CAPIF core functional entities | |
| WO2021136233A1 (en) | Service upgrading method, device and system | |
| CN114185678A (en) | Data storage method, device, equipment and storage medium | |
| CN114385386A (en) | Method, device, equipment and storage medium for calling micro-service | |
| CN114884912A (en) | Communication method, system, equipment and computer readable storage medium of SOA architecture | |
| CN109120680B (en) | Control system, method and related equipment | |
| CN111131131B (en) | Vulnerability scanning method and device, server and readable storage medium | |
| CN108073460B (en) | Global lock preemption method and device in distributed system and computing equipment | |
| CN111343220B (en) | Repeater, distributed file transmission method, distributed file transmission system, medium and electronic equipment | |
| CN111399866B (en) | Updating method and device of VNF (virtual network function) package | |
| CN115495195A (en) | Data processing method and device and related equipment | |
| CN114637525A (en) | Method, device, equipment and medium for compatibility of SDK and access application | |
| CN113050978B (en) | Gray release control method, device and equipment for application and computer storage medium | |
| CN107454021B (en) | Communication method and device | |
| CN113285888A (en) | Multi-service system multi-data center shunting method, device, equipment and medium | |
| CN114422295B (en) | Network information processing method, electronic equipment and storage medium | |
| CN104657168A (en) | Client side and method for upgrading client side | |
| CN117908924A (en) | Operating system version updating method, device and equipment | |
| CN114327542B (en) | Service equipment updating method and device, electronic equipment and storage medium | |
| CN114071648B (en) | Information configuration method, device, equipment and medium | |
| CN117950699A (en) | System upgrading method and device and hardware platform | |
| CN115941386A (en) | Vehicle-mounted Ethernet ring network data redundancy processing method, device, equipment and medium | |
| CN114710550A (en) | Request response method, device, equipment and computer storage medium |
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 |