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 2022/02/13 13:50:53 UTC

[GitHub] [cloudstack] Hudratronium commented on issue #5803: User from domain can't deploy VM in dedicated to that domain pod

Hudratronium commented on issue #5803:
URL: https://github.com/apache/cloudstack/issues/5803#issuecomment-1038132084


   > @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.
   
   Just as a quick thought reading through this:
   Maybe the whole topic of "dedication" of ressources, at least on host level, could be "solved" with the usage of the tagging feature for this purposes?
   Currently we are using this to determine and find suitable hosts for VM-Deployment. Why not concider "ownership" or something similar as another "characteristic" of the host which can be changed on the fly? I guess we would have all the logic for deployment-decisions already in the backend... 


-- 
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: commits-unsubscribe@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org