svenvogel commented on issue #3371: Fix virtual template size for managed 
storage for KVM / refactor cloud-install-sys-tmplt
URL: https://github.com/apache/cloudstack/pull/3371#issuecomment-554669880
 
 
   > hm... I've personally used KVM with SolidFire, including hosting all 
system VMs on SF.
   > 
   > I read the explanation but still don't get it why it is now required 
@svenvogel
   
   @andrijapanicsb we use Netapp Solidfire since end of 2018 and work with them 
in KVM. you will see from testing to production the timeframe is not so large. 
The term "now" is not entirely correct. its 6 month of tests and wip. the PR is 
open since June 2019 with some changes and to find out how it works. i dont 
think its good to edit the database for new install and/or change values all 
the time i need an upgrade. except an emergency, I do not think it makes sense 
to edit in the database. do you change always the database? we want to min the 
change of the database.
   
   I think the video of @mike-tutkowski is a good explanation.
   
   > i.e. what EXACTLY doesn't work atm in 4.11+?
   
   i dont know before or after this release. i know that since we use the 
solidfire we have described problem above. the red rectangle with virtualsize 
is set without this fix to the disk disk size from the qcow2 and not 
virtualsize. if you upgrade the systemvm and change and the copy process will 
start it uses the disk size. SF system refuses the disk size. it needs an 
virtualsize and refuse the copy process.
   
   with fix.
   
![image](https://user-images.githubusercontent.com/5433844/68998426-8b26d400-08b2-11ea-8db4-52ba0ca355da.png)
   
   without fix. solidfire copy process will not work.
   
![image](https://user-images.githubusercontent.com/5433844/68998551-f624da80-08b3-11ea-87e6-1ef74ed2901b.png)
   
   make that sense?
   
   maybe @syed can add more historical information in this case. 

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to