Go to file

Tang Chen 30c6f49817 Add a REST API to trigger crash dump in an instance.

Change I9b649aafba011d537e3fe4eebef7a678ff6733e4 has added a
compute API to trigger crash dump in instance. This patch adds
the REST API to nova. It enables users to trigger crash dump in
an instance through REST API.

Change-Id: I6ed777ff637254b4b79417008f9055dd19fc7405
Implements: blueprint instance-crash-dump
Co-Authored-By: Hironori Shiina <shiina.hironori@jp.fujitsu.com>
Co-Authored-By: Tang Chen <tangchen@cn.fujitsu.com>

2016-01-20 09:42:50 +08:00

api-guide/source

Merge "api-guide: add a doc on users"

2016-01-12 15:02:03 +00:00

contrib

Merge "changed quantum to neutron in vif-openstack"

2014-03-05 10:45:05 +00:00

devstack

Merge "Remove skips for resize tests from tempest-dsvm-cells-rc"

2015-12-01 06:33:22 +00:00

doc

Add a REST API to trigger crash dump in an instance.

2016-01-20 09:42:50 +08:00

etc/nova

Add a REST API to trigger crash dump in an instance.

2016-01-20 09:42:50 +08:00

nova

Add a REST API to trigger crash dump in an instance.

2016-01-20 09:42:50 +08:00

plugins/xenserver

Fix indexing of dict.keys() in python3

2016-01-15 00:48:35 +08:00

releasenotes

Add a REST API to trigger crash dump in an instance.

2016-01-20 09:42:50 +08:00

tools

Merge "XenAPI: Fix race in rotate_xen_guest_logs"

2016-01-05 17:33:36 +00:00

.coveragerc

Change ignore-errors to ignore_errors

2015-09-21 14:34:39 +00:00

.gitignore

Merge "Add reno for release notes management"

2015-11-13 16:24:51 +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

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

CONTRIBUTING.rst

Workflow documentation is now in infra-manual

2014-12-05 03:30:37 +00:00

HACKING.rst

add hacking check for config options location

2015-11-26 19:24:19 +01: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

openstack-common.conf

Switch to the oslo_utils.fileutils

2015-07-24 14:10:44 +03:00

README.rst

Update links in README

2014-05-07 16:06:24 -07:00

requirements.txt

Updated from global requirements

2016-01-07 14:03:22 +00:00

run_tests.sh

Wrong URL reported by the run_tests.sh message

2016-01-06 10:47:15 +00:00

setup.cfg

Merge "single point of entry for sample config generation"

2016-01-11 21:50:36 +00:00

setup.py

Updated from global requirements

2015-09-17 16:41:48 +00:00

test-requirements.txt

Updated from global requirements

2015-12-23 00:35:53 +00:00

tests-py3.txt

Block flaky python34 test : vmwareapi.test_configdrive.ConfigDriveTestCase

2016-01-13 10:20:59 -05:00

tox.ini

Revert "Workaround reno reverts by accepting warnings"

2016-01-16 14:31:06 +00: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