![Dan Smith](/assets/img/avatar_default.png)
This adds a --until_complete flag to the db archive command, which will attempt to run batches of max_rows continuously until archiving has completed (or stops being able to archive anything). We also take care to catch KeyboardInterrupt so that it will, if stopped, still print the verbose report at the end. Instead of printing the table on each iteration, we print some progress information and then provide a completed summary table at the end of the run. This also defaults max_rows to a sane value. The previous meaning of not providing a value was "archive a whole table in a single operation", which was useful only in the most simple of cases. Now that we have a more reasonable "do it until you are done" mechanism, we default this to 1000 rows for sanity, which also serves as the batch size for the continuous mode. Implements blueprint archive-deleted-rows-all Change-Id: I2929c2f5b3116b63a4666b258bf078bc51d4e45a
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer and OpenStack Ironic.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
API
To learn how to use Nova's API, consult the documentation available online at:
http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
http://www.openstack.org/appdev/ http://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
http://docs.openstack.org/developer/nova/feature_classification.html
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at: