openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
30,241 Commits 10 Branches 95 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
d65ca49990
Go to file
John Garbutt d65ca49990 xenapi: deal with reboots while talking to agent 
The latest version of the agent has started changing the hostname
through the official windows APIs, when resetnetwork is called. This
means a reboot might happen after resetnetwork.

A reboot happens when polling for the version. Until now we wait for the
call timeout, before fetching the new dom id. This change ensures that
if we spot a reboot, the plugin exits early rather than keeping polling
the wrong dom id.

Turns out its best to wait for the dom_id to change, before trying
to poll the agent again. Once the dom_id in xenapi has been updated,
the xenstore keys are always in place.

Trying too early leads to lots of reboot detections because we are
retrying with the old dom_id. XenServer continues to return the old
dom_id for a little while after the reboot.

Closes-Bug: #1370999

Change-Id: Id0bf5b64f2b271d162db5bbce50167ab1f665c87
2014-09-26 14:57:05 +01:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
doc Merge "Fix integrated test cases for assisted-volume-snapshots" 2014-09-21 01:47:19 +00:00
etc/nova Merge "Fix rootwrap for non openstack.org iqn's" 2014-09-12 05:34:45 +00:00
nova xenapi: deal with reboots while talking to agent 2014-09-26 14:57:05 +01:00
plugins/xenserver xenapi: deal with reboots while talking to agent 2014-09-26 14:57:05 +01:00
tools bring over pretty_tox.sh from tempest 2014-09-16 11:57:20 -04:00
.coveragerc Port Cheetah templates to Jinja2 2013-09-02 16:03:34 +02:00
.gitignore Merge "Ignore etc/nova/nova.conf.sample" 2014-05-17 21:16:47 +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 Fix tests to work with mysql+postgres concurrently 2013-10-27 09:46:45 +11:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
CONTRIBUTING.rst Fix the section name in CONTRIBUTING.rst 2014-03-28 12:12:11 +01:00
HACKING.rst mock.assert_called_once() is not a valid method 2014-09-16 16:38:49 -04:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MANIFEST.in Finish AUTHORS transition. 2012-07-05 09:11:37 -05:00
openstack-common.conf Move to oslo.db 2014-09-05 14:18:36 +02:00
pylintrc Don't warn about C0111 (No docstrings) 2011-03-16 15:28:09 -07:00
README.rst Update links in README 2014-05-07 16:06:24 -07:00
requirements.txt Updated from global requirements 2014-09-19 18:20:40 +00:00
run_tests.sh Provide a quick way to run flake8 2014-08-11 13:43:41 +01:00
setup.cfg Merge "Port image-size extension to work in v2.1/v3 framework" 2014-09-07 02:50:07 +00:00
setup.py Updated from global requirements 2014-04-30 02:43:45 +00:00
test-requirements.txt Updated from global requirements 2014-09-19 18:20:40 +00:00
tox.ini Remove unused py33 tox env 2014-09-22 13:06:56 +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