- Overview - What is the keystone module?
- Module Description - What does the module do?
- Setup - The basics of getting started with keystone
- Implementation - An under-the-hood peek at what the module is doing
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
- Contributors - Those with commits
- Release Notes - Release notes for the project
- Repository - The project source code repository
The keystone module is a part of OpenStack, an effort by the OpenStack infrastructure team to provide continuous integration testing and code review for OpenStack and OpenStack community projects as part of the core software. The module itself is used to flexibly configure and manage the identity service for OpenStack.
The keystone module is a thorough attempt to make Puppet capable of managing the entirety of keystone. This includes manifests to provision region specific endpoint and database connections. Types are shipped as part of the keystone module to assist in manipulation of configuration files.
This module is tested in combination with other modules needed to build and leverage an entire OpenStack software stack.
What the keystone module affects
- Keystone, the identity service for OpenStack.
puppet module install openstack/keystone
To utilize the keystone module's functionality you will need to declare multiple resources. This is not an exhaustive list of all the components needed, we recommend you consult and understand the core openstack documentation.
Define a keystone node
class { 'keystone::db':
database_connection => 'mysql://keystone_admin:[email protected]/keystone',
}
class { 'keystone':
catalog_driver => 'sql',
}
class { 'keystone::bootstrap':
password => 'super_secret',
public_url => 'http://10.16.0.101:5000',
admin_url => 'http://10.16.1.101:5000',
internal_url => 'http://10.16.2.101:5000',
region => 'example-1',
}Leveraging the Native Types
Keystone ships with a collection of native types that can be used to interact with the data stored in keystone. The following, related to user management could live throughout your Puppet code base. They even support puppet's ability to introspect the current environment much the same as puppet resource user, puppet resource keystone_tenant will print out all the currently stored tenants and their parameters.
keystone_tenant { 'openstack':
ensure => present,
enabled => true,
}
keystone_user { 'openstack':
ensure => present,
enabled => true,
}
keystone_role { 'admin':
ensure => present,
}
keystone_user_role { 'admin@openstack':
roles => ['admin', 'superawesomedude'],
ensure => present
}These two will seldom be used outside openstack related classes, like nova or cinder. These are modified examples from Class['nova::keystone::auth'].
# Setup the nova keystone service
keystone_service { 'nova':
ensure => present,
type => 'compute',
description => 'OpenStack Compute Service',
}
Services can also be written with the type as a suffix:
keystone_service { 'nova::type':
ensure => present,
description => 'OpenStack Compute Service',
}
# Setup nova keystone endpoint
keystone_endpoint { 'example-1-west/nova':
ensure => present,
type => 'compute',
public_url => "http://127.0.0.1:8774/v2/%(tenant_id)s",
admin_url => "http://127.0.0.1:8774/v2/%(tenant_id)s",
internal_url => "http://127.0.0.1:8774/v2/%(tenant_id)s",
}Endpoints can also be written with the type as a suffix:
keystone_endpoint { 'example-1-west/nova::compute':
ensure => present,
public_url => "http://127.0.0.1:8774/v2/%(tenant_id)s",
admin_url => "http://127.0.0.1:8774/v2/%(tenant_id)s",
internal_url => "http://127.0.0.1:8774/v2/%(tenant_id)s",
}Defining an endpoint without the type is supported in Liberty release for backward compatibility, but will be dropped in Mitaka, as this can lead to corruption of the endpoint database if omitted. See this bug
Setting up a database for keystone
A keystone database can be configured separately from the keystone services.
If one needs to actually install a fresh database they have the choice of mysql or postgres. Use the mysql::server or postgreql::server classes to do this setup, and then the Class['keystone::db::mysql'] or Class['keystone::db::postgresql'] for adding the databases and users that will be needed by keystone.
- For mysql
class { 'mysql::server': }
class { 'keystone::db::mysql':
password => 'super_secret_db_password',
allowed_hosts => '%',
}- For postgresql
class { 'postgresql::server': }
class { 'keystone::db::postgresql': password => 'super_secret_db_password', }About Keystone V3 syntax in keystone_user/keystone_tenant/keystone_user_role
A complete description of the syntax available for those resources are
in examples/user_project_user_role_composite_namevar.pp
About Keystone V3 and default domain
For users
With Keystone V3, domains made their appearance. For backward
compatibility a default domain is defined in the keystone.conf file.
All the V2 resources are then assigned to this default domain. The
default domain id is by default default associated with the name
Default.
What it means is that this user:
keystone_user { 'my_non_full_qualified_user':
ensure => present
}will be assigned to the Default domain.
The same is true for keystone_tenant and keystone_user_role:
keystone_tenant { 'project_one':
ensure => present
}
keystone_user_role { 'user_one@project_one':
ensure => present,
roles => ['admin']
}will be assigned to the Default domain.
Now, you can change the default domain if you want. But then the puppet resource you defined will have to be fully qualified.
So, for instance, if you change the default domain to be
my_new_default, then you'll have to do:
keystone_user { 'full_qualified_user::my_new_default':
ensure => present
}
keystone_tenant { 'project_one::my_new_default':
ensure => present
}
keystone_user_role { 'user_one::my_new_default@project_one::my_new_default':
ensure => present,
roles => ['admin']
}as the module will always assign a resource without domain to
the Default domain.
A deprecation warning will be visible in the log when you have changed the default domain id and used an non fully qualified name for your resource.
In Mitaka, a deprecation warning will be displayed any time you use a non fully qualified resource.
After Mitaka all the resources will have to be fully qualified.
For developers
Other modules can try to find user/tenant resources using Puppet's indirection. The rule for the name of the resources are:
- fully qualified if domain is not 'Default';
- short form if domain is 'Default'
This is for backward compatibility.
Note that, as stated above, the 'Default' domain is hardcoded. It is not related to the real default domain which can be set to something else. But then again, you will have to set the fully qualified name.
You can check spec/acceptance/default_domain_spec.rb to see an
example of the behavior described here.
keystone is a combination of Puppet manifest and ruby code to delivery configuration and extra functionality through types and providers.
The keystone_config provider is a children of the ini_setting provider. It allows one to write an entry in the /etc/keystone/keystone.conf file.
keystone_config { 'token/expiration' :
value => 3600,
}This will write expiration=3600 in the [token] section.
Section/setting name to manage from keystone.conf
The value of the setting to be defined.
Whether to hide the value from Puppet logs. Defaults to false.
If value is equal to ensure_absent_val then the resource will behave as if ensure => absent was specified. Defaults to <SERVICE DEFAULT>
- All the keystone types use the CLI tools and so need to be run on the keystone node.
- If you've setup OpenStack using previous versions of this module you need to be aware that it used UUID as the default for the token_format parameter but now defaults to PKI. If you're using this module to manage a Grizzly OpenStack deployment that was set up using a development release of the modules or are attempting an upgrade from Folsom then you'll need to make sure you set the token_format to UUID at classification time.
Developer documentation for the entire puppet-openstack project.