| Who would most benefit from this idea? | Lab Developers or Lab Authors |
Thanks for taking a minute to send along this suggestion! Our Product Group has given this an initial review and assigned this a status of "Future Consideration." This status mean this Idea is not yet on our roadmap, but will be part of our normal prioritization processes.
If you have additional context or would like to generate more demand, feel free to edit your original post, add a comment, and/or invite your peers to upvote your Idea.
I thought that perhaps the cloning process could have two options:
The way it is now with a note that it is faster but carries the diff disks with it.
A new way where it takes much more time but collapses the diff disks.
When a customer has option 2 available to them, they could at least clean up any environment by using such a tool. Of course, Skillable would have to develop this on the back end (script what it is that the support group does to collapse the disks.)
Kim Nielsen
To have the option to do Diff Disk Merger ourselves is a must to save time for our Lab development and publishing. Building our large Labs it often takes many save before a Lab is ready, and by that we end up with a lot of Diff Disk. By having the option to do the Disk Merger ourselves will saves us a couple of days to get a Lab Publish. The Diff Disk Merger often reduce the start time of a Lab with up to 20 min.
Maybe when we set Lab to Complete it should automatic go through a Diff Disk Merger to optimize the Lab. But any option for a self service would be appreciated.
What about having differencing disks automatically merged on the target lab profile when cloning a lab profile?
My co-worker came up with a solution that might be easier to implement. What if the oldest differencing disk was automatically merged when a fourth differencing disk was created? That way there would never be more than three differencing disks, keeping within best practices.
We have spent a few cycles talking through how we might make improvements in this process. Good time to vote for this and/or add specifics if you're pulling for this feature.
Any update on this?
I have several clients (Quantum, Tanium and others) who would LOVE this feature.
I would like to see self-service merging added back to the roadmap as well. It should be possible to handle a tree as well though. If a disk is detected as part of a tree it could be cloned and merged into the parent keeping the original disk as part of the tree branch. A warning could be displayed saying that merging disks could increase the overall storage used.