# US 2024/0403042 A1 · Cloud resource project management

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

- Number: US 2024/0403042 A1
- Document ID: US20240403042A1
- Status: Published application
- Kind: A1
- Application number: 18/327,641
- Filed: 2023-06-01
- Published: 2024-12-05
- Earliest claimed: 2023-06-01
- Assignees: VMware, Inc.
- Applicants: VMware LLC
- Inventors: Ventsyslav Raikov; George P. Dimitrov; Alexander Dimitrov; Ivan Slavov; Atanas Todorov
- Web page: https://patentgrep.com/patent/US20240403042A1

## CPC

- G06F 8/77: Software metrics
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods, apparatus, systems, and articles of manufacture are disclosed to manage cloud project resources. An example apparatus includes instructions to program programmable circuitry to: monitor first events for a first reference to a project, the project to coordinate access to computing resources in a cloud or hybrid cloud computing environment; manage a record stored for the project, the record including a status of the project, the status updated in response to the first reference; delete the project in response to a delete instruction in the first events when the status of the project indicates that the project is not in use; monitor second events for a second reference to the project; and restore the project when the second events include the second reference.

## Claims

### Claim 1

An apparatus comprising:
interface circuitry;
machine readable instructions; and
programmable circuitry to at least one of instantiate or execute the machine readable instructions to:
monitor first events for a first reference to a project, the project to coordinate access to computing resources in a cloud or hybrid cloud computing environment;
manage a record stored for the project, the record including a status of the project, the status updated in response to the first reference;
delete the project in response to a delete instruction in the first events when the status of the project indicates that the project is not in use;
monitor second events for a second reference to the project; and
restore the project when the second events include the second reference.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the programmable circuitry is to synchronize the project between an infrastructure automation manager and a cloud services manager.

### Claim 3 (depends on 2)

The apparatus of claim 2, wherein the programmable circuitry is to maintain a first record of the project with the infrastructure automation manager and a second record of the project with the cloud services manager.

### Claim 4 (depends on 3)

The apparatus of claim 3, wherein the programmable circuitry is to implement resource management circuitry in the cloud services manager and project migrator circuitry and synchronization circuitry in the infrastructure automation manager.

### Claim 5 (depends on 4)

The apparatus of claim 4, wherein the project migration circuitry is to create the project with the resource management circuitry, and wherein the synchronization circuitry is to read the project from the resource management circuitry.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the programmable circuitry is to deny the delete instruction when the status of the project indicates that the project is in use.

### Claim 7 (depends on 1)

The apparatus of claim 1, wherein the first events include at least one of a project creation, a project update, or a project deletion, the project delete associated with the delete instruction.

### Claim 8 (depends on 1)

The apparatus of claim 1, wherein the programmable circuitry is to create a deployment using the project.

### Claim 9 (depends on 8)

The apparatus of claim 8, wherein the programmable circuitry is to add a resource to the project.

### Claim 10 (depends on 1)

The apparatus of claim 1, wherein the programmable circuitry is to periodically check to determine whether the project is in use and marks the status of the project as in use or not in use based on the determination.

### Claim 11

A non-transitory machine readable storage medium comprising instructions to cause programmable circuitry to at least:
monitor first events for a first reference to a project, the project to coordinate access to computing resources in a cloud or hybrid cloud computing environment;
manage a record stored for the project, the record including a status of the project, the status updated in response to the first reference;
delete the project in response to a delete instruction in the first events when the status of the project indicates that the project is not in use;
monitor second events for a second reference to the project; and
restore the project when the second events include the second reference.

### Claim 12 (depends on 11)

The non-transitory machine readable storage medium of claim 11, wherein the instructions cause the programmable circuitry to synchronize the project between an infrastructure automation manager and a cloud services manager.

### Claim 13 (depends on 12)

The non-transitory machine readable storage medium of claim 12, wherein the instructions cause the programmable circuitry to maintain a first record of the project with the infrastructure automation manager and a second record of the project with the cloud services manager.

### Claim 14 (depends on 11)

The non-transitory machine readable storage medium of claim 11, wherein the instructions cause the programmable circuitry to deny the delete instruction when the status of the project indicates that the project is in use.

### Claim 15 (depends on 11)

The non-transitory machine readable storage medium of claim 11, wherein the first events include at least one of a project creation, a project update, or a project deletion, the project delete associated with the delete instruction.

### Claim 16 (depends on 11)

The non-transitory machine readable storage medium of claim 11, wherein the instructions cause the programmable circuitry to create a deployment using the project.

### Claim 17 (depends on 16)

The non-transitory machine readable storage medium of claim 16, wherein the instructions cause the programmable circuitry to add a resource to the project.

### Claim 18 (depends on 11)

The non-transitory machine readable storage medium of claim 11, wherein the instructions cause the programmable circuitry to periodically check to determine whether the project is in use and marks the status of the project as in use or not in use based on the determination.

### Claim 19

A method comprising:
monitoring, by executing an instruction using programmable circuitry, first events for a first reference to a project, the project to coordinate access to computing resources in a cloud or hybrid cloud computing environment;
managing, by executing an instruction using the programmable circuitry, a record stored for the project, the record including a status of the project, the status updated in response to the first reference;
deleting, by executing an instruction using the programmable circuitry, the project in response to a delete instruction in the first events when the status of the project indicates that the project is not in use;
monitoring, by executing an instruction using the programmable circuitry, second events for a second reference to the project; and
restoring, by executing an instruction using the programmable circuitry, the project when the second events include the second reference.

### Claim 20 (depends on 19)

The method of claim 19, further including:
periodically checking to determine whether the project is in use; and
marking the status of the project as in use or not in use based on the determination.

### Claim 21 (depends on 20)

The method of claim 20, further including:
denying the delete instruction when the status of the project indicates that the project is in use.
