Multi-cloud provisioning architecture with template aggregation

• US 10,547,520 B2
• Filed: 08/21/2015
• Issued: 01/28/2020
• 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): Bates, Kevin T
• Assistant Examiner(s): Patel, Ronak
• Application Number:
  US14/832,652
• Publication Number:
  US 20160164753A1
• Time in Patent Office: 1,621 Days
• Field of Search: None
• 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 analyses that successfully provisions complex cloud computing services. The provisioning architecture disaggregates resources into individual provisioning actions, and also selectively re-aggregates the resources into template blocks which a service provider accepts for native provisioning.

Claims

1. A system comprising:

template dispatcher circuitry;

job preparation circuitry in communication with the template dispatcher circuitry, the job preparation circuitry configured to;

receive a provisioning request message for a system deployment from the template dispatcher circuitry, the system deployment including aggregated deployment of multiple virtual machines;

obtain a template identifier from the provisioning request message;

obtain a provisioning template specified by the template identifier for implementing the system deployment, the provisioning template providing a single resource provisioning task for the aggregate deployment of the multiple virtual machines; and

disaggregate individual ones of the multiple virtual machines in the provisioning template into separately queueable resource provisioning tasks for corresponding disaggregated individual ones of the multiple virtual machines; and

resource correlation circuitry in communication with the job preparation circuitry, the resource correlation circuitry configured to;

determine, based on one or more characteristics of individual ones of the multiple virtual machines and using a pre-defined correlation test, correlated virtual machines among the disaggregated individual ones of the multiple virtual machines;

re-aggregate the correlated virtual machines into a common resource provisioning template block for provisioning the correlated virtual machines together on a cloud queue as a single queued item; and

submit the common resource provisioning template block to provisioning workflow circuitry that handles provisioning of the correlated virtual machines.

2. The system of claim 1, where:

the resource correlation circuitry is further configured to;

determine un-correlated virtual machines among the disaggregated individual ones of the multiple virtual machines; and

for each of the un-correlated virtual machines, submit a separate provisioning message to the provisioning workflow circuitry.

3. The system of claim 1, where:

the resource correlation circuitry is configured to determine that disaggregated individual ones of the multiple virtual machines are correlated virtual machines when they have a common resource provider region specifier.

4. The system of claim 1, where:

the resource correlation circuitry is configured to determine that disaggregated individual ones of the multiple virtual machines are correlated virtual machines when they will be placed in a common resource provider region, and when each of the disaggregated individual ones of the multiple virtual machines is template deployable in the common resource provider region.

5. The system of claim 4, further comprising:

a correlation application programming interface (API) to resource information circuitry, the correlation API defining a correlation data request interface; and

where the resource correlation circuitry is configured to query the correlation data request interface to determine;

whether the disaggregated individual ones of the multiple virtual machines will be placed in the common resource provider region; and

whether the disaggregated individual ones of the multiple virtual machines are template deployable in the common resource provider region.

6. The system of claim 5, where:

the resource correlation circuitry is further configured to query the correlation data request interface for a provisioning script identifier; and

communicate the provisioning script identifier to the provisioning workflow circuitry with the common resource provisioning template block.

7. The system of claim 6, where:

the provisioning script identifier comprises a resource locator for a provisioning script in a script repository in communication with the provisioning workflow circuitry.

8. The system of claim 7, where:

the provisioning script comprises a pass-through execution instruction configured to pass the common resource provisioning template block to the common resource provider region, and communicate a provisioning instruction to the common resource provider region to natively instantiate the correlated virtual machines specified in the common resource provisioning template block.

9. The system of claim 1, further comprising:

a return queue configured to receive a provisioning result message from the provisioning workflow circuitry; and

where the resource correlation circuitry is configured to receive the provisioning result message and provide the provisioning result message to the job preparation circuitry.

10. A system comprising:

template dispatcher circuitry configured to;

prepare a provisioning request message comprising a template identifier of a provisioning template specifying implementation of a first virtual machine aggregated with implementation of a second virtual machine; and

submit the provisioning request message to initiate provisioning of the first virtual machine and second virtual machine;

job preparation circuitry in communication with the template dispatcher circuitry, the job preparation circuitry configured to;

receive the provisioning request message from the template dispatcher circuitry;

obtain the template identifier from the provisioning request message;

retrieve the provisioning template specified by the template identifier, the provisioning template specifying implementation for both the first virtual machine and the second virtual machine, the provisioning template providing a single resource provisioning task for aggregated deployment of the first and second virtual machines; and

