Improvevment of accessing to Glance API server

Registered by Noboru Arai on 2014-01-07

The goal of this blueprint is effective image data transfer in the case of a large scale deployment.

Nova can access to multiple Glance API Severs defined by "glance_api_servers"option, and the order of access is random.

In this blueprint, we would like to propose to change the order as follow:
 - Glance API Servers are categorized into two groups("Primary" and "Secondary").
 - Firstly, Nova tries to access Glance API Servers of "Primary" randomly.
 - If Nova failed to access all Glance API Servers of "Primary", Nova tries to access Glance API
   Servers of "Secondary" randomly.

The benefits will be the followings:
 - Nova can preferentially access Glance API Servers which is more "near" in a viewpoint of network.
 - Data transfer between different network address is reduced.
   (if network is divided into multiple network address)

Blueprint information

Status:
Started
Approver:
Russell Bryant
Priority:
Undefined
Drafter:
Noboru Arai
Direction:
Needs approval
Assignee:
Noboru Arai
Definition:
Drafting
Series goal:
None
Implementation:
Needs Code Review
Milestone target:
None
Started by
Noboru Arai on 2014-01-09

Related branches

Sprints

Whiteboard

This bluprint is started a thread on http://lists.openstack.org/pipermail/openstack-dev/2014-February/026122.html

Gerrit topic: https://review.openstack.org/#q,topic:bp/improvement-of-accessing-to-glance,n,z

Addressed by: https://review.openstack.org/65623
    Improvement of accessing to Glance API server

This is probably something we should discuss on the openstack-dev mailing list. I'd really rather see enhancements to the service catalog and Nova's usage of the service catalog. If you start a thread on the mailing list, please include a link to the message from the list archives on the blueprint whiteboard. Thanks! --russellb

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

Following is the wiki of additional material. Please see this.
https://wiki.openstack.org/wiki/ImprovementOfAccessingToGlanceAPIServer

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguyThis bluprint is started a thread on http://lists.openstack.org/pipermail/openstack-dev/2014-February/026122.html

Gerrit topic: https://review.openstack.org/#q,topic:bp/improvement-of-accessing-to-glance,n,z

Addressed by: https://review.openstack.org/65623
    Improvement of accessing to Glance API server

This is probably something we should discuss on the openstack-dev mailing list. I'd really rather see enhancements to the service catalog and Nova's usage of the service catalog. If you start a thread on the mailing list, please include a link to the message from the list archives on the blueprint whiteboard. Thanks! --russellb

deferred from icehouse-3 to "next": http://lists.openstack.org/pipermail/openstack-dev/2014-February/026335.html

Following is the wiki of additional material. Please see this.
https://wiki.openstack.org/wiki/ImprovementOfAccessingToGlanceAPIServer

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy

Marking this blueprint as definition: Drafting. If you are still working on this, please re-submit via nova-specs. If not, please mark as obsolete, and add a quick comment to describe why. --johnthetubaguy (20th April 2014)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.