[glance] glance-cache-management hardcodes URL with port
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.
Not illegal, but it disables the glance-cache-manage client in its
On 8/13/2019 1:50 AM, Erno Kuvaja wrote:
> On Thu, Aug 8, 2019 at 12:49 PM Bernd Bausch <berndbausch at gmail.com
> <mailto:berndbausch at gmail.com>> wrote:
> Stein re-introduces Glance cache management, but I have not been
> able to
> use the glance-cache-manage command. I always get errno 111,
> It turns out that the command tries to access
> http://localhost:9292. It
> has options for non-default IP address and port, but unfortunately
> on my
> (devstack) cloud, the Glance endpoint is
> http://192.168.1.200/image. No
> Is there a way to tell glance-cache-manage to use this endpoint?
> Hi Bernd,
> 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.
> - Erno "jokke" Kuvaja
-------------- next part --------------
An HTML attachment was scrubbed...