Bug 1466880

Summary: [Intel OSP13] Identify and list Health/State of RSD resources
Product: Red Hat OpenStack Reporter: Krish Raghuram <krishnan.raghuram>
Component: openstack-ironicAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: mlammon
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13.0 (Queens)CC: jdonohue, krishnan.raghuram, lin.a.yang, mburns, nathaniel.potter, paul.von.behren, priyank.durugkar, racedoro, rhel-osp-director-maint, robert.h.armstrong, srevivo
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-20 10:15:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1414581, 1419948, 1422243    

Description Krish Raghuram 2017-06-30 15:56:11 UTC
Description of feature:
Each RSD asset has different Health (configuration error, correctible or uncorrectable error, Temperature trip) and State information (presence detected, removed, power state and so on).
The appropriate RedHat OSP modules should be able to identify and list the above Health/State types for every RSD resource (Server, Storage, Compute, Memory, FPGAs) when needed

Version-Release number of selected component (if applicable):
OpenStack Ironic version (or others potentially) in OpenStack Queens release

2. Business Justification:
  a) Why is this feature needed?
     RSD is a new architecture that realizes an agile infrastructure where the hardware resources can be pooled according to application needs. It also enables a more easily scaled infrastructure, so CPU, memory, network and storage resources can be added as needed, without the need to do complete replacements of nodes
  b) What hardware does this enable?
   New platforms based on RSD architecture
  c) Is this hardware on-board in a system (eg, LOM) or an add-on card? 
  RSD nodes are disaggregated (CPU, memory, storage, accelerators etc.)
  d) Business impact? N/A
  
  e) Other business drivers: N/A

3. Primary contact at Partner, email, phone (chat)
   Priyank Durugkar - priyank.durugkar

4. Expected results:
- DC admin lists available RSD nodes 
- Admin lists the health/state of each node and resources within each node
- Admin also lists available RSD resources and health/state of each

Additional info:

Comment 1 Red Hat Bugzilla Rules Engine 2017-06-30 15:56:18 UTC
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.

Comment 2 Krish Raghuram 2017-09-21 14:52:02 UTC
This work is automatically covered in the upstream work being done for BZ# 1466873 and 1466874, which are high priority for Queens

Comment 3 Ramon Acedo 2017-10-20 10:15:42 UTC
Hi Krish, if pythonrsd-client is capable of identifying and listing Health/State of RSD resources, I suggest we mark this BZ as a duplicate of BZ#1466874.

*** This bug has been marked as a duplicate of bug 1466874 ***

Comment 4 Krish Raghuram 2017-10-20 16:40:33 UTC
(In reply to Ramon Acedo from comment #3)
> Hi Krish, if pythonrsd-client is capable of identifying and listing
> Health/State of RSD resources, I suggest we mark this BZ as a duplicate of
> BZ#1466874.
> 
> *** This bug has been marked as a duplicate of bug 1466874 ***

Agreed