We have a System where the ethernet interfaces are being shared between BMC & HOST through the NCSI switch. the HOST is reachable over the IP address but in our system we don't communicate to the HOST over ethernetInterface.
inband communication (BMC-HOST) happens over LPC.
Any external management client can communicate with the Host(KVM or any other Hypervisor) using the HOST IP address.
Have the two proposed solutions to model the Host's(kvm/hypervisor) ethernet interface as follows,
"InterfaceEnabled: false" - To indicate the BMC is restricted to access this host interface "ExternalAccessible: true" - To indicate this interface can be accessed externally from any other management client
Under /redfish/v1 we create another System resource; say "Hypervisor" and then configure the Ethernet interface under this System Resource. This will mean, at redfish root level there would be two Systems for the Server. 1) System which represents the whole server 2) System which represents only the Hypervisor(KVM/propreitary)
For Option 2) , the following additional two items also need to be defined -
1/ Relationship of Hypervisor being a part of the overall Server system We can do this by having a link property to connect the overall System to the Hypervisor Syestem which needs to be newly defined in the spec.
2/ We have a requirement to indicate the network protocols supported by the HOST(KVM/any Hypervisor). Currently the Computer System object does not have a property to set this.
We can include the "Network Protocol" property in the computer system resource which is of type "https://redfish.dmtf.org/schemas/v1/ManagerNetworkProtocol.v1_5_0.json"
PS: For the Option 1), the HostInterface resource has the Network Protocol property.
Please let me know your views on which option can be a more appropriate solution. Would like to hear if there are other alternatives too.