Red Hat Bugzilla – Bug 463329
[LTC 6.0 FEAT] 201660:Update SBLIM data gatherer to 2.1.6 or later
Last modified: 2010-10-05 06:03:01 EDT
Emily J. Ratliff <firstname.lastname@example.org> - 2008-09-16 18:28 EDT
1. Feature Overview:
Feature Id: 
a. Name of Feature: Update SBLIM data gatherer to 2.1.6 or later
b. Feature Description
Update the version of sblim-gather, including sblim-gather-develop, sblim-gather-provider and
sblim-gather-test, to version 2.1.6 or later.
2. Feature Details:
Sponsor: LTC Systems Mgt
Arch Specificity: Purely Common Code
Delivery Mechanism: Direct from community
Category: Systems management
Request Type: Package - Update Version
d. Upstream Acceptance: Accepted
Sponsor Priority 2
f. Severity: Medium
IBM Confidential: no
Code Contribution: IBM code
g. Component Version Target: The sblim-gather package v2.1.6 is already available via SourceForge
3. Business Case
IBM Director will likely be converging on the SBLIM Data Gatherer to provide the base DMTF Metrics
Profile complaint runtime metric gathering instrumentation. We have been using it for some time for
Director Xen, zVM is planning on using for Director 6.1, and when we properly converge on some
common VSM metrics post-6.1 having some cross-platform infrastructure established and available will
be even more important.
4. Primary contact at Red Hat:
5. Primary contacts at Partner:
Project Management Contact:
Sarah Wright, email@example.com, 503-578-5145
Narasimha Sharoff, firstname.lastname@example.org
Gareth Bestor, email@example.com
Jeffrey Heroux, firstname.lastname@example.org
Version 2.1.8 is now available and GA'ed on the site listed above. Please use that version instead of the older version listed.
Version 2.1.9 is now available. Please use
that version instead of the older version listed.
Fixed in 'sblim-gather-2.1.9-1.el6'. 'sblim-gather-2.1.9-1.el6' included in compose 'RHEL6.0-20091216.nightly'.
Moving to ON_QA.
This bug is a duplicate of bug #598690 or more precisely they cover the same request twice. The requested version update here is 2.1.6 or later vs. 2.2.1 on the other bug.
*** This bug has been marked as a duplicate of bug 598690 ***