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...") |
Memo Garcia (talk | contribs) m (→Freezer features) |
||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | ==Releases== | ||
| + | As numerous companies are still running Kilo based OpenStacks, we believe Freezer needs support from that version onward. | ||
| + | For that reason 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: [mitaka] |
** '''freezer-scheduler''': daemon only that schedules backup/restore jobs using the freezer-agent. | ** '''freezer-scheduler''': daemon only that schedules backup/restore jobs using the freezer-agent. | ||
** '''python-freezerclient''': api client used for job management. | ** '''python-freezerclient''': api client used for job management. | ||
| Line 6: | Line 14: | ||
==Openstack Integration== | ==Openstack Integration== | ||
| − | * freezer-api should use oslo.logging and oslo.config | + | * freezer-api should use oslo.logging and oslo.config [liberty] |
| − | * freezer-scheduler should use oslo.logging and oslo.config | + | * freezer-scheduler should use oslo.logging and oslo.config [mitaka] |
| − | * freezer-agent should use oslo.logging and oslo.config | + | * freezer-agent should use oslo.logging and oslo.config [mitaka] |
| − | * python-freezerclient should use cliff | + | * python-freezerclient should use cliff [mitaka] |
| − | * Move to Tempest for integration test | + | * Move to Tempest for integration test [mitaka] |
| − | * Oslo.policy integration | + | * Oslo.policy integration |
* Bandit integration | * Bandit integration | ||
| Line 22: | Line 30: | ||
** Redis Database backup | ** Redis Database backup | ||
** Elasticsearch Database backup | ** Elasticsearch Database backup | ||
| + | * Support for SSL connections | ||
*Support for new backend to store backup: | *Support for new backend to store backup: | ||
| Line 33: | Line 42: | ||
* Consistency check after a restore | * Consistency check after a restore | ||
| − | * Support for block based incremental | + | * Support for block based incremental [liberty] |
| − | * Parallel backup upload to multiple backend fully supported (engine already merged) | + | * Parallel backup upload to multiple backend fully supported (engine already merged) [liberty] |
| − | * Support for properties that span across multiple actions on a json job definition | + | * Support for properties that span across multiple actions on a json job definition [liberty] |
* Data deduplication | * Data deduplication | ||
* Define the metadata information across any type of backups or on any case | * Define the metadata information across any type of backups or on any case | ||
| − | * Backup listing from python-freezerclient | + | * Backup listing from python-freezerclient [liberty] |
* Showing the content of a backup | * Showing the content of a backup | ||
| − | |||
| − | |||
==Refactoring== | ==Refactoring== | ||
| − | * Logging audit and improvement (what is logged and with which log level) | + | * Logging audit and improvement (what is logged and with which log level) [liberty] |
* Name collision prevention: | * Name collision prevention: | ||
| − | ** freezer-scheduler client_id | + | ** freezer-scheduler client_id [liberty] |
** freezer-agent backup_name | ** freezer-agent backup_name | ||
Latest revision as of 11:33, 18 January 2016
Contents
Releases
As numerous companies are still running Kilo based OpenStacks, we believe Freezer needs support from that version onward. For that reason 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: [mitaka]
- 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 [liberty]
- freezer-scheduler should use oslo.logging and oslo.config [mitaka]
- freezer-agent should use oslo.logging and oslo.config [mitaka]
- python-freezerclient should use cliff [mitaka]
- Move to Tempest for integration test [mitaka]
- 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 SSL connections
- 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 [liberty]
- Parallel backup upload to multiple backend fully supported (engine already merged) [liberty]
- Support for properties that span across multiple actions on a json job definition [liberty]
- Data deduplication
- Define the metadata information across any type of backups or on any case
- Backup listing from python-freezerclient [liberty]
- Showing the content of a backup
Refactoring
- Logging audit and improvement (what is logged and with which log level) [liberty]
- Name collision prevention:
- freezer-scheduler client_id [liberty]
- 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
