Logical server management

• US 8,549,123 B1
• Filed: 03/16/2009
• Issued: 10/01/2013
• Est. Priority Date: 03/10/2009
• Status: Expired due to Fees

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Patil, Bapugouda, Wilkinson, Lyle Eric, Rozhin, Mark, Traynor, Mike, Beyh, Yehia S, Deadwiler, Byron R., de Moraes, Juliano Godinho Varaschin, Hudson, Phillip J.
• Primary Examiner(s): SHAW, PETER C
• Application Number:
  US12/405,175
• Time in Patent Office: 1,660 Days
• Field of Search: 709/203, 709/223, 709/226, 709/229, 718/1
• US Class Current: 709/223
• 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/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]

Abstract

A logical-server manager provides for deployment of a logical server to a real server so a network identity of said logical server and a network identity of said real server are conformed.

Claims

1. A system comprising non-transitory computer-readable storage media encoded with a logical-server manager to, when executed by a processor:

store a logical server in a logical-server database while said logical server is undeployed, said logical server having a logical-server network identity, said logical-server network identity and historical data being stored in association with said logical server in said logical-server database, said historical data including a list of real servers on which

said logical server has been deployed, said list specifying at least one real server on which said logical server is not currently deployed as a server on which said logical server has been deployed;

select a real server for deployment of said logical server based at least in part on said list of real servers on which said logical server has been deployed; and

deploy said logical server on said real server.

2. A system as recited in claim 1 further comprising said processor.

3. A system as recited in claim 1 further comprising said real server, said real server having at least one pre-deployment real-server network identity, said logical-server manager providing for said logical server to adopt said real-server network identity upon deployment to said real server.

4. A system as recited in claim 1 wherein the deploying includes causing said real server to adopt said logical-server network identity.

5. A system as recited in claim 4 wherein said real server has a hardwired network identity, said logical-server manager causing a proxy for said hardwired network identity to conform to said logical-server network identity.

6. A system as recited in claim 1 wherein said historical data also includes utilization data in the form of utilization-vs-time profiles, said selecting being based in part of said utilization-vs-time profiles.

7. A system as recited in claim 1 wherein said list identifies at least one real server on which said logical server is not currently deployed as a real server on which said logical server has been deployed.

8. A method comprising:

storing a logical server, while said logical server is undeployed, in association with a pre-deployment logical-server network identity and historical data for said logical server in a logical-server database stored on a computer system including hardware, said historical data including a list of real servers on which said logical server has been deployed, said list specifying at least one real server on which said logical server is not currently deployed as a server on which said logical server has been deployed;

selecting a first real server of said computer system as a deployment target for said logical server based at least in part on said list of real servers on which said logical server has been deployed; and

deploying said logical server to said first real server so that said real server assumes said logical-server network identity or said logical server assumes a network identity of said real server.

9. A method as recited in claim 8 further comprising creating said logical server based on a real server so that said logical server adopts a network identity of said real server, said network identity being stored in association with said logical server in said logical-server database.

10. A method as recited in claim 8 wherein said real server effectively adopts said logical-server network identity upon deployment of said logical server to said real server.

11. A method as recited in claim 10 wherein said real server effectively adopts said logical-server network identity in that said logical-server network identity is adopted as a proxy to a hardware network identity of said real server.

12. A method as recited in claim 8 wherein, before said deploying, said logical server is deployed and then released from a second real server different from said first real server.

13. A method as recited in claim 12 wherein one of said first and second real servers is a virtual-machine server and the other is a hardware server.

14. A method as recited in claim 8 further comprising finding workloads with utilizations that vary over time in a complementary fashion based at least in part on said utilization data.

15. A method as recited in claim 8 wherein said selecting is based at least in part on similarity to other hosts on said list.