-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disk description now contains a StorageId and a RedfishURI #8937
Disk description now contains a StorageId and a RedfishURI #8937
Conversation
@@ -911,6 +913,7 @@ def get_disk_inventory(self, systems_uri): | |||
drive_result[property] = data[property] | |||
drive_results.append(drive_result) | |||
drives = {'Controller': controller_name, | |||
'StorageId': storage_id, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be worth adding "RedfishURI" for the Storage resource in addition to "StorageId" since there can be different storage subsystems across multiple systems with the same "Id" property. For example, these URIs are all unique Storage resources, but they all have "1" for the Id property...
/redfish/v1/Systems/RackMount1/Storage/1
/redfish/v1/Systems/RackMount2/Storage/1
/redfish/v1/Systems/RackMount3/Storage/1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mraineri , Thank you for your review, I understand, but i have a question:
My will here is to have a storage_subsystem_id
to give to the CreateVolume
command of community.general.redfish_config
.
In your case what storage_subsystem_id
would you provide to the command ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, specifically with CreateVolume, "resource_id" is already used to point to a specific system if needed. So, at least for your usage, it's not needed today; the combination of "resource_id" and "storage_subsystem_id" will guarantee uniqueness.
Okay, so this isn't necessary at this time based on the current interfaces.
shipit |
Backport to stable-9: 💚 backport PR created✅ Backport PR branch: Backported as #8942 🤖 @patchback |
* Disks controller is now uniquely identified by the controller ID * Fix typo `StorageID` to `StorageId` * Add changelog fragments --------- Co-authored-by: Pierre-yves FONTANIERE <[email protected]> (cherry picked from commit 84e0190)
…a StorageId and a RedfishURI (#8942) Disk description now contains a StorageId and a RedfishURI (#8937) * Disks controller is now uniquely identified by the controller ID * Fix typo `StorageID` to `StorageId` * Add changelog fragments --------- Co-authored-by: Pierre-yves FONTANIERE <[email protected]> (cherry picked from commit 84e0190) Co-authored-by: Pierre-yves Fontaniere <[email protected]>
…ollections#8937) * Disks controller is now uniquely identified by the controller ID * Fix typo `StorageID` to `StorageId` * Add changelog fragments --------- Co-authored-by: Pierre-yves FONTANIERE <[email protected]>
SUMMARY
Add a
StorageID
to the drives description and aRedfishURI
to each disk in the redfish_facts returned by the GetDiskInventory command.Fixes #8935
ISSUE TYPE
COMPONENT NAME
redfish_utils
ADDITIONAL INFORMATION
entries description before
And after