← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1598282] [NEW] location strategy config shouldn't be ristricted

 

Public bug reported:

The idea of location strategy is allowing cloud provider can add a
customized location strategy. That said, no code change should be
involved. But seems it's not true for this case.

See
https://github.com/openstack/glance/blob/master/glance/common/location_strategy/__init__.py#L26

** Affects: glance
     Importance: Undecided
     Assignee: Fei Long Wang (flwang)
         Status: New

** Description changed:

  The idea of location strategy is allowing cloud provider can add a
  customized location strategy. That said, no code change should be
- involved. As Brian pointed out, seems it's not true for this case.
+ involved. But seems it's not true for this case.
  
- 
- See https://github.com/openstack/glance/blob/master/glance/common/location_strategy/__init__.py#L26
+ See
+ https://github.com/openstack/glance/blob/master/glance/common/location_strategy/__init__.py#L26

** Changed in: glance
     Assignee: (unassigned) => Fei Long Wang (flwang)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1598282

Title:
  location strategy config shouldn't be ristricted

Status in Glance:
  New

Bug description:
  The idea of location strategy is allowing cloud provider can add a
  customized location strategy. That said, no code change should be
  involved. But seems it's not true for this case.

  See
  https://github.com/openstack/glance/blob/master/glance/common/location_strategy/__init__.py#L26

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1598282/+subscriptions


Follow ups