one
one copied to clipboard
Feature Request - OS Image Maintenance
Description
"OS Image" Maintenance (Golden-Image)
https://github.com/OpenNebula/one/issues/5894
- Maintenance Mode for Images (non-persistent Images able to run Guest Side Updates for new VM Deployments)
- Maintain X Versions (Example a User want to keep 5x Versions of an Golden Image) 5x patch cycles. So can go back if an Issue happens with an Patched Image. Cleanup Option if user know specific Versions not needed.
for persistent Images (linked Clones) may works with Recomposition to distribute updated Images ?
Use case Image Maintenance is very helpfully - because a user can be sure for example with non-persistent Image to provide new VM's with new Patches
Interface Changes cli + UI
No Developer Comment on that one? Pitty
At the moment we are in the process of re-factoring the storage system drivers, see https://github.com/OpenNebula/one/issues/5908 Once we have this, it will be easier to implement features such as these ones.
We have had a couple ideas for quite a while on the implementation of those two features since we have run into instances in our internal development pipelines where having image versioning and maintenance mode could have helped.
At the moment you can kind of implement those features by
- using chroot to mount the images and perform maintenance/update operations
- alternatively flag the non persistent image as persistent, perform operations, undeploy and then flag non-persistent again
- have a naming system for the images/update the SOURCE attribute to a new version of the image. This will also be kind of a consequence of implementing our improved backup interface, see https://github.com/OpenNebula/one/issues/5516
Hi Dann, thx for Answer.
well the Point 2 sounded easy to me > but this is the one not working ;). It's blaming VMs using it > explain to me was its expecting the Image in case Recover triggered. Even if its non-persistent.
reason i had to go with an "workaround" like here described https://github.com/OpenNebula/one/issues/5894
after i opend Feature Request ;)