Investigate endpoint, service, and region configuration options

Bug #1835106 reported by Lance Bragstad
This bug affects 1 person
Affects Status Importance Assigned to Milestone
In Progress
Victor Coutellier

Bug Description

The current implementation of oslo.limit requires that services know who they are. To do this, operators need to set a configuration option that tell each service which service they are and what region they are in.

Currently, this is achieved using endpoint_ids, since endpoints reference both services and regions. Oslo.limit and query keystone for information about the service and region based on the endpoint ID in configuration. Endpoint IDs aren't as user friendly as service name + region name configuration options.

We should ask operators which approach is better, since they're the ones that have to configure the system. Based on their answer, we should either implement new configuration options for services and region or keep the single endpoint ID option we have today.

This was discussed during a group code review of the oslo.limit implementation [0].


Colleen Murphy (krinkle)
Changed in oslo.limit:
status: New → Triaged
importance: Undecided → Low
Changed in oslo.limit:
assignee: nobody → Victor Coutellier (alistarle)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to oslo.limit (master)

Fix proposed to branch: master

Changed in oslo.limit:
status: Triaged → In Progress
Revision history for this message
Victor Coutellier (alistarle) wrote :

Note that this fix rely on another patch against openstacksdk :

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers