GabrielBrascher commented on PR #6399: URL: https://github.com/apache/cloudstack/pull/6399#issuecomment-1131638132
@andrijapanicsb I totally understand it. I am sorry in the case I was not clear. I am +1 on proceeding with the current route and merging this, I do understand that this impact a relevant amount of our users. But I wanted to take the opportunity to raise the concerns. We've been seeing this happening other times, and it will stay happening many other times in the future. Supporting a wide set of technologies has been a great strength of CloudStack, I do not want to take this out. But we might need to improve the way we design some features in order to explore the best of each environment that CloudStack will be running into. Otherwise, inevitably, people will start blaming CloudStack / KVM for "poor performance" and walk away to other options that suit best them. While they could actually be having the best for their environment. Right now, I don't have any option on the table to fix it. But it is something good to keep in mind (for another time). -- 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]