disaggregate the first virtual machine from the second virtual machine, by preparing separately queueable resource provisioning tasks for the first virtual machine and the second virtual machine; and

resource correlation circuitry in communication with the job preparation circuitry, the resource correlation circuitry configured to;

query a resource service on the first virtual machine and obtain a first service provider region identifier and a first aggregation indicator;

query the resource service on the second virtual machine and obtain a second service provider region identifier and a second aggregation indicator;

determine that the first service provider region identifier and the second service provider region identifier both identify a common service provider region;

determine that the first aggregation indicator is True;

determine that the second aggregation indicator is True;

responsive to the first and second aggregation flags being determined to be True, determine that aggregation is allowed;

after determining aggregation is allowed, re-aggregate the first virtual machine and the second virtual machine into a common resource provisioning template block for provisioning the first and second virtual machines together on a cloud queue as a single queued item; and

submit the common resource provisioning template block to provisioning workflow circuitry tasked with facilitating provisioning of the correlated first and second virtual machines.

11. The system of claim 10, further comprising:

a tenant-specific queue for an on-premises cloud region, the tenant-specific queue configured for secure access by the on-premises cloud region through access credentials specific to the on-premises cloud region;

a public cloud queue for a public cloud region, the public cloud queue configured to allow access by public cloud provisioning workflow circuitry that communicates provisioning instructions to multiple different public cloud service providers; and

where the resource correlation circuitry is further configured to;

route the common resource provisioning template block to the public cloud queue for retrieval by the public cloud provisioning workflow circuitry, when the common service provider region is the public cloud region; and

route the common resource provisioning template block to the tenant-specific queue for retrieval by on-premises cloud provisioning workflow circuitry, when the common service provider region is the on-premises cloud region.

12. A method comprising:

in a multi-cloud provisioning machine;

with job preparation circuitry;

receiving a provisioning request message for a system deployment from template dispatcher circuitry, the system deployment including aggregated deployment of multiple virtual machines;

obtaining a template identifier from the provisioning request message;

obtaining a provisioning template specified by the template identifier for implementing the system deployment, the provisioning template providing a single resource provisioning task for the aggregate deployment of the multiple virtual machines; and

disaggregating individual ones of the multiple virtual machines in the provisioning template into separately queueable resource provisioning tasks for corresponding disaggregated the individual ones of the multiple virtual machines; and

with resource correlation circuitry;

determining, based on one or more characteristics of individual ones of the multiple virtual machines and using a pre-defined correlation test, correlated virtual machines among the disaggregated individual ones of the multiple virtual machines;

re-aggregating the correlated virtual machines into a common resource provisioning template block for provisioning the correlated virtual machines together on a cloud queue as a single queued item; and

submitting the common resource provisioning template block to provisioning workflow circuitry for carrying out provisioning of the correlated resources.

13. The method of claim 12, further comprising:

with the resource correlation circuitry;

determining un-correlated virtual machines among the disaggregated individual ones of the multiple virtual machines; and

submitting a separate provisioning message to the provisioning workflow circuitry for each of the un-correlated virtual machines.

14. The method of claim 12, further comprising:

with the resource correlation circuitry;

determining that disaggregated individual ones of the multiple virtual machines are correlated virtual machines when they are implemented in a common resource provider region.

15. The method of claim 12, further comprising:

with the resource correlation circuitry;

determining, as the correlated virtual machines, those disaggregated individual ones of the multiple virtual machines to be placed in a common resource provider region and that are template deployable in the common resource provider region.

16. The method of claim 15, further comprising:

with the resource correlation circuitry;

querying a correlation data request interface to determine;

whether the disaggregated individual ones of the multiple virtual machines will be placed in the common resource provider region; and

whether the disaggregated individual ones of the multiple virtual machines are template deployable in the common resource provider region.

17. The method of claim 16, further comprising:

with the resource correlation circuitry;

querying the correlation data request interface for a provisioning script identifier; and

communicating the provisioning script identifier to the provisioning workflow circuitry with the common resource provisioning template block.

18. The method of claim 17, further comprising:

receiving a resource locator as the provisioning script identifier, the resource locator pointing to a provisioning script in a script repository in communication with the provisioning workflow circuitry.

19. The method of claim 18, further comprising:

executing the provisioning script to pass the common resource provisioning template block to the common resource provider region; and

communicating a provisioning instruction to the common resource provider region to request the common resource provider region to natively instantiate the correlated virtual machines specified in the common resource provisioning template block.

20. The method of claim 12, further comprising:

receiving, in a return queue, a provisioning result message from the provisioning workflow circuitry; and

passing the provisioning result message to the job preparation circuitry.