You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But as you can see, IDs are not unique... I've never seen that on DELL servers, but HPe did. :(
I would like to be able to specify an ID as a variable to my playbook. And in my use case, ID must be unique on a single server but can be the same on multiple servers of the same type. So MACAddress can't be used.
I thought that keeping the @odata.id in the resource would be a good idea ?
Code of Conduct
I agree to follow the Ansible Code of Conduct
The text was updated successfully, but these errors were encountered:
Yeah, I can see that coming up in other implementations too. Id is only guaranteed to be unique for a given resource collection (and not across the entire service). Having the full URI would be useful. I'd like to avoid calling it @odata.id in the output payload if possible.
@mraineri I started to write something for disks resources which is named RedfishURI (see #8937).
I'm thinking of implementing the same thing for network interfaces. Is it OK for you ?
Summary
I have a problem to identify network devices on HPe servers.
I would like to have a specific ID for each redfish resource.
Perhaps one should keep @odata.id in final resources.
Issue Type
Feature Idea
Component Name
redfish_info
Additional Information
With the following playbook:
We can have description of each Ethernet interface.
But as you can see, IDs are not unique... I've never seen that on DELL servers, but HPe did. :(
I would like to be able to specify an ID as a variable to my playbook. And in my use case, ID must be unique on a single server but can be the same on multiple servers of the same type. So MACAddress can't be used.
I thought that keeping the
@odata.id
in the resource would be a good idea ?Code of Conduct
The text was updated successfully, but these errors were encountered: