Bug 1302813

Summary: backport the metadata_cache_expiration config option to avoid harcoded value of 15s
Product: Red Hat OpenStack Reporter: Sven Anderson <svanders>
Component: openstack-novaAssignee: Sven Anderson <svanders>
Status: CLOSED DUPLICATE QA Contact: nlevinki <nlevinki>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.0 (RHEL 7)CC: berrange, dasmith, dcadzow, eglynn, kchamart, ndipanov, nlevinki, sbauza, sferdjao, sgordon, vromanso, yeylon
Target Milestone: ---Keywords: FeatureBackport, ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1302401 Environment:
Last Closed: 2016-02-01 13:48:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1302401    
Bug Blocks: 1302811    

Description Sven Anderson 2016-01-28 16:54:14 UTC 
+++ This bug was initially created as a clone of Bug #1302401 +++

The metadata cache expiration timeout was hardcoded to 15 seconds in versions older than kilo (OSP7).

In kilo a new configuration option was added:

  'metadata_cache_expiration',

  Time in seconds to cache metadata; 0 to disable
  metadata caching entirely (not recommended). Increasing
  this should improve response times of the metadata API
  when under heavy load. Higher values may increase memory
  usage and result in longer times for host metadata
  changes to take effect.

introduced in:

  https://review.openstack.org/159264

This config option should be backported to OSP5 in order to provide the same flexibility and avoid premature cache expiration in cases where the metadata is highly static.

--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-01-27 13:30:20 EST ---

Since this issue was entered in bugzilla without a release flag set, rhos-8.0? has been automatically added to ensure that it is properly evaluated for this release.
Comment 1 Sven Anderson 2016-02-01 13:48:33 UTC 

*** This bug has been marked as a duplicate of bug 1302812 ***