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

Patent metadata

Field	Value
Publication number	US-2017078162-A1
Application number	US-201615343324-A
Country	US
Kind code	A1
Filing date	Nov 4, 2016
Priority date	Dec 5, 2014
Publication date	Mar 16, 2017
Grant date	—

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.

First claim

What is claimed is:

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

2 . The system of claim 1 , where:
the first set of technical properties comprises an input technical property of the first component type for translation; and the property translation circuitry comprises an input table that assigns the input technical property to a first translation identifier.

3 . The system of claim 2 , where:
the property translation circuitry further comprises a translation table configured to specify whether a translation script exists for the input technical property and includes a script path field for identifying the translation script; the input table specifies a script variable field for the translation script; the script variable field comprises a script variable name; and the type mapping circuitry is configured to: obtain a value of the input technical property; and provide the value to the translation script through the script variable name.

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.

9 . A method comprising:
in a hybrid cloud architecture system: with type definition circuitry:
assigning a first type specifier to the first component type available from the 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; and
linking a second set of second 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; 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.

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

11 . The method of claim 10 , further comprising:
specifying whether a translation script exists for the input technical property; providing a script path field for identifying the translation script; specifying a script variable field for the translation script; setting, in the script variable field, a script variable name, when the script path field identifies the translation script; obtaining a value of the input technical property; and providing the value to the translation script through the script variable name.

12 . 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 system.

13 . The method of claim 12 , 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.

14 . The method of claim 10 , 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.

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

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: t

Assignees

• Accenture Global Services Ltd

Inventors

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

Classifications

• H04L41/0806

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

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• H04L47/27

  Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets · CPC title

• H04L67/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 title

• H04L41/5041

  characterised by the time relationship between creation and deployment of a service · CPC title