Comment 28 for bug 1460222

There are a number of cases where this feature can be useful, not just the ones above: bare metal provisioning is one of them.

I have finally come to the conclusion, after these many cycles involved in Neutron, that it is fine to provide the ability to tag resources, with the caveat that in lack of a strong protection mechanism against abuse by neutron drivers, we restrict access to admin only as the default choice, just to err on the side of caution.

I understand that this can there's a potential danger of lock-in, but technically speaking no two Neutron deployments are alike, and interoperability (or lack thereof) if not properly defined feels like a weak argument, especially in face of so much API diversity, and extensibility of the existing platform. Surely we don't want to make things worse, but in light of what the platform can do, it doesn't seem like we're making things that much more terrible.

My 2c