Go to file

Mark McLoughlin 008875048c Move imagecache code from nova.virt.libvirt.utils

The imagecache related code in libvirt.utils uses the base_dir_name
config option.

If we move the imagecache utils into imagecache, then we can move
the base_dir_name option into that module since there are no other
users of it.

Having all the imagecache code in the imagecache module seems like
a sensible thing to do anyway.

blueprint: scope-config-opts
Change-Id: I1e154aa4de1628d40964207bdcbe5b3b55076442

2012-11-28 15:04:34 +00:00

bin

Validate rxtx_factor as a float.

2012-11-27 11:12:41 -05:00

nova

Move imagecache code from nova.virt.libvirt.utils

2012-11-28 15:04:34 +00:00

.coveragerc

Finalize tox config.

2012-06-07 12:15:42 -04:00

.gitignore

Ignore editor backup files.

2012-11-19 09:20:52 +13:00

.gitreview

Add .gitreview config file for gerrit.

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

.mailmap

Add SSL support to utils.generate_glance_url().

2012-11-26 14:29:37 -06:00

CONTRIBUTING.rst

Add a CONTRIBUTING file.

2012-11-21 17:04:48 -05:00

HACKING.rst

Ban db import from nova/virt

2012-11-12 12:37:33 -08: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

Add a CONTRIBUTING file.

2012-11-21 17:04:48 -05: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

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:

https://lists.launchpad.net/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