Adapt "nova resize" code to support Virtuozzo ploop disks. As far as ploop disks are in fact directories we add '-r' argument to all utilities that deal with instance' disks such as cp, rsync and scp. Thus we copy disks universally whether they are folders or files. Also using "prl_disk_tool" instead of "qemu-img" is better for ploop images because it resizes guest filesystem as well. We can't resize disks from guest OS in containers, because they are not allowed to write directly to block device. ploop tool can resize partition table and internal filesystem, but only for container's disks. Such disks must have only one partition with ext filesystem. prl_disk_tool can resize disks with internal filesystems and doesn't require any special layout so it can resize disks for virtual machines. So it's better to use this tool instead of ploop. Also we make compute.filters more strict We call "ploop" only with "restore-descriptor" argument And we set disk size in megabytes for prl_disk_tool Co-Authored-By: Dmitry Guryanov <dguryanov@parallels.com> Depends-On: I04c4379459c2fc1fd4801ec2aad53d0f6053b6d6 Change-Id: I38dbf73beb01fe1939ddca63fbfedbec1dc3c826 Implements: blueprint virtuozzo-instance-resize-support
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