Location selection strategy based on image level

Registered by Feilong Wang on 2014-02-21

User case: Based on current image location selection strategy, I would like to see the location selection strategy can be configured for specific image. Which will override the overall image location selection strategy.

Blueprint information

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

Related branches

Sprints

Whiteboard

Can you give some more information about what user need this would address? I'm trying to understand why a user would want a different selection strategy for a given image. Also, what kind of user are we talking about here? admin? deployer? cloud-user?
markwash more-info 2014-04-25

Thanks for the reviewing, Mark.
Based on current implement, the location selection strategy is static and global. That means end user can't specific which backend is the best one he preferred. For example, if the global strategy is filesystem, cloud user creates an image with 3 different locations, filesystem, swift and http. But the cloud user clearly know swift or http is providing the best performance. We don't provide the way to do that. That's what this BP want to address.
flwang 2014-4-29

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.