c1a2f49c11
Wrong usage of "a" in the mesages: "lookup the instance after a instance_destroy_at_top hits" "returns the PCI address of a an device" "will result in a additional lookup to glance for said attr" "This will ensure that a image is not deleted during the spawn" "Lock to ensure that the spawn will not try and access a image" "cleanup the _events_delayed dictionary when a event" "it will raise a exception.NovaException" "we need to allocate a ephemeral disk if required" "this may be a endless loop, so check the id of" Should be: "lookup the instance after an instance_destroy_at_top hits" "returns the PCI address of a device" "will result in an additional lookup to glance for said attr" "This will ensure that an image is not deleted during the spawn" "Lock to ensure that the spawn will not try and access an image" "cleanup the _events_delayed dictionary when an event" "it will raise an exception.NovaException" "we need to allocate an ephemeral disk if required" "this may be an endless loop, so check the id of" Totally 10 occasions in Nova base code. Change-Id: I5d5d2d08ea2dbeba519adba73139061702233f7a
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:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
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 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:
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:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast