OpenStack Compute (Nova)
Go to file
Javeme c824982e6a raise exception ComputeHostNotFound if host is not found
When performing a live migration,I passed a wrong host parameter,
and then I got a wrong result like this:
"Compute service of host-1 is unavailable at this time".
I thought the compute service stopped, but the fact was I passed
a host id instead of a host name,therefore it could not find the host.

In order to distinguish the error "host not found" from the error
"service not available", I think we should raise a different exception
ComputeHostNotFound instead of ComputeServiceUnavailable.

This patch we will return more accurate error msg for live migration.

Closes-Bug: #1538837
Change-Id: I6ad377147070f85b9b1d5a1d1be459e890e02bcc
2016-05-23 17:05:30 +08:00
api-guide/source [doc] fix 5 typos 2016-04-28 20:40:18 +09:00
api-ref/source Merge "api-ref, os-fping.inc" 2016-05-23 08:20:10 +00:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
devstack Add RC file for excluding tempest tests for LVM job 2016-05-17 10:25:45 -04:00
doc Hyper-V: Implement nova rescue 2016-05-21 02:15:04 +03:00
etc/nova Merge "Config options: centralize cache options" 2016-05-17 20:00:58 +00:00
nova raise exception ComputeHostNotFound if host is not found 2016-05-23 17:05:30 +08:00
plugins/xenserver Merge "plugins/xenserver: Resolve PEP8 issues" 2016-03-10 14:27:09 +00:00
releasenotes Add online migration to move keypairs from main to API database 2016-05-19 11:59:14 -07:00
tools Config options: Centralize compute options 2016-04-20 19:00:25 +00:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:34:39 +00:00
.gitignore Add api-ref/build/* to .gitignore 2016-04-06 12:51:27 -04: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 a hacking check for test method closures" 2016-04-04 11:08:43 +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
requirements.txt Updated from global requirements 2016-05-20 06:02:34 +00:00
run_tests.sh Add description on how to run ./run_test.sh -8 2016-01-11 13:17:04 +00:00
setup.cfg Move config options from nova/api directory (5) 2016-05-17 13:07:47 +00:00
setup.py Updated from global requirements 2015-09-17 16:41:48 +00:00
test-requirements.txt migrate to os-api-ref 2016-05-16 08:10:14 -04:00
tests-py3.txt Rename Raw backend to Flat 2016-05-17 10:51:38 +01:00
tox.ini Final warnings removals for api-ref 2016-04-20 11:25:30 -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