Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1142510

Summary: [Doc] Fix naming inconsistencies for the OpenStack Networking database (neutron)
Product: Red Hat OpenStack Reporter: Summer Long <slong>
Component: doc-Deploying_OpenStack_Learning_EnvironmentsAssignee: Martin Lopes <mlopes>
Status: CLOSED CURRENTRELEASE QA Contact: Andrew Dahms <adahms>
Severity: high Docs Contact:
Priority: high    
Version: 5.0 (RHEL 7)CC: adahms
Target Milestone: ---Keywords: Documentation, Triaged
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-15 23:49:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Summer Long 2014-09-16 23:09:04 UTC
Description of problem:
7.5.7. Create the OpenStack Networking Database
talks about creating a database using a naming format that depends on the plug-in. For example, ovs_neutron.
7.12. Configuring the OpenStack Networking SQL database connection
talks about the 'neutron' database.

All naming inconsistencies should be fixed.

Additional info:
Rajasekhar Manam (rmanam)" <rmanam> has raised this issue. We've emailed for the book version from which he's working.

Comment 1 Summer Long 2014-09-16 23:12:39 UTC
Martin, you might also think about making the neutron database naming consistent? E.g. neutron_<pluginName>.

Comment 2 Summer Long 2014-09-16 23:20:16 UTC
*** Bug 1142509 has been marked as a duplicate of this bug. ***

Comment 3 Martin Lopes 2014-09-17 05:11:56 UTC
* Removed 'neutron' database reference in "7.12. Configuring the OpenStack Networking SQL database connection"

* Added line directing user to naming recommendations instead: "See Section 7.5.7, “Create the OpenStack Networking Database” for recommended database naming conventions."

Comment 4 Martin Lopes 2014-09-17 05:14:57 UTC
Reviewed the 'ovs_neutron' database name. While not consistent with the other database names, this is how the component is referenced within the config files. I recommend keeping as-is to maintain the internal consistency.

Comment 5 Martin Lopes 2014-09-17 05:15:17 UTC
Ready for QA once package has been created.

Comment 7 Martin Lopes 2014-10-19 23:11:42 UTC
Setting to verified.