CN106354531A - Physical node upgrading method and device - Google Patents

Physical node upgrading method and device Download PDF

Info

Publication number
CN106354531A
CN106354531A CN201610734647.6A CN201610734647A CN106354531A CN 106354531 A CN106354531 A CN 106354531A CN 201610734647 A CN201610734647 A CN 201610734647A CN 106354531 A CN106354531 A CN 106354531A
Authority
CN
China
Prior art keywords
physical node
service instance
physical
node
batch
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.)
Granted
Application number
CN201610734647.6A
Other languages
Chinese (zh)
Other versions
CN106354531B (en
Inventor
郭家发
李健
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Huawei Cloud Computing Technology Co ltd
Original Assignee
Hangzhou Huawei Digital Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hangzhou Huawei Digital Technologies Co Ltd filed Critical Hangzhou Huawei Digital Technologies Co Ltd
Priority to CN201610734647.6A priority Critical patent/CN106354531B/en
Publication of CN106354531A publication Critical patent/CN106354531A/en
Application granted granted Critical
Publication of CN106354531B publication Critical patent/CN106354531B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network

Abstract

The invention discloses a physical node upgrading method and a device. The method comprises the steps of determining the ithphysical node among the physical nodes not upgraded; upgrading the ithbatch of physical node; after upgrading completion, detecting the non-upgraded physical node existence; if non-upgraded physical nodes still exist, make i=i+1, and re-implement the steps of determining the ithbatch of physical node from the non-upgraded physical nodes, which solves the problem of the whole distributed system failing to provide external service under current technology when all physical hosts restart upgrading simultaneously, and long service interrupt duration when the upgrading duration is relatively long; and the physical node upgrading method and device achieves the effect of no service interrupt and that other physical nodes can still provide external service except the current batch when each batch of physical node is upgrading, and for upgrading the multiple physical nodes according to different batches.

Description

Physical node upgrade method and device
Technical field
The present embodiments relate to computer realm, particularly to a kind of physical node upgrade method and device.
Background technology
Openstack distributed computing system is a cloud computing management platform project increased income.Openstack is distributed Computing system includes multiple physical hosts, and each physical host runs several Service Instances.Same Service Instance can To dispose two with active/standby mode on different physical hosts, or, disposed multiple with load balancing mode.
When operating system is because of reason upgradings such as version updating, security breaches, driving renewals, need to restart physical host Upgrading.Restart in escalation process in physical host, the virtual machine on physical host will be unable to externally provide service.In prior art Conventional upgrade method is: all of physical host is restarted upgrading simultaneously.
Obviously, when all physical hosts restart upgrading simultaneously, whole distributed computing system all cannot externally provide clothes Business.And the duration due to service disruption is identical with upgrading duration, if upgrading duration is longer, the duration of service disruption also can Very long.
Content of the invention
In order to solve in prior art when all physical hosts restart upgrading simultaneously, when the duration of service disruption and upgrading Longer problem, embodiments provides a kind of physical node upgrade method and device.Technical scheme is as follows:
The physical node upgrade method that each embodiment of the present invention provides and device are used in distributed computing system, this point Cloth computing system includes management terminal and physical node, and wherein management terminal is used for the ruuning situation to each physical node It is managed, physical node is used for running at least one Service Instance, each Service Instance is used for providing one or more service.
A kind of first aspect, there is provided physical node upgrade method, this physical node upgrade method includes:
Never determine i-th batch of physical node in the physical node of upgrading, in its in addition to described i-th batch of physical node The Service Instance of all categories is included, i is integer in the described Service Instance running in its physical node;
Described i-th batch of physical node is upgraded;
After upgrading finishes, detect whether the physical node do not upgraded described in also existing;
If the physical node do not upgraded described in also existing, make i=i+1, re-execute described in never upgrading physical node In determine the step of i-th batch of physical node.
Scheme shown in the embodiment of the present invention, determines i-th batch of physical node in the physical node by never upgrading;Right I-th batch of physical node is upgraded;After upgrading finishes, detect whether also there is the physical node do not upgraded;If also existing not The physical node of upgrading, makes i=i+1, determines the step of i-th batch of physical node in the physical node re-executing never upgrading Suddenly;Solve in prior art when all physical hosts restart upgrading simultaneously, whole distributed system all cannot externally provide Service, and the duration of service disruption also can very long problem when duration of upgrading is longer;Reach multiple physical nodes according to not Same batch is upgraded, and, in upgrading, the other physical nodes in addition to present lot are still for the physical node of each batch Can be provided out servicing, the effect that service will not be interrupted.
In the first embodiment of first aspect, never determine i-th batch of physical node in the physical node of upgrading, Including: determine the first physical node from the described physical node do not upgraded;Described first physical node is added to described I-th batch of physical node;According to predefined procedure detect one by one described in the physical node do not upgraded except described first physical node it Whether outer remaining physical node meets anti-affinity condition, and described anti-affinity condition includes: present physical node runs The physical node set that the described kth kind Service Instance running in kth kind Service Instance and described i-th batch of physical node is constituted It is not the complete or collected works of described kth kind Service Instance, k is integer;If meeting described anti-affinity condition, by described residue physics section Point adds to described i-th batch of physical node.
Whether the scheme shown in the embodiment of the present invention, meet anti-affinity condition by each physical node of dynamic detection, Whole physical nodes are upgraded in batches it is ensured that physical node escalation process interrupts externally servicing;Make each batch Physical node in upgrading, the other physical nodes in addition to present lot remain able to be provided out service, and service will not The effect interrupted.
In conjunction with the first possible embodiment of first aspect or first aspect, in the possible embodiment of second In, described from the described physical node do not upgraded, determine the first physical node, comprising: calculate the thing do not upgraded described in each The instance number of the standby Service Instance running in reason node;By physical nodes most for the instance number of described standby Service Instance, determine For described first physical node.
Possible in conjunction with the second of first aspect, the first possible embodiment of first aspect or first aspect Embodiment, in the third possible embodiment, the method also includes: the master that will run in described i-th batch of physical node Service Instance carries out masterslave switchover with the standby Service Instance of operation in described other physical node.
Scheme shown in the embodiment of the present invention, by having the most physical node of standby Service Instance to be defined as first operation Physical node, so that needing the Service Instance carrying out masterslave switchover to be minimum, can reduce the clothes that masterslave switchover process is brought Business interruption times, reduce out of service time as far as possible.
In conjunction with the possible reality of the second of first aspect, the first possible embodiment of first aspect, first aspect Apply the third possible embodiment of mode or first aspect, in the 4th kind of possible embodiment, the method is also wrapped Include: for each Service Instance, in the other physical nodes in addition to described i-th batch of physical node, detect whether exist It is in the Service Instance of upstate;If each Service Instance all has the Service Instance being in upstate, execute institute State the step that described i-th batch of physical node is upgraded.
Scheme shown in the embodiment of the present invention, also by before upgrading to i-th batch of Service Instance, to each type of The availability of Service Instance is judged;Avoid being in malfunction so that the type in escalation process because of certain Service Instance The disabled problem of Service Instance, prevent produced service disruption in the escalation process of physical node.
Second aspect, embodiments provides a kind of physical node update device, this physical node update device bag Include at least one unit, this at least one unit is used for realizing any one possible design in above-mentioned first aspect or the first face Provided in physical node upgrade method.
The third aspect, the embodiment of the present invention provides a kind of terminal, and this terminal includes processor and memorizer;Described processor For storing one or more instruction, described instruction is indicated as by described computing device, and described processor is used for Realize the physical node upgrade method provided in any one possible design in above-mentioned first aspect or first aspect.
Fourth aspect, embodiments provides a kind of computer-readable recording medium, this computer-readable storage medium It is stored with matter for realizing the physical node that in above-mentioned first aspect or first aspect, any one possible design is provided The executable program of upgrade method.
The technique effect that the second aspect of the embodiments of the present invention is obtained to fourth aspect is corresponding with first aspect The technique effect that obtains of technological means approximate, repeat no more here.
It should be appreciated that above general description and detailed description hereinafter are only illustrative, can not be limited this Invention.
Brief description
Fig. 1 shows a kind of Organization Chart of distributed computing system that one embodiment of the invention provides;
Fig. 2 shows a kind of Organization Chart of distributed computing system that another embodiment of the present invention provides;
Fig. 3 is the principle schematic of the physical node upgrade method providing in one embodiment of the invention;
Fig. 4 is the principle schematic of the physical node upgrade method providing in one embodiment of the invention;
Fig. 5 is the principle schematic of the physical node upgrade method providing in another embodiment of the present invention;
Fig. 6 a and Fig. 6 b is the principle schematic of the physical node upgrade method providing in another embodiment of the present invention;
Fig. 7 a and Fig. 7 b is the principle schematic of the physical node upgrade method providing in further embodiment of the present invention;
Fig. 8 is the block diagram of the physical node update device that one embodiment of the invention provides;
Fig. 9 is the block diagram of the physical node update device that another embodiment of the present invention provides;
Figure 10 is the management terminal of one embodiment of the invention offer or the structural representation of physical node.
Specific embodiment
For making the object, technical solutions and advantages of the present invention clearer, below in conjunction with accompanying drawing to embodiment party of the present invention Formula is described in further detail.
Fig. 1 shows a kind of structural representation of distributed computing system that one embodiment of the invention provides.This distribution Formula computing system includes: management terminal 120 and physical node 140.
Management terminal 120 is the equipment of such as pocket computer on knee, desk computer, mobile phone, panel computer etc. Management terminal 120 is used for the ruuning situation of each physical node 140 is managed.Schematically, when physical node 140 needs Carry out operating system upgrading when, management terminal 120 control each physical node 140 upgraded.
Management terminal 120 is connected with physical node 140 by network 160.This network 160 can be cable network or light Fibre web network.
Physical node 140 is the server with hardware entities, such as: single-board server.In distributed computing system, The number of physical node 140 is usually multiple.In FIG, only to be illustrated with the number of physical node 140 for three.
Running on each physical node 140 has at least one Service Instance 142, and each Service Instance 142 is used for offer one Plant or multiple service.Alternatively, Service Instance 142 is any one in thread, process, container and virtual machine (vmware, vm) Kind.
Schematically, when distributed computing system is openstack distributed computing system, physical node 140 is single Plate server, Service Instance 142 is virtual machine.
Generally, same type of Service Instance 142 is disposed on two physical nodes 140 with active and standby form, such as: Main Service Instance 142 is deployed on a physical node 140, and standby Service Instance 142 is deployed on another physical node 140. And/or, same type of Service Instance 142 is disposed on different physical nodes 140 with load balancing form, such as same 3 Service Instances 142 of type are deployed on three different physical nodes 140 respectively.
Fig. 2 shows a kind of structural representation of distributed computing system that another embodiment of the present invention provides.This point Cloth computing system includes: the multiple physical nodes being connected by network 160.So that physical node is 5 as a example, physical node bag Include: physical node 1, physical node 2, physical node 3, physical node 4 and physical node 5.
Each physical node is the server with hardware entities, such as: single-board server.
Running on each physical node has at least one Service Instance, and each Service Instance is used for providing one or more clothes Business.Alternatively, Service Instance is any one in thread, process, container and virtual machine (vmware, vm).Generally:
Same type of Service Instance is disposed on two physical nodes with active and standby form.In fig. 2, a represents main service Example, for Service Instance, Service Instance 1-a is the main Service Instance of first kind Service Instance to behalf, and Service Instance 1-s is The standby Service Instance of one class Service Instance;Service Instance 3-a is the main Service Instance of the 3rd class Service Instance, Service Instance 3-s It is the standby Service Instance of the 3rd class Service Instance;Service Instance 4-a is the main Service Instance of the 4th class Service Instance, Service Instance 4-s is the standby Service Instance of the 4th class Service Instance;Service Instance 6-a is the main Service Instance of the 6th class Service Instance, service Example 6-s is the standby Service Instance of the 6th class Service Instance.
And/or, same type of Service Instance is disposed on different physical nodes with load balancing form.In fig. 2, Equations of The Second Kind Service Instance includes 5 Service Instances: Service Instance 2-1, Service Instance 2-2, Service Instance 2-3, Service Instance 2- 4th, Service Instance 2-5, each physical node is deployed with an Equations of The Second Kind Service Instance;5th class Service Instance includes 4 Service Instance: Service Instance 5-1, Service Instance 5-2, Service Instance 5-3, Service Instance 5-4, Service Instance 5-1 is deployed in thing Reason node 2, Service Instance 5-2 is deployed in physical node 3, and Service Instance 5-3 is deployed in physical node 4, and Service Instance 5-4 disposes In physical node 5.
From unlike Fig. 1, the distributed computing system in Fig. 2 does not need management node, schematically, works as physical node When needing the upgrading carrying out operating system, each physical node 140 is controlled to enter by the Service Instance 1-a for being responsible for upgrade service Row upgrading.
Herein, by management terminal and/or be used for being responsible for the Service Instance of upgrade service and be referred to as management end.That is, This management end can be physical entity or logic entity.
Refer to Fig. 3, the flow chart that the physical node upgrade method of one embodiment of the invention offer is provided.This reality Apply example to be applied in management end be illustrated with this physical node upgrade method.This physical node upgrade method, comprising:
I-th batch of physical node is determined in the physical node of step 301, never upgrading.
Alternatively, include complete in the Service Instance running in the other physical nodes in addition to i-th batch of physical node The Service Instance of portion's species, the initial value for integer and i for the i is 0 or 1.
Assume that distributed computing system includes n physical node, i-th batch of physical node is k physical node, then except the Other physical nodes outside i criticizes physical node are n-k.The physical node that other physical nodes are not possibly upgraded, also may be used It can be the promoted physical node finishing.
But, in this other physical node, include the Service Instance of all categories.If that is, distributed computing system Middle operation has m kind Service Instance, then running in other physical nodes has m kind Service Instance, and each Service Instance is at least deposited In a Service Instance being in upstate.
Step 302, upgrades to i-th batch of physical node.
Step 303, after upgrading finishes, detects whether also there is the physical node do not upgraded.
Step 304, if also there is the physical node do not upgraded, makes i=i+1, re-executes the physical node of never upgrading In determine the step of i-th batch of physical node.
If there is not the physical node do not upgraded it is determined that upgrading finishes.
In sum, the physical node upgrade method that the present embodiment provides, by determining in the physical node of never upgrading Go out i-th batch of physical node;I-th batch of physical node is upgraded;After upgrading finishes, detect whether also there is the thing do not upgraded Reason node;If also there is the physical node do not upgraded, making i=i+1, in the physical node re-executing never upgrading, determining The step that i criticizes physical node;Solve in prior art when all physical hosts restart upgrading simultaneously, whole distributed system Service all cannot be externally provided, and the duration of service disruption also can very long problem when duration of upgrading is longer;Having reached will be multiple Physical node is upgraded according to different batches, the physical node of each batch in upgrading, its in addition to present lot Its physical node remains able to be provided out servicing, the effect that service will not be interrupted.
Refer to Fig. 4, the flow chart that the physical node upgrade method of another embodiment of the present invention offer is provided.This Embodiment is applied in management end be illustrated with this physical node upgrade method.This physical node upgrade method, comprising:
Step 401, management end calculates the instance number of the standby Service Instance running in the physical node that each is not upgraded.
Include multiple physical nodes in distributed computing system, each physical node runs has at least one service real Example, same Service Instance is multiple according to main and standby relation or load balancing relational deployment in different physical nodes.
In the escalation process that operating system is carried out to physical node, the physical node of different batches can be upgraded successively. When determining the physical node that i-th batch needs upgrading, need to determine the first physical node first.Alternatively, the initial value of i is 1.
So that each physical node in Fig. 2 is upgraded as a example, management end calculates the standby clothes running in 5 physical nodes The instance number of pragmatic example, result of calculation is: running on physical node 1 to have to run on 1 standby Service Instance, physical node 2 has 1 Run on standby Service Instance, physical node 3 to have to run on 2 standby Service Instances, physical node 4 and physical node 5 and have 0 standby clothes Pragmatic example.
Therefore, management end be calculated on physical node 3 run standby Service Instance instance number most.
Step 402, management end, by physical nodes most for the instance number of standby Service Instance, is defined as the first physical node.
Schematically, physical node 3 is defined as the first physical node by management end.
Step 403, management end adds the first physical node to i-th batch of physical node.
Schematically, management end adds physical node 3 to first physical node.First physical node is first Need the physical node of upgrading.
Step 404, management end detects in the physical node do not upgraded in addition to the i-th physical node according to predefined procedure one by one Remaining physical node whether meet anti-affinity condition.
Alternatively, anti-affinity condition includes: kth kind Service Instance and i-th batch of physics section that present physical node runs The physical node set that the kth kind Service Instance running in point is constituted is not the complete or collected works of kth kind Service Instance, and k is integer.
In other words, anti-affinity condition includes: the main Service Instance of same Service Instance and standby Service Instance can not Upgraded in a collection of physical node simultaneously, belonged to each Service Instance of the same Service Instance of load balancing relation Can not be upgraded in a collection of physical node simultaneously.
Alternatively, according to the order that the numbering of physical node is incremented by, management end detects do not upgrade physical node whether one by one Meet anti-affinity condition;Or, management end detects, according to the order that the numbering of physical node is successively decreased, the physics do not upgraded one by one Whether node meets anti-affinity condition
, whether management end accords with to physical node 5, physical node 4, physical node 2 and physical node 1 successively taking Fig. 2 as a example Close anti-affinity condition to be detected.
If meeting anti-affinity condition, enter step 405;If not meeting anti-affinity condition, enter step 406.
Step 405, if meeting anti-affinity condition, management end adds this remaining physical node to i-th batch of physics section Point.
Step 406, if not meeting anti-affinity condition, this remaining physical node is retained in the thing do not upgraded by management end In reason node;
As a example distributed computing system shown in by Fig. 2, in conjunction with reference to Fig. 5:
When management end carries out anti-affinity condition inspection to physical node 5, first physical node 01 includes physics section Point 3, the Service Instance 2-3 in Service Instance 2-5 and physical node 3 in physical node 5 is only in Equations of The Second Kind Service Instance Part of service example, the Service Instance 5-2 in Service Instance 5-4 and physical node 3 in physical node 5 is only the 5th class clothes Part of service example in pragmatic example, so physical node 5 meets anti-affinity condition, management end compared with physical node 3 Physical node 5 is added to first physical node 01.
When management end carries out anti-affinity condition inspection to physical node 4, first physical node 01 includes physics section Point 3 and physical node 5, the Service Instance 6-s in Service Instance 6-a and physical node 3 in physical node 4 is the 6th class service Whole Service Instances of example, so physical node 4 is conflicted with physical node 3, physical node 4 is not inconsistent compared with physical node 3 Close anti-affinity condition, physical node 4 is continued to be left the physical node do not upgraded by management end.
When management end carries out anti-affinity condition inspection to physical node 2, first physical node 01 includes physics section Point 3 and physical node 5, in the Service Instance 2-2 in physical node 2, the Service Instance 2-3 in physical node 3, physical node 5 Service Instance 2-5 be Equations of The Second Kind Service Instance part of service example, the Service Instance 5-1 in physical node 2, physics section Service Instance 5-2, the Service Instance 5-4 in physical node 5 in point 3 is the part of service example of the 5th class Service Instance, So physical node 4 meets anti-affinity condition compared with (physical node 3+ physical node 5), physical node 2 is added by management end Add to first physical node 01.
When management end carries out anti-affinity condition inspection to physical node 1, first physical node 01 includes physics section Put 3, physical node 5 and physical node 2, the Service Instance 1-a in physical node 1 with the Service Instance 1-s in physical node 2 is Service Instance in whole Service Instances of first kind Service Instance, the Service Instance 3-a in physical node 1 and physical node 3 3-s is whole Service Instances of the 3rd class Service Instance, the service in the Service Instance 4-s in physical node 1 and physical node 2 Example 4-a is whole Service Instances of the 4th class Service Instance, so physical node 1 and (physical node 3+ physical node 5+ thing Reason node 2) to compare and do not meet anti-affinity condition, physical node 1 is continued to be left the physical node do not upgraded by management end.
So far, management end determines first physical node 01 needing upgrading: physical node 2, physical node 3 and physics Node 5.
Step 407, management end will be run in the main Service Instance running in i-th batch of physical node and other physical nodes Standby Service Instance carries out masterslave switchover.
The standby service that management end will be run in the main Service Instance running in first physical node and other physical nodes Example carries out masterslave switchover, so that by Service Instance based on the standby Service Instance running in other management nodes change, can be the In the escalation process of a collection of management node, it is provided out servicing by the main Service Instance in other management nodes.
Schematically, management end is by the main Service Instance 4-a in the physical node 2 in first physical node and physics section Service Instance 4-s in point 1 carries out masterslave switchover, and it is standby Service Instance 4- that the main Service Instance 4-a in physical node 2 is switched s.Hereafter, when first physical node 01 being upgraded, provided the service of the 4th class Service Instance by physical node 1.
Step 408, for each Service Instance, management end is in the other physical nodes in addition to i-th batch of physical node In, detect whether there is the Service Instance being in upstate.
Because some Service Instances may be in malfunction, so formally being risen to i-th batch of physical node Before level, management end also needs to carry out availability detection to whole system.
Management end needs, to each Service Instance, to be confirmed whether there are the clothes being in upstate in other physical nodes Pragmatic example.
Schematically, the other physical nodes in addition to first physical node include physical node 1 and physical node 4. In physical node 1, running has Service Instance 1-a, Service Instance 2-1, Service Instance 3-a, Service Instance 4a, in physical node In 4, running has Service Instance 5-3 and Service Instance 6-a.So, six kinds of different types of Service Instances are in physical node 1 and thing All have, in reason node 4, the Service Instance being in upstate.
If each Service Instance all has the Service Instance being in upstate, enter step 409, otherwise suspend and rise Level.
Step 409, if each Service Instance all has the Service Instance being in upstate, management end is to i-th batch Physical node is upgraded.
Step 410, after upgrading finishes, management end detects whether also there is the physical node do not upgraded.
Schematically, after the completion of the upgrading of first physical node, management end detects whether also there is the physics do not upgraded Node.
If also there is the physical node do not upgraded, entering step 411, otherwise terminating to upgrade.
Step 411, if also there is the physical node do not upgraded, makes i=i+1, re-executes the physical node of never upgrading In determine the step of i-th batch of physical node.
Management end detects that physical node 1 and physical node 4 are not also upgraded, and makes i=1+1, re-executes step 401 and arrives step Rapid 410.
In management end Computational Physicses node 1 first and physical node 4 run standby Service Instance number of examples, node, Due to all there is not standby Service Instance, then management end Computational Physicses node 1 and physical node 4 in physical node 1 and physical node 4 The instance number of the Service Instance of middle operation, physical nodes most for the instance number of Service Instance is defined as second batch physical node In the first physical node.
Schematically, the result of calculation of management end is: running on physical node 1 has on 4 Service Instances, physical node 4 Operation has 3 Service Instances.Therefore, management end is calculated the instance number of the Service Instance run on physical node 1 at most, will Physical node 1 is defined as the first physical node.
Schematically, management end adds physical node 1 to second batch physical node 02.Second batch physical node is second Criticize the physical node needing upgrading.
Whether management end meets anti-affinity condition to physical node 4 is detected.When management end is carried out to physical node 4 When anti-affinity condition checks, second batch physical node 02 includes physical node 1, the Service Instance 2-4 in physical node 5 and thing Service Instance 2-1 in reason node 1 is only the part of service example in Equations of The Second Kind Service Instance, the service in physical node 4 Example 5-3 is only the part of service example in the 5th class Service Instance, so physical node 4 is met compared with physical node 1 Anti- affinity condition, management end adds physical node 4 to second batch physical node 02.
Physical node 1 and physical node 4 are defined as second batch physical node 02 and are upgraded by management end.
The standby clothes that management end will be run in the main Service Instance running in second batch physical node 02 and other physical nodes Pragmatic example carries out masterslave switchover, so that by Service Instance based on the standby Service Instance running in other management nodes change, Neng Gou In the escalation process of first management node, it is provided out servicing by the main Service Instance in other management nodes.
Schematically, management end is by the main Service Instance 1-a in the physical node 1 in second batch physical node 02 and physics Service Instance 1-s in node 2 carries out masterslave switchover, and it is standby Service Instance that the main Service Instance 1-a in physical node 1 is switched 1-s;Main Service Instance 3-a in physical node 1 carries out masterslave switchover, by physics section with the Service Instance 3-s in physical node 3 It is standby Service Instance 3-s that main Service Instance 3-a in point 1 switches;Main Service Instance 4-a in physical node 1 and physical node 2 In Service Instance 4-s carry out masterslave switchover, it is standby Service Instance 4-s that the main Service Instance 4-a in physical node 1 is switched; Main Service Instance 6-a in physical node 4 is carried out masterslave switchover with the Service Instance 6-s in physical node 3, by physical node It is standby Service Instance 6-s that main Service Instance 6-a in 4 switches;Hereafter, when second batch physical node 02 being upgraded, by thing Reason node 2 provides the service of first kind Service Instance and the service of the 4th class Service Instance, provides the 3rd class clothes by physical node 3 The service of pragmatic example and the service of the 6th class Service Instance.
Schematically, the other physical nodes in addition to second batch physical node 02 include physical node 2, physical node 3 With physical node 5.In physical node 2, running has Service Instance 1-a, Service Instance 2-2, Service Instance 4-a, Service Instance 5-1, in physical node 3, running has Service Instance 3-a, Service Instance 2-3, Service Instance 5-2, Service Instance 6-4, in thing In reason node 5, running has Service Instance 2-5, Service Instance 5-4.So, six kinds of different types of Service Instances are in physical node 2nd, all have, in physical node 3 and physical node 5, the Service Instance being in upstate.
Management end is upgraded to second batch physical node 02, and so far in the present embodiment, whole physical node upgradings finish.
It should be noted that determining the first physics section in the physical node to management end never upgrading for the embodiment of the present invention The mode of point is not limited.Such as, physical nodes most for the instance number of operation service example is defined as first by management end Physical node;Again such as, physical nodes most for the main Service Instance number of operation service example is defined as the first thing by management end Reason node.This several determination mode can also combine enforcement.
In sum, the physical node upgrade method that the present embodiment provides, by determining in the physical node of never upgrading Go out i-th batch of physical node;I-th batch of physical node is upgraded;After upgrading finishes, detect whether also there is the thing do not upgraded Reason node;If also there is the physical node do not upgraded, making i=i+1, in the physical node re-executing never upgrading, determining The step that i criticizes physical node;Solve in prior art when all physical hosts restart upgrading simultaneously, whole distributed system Service all cannot be externally provided, and the duration of service disruption also can very long problem when duration of upgrading is longer;Having reached will be multiple Physical node is upgraded according to different batches, the physical node of each batch in upgrading, its in addition to present lot Its physical node remains able to be provided out servicing, the effect that service will not be interrupted.
The physical node upgrade method that the present embodiment provides, anti-affine by whether each physical node of dynamic detection meets Whole physical nodes are upgraded it is ensured that physical node escalation process interrupts externally servicing by property condition in batches;So that it is every In upgrading, the other physical nodes in addition to present lot remain able to be provided out servicing the physical node of individual batch, clothes The effect that business will not be interrupted.
The physical node upgrade method that the present embodiment provides, by having the most physical node of standby Service Instance true operation Be set to the first physical node so that need in step 407 to carry out masterslave switchover Service Instance be minimum, can reduce active and standby fall The service interruption times that the process of changing is brought, reduce out of service time as far as possible.
The physical node upgrade method that the present embodiment provides, also by before upgrading to i-th batch of Service Instance, to every The availability of the Service Instance of type is judged;Avoid being in malfunction so that escalation process because of certain Service Instance The disabled problem of Service Instance of middle the type, prevents produced service disruption in the escalation process of physical node.
Alternatively, physical node running has with the Service Instance of active and standby form deployment and/or with load balancing form portion The Service Instance of administration.
Fig. 6 a and Fig. 6 b shows a kind of structural representation of distributed computing system that further embodiment of the present invention provides Figure.So that physical node is 4 as a example, physical node includes: physical node 1, physical node 2, physical node 3, physical node 4. Illustrated by physical node deployment in the present embodiment taking the Service Instance of active and standby form deployment as a example.
Each physical node is the server with hardware entities, such as: single-board server.
Running on each physical node has at least one Service Instance, and each Service Instance is used for providing one or more clothes Business.Alternatively, Service Instance is any one in thread, process, container and virtual machine (vmware, vm).
Same type of Service Instance is disposed on two physical nodes with active and standby form.In figure 6, Service Instance 1-a It is the main Service Instance of first kind Service Instance, Service Instance 1-s is the standby Service Instance of first kind Service Instance;Service Instance 2-a is the main Service Instance of Equations of The Second Kind Service Instance, and Service Instance 2-s is the standby Service Instance of Equations of The Second Kind Service Instance;Service Example 3-a is the main Service Instance of the 3rd class Service Instance, and Service Instance 3-s is the standby Service Instance of the 3rd class Service Instance; Service Instance 4-a is the main Service Instance of the 4th class Service Instance, and Service Instance 4-s is that the standby service of the 4th class Service Instance is real Example;Service Instance 5-a is the main Service Instance of the 5th class Service Instance, and Service Instance 5-s is the standby clothes of the 5th class Service Instance Pragmatic example.
Wherein, Service Instance 1-a, Service Instance 4-s are deployed on physical node 1, Service Instance 1-s, Service Instance 2- A, Service Instance 3-a, Service Instance 5-a are deployed on physical node 2, Service Instance 2-s, Service Instance 5-s, Service Instance 4- S is deployed on physical node 3, and Service Instance 3-s is deployed on physical node 4.
Management end calculates the instance number of the standby Service Instance running in 4 physical nodes, and result of calculation is: physical node 1 Upper operation has on 1 standby Service Instance, physical node 2 to run to have to run on 1 standby Service Instance, physical node 32 standby clothes Run on pragmatic example, physical node 4 and have 1 standby Service Instance.
Therefore, management end be calculated on physical node 3 run standby Service Instance instance number most.
Physical node 3 is defined as the first physical node by management end.
Management end adds physical node 3 to first physical node 01.First physical node 01 is first needs The physical node of upgrading.
Alternatively, according to the order that the numbering of physical node is incremented by, management end detects do not upgrade physical node whether one by one Meet anti-affinity condition, that is, whether management end accords with to physical node 1, physical node 2, physical node 2 and physical node 4 successively Close anti-affinity condition to be detected.
When management end carries out anti-affinity condition inspection to physical node 1, first physical node 01 includes physics section Point 3, the Service Instance 4-s in Service Instance 4-a and physical node 3 in physical node 1 is the whole of the 4th class Service Instance Service Instance, so physical node 1 is conflicted with physical node 3, physical node 1 does not meet anti-affinity compared with physical node 3 Condition, physical node 1 is continued to be left the physical node do not upgraded by management end.
When management end carries out anti-affinity condition inspection to physical node 2, first physical node 01 includes physics section Point 3, the Service Instance 2-s in Service Instance 2-a and physical node 3 in physical node 1 is the whole of Equations of The Second Kind Service Instance The Service Instance 5-s in Service Instance 5-a and physical node 3 in Service Instance, and physical node 1 is the 5th class Service Instance Whole Service Instances, so physical node 2 is conflicted with physical node 3, physical node 2 is not met instead compared with physical node 3 Affinity condition, physical node 2 is continued to be left the physical node do not upgraded by management end.
When management end carries out anti-affinity condition inspection to physical node 4, first physical node 01 includes physics section Point 3, the presence service example 3-s in physical node 4, non-existent Service Instance 3-s in physical node 3, so physical node 4 It is the part in the 3rd class Service Instance with the Service Instance 3-s in physical node 3, so physical node 4 and physical node 3 Compare and meet anti-affinity condition, management end adds physical node 4 to first physical node 01.
So far, management end determines first physical node 01 needing upgrading: physical node 3 and physical node 4.
Management end is by the main Service Instance 4-a in the physical node 3 in first physical node 01 and physical node 1 Service Instance 4-s carries out masterslave switchover, and it is standby Service Instance 4-s that the main Service Instance 4-a in physical node 3 is switched.Hereafter, When first physical node 01 is upgraded, provided the service of the 4th class Service Instance by physical node 1.
Management end needs, to each Service Instance, to be confirmed whether there are the clothes being in upstate in other physical nodes Pragmatic example.
Other physical nodes in addition to first physical node 01 include physical node 1 and physical node 2.In physics section In point 1, running has Service Instance 1-s, Service Instance 4-a, and in physical node 2, running has Service Instance 1-a, Service Instance 2-a, Service Instance 3-a and Service Instance 5-a.So, five kinds of different types of Service Instances are in physical node 1 and physical node All there is the Service Instance being in upstate in 2.
Management end is upgraded to first physical node 01.
After upgrading finishes, management end detects whether also there is the physical node do not upgraded.Management end detects physics section Point 1 and physical node 2 are not also upgraded, the example of the standby Service Instance running in management end Computational Physicses node 1 and physical node 2 Number, result of calculation is: running on physical node 1 to have to run on 1 standby Service Instance, physical node 2 has 0 standby Service Instance.
Physical node 1 is defined as the first physical node by management end.
Management end adds physical node 1 to second batch physical node 02.Second batch physical node 02 is second batch needs The physical node of upgrading.
Whether management end meets anti-affinity condition to physical node 2 is detected.
When management end carries out anti-affinity condition inspection to physical node 2, second batch physical node 02 includes physics section Point 1, the Service Instance 1-a in Service Instance 1-s and physical node 2 in physical node 2
Service Instance 1-a in physical node 2 is first kind Service Instance with the Service Instance 1-s in physical node 1 All Service Instances, so physical node 2 is conflicted with physical node 1, physical node 2 does not meet anti-parent compared with physical node 1 With property condition, physical node 2 continues to be left the physical node do not upgraded by management end.
So far, management end determines the second batch physical node 02 needing upgrading: physical node 1.
Management end is by the main Service Instance 4-a in the physical node 1 in second batch physical node 02 and physical node 3 Service Instance 4-s carries out masterslave switchover, and it is standby Service Instance 4-s that the main Service Instance 4-a in physical node 1 is switched.Hereafter, The service of the 4th class Service Instance, when second batch physical node 02 is upgraded, is provided by physical node 3.
Management end needs, to each Service Instance, to be confirmed whether there are the clothes being in upstate in other physical nodes Pragmatic example.
Other physical nodes in addition to second batch physical node 02 include physical node 2, physical node 3 and physical node 4.In physical node 2, running has Service Instance 1-a, Service Instance 2-a, Service Instance 3-a and Service Instance 5-a, in physics In node 3, running has Service Instance 2-s, Service Instance 5-s, Service Instance 4-a, and running in physical node 4 has Service Instance 3-s.So, five kinds of different types of Service Instances are all in available in physical node 2, physical node 3 and physical node 4 The Service Instance of state.
Management end is upgraded to second batch physical node 02.
After upgrading finishes, management end detects whether also there is the physical node do not upgraded.Management end only detects now Remaining physical node 2 is not also upgraded, and because physical node 2 is the node uniquely do not upgraded, physical node 2 is added to the 3rd batch Physical node 03 is upgraded, and does not now need to carry out anti-affinity inspection.Before the 3rd batch of physical node 03 upgrading, management Hold the Service Instance 1-s in the main Service Instance 1-a in the physical node 2 in the 3rd batch of physical node 03 and physical node 1 Carry out masterslave switchover, it is standby Service Instance 1-s that the main Service Instance 1-a in physical node 2 is switched;Master in physical node 2 Service Instance 2-a carries out masterslave switchover, by the main Service Instance 2- in physical node 2 with the Service Instance 2-s in physical node 3 It is standby Service Instance 2-s that a switches;Main Service Instance 3-a in the physical node 2 and Service Instance 3-s in physical node 4 is carried out Masterslave switchover, it is standby Service Instance 3-s that the main Service Instance 3-a in physical node 2 is switched;Main service in physical node 2 Example 5-a carries out masterslave switchover with the Service Instance 5-s in physical node 3, and the main Service Instance 5-a in physical node 2 is fallen It is changed to standby Service Instance 5-s.Hereafter, when the 3rd batch of physical node 03 being upgraded, provide first kind service by physical node 1 The service of example, physical node 3 provides the service of Equations of The Second Kind Service Instance and the service of the 5th class Service Instance, physical node 4 The service of the 3rd class Service Instance is provided.
Other physical nodes in addition to the 3rd batch of physical node 03 include physical node 1, physical node 3 and physical node 4.In physical node 1, running has Service Instance 1-a, Service Instance 4-a, and in physical node 3, running has Service Instance 2- A, Service Instance 5-a and Service Instance 4-s, in physical node 4, running has Service Instance 3-a.So, five kinds are dissimilar Service Instance all have, in physical node 1, physical node 3 and physical node 4, the Service Instance being in upstate.
Management end is upgraded to the 3rd batch of physical node 03.So far in the present embodiment, whole physical node upgradings finish.
Fig. 7 a and Fig. 7 b shows a kind of structural representation of distributed computing system that another embodiment of the present invention provides Figure.So that physical node is 3 as a example, physical node includes: physical node 1, physical node 2, physical node 3, physical node 4. Illustrated by physical node deployment in the present embodiment taking the Service Instance of load balancing form deployment as a example.
Each physical node is the server with hardware entities, such as: single-board server.
Running on each physical node has at least one Service Instance, and each Service Instance is used for providing one or more clothes Business.Alternatively, Service Instance is any one in thread, process, container and virtual machine (vmware, vm).
Same type of Service Instance is disposed on different physical nodes with load balancing form.In the figure 7, the first kind Service Instance includes 2 Service Instances: Service Instance 1-1 and Service Instance 1-2;It is real that Equations of The Second Kind Service Instance includes 2 services Example: Service Instance 2-1 and Service Instance 2-2;3rd class Service Instance includes 3 Service Instances: Service Instance 3-1, service are real Example 3-2 and Service Instance 2-3;4th class Service Instance includes 5 Service Instances: Service Instance 4-1, Service Instance 4-2, service Example 4-3, Service Instance 4-4 and Service Instance 4-5.
Wherein, Service Instance 1-1, Service Instance 2-1, Service Instance 3-1, Service Instance 4-1 and Service Instance 4-5 deployment On physical node 1;Service Instance 1-2, Service Instance 2-2, Service Instance 3-2 and Service Instance 4-4 are deployed in physical node 2 On;Service Instance 3-3 and Service Instance 4-3 is deployed on physical node 3, and Service Instance 4-2 is deployed on physical node 4.
Alternatively, management end calculates the instance number of the Service Instance running in 4 physical nodes, and result of calculation is: physics Run on node 1 to have on 5 Service Instances, physical node 2 to run to have to run on 4 Service Instances, physical node 3 and have 2 clothes Pragmatic example, physical node 4 runs 1 Service Instance.
Therefore, management end be calculated on physical node 1 run Service Instance instance number most.
Physical node 1 is defined as the first physical node by management end.
Management end adds physical node 1 to first physical node 01.First physical node 01 is first needs The physical node of upgrading.
Alternatively, according to the order that the numbering of physical node is incremented by, management end detects do not upgrade physical node whether one by one Meet anti-affinity condition, that is, whether management end meets anti-affinity to physical node 2, physical node 3 and physical node 4 successively Condition is detected.
When management end carries out anti-affinity condition inspection to physical node 2, first physical node 01 includes physics section Point 1, the Service Instance 1-1 in Service Instance 1-2 and physical node 1 in physical node 2 is the whole of first kind Service Instance The Service Instance 2-1 in Service Instance 2-2 and physical node 1 in Service Instance, and physical node 2 is Equations of The Second Kind Service Instance Whole Service Instances, so physical node 2 is conflicted with physical node 1, physical node 2 is not met instead compared with physical node 1 Affinity condition, physical node 2 is continued to be left the physical node do not upgraded by management end.
When management end carries out anti-affinity condition inspection to physical node 3, first physical node 01 includes physics section Point 1, the Service Instance 3-1 in Service Instance 3-3 and physical node 1 in physical node 3 is of the 3rd class Service Instance Point Service Instance, the Service Instance 4-1 in Service Instance 4-3 and physical node 1 in physical node 3, Service Instance 4-5 are the The part of service example of four class Service Instances, so physical node 3 meets anti-affinity condition compared with physical node 1, pipe Reason end adds physical node 3 to first physical node 01.
When management end carries out anti-affinity condition inspection to physical node 4, first physical node 01 includes physics section Point 1, the Service Instance 4-1 in Service Instance 4-2 and physical node 1 in physical node 4, Service Instance 4-1 are the 4th class clothes The part of service example of pragmatic example, so physical node 4 meets anti-affinity condition compared with physical node 1, management end will Physical node 3 adds to first physical node 01.
So far, management end determines first physical node 01 needing upgrading: physical node 1, physical node 3 and physics Node 4.
Due to the Service Instance that on physical node in the present embodiment, only deployment is disposed with load balancing form, so this enforcement Example does not need to carry out masterslave switchover.
Before upgrading, management end needs to include physical node 2 to the other physical nodes in addition to first physical node 01 Carry out availability detection.
Schematically, in physical node 2, running has Service Instance 1-2, Service Instance 2-2 and Service Instance 3-2 kimonos Pragmatic example 4-4, so, four kinds of different types of Service Instances all have the Service Instance being in upstate in physical node 2.
Management end is upgraded to first physical node 01.
After the completion of first physical node upgrading 01, management end detects that being now only left physical node 2 does not also upgrade, Because physical node 2 is the node uniquely do not upgraded, physical node 2 is added and is upgraded to second batch physical node 02, and Now do not need to carry out anti-affinity inspection.
Due to the Service Instance that on physical node in the present embodiment, only deployment is disposed with load balancing form, so this enforcement Example does not need to carry out masterslave switchover.
Before upgrading, management end need the other physical nodes in addition to second batch physical node 02 are included physical node 1, Physical node 3 and physical node 4 carry out availability detection.
Schematically, in physical node 1, running has Service Instance 1-2, Service Instance 2-1, Service Instance 3-1, service Example 4-1 and Service Instance 4-5, in physical node 3, running has Service Instance 3-3 and Service Instance 4-3, in physical node 4 In, run have Service Instance 4-2 so, four kinds of different types of Service Instances are in physical node 1, physical node 3 and physics section Point 4 all has the Service Instance being in upstate.
Management end is upgraded to second batch physical node 02.So far in the present embodiment, whole physical node upgradings finish.
Refer to Fig. 8, it illustrates the block diagram of the physical node update device that one embodiment of invention provides.Should Physical node update device can pass through special hardware circuit, or, being implemented in combination in of software and hardware becomes the whole of server Or a part.The present embodiment is applied in virtualization system with this physical node update device.This physical node update device, bag Include: batch determining unit 801, node upgrade unit 802, nodal test unit 803 and upgrading cycling element 804
Batch determining unit 801, for realizing the function of above-mentioned steps 301.
Node upgrade unit 802, for realizing the function of above-mentioned steps 302.
Nodal test unit 803, for realizing the function of above-mentioned steps 303.
Upgrading cycling element 804, for realizing the function of above-mentioned steps 304.
Refer to Fig. 9, it illustrates the block diagram of the physical node update device that one embodiment of invention provides.Should Physical node update device can pass through special hardware circuit, or, being implemented in combination in of software and hardware becomes the whole of server Or a part.The present embodiment is applied in virtualization system with this physical node update device.This physical node update device, bag Include: batch determining unit 901, masterslave switchover unit 902, node upgrade unit 903, nodal test unit 904 and upgrading circulation Unit 905.
Batch determining unit 901, be used for realizing above-mentioned steps 401, step 402, step 403, step 404, step 405 and The function of step 406.
Masterslave switchover unit 902, for realizing the function of above-mentioned steps 407.
Node upgrade unit 903, for realizing the function of above-mentioned steps 409.
Nodal test unit 904, for realizing the function of upper step 408 and step 410.
Upgrading cycling element 905, for realizing the function of above-mentioned steps 411.
Above-mentioned mainly from the angle of management terminal or physical node, scheme provided in an embodiment of the present invention is described. It is understood that management terminal or physical node, in order to realize above-mentioned functions, it comprises each function of execution hard accordingly Part structure and/or software module.In conjunction with disclosed in this invention the module of each example of embodiment description and algorithm steps, this Inventive embodiments can be realized with the combining form of hardware or hardware and computer software.Certain function is actually with hardware still Computer software drives the mode of hardware executing, the application-specific depending on technical scheme and design constraint.This area Technical staff can use different methods for each specific application realizing described function, but this realization is not It is considered as the scope of the technical scheme beyond the embodiment of the present invention.
Figure 10 is the management terminal of one embodiment of the invention offer or the structural representation of physical node.For example, this pipe Reason terminal or physical node are servers, for realizing the physical node upgrade function of said method embodiment.This management terminal Or physical node 1000 includes: network interface 1010, processor 1020 and memorizer 1030.Network interface 1010 be used for support with Receive and send messages between outside other physical nodes.Processor 1020 is used for realizing management node or the items of physical node 1000 Function, such as determines the first physical node, controls upgrading of physical node etc..Processor 1020 is additionally operable to execute above-mentioned Fig. 3 extremely Each step in embodiment illustrated in fig. 4, or other steps of technical scheme described in the invention.
Further, management terminal or physical node 1000 can also include memorizer 1030, and memorizer 1030 is used for depositing Store up one or more programmed instruction data.This one or more programmed instruction is configured to by processor 1020 execution are to realize above-mentioned Fig. 3 or illustrated in fig. 4 physical node upgrade method.
Additionally, management terminal or physical node 1000 can also include bus 1040.Memorizer 1030 and network interface 1010 are connected with processor 1020 by bus 1040.
It is understood that Figure 10 illustrate only management terminal or the simplification design of physical node 1000.Answer actual With in, management terminal or physical node 1000 can comprise any number of network interface, processor, memorizer etc., and own The equipment that the embodiment of the present invention can be realized is all within the protection domain of the embodiment of the present invention.
The embodiments of the present invention are for illustration only, do not represent the quality of embodiment.
One of ordinary skill in the art will appreciate that all or part of step realizing above-described embodiment can pass through hardware To complete it is also possible to the hardware being instructed correlation by program is completed, described program can be stored in a kind of computer-readable In storage medium, storage medium mentioned above can be read only memory, disk or CD etc..
The foregoing is only presently preferred embodiments of the present invention, not in order to limit the present invention, all spirit in the present invention and Within principle, any modification, equivalent substitution and improvement made etc., should be included within the scope of the present invention.

Claims (10)

1. a kind of physical node upgrade method is it is characterised in that for including in the distributed system of multiple physical nodes, each Physical node run have at least one Service Instance, same Service Instance in different physical nodes each other main and standby relation or Load balancing relation, methods described includes:
Never determine i-th batch of physical node in the physical node of upgrading, in the other things in addition to described i-th batch of physical node The Service Instance of all categories is included, i is integer in the described Service Instance running in reason node;
Described i-th batch of physical node is upgraded;
After upgrading finishes, detect whether the physical node do not upgraded described in also existing;
If the physical node do not upgraded described in also existing, make i=i+1, re-execute described in never in the physical node of upgrading really The step making i-th batch of physical node.
2. method according to claim 1 is it is characterised in that determine i-th batch in the physical node of described never upgrading Physical node, comprising:
Determine the first physical node from the described physical node do not upgraded;
Described first physical node is added to described i-th batch of physical node;
According to predefined procedure detect one by one described in the residue in addition to described first physical node in the physical node do not upgraded Whether reason node meets anti-affinity condition, and described anti-affinity condition includes: the kth kind service that present physical node runs is real Example is not described kth with the physical node set that constituted of described kth kind Service Instance of operation in described i-th batch of physical node Plant the complete or collected works of Service Instance, k is integer;
If meeting described anti-affinity condition, described residue physical node is added to described i-th batch of physical node.
3. method according to claim 2 is it is characterised in that described determine from the described physical node do not upgraded One physical node, comprising:
Calculate the instance number of the standby Service Instance running in the physical node do not upgraded described in each;
By physical nodes most for the instance number of described standby Service Instance, it is defined as described first physical node.
4. method according to claim 2 it is characterised in that described described i-th batch of physical node is upgraded before, Also include:
Standby Service Instance by the main Service Instance running in described i-th batch of physical node and operation in described other physical node Carry out masterslave switchover.
5. method according to claim 2 it is characterised in that described described i-th batch of physical node is upgraded before, Also include:
For each Service Instance, in the other physical nodes in addition to described i-th batch of physical node, detect whether exist It is in the Service Instance of upstate;
If all there is the Service Instance being in upstate in each Service Instance, execute described to described i-th batch of physics section The step that point is upgraded.
6. a kind of physical node update device is it is characterised in that be used for including the described distributed system of multiple described physical nodes In system, each physical node described runs at least one Service Instance described, and described same Service Instance is in different institutes State in physical node described main and standby relation or described load balancing relation each other, described device includes:
Batch determining unit, for determining described i-th batch of physical node from the described physical node do not upgraded, except described Described all categories are included in the described Service Instance running in described other physical node outside i-th batch of physical node Service Instance, i is integer;
Node upgrade unit, for upgrading to described i-th batch of physical node;
Nodal test unit, for the physical node do not upgraded described in after upgrading finishes, detecting whether also to exist;
Upgrading cycling element, if for the physical node do not upgraded described in also existing, making i=i+1, re-execute described in never rise The step determining described i-th batch of physical node in the physical node of level.
7. device according to claim 6 is it is characterised in that described batch determining unit is additionally operable to:
Described first physical node is determined from the described physical node do not upgraded;
Described first physical node is added to described i-th batch of physical node;
According to described predefined procedure detect one by one described in surplus in addition to described first physical node in the physical node do not upgraded Whether remaining physical node meets anti-affinity condition, and described anti-affinity condition includes: the institute that described present physical node runs State the physical node collection that the described kth kind Service Instance running in kth kind Service Instance and described i-th batch of physical node is constituted Closing is not the complete or collected works of described kth kind Service Instance, and k is integer;
If meeting described anti-affinity condition, described residue physical node is added to described i-th batch of physical node.
8. device according to claim 7 is it is characterised in that described batch determining unit is additionally operable to:
Calculate the instance number of the standby Service Instance running in the physical node do not upgraded described in each;
By physical nodes most for the instance number of described standby Service Instance, it is defined as described first physical node.
9. device according to claim 7, it is characterised in that described device, also includes:
Masterslave switchover unit, for the described main Service Instance and the described other physics that will run in described i-th batch of physical node The described standby Service Instance running in node carries out described masterslave switchover.
10. device according to claim 7, it is characterised in that described device, also includes:
Described nodal test unit, is additionally operable to for each Service Instance described, in addition to described i-th batch of physical node In described other physical node, detect whether there is the Service Instance being in described upstate;
Described node upgrade unit, is additionally operable to all there is the service being in described upstate in fact when each Service Instance described During example, execute the described step that described i-th batch of physical node is upgraded.
CN201610734647.6A 2016-08-25 2016-08-25 Physical node upgrading method and device Active CN106354531B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610734647.6A CN106354531B (en) 2016-08-25 2016-08-25 Physical node upgrading method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610734647.6A CN106354531B (en) 2016-08-25 2016-08-25 Physical node upgrading method and device

Publications (2)

Publication Number Publication Date
CN106354531A true CN106354531A (en) 2017-01-25
CN106354531B CN106354531B (en) 2020-03-27

Family

ID=57855615

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610734647.6A Active CN106354531B (en) 2016-08-25 2016-08-25 Physical node upgrading method and device

Country Status (1)

Country Link
CN (1) CN106354531B (en)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107104834A (en) * 2017-04-25 2017-08-29 网宿科技股份有限公司 Method for restarting, the traffic scheduling method of multi-process server and its software
WO2018177417A1 (en) * 2017-03-30 2018-10-04 杭州海康威视数字技术股份有限公司 Method of upgrading distributed system, distributed system, and upgrade management device
CN109213507A (en) * 2018-08-27 2019-01-15 郑州云海信息技术有限公司 A kind of upgrade method and server
CN109525410A (en) * 2017-09-20 2019-03-26 华为技术有限公司 The method, apparatus and distributed memory system of distributed memory system updating and management
CN109710285A (en) * 2018-11-22 2019-05-03 网宿科技股份有限公司 A kind of device updating method and system
CN110134548A (en) * 2019-05-06 2019-08-16 苏州涅瓦信息科技有限公司 A kind of rapid restarting method of distributed memory big data processing system
WO2020021357A1 (en) * 2018-07-23 2020-01-30 International Business Machines Corporation Maintenance of computing nodes concurrently in a number updated dynamically
CN111213343A (en) * 2018-09-28 2020-05-29 华为技术有限公司 Host upgrading method and device
CN112470119A (en) * 2019-07-09 2021-03-09 华为技术有限公司 Service upgrading method and device in distributed system and distributed system
WO2022156099A1 (en) * 2021-01-21 2022-07-28 中兴通讯股份有限公司 Host upgrade method and apparatus, and electronic device and storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1753376A (en) * 2005-10-27 2006-03-29 杭州华为三康技术有限公司 Biprimary controlled network equipment and its master back-up switching method
CN104094248A (en) * 2012-02-02 2014-10-08 微软公司 Self-updating functionality in a distributed system
CN104572179A (en) * 2014-12-19 2015-04-29 华为技术有限公司 IAAS (infrastructure as a service) software upgrading method and device
CN105005487A (en) * 2015-06-29 2015-10-28 清华大学 Continuous-service high-performance cluster operating system online upgrading method
CN105610903A (en) * 2015-12-17 2016-05-25 北京奇虎科技有限公司 Data node upgrading method and device for distributed system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1753376A (en) * 2005-10-27 2006-03-29 杭州华为三康技术有限公司 Biprimary controlled network equipment and its master back-up switching method
CN104094248A (en) * 2012-02-02 2014-10-08 微软公司 Self-updating functionality in a distributed system
CN104572179A (en) * 2014-12-19 2015-04-29 华为技术有限公司 IAAS (infrastructure as a service) software upgrading method and device
CN105005487A (en) * 2015-06-29 2015-10-28 清华大学 Continuous-service high-performance cluster operating system online upgrading method
CN105610903A (en) * 2015-12-17 2016-05-25 北京奇虎科技有限公司 Data node upgrading method and device for distributed system

Cited By (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018177417A1 (en) * 2017-03-30 2018-10-04 杭州海康威视数字技术股份有限公司 Method of upgrading distributed system, distributed system, and upgrade management device
CN107104834A (en) * 2017-04-25 2017-08-29 网宿科技股份有限公司 Method for restarting, the traffic scheduling method of multi-process server and its software
CN107104834B (en) * 2017-04-25 2021-05-07 网宿科技股份有限公司 Multi-process server and software restarting method and flow scheduling method thereof
EP3675420A4 (en) * 2017-09-20 2020-10-07 Huawei Technologies Co., Ltd. Distributed storage system upgrade management method and device, and distributed storage system
US11526276B2 (en) 2017-09-20 2022-12-13 Huawei Technologies Co., Ltd. Upgrade management method and scheduling node, and storage system
CN109525410A (en) * 2017-09-20 2019-03-26 华为技术有限公司 The method, apparatus and distributed memory system of distributed memory system updating and management
GB2587592A (en) * 2018-07-23 2021-03-31 Ibm Maintenance of computing nodes concurrently in a number updated dynamically
WO2020021357A1 (en) * 2018-07-23 2020-01-30 International Business Machines Corporation Maintenance of computing nodes concurrently in a number updated dynamically
GB2587592B (en) * 2018-07-23 2021-09-29 Ibm Maintenance of computing nodes concurrently in a number updated dynamically
US10824413B2 (en) 2018-07-23 2020-11-03 International Business Machines Corporation Maintenance of computing nodes concurrently in a number updated dynamically
CN109213507A (en) * 2018-08-27 2019-01-15 郑州云海信息技术有限公司 A kind of upgrade method and server
CN111213343A (en) * 2018-09-28 2020-05-29 华为技术有限公司 Host upgrading method and device
US11886905B2 (en) 2018-09-28 2024-01-30 Huawei Technologies Co., Ltd. Host upgrade method and device
CN109710285A (en) * 2018-11-22 2019-05-03 网宿科技股份有限公司 A kind of device updating method and system
CN109710285B (en) * 2018-11-22 2022-09-16 网宿科技股份有限公司 Equipment upgrading method and system
CN110134548A (en) * 2019-05-06 2019-08-16 苏州涅瓦信息科技有限公司 A kind of rapid restarting method of distributed memory big data processing system
CN110134548B (en) * 2019-05-06 2023-08-11 深圳市预见之网科技有限公司 Quick restarting method of distributed memory big data processing system
CN112470119A (en) * 2019-07-09 2021-03-09 华为技术有限公司 Service upgrading method and device in distributed system and distributed system
WO2022156099A1 (en) * 2021-01-21 2022-07-28 中兴通讯股份有限公司 Host upgrade method and apparatus, and electronic device and storage medium

Also Published As

Publication number Publication date
CN106354531B (en) 2020-03-27

Similar Documents

Publication Publication Date Title
CN106354531A (en) Physical node upgrading method and device
US7925923B1 (en) Migrating a virtual machine in response to failure of an instruction to execute
US8413148B2 (en) Virtualization support in platform management (PLM) information model
US9432301B2 (en) Defining disjoint node groups for virtual machines with pre-existing placement policies
US9996331B1 (en) Customized application state transition
CN106201566A (en) The rich big special hot upgrade method of software of profit and equipment
CN102165431A (en) On-the-fly replacement of physical hardware with emulation
WO2020123213A1 (en) Container migration in computing systems
CN106803790A (en) The upgrade control method and device of a kind of group system
US10860375B1 (en) Singleton coordination in an actor-based system
US8015432B1 (en) Method and apparatus for providing computer failover to a virtualized environment
JP2013508839A5 (en)
US20190297141A1 (en) Automatic system response to external field-replaceable unit (fru) process
CA2503184A1 (en) Transitional resolution in a just in time environment
US9563719B2 (en) Self-monitoring object-oriented applications
Burckhardt et al. Serverless workflows with durable functions and netherite
CN100517224C (en) Serializing storage of objects and recovering system and method thereof
CN103856502B (en) Realize method and the NAS group system of virtual machine image file thermophoresis
Desell et al. Salsa lite: A hash-based actor runtime for efficient local concurrency
CN109324867A (en) A kind of virtual machine temporary storage method, restoration methods and device
US11226829B2 (en) Trigger correlation for dynamic system reconfiguration
Rangarajan et al. Managing the availability of VNFs with the availability management framework
US20220237048A1 (en) Affinity and anti-affinity for sets of resources and sets of domains in a virtualized and clustered computer system
CN104731633B (en) Rollback method and system after multi partition storage device dismount failure under a kind of linux system
US20110282820A1 (en) Dynamic backjumping in constraint satisfaction problem solving

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right

Effective date of registration: 20200422

Address after: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen

Patentee after: HUAWEI TECHNOLOGIES Co.,Ltd.

Address before: 301, A building, room 3, building 301, foreshore Road, No. 310052, Binjiang District, Zhejiang, Hangzhou

Patentee before: Hangzhou Huawei Digital Technology Co.,Ltd.

TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20220224

Address after: 550025 Huawei cloud data center, jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province

Patentee after: Huawei Cloud Computing Technology Co.,Ltd.

Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen

Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd.

TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20221208

Address after: 518129 Huawei Headquarters Office Building 101, Wankecheng Community, Bantian Street, Longgang District, Shenzhen, Guangdong

Patentee after: Shenzhen Huawei Cloud Computing Technology Co.,Ltd.

Address before: 550025 Huawei cloud data center, jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province

Patentee before: Huawei Cloud Computing Technology Co.,Ltd.

TR01 Transfer of patent right