Oded Le'Sage f4276baa19 Enhance Shaker to use flavor metadata matching with host aggregates ... Problem: We have large compute deployments (400+) but some of these computes have metadata set because they offer special hardware.For this example let's assume 100 of these computes have the metdata dpdk=true. There is currently no way in Shaker to choose a flavor that will only run on a subset of all available computes to run hardware specific tests It is not feasible or practical to isolate, reconfigure, or create an availbility_zone or host aggregate for these 100 computes. Nova has a feature to address situations like this by using aggregate_instance_extra_specs in a flavor. This commit enhances Shaker to make use of the Nova feature to match a flavor with a host aggregate to ensure VMs are only spun up on computes that can support that flavor. Using this enhancement users could create a shaker-dpdk flavor with metadata aggregate_instance_extra_specs:dpdk=true. When running the function get_available_compute_nodes Shaker will only take into account the computes which have the metadata dpdk:true as matching/available computes. This will allow users to run tests on all dpdk computes only, just by specifying the correct flavor. If a flavor with no metadata is chosen, the same behavior (use all computes) that shaker uses today would apply. Change-Id: If04e90fc23959a2ff5c1a51a1bd19f40cec5cd2b		2018-10-24 11:11:59 -05:00
..
clients	Enhance Shaker to use flavor metadata matching with host aggregates	2018-10-24 11:11:59 -05:00
__init__.py	Initial commit	2015-01-28 18:56:01 +03:00