Mechanism for performing rolling updates with data unavailability check in a networked virtualization environment for storage management
US-2016203008-A1 · Jul 14, 2016 · US
US9590843B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9590843-B2 |
| Application number | US-201414206869-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 12, 2014 |
| Priority date | Mar 12, 2014 |
| Publication date | Mar 7, 2017 |
| Grant date | Mar 7, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method for handling failure in a networked virtualization environment having distributed virtual machine management.
Opening claim text (preview).
What is claimed is: 1. A method for handling failure in a networked virtualization environment having distributed virtual machine management, comprising: identifying a failed management virtual machine instance of a plurality of management virtual machine instances in the networked virtualization environment, wherein the networked virtualization environment comprises a plurality of nodes, where a node of the plurality of nodes comprises a hypervisor, one or more virtualization components and a management virtual machine instance that runs on top of the hypervisor, wherein each management virtual machine instance of the plurality of management virtual machine instances services a subset of virtualization components in the networked virtualization environment, and wherein a management virtual machine instance of the plurality of management virtual machine instances has access to a corresponding shard of a distributed database for the networked virtualization environment, the corresponding shard storing a subset of management data for virtualization components managed by the management virtual machine instance; designating one or more active management virtual machine instances of the plurality of management virtual machine instances for replacing virtualization component management functionality of the failed management virtual machine instance, wherein the one or more active management virtual machine instances replace virtualization component management functionality of the failed management virtual machine instance by each accessing its subset of management data in its corresponding shard of the distributed database, and wherein the one or more active management virtual machine instances are configured to replace virtualization component management functionality of another management virtual machine instance whenever the other management virtual machine instance fails; and distributing a workload of the failed management virtual machine instance amongst the one or more active management virtual machine instances in response to identifying the failed management virtual machine instance. 2. The method of claim 1 , wherein the subset of virtualization components in the networked virtualization environment being serviced by each management virtual machine instance comprises virtual machines. 3. The method of claim 2 , wherein the subset of management data for the networked virtualization environment being stored in the corresponding shard of a distributed database for each management virtual machine instance comprises virtual machine management data. 4. The method of claim 1 , further comprising: determining whether the failed management virtual machine instance has recovered; and reassigning the workload of the failed management virtual machine instance when the failed management virtual machine instance has recovered. 5. The method of claim 1 , wherein identifying the failed management virtual machine instance comprises: identifying a state of the networked virtualization environment by the one or more active management virtual machine instances in a corresponding shard of the distributed database. 6. The method of claim 1 , wherein identifying the failed management virtual machine instance comprises: utilizing pings between the failed management virtual machine instance and the one or more active management virtual machine instances. 7. The method of claim 1 , wherein the failed management virtual machine instance has itself failed rather than a node at which the failed management virtual machine instance resides. 8. The method of claim 7 , wherein distributing the workload of the failed management virtual machine instance amongst the one or more active management virtual machine instances comprises migrating virtual machine management functionality for one or more user virtual machines previously serviced by the failed management virtual machine instance to the one or more active management virtual machine instances. 9. The method of claim 1 , wherein the failed management virtual machine instance resides on a failing node of the networked virtualization environment. 10. The method of claim 9 , wherein distributing the workload of the failed management virtual machine instance amongst the one or more active management virtual machine instances comprises migrating one or more user virtual machines previously serviced by the failed management virtual machine instance to nodes at which the one or more active management virtual machine instances reside. 11. The method of claim 1 , wherein designating the one or more active management virtual machine instances for replacing the failing management virtual machine instance comprises: electing an active management virtual machine instance as a leader management virtual machine instance; and designating the one or more active management virtual machine instances for replacing the failing management virtual machine instance by the leader management virtual machine instance. 12. The method of claim 11 , wherein designating the one or more active management virtual machine instances is based on a current workload of the one or more active management virtual machine instances. 13. The method of claim 11 , wherein designating the one or more active management virtual machine instances is based on a workload of the failed management virtual machine instance. 14. A computer program product embodied on a non-transitory computer readable medium, the non-transitory computer readable medium having stored thereon a sequence of instructions which, when executed by a processor causes the processor to execute a method for handling failure in a networked virtualization environment having distributed virtual machine management, comprising: identifying a failed management virtual machine instance of a plurality of management virtual machine instances in the networked virtualization environment, wherein the networked virtualization environment comprises a plurality of nodes, where a node of the plurality of nodes comprises a hypervisor, one or more virtualization components and a management virtual machine instance that runs on top of the hypervisor, wherein each management virtual machine instance of the plurality of management virtual machine instances services a subset of virtualization components in the networked virtualization environment, and wherein a management virtual machine instance of the plurality of management virtual machine instances has access to a corresponding shard of a distributed database for the networked virtualization environment, the corresponding shard storing a subset of management data for virtualization components managed by the management virtual machine instance; designating one or more active management virtual machine instances of the plurality of management virtual machine instances for replacing virtualization component management functionality of the failed management virtual machine instance, wherein the one or more active management virtual machine instances replace virtualization component management functionality of the failed management virtual machine instance by each accessing its subset of management data in its corresponding shard of the distributed database, and wherein the one or more active management virtual machine instances are configured to replace virtualization component management functionality of another management virtual machine instance whenever the other management virtual machine instance fails; and distributing a workload of the failed management virtual machine instance amongst the one or more active management virtual machine ins
by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure · CPC title
using migration · CPC title
Error detection or correction of the data by redundancy in hardware · CPC title
involving virtual machines · CPC title
in a virtual computing platform, e.g. logically partitioned systems · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.