Bug 629329 - [RFE] Satellite recognition of System z LPAR/zVM
[RFE] Satellite recognition of System z LPAR/zVM
Product: Red Hat Satellite 5
Classification: Red Hat
Component: New Feature (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Todd Warner
Red Hat Satellite QA List
: FutureFeature
Depends On:
Blocks: 260381
  Show dependency treegraph
Reported: 2010-09-01 12:58 EDT by Brent Holden
Modified: 2015-09-11 10:57 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-09-11 10:57:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Example of /proc/sysinfo contents on a RHEL5 guest (2.05 KB, text/plain)
2010-09-01 12:58 EDT, Brent Holden
no flags Details

  None (edit)
Description Brent Holden 2010-09-01 12:58:43 EDT
Created attachment 442450 [details]
Example of /proc/sysinfo contents on a RHEL5 guest

Description of problem:
Satellite does not currently include any identification of System z specific information such as the LPAR or the z/VM instance name it is running under.  This can make tracking RHEL guests on System z difficult through the management interface.

Identification Support in RHEL:
Newer updates to RHEL5 include a proc interface (/proc/sysinfo) that contains some of this information.  Adding this to the hardware tab of a system in Satellite would be enormously helpful for auditing.

LPAR Number:          10
LPAR Characteristics: Shared 
LPAR Name:            L10     
LPAR Adjustment:      222
LPAR CPUs Total:      8
LPAR CPUs Configured: 4
LPAR CPUs Standby:    4
LPAR CPUs Reserved:   0
LPAR CPUs Dedicated:  0
LPAR CPUs Shared:     4

VM00 Name:            ZVM1    
VM00 Control Program: z/VM    6.1.0   
VM00 Adjustment:      1000
VM00 CPUs Total:      4
VM00 CPUs Configured: 4
VM00 CPUs Standby:    0
VM00 CPUs Reserved:   0

Note You need to log in before you can comment on or make changes to this bug.