Hi again Andy, Thanks for the update. Sounds like there is some work to do in various client libraries first.
I also just tried to launch a Sahara cluster against a community image-- it failed, because our current validation wants the image ID to actually appear in the image list. So there will have to be a server side tweak to Sahara as well (not necessarily using your desired "list all" mechanism, but it could be). Anyway, the Sahara team is aware, and we'll keep an eye on this moving forward. Cheers, Jeremy On Thu, Aug 23, 2018 at 8:43 PM, Andy Botting <a...@andybotting.com> wrote: > Hi Jeremy, > >> >> Can you comment more on what needs to be updated in Sahara? Are they >> simply issues in the UI (sahara-dashboard) or is there a problem >> consuming community images on the server side? > > > We haven't looked into it much yet, so I couldn't tell you. > > I think it would be great to extend the Glance API to include a > visibility=all filter, so we can actually get ALL available images in a > single request, then projects could switch over to this. > > It might need some thought on how to manage the new API request when using > an older version of Glance that didn't support visibility=all, but I'm sure > that could be worked out. > > It would be great to hear from one of the Glance devs what they think about > this approach. > > cheers, > Andy > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
