x/gantt

Go to file

Johannes Erdfelt 8ac7846ee8 Make XenAPI agent configuration synchronous

Fixes bug 897887

Much of the XenAPI agent configuration happens asynchronously from the
spawn process. This allows the instance to go ACTIVE state earlier and
leaves the possibility of a race with delete open. This makes the
steps synchronous, ensuring the process only goes to ACTIVE after the
configuration is done.

Change-Id: I294b595128979e153c797d9e610b66bc76f47666

2011-12-15 15:22:31 +00:00

bin

Follow-on to I665f402f to convert rxtx_quota to rxtx_factor in

2011-12-13 15:23:31 -06:00

doc

Rename .nova-venv to .venv.

2011-12-08 15:17:51 -08:00

nova

Make XenAPI agent configuration synchronous

2011-12-15 15:22:31 +00:00

Imported Translations from Launchpad

2011-12-11 23:02:45 +00:00

.gitignore

Rename .nova-venv to .venv.

2011-12-08 15:17:51 -08:00

.gitreview

Add .gitreview config file for gerrit.

2011-10-24 15:07:19 -04:00

.mailmap

removing TODO as we support Windows+XenServer and have no plans to support quiesce or VSS at the moment

2011-12-08 18:59:52 -06:00

Authors

Merge "Added support for creating nova volume snapshots using OS API."

2011-12-14 09:15:10 +00:00

HACKING.rst

First steps towards consolidating testing infrastructure

2011-12-06 09:37:57 -08:00

LICENSE

initial commit

2010-05-27 23:05:26 -07:00

MANIFEST.in

Sanitize EC2 manifests and image tarballs

2011-12-13 16:00:41 +01:00

pylintrc

Don't warn about C0111 (No docstrings)

2011-03-16 15:28:09 -07:00

README.rst

Converted README to RST format.

2011-11-20 18:54:08 -05:00

run_tests.sh

Making pep8 output less verbose.

2011-12-14 20:59:33 -06:00

setup.cfg

Remove remnants of babel i18n infrastructure

2011-12-06 11:31:02 +00:00

setup.py

A more secure root-wrapper alternative

2011-12-07 15:10:04 +01:00

README.rst

The Choose Your Own Adventure README for Nova

You have come across a cloud computing fabric controller. It has identified itself as "Nova." It is apparent that it maintains compatibility with the popular Amazon EC2 and S3 APIs.

To monitor it from a distance: follow @openstack on twitter.

To tame it for use in your own cloud: read http://docs.openstack.org

To study its anatomy: read http://nova.openstack.org

To dissect it in detail: visit http://github.com/openstack/nova

To taunt it with its weaknesses: use http://bugs.launchpad.net/nova

To watch it: http://jenkins.openstack.org

To hack at it: read HACKING

To cry over its pylint problems: http://jenkins.openstack.org/job/nova-pylint/violations