Nova flavor extra_spec is case sensitive

Confirmed: The "trusted_filter" for example uses a case sensitive comparison [1]:

    def is_trusted(self, host, trust):
        level = self.caches.get_host_attestation(host)
        return trust == level

[1] https://github.com/openstack/nova/blob/master/nova/scheduler/filters/trusted_filter.py#L249

In Progress: Tan Lin is set as assignee.

Adds patch link:

https://review.openstack.org/#/c/193047/

Change abandoned by Michael Still (<email address hidden>) on branch: master
Review: https://review.openstack.org/193047
Reason: This patch has been stalled for quite a while, so I am going to abandon it to keep the code review queue sane. Please restore the change when it is ready for review.

Should this be progressed? Can we get agreement on whether filters should be case sensitive or not?

I've seen particular situation where different users are responsible for creating flavors and extra_specs on a host aggregate. In that situation case sensitivity can be more of a pain.

i.e.
User one creates flavors to support CPU pinning

nova flavor-key compute-optimized.small set aggregate_instance_extra_specs:pinned"="false";

User two who racks the hardware and configures it in Openstack, specifies which machines can be used for dedicated CPU pinning

nova aggregate-set-metadata 2 pinned=False

In this scenario the operators would want false == False.

Are there any scenarios where case insensitivity would be undesirable?