yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: quantum
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1099895

Title:
  Missing migration for NVP plugin

Status in OpenStack Quantum (virtual network service):
  Fix Released

Bug description:
  A model used by Nicira NVP plugin is not included in folsom_initial
  migration, so a new migration is required:

  class NvpNetworkBinding(model_base.BASEV2):
      """Represents a binding of a virtual network with a transport zone.

      This model class associates a Quantum network with a transport zone;
      optionally a vlan ID might be used if the binding type is 'bridge'
      """
      __tablename__ = 'nvp_network_bindings'

      network_id = Column(String(36),
                          ForeignKey('networks.id', ondelete="CASCADE"),
                          primary_key=True)
      # 'flat', 'vlan', stt' or 'gre'
      binding_type = Column(Enum('flat', 'vlan', 'stt', 'gre'), nullable=False)
      tz_uuid = Column(String(36))
      vlan_id = Column(Integer)

  Each plugin is currently providing its own network binding model, so
  the ones created for instance, for the OVS plugin, won't work with the
  NVP plugin.

  This is likely to be happened because the patches for alembic
  migrations and provider networks on NVP where concurrently under
  review.

To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/1099895/+subscriptions