svenvogel edited a comment on issue #3294: Set default service offering over api and ui URL: https://github.com/apache/cloudstack/pull/3294#issuecomment-495555701 Yes you are right at the moment we have a redundant way to set default values 1. global settings 2. this PR First of all we introduced this to make it possible to use the UI to change the service offering for the routers not to use this ugly database hack. before you could set it in the global settings and the hack. now you can set in in the UI. we focused on not to break the functionality. there are different tables. "disk offering" and "service offering" they are connected. there are a "unique_name" and "default_use" ... they seems to be connected. first we thought to rewrite them but there is a lot of work to do and it would break the existing functionality. okay here is the plan, 1. we implement this PR 2. we and our team will work on all our issues and we will improve and change them step by step accordingly. we remove in a second PR the global settings _it can be under discussion to change/adapt the "network offering" "but" i have to admit "network offering" the present network offerings meet all recent requirements. if we change them we would create a huge and complex beast. these mean, change the database and the UI. its a lot of work._ at the moment i think the System Offering is the best location to set up values.  the main problem here is the awful connection between the "disk offering" "service offering" because in "Service Offering" there will be saved CPU, RAM and so one... lets try to work out best solution...
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
