yahoo-eng-team team mailing list archive

[OpenStack Infra <1886374@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/739423
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=ab0e5268a9c2614572659d763b3c0b6fc36dd0cf
Submitter: Zuul
Branch:    master

commit ab0e5268a9c2614572659d763b3c0b6fc36dd0cf
Author: Abhishek Kekane <akekane@xxxxxxxxxx>
Date:   Mon Jul 6 07:49:31 2020 +0000

    Improve lazy loading mechanism for multiple stores
    
    Glance has a facility lazy loading for legacy images which will be called
    on get/list api calls to add store information in image's location metadata
    based on location URL of image. Even if admin decides to change the store
    names in glance-api.conf same will also be updated in location metadata
    for all images related to that particular store. Current implementation of
    legacy image performs this operation on each get/list call as location metadata
    is not getting updated in database or it doesn't handle to perform store name
    check in glance-api.conf.
    
    Improvements done:
    1. Save updated location metadata information in database permenantly
    2. Add logic to perform lazy loading only if store information is not present
    in location metadata or store present in location metadata is not defined in
    glance's enbaled_backends configuration option.
    
    Change-Id: I789fa7adfb459e7861c90a51f418a635c0c22244
    Closes-Bug: #1886374


** Changed in: glance
       Status: In Progress => Fix Released

** Changed in: glance/ussuri
       Status: New => In Progress

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

Title:
  Improve lazy loading mechanism for multiple stores

Status in Glance:
  Fix Released
Status in Glance train series:
  New
Status in Glance ussuri series:
  In Progress

Bug description:
  Glance has a facility lazy loading for legacy images which will be
  called on get/list api calls to add store information in image's
  location metadata based on location URL of image. Even if admin
  decides to change the store names in glance-api.conf same will also be
  updated in location metadata for all images related to that particular
  store. Current implementation of legacy image performs this operation
  on each get/list call as location metadata is not getting updated in
  database or it doesn't handle to perform store name check in glance-
  api.conf

  Proposed fix for improvements:
  1. Save updated location metadata information in database permanently
  2. Add logic to perform lazy loading only if store information is not present in location metadata or store present in location metadata is not defined in glance's enbaled_backends configuration option.

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