OpenStack Compute (Nova)
Go to file
Chen Hanxiao 13418faa17 libvirt: properly decode error message from qemu guest agent
Some of error messages from qemu-guest-agent is
localized encoding.
We may get GB2312(Chinese charactors) from qga's error message
from a Chinese version of Windows.

nova didn't cover this senario, we may get errors like:
    UnicodeDecodeError: 'ascii' codec can't decode byte 0xe6
    in position 138: ordinal not in range(128)

This patch will fix this issue by exception_to_unicode

Closes-bug: #1727643

Change-Id: I3b8bfaec8af0e9b4859dcfe7e35fc5bb26c208dc
Signed-off-by: Chen Hanxiao <chenhx@certusnet.com.cn>
2017-10-28 10:10:41 +08:00
api-guide/source Update "SHUTOFF" description in API guide 2017-10-11 16:33:47 -04:00
api-ref/source Merge "api-ref: fix server status values in GET /servers docs" 2017-10-18 10:54:57 +00:00
contrib trivial: Remove "vif" script 2017-08-07 16:00:10 +01:00
devstack Blacklist test_extend_attached_volume from cells v1 job 2017-10-05 17:31:05 -04:00
doc Move the idmapshift binary into privsep. 2017-10-24 18:50:23 +11:00
etc/nova Move loopback setup and removal to privsep. 2017-10-24 18:50:33 +11:00
gate move gate hooks to gate/ 2017-01-04 11:05:16 +00:00
nova libvirt: properly decode error message from qemu guest agent 2017-10-28 10:10:41 +08:00
placement-api-ref/source Merge "api-ref: note the microversions for GET /resource_providers query params" 2017-10-11 11:19:03 +00:00
releasenotes Merge "xenapi: cached images should be cleaned up by time" 2017-10-24 18:30:32 +00:00
tools xenapi: cached images should be cleaned up by time 2017-10-23 16:29:16 +00:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Fix test runner config issues with os-testr 1.0.0 2017-09-13 17:11:57 -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
.stestr.conf Fix test runner config issues with os-testr 1.0.0 2017-09-13 17:11:57 -04:00
.testr.conf [placement] Adjust the name of the gabbi tests 2016-09-20 19:14:44 +00:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst Enable global hacking checks and removed local checks 2017-02-10 15:09:37 +01:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Fix broken URLs 2017-09-07 15:42:31 +02:00
README.rst doc: Rework README to reflect new doc URLs 2017-08-03 16:06:08 -04:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt List system dependencies for running common tests 2016-08-24 06:49:32 +02:00
requirements.txt Updated from global requirements 2017-10-11 05:50:00 +00:00
setup.cfg Move the idmapshift binary into privsep. 2017-10-24 18:50:23 +11:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Merge "cleanup test-requirements" 2017-09-26 17:44:17 +00:00
tests-functional-py3.txt Remove invalid URL in gabbi tests 2017-01-17 21:10:45 +00:00
tests-py3.txt Skip unit tests for SSL + py3 2017-03-02 14:30:16 +08:00
tox.ini Make setenv consistent for unit, func, and api-samples 2017-10-05 21:45:46 +00:00

README.rst

Team and repository tags

image

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, OpenStack Ironic and PowerVM.

Use the following resources to learn more.

API

To learn how to use Nova's API, consult the documentation available online at:

For more information on OpenStack APIs, SDKs and CLIs in general, refer to:

Operators

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

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:

Other Information

During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: