Updating elements in data storage facility using predefined state machine over extended time period

US9600265B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9600265-B2
Application numberUS-201514623924-A
CountryUS
Kind codeB2
Filing dateFeb 17, 2015
Priority dateApr 29, 2010
Publication dateMar 21, 2017
Grant dateMar 21, 2017

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 sequence for distributing at least one of a plurality of code packages to the at least one facility according to different states of a fixed state machine is set. The at least one of the plurality of code packages is maintained in at least one staging area in a valid, dormant mode while the fixed state machine is stopped. Pursuant to a resumption of the fixed state machine at a subsequent time, a current code package is swapped with the at least one of the plurality of code packages in the at least one staging area to activate the at least one of the plurality of code packages.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for updating at least one facility in a computing storage environment by a processor device, comprising: setting a sequence for distributing at least one of a plurality of code packages to the at least one facility according to different states of a fixed state machine; detecting a change in the fixed state machine; determining whether the fixed state machine change is an accidental state change resulting in a modification of the configuration of an updateable element; if the fixed state machine change is not an accidental state change, determining whether the fixed state machine change results in a modification of the configuration of an updateable element; if the fixed state machine change results in a modification of the configuration of the updateable element, then analyzing and synchronizing the modification to bring the fixed state machine to a valid state; and if the fixed state machine change does not result in a modification, maintaining the fixed state machine in the valid state; if the fixed state machine change is an accidental state change, notifying support personnel for repair or replacement of a failing part causing the accidental state change; if the repair results in a modification of the configuration of the updateable element of the at least one of the plurality of code packages maintained in at least one staging area, analyzing and synchronizing the modification to bring the fixed state machine to the valid state; if the repair does not result in a modification of the configuration of the updateable element of the at least one of the plurality of code packages maintained in the at least one staging area, placing the fixed state machine in the valid state; and pursuant to a resumption of the fixed state machine at a subsequent time after the fixed state machine is brought to the valid state, swapping a current code package with the at least one of the plurality of code packages in the at least one staging area to activate the at least one of the plurality of code packages. 2. The method of claim 1 , further including identifying the at least one facility as an update candidate. 3. The method of claim 1 , further including periodically performing a verification procedure on the at least one facility. 4. The method of claim 3 , further including, pursuant to periodically performing the verification procedure on the at least one facility, detecting a modification to the at least one facility. 5. The method of claim 4 , wherein the detecting the modification to the at least one facility further includes at least one of detecting a hardware addition, detecting a license activation, and detecting a logical configuration change. 6. The method of claim 4 , further including, pursuant to the detecting the modification to the at least one facility, identifying at least one difference between the at least one of the plurality of code packages and a current code level in the at least one facility. 7. The method of claim 6 , further including, pursuant to the identifying at least one difference between the at least one of the plurality of code packages and the current code level in the at least one facility, synchronizing the at least one of the plurality of code packages in the at least one staging area and the current code level in the at least one facility. 8. The method of claim 7 , further including, subsequent to synchronizing the at least one of the plurality of code packages in the at least one staging area and the current code level in the at least one facility, performing the resumption of the fixed state machine. 9. A system for updating at least one facility in a computing storage environment, comprising: at least one processor device, operable in the computing storage environment, wherein the at least one processor device is adapted for: setting a sequence for distributing at least one of a plurality of code packages to the at least one facility according to different states of a fixed state machine, detecting a change in the fixed state machine; determining whether the fixed state machine change is an accidental state change resulting in a modification of the configuration of an updateable element; if the fixed state machine change is not an accidental state change, determining whether the fixed state machine change results in a modification of the configuration of an updateable element; if the fixed state machine change results in a modification of the configuration of the updateable element, then analyzing and synchronizing the modification to bring the fixed state machine to a valid state; and if the fixed state machine change does not result in a modification, maintaining the fixed state machine in the valid state; if the fixed state machine change is an accidental state change, notifying support personnel for repair or replacement of a failing part causing the accidental state change; if the repair results in a modification of the configuration of the updateable element of the at least one of the plurality of code packages maintained in at least one staging area, analyzing and synchronizing the modification to bring the fixed state machine to the valid state; if the repair does not result in a modification of the configuration of the updateable element of the at least one of the plurality of code packages maintained in the at least one staging area, placing the fixed state machine in the valid state; and pursuant to a resumption of the fixed state machine at a subsequent time after the fixed state machine is brought to the valid state, swapping a current code package with the at least one of the plurality of code packages in the at least one staging area to activate the at least one of the plurality of code packages. 10. The system of claim 9 , wherein the at least one processor device is further adapted for identifying the at least one facility as an update candidate. 11. The system of claim 9 , wherein the at least one processor device is further adapted for periodically performing a verification procedure on the at least one facility. 12. The system of claim 9 , wherein the at least one processor device is further adapted for, pursuant to the detecting a change in the fixed state machine, performing at least one of detecting a hardware addition, detecting a license activation, and detecting a logical configuration change. 13. The system of claim 12 , wherein the at least one processor device is further adapted for, pursuant to the detecting a change in the fixed state machine, identifying at least one difference between the at least one of the plurality of code packages and a current code level in the at least one facility. 14. The system of claim 13 , wherein the at least one processor device is further adapted for, pursuant to the identifying at least one difference between the at least one of the plurality of code packages and the current code level in the at least one facility, synchronizing the at least one of the plurality of code packages in the at least one staging area and the current code level in the at least one facility. 15. The system of claim 14 , wherein the at least one processor device is further adapted for, subsequent to synchronizing the at least one of the plurality of code packages in the at least one staging area and the current code level in the at least one facility, performing the resumption of the fixed state machine. 16. The system of claim 9 , wherein the at least one facility is a computing storage facility, and the at least one processor device is operable as at least a portion of a serv

Assignees

Inventors

Classifications

  • G06F8/65Primary

    Updates (security arrangements therefor G06F21/57) · 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 US9600265B2 cover?
A sequence for distributing at least one of a plurality of code packages to the at least one facility according to different states of a fixed state machine is set. The at least one of the plurality of code packages is maintained in at least one staging area in a valid, dormant mode while the fixed state machine is stopped. Pursuant to a resumption of the fixed state machine at a subsequent tim…
Who is the assignee on this patent?
IBM
What technology area does this patent fall under?
Primary CPC classification G06F8/65. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Mar 21 2017 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 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).