nxsbi commented on issue #9416: URL: https://github.com/apache/cloudstack/issues/9416#issuecomment-2251794037
I see your point @DaanHoogland 2 things come to mind 1. Yes, one column that is aligned to physical data store - does the file exist - Yes or No - this needs to be added. Second column that shows client recorvery available Yes/No (this is exactly what the current "status" column shows). 2. I would suggest that instead of showing the size of the physical size of the last chain vhd file, we shold show the total chain size. This way the client can see that on Day 1 its the physical size used, which grows until day 7, and when a full snapshot takes palce, it resets to new disk size. Reasoning = many of these snapshots can be of a few MB in size on daily basis while base disk is 500 GB. So if the 3 sizes are only 100 MB for last 3 snapshots, but as a provider we have to provide free 500GB storage for base snapshot, its not right for provider - and in reality is the total that is stored, So showing the total chain size is closest thing to reality for client as well. Note - I have had question from client as why sometimes the snapshot size on the UI shows as 0.1 GB when the disk is 500GB. I will be happy to do testing of any development that is done for this (althrough someone will need to provide me the install files of the release candidate) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
