Difference between revisions of "FreezerRoadmap"
(Created page with "==Architecture== * Spliting the freezer-scheduler into: ** '''freezer-scheduler''': daemon only that schedules backup/restore jobs using the freezer-agent. ** '''python-fre...") |
|||
| Line 1: | Line 1: | ||
| + | ==Releases== | ||
| + | We are still catching up with OpenStack's release cycle: | ||
| + | |||
| + | * Kilo will be tagged on 13/11/2015 | ||
| + | * Liberty will be tagged on 18/12/2015 latest | ||
| + | * Work on Mitaka will start after that date | ||
| + | |||
==Architecture== | ==Architecture== | ||
* Spliting the freezer-scheduler into: | * Spliting the freezer-scheduler into: | ||
Revision as of 17:03, 12 November 2015
Contents
Releases
We are still catching up with OpenStack's release cycle:
- Kilo will be tagged on 13/11/2015
- Liberty will be tagged on 18/12/2015 latest
- Work on Mitaka will start after that date
Architecture
- Spliting the freezer-scheduler into:
- freezer-scheduler: daemon only that schedules backup/restore jobs using the freezer-agent.
- python-freezerclient: api client used for job management.
Openstack Integration
- freezer-api should use oslo.logging and oslo.config
- freezer-scheduler should use oslo.logging and oslo.config
- freezer-agent should use oslo.logging and oslo.config
- python-freezerclient should use cliff
- Move to Tempest for integration test
- Oslo.policy integration
- Bandit integration
Freezer features
- Support for new types of application-aware backup:
- Pluggable backup mode abstraction layer
- Oracle Database backup
- Postresql Database backup
- Redis Database backup
- Elasticsearch Database backup
- Support for new backend to store backup:
- Pluggable storage backend abstraction layer
- Tape backend
- Job session related:
- Sessions names
- Time synchronisation improvement
- Synchronized backup across multiple technologies
- Consistency check after a restore
- Support for block based incremental
- Parallel backup upload to multiple backend fully supported (engine already merged)
- Support for properties that span across multiple actions on a json job definition
- Data deduplication
- Define the metadata information across any type of backups or on any case
- Backup listing from python-freezerclient
- Showing the content of a backup
Refactoring
- Logging audit and improvement (what is logged and with which log level)
- Name collision prevention:
- freezer-scheduler client_id
- freezer-agent backup_name
Goals continuously delivered
- More and more features available though the Horizon Web UI
- Improve documentation
- Improve test coverage
- Improve usability
- Improve security
Miscellaneous
- Logo
