<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Erno,</p>
<p>yes, the /image is the problem. This is a Devstack
(stable/Stein), which by default deploys Glance and all(?) other
services as WSGI applications. I know that this is not recommended
for Glance, but it's not illegal either, as far as I understand
it.</p>
<p>Not illegal, but it disables the glance-cache-manage client in
its current form.<br>
</p>
<p>Bernd<br>
</p>
<div class="moz-cite-prefix">On 8/13/2019 1:50 AM, Erno Kuvaja
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKwVDDNBUxFGc4nh0=81cW+JrS19p=K6MypeGwpKSowcgdr9bA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Aug 8, 2019 at 12:49
PM Bernd Bausch <<a href="mailto:berndbausch@gmail.com"
moz-do-not-send="true">berndbausch@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div>Stein re-introduces Glance cache management, but I have
not been able to <br>
use the glance-cache-manage command. I always get errno
111, connection <br>
refused.<br>
<br>
It turns out that the command tries to access <a
href="http://localhost:9292" rel="noreferrer"
target="_blank" moz-do-not-send="true">http://localhost:9292</a>.
It <br>
has options for non-default IP address and port, but
unfortunately on my <br>
(devstack) cloud, the Glance endpoint is <a
href="http://192.168.1.200/image" rel="noreferrer"
target="_blank" moz-do-not-send="true">http://192.168.1.200/image</a>.
No <br>
port.<br>
<br>
Is there a way to tell glance-cache-manage to use this
endpoint?<br>
<br>
Bernd.<br>
<br>
</div>
</blockquote>
<div> </div>
<div>Hi Bernd,<br>
</div>
<div><br>
</div>
<div>You can always give it the port 80, the real problem
likely is the prefix /image you have there. Are you running
glance-api as wsgi app under some http-server or is that
reverse-proxy/loadbalancer you're directing the
glance-cache-manage towards? Remember that the management is
not currently cluster wide so you should be always targeting
single service process at the time.</div>
<div><br>
</div>
<div>- Erno "jokke" Kuvaja<br>
</div>
</div>
</div>
</blockquote>
</body>
</html>