Pike Series Release Notes



Currently Freezer provides basic features to execute Cinder volumes backup. The current approach present significant challenges, due mainly to the difficulty of downloading Cinder Volumes without passing through Glance. This can be an issue for time and scalability reasons, (i.e. volumes of few hundreds GB size, potential error probability increase, as more services are part of the process, unailability of cinder-backup).

Currently, freezer can only store backup data to swift compatible object storage (except local and ssh), so we should increase support for other storage driver. S3 compatible object storage is a valid choice, which is used by many individuals and companies in the public or private clouds.

Currently, when using ‘freezer-agent –action backup –engine nova –nova-inst-id xxx –mode nova –no-incremental true’ to backup instance that boot from volume or snapshot, it gives us the result of successful backup. But when we restore the nova instance from the backup data and launch the restored instance, it will fail with ‘no boot device error’ message. This can be an issue.

New Features

  • Added new backup engine called ‘os-brick’ which allows to backup and restore the content of cinder volumes attaching it directly to localhost using functionality of os-brick library.

  • Added new storage type called ‘s3’ which allows to store the backup data to S3 compatible object storage and restore from it with using botocore library.

Known Issues

  • There are could be a read/write file permisson issues if freezer-agent don’t have appropriate right to readwrite files to mounted FS.

Bug Fixes

  • With the above issue, freezer can not support the backup and restore of instance that boot from volume or snapshot correctly. With this fix, when using backup, freezer will create an image from the volume, and then store the image data to storage media. After this fix, users can backup and restore the nova instance no matter what type of the instance is.