This section describes how to install and configure the OpenStack Identity service, code-named keystone, on the controller node. For scalability purposes, this configuration deploys Fernet tokens and the Apache HTTP server to handle requests.
Ensure that you have completed the prerequisite installation steps in the Openstack Install Guide before proceeding.
Before you install and configure the Identity service, you must create a database.
Use the database access client to connect to the database server as the
MariaDB [(none)]> CREATE DATABASE keystone;
Grant proper access to the
MariaDB [(none)]> GRANT ALL PRIVILEGES ON keystone.* TO 'keystone'@'localhost' \ IDENTIFIED BY 'KEYSTONE_DBPASS'; MariaDB [(none)]> GRANT ALL PRIVILEGES ON keystone.* TO 'keystone'@'%' \ IDENTIFIED BY 'KEYSTONE_DBPASS';
KEYSTONE_DBPASS with a suitable password.
This guide uses the Apache HTTP server with
mod_wsgi to serve Identity service requests on port 5000. By default, the keystone service still listens on this port. The package handles all of the Apache configuration for you (including the activation of the
mod_wsgi apache2 module and keystone configuration in Apache).
Run the following command to install the packages:
# apt install keystone
/etc/keystone/keystone.conffile and complete the following actions:
[database] section, configure database access:
KEYSTONE_DBPASS with the password you chose for the database.
Comment out or remove any other
connection options in the
[token] section, configure the Fernet token provider:
Populate the Identity service database:
# su -s /bin/sh -c "keystone-manage db_sync" keystone
Initialize Fernet key repositories:
--keystone-group flags are used to specify the operating system's user/group that will be used to run keystone. These are provided to allow running keystone under another operating system user/group. In the example below, we call the user & group
# keystone-manage fernet_setup --keystone-user keystone --keystone-group keystone # keystone-manage credential_setup --keystone-user keystone --keystone-group keystone
Bootstrap the Identity service:
Before the Queens release, keystone needed to be run on two separate ports to accommodate the Identity v2 API which ran a separate admin-only service commonly on port 35357. With the removal of the v2 API, keystone can be run on the same port for all interfaces.
# keystone-manage bootstrap --bootstrap-password ADMIN_PASS \ --bootstrap-admin-url http://controller:5000/v3/ \ --bootstrap-internal-url http://controller:5000/v3/ \ --bootstrap-public-url http://controller:5000/v3/ \ --bootstrap-region-id RegionOne
ADMIN_PASS with a suitable password for an administrative user.
/etc/apache2/apache2.conf file and configure the
ServerName option to reference the controller node:
ServerName entry will need to be added if it does not already exist.
A secure deployment should have the web server configured to use SSL or running behind an SSL terminator.
Restart the Apache service:
# service apache2 restart
Configure the administrative account by setting the proper environmental variables:
$ export OS_USERNAME=admin $ export OS_PASSWORD=ADMIN_PASS $ export OS_PROJECT_NAME=admin $ export OS_USER_DOMAIN_NAME=Default $ export OS_PROJECT_DOMAIN_NAME=Default $ export OS_AUTH_URL=http://controller:5000/v3 $ export OS_IDENTITY_API_VERSION=3
These values shown here are the default ones created from
ADMIN_PASS with the password used in the
keystone-manage bootstrap command in keystone-install-configure-ubuntu.