Add support for extra ops to aggregate_instance_extra_specs filter

[Mark McLoughlin]

We added extra comparison operators to the extra specs support in compute_capabilities_filter: https://review.openstack.org/8089

This is where we compare the extra specs to the capabilities reported by the hypervisor

However, using host aggregates, we also allow administrators to define per-host properties which extra specs gets matched against. This is handled by the aggregate_instance_extra_specs filter.

We should add the extra operators to the aggregate_instance_extra_specs too.

Being addressed at https://review.openstack.org/#/c/11449/.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/11449

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/11832

[Mark McLoughlin (markmc)]

Joeseph - do you need someone else to take over this issue?

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/11449
Committed: http://github.com/openstack/nova/commit/6bc54f4af01126712716682a5e50333bf63ff1a7
Submitter: Jenkins
Branch: master

commit 6bc54f4af01126712716682a5e50333bf63ff1a7
Author: Jinwoo 'Joseph' Suh <email address hidden>
Date: Wed Aug 22 19:59:04 2012 -0400

    Add ops to aggregate_instance_extra_specs filter.

    The following operators on instance_type_extra_specs were added in
    aggregate_instance_extra_specs filter. Fixes bug 1037090.

    = (equal to or greater than as a number; same as vcpus case)
    == (equal to as a number)
    != (not equal to as a number)
    >= (greater than or equal to as a number)
    <= (less than or equal to as a number)
    s== (equal to as a string)
    s!= (not equal to as a string)
    s>= (greater than or equal to as a string)
    s> (greater than as a string)
    s<= (less than or equal to as a string)
    s< (less than as a string)
    <in> (substring)
    <or> (find one of these)

    If the first word in the instance_type_extra_spec is not one of the
    keywords above, a default operator "s==" is used.

    E.g.: ">= 5", "s== 2.1.0", "<in> gcc", and "<or> fpu <or> gpu"

    Change-Id: Iee9bf68011738aab146e6311a17cb3c673d7a392