document base model types for key elements within Keystone API
Bug #928441 reported by
Joseph Heck
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Joseph Heck |
Bug Description
Set up an "abstract base class" for the objects that the Keystone API interacts with, including docstring documentation to outline how they're allowed to interact with the service APIs and how they're not. This is intended to help inform Backend/driver implementors what needs to be done to work with the keystone internal APIs
* User
* Tenant
* Token
* Catalog endpoint
* Roles
* Action
* Capability
Termie's suggestion - document this in keystone/
summary: |
- create abstract base classes for key elements within Keystone API + document base model types for key elements within Keystone API |
description: | updated |
Changed in keystone: | |
importance: | Medium → High |
tags: | added: docs |
Changed in keystone: | |
status: | Confirmed → Fix Committed |
milestone: | none → essex-rc2 |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
milestone: | essex-rc2 → folsom-1 |
status: | Fix Released → Confirmed |
Changed in keystone: | |
assignee: | nobody → Joseph Heck (heckj) |
Changed in keystone: | |
milestone: | folsom-1 → folsom-2 |
Changed in keystone: | |
status: | Confirmed → In Progress |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | folsom-2 → 2012.2 |
To post a comment you must log in.
Should not be an Abstract base class, but rather a domain model class that is not tied to any of the backend implementations.