Public bug reported:
Now that the database is healed and all tables are present, the names of
tables are haphazard and there is no convention for avoiding naming
conflicts or having sensible grouping.
A naming convention may look something like:
<vendor>_<plugin|service>_<feature|purpose>
Existing tables should be renamed to follow the convention.
A README file explaining the convention should be created in the
directory with the models.
** Affects: neutron
Importance: Undecided
Assignee: Henry Gessau (gessau)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Henry Gessau (gessau)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1347361
Title:
There should be a naming convention for neutron DB tables
Status in OpenStack Neutron (virtual network service):
New
Bug description:
Now that the database is healed and all tables are present, the names
of tables are haphazard and there is no convention for avoiding naming
conflicts or having sensible grouping.
A naming convention may look something like:
<vendor>_<plugin|service>_<feature|purpose>
Existing tables should be renamed to follow the convention.
A README file explaining the convention should be created in the
directory with the models.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1347361/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
