Hudratronium commented on issue #5803: URL: https://github.com/apache/cloudstack/issues/5803#issuecomment-1604796964
> I don't know:) If user from domain try do deploy instance with CO with Deployment planner equal ImplicitDedicationPlanner with strict policy and DON'T choose Affinity Group deploy is failed. If user from domain try do deploy instance with CO with Deployment planner equal FirstFitPlanner and choose Affinity Group deploy is passed. If user from domain try do deploy instance with CO with Deployment planner equal FirstFitPlanner and DON'T choose Affinity Group deploy is passed. > > I think main thing there is "choose Affinity Group". For me, VM with CO with Deployment planner equal ImplicitDedicationPlanner with strict policy shoud deploy on dedicated resources and ignoring Affinity Group (it doesn't matter whether it is chosen or not). As @edikevich wrote above that the problem is not, that he can't deploy anything at all. From my understanding the problem is, that a user, who wants to deploy a vm needs actively to select the affinity group. The intention when creating a service offering with: "Deployment Planner = Implicit dedication & Planner mode = strict"seems to be that when using this service offering it is only deployed on dedicated hosts. everything else shall not be possible. So why a user of the serviceoffering needs to select the correct affinity group while deploying a vm? The decision on "which" is the correct affinity group (at least for deployment) is already made due to dedication (as we learned realized with a affinity group). One would expect, that this affinity group is the only availeable one and therefore afaik 'standard' / preselected. -- 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]
