Method and apparatus for negotiating revised service level agreements

• US 7,793,058 B2
• Filed: 04/19/2005
• Issued: 09/07/2010
• Est. Priority Date: 04/19/2005
• Status: Expired due to Fees

• Current Assignee: Kyndryl Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Boss, Gregory Jensen, Waters, Timothy Moffett, Hamilton, Rick Allen II, Dawson, Christopher James
• Primary Examiner(s): Chery; Mardochee
• Application Number:
  US11/109,086
• Publication Number:
  US 20060236062A1
• Time in Patent Office: 1,967 Days
• Field of Search: 711/170
• US Class Current: 711/156
• CPC Class Codes: G06F 3/0605 by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0653 Monitoring storage devices or systems
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

An application'"'"'s storage availability is adjusted by noting a storage event occurrence. An occurrence that necessitates a requirements change triggers negotiation, wherein a series of negotiation stages are presented to a storage provider server. For each storage provider response to a transmitted negotiation stage, a determination is made to see if the response is better than the proposal described in the negotiation stage. If so, the application commits the storage changes.

Claims

1. A method for setting a level of service for storage comprising the steps of:

detecting an occurrence of a scheduled storage event, wherein detecting an occurrence of a scheduled storage event comprises;

monitoring a performance level that correlates with data storage requirement fluctuations; and

determining that the performance level is beyond a threshold, wherein the occurrence of a scheduled storage event is detected when the performance level is determined to be beyond the threshold;

in response to detecting the occurrence of the scheduled storage event, determining whether a requirement change occurred;

in response to determining that a requirement change occurred, looking up a first unused negotiation stage from among a plurality of negotiation stages stored in a metadata structure, wherein the first unused negotiation stage is looked up on the basis of at least one parameter comprising at least one of data throughput rate, time to recover from failure, and presence of backup;

requesting an online storage service based on the first looked up unused negotiation stage to form a first request;

receiving a first service provider response to the first request;

determining whether the first service provider response is acceptable;

in response to determining that the first service provider response is acceptable, committing a storage change based on the first service provider response;

in response to determining that the first service provider response is not acceptable, determining whether a second unused negotiation stage exists;

in response to the determining that a second unused negotiation stage exists, looking up the second unused negotiation stage from among the plurality of negotiation stages stored in the metadata structure, wherein the second unused negotiation stage is looked up on the basis of at least one parameter comprising at least one of data throughput rate, time to recover from failure, and presence of backup;

requesting the online storage service based on the second unused negotiation stage to form a second request;

receiving a second service provider response to the second request;

determining whether the second service provider response is acceptable; and

in response to determining that the second service provider response is acceptable, committing a storage change based on the second service provider response, wherein committing the storage change based on the first or second service provider response comprises establishing a reference table of a network location of a storage that is to be used during a time interval.

2. A method for setting a level of service for storage comprising the steps of:

detecting a storage event for a running application;

determining whether a requirement change occurred in response to detecting a performance level of the running application being beyond a threshold;

looking up an unused negotiation stage from among at least one negotiation stage stored in a metadata structure in response to determining that a requirement change occurred, wherein the unused negotiation stage is looked up on the basis of at least one parameter comprising at least one of data throughput rate, time to recover from failure, and presence of backup;

requesting a service based on the unused negotiation stage;

receiving a service provider response;

determining whether the service provider response is acceptable; and

committing a storage change for the running application based on the service provider response.

3. The method for setting a level of service for storage of claim 2, wherein the step of detecting comprises the steps of:

monitoring a performance level; and

detecting whether the performance level is beyond a threshold.

4. The method for setting a level of service for storage of claim 2, wherein the step of detecting comprises the step of:

detecting a scheduled event.

5. The method for setting a level of service for storage of claim 2, wherein the step of requesting a service based on the unused negotiation stage comprises:

requesting a service based on the unused negotiation stage, wherein the unused negotiation stage has a token accounting.

6. The method of claim 2 following the step of determining whether the service provider response is acceptable, comprising the steps:

determining whether a second unused negotiation stage exists in response to a determining that the service provider response is not acceptable;

looking up the second unused negotiation stage from among the at least one negotiation stage stored in the metadata structure in response to determining that the second unused negotiation stage exists;

