Network component placement architecture

Patent metadata

Field	Value
Publication number	US-2016191414-A1
Application number	US-201615066541-A
Country	US
Kind code	A1
Filing date	Mar 10, 2016
Priority date	Dec 5, 2014
Publication date	Jun 30, 2016
Grant date	—

Abstract

A network component placement architecture addresses the difficult technical challenge of determining where specific technical components of an overall service may be provisioned. The architecture is particularly effective at determining where, among a myriad of possible service provides, platforms, and regions, the technical components can be placed and meet all of the applicable technical constraints on the placement of the technical components. In one implementation, the placement architecture includes a sequence of pipeline stages that define an analysis sequence leading to a set of possible placement options.

First claim

What is claimed is:

1 . A system comprising:
a communication interface configured to receive a technical service request for a cloud-deployed resource from an external resource requester of the cloud-deployed resource; template circuitry configured to:
determine a baseline technical service template for implementing the cloud-deployed resource;
generate a concretized technical service template from the baseline technical service template by deciding parameter values for entries in the baseline technical service template; and
provide the concretized technical service template to placement pipeline circuitry comprising multiple sequential pipeline processing stages; and
placement pipeline circuitry configured to:
receive the concretized technical service template;
determine feasible placement options for the cloud-deployed resource from among candidate placement options by executing sequential pipeline processing stages including:
a subscription stage configured to determine to which service provider regions and networks the external resource requester has active subscriptions;
a network stage following the subscription stage and configured to determine which of the service provider regions support the networks;
a capacity stage following the network stage and configured to determine which of the service provider regions have sufficient capacity to meet implementation requirements for the cloud-deployed resource; and

communicate the feasible placement options to the external resource requester through the communication interface.

2 . The system of claim 1 , where:
the capacity stage is configure to: request and receive updated service provider metadata to obtain an updated snapshot of current capacity of the service provider regions.

3 . The system of claim 1 , where:
the sequential pipeline processing stages further include: a type stage following the subscription stage and configured to:
receive a candidate set of placement options for the cloud-deployed resource from the subscription stage; and
determine which of the service provider regions support the cloud-deployed resource.

4 . The system of claim 3 , where:
the type stage is configured to receive service provider metadata from a metadata database; and analyze the service provider metadata to facilitate the determination of which of the service provider regions support the cloud-deployed resource.

5 . The system of claim 3 , where:
the type stage is configured to initiate processing by type-to-type circuitry to analyze the cloud-deployed resource and determine an equivalent resource type to the cloud-deployed resource.

6 . The system of claim 5 , where:
determining the feasible placement options also comprises determining feasible placement options for the equivalent resource type.

7 . The system of claim 1 , where:
the sequential pipeline processing stages further include: an asset stage following the subscription stage and configured to:
determine an asset implementing, at least in part, the cloud-deployed resource; and
determine which of the service provider regions support the asset.

8 . The system of claim 7 , where:
the asset stage is configured to receive service provider metadata from a metadata database; and analyze the service provider metadata to facilitate the determination of which of the service provider regions support the asset.

9 . A method comprising:
receiving, through a communication interface, a technical service request for a cloud-deployed resource from an external resource requester of the cloud-deployed resource; determining a baseline technical service template for implementing the cloud-deployed resource; generating a concretized technical service template from the baseline technical service template by deciding parameter values for entries in the baseline technical service template; and providing the concretized technical service template to placement pipeline circuitry comprising multiple sequential pipeline processing stages; and executing placement pipeline circuitry configured to:
receive the concretized technical service template;
determine feasible placement options for the cloud-deployed resource from among candidate placement options by executing sequential pipeline processing stages including:
a subscription stage configured to determine to which service provider regions and networks the external resource requester has active subscriptions;
a network stage following the subscription stage and configured to determine which of the service provider regions support the networks;
a capacity stage following the network stage and configured to determine which of the service provider regions have sufficient capacity to meet implementation requirements for the cloud-deployed resource; and

communicating the feasible placement options to the external resource requester through the communication interface.

10 . The method of claim 9 , further comprising:
requesting and receiving, the capacity stage, updated service provider metadata to obtain an updated snapshot of current capacity of the service provider regions.

11 . The method of claim 9 , further comprising:
executing, in the sequential pipeline processing stages: a type stage following the subscription stage and configured to:
receive a candidate set of placement options for the cloud-deployed resource from the subscription stage; and
determine which of the service provider regions support the cloud-deployed resource.

12 . The method of claim 11 , further comprising:
receiving, at the type stage, service provider metadata from a metadata database; and analyzing/the service provider metadata to facilitate the determination of which of the service provider regions support the cloud-deployed resource.

13 . The method of claim 11 , further comprising:
initiating, by the type stage, processing by type-to-type circuitry to analyze the cloud-deployed resource and determine an equivalent resource type to the cloud-deployed resource.

14 . The method of claim 13 , further comprising:
determining feasible placement options for the equivalent resource type.

15 . The method of claim 9 , further comprising:
executing, in the sequential pipeline processing stages: an asset stage following the subscription stage and configured to:
determine a computing asset implementing, at least in part, the cloud-deployed resource; and
determine which of the service provider regions support the computing asset.

16 . The method of claim 15 , further comprising:
receiving, at the asset stage, service provider metadata from a metadata database; and analyzing the service provider metadata to facilitate the determination of which of the service provider regions support the computing asset.

17 . A system comprising:
a communication interface configured to receive a technical service request for a cloud-deployed resource from an external resource requester of the cloud-deployed resource; template circuitry configured to:
determine a baseline technical service template for implementing the cloud-deployed resource;
generate a concretized technical service template from the baseline technical service template by deciding parameter values for entries in the baseline technical service template; and
provide the concretized technical service template to placement pipeline circuitry comprising multiple sequential pipeline processing stages; and
placement pipeline circuitry configured to:
receive the concretized technical service template;

Assignees

• Accenture Global Services Ltd

Inventors

• Cimprich Patrick Francis
• Deluca Michael Gerald
• Cantwell Jack Q W
• Peterson Sean David
• Wells Marshall J

Classifications

• G06F9/5077

  Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455) · CPC title

• H04L41/082

  the condition being updates or upgrades of network functionality · CPC title

• H04L41/5048 Primary

  Automatic or semi-automatic definitions, e.g. definition templates · CPC title

• H04L41/0806

  for initial configuration or provisioning, e.g. plug-and-play · CPC title

• H04L41/022

  Multivendor or multi-standard integration · CPC title