[ovs-git] [openvswitch/ovs] c557ca: ovs-vsctl: Create AutoAttach records on demand, fo...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/openvswitch/ovs
  Commit: c557ca04169bbe0af253bd910a5328ac3eee98e7
      https://github.com/openvswitch/ovs/commit/c557ca04169bbe0af253bd910a5328ac3eee98e7
  Author: Ben Pfaff <blp at nicira.com>
  Date:   2015-03-20 (Fri, 20 Mar 2015)

  Changed paths:
    M utilities/ovs-vsctl.c

  Log Message:
  -----------
  ovs-vsctl: Create AutoAttach records on demand, for backward compatibility.

The AutoAttach table is new in OVS 2.3.90, but ovs-vsctl was creating a
record in the table unconditionally whenever it created a new bridge.
This caused a gratuitous incompatibility with older databases, which can
be a problem during upgrade.  This commit switches to creating the
AutoAttaach record for a bridge lazily, only when the first mapping is
created for the bridge.

VMware-BZ: #1413562
CC: Dennis Flynn <drflynn at avaya.com>
Reported-by: Alex Wang <alexw at nicira.com>
Signed-off-by: Ben Pfaff <blp at nicira.com>
Acked-by: Justin Pettit <jpettit at nicira.com>


  Commit: d6f115f56a88d66f3f6b5f657a45ce6e37099702
      https://github.com/openvswitch/ovs/commit/d6f115f56a88d66f3f6b5f657a45ce6e37099702
  Author: Ben Pfaff <blp at nicira.com>
  Date:   2015-03-20 (Fri, 20 Mar 2015)

  Changed paths:
    M utilities/ovs-vsctl.c

  Log Message:
  -----------
  ovs-vsctl: Only monitor AutoAttach columns when useful.

Otherwise this creates a gratuitous incompatibility with older databases,
which can be a problem in upgrade situations.

VMware-BZ: #1413562
Reported-by: Alex Wang <alexw at nicira.com>
Signed-off-by: Ben Pfaff <blp at nicira.com>
Acked-by: Justin Pettit <jpettit at nicira.com>


Compare: https://github.com/openvswitch/ovs/compare/58397e6c1e6c...d6f115f56a88