OpenStack Compute (Nova)
Go to file
Matt Riedemann e37279b459 Print number of rows archived per table in db archive_deleted_rows
The `nova-manage db archive_deleted_rows` command doesn't print any
results, not even how many rows were deleted, which is something the
database API returns.

The number of rows deleted also changes depending on the max_rows input
and how many rows are deleted in each table, it's a cumulative effect.

We should keep track of which tables we've deleted rows from along with
how many rows, and print that all out to the CLI console if the user
passed a --verbose option.

Implements blueprint print-table-archived-rows

Change-Id: I5c47cd5633eca056f8ae508753a41e2c1ed9e523
2015-10-16 10:23:54 -07:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
devstack Merge "Creating instance fail when inject ssh key in cells mode" 2015-09-14 22:19:04 +00:00
doc Print number of rows archived per table in db archive_deleted_rows 2015-10-16 10:23:54 -07:00
etc/nova Fix logging_sample.conf to use oslo_log formatter 2015-09-24 18:04:20 +09:00
nova Print number of rows archived per table in db archive_deleted_rows 2015-10-16 10:23:54 -07:00
plugins/xenserver Merge "Fix a few typos" 2015-09-15 11:24:36 +00:00
tools tox: make it possible to run pep8 on current patch only 2015-07-24 16:15:38 +01:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:34:39 +00:00
.gitignore Add sample config file to nova docs 2015-09-30 22:35:46 +00:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 15:07:19 -04:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.testr.conf Add tox -e functional 2014-11-12 15:31:06 -05:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst Merge "Add hacking check for eventlet.spawn()" 2015-10-08 03:43:00 +00:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Add a maintainers file 2015-05-23 03:22:07 +10:00
README.rst Update links in README 2014-05-07 16:06:24 -07:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bandit.yaml Add bandit for security static analysis testing 2015-07-02 09:17:48 -07:00
openstack-common.conf Switch to the oslo_utils.fileutils 2015-07-24 14:10:44 +03:00
requirements.txt Updated from global requirements 2015-10-14 09:32:07 +00:00
run_tests.sh Fix likely undesired use of redirection 2015-02-02 16:26:31 +01:00
setup.cfg Open Mitaka development 2015-09-22 15:11:02 +01:00
setup.py Updated from global requirements 2015-09-17 16:41:48 +00:00
test-requirements.txt Updated from global requirements 2015-10-13 11:03:34 +00:00
tests-py3.txt Replaces contextlib.nested with test.nested 2015-10-08 23:13:30 +03:00
tox.ini Use os-testr for py34 tox target 2015-09-30 19:53:53 -04:00

README.rst

OpenStack Nova README

OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.

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.

Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.

To keep updated with new developments in the OpenStack project follow @openstack on Twitter.

To learn how to deploy OpenStack Nova, consult the documentation available online at:

http://docs.openstack.org

For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:

https://wiki.openstack.org/wiki/HypervisorSupportMatrix

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:

http://bugs.launchpad.net/nova

Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:

https://git.openstack.org/cgit/openstack/nova

Developers should also join the discussion on the mailing list, at:

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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:

http://docs.openstack.org/developer/nova/

For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.

-- End of broadcast