On 19 August 2015 at 19:30, Alberto Geniola <[email protected]> wrote: > > Hi everyone, > > > This is my first email to the OS developer forum, so forgive me if I > misplaced the subject tags J.
Welcome! For future posts, I hope this helps make it easier: https://wiki.openstack.org/wiki/MailingListEtiquette > Straight to the point: for a project we’re involved in, we think that a > pre-fetcher mechanism would be great for a variety of use cases. There was an > attempt with this blueprint: > > https://blueprints.launchpad.net/nova/+spec/nova-image-cache-management-2 > > and a more recent one: > > https://blueprints.launchpad.net/python-novaclient/+spec/prefetch-image > > although both seems to be dead now. > > So I really want to get a feedback from the developer’s community whether (1) > such a feature makes sense in general, and (2) it may be worth the > integration of such a component in the OpenStack code. In fact, although we > can solve our problem by developing an in-house component, it would be better > to have it integrated in OpenStack, including Nova and Horizon, so I need the > feedback from the OS Guru guys J. > > > What do you think? I think it does make some sense. The disagreement in the past is about agreeing what should live inside Nova, and what should live outside Nova. For me, I am OK having an API to trigger an image prefetch on a particular host (although in many cases doing a build on that host has the same affect). I think the rest of that mechanism should probably live outside of Nova and Glance. So the question is what extra API are required to create such a tool. Thanks, johnthetubaguy __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
