Missing migration for NVP plugin

[Salvatore Orlando]

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.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/19709

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/19709
Committed: http://github.com/openstack/quantum/commit/2d4431d7bc6b7ab362ce2cf084b901be45c51c2f
Submitter: Jenkins
Branch: master

commit 2d4431d7bc6b7ab362ce2cf084b901be45c51c2f
Author: Salvatore Orlando <email address hidden>
Date: Tue Jan 15 07:49:04 2013 -0800

    Add migration for network bindings in NVP plugin

    Bug 1099895

    Ensures the table nvp_network_bindings is created when upgrading
    database to head, by adding an appropriate alembic migration

    Change-Id: I4a794ed0ec6866d657cb2470d5aa67828e81aa75