DaanHoogland commented on issue #5803: URL: https://github.com/apache/cloudstack/issues/5803#issuecomment-1013074176
@edikevich I did a deep code dive and think I need to move this to 4.17, if at all we will change this behaviour. The reason: 1. What if there are two dedicated PODs or even two dedicated resource pools, maybe even at different levels? This is not something that allows for the implicit choice of an affinity group on an explicitly dedicated resource group. We wouldn't know if both are valid or even if either is valid. 2. The behaviour of the strict mode is to strictly deploy on the resources that belong to the affinity group and if no one is known no deployment is possible. These two points combined make your expectations hard to achieve. Let's think on how to address your need. - One possibility would be in the UI; make sure that the planner is retrieved and it is scanned for the requirement of a dedication, and force the user to pick one. - another one is in the backend, to scan dedicated resources for this user and allow all if none is choosen - a third is to make a default choice. In any case I am moving this to 4.17, sorry. -- 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]
