7f67cc681a
Implementation overview: - Incremental points are saved as dedicated rbd snapshots under the "one_backup_<increment_id>" namespace. This snapshots are used to generate delta files in rbdiff format. - The rbdiff formats are stored in the backup server to restore the rbd volumes. - The restore process is performed directly on the Ceph cluster importing the base image (first full backup in the chain, rbd import) and then applying the increments (rbd import-diff) up to the target increment. - Two new pseudo-protocols has been implemented to adopt the restore pattern above (restic+rbd, rsync+rbd). This protocols bundle of the rbdiff files in a tarball for transfer from the backup server. Note: reconstruct process uses the Ceph BRIDGE_LIST and not the backup server (as opposed to qcow2 backups) Other bug fixes - This commit also fixes #6741, resetting the backup chain after a restore - The original ceph drivers do not receive the full action information, this now has been fixed by including VM information in the STDIN string sent to the driver. Compatibility note. - backup actions should return now the backup format used raw, rbd, ... If not provided oned (6.10.x) will use raw as a default to accommodate any third party driver implementation. It is recommended to include this third argument. Signed-off-by: Guillermo Ramos <gramos@opennebula.io> Co-authored-by: Guillermo Ramos <gramos@opennebula.io> (cherry picked from commit 5f7b370c5274434804726c3feb435c98af761963)
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.
- Check our Quick Start Guide.
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
You can quickly and easily try out OpenNebula’s functionality by installing:
- miniONE for infrastructures based on open-source hypervisors.
- vOneCloud for infrastructures based on Broadcom VMware.
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 deployment guide site for details.
Contact
License
Copyright 2002-2024, 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.