Support Accept-Language for API messages
Currently, error/exception messages coming back from Keystone are not translated at all. Ideally, we would like to have the messages translated to the request senders locale, which we can support using the HTTP Accept-Language header to determine a preferred locale before sending back the translated response. Alternatively, there is the possibility of using the tenant/user data to store a preferred locale for the request.
There is a similar blueprint for Nova that can be used to track the implementation work there:
https:/
Blueprint information
- Status:
- Complete
- Approver:
- Brant Knudson
- Priority:
- Medium
- Drafter:
- Mathew Odden
- Direction:
- Approved
- Assignee:
- Brant Knudson
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
-
Implemented
- Milestone target:
-
2014.1
- Started by
- Brant Knudson
- Completed by
- Dolph Mathews
Related branches
Related bugs
Sprints
Whiteboard
A good spot to do any checking and translation of exception messages is here:
https:/
Gerrit topic: https:/
Addressed by: https:/
Add support for API message localization
Addressed by: https:/
Use keystone.
---
Unfortunately, this was disabled late in the havana cycle. See https:/
---
All we should need to do here is
a) wait for oslo changes
b) merge oslo changes
b) Change gettextutils.
Addressed by: https:/
Do not append to messages with +
Addressed by: https:/
Sync gettextutils from oslo-incubator 997ab277
Addressed by: https:/
Enable lazy translation
Addressed by: https:/
Add localized response test
Work Items
Work items:
Integrate common gettext utilities for delayed translations from oslo-incubator: TODO
Re-enable support Accept-Language header support and API layer translations: TODO
Dependency tree
* Blueprints in grey have been implemented.
