Create a separate service for the cache manager

Registered by Flavio Percoco on 2013-03-29

**** THIS IS A WORK IN PROGRESS IDEA ****

The idea here is to have a separate service for the cache manager.

Scenario:

    1) glance-api running in a server (which doesn't have huge amounts of memory / disk) perhaps shared with other services that takes all requests for images / members.

    2) glance-cache living in a server with more resources with the cached images.

    3) Glance api gets a request for "downloading" an image and routes the client to the cached node with the cached image

This will allow the user for distributing cached images, glance-api would still handle those at a higher level and would be responsible for routing the client to the right cache server and in a bigger scenario, glance could also have some heuristics to "automatically" cache the most recent / common images.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Flavio Percoco
Direction:
Needs approval
Assignee:
None
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Hi Flavio,

In general I think these ideas of better cache management are good. However, I'm tempted to say they are out of scope for glance proper. Really, the better types of caching and efficient transfer of bulk data feel like they belong either in a protocol (like bittorrent) or in a separate bulk data transfer service. How do you feel about that answer? Let me know in irc or email b/c I might not notice updates to this whiteboard.

markwash rejected 2014-03-14

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.