Centralized approach for managing cross-service data of cloud resources
Techniques for managing network-accessible infrastructure metadata are provided. A method includes receiving a resource request comprising resource metadata corresponding to a network-accessible infrastructure resource, determining whether to commit the resource request based at least in part on a constraint associated with the network-accessible infrastructure resource, and, in accordance with a determination to commit the resource request: generating, by the computer system, a resource identifier describing resource metadata in accordance with the resource request, storing, by the computer system, the resource metadata in a data store in communication with the computer system, receiving, by the computer system, a data request to provide the resource metadata described by the resource identifier, and providing, by the computer system, the resource metadata described by the resource identifier in accordance with the data request.
1. A method, comprising:
receiving a resource request for access to a network-accessible infrastructure resource, the resource request comprising resource metadata corresponding to the network-accessible infrastructure resource, wherein access to the network-accessible infrastructure resource is granted or denied based at least in part on the resource request;
determining that the resource request is to be persisted based at least in part on whether a resource usage corresponding to the resource request exceeds a quota limit for the resource request;
responsive to determining that the resource request is to be persisted:
persisting at least a portion of the resource request, the portion of the resource request comprising the resource metadata;
receiving a data request to provide the resource metadata, the resource metadata being previously received with the resource request; and
providing, in accordance with the data request, the resource metadata from the portion of the resource request.
2. The method of claim 1 , further comprising:
generating a request identifier describing the resource metadata in accordance with the resource request by:
storing the resource request in a data store as an in-progress request, the in-progress request comprising a predefined timeout period;
fetching, in response to a fetch request or after the predefined timeout period is elapsed, the in-progress request from the data store;
requesting a resource status associated with the in-progress request;
receiving the resource status corresponding to the network-accessible infrastructure resource identified in the resource metadata; and
reconciling the in-progress request with the resource status.
3. The method of claim 2 , wherein reconciling the in-progress request with the resource status comprises:
ascertaining a lease token value associated with the in-progress request; and
in accordance with the lease token value being true, releasing the in-progress request to the data store; or
in accordance with the lease token value being false, assigning the in-progress request to a default queue of a reconciler instance.
4. The method of claim 2 , wherein reconciling the in-progress request comprises, in accordance with the resource status indicating an active status, committing the resource request.
5. The method of claim 2 , wherein the predefined timeout period is a first predefined timeout period, and wherein reconciling the in-progress request comprises, in accordance with the resource status indicating an in-progress status, rescheduling the resource request after a second predefined timeout period, wherein the in-progress status comprises at least one of creating, terminating, or updating.
6. The method of claim 2 , wherein reconciling the in-progress request comprises, in accordance with the resource status indicating a terminated status, aborting the resource request, at least in part by removing the resource request from the data store.
7. The method of claim 1 , wherein determining that the resource request is to be persisted comprises:
receiving a resource usage corresponding to the resource request; and
determining a quota limit for the resource request based at least in part on the resource metadata.
8. A system, comprising:
at least one device including a hardware processor; and
the system being configured to perform operations comprising:
receiving a resource request for access to a network-accessible infrastructure resource, the resource request comprising resource metadata corresponding to the network-accessible infrastructure resource, wherein access to the network-accessible infrastructure resource is granted or denied based at least in part on the resource request;
determining that the resource request is to be persisted based at least in part on whether a resource usage corresponding to the resource request exceeds a quota limit for the resource request;
responsive to determining that the resource request is to be persisted:
persisting at least a portion of the resource request, the portion of the resource request comprising the resource metadata;
receiving a data request to provide the resource metadata, the resource metadata being previously received with the resource request; and
providing, in accordance with the data request, the resource metadata from the resource request.
9. The system of claim 8 , wherein the operations further comprise:
generating a request identifier describing the resource metadata in accordance with the resource request by:
storing the resource request in a data store as an in-progress request, the in-progress request comprising a predefined timeout period;
fetching, in response to a fetch request or after the predefined timeout period is elapsed, the in-progress request from the data store;
requesting a resource status associated with the in-progress request;
receiving the resource status corresponding to the network-accessible infrastructure resource identified in the resource metadata; and
reconciling the in-progress request with the resource status.
10. The system of claim 9 , wherein reconciling the in-progress request comprises, in accordance with the resource status indicating a committed status, committing the resource request.
11. The system of claim 9 , wherein reconciling the in-progress request comprises, in accordance with the resource status indicating an in-progress status, rescheduling the resource request after a second predefined timeout.
12. The system of claim 9 , wherein reconciling the in-progress request comprises, in accordance with the resource status indicating an aborted status, aborting the resource request, at least in part by removing the resource request from the data store.
13. The system of claim 8 , wherein determining that the resource request is to be persisted comprises:
receiving a resource usage corresponding to the resource request; and
determining a quota limit for the resource request based at least in part on the resource metadata.
14. One or more non-transitory computer-readable media storing instructions that, when executed by one or more hardware processors, cause performance of operations comprising:
receiving a resource request for access to a network-accessible infrastructure resource, the resource request comprising resource metadata corresponding to the network-accessible infrastructure resource, wherein access to the network-accessible infrastructure resource is granted or denied based at least in part on the resource request;
determining that the resource request is to be persisted based at least in part on whether a resource usage corresponding to the resource request exceeds a quota limit for the resource request;
responsive to determining that the resource request is to be persisted:
persisting at least a portion of the resource request, the portion of the resource request comprising the resource metadata;
receiving a data request to provide the resource metadata, the resource metadata being previously received with the resource request; and
providing, in accordance with the data request, the resource metadata from the resource request.
15. The one or more non-transitory computer-readable media of claim 14 , wherein the operations further comprise:
generating a resource identifier describing the resource metadata in accordance with the resource request by:
storing the resource request in a data store as an in-progress request, the in-progress request comprising a predefined timeout period;
fetching, in response to a fetch request or after the predefined timeout period is elapsed, the in-progress request from the data store;
requesting a resource status associated with the in-progress request;
receiving the resource status corresponding to the network-accessible infrastructure resource identified in the resource metadata; and
reconciling the in-progress request with the resource status.
16. The one or more non-transitory computer-readable media of claim 15 , wherein reconciling the in-progress request comprises, in accordance with the resource status indicating a committed status, committing the resource request.
17. The one or more non-transitory computer-readable media of claim 15 , wherein reconciling the in-progress request comprises, in accordance with the resource status indicating an in-progress status, rescheduling the resource request after a second predefined timeout.
18. The one or more non-transitory computer-readable media of claim 15 , wherein reconciling the in-progress request comprises, in accordance with the resource status indicating an aborted status, aborting the resource request, at least in part by removing the resource request from the data store.
19. The one or more non-transitory computer-readable media of claim 14 , wherein determining that the resource request is to be persisted comprises:
receiving a resource usage corresponding to the resource request; and
determining a quota limit for the resource request based at least in part on the resource metadata.
20. The one or more non-transitory computer-readable media of claim 14 , wherein the resource metadata comprises at least one of a resource identifier, a compartment identifier, an availability domain, a resource kind, a resource status, a last transaction identifier, or a tenancy identifier.