lenovo / lenovo/python-redfish-lenovo
Volume creation does not support passing specific disks in the controller
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 106
- Forks
- 57
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 1
Description
So far I see the request to the Redfish API does not send speicific physical disks
https://github.com/lenovo/python-redfish-lenovo/blob/master/examples/lenovo_create_raid_volume.py#L180-L184
For me it fails with code 500
I got 2x SSD 1TB and 8x8TB HDD on one conttroller and wants to create RAID1
Does the firmware support passing the actual drives ? So I could modify the lenovo-create_raid_volume.py script to pass list of drives in the request body ?
Similarly to iDRAC ? like https://jonamiki.com/2019/04/14/example-redfish-rest-calls-create-raid-volume/
Or it will work only when the list of drives matches the RAIDType ?
By guessing I tried passing drives or disks by guessing but none of them work
Url '/redfish/v1/Systems/1/Storage/RAID_Slot7/Volumes' response Error code 500
error_message: The property Drives is not in the list of valid properties for the resource
Also would be cool if the REST API guide was updated accordingly
also would like to know which firmware version supports it ?
I got mine SR650 updated to the newest firmware on all components
Mine BMC Version: 8.80 CDI3A2Q (09/22/2022)
https://sysmgt.lenovofiles.com/help/topic/com.lenovo.systems.management.xcc.restapi.doc/xcc_restapi_book.pdf
Originally posted by @mastier in https://github.com/lenovo/python-redfish-lenovo/issues/2#issuecomment-1380284238
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with examples/lenovo_create_raid_volume.py around lines 180-184 and reproduce the request against the Redfish endpoint described in the issue. Read the linked XCC REST API guide for the Volumes resource and Drives property, including firmware details. Done means the supported request shape and firmware behavior are established, with the script or documentation updated accordingly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100