I think it should go into Interface.
The field should be mutable, because its value is not known when
ovs-vsctl (or another OVSDB client) adds the Interface record;
instead, ovs-vswitchd fills it in later. Otherwise your plan sounds
right.
Other interface status columns, such as 'link_state' and
Want to make sure I get off on the right foot... should the read-only ifindex
field go
into "Port" or "Interface" ? It seems like ovsrec_interface is the one with
the pointer to netdev.
So I just need to:
1. change the schema to add ifindex as a new field (with mutable: false),
2. update the
On May 28, 2013, at 5:01 PM, Ben Pfaff wrote:
> On Tue, May 28, 2013 at 12:17:39PM -0700, Neil Mckee wrote:
>> It would be helpful if ovs-vsctl(1) had a way to write out the
>> netdev ifIndex numbers, where applicable, of the bridge ports. This
>> would help to harmonize integration with SNMP,
On Tue, May 28, 2013 at 12:17:39PM -0700, Neil Mckee wrote:
> It would be helpful if ovs-vsctl(1) had a way to write out the
> netdev ifIndex numbers, where applicable, of the bridge ports. This
> would help to harmonize integration with SNMP, sFlow, LLDP and more.
>
> Could it be an extra column
Hello All,
It would be helpful if ovs-vsctl(1) had a way to write out the netdev ifIndex
numbers, where applicable, of the bridge ports.This would help to
harmonize integration with SNMP, sFlow, LLDP and more.
Could it be an extra column in the output from "ovs-vsctl list Port" ? Or a
k
