Mistral can schedule the executions and then a workflow to do the server image create.
The CERN implementation of this is described at http://openstack-in-production.blogspot.com/2017/08/scheduled-snapshots.html with the implementation at https://gitlab.cern.ch/cloud-infrastructure/mistral-workflows. It is pretty generic but I don't know if anyone has tried to run it elsewhere. A few features - Schedule can be chosen - Logs visible in Horizon - Option to shutdown instances before and restart after - Mails can be sent on success and/or failure - Rotation of backups to keep a maximum number of copies There are equivalent restore and clone functions in the workflow also. Tim -----Original Message----- From: Jay Pipes <jaypi...@gmail.com> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Friday, 16 November 2018 at 20:58 To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [nova] Can we deprecate the server backup API please? The server backup API was added 8 years ago. It has Nova basically implementing a poor-man's cron for some unknown reason (probably because the original RAX Cloud Servers API had some similar or identical functionality, who knows...). Can we deprecate this functionality please? It's confusing for end users to have an `openstack server image create` and `openstack server backup create` command where the latter does virtually the same thing as the former only sets up some whacky cron-like thing and deletes images after some number of rotations. If a cloud provider wants to offer some backup thing as a service, they could implement this functionality separately IMHO, store the user's requested cronjob state in their own system (or in glance which is kind of how the existing Nova createBackup functionality works), and run a simple cronjob executor that ran `openstack server image create` and `openstack image delete` as needed. This is a perfect example of an API that should never have been added to the Compute API, in my opinion, and removing it would be a step in the right direction if we're going to get serious about cleaning the Compute API up. Thoughts? -jay __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
