Difference between revisions of "Nova/UserManagerAPISpec"
m (Text replace - "__NOTOC__" to "") |
|||
Line 1: | Line 1: | ||
− | + | ||
* '''Launchpad Entry''': [[NovaSpec]]:auth-manager-api | * '''Launchpad Entry''': [[NovaSpec]]:auth-manager-api | ||
* '''Created''': 2010-10-28 | * '''Created''': 2010-10-28 |
Revision as of 23:30, 17 February 2013
- Launchpad Entry: NovaSpec:auth-manager-api
- Created: 2010-10-28
- Contributors: Soren Hansen
Contents
Summary
Expose a user management API.
Release Note
OpenStack now exposes a user management API. This enables people deploying OpenStack to create custom interfaces to manage users.
Rationale
There's no reason why nova-manage should be the only way to admin users, and there's certainly no reason why people wanting to do this should talk directly to the DB or to LDAP.
User stories
Andrew wants to deploy OpenStack as a public cloud service. His company already has a web portal, and they want to be able to hook into OpenStack's user db.
Implementation
Through the EC2 API, these API calls will be exposed:
- CreateUser
- DescribeUsers
- DestroyUser
CreateUser
CreateUser takes a single argument:
Name |
AccessKey |
SecretKey |
Admin |
If succesful, the API call will return:
Name |
AccessKey |
SecretKey |
Admin |
DescribeUser
DescribeUsers takes the following arguments:
Name |
AccessKey |
Both are optional. If none are given, a complete list of users is returned. If either (or both) are given, the user (if any) matching the criteria is returned.
Returns a list of these:
Name |
AccessKey |
SecretKey |
Admin |
DestroyUser
DestroyUser takes a single argument:
Name |
OpenStack API
We need to expose the same functionality through the OpenStack API
TBD
Test/Demo Plan
This need not be added or completed until the specification is nearing beta.