Move database creation into role (glance)

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 test-vars which were duplicated from the
role, and remove the DB setup tasks as they are no longer required.

Change-Id: I0dfe0bd8316ff7c1db916aa8e8d6c13d0715b30d
Depends-On: https://review.openstack.org/568481

test-install-glance.yml

@@ -37,10 +37,6 @@
       when:
         - "'oslomsg_rpc_all' in groups"
         - "groups['oslomsg_rpc_all'] | length > 0"
-
-    - include: create-grant-db.yml
-      db_name: "{{  glance_galera_database }}"
-      db_password: "{{ glance_container_mysql_password }}"
   roles:
     - role: "{{ glance_rolename | default('os_glance') }}"
   vars_files:

test-vars.yml

@@ -162,7 +162,6 @@ glance_service_user_name: glance
 glance_container_mysql_password: "SuperSecrete"
 glance_developer_mode: true
 glance_galera_address: "{{ test_galera_host }}"
-glance_galera_database: glance
 glance_git_install_branch: "{{ test_branch }}"
 glance_profiler_hmac_key: "secrete"
 glance_oslomsg_rpc_password: "{{ oslomsg_rpc_password }}"