You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also you should know that the custom system storage feature has become available
since version OpenNebula 5.0, and currently not developed for my zfs-addon.
If anyone want to develop it, need to write 2 new files:
/vmm/kvm/restore.zfs and /vmm/kvm/save.zfs
Can you tell me / us a slight bit more about that?
I would like to try to write them if it's useful & important.
But I don't exactly understand the role and how critical it is.
Which of these are true?
relevance
description
classification
1 - matters
This is for suspending/resume of VMs in general?
core functionality
2 - matters
This is for making runtime snapshots of disks
core functionality
3 - someone should do it
This is for cross-DS migration
higher level feature
4 - i don't wanna touch
This is enabling something for wild edge cases where someone multi-attaches one zpool to multiple hosts(*)
core functionality only used in 1 case
(*)As in the thread linked. I don't like it too much since it's a layering violation. ONE ends up the manager of the zvols.
i would rather not work on that even when granting that it might be someone who knows more than just the average zfs-forum-poster-gist can do with good procedures)
The text was updated successfully, but these errors were encountered:
Hi @kvaps in https://forum.opennebula.io/t/using-datastores-with-zfs/3075/7 you wrote:
Can you tell me / us a slight bit more about that?
I would like to try to write them if it's useful & important.
But I don't exactly understand the role and how critical it is.
Which of these are true?
(*)As in the thread linked. I don't like it too much since it's a layering violation. ONE ends up the manager of the zvols.
i would rather not work on that even when granting that it might be someone who knows more than just the average zfs-forum-poster-gist can do with good procedures)
The text was updated successfully, but these errors were encountered: