On 2/2/24 16:38, Simon Horman wrote:
> Since the patch-set that included [1] there has been a policy of using
> the term member for bonds, LACP, and bundle contexts.  This is
> consistent with the more recently adopted policy of using the inclusive
> naming word list v1 [2, 3].
> 
> This patch addresses the name of the bond_active_member ovsdb column.
> This is used internally to allow the active member of a bond across OVS
> restart. And the effect of this patch is that when restarting OVS, if
> the instance before restart did not have this patch and the instance
> after does, or vice-versa, then active bond member selection will not be
> sticky across that restart. Otherwise, the existing behaviour is
> maintained.

Hi, Simon.  Unfortunately it is not possible to remove existing columns
from the database.  The new schema is not compatible and the existing
clients will fail to connect to the updated database.  You may see that
if you only update the schema, but not re-compile ovs-vswitchd:

2024-02-02T16:43:00.228Z|00027|ovsdb_cs|INFO|unix:sandbox/db.sock:
  received unexpected error response in DATA_MONITOR_REQUESTED state:
  {"error":{"details":"bond_active_slave is not a valid column name",
   "error":"syntax error",
   "syntax":"[\"bond_active_slave\", \"bond_downdelay\",\"bond_fake_iface\",
              \"bond_mode\",\"bond_updelay\",\"cvlans\",\"fake_bridge\",
              \"interfaces\",\"lacp\",\"mac\",\"name\",\"other_config\",
              \"protected\",\"qos\",\"rstp_statistics\",\"rstp_status\",
              \"statistics\",\"status\",\"tag\",\"trunks\",\"vlan_mode\"]"
  },"id":52,"result":null}


The column have to stay, similarly to other public interfaces.

What we can probably do is to add a new column and use/store values
from/into both, while removing the old one from the documentation.

Best regards, Ilya Maximets.
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to