Plugin request helpers

Registered by Jamie Lennox on 2015-02-13

There are a number of growing de-facto standards around the ways that services should talk to each other. For the moment those i know of are:
 - You should include the X-Service-Token when making requests between services
 - You should include the X-OpenStack-Request-id from the incoming request in outgoing requests.

And i'm sure others will come along.

Given that we pass an auth plugin down from keystonemiddleware that correctly fills the X-Auth-Token and that the above information is generally available from auth_token middleware the plugin that is presented to the user should transparently do 'the right thing' as much as possible to distance these standards from service writers.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Jamie Lennox
Direction:
Needs approval
Assignee:
Jamie Lennox
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:subject-token,n,z

Addressed by: https://review.openstack.org/141614
    Add subject token token to user token plugin

Addressed by: https://review.openstack.org/155672
    Add Request ID to outbound calls when set

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.