Valence

Get storage recursively

Bug #1632488 reported by Nate Potter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Valence
Fix Committed
Medium
Nate Potter
Valence ocata-1

Bug Description

Right now the getStorage method in valence.ui.src.js.util assumes that logical drives will exist at /redfish/v1/Services/1/LogicalDrives. However, it's not a given that there will be one member of /redfish/v1/Services, or that its ID will be 1. We should get logical drives recursively from all Services.

Revision history for this message
Nate Potter (ntpttr) wrote :

Patch up for review here: https://review.openstack.org/#/c/385171/

Changed in openstack-valence:
importance: Undecided → Medium
status: New → In Progress
Lin Yang (lin-a-yang)
Changed in openstack-valence:
assignee: nobody → Nate Potter (ntpttr)
Nate Potter (ntpttr)
Changed in openstack-valence:
status: In Progress → Fix Committed
Revision history for this message
chesterkuo (chester-kuo) wrote :

Did "getStorage method" plan to show storage device for a compute system/composed node ??
if so , we should go to PODM NB (or Valence) API in "LocalDrives" and "RemoteDrive" property , the logical drive (/redfish/v1/Services/1/LogicalDrives), is a logical drive export by storage service (ex: iSCSI), it doesn't mean it will be a storage device used by a composed node.

Lin Yang (lin-a-yang)
Changed in openstack-valence:
milestone: none → ocata-1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.