IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Some backup drivers may not allow delete (forget) operations while an
active backup is being performed. This commits fails the
one.image.delete API call in that case.
A new configuration attribute to describe the related driver behavior has been
added CONCURRENT_FORGET for DS_MAD_CONF.
- Keep last 2 checkpoints to be able to retry failed operations
- Bitmap are managed in an equivalent way for RUNNING and POWEROFF VMs.
(cherry picked from commit d008ae343f771e6d2ee9ffbad024c551f71b2164)
* Introduce support to follow KEEP_LAST for incremental backups.
- New increment_flatten action added for backup datastores.
- increment_flatten will consolidate KEEP_LAST increments into the
current first increment in the chain.
- increment_flatten MUST return the new chain (inc1:source1,...) and size
of the new first increment (FULL) in the chain.
* Downloader logic for restore has been extracted from downloader.sh to
reuse the increment flatten logic. A new command restic_downloader.rb
process restic:// pseudo-urls.
* Restore process uses two new attributes to customize the restore
process:
- NAME to be used as base name for images and VM Template
- INCREMENT_ID to restore disks from a given increment (not always the
last one)
* Common logic has been added to BackupImage class (backup.rb)
* Includes the following fixes:
- Fix when increment includes blocks larger than max qemu-io request size
- Fix IMAGE counter for quotas on backup images
- Fix rsync restore NO_IP / NO_NIC attributes
TODO:
* Mimic increment_flatten logic and restore images on the backup server
* Suntone restore options
co-authored-by:Michal Opala <mopala@opennebula.io>
Custom attributes have been added at the role level.
In this way, roles can be individually customized during instantiation.
Added parameters:
- custom_attrs: contains user-defined custom attributes.
- custom_attrs_values: contains the values of the custom_attrs.
In case of overlapping role and service level attributes, role level attributes will take precedence.
Example:
roles: [
{
"name": "role_1",
...
"custom_attrs": {
"MEMORY": "M|range|memory (mb)|100..500|200",
"DISK_SIZE": "M|range|disk size (mb)|100..500|250"
}
}
]
In order to be used from CLI, the vm_template_contents in the service template must be filled manually.
This permit to use the the LDAP_MATCHING_RULE_IN_CHAIN for nested group membership
Here is "ldap_auth.conf" config related 👍
:group_field: 'member:1.2.840.113556.1.4.1941'
:rfc2307bis: false
This fix#1289
Signed-off-by: Alexandre ROTA <alex@not24get.fr>
(cherry picked from commit 608189fb756e0b039aed2cf7bc9874c527022d9c)
