Pranav Salunke e0d970e40d Adds Keystone service tenant
Keystone service tenant is required by OpenStack services to
authenticate. We could reuse admin tenant for the same but it
will provide OpenStack services with unnecessary privileges.

Implements: blueprint openstack-training-labs
Change-Id: Ia72012a09da36df5f52454c289775a8b050f9e1a
2014-08-09 11:14:00 +02:00

35 lines
1.3 KiB
Bash

# This file contains user names, passwords, and tokens that are set and used
# by OpenStack applications and related software running in the VMs.
# Note that the VM shell user and its password are not set here. By default,
# those are hard-coded in the preseed/kickstart files or in the Vagrant base
# box. The scripts get the shell user name from deploy.{osbash,vagrant} and
# don't need a password (they use password-less sudo and -- if configured --
# ssh keys).
# Used for MySQL or whatever other DBMS is configured
: ${DATABASE_PASSWORD:=secrete}
# A "shared secret" used as OS_SERVICE_TOKEN, together with
# OS_SERVICE_ENDPOINT, before keystone can be used for authentication
# Produced by: openssl rand -hex 10
: ${ADMIN_TOKEN:=c9fbb405c325e018fc5e}
# Tenant and role for admin accounts
: ${ADMIN_ROLE_NAME:=admin}
: ${ADMIN_TENANT_NAME:=admin}
# User name and password for administrator
: ${ADMIN_USER_NAME:=admin}
: ${ADMIN_PASSWORD:=admin_pass}
# OpenStack Services needs to be affiliated with a tenant to provide
# authentication to other OpenStack services. We create a "service" tenant for
# the OpenStack services. All the OpenStack services will be registered via
# service tenant.
# Tenant and role for service accounts.
: ${SERVICE_TENANT_NAME:=service}
# vim: set ai ts=4 sw=4 et ft=sh: