Type-to-type analysis for cloud computing technical components with translation through a reference type

• US 10,033,598 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,324
• Publication Number:
  US 20170078162A1
• 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, including translation through a reference type.

Claims

1. A system comprising:

hardware microprocessor circuitry comprising;

type definition circuitry configured to;

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

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, the first set of technical properties comprising an input technical property of the first component type for translation; and

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

property translation circuitry configured to;

establish a type 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;

assign the input technical property to a first translation identifier;

specify whether a translation script exists for the input technical property and provide a script path field for identifying the translation script; and

specify a script variable field for the translation script, the script variable field comprising a script variable name; and

type mapping circuitry configured to;

translate the first component type into the second component type by translating the first component type into a reference type and the reference type into the second component type, according to the type translation correspondence, for provisioning the first component type at the second service provider as the second component type;

obtain a value of the input technical property; and

provide the value to the translation script through the script variable name.

2. The system of claim 1, where:

the property translation circuitry comprises an input table that assigns the input technical property to the first translation identifier.

3. The system of claim 2, where:

the property translation circuitry further comprises a translation table configured to specify whether the translation script exists and include the script path field for identifying the translation script; and

the input table specifies the script variable field.

4. The system of claim 1, where:

the reference type comprises a most commonly represented type among technical service templates available to the system.

5. The system of claim 4, where:

the technical service templates are present in a pre-defined library of technical service templates that provide a baseline specification of resources that implement technical service requests.

6. The system of claim 4, further comprising:

translation and equivalency tables from the first component type to the reference type and from the reference type to the second component type.

7. The system of claim 2, where:

the second set of technical properties comprises an output technical property of the second component type;

the property translation circuitry further comprises an output table configured to link the first translation identifier to the second component type; and

where;

the type mapping circuitry is configured to translate by;

mapping 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

mapping 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.

19. The system of claim 1, where the type translation correspondence is based on a first stored correspondence between the first component type and a reference type and a second stored correspondence between the second component type and the reference type.

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;

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, the first set of technical properties comprising an input technical property of the first component type for translation; 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;

assigning the input technical property to a first translation identifier;

specifying whether a translation script exists for the input technical property and includes a script path field for identifying the translation script; and

specifying a script variable field for the translation script, the script variable field comprising a script variable name; and

with type mapping circuitry;

translating the first component type into the second component type according to the translation correspondence by translating the first component type into a reference type and the reference type into the second component type, for provisioning the first component type at the second service provider as the second component type;

obtaining a value of the input technical property; and

providing the value to the translation script through the script variable name.

10. The method of claim 9, further comprising:

choosing the reference type to be a most commonly represented type among technical service templates available to the hybrid cloud architecture system.

11. The method of claim 10, where:

the technical service templates are present in a pre-defined library of technical service templates that provide a baseline specification of resources that implement technical service requests; and

/or

further comprising;

setting up translation and equivalency tables from the first component type to the reference type and from the reference type to the second component type.

12. The method of claim 9, where:

the second set of technical properties comprises an output technical property of the second component type;

the property translation circuitry further comprises an output table configured to link the first translation identifier to the second component type; and

where;

the type mapping circuitry is configured to translate by;

mapping 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

mapping 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.

13. The method of claim 9, further comprising:

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

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

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

replacing the asset value with the asset substitution.

14. The method of claim 9 where:

assigning the input technical property to a first translation identifier comprises assigning the input technical property via an input table; and

specifying whether a translation script exists comprises specifying whether a translation script exists via a translation table.

15. A product comprising:

a non-transitory machine readable medium; and

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

type definition circuitry configured to;

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

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, the first set of technical properties comprising an input technical property of the first component type for translation; and

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

property translation circuitry configured to;

establish a type 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;

assign the input technical property to a first translation identifier;

specify whether a translation script exists for the input technical property and includes a script path field for identifying the translation script; and

specify a script variable field for the translation script, the script variable field comprising a script variable name; and

type mapping circuitry configured to;

translate the first component type into the second component type by translating the first component type into a reference type and the reference type into the second component type, according to the type translation correspondence, for provisioning the first component type at the second service provider as the second component type;

obtain a value of the input technical property; and

provide the value to the translation script through the script variable name.

16. The product of claim 15, where:

the property translation circuitry further comprises;

a translation table configured to specify whether the translation script exists and include the script path field for identifying the translation script; and

an input table configured to specify the script variable field.

17. The product of claim 15, where:

the second set of technical properties comprises an output technical property of the second component type;

the property translation circuitry further comprises an output table configured to link a first translation identifier to the second component type; and

where;

the type mapping circuitry is configured to translate by;

mapping 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

mapping 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.

18. The product of claim 15, 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.

20. The product of claim 15, where the type translation correspondence is based on a first stored correspondence between the first component type and a reference type and a second stored correspondence between the second component type and the reference type.