Red Hat Bugzilla – Bug 977525
Step 3 uses the specific database name "network"
Last modified: 2013-09-24 13:56:48 EDT
Title: Creating the OpenStack Networking Database
Describe the issue:
Section 9.2 Step 3 uses the specific database name "network" rather than the generic DBNAME used in step 2
Suggestions for improvement:
Reworded step 3, so that the 'network' name is used (used later this chapter, not just this procedure). However, kept note about recommended database names.
Ready for QA with next doc release.
Sent in email as well. Have no idea whether Robert can access the file server...
I would suggest two solutions:
You could split the section into two tracks, Open vSwitch and Linux Bridge.
For packstack and Open vSwitch the database login name is quantum and the database is called ovs_quantum. I am not sure what the database login name if for Linux Bridge.
A different solution would be to mostly drop Linux Bridge. Use the quantum and ovs-quantum names and have a foot note explaining the different names for Linux Bridge.
I think the second solution is better since the direction OpenStack is taking is quantum. Are there many people migrating from Nova Networking to Linux Bridge? Is there a use case for existing Nova Network installations upgrading to Grizzly using Linux Bridge to preserve their Nova Networking configuration?
A third solution comes to mind. Since the quantum name is on the way out because of trademark issues, maybe packstack should be changed to use the names network for database login name and database name. I think this may be the best long term solution assuming that the name "network" is going to stick.
Also these changes will have to go into the next section at least, Configuring quantum.conf, if not others. The bear of documentation, getting everything to agree.
Thanks for that, Robert.
Yes, I thought about using either the open vswitch or linux bridge recommendations as the example, but because we are just days away from the release, have opted for the technically-accurate-that-won't break-anything-in-other-sections solution. So, if the 'network' name usage is at least now technically correct, am loathe to change it.
In version 4, anything to do with OS networking will be reworked and reworded to match the new neutron naming. I know that Packstack will be updated as well to match and anything 'quantum' will disappear. Certainly ovs_quantum will go away.
Am wondering if I should just get rid of the recommendations for now? Then it's a clean install, having nothing to do with the packstack conventions.
(In reply to Robert Harker from comment #5)
> I would suggest two solutions:
> You could split the section into two tracks, Open vSwitch and Linux Bridge.
> For packstack and Open vSwitch the database login name is quantum and the
> database is called ovs_quantum. I am not sure what the database login name
> if for Linux Bridge.
> A different solution would be to mostly drop Linux Bridge. Use the quantum
> and ovs-quantum names and have a foot note explaining the different names
> for Linux Bridge.
> I think the second solution is better since the direction OpenStack is
> taking is quantum. Are there many people migrating from Nova Networking to
> Linux Bridge? Is there a use case for existing Nova Network installations
> upgrading to Grizzly using Linux Bridge to preserve their Nova Networking
Last information I received on this was that nova network -> linuxbridge is actually the easiest/most likely to work migration. When and how nova network is going to be obsoleted in the upstream project is still a hot topic though so there are still decisions to be made (and migration paths finalized) here.
Either way both linuxbridge and openvswitch are intended to be fully supported and on an equal footing here so I would ensure that the solution does not involve making one of them a footnote.
*** Bug 979111 has been marked as a duplicate of this bug. ***
Created attachment 766384 [details]
Chapter 9-Installing the OpenStack Networking Service
Previous comment w/o internal link:
Ok, if we're going to pick one, using the packstack default makes sense. Also makes sense to switch the service default to make it all consistent. Here are the changes:
9.2.1 Creating the OpenStack Networking Database - Switched 'network' to 'ovs_quantum', and 'network' user to 'quantum'.
9.2.2 Creating the OpenStack Networking Identity Records - Switched both user and service from 'network' to 'quantum'. Note: The whole tenant issue will be dealt with in 965943. (will be switching to using one tenant for all services)
9.4 Configuring the Networking Service - Switched user to 'quantum'. Updated with note about 'ovs_quantum' as the example database.
9.5 Configuring the DHCP Agent - Switched user name to 'quantum'.
Robert, could you please do a review of this section please? I've attached a pdf of the chapter.
many thanks, Summer
From Robert per email: "Looks good." Note: He found more issues with adjacent material, and will be raising another bug (or more).
Ready for QA with the next doc release.