Feature #9161
openCache warmup and ejection
0%
Description
Initial access of an object in a high performance cache tier can have high latency as the object is fetched from the backing tier.
If a mechanism can be created to allow a hint to be given about the likely access of a set of objects (eg a golden VM image) to RADOS so that it can pre-populate the cache tier, this can the be exposed out through OpenStack Cinder.
Updated by paul luse over 9 years ago
I'm not familiar with the process here, looks like this was opened 17 days ago though -- is there something else that needs to be done to get this reviewed/dispositioned?
Updated by Greg Farnum over 9 years ago
This is a feature request ticket; the code implementing it doesn't exist yet. ;)
Updated by paul luse over 9 years ago
Thanks Greg, that part is clear enough :) My question is about the life cycle of a feature request - when dopes this get reviewed and by whom? Is there something else that the requester and/or interested parties need to do to have this feature request dispositioned?
Updated by Greg Farnum over 9 years ago
There are (ir)regularly scheduled backlog audits with product and engineering that go through the new tickets and prioritize them. Since Neil created this one I'm sure he'll be pushing it appropriately.
Updated by Anonymous over 9 years ago
I started to work on this.
Is there a change it could go into Hammer release?
Updated by Anonymous over 9 years ago
I started to work on this.
Is there a chance it could go into Hammer release?