OpenStack Compute (Nova)
Go to file
Dan Smith 277c07b605 Make virt drivers use a consistent hostname
Right now, the virt drivers will happily return the hostname
of a system, even if it has changed since the compute service has
started. The problem with this is that DNS issues can cause the
service to constantly delete and re-create itself in the database
leading to flaky scheduling without the operator knowing.

This patch makes them cache the hostname at the first call, and
log a visible error message if the hostname changes during the
lifetime of the process so that the admin can see what is
going on.

NOTE: This excludes hyperv and vmwareapi until further study of
if this is appropriate to do for those drivers as well, as they
can manage multiple systems behind a single compute host.

Closes-bug: 1224982
Change-Id: I4ef64f9715ff117f50120846d8b43ee7183a0b42
2013-09-17 06:39:02 -07:00
contrib Enable N302: Import modules only 2013-01-25 12:11:54 -05:00
doc Merge "Fix v3 swap volume with wrong signature" 2013-09-12 15:07:57 +00:00
etc/nova Merge "Add encryption support for volumes to libvirt" 2013-09-11 19:19:58 +00:00
nova Make virt drivers use a consistent hostname 2013-09-17 06:39:02 -07:00
plugins/xenserver Merge "Adds Instance UUID to rsync debug logging" 2013-08-30 22:52:24 +00:00
smoketests Fix and Gate on H303 (no wildcard imports) 2013-07-30 14:34:31 -07:00
tools Updates tools/config/README 2013-08-22 10:15:14 +08:00
.coveragerc Port Cheetah templates to Jinja2 2013-09-02 16:03:34 +02:00
.gitignore add .idea folder to .gitignore pycharm creates this folder 2013-03-07 17:00:22 -06:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 15:07:19 -04:00
.mailmap Update mailmap for jhesketh 2013-09-12 14:50:59 +10:00
.testr.conf Make testr preserve existing OS_* env vars values 2013-05-29 11:55:49 +03:00
CONTRIBUTING.rst Add a CONTRIBUTING file. 2012-11-21 17:04:48 -05:00
HACKING.rst Use timeutils.utcnow() throughout the code 2013-07-19 16:08:54 +03: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
README.rst Update references with new Mailing List location 2013-07-28 11:28:46 -07:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
openstack-common.conf Remove unsafe XML parsing 2013-08-08 13:49:45 +02:00
pylintrc Don't warn about C0111 (No docstrings) 2011-03-16 15:28:09 -07:00
requirements.txt Update requirements not to boto 2.13.0 2013-09-13 15:26:53 +08:00
run_tests.sh Merge "emit warning while running flake8 without virtual env" 2013-09-02 07:36:38 +00:00
setup.cfg Revert baremetal v3 API extension 2013-09-05 15:19:31 -07:00
setup.py Updated from global requirements 2013-09-05 11:12:57 -04:00
test-requirements.txt Updated from global requirements 2013-09-05 11:12:57 -04:00
tox.ini Ignore H803 from Hacking. 2013-09-13 13:56:35 +12: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:

http://github.com/openstack/nova

Developers should also join the discussion on the mailing list, at:

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

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://nova.openstack.org/

For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.

-- End of broadcast