Difference between revisions of "Backup-schedule"
(talk) |
(talk) |
||
| Line 33: | Line 33: | ||
** For each images, if the creation date plus the time defines in the property 'backup_type' is older than current date, we make another backup of the server. | ** For each images, if the creation date plus the time defines in the property 'backup_type' is older than current date, we make another backup of the server. | ||
* If the administrator wants to stop the periodic backup of a server, he just need to delete all backup images of this server in the image library. | * If the administrator wants to stop the periodic backup of a server, he just need to delete all backup images of this server in the image library. | ||
| + | |||
| + | == Related resources == | ||
| + | |||
| + | * https://code.launchpad.net/~rconradharris/nova/backup_schedule_extension/+merge/74665 | ||
| + | * https://review.openstack.org/#/c/840/7/nova/api/openstack/backup_schedules.py | ||
| + | * http://docs.rackspacecloud.com/openstack-extensions/compute/rax-bak/content/ch02.html | ||
| + | * Another blueprint: https://blueprints.launchpad.net/nova/+spec/image-backup-scheduler | ||
== Design == | == Design == | ||
Revision as of 14:15, 24 October 2012
- Launchpad Entry: NovaSpec:backup-schedule
- Created: 24 oct 2012
- Contributors: Édouard Thuleau
Schedule Snapshote
<<TableOfContents()>>
Summary
In addition to creating image backup on demand, you may also want to schedule periodic image backup. These periodic image backups are triggered automatically based on backup schedule established.
Release Note
The administrator wants to add an image periodic backup mechanism for a server.
Rationale
The OpenStack compute API proposes 'backup server' in the extension 'admin_action'. This action permits to defines a backup type (daily or weekly) and the persistence of the backup.
The schedule backup will permit administrator to automate this backup periodically (daily or weekly).
User stories
Administrator wants to backup periodically (daily or weekly) the image of an instance server and defines the persistence of the backuped images.
Assumptions
- Administrator creates a periodic backup for a server through the API extension 'admin_action/createBackup'
- The compute manager creates a snapshot of the image server and upload it to Glance with 'image_type' set to 'backup'.
- A periodic task of nova-compute or a new nova service 'nova-schedule-backup' list images with property 'image_type' equal to 'backup' from Glance.
- For each images, if the creation date plus the time defines in the property 'backup_type' is older than current date, we make another backup of the server.
- If the administrator wants to stop the periodic backup of a server, he just need to delete all backup images of this server in the image library.
Related resources
- https://code.launchpad.net/~rconradharris/nova/backup_schedule_extension/+merge/74665
- https://review.openstack.org/#/c/840/7/nova/api/openstack/backup_schedules.py
- http://docs.rackspacecloud.com/openstack-extensions/compute/rax-bak/content/ch02.html
- Another blueprint: https://blueprints.launchpad.net/nova/+spec/image-backup-scheduler
Design
Implementation
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
UI Changes
Should cover changes required to the UI, or specific UI that is required to implement this
Code Changes
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Migration
Include:
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
Test/Demo Plan
This need not be added or completed until the specification is nearing beta.
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
