Table tz_network_bindings uses nullable on primary keys

[Jakub Libosvar]

Primary key cannot be null therefore setting NULL on column that is primary key is wrong and then generates wrong migration script using autogenerate.

[OpenStack Infra (hudson-openstack)]

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

[Henry Gessau (gessau)]

This bug should have the same milestone and importance as bug 1346638 (juno-3, medium).

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/108690
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=e416a5420f45391c180f84098f4d2c02ecf857b9
Submitter: Jenkins
Branch: master

commit e416a5420f45391c180f84098f4d2c02ecf857b9
Author: Jakub Libosvar <email address hidden>
Date: Tue Jul 22 15:22:24 2014 +0200

    Replace nullable from primary keys in tz_network_bindings with default

    Columns vlan_id and phy_uuid were both nullable and primary keys.
    Primary keys cannot be nulls. This situation caused problems in
    autogenerating scripts creating always migration that set these columns
    to nullable.

    Instead of having primary keys nullable this patch creates a default
    values.

    Change-Id: I04642f6d6ad232997a593bff8ca44f9a7a803ffd
    Closes-bug: #1346900