On Mon, Mar 25, 2019 at 12:48:34PM +0100, Eelco Chaudron wrote: > > > On 22 Mar 2019, at 13:58, Ilya Maximets wrote: > > > Virtual ports like 'patch' ports that almost fully implemented on > > 'ofproto' layer could have internal to 'ofproto' statuses that > > could not be retrieved from 'netdev' or other layers. For example, > > in current implementation there is no way to get the patch port > > pairing status (i.e. if it has usable peer?). > > > > New 'ofproto-provider' API function 'vport_get_status' introduced to > > cover this gap. It allowes 'bridge' layer to retrive current status > > of ofproto virtual ports and propagate it to DB. > > For now we're only interested in pairing errors of 'patch' ports. > > That are propagated to the 'error' column of the 'Interface' table. > > > > Ex.: > > > > $ ovs-vsctl show > > ... > > Bridge "br1" > > ... > > Port "patch1" > > Interface "patch1" > > type: patch > > options: {peer="patch0"} > > error: "No usable peer 'patch0' exists in 'system' datapath." > > > > Bridge "br0" > > datapath_type: netdev > > ... > > Port "patch0" > > Interface "patch0" > > type: patch > > options: {peer="patch1"} > > error: "No usable peer 'patch1' exists in 'netdev' datapath." > > > > Signed-off-by: Ilya Maximets <i.maxim...@samsung.com> > > Thanks for taking care of this Ilya! > > Acked-by: Eelco Chaudron <echau...@redhat.com>
Thanks, Ilya (and Eelco). I applied this to master. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev