[RFE] Stop duplicating schema for common attributes

[Kevin Benton]

Several features have come up that can apply to multiple types of objects (qos, port security enabled, rbac, timestamps, tags) and each time we implement them we either duplicate schema across a bunch of tables or we have a single table with no referential integrity.

We should add a new table that all of the Neutron resources relate to and then have new features that apply to multiple object types relate to the new neutron resources table. This prevents duplication of schema while maintaining referential integrity.

[Armando Migliaccio (armando-migliaccio)]

I think the latest technical kinks have been resolved or in the process of being resolved, and discussed with DB SMEs, so this should be good to go.

[Armando Migliaccio (armando-migliaccio)]

https://review.openstack.org/#/c/222079/

[OpenStack Infra (hudson-openstack)]

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

commit 3c8570f3fcd54c1061467616f1d04e95db27a292
Author: Kevin Benton <email address hidden>
Date: Wed Sep 2 16:37:17 2015 -0700

    Make Neutron resources reference standard attr table

    This adds a new 'standardattributes' table and adds a foreign-key
    references from ports, subnets, networks, subnetpools, routers,
    securitygroups, and floatingips to this table.

    This will make it easy to add new things to the schema like
    timestamp fields or anything else that applies to multiple types
    of Neutron resources. The new fields would just be added to the
    'neutronresources' table instead of being duplicated across each
    resource's table. Or, if the the relationship is 1-to-many (e.g. tags),
    the new association table would be related to the 'standardattribute'
    table.

    Related-Bug: #1496802
    Change-Id: Iaa3ba81a7e9cae09cea153720b29879d8cc9a080

[Armando Migliaccio (armando-migliaccio)]

Technically speaking this bug report was addressed. It's the ones that leverage this capability that need to be moved along.