Antoine, As far as I understand, what you want is a missing feature. You can dedicate a zone/pod/cluster/host to a domain but for the users in that domain to be forced on that domain they have to only have access to compute offerings with the implicitDedicationPlanner *and* when deploying, they still have to select the affinity group for the dedicated resourcegroup.
Your observations are correct and the only thing that is a bit less intuitive (afaics) is that the dedicated resources will only work with this specific setup. There is an issue (5803) out that requires about the same. (maybe a colleague?) On Sat, Jan 15, 2022 at 3:37 AM Antoine Boucher <[email protected]> wrote: > Hello, > > I would like to implicitly force users of a Domain to use a specific sets > of hosts and block all other domain users to use the said hosts. > > If I dedicate the hosts to the domain. It will prevent the other domains > to use them and allow the domain owner users to use them explicitly using > the affinity profile. > > However, I have not found a way to implicitly make it work during instance > creation without having to select the affinity option. Including using a > specially created compute offering with the implicitDedicationPlanner > strict or preferred. > > From the logs, I see that the dedicated hosts are removed right away from > the potential hosts candidate regardless of the user creating the instance > being a member on the domain owner. > > Perhaps I’m not understanding the feature properly, what am I missing? > > Regards, > Antoine > > > > Antoine Boucher > [email protected] > [o] +1-226-505-9734 > www.haltondc.com > > “Data security made simple and affordable” > > > > Confidentiality Warning: This message and any attachments are intended > only for the use of the intended recipient(s), are confidential, and may be > privileged. If you are not the intended recipient, you are hereby notified > that any review, retransmission, conversion to hard copy, copying, > circulation or other use of this message and any attachments is strictly > prohibited. If you are not the intended recipient, please notify the sender > immediately by return e-mail, and delete this message and any attachments > from your system. > -- Daan
