IP Library Granted Patent US 8,949,654
Granted Patent B2
US 8,949,654 · App. 13/582,741 · Granted Feb 3, 2015

Parameterized dynamic model for cloud migration

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,949,654
App. No.
13/582,741
Granted
Feb 3, 2015
Kind
B2
Abstract

Technologies are generally presented for a migration system and a method for moving data and applications from a cloud or non-cloud network to a cloud network employing a Parameterized Dynamic Model (PDM) having one or more multi-dimensional parameters. In some examples, the PDM parameters may represent the Service level Agreement (SLA) requirements that a target cloud may need to satisfy for a successful cloud migration. The PDM may include a Model Execution Code (MEC) module configured to execute the PDM acting upon the PDM parameter in a cloud environment following the sequencing defined in the PDM as a sequencing parameter. The PDM-MEC based migration system may also include fault-tolerance and error recovery during the migration while the MEC code is executed.

Claims (37)

1. A method to implement a parameterized dynamic model (PDM) for cloud migration, the method comprising:

determining a plurality of PDM parameters with each parameter having one or more dimensions in an n-dimensional space, wherein the PDM defines service level agreement requirements to be met for migration from a source cloud to a target cloud; and

performing the cloud migration by executing the PDM according to a sequence defined by the PDM, wherein the PDM is a N×N dimensional model that is neither a matrix model nor a symmetrical model.

2. The method according to claim 1 , further comprising: defining in each dimension of a PDM parameter one from a set of a conditional limit, an attribute, a priority, and a fault tolerance action for the PDM parameter.

3. The method according to claim 1 , wherein the sequence of the PDM parameters is defined by a model execution code (MEC) with at least one fault tolerance feature and at least one backtracking feature.

4. The method according to claim 3 , wherein the MEC is part of one of: the PDM and an MEC module distinct from the PDM.

5. The method according to claim 3 , wherein the fault tolerance definition and the backtracking features are defined for one of each PDM parameter and a group of PDM parameters.

6. The method according to claim 3 , further comprising: enabling one of multiple retries and manual intervention to retune the PDM parameters through the fault-tolerance and back-tracking features in case of migration failure.

7. A computing device to implement a parameterized dynamic model (PDM) for cloud migration, the computing device comprising:

a memory configured to store instructions; and

a processing unit configured to execute a migration application in conjunction with the instructions, wherein the migration application is configured to:

determine a plurality of PDM performance parameters and notional parameters with each parameter having one or more dimensions, wherein the PDM defines service level agreement requirements to be met for migration from a source cloud to a target cloud, and wherein the notional parameters include model execution, sequencing of execution, error handling and reporting, temporary files creation, and clean-up at the target cloud; and

execute the PDM according to a sequence defined by the PDM.

8. The computing device according to claim 7 , wherein the sequence includes at least one of a parameter-to-parameter succession or a dimension-to-dimension succession.

9. The computing device according to claim 7 , wherein the migration application is further configured to:

determine the plurality of PDM parameters through at least one of automatic definition or manual definition; and

enable one of override and fine-tune one or more PDM parameters.

10. The computing device according to claim 7 , wherein the migration application is further configured to:

define one or more dimensions of the plurality of PDM parameters based on actual measurements in one of a cloud setting and a non-cloud setting.

11. The computing device according to claim 7 , wherein the plurality of PDM parameters is determined and the PDM executed by one or more of: a source cloud operator, a target cloud operator, and a third party facilitator.

12. The computing device according to claim 7 , wherein the PDM parameters define at least one from a set of: a server latency, a storage limit, a storage quota, a scalability factor, a backup guarantee, a computing power, a power backup, an uptime guarantee, a peak period load, a transaction processing timeout, a concurrent maximum users limit, a data roll back capacity, a real-time mirroring capability, a resource usage reporting capability, an audit trail capability, a support capability, and/or an automatic parallelization of code for a parallel computing environment.

13. The computing device according to claim 7 , wherein the dimensions of the PDM parameters include one or more of a numeric value and a logic value.

14. The computing device according to claim 7 , wherein the at least two PDM parameters have a distinct number of dimensions.

15. A non-transitory computer-readable storage medium having instructions stored thereon to implement a parameterized dynamic model (PDM) for cloud migration, the instructions comprising:

determining a plurality of PDM performance parameters and notional parameters with each parameter having one or more dimensions in an n-dimensional space, wherein the PDM defines service level agreement requirements to be met for migration from a source cloud to a target cloud, and wherein the notional parameters include model execution, sequencing of execution, error handling and reporting, temporary files creation, and clean-up at the target cloud; and

performing the cloud migration by executing the PDM according to a sequence defined by the PDM, wherein the PDM is a N×N dimensional model that is neither a matrix model nor a symmetrical model.

16. The non-transitory computer-readable storage medium of claim 15 , wherein the instructions further comprise:

defining in each dimension of a PDM parameter one from a set of a conditional limit, an attribute, a priority, and a fault tolerance action for the PDM parameter.

17. The non-transitory computer-readable storage medium of claim 15 , wherein the sequence of the PDM parameters is defined by a model execution code (MEC) with at least one fault tolerance feature and at least one backtracking feature defined for one of each PDM parameter and a group of PDM parameters, and wherein the instructions further comprise:

enabling one of multiple retries and manual intervention to retune the PDM parameters through the fault-tolerance and back-tracking features in case of migration failure.

18. The non-transitory computer-readable storage medium of claim 15 , wherein the instructions further comprise:

determining the plurality of PDM parameters through at least one of automatic definition or manual definition;

enabling a user to one of override and fine-tune one or more PDM parameters; and

defining one or more dimensions of the plurality of PDM parameters based on actual measurements in one of a cloud setting and a non-cloud setting.

19. The non-transitory computer-readable storage medium of claim 15 , wherein the instructions further comprise:

providing at least one of error reporting or final reporting associated with a migration attempt based on a user request.

20. The non-transitory computer-readable storage medium of claim 15 , wherein the cloud migration includes one of: a single source to multiple target migration, a multiple source to single target migration, and a multiple source to multiple target migration.

Assignments (2)
SECURITY INTEREST Recorded Jan 29, 2019
From: EMPIRE TECHNOLOGY DEVELOPMENT LLC
To: CRESTLINE DIRECT FINANCE, L.P.
Reel/Frame 048373/0217 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 4, 2012
From: HASIT, SETH
To: EMPIRE TECHNOLOGY DEVELOPMENT LLC
Reel/Frame 028905/0427 →