ó
»EYc@sz
dd
lm
Z

dZi
e
jdddddƒ
e
jddd	dd
ƒ
e
jddeddƒ
e
jd
dgdeddƒ
e
jddgddƒ
e
jdde	ddƒ
e
jdde	ddƒ
e
jdddg
ddƒ
e
jddd+ddƒ
e
jdddddƒ
e
jd dd!dd"ƒ
e
jd#dddd$ƒ
e
jd%dd!dd&ƒ
g
d'6Z
d(„Zd)„Zd*S(,iÿÿÿÿ(
tcfgsdogpile.cache.nullt
config_prefixtdefaults
cache.oslothelps¸Prefix for building the configuration dictionary for the cache region. This should not need to be changed unless there is another dogpile.cache region with the same configuration name.texpiration_timeiXs¯Default TTL, in seconds, for any cached item in the dogpile.cache region. This applies to any cached method that doesn't have an explicit cache expiration time defined for it.tbackends
Dogpile.cache backend module. It is recommended that Memcache or Redis (dogpile.cache.redis) be used in production deployments. For eventlet-based or highly threaded servers, Memcache with pooling (oslo_cache.memcache_pool) is recommended. For low thread servers, dogpile.cache.memcached is recommended. Test environments with a single instance of the server can use the dogpile.cache.memory backend.tbackend_argumenttsecretsŸArguments supplied to the backend module. Specify this option once per argument to be passed to the dogpile.cache backend. Example format: "<argname>:<value>".tproxiess—Proxy classes to import that will affect the way the dogpile.cache backend functions. See the dogpile.cache documentation on changing-backend-behavior.tenabledsGlobal toggle for caching.tdebug_cache_backendsïExtra debugging from the cache backend (cache keys, get/set/delete/etc calls). This is only really useful if you need to see the specific cache-backend get/set/delete calls with the keys/values.  Typically this should be left set to false.tmemcache_serversslocalhost:11211ssMemcache servers in the format of "host:port". (dogpile.cache.memcache and oslo_cache.memcache_pool backends only).tmemcache_dead_retryii<s”Number of seconds memcached server is considered dead before it is tried again. (dogpile.cache.memcache and oslo_cache.memcache_pool backends only).tmemcache_socket_timeoutissTimeout in seconds for every call to a server. (dogpile.cache.memcache and oslo_cache.memcache_pool backends only).tmemcache_pool_maxsizei
shMax total number of open connections to every memcached server. (oslo_cache.memcache_pool backend only).tmemcache_pool_unused_timeouts„Number of seconds a connection to memcached is held unused in the pool before it is closed. (oslo_cache.memcache_pool backend only).t$memcache_pool_connection_get_timeoutsRNumber of seconds that an operation will wait to get a memcache client connection.tcachec
Cs=x6tD].}
x%t|
D]}|j
|d
|
ƒ


qWqWdS(Ntgroup(tFILE_OPTIONStregister_opt(tconftsectiontoption((sE/home/tvault/.virtenv/lib/python2.7/site-packages/oslo_cache/_opts.pyt	configureas



cCstt
jƒƒ
S(
sçReturn a list of oslo_config options.

    The returned list includes all oslo_config options which are registered as
    the "FILE_OPTIONS".

    Each object in the list is a two element tuple. The first element of
    each tuple is the name of the group under which the list of options in the
    second element will be registered. A group name of None corresponds to the
    [DEFAULT] group in config files.

    This function is also discoverable via the 'oslo_config.opts' entry point
    under the 'oslo_cache.config.opts' namespace.

    The purpose of this is to allow tools like the Oslo sample config file
    generator to discover the options exposed to users by this library.

    :returns: a list of (group_name, opts) tuples
    (tlistRtitems(((sE/home/tvault/.virtenv/lib/python2.7/site-packages/oslo_cache/_opts.pyt	list_optsgsNi,
(
toslo_configRt_DEFAULT_BACKENDtStrOpttIntOpttMultiStrOpttTruetListOpttBoolOpttFalseRRR(((sE/home/tvault/.virtenv/lib/python2.7/site-packages/oslo_cache/_opts.pyt<module>sF