requesting a service based on the second unused negotiation stage;

receiving a second service provider response; and

determining whether the second service provider response is acceptable.

7. The method for setting a level of service for storage of claim 6, wherein the step of detecting comprises the steps of:

monitoring a performance level; and

detecting whether the performance level is beyond a threshold.

8. The method for setting a level of service for storage of claim 6, wherein the step of detecting comprises the step of:

detecting a scheduled event.

9. A storage consumer for setting a level of service for storage comprising:

a means for detecting a storage event for a running application;

a means for determining whether a requirement change occurred in response to detecting a performance level of the running application being beyond a threshold;

a means for looking up an unused negotiation stage from among at least one negotiation stage stored in a metadata structure in response to determining that a requirement change occurred, wherein the unused negotiation stage is looked up on the basis of at least one parameter comprising at least one of data throughput rate, time to recover from failure, and presence of backup;

a means for requesting a service based on the unused negotiation stage;

a means for receiving a service provider response;

a means for determining whether the service provider response is acceptable; and

a means for committing a storage change for the running application based on the service provider response.

10. The storage consumer for setting a level of service for storage of claim 9, wherein the means for detecting comprises:

a means for monitoring a performance level; and

a means for detecting whether the performance level is beyond a threshold.

11. The storage consumer for setting a level of service for storage of claim 9, wherein the means for detecting comprises:

a means for detecting a scheduled event.

12. The storage consumer for setting a level of service for storage of claim 9, wherein the means for requesting a service based on the unused negotiation stage comprises:

a means for requesting a service based on the unused negotiation stage, wherein the unused negotiation stage has a token accounting.

13. The storage consumer of claim 9, further comprising:

a means for determining whether a second unused negotiation stage exists in response to a determining that the service provider response is not acceptable;

a means for looking up the second unused negotiation stage from among the at least one negotiation stage stored in the metadata structure in response to determining that the second unused negotiation stage exists;

a means for requesting a service based on the second unused negotiation stage;

a means for receiving a second service provider response; and

a means for determining whether the second service provider response is acceptable.

14. The storage consumer for setting a level of service for storage of claim 13, wherein the means for detecting comprises:

a means for monitoring a performance level; and

a means for detecting whether the performance level is beyond a threshold.

15. A data processing system comprising:

a memory containing computer usable program code for setting a level of service for storage;

a bus system connecting the memory to a processor; and

a processor, wherein the processor executes the computer usable program code;

to detect a storage event for a running application;

to determine whether a requirement change occurred in response to detecting a performance level of the running application being beyond a threshold;

to look up an unused negotiation stage from among at least one negotiation stage stored in a metadata structure in response to determining that a requirement change occurred, wherein the unused negotiation stage is looked up on the basis of at least one parameter comprising at least one of data throughput rate, time to recover from failure, and presence of backup;

to request a service based on the unused negotiation stage;

to receive a service provider response;

to determine whether the service provider response is acceptable; and

to commit a storage change for the running application based on the service provider response.

16. The data processing system of claim 15, wherein the processor executing the computer usable program code to detect a storage event further comprises executing the computer usable program code:

to monitor a performance level; and

to detect whether the performance level is beyond a threshold.

17. The data processing system of claim 15, wherein the processor executing the computer usable program code to detect a storage event further comprises executing the computer usable program code:

to detect a scheduled event.

18. The data processing system of claim 15, wherein the processor executing the computer usable program code to request a service based on the unused negotiation stage further comprises executing the computer usable program code:

to request a service based on the unused negotiation stage, wherein the unused negotiation stage has a token accounting.

19. The data processing system of claim 15, wherein following the processor executing the computer usable program code to determine whether the storage provider response is acceptable, the processor further executing the computer usable program code:

to determine whether a second unused negotiation stage exists in response to a determining that the service provider response is not acceptable;

to look up the second unused negotiation stage from among the at least one negotiation stage stored in the metadata structure in response to the determining that the second unused negotiation stage exists;

to request a service based on the second unused negotiation stage;

to receive a second service provider response; and

to determine whether the second service provider response is acceptable.

20. The data processing system of claim 19, wherein the processor executing the computer usable program code to detect a storage event further comprises executing the computer usable program code:

to monitor a performance level; and

to detect whether the performance level is beyond a threshold.