yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1940341] [NEW] Adding a second region breaks existing clients

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Sam Morrison <1940341@xxxxxxxxxxxxxxxxxx>
Date: Wed, 18 Aug 2021 01:44:23 -0000
Reply-to: Bug 1940341 <1940341@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx

Public bug reported:

We currently have an installation with a single region. We want to
expand to another region but this is proving difficult.

When I add a new endpoint for our new region, clients that are
configured not to use a region can (depending on the ID of the endpoint)
all of a sudden now start hitting the new endpoint.

It is not practical to get all of our thousands of users using lots of
different clients to explicitly set a region when authing.

So I'm wondering if it is possible to support a default region or
default endpoint. This endpoint would be listed first when listing the
endpoints for a service. Currently this is ordered based on the endpoint
ID so a work around is to hack the endpoint IDs to ensure the one you
want listed first is set.

Thoughts?

** Affects: keystone
     Importance: Undecided
         Status: New

** Summary changed:

- Default regions and endpoints
+ Adding a second region breaks existing clients

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1940341

Title:
  Adding a second region breaks existing clients

Status in OpenStack Identity (keystone):
  New

Bug description:
  We currently have an installation with a single region. We want to
  expand to another region but this is proving difficult.

  When I add a new endpoint for our new region, clients that are
  configured not to use a region can (depending on the ID of the
  endpoint) all of a sudden now start hitting the new endpoint.

  It is not practical to get all of our thousands of users using lots of
  different clients to explicitly set a region when authing.

  So I'm wondering if it is possible to support a default region or
  default endpoint. This endpoint would be listed first when listing the
  endpoints for a service. Currently this is ordered based on the
  endpoint ID so a work around is to hack the endpoint IDs to ensure the
  one you want listed first is set.

  Thoughts?

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1940341/+subscriptions