Bug 1041762

Summary: [RFE][glance]: Create a separate service for the cache manager
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/glance/+spec/glance-cache-service
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_discussion
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:34:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 19:12:55 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/glance-cache-service.

Description:

**** 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.

Specification URL (additional information):

None