vmware-nsx

History

Henry Gessau 22b6a3f0a0 Use DB field sizes instead of _MAX_LEN constants

The following _MAX_LEN constants are being removed from
neutron/api/v2/attributes.py in [1]. The corresponding DB field size
constants from neutron_lib.db.constants should be used instead.

 NAME_MAX_LEN              -->  NAME_FIELD_SIZE
 TENANT_ID_MAX_LEN         -->  PROJECT_ID_FIELD_SIZE
 DESCRIPTION_MAX_LEN       -->  DESCRIPTION_FIELD_SIZE
 LONG_DESCRIPTION_MAX_LEN  -->  LONG_DESCRIPTION_FIELD_SIZE
 DEVICE_ID_MAX_LEN         -->  DEVICE_ID_FIELD_SIZE
 DEVICE_OWNER_MAX_LEN      -->  DEVICE_NAME_FIELD_SIZE

In alembic migration scripts, the raw numerical value shall be used.

For more information, see [2].

[1] https://review.openstack.org/399891
[2] http://lists.openstack.org/pipermail/openstack-dev/2016-October/105789.html

Change-Id: I7e53de4ceecfe37edc0cb0041c23ce131f5eeca1

2016-11-26 01:05:21 -05:00

__init__.py

Move vmware_nsx/neutron/plugins/vmware to vmware_nsx

2015-09-14 18:51:57 -07:00

advancedserviceproviders.py

Move vmware_nsx/neutron/plugins/vmware to vmware_nsx

2015-09-14 18:51:57 -07:00

api_replay.py

Use DB field sizes instead of _MAX_LEN constants

2016-11-26 01:05:21 -05:00

dhcp_mtu.py

NSX|V add dhcp-mtu extension to subnet