Cloud computing placement and provisioning architecture

• US 10,148,528 B2
• Filed: 08/21/2015
• Issued: 12/04/2018
• Est. Priority Date: 12/05/2014
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services Limited (Accenture PLC)
• Inventors: Cimprich, Patrick Francis, DeLuca, Michael Gerald, Cantwell, Jack Q. W., Peterson, Sean David, Wells, Marshall J.
• Primary Examiner(s): Serrao, Ranodhi
• Application Number:
  US14/832,679
• Publication Number:
  US 20160164727A1
• Time in Patent Office: 1,201 Days
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: 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
• CPC Class Codes: H04L 41/022 Multivendor or multi-standard integration
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/14 Network analysis or design
• CPC Class Codes: H04L 41/145 involving simulating, designing, planning or modelling of a network
• CPC Class Codes: H04L 41/5048 Automatic or semi-automatic definitions, e.g. definition templates
• CPC Class Codes: H04L 45/40 Wormhole routing
• CPC Class Codes: H04L 47/27 Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/808 User-type aware
• CPC Class Codes: H04L 47/83 based on usage prediction
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

Provisioning resources into the cloud is a constantly increasing technical challenge as more cloud service providers emerge, each offering disparate computing platforms, services, assets, supported technical components, and other features. A cloud computing provisioning architecture implements a sequence of complex technical analyzes that successfully provisions complex cloud computing services.

Claims

1. A system comprising:

a communication interface configured to receive a selection of a computing environment for provisioning from a resource requester;

placement circuitry in communication with the communication interface, the placement circuitry configured to;

determine placement options for a resource type for implementing the computing environment; and

obtain, from the resource requester, a selected placement from among the placement options through the communication interface;

type translation circuitry configured to;

determine a service provider region corresponding to the selected placement; and

reference a translation table defining a mapping between the resource type and a destination type for provisioning in the service provider region, wherein the translation table includes a translation identifier for mapping an input table corresponding to the resource type and an output table corresponding to the destination type, and wherein the translation table also includes a path field to an executable script that, when executed, facilitates translation of the resource type to the destination type;

after referencing the translation table and prior to initiating provisioning of the destination type within the service provider region, translate the resource type to the destination type based on execution of the executable script;

job preparation circuitry configured to prepare a new job and new tasks that implement the new job for provisioning the destination type; and

provisioning workflow circuitry configured to initiate provisioning of the destination type within the service provider region.

2. The system of claim 1, where:

the placement circuitry is configured to receive a technical service template for the computing environment, the technical service template specifying the resource type.

3. The system of claim 2, where:

the placement circuitry is further configured to receive, for determining the placement options;

container metadata characterizing a structural organization of the resource requester;

requester metadata specifying implementation options of the resource requester for the computing environment; and

service provider metadata specifying available technical components available from different service providers.

4. The system of claim 1, where:

the job preparation circuitry is further configured to store the new job and the new tasks in a pending job database as pending jobs with pending tasks.

5. The system of claim 4, further comprising:

polling circuitry configured to query the job preparation circuitry for the pending jobs with the pending tasks.

6. The system of claim 5, further comprising:

dispatcher circuitry configured to obtain the pending tasks and provide the pending tasks to the provisioning workflow circuitry.

7. The system of claim 6, where:

the provisioning workflow circuitry is configured to initiate provisioning of a destination type within the service provider region by sending the pending tasks to a service provider system responsible for instantiating resources in the service provider region.

8. The system of claim 1, where:

the resource type comprises a virtual machine.

9. The system of claim 1, where:

the resource type comprises a database.

10. The system of claim 1, where:

the resource type comprises a website.

11. A method comprising:

receiving, from a resource requester, a selection of a computing service for provisioning;

determining a technical service template that specifies a baseline implementation of a technical component supporting the computing service;

determining placement options for the technical component;

obtaining, from the resource requester, a selected placement from among the placement options that is different than the baseline implementation;

determining a service provider region corresponding to the selected placement;

referencing a translation table defining a mapping between the technical component and a destination component for provisioning in the service provider region, wherein the translation table includes a translation identifier for mapping an input table corresponding to the resource type and an output table corresponding to the destination type, and wherein the translation table also includes a path field to an executable script that, when executed, facilitates translation of the resource type to the destination type;

after referencing the translation table and prior to initiating provisioning of the destination component within the service provider region, translating the technical component to the destination component by executing the executable script;

preparing a new job composed of new tasks that implement the new job for provisioning the destination component;

storing the new job and the new tasks in a pending job database; and

initiating provisioning of the destination component within the service provider region.

12. The method of claim 11, further comprising:

retrieving the technical service template from a collection of pre-defined technical service templates.

13. The method of claim 11, further comprising:

determining the placement options responsive to;

container metadata characterizing a structural organization of the resource requester;

requester metadata specifying implementation options of the resource requester for the computing service; and

service provider metadata specifying available technical components available from different service providers.

14. The method of claim 11, further comprising:

polling the pending job database for pending jobs defined by pending tasks.

15. The method of claim 14, further comprising:

dispatching the pending tasks for provisioning.

16. The method of claim 15, where initiating provisioning comprises:

requesting a service provider system responsible for instantiating resources in the service provider region to execute the pending tasks.

17. A system comprising:

a communication interface configured to receive, from a resource requester, a selection of a computing service for provisioning;

a technical service template database comprising a technical service template that specifies a baseline implementation of a technical component of the computing service;

placement circuitry in communication with the communication interface, the placement circuitry configured to;

execute a sequence of placement pipeline stages to determine placement options for the technical component;

transmit, through the communication interface, the placement options to the resource requester; and

obtain through the communication interface, from the resource requester, a selected placement from among the placement options;

type translation circuitry configured to;

determine a service provider region corresponding to the selected placement; and

reference a translation table defining a mapping between the technical component and a destination component supported by the service provider region for provisioning in the service provider region, wherein the translation table includes a translation identifier for mapping an input table corresponding to the technical component and an output table corresponding to the destination component, and wherein the translation table also includes a path field to an executable script that, when executed, facilitates translation of the technical component to the destination component;

after referencing the translation table and prior to initiating provisioning of the destination component within the service provider region, translate the technical component to the destination component based on execution of the executable script;

polling circuitry configured to query for a provisioning job for the destination component; and

dispatcher circuitry configured to forward the provisioning job to provisioning workflow circuitry.

18. The system of claim 17, further comprising:

job preparation circuitry configured to;

prepare a new job and tasks that implement the new job for provisioning the destination component; and

store the new job and the tasks in a pending job database as pending jobs with pending tasks; and

where;

the provisioning workflow circuitry is configured to transmit the tasks to a service provider system for provisioning the destination component within the service provider region.

19. The system of claim 17, wherein the provisioning workflow circuitry is configured to initiate provisioning of the destination type within the service provider region.

20. The system of claim 17, wherein the placement circuitry is configured to receive, for determining the placement options:

container metadata characterizing a structural organization of the resource requester;

requester metadata specifying implementation options of the resource requester for the computing environment; and

service provider metadata specifying available technical components available from different service providers.