Dynamic network component placement
First Claim
Patent Images
1. A system comprising:
- placement pipeline circuitry comprising multiple processing stages, the placement pipeline circuitry configured to determine an initial placement location from initial placement options for a technical component defined within a request template of a specified service request;
timing metadata linked to the technical component and included within the request template, the timing metadata defining a dynamic re-evaluation timing specifier for re-evaluating placement of the technical component;
trigger metadata linked to the technical component and included within the request template, the trigger metadata defining a dynamic re-evaluation trigger condition specifier for re-evaluating the placement of the technical component; and
re-evaluation circuitry configured to, responsive to the dynamic re-evaluation timing specifier, the dynamic re-evaluation trigger condition specifier, or both, re-execute the placement pipeline circuitry on the technical component and determine updated placement options including a new placement location for the technical component; and
wherein the placement pipeline circuitry comprises a subscription stage configured to;
determine to a change to which service provider regions a resource requester has active subscriptions; and
responsive to the change, determine the new placement location.
1 Assignment
0 Petitions
Accused Products
Abstract
A network component placement architecture addresses the difficult technical challenge of determining where specific technical components of an overall service may be provisioned. However, the placement decision can change over time in response to complex updates relating to service providers, the regions they support, the assets they support, and many other dynamic factors. Dynamic network component placement effectively determines updated possibilities for placing the technical components of a specified service, while meeting all of the applicable technical constraints on the placement of the technical components.
122 Citations
18 Claims
-
1. A system comprising:
-
placement pipeline circuitry comprising multiple processing stages, the placement pipeline circuitry configured to determine an initial placement location from initial placement options for a technical component defined within a request template of a specified service request; timing metadata linked to the technical component and included within the request template, the timing metadata defining a dynamic re-evaluation timing specifier for re-evaluating placement of the technical component; trigger metadata linked to the technical component and included within the request template, the trigger metadata defining a dynamic re-evaluation trigger condition specifier for re-evaluating the placement of the technical component; and re-evaluation circuitry configured to, responsive to the dynamic re-evaluation timing specifier, the dynamic re-evaluation trigger condition specifier, or both, re-execute the placement pipeline circuitry on the technical component and determine updated placement options including a new placement location for the technical component; and wherein the placement pipeline circuitry comprises a subscription stage configured to; determine to a change to which service provider regions a resource requester has active subscriptions; and responsive to the change, determine the new placement location. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A method comprising:
-
in a hybrid cloud architect; receiving a technical service template for implementing a service request for a resource requester; identifying a resource within the technical service template; executing, for the resource, placement pipeline circuitry comprising multiple processing stages configured to determine an initial placement from initial placement options for the resource; obtaining, from within the hybrid cloud architect, timing metadata linked to the resource and included within the technical service template, the timing metadata defining a timing specifier for re-evaluating placement of the resource; obtaining, from within the hybrid cloud architect, trigger metadata linked to the resource and included within the technical service template, the trigger metadata defining a dynamic re-evaluation trigger condition specifier for re-evaluating the placement of the resource; executing re-evaluation circuitry configured to, responsive to the timing metadata, the trigger metadata, or both, determine when to re-execute the placement pipeline circuitry for the resource and determine updated placement options including a new placement location for the resource; and at a metadata architecture of the hybrid cloud architect; determining a change to which service provider regions qualify to provision the resource; and responsive to the change, determining the new placement location. - View Dependent Claims (12, 13, 14)
-
-
15. A system comprising:
-
a communication interface configured to receive a technical service template configured to implement a technical service request from a resource requester; a metadata architecture comprising; container metadata for a container hierarchy defining a model of the resource requester; resource requester metadata included within the technical service template, the resource requester metadata defining specific implementation data for the technical service request; and service provider metadata defining capabilities of candidate service provider regions for hosting the technical service request; timing metadata linked to a computing resource and included within the technical service template, the timing metadata defining a dynamic re-evaluation timing specifier for re-evaluating placement of the computing resource; trigger metadata linked to the computing resource and included within the technical service template, the trigger metadata defining a dynamic re-evaluation trigger condition specifier for re-evaluating placement of the computing resource; placement pipeline circuitry configured to; determine the computing resource defined within the technical service template, the computing resource for implementing the technical service request; receive the container metadata, the service provider metadata, and the resource requester metadata; execute sequential pipeline stages to determine feasible placement options for the computing resource from among candidate placement options responsive to the container metadata, the service provider metadata, and the resource requester metadata; determine a change to which service provider regions qualify to provision the resource; and responsive to the change, determine the new placement location re-evaluation circuitry configured to, responsive to the timing metadata, trigger metadata, or both, re-execute the placement pipeline circuitry on the computing resource and determine updated placement options including a new placement location for the computing resource. - View Dependent Claims (16, 17, 18)
-
Specification