PROFILE MANAGEMENT SYSTEMS

• US 20110145414A1
• Filed: 12/14/2009
• Published: 06/16/2011
• Est. Priority Date: 12/14/2009
• Status: Active Grant

• Current Assignee: Valtrus Innovations Limited (f/k/a Dolya Holdco 9 Limited) (Key Patent Innovations Limited)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: DARLING, Jim, McMenomey, Jeffrey, Cripe, Daniel N.
• Granted Patent: US 8,688,838 B2
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: G06F 15/161 Computing infrastructure, e.g. computer clusters, blade chassis or hardware partitioning casings, cabinets, racks or drawers for data centers H05K5/00

Abstract

Systems and methods for profile management on a network are disclosed. A profile management system for first and second servers on the network may include a profile manager configured to manage a first profile that uniquely identifies the first server on the network; and an administrator configured to issue a command to the profile manager instructing the profile manager to migrate the first profile such that the first profile is no longer associated with the first server, and such that the first profile uniquely identifies the second server on the network, wherein at least one of the first and second servers is a conjoined server.

Claims

1. A profile management system for first and second servers on a network, comprising:

a profile manager configured to manage a first profile that uniquely identifies the first server on the network; and

an administrator configured to issue a command to the profile manager instructing the profile manager to migrate the first profile such that the first profile is no longer associated with the first server, and such that the first profile uniquely identifies the second server on the network, wherein at least one of the first and second servers is a conjoined server.

2. The system of claim 1, wherein the second server is a conjoined server that includes third and fourth servers, and the profile manager is further configured, when migrating the first profile, to assign a part of the first profile to the third server, and to assign another part of the first profile to the fourth server.

3. The system of claim 2, further comprising an enclosure manager configured to manage distribution of power to the first, third, and fourth servers, the profile manager further configured, when migrating the first profile, to instruct the enclosure manager to deny power-on requests from the third and fourth servers until after the profile manager assigns the part of the first profile to the third server and the another part of the first profile to the fourth server.

4. The system of claim 2, wherein the third server runs a single operating system instance for the conjoined server, and the part of the first profile includes an identifier associated with the conjoined server.

5. The system of claim 4, wherein the identifier includes a serial number of the conjoined server.

6. The system of claim 2, wherein each of the first, third, and fourth servers includes a plurality of ports, the part of the first profile including an identifier for each of two or more ports of the plurality of ports of the third server.

7. The system of claim 6, wherein the identifier includes a media access control address.

8. The system of claim 6, wherein the identifier includes a world wide name.

9. The system of claim 1, wherein the profile manager is further configured to associate a second profile different from the first profile to the first server when the first profile is migrated to the second server.

10. The system of claim 9, wherein the first server is a conjoined server that includes fifth and sixth servers, and the profile manager is further configured to associate a part of the second profile to the fifth server and another part of the second profile to the sixth server when the first profile is migrated to the second server.

11. The system of claim 1, wherein the profile manager is configured to migrate the first profile when the first server is disconnected from the network, and to associate a second profile different from the first profile when the first server is reconnected with the network.

12. The system of claim 11, wherein the first server is a conjoined server that includes fifth and sixth servers, wherein the profile manager is further configured to migrate the first profile when at least one of the fifth and sixth servers is disconnected from the network, and to associate a part of the second profile to the fifth server and another part of the second profile to the sixth server when the at least one of the fifth and sixth servers is reconnected with the network.

13. The system of claim 1, wherein the profile manager is further configured to wait until the first and second servers are powered off before migrating the first profile to the second server.

14. The system of claim 13, wherein the second server is a conjoined server that includes third and fourth servers, the profile manager being configured to associate a part of the first profile to the third server and another part of the first profile to the fourth server when the first, third, and fourth servers are powered off.

15. A network, comprising:

a first server associated with a first profile that uniquely identifies the first server on the network;

a second server coupled to the first server, wherein at least one of the first and second servers is a conjoined server;

a profile manager configured to manage the first profile; and

an administrator configured to issue a command to the profile manager instructing the profile manager to migrate the first profile such that the first profile is free from being associated with the first server, and such that the first profile uniquely identifies the second server on the network.

16. The network of claim 15, wherein the second server is a conjoined server that includes third and fourth servers, and the profile manager is further configured, when migrating the first profile, to assign a part of the first profile to the third server, and to assign another part of the first profile to the fourth server.

17. The system of claim 16, wherein the first server is a conjoined server that includes fifth and sixth servers, and the profile manager is further configured to associate a part of a second profile to the fifth server, and another part of the second profile to the sixth server when the first profile is migrated to the second server, the second profile being different from the first profile.

18. A method of profile management on a network, the network including a first server associated with a first profile that uniquely identifies the server on the network, and a second server coupled to the first server, at least one of the first and second servers being a conjoined server, comprising:

associating a second profile with the first server instead of the first profile, the second profile being different from the first profile;

associating the first profile with the second server.

19. The method of claim 18, where the second server is a conjoined server that includes third and fourth servers, and wherein associating the first profile with the second server includes associating a part of the first profile to the third server and another part of the first profile to the fourth server.

20. The method of claim 19, where the first server is a conjoined server that includes fifth and sixth servers, and wherein associating a second profile with the first server includes associating a part of the second profile to the fifth server and another part of the second profile to the sixth server.