Cisco's Cloud and Virtualization Group (CVG) Announces Rolling Updates for Prime Infrastructure

Available Languages

Download Options

PDF (149.0 KB)
View with Adobe Reader on a variety of devices
ePub (133.6 KB)
View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle) (154.2 KB)
View on Kindle device or Kindle app on multiple devices

Updated:February 4, 2016

Document ID:1454617285106828

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

CVG announces a new mechanism to deliver critical software fixes called "Rolling Updates." Rolling Updates mean bug fixes are available for customer use sooner than before. Rolling Updates consist of smaller batches of fixes to critical or frequently encountered software defects. Delivered every 3 weeks or so, they are updates to the current maintenance release that are available in between maintenance release publications. A maintenance release is known by the third position of a Prime Infrastructure Release version number, like this: 2.2.x.

The first rolling update is for Prime Infrastructure 2.2.2 (a maintenance release) and is delivered under the filename pi222_Update_03-4.ubf. Not to be confused with the upcoming 2.2.3 release (a separate maintenance release), this Rolling Update provides fixes sooner than waiting for the next maintenance release, while reducing the need for individual point patches for specific defects. Defects that would have required point patches in the past will make good candidates for being included in future Roling Updates.

A Rolling Update must only be installed on the maintenance release it was published for. For example, pi222_Update_03-4.ubf cannot be installed on 2.2 or 2.2.1; it must only be installed on 2.2.2.

The next Rolling Update for Prime Infrastructure 2.2.2 will be Update_04-x. Being cumulative, Update_04 will include the fixes from Update_03-4 and will not require those who did not install Update_03-4 to backtrack on through previous updates to receive the benefits of those fixes.

Availability of a Rolling Update is indicated by the red, round "Software Update is Available" badge in the upper right corner of the Prime Infrastructure GUI. On Prime Infrastructure's Software Update page and on Cisco.com, Rolling Updates will also appear in the Critical Fixes section. For details of a rolling update, please go to Cisco.com's Prime Infrastructure Software Download page, choose Prime Infrastructure Patches, and then hover over the filename to see the link for the Rolling Update's Read-me file. Rolling Updates are for a specific maintenance release; Rolling Updates cannot be installed on a different maintenance release than the specific one they were written for.