Skip to main content

Turn a standby into volumes

POST 

/v1/standbys/:id/promote

Creates volumes in the standby's project from its applied_snap, boot disk first, ready to attach or boot from. They hold applied_point_id exactly, whatever state the standby is in: a standby that is updating or whose last update failed still promotes to the backup it last finished. No server is created. Each volume is cloned, registered with the block storage service and handed to the project through a delegation the caller's token grants; every volume is cloned in full in the background. Either every disk becomes a volume or none does. The identity service delegates only roles the caller holds in the standby's project itself: an admin role on the system or on another project does not count, so an operator account that promotes standbys needs a role, such as member, in every project whose standbys it promotes.

Any member of the project the token is scoped to.

Request​

Responses​

OK