Juju Charms

Summary
OpenStack identity service

Charm Store
juju deploy cs:~gandelman-a/precise/keystone-1

Owner
gandelman-a

Maintainer
Adam Gandelman

Series
precise

Description
Keystone is an OpenStack project that provides Identity, Token, Catalog and Policy services for use specifically by projects in the OpenStack family. It implements OpenStack’s Identity API.

Links
Repository Bugs
lp:~gandelman-a/charms/precise/keystone/trunk

Hooks

Interfaces

Provides

identity-service
keystone

Requires

shared-db
mysql-shared

Config

admin-user string

admin-token string

openstack-origin string

verbose string

database string

admin-role string

admin-port int

service-port int

keystone-service-admin-role string

config-file string

token-expiry string

keystone-admin-role string

service-tenant string

debug string

database-user string

admin-password string

Details

Readme

This charm provides Keystone, the Openstack identity service.  It's target
platform is Ubuntu Precise + Openstack Essex.  This has not been tested
using Oneiric + Diablo.

It provides two interfaces.
 
    - identity-service:  Openstack API endpoints request an entry in the 
      Keystone service catalog + endpoint template catalog.  When a relation
      is established, Keystone receives: service name, region, public_url,
      admin_url and internal_url.  It first checks that the requested service
      is listed as a supported service.  This list should stay updated to
      support current Openstack core services.  If the services is supported,
      a entry in the service catalog is created, an endpoint template is
      created and a admin token is generated.   The other end of the relation
      recieves the token as well as info on which ports Keystone is listening.

    - keystone-service:  This is currently only used by Horizon/dashboard
      as its interaction with Keystone is different from other Openstack API
      servicies.  That is, Horizon requests a Keystone role and token exists.
      During a relation, Horizon requests its configured default role and
      Keystone responds with a token and the auth + admin ports on which
      Keystone is listening.

Keystone requires a database.  By default, a local sqlite database is used.
The charm supports relations to a shared-db via mysql-shared interface.  When
a new data store is configured, the charm ensures the minimum administrator
credentials exist (as configured via charm configuration)

Changes

2012/10/12 Adam Gandelman Rename config option for consistency across charms: keystone-release -> openstack-origin. (revno 39)
2012/10/10 Adam Gandelman Support cloud:precise-folsom/staging installation source. (revno 38)
2012/10/03 Adam Gandelman Factor out common code. Allow upgrades Essex -> Folsom. (revno 37)
2012/09/20 Adam Gandelman hooks/utils.py: Avoid another duplicate role assignment in create_role(). Do not add role directly (revno 36)
2012/09/18 Adam Gandelman Allow service entries to be recreated after new database relation. This eliminates the need for ser (revno 35)
2012/09/17 Adam Gandelman Add missing sym link: hooks/config-changed. (revno 34)
2012/08/10 Adam Gandelman Merged config-changed support from lp:~gandelman-a/charms/precise/keystone/config-changed (revno 33)
2012/08/10 Adam Gandelman Merged role grant fix from lp:~gandelman-a/charms/precise/keystone/fix-grant-role (revno 32)
2012/06/07 Adam Gandelman metadata.yaml: Add maintainer, update description. (revno 31)

Lint Check

warn: missing recommended hook start
warn: missing recommended hook stop

In other archives

Newer precise/keystone
~smoser:precise/keystone
Newer ~openstack-ubuntu-testing:precise/keystone

Charm: keystone