Based on ConditionalRequirements, WriteRequirement is verified for eth0(physical instance), usb0(Logical instance for Host interface communication between BMC and Host) in Manager ethernetinterface instance. In case of usb0(Logical instance for Host interface communication between BMC and Host) it's not required to support changing HostName, FQDN, IPv4Addresses#0, NameServers since it's going to be same as physical instance(eth0) in Manager resource.
Chances for some Physical instance also to restrict patch. Is it possible to skip WriteRequirement for logical interface by using use case or anyof comparison to make sure to change one instance in Manager ethernetinterface collection?
@mraineri @jautor Please add your inputs based on schema for skipping WriteRequirement for logical ethernetinterface instance like usb0 or we can accept patch on usb0, reflect the values in eth0, usb0
Hi, As per https://github.com/opencomputeproject/HWMgmt-OCP-Profiles/blob/master/HWMgmt/OCPBaselineHardwareManagement.v1_1_0.json
Based on ConditionalRequirements, WriteRequirement is verified for eth0(physical instance), usb0(Logical instance for Host interface communication between BMC and Host) in Manager ethernetinterface instance. In case of usb0(Logical instance for Host interface communication between BMC and Host) it's not required to support changing HostName, FQDN, IPv4Addresses#0, NameServers since it's going to be same as physical instance(eth0) in Manager resource. Chances for some Physical instance also to restrict patch. Is it possible to skip WriteRequirement for logical interface by using use case or anyof comparison to make sure to change one instance in Manager ethernetinterface collection?
@mraineri @jautor Please add your inputs based on schema for skipping WriteRequirement for logical ethernetinterface instance like usb0 or we can accept patch on usb0, reflect the values in eth0, usb0
Thanks, Mani