HP ProLiant SL270s HP ProLiant firmware management architecture - Page 5

Firmware bundles

Get HP ProLiant SL270s PDF manuals and user guides View all HP ProLiant SL270s manuals
Add to My Manuals
Save this manual to your list of manuals

Page 5 highlights

changes continue for new devices, bug fixes, microcode changes, and so on. We test these new changes against the existing Release Set (indicated by the yellow left arrow). Then we collect the new changes and put them into the next Release Set (indicated by the right green arrow). We validate the Release Set and then launch it to the web. We validate subsequent updates against the current Release Set. After this entire process completes, the cycle repeats. We also update the HP BladeSystem Compatibility Chart on the HP website at http://www.hp.com/go/bladesystemupdates to show when the updates will become available. The HP BladeSystem Compatibility Chart lists three versions of Release Sets-the current version and two previous versions. Each set contains a single version of the online firmware smart components. Figure 1. Lifecycle of a firmware Release Set Before we release an individual component out of cycle, we test it with the latest Release Set and the two previous versions to ensure quality. The Release Set reflects the component as a smart-component update. The HP BladeSystem Compatibility Chart reflects the out-of-cycle component as well. You can customize Release Sets and create your own firmware baselines, as long as the baselines use currently available components. HP provides support for the current and two previous Release Sets. For example, if we deliver three Release Sets (A, B, and C) over three calendar quarters, all of the three releases represent a supported configuration. Firmware bundles Although ProLiant DL, ML, and SL servers are not as complex as HP BladeSystem servers, we use similar firmware development and testing processes for all ProLiant servers. The HP firmware strategy requires similar standards and procedures to provide a smooth update process. 5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
changes continue for new devices, bug fixes, microcode changes, and so on. We test these new
changes against the existing Release Set (indicated by the yellow left arrow). Then we collect the new
changes and put them into the next Release Set (indicated by the right green arrow).
We validate the Release Set and then launch it to the web. We validate subsequent updates against
the current Release Set. After this entire process completes, the cycle repeats.
We also update the HP BladeSystem Compatibility Chart on the HP website at
to show when the updates will become available. The
HP BladeSystem Compatibility Chart lists three versions of Release Sets—the current version and two
previous versions. Each set contains a single version of the online firmware smart components.
Figure 1.
Lifecycle of a firmware Release Set
Before we release an individual component out of cycle, we test it with the latest Release Set and the
two previous versions to ensure quality. The Release Set reflects the component as a smart-component
update. The HP BladeSystem Compatibility Chart reflects the out-of-cycle component as well.
You can customize Release Sets and create your own firmware baselines, as long as the baselines use
currently available components. HP provides support for the current and two previous Release
Sets. For example, if we deliver three Release Sets (A, B, and C) over three calendar quarters, all of
the three releases represent a supported configuration.
Firmware bundles
Although ProLiant DL, ML, and SL servers are not as complex as HP BladeSystem servers, we use
similar firmware development and testing processes for all ProLiant servers. The HP firmware strategy
requires similar standards and procedures to provide a smooth update process.
5