NEW FEATURE: Create data source for 'redfish_storage_volume'

[Rossnunez]

Right now redfish has a resource block known as, redfish_storage_volume. This works great for creating a virtual disk on an iDRAC.

However, there is no data source to collect information for current volumes that are mapped to an iDRAC. There are only data sources for, redfish_storage_controller and redfish_storage. None of these give me information on the virtual disk that I currently have for my server. I can confirm this based on the prompt listed for the redfish_storage_volume resource:

Odata ID of all available volumes on a storage controller can be fetched by running the following GET request on the iDRAC "/redfish/v1/Systems/System.Embedded.1/Storage//Volumes/" Eg. redfish/v1/Systems/System.Embedded.1/Storage/RAID.Integrated.1-1/Volumes/ The ID of any storage controller on the iDRAC, in turn, can be fetched using the "redfish_storage" data source

I think it would be better to have a data source to collect information for current volumes that are mapped to the drives on a iDRAC.
This would be extremely useful to check if my servers already have a volume, of a specific name. And decide whether I need to create a volume based on the output of this potential data source.

There's a use case where I want to check if a volume/virtual disk exists already on my iDRAC. If there was a data source for this, it would bridge that gap perfectly.

[gokul-srivathsan]

@Rossnunez thanks for raising this. Will do initial investigation and get back to you.

[Rossnunez]

Hi @gokul-srivathsan, any updates on this investigation?

[gokul-srivathsan]

@Rossnunez , it is already taken into our backlog grooming. Exact month of delivery will be notified soon here. cc: @anupamaloke