Bug 820772

The creation of a user is documented in the beaker-init step, where we pass an admin user and password in.

Beaker supports MySQL,MSSQL,Oracle,MaxDB,PostgreSQL, and SQLite. For this tutorial,we willMySQL. First, make sure MySQL server is installed, and configure the daemon to run at startup.
$ yum install -y mysql-server MySQL-python
$ chkconfig mysqld on
$ service mysqld start
Create a database, and grant access to beaker user. You can put the database on the local machine,
or on a remote machine. In the example below, the database is hosted on the local machine.
$ echo "create database beaker;" | mysql
$ echo "grant all on beaker.* to 'beaker'@'localhost' IDENTIFIED BY 'beaker';"| mysql
Now let's initialise our DB with tables. We'll also create an admin account called admin with password
testing, and email root@localhost.
$ beaker-init -u admin -p testing -e root@localhost

This is from Beaker-0-Deployment_Guide-en-US.pdf, which appears to be the only version available online.

Looking in my git tree (not fully up to date, but pretty recent), none of this has changed in pub_doc?

Let's say you are right, though, and the beaker-init step does something to create a 'beaker' user -- that should be documented that it's happening, shouldn't it?

Finally, the DB commands are *before* the beaker-init commands in the doc, so it doesn't seem like the beaker-init command should be relevant.

(In reply to comment #2)
> Beaker supports MySQL,MSSQL,Oracle,MaxDB,PostgreSQL, and SQLite. For this
> tutorial,we willMySQL. First, make sure MySQL server is installed, and
> configure the daemon to run at startup.
> $ yum install -y mysql-server MySQL-python
> $ chkconfig mysqld on
> $ service mysqld start
> Create a database, and grant access to beaker user. You can put the database
> on the local machine,
> or on a remote machine. In the example below, the database is hosted on the
> local machine.
> $ echo "create database beaker;" | mysql
> $ echo "grant all on beaker.* to 'beaker'@'localhost' IDENTIFIED BY
> 'beaker';"| mysql
> Now let's initialise our DB with tables. We'll also create an admin account
> called admin with password
> testing, and email root@localhost.
> $ beaker-init -u admin -p testing -e root@localhost
> 
> This is from Beaker-0-Deployment_Guide-en-US.pdf, which appears to be the
> only version available online.
> 
> Looking in my git tree (not fully up to date, but pretty recent), none of
> this has changed in pub_doc?
> 
> Let's say you are right, though, and the beaker-init step does something to
> create a 'beaker' user -- that should be documented that it's happening,
> shouldn't it?
> 
> Finally, the DB commands are *before* the beaker-init commands in the doc,
> so it doesn't seem like the beaker-init command should be relevant.

Sorry Nish. When you said 'creating a beaker user' I expected you meant a user in the beaker user database. Which is what 'beaker-init -u admin -p testing' does, it creates the 'admin' user.

I think what you meant though was 'create the beaker user in the DB', which is the user referred to here:

  $ echo "grant all on beaker.* to 'beaker'@'localhost' IDENTIFIED BY   'beaker';"| mysql

http://gerrit.beaker-project.org/#/c/1081/