-
Notifications
You must be signed in to change notification settings - Fork 72
OpenNESS (20.09.01) interfaceservice config for the OpenVINO samples #33
Comments
Hi @kmaloor, The interfaceservice reads the MAC address of the interfaces on the edgenode from the system itself via the Golang net package. Looking at the OVS documentation for ovs-vsctl, it looks for the interface ID and MAC address of an interface as well when it is adding a new interface to an OVS bridge. Could you check if both interfaces on the edgenode have MAC addresses associated with them please? |
Hi @cjnolan Thank you for the response. It appears that the two NICs have valid
It appears that the framework queries the machine's network interfaces through here: Do you think something may be going wrong in this block? |
Hi @cjnolan Just a quick follow-up. By manually reading the uevent as over here:
It appears that the interfaceservice code wants to extract the PCI address corresponding As such, I'm wondering if the interfaceservice code needs to use an alternative
If the above output were placed into the |
Hi @kmaloor The cause of the failure with the interfaceservice is that the uevent is not being populated with the PCI addresses of the network interfaces. This appears to be due to the edgenode being deployed on a virtual machine with two virtual network interfaces. This configuration of the edgenode on a virtual machine was not tested with OpenNESS however the interfaceservice has been tested and validated with the edgenode on baremetal. |
Hi @cjnolan Thank you for your response. Yes, my Edge node has two (virtio) Ethernet controllers with distinct PCI addresses.
I am currently testing an OpenNESS edge deployment cluster on Google Cloud. I was wondering if there's any scope for altering the code such that it works |
Hi @kmaloor |
Hello,
I have built a network edge deployment (OpenNESS 20.09.01) cluster between two
QEMU/KVM machines, and have successfully tested producer/consumer apps.
The edge node (worker) is provisioned with two network interfaces (eth0 and eth1) with the idea
of dedicating one to management/control and the 2nd to data. The worker connects
to the master via eth0 and eth1 is on a different subnet.
To route traffic from an external machine to the OpenVINO apps, I am unable to bridge the
2nd (data) network interface on the Edge node to the OVS as suggested in the documentation.
Specifically, a listing of interfaces on the worker node returns two
kernel interfaces
(which is expected-eth0 and eth1 respectively for control and data), but the output
does not include the MAC addresses of the interfaces.
Further, attaching the interface fails as follows:
Is anything misconfigured on my Edge node? Please advise.
If it helps, below is a listing of all PCI devices on the Edge/worker node
which indicates the two Ethernet controllers.
Also, below is the status of all pods as seen from the master:
The text was updated successfully, but these errors were encountered: