Migration in place by infrastructure deployment of platforms to customer hardware

• US 8,880,704 B2
• Filed: 04/19/2012
• Issued: 11/04/2014
• 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
• Primary Examiner(s): VU, VIET DUY
• Application Number:
  US13/578,025
• Publication Number:
  US 20130282791A1
• Time in Patent Office: 929 Days
• Field of Search: 709/213, 709/214, 709/215, 709/217, 709/218, 709/223, 709/226
• US Class Current: 709/226
• 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. An infrastructure provider method comprising:

providing, by the infrastructure provider, a plurality of servers for a plurality of platform providers and platform customers, wherein;

each of the platform providers provides platform service modules, at one or more of the servers, for one or more platform customers; and

each of the platform customers is associated with platform customer data stored at one or more of the servers and supported by platform service modules of a platform provider selected by each platform customer;

receiving, by the infrastructure provider, a hardware identification request, wherein the hardware identification request comprises a request to identify servers storing an identified platform customer'"'"'s data;

providing, by the infrastructure provider, in response to the hardware identification request, requested hardware identifiers identifying the servers storing the identified platform customer'"'"'s data;

receiving, by the infrastructure provider, a migration in place request, the migration in place request comprising a request to switch the identified platform customer'"'"'s data from a first platform provider to a second platform provider while the identified platform customer'"'"'s data remains at the same servers storing the identified platform customer'"'"'s data as identified in response to the hardware identification request; and

deploying, by the infrastructure provider, in response to the migration in place request, platform service modules of the second platform provider to the same servers storing the identified platform customer'"'"'s data as identified in response to the hardware identification request;

wherein the platform service modules of the second platform provider are adapted to migrate the identified platform customer'"'"'s data from platform service modules of the first platform provider to the platform service modules of the second platform provider while the identified platform customer'"'"'s data remains at the same servers storing the identified platform customer'"'"'s data as identified in response to the hardware identification request.

2. The method of claim 1, further comprising directing, by the infrastructure provider, an increasing number of service calls to the platform service modules of the second platform provider as the identified platform customer'"'"'s data is migrated to the platform service modules of the second platform provider.

3. The method of claim 1, further comprising providing, by the infrastructure provider, a User Interface (UI) or Application Programming Interface (API) comprising a hardware identification request control, wherein the infrastructure provider receives the hardware identification request via the UI or API and wherein the infrastructure provider provides the requested hardware identifiers via the UI or API.

4. The method of claim 1, further comprising:

receiving, by the infrastructure provider, a platform compatibility request comprising the requested hardware identifiers; and

providing, by the infrastructure provider, in response to the platform compatibility request, platform compatibility information defining whether the platform service modules of the second platform provider are compatible with the servers storing the identified platform customer'"'"'s data, as identified by the requested hardware identifiers.

5. The method of claim 1, wherein the requested hardware identifiers provided in response to the hardware identification request comprise limited-use hardware identifiers.

6. An infrastructure provider server for an infrastructure provider that provides hardware comprising a plurality of servers for a plurality of platform providers and platform customers, wherein each of the platform providers provides platform service modules, at one or more of the servers, for one or more platform customers, and wherein each of the platform customers is associated with platform customer data stored at one or more of the servers and supported by platform service modules of a platform provider selected by each platform customer, the infrastructure provider server comprising:

a processor;

a memory; and

a hardware identification request service module and a migration in place deployment 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 storing an identified platform customer'"'"'s data; and

provide, in response to the hardware identification request, requested hardware identifiers identifying the servers storing the identified platform customer'"'"'s data; and

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 switch the identified platform customer'"'"'s data from a first platform provider to a second platform provider while the identified platform customer'"'"'s data remains at the same servers storing the identified platform customer'"'"'s data as identified in response to the hardware identification request; and

deploy, in response to the migration in place request, platform service modules of the second platform provider to the same servers storing the identified platform customer'"'"'s data as identified in response to the hardware identification request;

wherein the platform service modules of the second platform provider are adapted to migrate the identified platform customer'"'"'s data from platform service modules of the first platform provider to the platform service modules of the second platform provider while the identified platform customer'"'"'s data remains at the same servers storing the identified platform customer'"'"'s data as identified in response to the hardware identification request.

7. The infrastructure provider server of claim 6, 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 to the platform service modules of the second platform provider as the identified platform customer'"'"'s data is migrated to the platform service modules of the second platform provider.

8. The infrastructure provider server of claim 6, 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 requested hardware identifiers via the UI or API.

9. The infrastructure provider server of claim 6, 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 the requested hardware identifiers; and

provide, in response to the platform compatibility request, platform compatibility information defining whether the platform service modules of the second platform provider are compatible with the servers storing the identified platform customer'"'"'s data, as identified by the requested hardware identifiers.

10. The infrastructure provider server of claim 6, 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 the requested hardware identifiers.

11. A non-transitory computer readable storage medium for an infrastructure provider that provides hardware comprising a plurality of servers for a plurality of platform providers and platform customers, wherein each of the platform providers provides platform service modules, at one or more of the servers, for one or more platform customers, and wherein each of the platform customers is associated with platform customer data stored at one or more of the servers and supported by platform service modules of a platform provider selected by each platform customer, the 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 storing an identified platform customer'"'"'s data; and

provide, in response to the hardware identification request, requested hardware identifiers identifying the servers storing the identified platform customer'"'"'s data; and

receive a migration in place request, the migration-in place request comprising a request to switch the identified platform customer'"'"'s data from a first platform provider to a second platform provider while the identified platform customer'"'"'s data remains at the same servers storing the identified platform customer'"'"'s data as identified in response to the hardware identification request; and

deploy, in response to the migration in place request, platform service modules of the second platform provider to the same servers storing the identified platform customer'"'"'s data as identified in response to the hardware identification request;

wherein the platform service modules of the second platform provider are adapted to migrate the identified platform customer'"'"'s data from platform service modules of the first platform provider to the platform service modules of the second platform provider while the identified platform customer'"'"'s data remains at the same servers storing the identified platform customer'"'"'s data as identified in response to the hardware identification request.

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

13. The non-transitory computer readable storage medium of claim 11, 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 requested hardware identifiers via the UI or API.

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

receive a platform compatibility request comprising the requested hardware identifiers; and

provide, in response to the platform compatibility request, platform compatibility information defining whether the platform service modules of the second platform provider are compatible with the servers storing the identified platform customer'"'"'s data, as identified by the requested hardware identifiers.

15. The non-transitory computer readable storage medium of claim 11, wherein the instructions cause the processor to generate limited-use hardware identifiers for use as the requested hardware identifiers.