Go to file
Hervé Beraud 83de99cdad Refactoring functional tests based on standard usages
Refactoring the functional tests by using the standard usages [1]
and best pratices available in the oslo.cache documentation.

The main goal of these changes is to help us to
test oslo.cache in the way that quite close to real life usages.

To test new backend now we just need to create the associated test class
dedicated to pass backend's config fixture.

These changes allow to test a new backend by:
- passing the right config to backend by using dedicated config fixture;
- adding the zuul job dedicated to manage functional tests
  against etcd backend;
- adding the right server backend to bindep.

[1] https://docs.openstack.org/oslo.cache/latest/user/usage.html

Change-Id: Iaf196d2d93225afa54e324fb830761049059926e
2020-05-28 14:34:47 +02:00
2020-05-09 14:42:28 +02:00
2020-05-14 14:45:12 +02:00
2019-04-19 19:29:50 +00:00
2020-05-14 14:45:12 +02:00
2020-05-14 14:45:12 +02:00
2017-04-08 22:33:53 +08:00
2017-07-11 21:51:41 +08:00
2020-05-09 14:26:35 +02:00
2020-05-09 12:32:55 +00:00
2020-02-10 18:34:34 +01:00

Team and repository tags

image

oslo.cache

Latest Version

Downloads

oslo.cache aims to provide a generic caching mechanism for OpenStack projects by wrapping the dogpile.cache library. The dogpile.cache library provides support memoization, key value storage and interfaces to common caching backends such as Memcached.

Description
An oslo.config enabled dogpile.cache.
Readme 6.2 MiB
Languages
Python 100%