Post by fanlufan on May 8, 2020 15:28:34 GMT
Hi,
We wanted to get your advice on a couple use cases. We have an application (UFM) that exposes an RF/SF interface. UFM is customer facing and manages/abstracts a number of other EBOF and eSSD systems. We are having a problem determining how to model the following use cases:
According to Redfish, VLANs, Switches, and Ports are now placed like this:
ServiceRoot->Systems->EthernetInterfaces->VLANs
ServiceRoot->Fabrics->Switches->ports
1) External switches
UFM Manages external switches residing over fabric between itself and the EBOFs. We want to create vlans on the switch ports. There could be multiple switches between UFM and the EBOFs. When we look at the Redfish models, we can only see vlans sitting under Systems->EthInterfaces->VLANs. We may not be thinking about this from the right perspective, but it feels like we should be able to create vlans on switch ports without having those VLANs be a subordinate object of EthInterfaces. With the model though, it doesn't seem possible since switch ports only have navigation links to existing vlans.
2) Internal switches
EBOFs can contain internal switches for internal eSSDs. If the vlan is attached to the eSSDs EthInterfaces (eSSDs are Systems in our current representation), if we need to replace that eSSD, then that EthInterface goes away and we lose that vlan. It feels like we need to have VLANs as a subordinate of switch->ports.
Can you provide some insight into the above scenarios? Thanks!
We wanted to get your advice on a couple use cases. We have an application (UFM) that exposes an RF/SF interface. UFM is customer facing and manages/abstracts a number of other EBOF and eSSD systems. We are having a problem determining how to model the following use cases:
According to Redfish, VLANs, Switches, and Ports are now placed like this:
ServiceRoot->Systems->EthernetInterfaces->VLANs
ServiceRoot->Fabrics->Switches->ports
1) External switches
UFM Manages external switches residing over fabric between itself and the EBOFs. We want to create vlans on the switch ports. There could be multiple switches between UFM and the EBOFs. When we look at the Redfish models, we can only see vlans sitting under Systems->EthInterfaces->VLANs. We may not be thinking about this from the right perspective, but it feels like we should be able to create vlans on switch ports without having those VLANs be a subordinate object of EthInterfaces. With the model though, it doesn't seem possible since switch ports only have navigation links to existing vlans.
2) Internal switches
EBOFs can contain internal switches for internal eSSDs. If the vlan is attached to the eSSDs EthInterfaces (eSSDs are Systems in our current representation), if we need to replace that eSSD, then that EthInterface goes away and we lose that vlan. It feels like we need to have VLANs as a subordinate of switch->ports.
Can you provide some insight into the above scenarios? Thanks!
