Move database creation into role (keystone)

There is no record for why we implement the database creation outside
of the role in the playbook, when we could do it inside the role.

Implementing it inside the role allows us to reduce the quantity of
group_vars duplicated from the role, and allows us to better document
the required variables in the role. The delegation can still be done
as it is done in the playbook too.

In this patch we remove the group_vars which were duplicated from the
role, and remove the DB setup tasks as they are no longer required.

Change-Id: I7c18ba034462138c29b361fc03d8b98857f250de
Depends-On: https://review.openstack.org/571774

inventory/group_vars/keystone_all.yml

@@ -43,11 +43,6 @@ keystone_rabbitmq_telemetry_host_group: "{{ keystone_rabbitmq_host_group }}"
 # If there are any Ceilometer hosts in the environment, then enable its usage
 keystone_ceilometer_enabled: "{{ (groups['ceilometer_all'] is defined) and (groups['ceilometer_all'] | length > 0) }}"
 
-# The MySQL details for the keystone service
-keystone_galera_user: keystone
-keystone_galera_database: keystone
-keystone_galera_address: "{{ galera_address }}"
-
 # The system user for all keystone services
 keystone_system_user_name: keystone
 

playbooks/os-keystone-install.yml

@@ -83,15 +83,6 @@
         - groups[oslomsg_notify_host_group] | length > 0
       run_once: yes
 
-    - name: Configure MySQL user
-      include: common-tasks/mysql-db-user.yml
-      vars:
-        user_name: "{{ keystone_galera_user }}"
-        password: "{{ keystone_container_mysql_password }}"
-        login_host: "{{ keystone_galera_address }}"
-        db_name: "{{ keystone_galera_database }}"
-      run_once: yes
-
 
 
 - name: Installation and setup of Keystone