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

Bug 910873

Summary: Chapter: Document MySQL setup as a component in its own right.
Product: Red Hat OpenStack Reporter: Stephen Gordon <sgordon>
Component: doc-Installation_and_Configuration_GuideAssignee: Stephen Gordon <sgordon>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: alyoung, breeler, jocarter
Target Milestone: ---Keywords: Documentation, Triaged
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Red_Hat_OpenStack-Installation_and_Configuration_Guide-3-en-US-3-10 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 958248 (view as bug list) Environment:
Last Closed: 2013-07-01 20:24:22 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:
Bug Depends On:    
Bug Blocks: 958248    

Description Stephen Gordon 2013-02-13 18:45:49 UTC
Description of problem:

Currently MySQL setup is strewn throughout the guide. As a result it's very difficult to determine which bits are required versus which bits are optional. 

It's also difficult to work out how to extricate the steps required for a standalone MySQL server, which is important for multi-node setups.

I'd like to see MySQL covered as a component in its own right rather than as an afterthought in the other chapters.

Must also cover information that is missing from the guide but important to users doing multi-node deployment such as firewall ports that must be open, whether a FQDN is required, logs, etc.

Comment 3 Stephen Gordon 2013-02-27 19:31:44 UTC
Quantum requires that the MySQL server has a FQDN (Bug # 888773).

Comment 4 Stephen Gordon 2013-02-27 20:22:28 UTC
Just fleshing out what I think is required here in a new chapter:

Installing MySQL:
  yum install mysql-server
  chkconfig mysqld on
  service mysqld start

Configuring MySQL:
  Create Users:
    mysql -u root
    > GRANT ALL ON *.* TO 'root'@'localhost' IDENTIFIED BY 'password'
    > ...grants for specific components...
    > FLUSH PRIVILEGES
    > quit
  Edit my.cnf to bind on public address.
  Edit iptables to allow connections on 3306 from hosts.

Each chapter then needs to be updated to reflect that:
  - If mysqld is installed remotely the package must be installed there as well
    and the init script run.
  - If mysqld is not install remotely then the init script will create a db on the
    local machine.
  - Need to provide rootpw to initdb.

Comment 7 Stephen Gordon 2013-04-02 07:44:49 UTC
*** Bug 947141 has been marked as a duplicate of this bug. ***

Comment 8 Stephen Gordon 2013-04-02 07:45:42 UTC
(In reply to comment #0)
> Description of problem:
> 
> Currently MySQL setup is strewn throughout the guide. As a result it's very
> difficult to determine which bits are required versus which bits are
> optional. 

As part of this we need to be generic enough in stating up front requirements that it's possible to plug in other database engines as support emerges.

Comment 9 Stephen Gordon 2013-05-03 15:41:54 UTC
Database Server Requirements
Installing the Packages
Configuring the Database
Configuring the Firewall
Starting the Database Service
Validating the Database Installation

Comment 10 Stephen Gordon 2013-05-16 19:58:04 UTC
*** Bug 958248 has been marked as a duplicate of this bug. ***