MIGRATION IN PLACE

• US 20130282791A1
• Filed: 04/19/2012
• Published: 10/24/2013
• Est. Priority Date: 04/19/2012
• Status: Active Grant

• Current Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Original Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Inventors: Kruglick, Ezekiel
• Granted Patent: US 8,880,704 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/119 Details of migration of file systems migration mechanisms in storage systems G06F3/0647
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06F 3/0647 Migration mechanisms
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

Technologies related to migration in place are generally described. In some examples, software and/or data associated with a platform customer can be “migrated” to a new platform while allowing the platform customer'"'"'s software and/or data to remain on same hardware. A data center and/or Infrastructure as a Service (IaaS) provider may be configured to support migration in place for example by providing hardware identifiers upon request, providing platform identifiers upon request, providing platform compatibility information upon request and/or approving platforms for migration in place operations, deploying platform modules to migration in place hardware, providing user session support during migration in place operations, and/or performing security operations.

Claims

1-27. -27. (canceled)

28. A method comprising:

providing a plurality of servers for use by a plurality of platform providers, wherein each of the platform providers is associated with one or more platform customers, and wherein each of the platform customers is associated with customer data that is stored on one or more of the plurality of servers;

receiving a hardware identification request, wherein the hardware identification request comprises a request to identify servers comprising platform customer data associated with an identified platform customer of a first platform provider;

providing, in response to the hardware identification request, one or more hardware identifiers corresponding to servers comprising platform customer data associated with the identified platform customer;

receiving a migration in place request, the migration-in place request comprising a request to deploy platform service modules of an identified platform service provider to the servers comprising platform customer data associated with the identified platform customer; and

deploying, in response to the migration in place request, platform service modules of the identified service provider to the one or more of the plurality of servers comprising platform customer data associated with the identified platform customer.

29. The method of claim 28, further comprising directing an increasing number of service calls associated with the identified platform customer to a platform provided by the identified platform provider as the identified platform customer'"'"'s data is migrated to the platform provided by the identified platform provider.

30. The method of claim 28, further comprising providing a User Interface (UI) or Application Programming Interface (API) comprising a hardware identification request control, wherein the hardware identification request is received via the UI or API and the one or more hardware identifiers are provided via the UI or API.

31. The method of claim 28, further comprising receiving a platform compatibility request comprising one or more hardware identifiers and providing, in response to the platform compatibility request, platform compatibility information defining platform compatibility of one or more platforms with hardware identified in the platform compatibility request.

32. The method of claim 28, wherein the one or more hardware identifiers provided in response to the hardware identification request comprise limited-use hardware identifiers.

33. A server comprising:

a processor;

a memory; and

a hardware identification request service module stored in the memory and executable by the processor, wherein the hardware identification request service module is configured to;

receive a hardware identification request, wherein the hardware identification request comprises a request to identify servers comprising platform customer data associated with an identified platform customer of a first platform provider of a plurality of platform providers, wherein each of the platform providers is associated with one or more platform customers, and wherein each of the platform customers is associated with customer data that is stored on one or more of a plurality of servers; and

provide, in response to the hardware identification request, one or more hardware identifiers corresponding to servers comprising platform customer data associated with the identified platform customer; and

a migration in place deployment module stored in the memory and executable by the processor, wherein the migration in place deployment module is configured to;

receive a migration in place request, the migration-in place request comprising a request to deploy platform service modules of an identified platform service provider to the servers comprising platform customer data associated with the identified platform customer; and

deploy, in response to the migration in place request, platform service modules of the identified service provider to the one or more of the plurality of servers comprising platform customer data associated with the identified platform customer.

34. The server of claim 33, further comprising a Session Border Controller (SBC) module stored in the memory and executable by the processor, wherein the SBC module is configured to direct an increasing number of service calls associated with the identified platform customer to a platform provided by the identified platform provider as the identified platform customer'"'"'s data is migrated to the platform provided by the identified platform provider.

35. The server of claim 33, further comprising a User Interface (UI) or Application Programming Interface (API) module stored in the memory and executable by the processor, wherein the UI or API module is configured to:

provide a UI or API comprising a hardware identification request control;

receive the hardware identification request via the hardware identification request control in the UI or API; and

provide the one or more hardware identifiers corresponding to the servers comprising platform customer data associated with the identified platform customer via the UI or API.

36. The server of claim 33, further comprising a platform compatibility module stored in the memory and executable by the processor, wherein the platform compatibility module is configured to receive a platform compatibility request comprising one or more hardware identifiers and to provide, in response to the platform compatibility request, platform compatibility information defining platform compatibility of one or more platforms with hardware identified in the platform compatibility request.

37. The server of claim 33, further comprising a security module stored in the memory and executable by the processor, wherein the security module is configured to generate limited-use hardware identifiers for use as hardware identifiers provided in response to hardware identification requests.

38. A non-transitory computer readable storage medium having computer executable instructions executable by a processor, the instructions that, when executed by the processor, cause the processor to:

receive a hardware identification request, wherein the hardware identification request comprises a request to identify servers comprising platform customer data associated with an identified platform customer of a first platform provider of a plurality of platform providers, wherein each of the platform providers is associated with one or more platform customers, and wherein each of the platform customers is associated with customer data that is stored on one or more of a plurality of servers; and

provide, in response to the hardware identification request, one or more hardware identifiers corresponding to servers comprising platform customer data associated with the identified platform customer; and

receive a migration in place request, the migration-in place request comprising a request to deploy platform service modules of an identified platform service provider to the servers comprising platform customer data associated with the identified platform customer; and

deploy, in response to the migration in place request, platform service modules of the identified service provider to the one or more of the plurality of servers comprising platform customer data associated with the identified platform customer.

39. The non-transitory computer readable storage medium of claim 38, wherein the instructions cause the processor to direct, with a Session Border Controller (SBC) module, an increasing number of service calls associated with the identified platform customer to a platform provided by the identified platform provider as the identified platform customer'"'"'s data is migrated to the platform provided by the identified platform provider.

40. The non-transitory computer readable storage medium of claim 38, wherein the instructions cause the processor to:

provide a UI or API comprising a hardware identification request control;

receive the hardware identification request via the hardware identification request control in the UI or API; and

provide the one or more hardware identifiers corresponding to the servers comprising platform customer data associated with the identified platform customer via the UI or API.

41. The non-transitory computer readable storage medium of claim 38, wherein the instructions cause the processor to receive a platform compatibility request comprising one or more hardware identifiers and to provide, in response to the platform compatibility request, platform compatibility information defining platform compatibility of one or more platforms with hardware identified in the platform compatibility request.

42. The non-transitory computer readable storage medium of claim 38, wherein the instructions cause the processor to generate limited-use hardware identifiers for use as hardware identifiers provided in response to hardware identification requests.