<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 18/10/16 15:52, Jamie Lennox wrote:<br>
</div>
<blockquote
cite="mid:CAAP=72j6LeB7zCVH4jcTy61k2AjR=gUkDUD-01PvfowCV40pNA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra">A comment from the cheap seats, almost
all clients are using a keystoneauth1 session at this point
and that's where your authentication information is being
cached. There is essentially no cost to creating a client with
an existing session as auth happens on demand.<br>
<br>
</div>
<div class="gmail_extra">The region_name is not part of the
authentication request, it's used to lookup the endpoint and
so is passed to Client creation. <br>
<br>
</div>
<div class="gmail_extra">Given this maybe there is no longer any
value in a ClientCache? It was mostly useful to prevent
clients doing dumb and share auth amongst them. So long as the
session/auth is created and saved once, a client can be
created per use/request with this information (including
region) with no real performance impact.<br>
<br>
</div>
<div class="gmail_extra">Jamie<br>
</div>
<div class="gmail_extra"><br>
</div>
</div>
</blockquote>
Getting rid of the cache would solve my problem, and considering
it's all one shared session it shouldn't cause any problems.<br>
<br>
Updating region_name would still be a problem for interactive mode,
although really that is a problem that is present right now anyway.<br>
</body>
</html>