Identifier management

1. A method for managing identifiers, comprising:

receiving, in an electronic identifier management system, a request for allocation of an identifier to a requesting party for a specified period of time;

accessing, by the identifier management system, an identifier database to determine existence of the identifier and verify availability of the identifier for the period of time; and

returning an affirmative response allocating the identifier to the requesting party for the period of time when the identifier is verified as available for the period of time.

2. The method of claim 1 , further comprising:

receiving, in the identifier management system, a request to extend identifier usage for a time period;

checking, by the identifier management system, the identifier database for reservations for the identifier that overlap the time period; and

returning a response to the requesting party.

3. The method of claim 2 , wherein the response is an affirmative response granting the request when no reservations overlap the time period and the response is a denial of the request when a reservation overlaps the time period.

4. The method of claim 1 , further comprising:

receiving, in the identifier management system a request to return an identifier; and

returning an identifier to storage for re-allocation.

5. The method of claim 4 , wherein the identifier comprises a product key, a license key, a domain name system (DNS) Host name, a virtual local area network (VLAN) tag, an IP address, a virtual machine name, a logical unit number (LUN) name, or a combination thereof.

6. The method of claim 1 , wherein the computing system is a cloud computing system.

7. An electronic system for identifier management, comprising:

a reservation manager to manage a request from a client for an identifier and to verify availability of the identifier;

a database to store lifecycle information of identifiers in a computing system; and

an identifier manager to manage the database,

wherein upon receiving the request from the client, the reservation manager accesses the database to verify availability of the identifier and returns to the client a response to the request based on the information received from the database.

8. The system of claim 7 , wherein the lifecycle information comprises creation, deletion, allocation, release, re-allocation, or a combination thereof of an identifier.

9. The system of claim 7 , wherein the identifier manager automatically updates the database when a change is made to an identifier.

10. The system of claim 7 , wherein the identifier is one of a domain name system (DNS) Host name, a virtual local area network (VLAN) tag, an IP address, a virtual machine name, a logical unit number (LUN) name, or a license key.

11. The system of claim 7 , wherein the reservation manager accesses the database to determine availability of the identifier.

12. The system of claim 7 , wherein the reservation manager returns an affirmative response granting the request when the identifier is available and the reservation manager returns a denial of the request when the identifier is not available.

13. The system of claim 12 , wherein when the reservation manager returns an affirmative response, the identifier manager updates the identifier database to reflect allocation of the identifier to a requesting party for a requested period of time.

14. The system of claim 7 , wherein the identifier management system manages identifiers in a cloud computing system.

15. A tangible, non-transitory, computer-readable storage medium, comprising code for identifier management that, when executed, causes a processor to:

receive a request for assignment of an identifier to a requesting party for a specified period of time;

access an identifier database to determine existence of the identifier and verify availability of the identifier for the period of time; and

return an affirmative response allocating the identifier to the requesting party for the period of time when the identifier is verified as available for the period of time.

16. The tangible, non-transitory, computer-readable storage medium of claim 15 , wherein the response is an affirmative response granting the request when the identifier is available for the period of time and the response is a denial of the request when the response is not available for the period of time.

17. The tangible, non-transitory, computer-readable storage medium of claim 15 , wherein the code further causes the processor to:

receive a request from the requesting party to extend identifier usage for a time period;

check the identifier database for reservations for the identifier that overlap the time period; and

return a response to the requesting party.

18. The tangible, non-transitory, computer-readable storage medium of claim 17 , wherein the response is an affirmative granting the request when no reservations overlap the period of time and the response is a denial of the request when a reservation overlaps the period of time.

19. The tangible, non-transitory, computer-readable storage medium of claim 15 , wherein the code further causes the processor to:

receive a request from the requesting party to return an identifier; and

return the identifier to storage.

20. The tangible, non-transitory, computer-readable storage medium of claim 19 , wherein the identifier is re-allocated in response to a new request for the identifier.