# US 2015/0106807 A1 · Methods and apparatus to manage virtual machines

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0106807 A1
- Document ID: US20150106807A1
- Status: Published application
- Kind: A1
- Application number: 14/315,297
- Filed: 2014-06-25
- Published: 2015-04-16
- Earliest claimed: 2013-10-11
- Assignees: VMware, Inc.
- Applicants: VMware, Inc.
- Inventors: Thirumalesh Reddy; Sreekantha Indireddy; Shreekanth Ankala; Bhavin Mathia
- Web page: https://patentgrep.com/patent/US20150106807A1

## CPC

- G06F 9/45558: {Hypervisor-specific management and integration aspects}
- G06F 9/45533: {Hypervisors; Virtual machine monitors}
- G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)}
- G06F 16/24: Querying
- G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files}
- G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing}
- G06F 2009/45595: {Network integration; Enabling network access in virtual machine instances}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods and apparatus to manage virtual machines are disclosed. An example method includes determining that a deployment of a first virtual machine has halted because the first virtual machine is dependent on a parameter of a second virtual machine, detecting that the second virtual machine has been deployed and has caused configuration information to be stored in a repository, retrieving, via a processor, the configuration information, including the parameter, from the repository, and transmitting, via the processor, the parameter to the first virtual machine to cause the first virtual machine to resume deployment.

## Claims

### Claim 1

An apparatus comprising:
a dependency controller to determine that a deployment of a first virtual machine has halted because the first virtual machine is dependent on a parameter of a second virtual machine and to detect that the second virtual machine has been deployed and has caused configuration information to be stored in a repository; and
a configuration controller to retrieve the configuration information, including the parameter, from the repository and to transmit the parameter to the first virtual machine to cause the first virtual machine to resume deployment.

### Claim 2 (depends on 1)

An apparatus as defined in claim 1, wherein the repository is a lightweight directory access protocol.

### Claim 3 (depends on 1)

An apparatus as defined in claim 1, wherein the configuration controller comprises a configuration retriever to receive the configuration information by performing a lightweight directory access protocol query.

### Claim 4 (depends on 1)

An apparatus as defined in claim 1, wherein the configuration controller comprises an information collector to store the configuration information in the repository in response to a request from the second virtual machine received.

### Claim 5 (depends on 1)

An apparatus as defined in claim 1, wherein the configuration controller retrieves the configuration information responsive to a request for the parameter from the first virtual machine.

### Claim 6 (depends on 1)

An apparatus as defined in claim 1, wherein the parameter is a network address for the second virtual machine.

### Claim 7 (depends on 1)

An apparatus as defined in claim 1, wherein the dependency controller is to determine that the deployment of the first virtual machine has halted in response to receiving a wait request from the first virtual machine.

### Claim 8 (depends on 7)

An apparatus as defined in claim 7, wherein the dependency controller is to, in response to receiving the wait request, query an inventory of virtual machines for a workload identified in the wait request to identify the second virtual machine.

### Claim 9 (depends on 1)

An apparatus as defined in claim 1, wherein the dependency controller is to detect that the second virtual machine has been deployed by querying a datastore for a notification received from the second virtual machine.

### Claim 10 (depends on 1)

An apparatus as defined in claim 1, wherein the dependency controller is to detect that the second virtual machine has been deployed in response to receiving a notify request from the second virtual machine.

### Claim 11

A method comprising:
determining that a deployment of a first virtual machine has halted because the first virtual machine is dependent on a parameter of a second virtual machine;
detecting that the second virtual machine has been deployed and has caused configuration information to be stored in a repository;
retrieving, via a processor, the configuration information, including the parameter, from the repository; and
transmitting, via the processor, the parameter to the first virtual machine to cause the first virtual machine to resume deployment.

### Claim 12 (depends on 11)

A method as defined in claim 11, wherein the repository is a lightweight directory access protocol.

### Claim 13 (depends on 11)

A method as defined in claim 11, wherein retrieving the configuration information comprises performing a lightweight directory access protocol query.

### Claim 14 (depends on 11)

A method as defined in claim 11, further comprising storing the configuration information in the repository in response to a request from the second virtual machine.

### Claim 15 (depends on 11)

A method as defined in claim 11, wherein the retrieving the configuration information is responsive to a request for the parameter from the first virtual machine.

### Claim 16 (depends on 11)

A method as defined in claim 11, wherein the parameter is a network address for the second virtual machine.

### Claim 17 (depends on 11)

A method as defined in claim 11, wherein the determining that the deployment of the first virtual machine has halted comprises receiving a wait request from the first virtual machine.

### Claim 18 (depends on 17)

A method as defined in claim 17, further comprising, in response to receiving the wait request, querying an inventory of virtual machines for a workload identified in the wait request to identify the second virtual machine.

### Claim 19 (depends on 11)

A method as defined in claim 11, wherein the detecting that the second virtual machine has been deployed comprises querying a datastore for a notification received from the second virtual machine.

### Claim 20 (depends on 11)

A method as defined in claim 11, wherein the detecting that the second virtual machine has been deployed comprises receiving a notify request from the second virtual machine.

### Claim 21

A tangible computer readable storage medium comprising instructions that, when executed, cause a machine to at least:
determine that a deployment of a first virtual machine has halted because the first virtual machine is dependent on a parameter of a second virtual machine;
detect that the second virtual machine has been deployed and has caused configuration information to be stored in a repository;
retrieve the configuration information, including the parameter, from the repository; and
transmit the parameter to the first virtual machine to cause the first virtual machine to resume deployment.

### Claim 22 (depends on 21)

A tangible computer readable storage medium as defined in claim 21, wherein the repository is a lightweight directory access protocol.

### Claim 23 (depends on 21)

A tangible computer readable storage medium as defined in claim 21, wherein the instructions, when executed cause the machine to retrieve the configuration information by performing a lightweight directory access protocol query.

### Claim 24 (depends on 21)

A tangible computer readable storage medium as defined in claim 21, wherein the instructions, when executed cause the machine to store the configuration information in the repository in response to a request from the second virtual machine.

### Claim 25 (depends on 21)

A tangible computer readable storage medium as defined in claim 21, wherein the instructions, when executed cause the machine to retrieve the configuration information responsive to a request for the parameter from the first virtual machine.

### Claim 26 (depends on 21)

A tangible computer readable storage medium as defined in claim 21, wherein the parameter is a network address for the second virtual machine.

### Claim 27 (depends on 21)

A tangible computer readable storage medium as defined in claim 21, wherein the instructions, when executed cause the machine to determine that the deployment of the first virtual machine has halted by receiving a wait request from the first virtual machine.

### Claim 28 (depends on 27)

A tangible computer readable storage medium as defined in claim 27, wherein the instructions, when executed cause the machine to, in response to receiving the wait request, query an inventory of virtual machines for a workload identified in the wait request to identify the second virtual machine.

### Claim 29 (depends on 21)

A tangible computer readable storage medium as defined in claim 21, wherein the instructions, when executed cause the machine to detect that the second virtual machine has been deployed by querying a datastore for a notification received from the second virtual machine.

### Claim 30 (depends on 21)

A tangible computer readable storage medium as defined in claim 21, wherein the instructions, when executed cause the machine to detect that the second virtual machine has been deployed by receiving a notify request from the second virtual machine.
