Managing a code load

US9329856B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9329856-B2
Application numberUS-201414219082-A
CountryUS
Kind codeB2
Filing dateMar 19, 2014
Priority dateMar 19, 2014
Publication dateMay 3, 2016
Grant dateMay 3, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A method and system for managing a code load for a storage system is disclosed. The method and system can include instantiating a code load. The code load can include a first update for a first component and a second update for a second component. The method and system can include monitoring the operational state of the first and second components in response to instantiating the code load. The method and system can also include determining to perform the first update in response to a triggering event. The method and system can also include performing the first update in response to determining to perform the first update.

First claim

Opening claim text (preview).

What is claimed is: 1. A computer implemented method for managing a code load for a storage system comprising: instantiating a code load, the code load including a first firmware update for a storage controller and a second firmware update for an interface adapter; monitoring, in response to instantiating the code load, a first operational state of the storage controller; maintaining a resource management database that includes information regarding the operational state of the storage controller, the interface adapter, and other devices in the storage system; wherein the resource management database contains a respective operational status, a respective serial number, a respective interface card identification number, and a respective power supply identification number for each respective device in the storage system; wherein the resource management database includes interfaces configured to allow system processes to register a callback function that will be invoked when a respective operational status in the resource management database changes; determining, in response to a triggering event, to perform the first firmware update, wherein the triggering event comprises a change in the operational state of the storage controller; performing, in response to determining to perform the first firmware update, the first firmware update; analyzing, within the same time frame as performing the first firmware update, an operational state of the interface adapter; writing, in response to the analyzing, a recommended action to take regarding the second firmware update for the interface adapter; and performing, in response to performing the first firmware update and writing the recommended action, the recommended action to take regarding the second firmware update for the interface adapter. 2. The method of claim 1 , wherein determining to perform the first firmware update further comprises: analyzing, by an event handler, the triggering event and the operational state of the storage controller to determine a recommended action; and writing, in a system file, the recommended action regarding the first firmware update. 3. The method of claim 2 , wherein the event handler is chosen from a plurality of event handlers based on the type of device and the type of the status change event. 4. The method of claim 2 , wherein performing the first firmware update further comprises reading the system file, and taking the recommended action. 5. A computer implemented method for managing a code load for a storage controller and an interface adapter of a storage system, the method comprising: instantiating a code load, the code load including a first firmware update for the storage controller and a second firmware update for the interface adapter; monitoring, in response to instantiating the code load, the operational state of the storage controller and the interface adapter; maintaining a resource management database that includes information regarding the operational state of the storage controller, the interface adapter, and other devices in the storage system; wherein the resource management database contains a respective operational status, a respective serial number, a respective interface card identification number, and a respective power supply identification number for each respective device in the storage system; wherein the resource management database includes interfaces configured to allow system processes to register a callback function that will be invoked when a respective operational status in the resource management database changes; determining, in response to a status change event associated with the operational state of the storage controller, to perform the first firmware update; and performing, within the same time frame as determining to perform the second firmware update, at least the first firmware update in response to determining to perform the first firmware update. 6. The method of claim 5 , wherein determining to perform the first firmware update further comprises: analyzing, by an event handler, of the status change event and the operational state of the storage controller, wherein the event handler can be selected based on the type of the status change event; and writing, in a system file, a recommended action to take regarding the first firmware update. 7. The method of claim 6 , further comprising: reading the system file, and taking the recommended action. 8. A computer program product for managing a code load of a storage system comprising a storage controller and an interface adapter, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, wherein the computer readable storage medium is not a transitory signal per se, the program instructions executable by a processor to cause the processor to perform a method comprising: instantiating a code load, the code load including a first firmware update for the storage controller; monitoring, in response to instantiating the code load, the operational state of the storage controller; maintaining a resource management database that includes information regarding the operational state of the storage controller, the interface adapter, and other devices in the storage system; wherein the resource management database contains a respective operational status, a respective serial number, a respective interface card identification number, and a respective power supply identification number for each respective device in the storage system; wherein the resource management database includes interfaces configured to allow system processes to register a callback function that will be invoked when a respective operational status in the resource management database changes; determining, in response to a triggering event associated with a change in the operational state of the storage controller, to perform the first firmware update; performing at least the first firmware update in response to determining to perform the first firmware update; analyzing, within the same time frame as performing the first firmware update, the operational state of the interface adapter; writing, in response to the analyzing, a recommended action to take regarding a second firmware update for the interface adapter; and performing, in response to performing the first firmware update and writing the recommended action, the recommended action to take regarding the second firmware update for the interface adapter. 9. The computer program product of claim 8 , wherein determining to perform the first firmware update further comprises; analyzing, using an event handler, the triggering event and the operational state of the storage controller; and writing, in a system file, a recommended action to take regarding the first firmware update. 10. The computer program product of claim 9 , wherein a different event handler can be used depending on the type of device and the type of status change event. 11. The computer program product of claim 9 , wherein performing the code-load further comprises reading the system file, and taking the recommended action.

Assignees

Inventors

Classifications

  • G06F8/665Primary

    Physics · mapped topic

  • G06F8/65Primary

    Updates (security arrangements therefor G06F21/57) · CPC title

  • Configuring for program initiating, e.g. using registry, configuration files · CPC title

  • Indexing; Data structures therefor; Storage structures · CPC title

  • G06F8/654Primary

    using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9329856B2 cover?
A method and system for managing a code load for a storage system is disclosed. The method and system can include instantiating a code load. The code load can include a first update for a first component and a second update for a second component. The method and system can include monitoring the operational state of the first and second components in response to instantiating the code load. The…
Who is the assignee on this patent?
IBM
What technology area does this patent fall under?
Primary CPC classification G06F8/665. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue May 03 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).