openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
23,877 Commits 10 Branches 94 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
e69310b27b
Go to file
Jay Lau e69310b27b VMware: Detach volume should not delete vmdk 
During volume detach a delete_virtual_disk_spec is used to remove
the device from the running instance. This spec also "destroy" the
underlying vmdk file, this is not right, we should not delete vmdk
file when detach it from a VM instance.

The fix was remove the fileOperation field when detach vmdk volume
so as to make sure the volume will not be destroyed; but for iscsi
we still need to destroy the volume.

Also I changed the function name from delete_virtual_disk_spec to
detach_virtual_disk_spec which is more accurate.

Change-Id: Ibd218d6a8cfeede4f5ca74f28bc0c3d0c185bb14
Closes-Bug: #1241350
(cherry picked from commit 0405d7b937)
2013-11-15 23:18:02 -08:00
contrib Enable N302: Import modules only 2013-01-25 12:11:54 -05:00
doc Merge "Add V3 API samples for security-groups" 2013-09-26 18:04:07 +00:00
etc/nova Baremetal: Be more patient with IPMI and BMC 2013-10-10 10:20:11 -04:00
nova VMware: Detach volume should not delete vmdk 2013-11-15 23:18:02 -08:00
plugins/xenserver XenAPI: Add versioning for plugins 2013-10-10 10:20:53 -04:00
smoketests Fix and Gate on H303 (no wildcard imports) 2013-07-30 14:34:31 -07:00
tools Merge "Update sample config generator script" 2013-09-26 10:09:49 +00: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 Open stable/havana 2013-10-17 16:15:09 -04:00
.mailmap Merge "update .mailmap" 2013-09-17 02:57:26 +00:00
.testr.conf Make testr preserve existing OS_* env vars values 2013-05-29 11:55:49 +03:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08: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
openstack-common.conf Revert "Importing correlation_id middleware from oslo-incubator" 2013-09-03 14:13:44 -07:00
pylintrc Don't warn about C0111 (No docstrings) 2011-03-16 15:28:09 -07:00
README.rst Update references with new Mailing List location 2013-07-28 11:28:46 -07:00
requirements.txt Update six dependency 2013-10-17 14:29:52 -04:00
run_tests.sh Merge "emit warning while running flake8 without virtual env" 2013-09-02 07:36:38 +00:00
setup.cfg Open stable/havana 2013-10-17 16:15:09 -04: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 xenapi: fix pep8 violations in nova plugins 2013-09-17 16:44:59 +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:

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