Client-side cache of server data

Registered by Dean Troyer on 2014-09-06

Many operations can be sped up with careful client-side caching of resources that would otherwise require additional server queries.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Medium
Drafter:
Dean Troyer
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Ideally the cache is portable across applications and implementation languages.

The cache must have:

* location: XDG_CACHE_HOME/openstack or ~/.cache/openstack on most distros defaults
* further subdivide using API name? ~/.cache/openstack/compute/xxx
* maintain individual caches for unique endpoint/domain/username combinations (similar to what nova and cinder CLIs do)
* defined TTL rules for expiring data
* a set of built-in commands to manage the cache, i.e. lookup, expire

[Cache portions of https://blueprints.launchpad.net/python-openstackclient/+spec/configuration-file were incorporated here]

(?)

Work Items

Work items:
define cache layout and what get cached: TODO
Implement basic cache: TODO

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.