Type-to-type analysis for cloud computing technical components with translation scripts

• US 10,033,597 B2
• Filed: 11/04/2016
• Issued: 07/24/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): HUQ, FARZANA B
• Application Number:
  US15/343,307
• Publication Number:
  US 20170078161A1
• Time in Patent Office: 627 Days
• Field of Search: 709221
• 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

Cloud computing has emerged as an extremely popular implementation option for a wide range of computing services. However, provisioning services into the cloud is an extremely difficult technical challenge. This is due in part to the regular emergence of new cloud service providers, as well as the routine changing and reconfiguration of the disparate computing platforms, services, assets, supported technical components, and other features offered by the service providers. An analysis architecture determines how to map a particular technical component into the execution environment of any particular service provider with the aid of translation scripts.

Claims

1. A system comprising:

type definition circuitry configured to;

assign a first type specifier to a first component type available from a first service provider; and

assign a second type specifier to a second component type available from a second service provider;

property linking circuitry configured to;

link a first set of technical properties to the first component type; and

link a second set of second technical properties to the second component type;

property translation circuitry configured to;

establish a translation correspondence between the first set of technical properties for the first component type and the second set of technical properties for the second component type;

the translation correspondence including;

a script path field configured to;

specify whether a translation script will execute to facilitate translation of the first set of technical properties, by matching the script path field against a translation identifier for the first set of technical properties; and

at a time the translation script executes, specify a path for the translation script, the path identifying a specific location of the translation script within a file system;

input parameter fields that identify input parameters to take from the first component type in the first set of technical properties for input to the translation script; and

an output property identifier that identifies an output technical property into which the translation script will write a translation output after execution given the input parameters;

type mapping circuitry configured to;

translate the first component type into the second component type according to the translation correspondence, including execution of the translation script to generate a provisioning script, for provisioning the first component type at the second service provider as the second component type; and

job preparation circuitry configured to;

receive a provisioning request; and

responsive to the provisioning request;

access the provisioning script; and

based on the provisioning script, deploy the first component type at the second service provider as the second component type.

2. The system of claim 1, where the translation correspondence further includes:

a translation table comprising the script path field;

an input table comprising the input parameter fields; and

an output table comprising the output property identifier.

3. The system of claim 2, where:

the first set of technical properties comprises an input technical property of the first component type for translation; and

the input table is configured to assign the input technical property to a first translation identifier.

4. The system of claim 1, where:

the type mapping circuitry is further configured to;

obtain values for the input parameters; and

provide the values to the translation script.

5. The system of claim 3, where:

the output table is configured to link the first translation identifier to the second component type.

6. The system of claim 3, where the type mapping circuitry is configured to translate by:

executing the translation script to map multiple input technical properties of the first component type in the first set to fewer output technical properties of the second component type in the second set.

7. The system of claim 3, where the type mapping circuitry is configured to translate by:

executing the translation script to map an input technical property of the first component type in the first set to multiple output technical properties of the second component type in the second set.

8. The system of claim 1, where:

the type mapping circuitry is further configured to, before translating the first component type into the second component type;

determine a first asset of the first component type, and an asset value for the first asset;

determine an asset substitution for the first asset, for provisioning the first asset to the second service provider; and

replace the asset value with the asset substitution.

9. A method comprising:

in a hybrid cloud architecture system;

with type definition circuitry;

assigning a first type specifier to a first component type available from a first service provider; and

assigning a second type specifier to a second component type available from a second service provider;

with property linking circuitry;

linking a first set of technical properties to the first component type; and

linking a second set of technical properties to the second component type;

with property translation circuitry;

establishing a translation correspondence between the first set of technical properties for the first component type and the second set of technical properties for the second component type, the translation correspondence including;

a script path field configured to;

specify whether a translation script will execute to facilitate translation of the first set of technical properties, by matching the script path field against a translation identifier for the first set of technical properties; and

at a time the translation script executes, specify a path for the translation script, the path identifying a specific location of the translation script within a file system;

input parameter fields that identify input parameters to take from the first component type in the first set of technical properties for input to the translation script; and

an output property identifier that identifies an output technical property into which the translation script will write a translation output after execution given the input parameters;

with type mapping circuitry;

translating the first component type into the second component type according to the translation correspondence, including executing the translation script to generate a provisioning script, for provisioning the first component type at the second service provider as the second component type; and

with job preparation circuitry;

receiving a provisioning request; and

responsive to the provisioning request;

accessing the provisioning script; and

based on the provisioning script, deploying the first component type at the second service provider as the second component type.

10. The method of claim 9, where the translation correspondence further includes:

a translation table comprising the script path field;

an input table comprising the input parameter fields; and

an output table comprising the output property identifier.

11. The method of claim 9, where:

the first set of technical properties comprises an input technical property of the first component type for translation; and

further comprising;

assigning the input technical property to a first translation identifier.

12. The method of claim 9, further comprising:

setting input parameter names for the translation script in the input parameter fields, when the script path field identifies the translation script.

13. The method of claim 12, further comprising:

obtaining values for the input parameters; and

providing the values to the translation script through the input parameter names.

14. The method of claim 11, further comprising:

executing the translation script to map multiple input technical properties of the first component type in the first set to fewer output technical properties of the second component type in the second set, or

executing the translation script to map an input technical property of the first component type in the first set to multiple output technical properties of the second component type in the second set.

15. The method of claim 9, further comprising:

with the type mapping circuitry and before translating the first component type into the second component type;

determine a first asset of the first component type, and an asset value for the first asset;

determine an asset substitution for the first asset, for provisioning the first asset to the second service provider; and

replace the asset value with the asset substitution.

16. A product comprising:

a machine readable medium other than a transitory signal; and

instructions stored on the machine readable medium for execution by system circuitry to implement;

type definition circuitry configured to;

assign a first type specifier to a first component type available from a first service provider; and

assign a second type specifier to a second component type available from a second service provider;

property linking circuitry configured to;

link a first set of technical properties to the first component type; and

link a second set of technical properties to the second component type;

property translation circuitry configured to;

establish a translation correspondence between the first set of technical properties for the first component type and the second set of technical properties for the second component type;

the translation correspondence including;

a script path field configured to;

specify whether a translation script will execute to facilitate translation of the first set of technical properties, by matching the script path field against a translation identifier for the first set of technical properties; and

at a time the translation script executes, specify a path for the translation script, the path identifying a specific location of the translation script within a file system;

input parameter fields that identify input parameters to take from the first component type in the first set of technical properties for input to the translation script; and

an output property identifier that identifies an output technical property into which the translation script will write a translation output after execution given the input parameters;

type mapping circuitry configured to;

translate the first component type into the second component type according to the translation correspondence, including executing the translation script to generate a provisioning script, for provisioning the first component type at the second service provider as the second component type; and

job preparation circuitry configured to;

receive a provisioning request; and

responsive to the provisioning request;

access the provisioning script; and

based on the provisioning script, deploy the first component type at the second service provider as the second component type.

17. The product of claim 16, where the translation correspondence further includes:

a translation table comprising the script path field;

an input table comprising the input parameter fields; and

an output table comprising the output property identifier.

18. The product of claim 17, where:

the first set of technical properties comprises an input technical property of the first component type for translation; and

the input table is configured to assign the input technical property to a first translation identifier.

19. The product of claim 18, where:

the output table is configured to link the first translation identifier to the second component type.

20. The product of claim 16, where:

the type mapping circuitry is further configured to, before translating the first component type into the second component type;

determine a first asset of the first component type, and an asset value for the first asset;

determine an asset substitution for the first asset, for provisioning the first asset to the second service provider; and

replace the asset value with the asset substitution.