Backup Force Delete API¶

Problem description¶

Currently there are volume force-delete and snapshot force-delete functions, but there is not a force-delete function for backups. Force-delete for backups would be beneficial when backup-create fails and the backup status is stuck in ‘creating’. This situation occurs when database just went down after backup volume and metadata and update the volume’s status to ‘available’, leaving the backup’s status to be ‘creating’ without having methods to deal with through API, because backup-delete api could only delete backup item in status of ‘available’ and ‘error’.

Use Cases¶

If backup create successfully in object storage, but become stuck in update backup’s status because database just went down. Then use force-delete API, we could directly delete the backup item(include all the stuff in storage backend and db entry info) without manually change the backup’s status in db to error or restart cinder-backup and call backup-delete function, which is very useful for administrators.

Proposed change¶

A new API function and corresponding cinder command will be added to force delete backups.

The proposal is to provide a method for administrator to quickly delete the backup item that is not in the status of ‘available’ or ‘error’.

• It’s an admin-only operation.

POST /v2/{tenant_id}/backups/{id}/action

{
    "os-force_delete": {}
}

Implementation¶

Dependencies¶

None

Testing¶

Need to test the force delete with an in-progress backup and ensure that it deletes successfully and cleans up correctly.

Documentation Impact¶

The cinder client documentation will need to be updated to reflect the new command.

http://docs.openstack.org/admin-guide/blockstorage-manage-volumes.html

The cinder API documentation will need to be updated to reflect the REST API changes.

References¶

None