Actions
Feature #26918
closed
Support redis as a caching backend
Difficulty:
Triaged:
No
Description
As a user I want to use redis as a caching backend for Foreman.
Updated by The Foreman Bot over 5 years ago
- Status changed from New to Ready For Testing
- Assignee set to Timo Goebel
- Pull request https://github.com/theforeman/foreman/pull/6811 added
Updated by Lukas Zapletal over 5 years ago
- Subject changed from support redis as a caching backend to Support redis as a caching backend
The context is we provide foreman_memcache but since Pulp V3 relies on Redis, it would be nice to actually provide session cache in Foreman Core on Redis.
I am interested in this since I would like to explore more options with Redis:
- foreman hooks queuing
- volatile facts store (?)
Updated by Ohad Levy over 5 years ago
I would also be interested to add support for websockets events to avoid api polling (e.g. for notifications) basedon redis events.
Updated by Lukas Zapletal over 5 years ago
- Related to Feature #26923: Cache for host's fact_hash added
Updated by Timo Goebel over 5 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset fab71a617b35618dae841760059c70fdbdd0a6ad.
Updated by The Foreman Bot over 5 years ago
- Pull request https://github.com/theforeman/foreman/pull/6836 added
Actions