156cd04ba5
- Add suport for delete snapshots in the middle of the chain in qcow2
(ALLOW_ORPHANS=NO). Example, snapshot 2 below:
0 <- 1 <- 2 <- 3
- It supports removing the last snapshot and active (blockpull) and
first one (snapshot 0). The first snapshot cannot be deleted in
persistent images because of the underlying link setting.
- Snapshots are deleted by blockcommit. For example to delete 2, 3 is
committed into 2:
0 <- 1 <- 2: (2+3)
A new file 3.current is created in the filesystem to look for the
actual file name supporting snapshot 3.
- qcow2/shared operations snap_delete, snap_revert and cpds
(disk-saveas) has been updated to react to the .current files
- The kvm/deploy action has been updated to resolve links in source file
attributes. This is needed so the <backingStore> of the libvirt domain
does not contain the sysmlinks that changes on the revert/create
operations.
- The kvm/migrate action also includes a minor modification to resolv
the VM disk
- Snapshots with more than 1 child (or their relatives) cannot be deleted to not
break backing chains.
- It has been found that the snap-delete operation in suspend state is
insecure as the guest caches may not be updated accordingly. The
operation is now not allowed in this state.
- The associated state has been removed from oned. It needs to be
removed in CLI/Sunstone and APIs
- The changes are for VM disk-snapshots. A similar update can be made
for images in the datastore/fs snap_delete action. This operation is
not implemented in this commit.
Note: Output of xmllint may or may not include new lines when multiple matches
of an xpath expression occurs. Parsing of xmllint output adds additional new lines
to deal with different versions.
|
||
|---|---|---|
| .github | ||
| include | ||
| share | ||
| src | ||
| .gitignore | ||
| install.sh | ||
| LICENSE | ||
| LICENSE.onsla | ||
| LICENSE.onsla-nc | ||
| NOTICE | ||
| package-lock.json | ||
| README.md | ||
| SConstruct | ||
Description
OpenNebula is an open source platform delivering a simple but feature-rich and flexible solution to build and manage enterprise clouds for virtualized services, containerized applications and serverless computing.
To start using OpenNebula
- Explore OpenNebula’s key features on our website.
- Have a look at our introductory datasheet.
- Browse our catalog of screencasts and video-tutorials.
- Download our technical white papers.
- See our Documentation.
- Join our Community Forum.
Contributing to OpenNebula
- Contribute to Development.
- Learn about our Add-on Catalog.
- Help us translate OpenNebula to your language.
- Report a security vulnerability.
Taking OpenNebula for a Test Drive
There are a couple of very easy ways to try out the OpenNebula functionality
- miniONE for infrastructures based on open source hypervisors.
- vOneCloud for VMware based infrastructures.
Installation
You can find more information about OpenNebula’s architecture, installation, configuration and references to configuration files in this documentation section.
It is very useful to learn where log files of the main OpenNebula components are placed. Also check the reference about the main OpenNebula daemon configuration file.
Front-end Installation
The Front-end is the central part of an OpenNebula installation. This is the machine where the server software is installed and where you connect to manage your cloud. It can be a physical node or a virtual instance.
Please, visit the official documentation for more details and a step-by-step guide. Using the packages provided on our site is the recommended method, to ensure the installation of the latest version, and to avoid possible package divergences with different distributions. There are two alternatives here: you can add our package repositories to your system, or visit the software menu to download the latest package for your Linux distribution.
If there are no packages for your distribution, please check the build dependencies for OpenNebula and head to the Building from Source Code guide.
Node Installation
After the OpenNebula Front-end is correctly set up, the next step is preparing the hosts where the VMs are going to run. Please, refer to the documentation site for more details.
Contact
License
Copyright 2002-2023, OpenNebula Project, OpenNebula Systems (formerly C12G Labs)
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.