Location-Based Management of Virtual Machines in Datacenters

Abstract

Embodiments manage physical locations of virtual machines (VMs) in a datacenter. A computing device, such as a cloud management device, aggregates location information for the VMs executing on hosts. The computing device compares the aggregated location information with event data to identify VMs potentially affected by adverse events (e.g., severe weather, scheduled maintenance, natural disasters, etc.). The computing device initiates migration of the affected VMs from their hosts to unaffected hosts. In some embodiments, the location information includes global positioning system (GPS) coordinates obtained by the hosts and shared with the computing device.

1 - 20 . (canceled) 
     
     
         21 . A system for relocating virtual machines (VMs) in anticipation of adverse events, said system comprising:
 a memory area associated with a computing device, said memory area storing an inventory of VMs in a virtualized datacenter; and   a processor programmed to:
 aggregate location information for a plurality of hosts in the virtualized datacenter, the hosts executing a plurality of the VMs, the location information associated with a plurality of racks in which the hosts are installed; 
 receive event data comprising a description of potential adverse events; 
 compare the aggregated location information with the received event data to identify a first host anticipated to be affected by the potential adverse events; 
 identify a second host that is anticipated to be not affected by the potential adverse events; 
 compare the identified first host anticipated to be affected by the potential adverse events with the inventory of VMs stored in the memory area to identify VMs anticipated to be affected by the potential adverse events; 
 notify the identified second host of an impending migration of the identified VMs; 
 migrate one or more VMs of the identified VMs anticipated to be affected by the potential adverse events from the identified first host to the identified second host; and 
 obtain updated location information from the one or more VMs migrated to the identified second host. 
   
     
     
         22 . The system of  claim 21 , wherein the processor is further programmed to prioritize one VM of the one or more VMs for migration from the first host to the second host based on a service level agreement with a user. 
     
     
         23 . The system of  claim 21 , wherein the processor is programmed to receive event data by receiving at least one of a weather forecast, an upcoming scheduled maintenance event, or a scheduled test event. 
     
     
         24 . The system of  claim 21 , wherein the processor is programmed to confirm successful migration of the one or more VMs migrated to the identified second host upon receiving the updated location information. 
     
     
         25 . The system of  claim 21 , wherein the processor is further programmed to power down other VMs anticipated to be affected by the adverse event after migrating the other VMs to the other hosts. 
     
     
         26 . The system of  claim 21 , wherein the inventory stored in the memory area comprises cloud zones each storing one or more of the VMs. 
     
     
         27 . The system of  claim 26 , wherein the event data adversely affects a first one of the cloud zones, and wherein the processor is programmed to migrate the one or more of the VMs anticipated to be affected from the first one of the cloud zones to a second one of the cloud zones. 
     
     
         28 . A method for relocating virtual machines (VMs) in anticipation of adverse events, comprising:
 aggregating location information for a plurality of hosts in the virtualized datacenter, the hosts executing a plurality of the VMs, the location information associated with a plurality of racks in which the hosts are installed;   receiving event data comprising a description of potential adverse events;   comparing the aggregated location information with the received event data to identify a first host anticipated to be affected by the potential adverse events;   identifying a second host that is anticipated to be not affected by the potential adverse events;   comparing the identified first host anticipated to be affected by the potential adverse events with the inventory of VMs stored in the memory area to identify VMs anticipated to be affected by the potential adverse events;   notifying the identified second host of an impending migration of the identified VMs;   migrating one or more VMs of the identified VMs anticipated to be affected by the potential adverse events from the identified first host to the identified second host; and   obtaining updated location information from the one or more VMs migrated to the identified second host.   
     
     
         29 . The method of  claim 28 , further comprising prioritizing one VM of the one or more VMs for migration from the first host to the second host based on a service level agreement with a user. 
     
     
         30 . The method of  claim 28 , further comprising receiving event data by receiving at least one of a weather forecast, an upcoming scheduled maintenance event, or a scheduled test event. 
     
     
         31 . The method of  claim 28 , wherein the processor is programmed to confirm successful migration of the one or more VMs migrated to the identified second host upon receiving the updated location information. 
     
     
         32 . The method of  claim 28 , further comprising powering down other VMs anticipated to be affected by the adverse event after migrating the other VMs to the other hosts. 
     
     
         33 . The method of  claim 28 , further comprising powering down other VMs anticipated to be affected by the adverse event after migrating the other VMs to the other hosts. 
     
     
         34 . The method of  claim 33 , wherein the event data adversely affects a first one of the cloud zones, and wherein the processor is programmed to migrate the one or more of the VMs anticipated to be affected from the first one of the cloud zones to a second one of the cloud zones. 
     
     
         35 . A non-transitory computer-readable storage medium including computer-executable instructions that, when executed, cause at least one processor to protect virtual machines (VMs) in anticipation of adverse events affecting a virtualized datacenter by causing the at least one processor to at least:
 aggregate location information for a plurality of hosts in the virtualized datacenter, the hosts executing a plurality of the VMs, the location information associated with a plurality of racks in which the hosts are installed;   receive event data comprising a description of potential adverse events;   compare the aggregated location information with the received event data to identify a first host anticipated to be affected by the potential adverse events;   identify a second host that is anticipated to be not affected by the potential adverse events;   compare the identified first host anticipated to be affected by the potential adverse events with the inventory of VMs stored in the memory area to identify VMs anticipated to be affected by the potential adverse events;   notify the identified second host of an impending migration of the identified VMs;   migrate one or more VMs of the identified VMs anticipated to be affected by the potential adverse events from the identified first host to the identified second host; and   obtain updated location information from the one or more VMs migrated to the identified second host.   
     
     
         36 . The non-transitory computer storage medium of  claim 35 , wherein migrating the at least one VM anticipated to be affected comprises at least one of moving, replicating, or cloning the at least one VM anticipated to be affected in anticipation of the future adverse event. 
     
     
         37 . The non-transitory computer storage medium of  claim 35 , wherein the at least one processor receives event data by receiving at least one of a weather forecast, an upcoming scheduled maintenance event, or a scheduled test event. 
     
     
         38 . The non-transitory computer storage medium of  claim 35 , wherein the at least one processor confirms successful migration of the one or more VMs migrated to the identified second host upon receiving the updated location information. 
     
     
         39 . The non-transitory computer storage medium of  claim 35 , wherein the at least one processor powers down other VMs anticipated to be affected by the adverse event after migrating the other VMs to the other host. 
     
     
         40 . The non-transitory computer storage medium of  claim 35 , wherein the inventory stored in the memory area comprises cloud zones each storing one or more of the VMs.