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 1Red 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.
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 ***
(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