You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by GitBox <gi...@apache.org> on 2019/05/30 18:28:26 UTC

[GitHub] [cloudstack] rafaelweingartner commented on issue #3294: Set default service offering over api and ui

rafaelweingartner commented on issue #3294: Set default service offering over api and ui
URL: https://github.com/apache/cloudstack/pull/3294#issuecomment-497434366
 
 
   @pbankonier and @svenvogel thanks for the PR and your valuable contributions. I have read the discussions, but still, have a question here.
   
   What does this change mean for the current method we have to override/change the default service offerings for system VMs? I mean, currently we have the following configurations available:
   * consoleproxy.service.offering
   * internallbvm.service.offering
   * secstorage.service.offering
   
   I do understand that you are introduced a method to change these default for other types of VMs, such as VRs, but still, how will this play out for people that are already used to use the current global settings parameters to configure the service offering for console proxy, ssvm, and internal LB VM?
   
   I do like the UI change you are proposing, but I see that it can be implemented with the same backend we have. Of course, you are now supporting the override for other types of system VMs as well, but I guess that we could just use the "standard" we have currently in place.
   
   Now, if the proposal is to change this "standard", then we need to create/propose a migration path for people.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services