|
Post by AMI_alvin on Feb 22, 2021 3:30:29 GMT
|
|
|
Post by mraineri on Feb 23, 2021 21:04:33 GMT
Yes, those URI patterns are accurate. The intent is the members of "NetworkPorts" within "NetworkInterface" will point to the NetworkPort instances underneath Chassis. So, your "NetworkPortCollection" underneath systems will look like this:
{ "@odata.id": "/redfish/v1/Systems/1/NetworkInterfaces/1/NetworkPorts", "@odata.type": "#NetworkPortCollection.NetworkPortCollection", "Name": "Network ports for interface 1", "Members": [ { "@odata.id": "/redfish/v1/Chassis/1/NetworkAdapters/Adapter1/NetworkPorts/1" }, { "@odata.id": "/redfish/v1/Chassis/1/NetworkAdapters/Adapter1/NetworkPorts/2" } ] }
The same is true for NetworkDeviceFunctions. The reason for this is to allow for complex types of designs where physical ports and functions can be shared by multiple systems. So, in order to prevent duplication of resources, the collections under a given system will ultimately point back to their physical representation under chassis. I think we can add some additional language in the descriptions in NetworkInterface to make this clear.
|
|
|
Post by AMI_alvin on Feb 25, 2021 3:25:26 GMT
Okay, this makes sense. And yes I think it will be helpful if you can add some descriptions for this purpose.
Thanks for your reply!
|
|