Open Stack

On Apr 11, 2019, at 9:10 AM, Adam Spiers <aspiers at suse.com> wrote:
> 
> Not so much concerns as just trying to make sure we don't miss an opportunity to discuss something in person which seemed to cause multiple discussions / redesigns over many months.  For example would it be worth considering tweaking the placement API so that only the driver can set/unset traits which it owns?  This would avoid the corner case conflict we currently have where a naughty admin messes around with driver traits on RPs. 

The concept of “owning” particular traits isn’t in Placement. Rather, it is in the domain of the service that is using Placement. So any enforcement regarding which traits are acceptable has to be on the calling end, not in the Placement API.

So yeah, “do nothing”.

-- Ed Leafe