About the scheduler filter (sorry for my late relpy), I believe I've used ComputeCapabilitiesFilter.
About the usage:
Actually we've used the flag to specify heterogeneous architecture support. In addition to x86 architecture, we wanted to support other architecture using the instance_type_extra_specs flag.
And we put dynamically changing values in the flag.
For example,
shows that the nova-compute node has two GPUs of NVdia fermi and runs LXC hypervisor.
The 'gpus' key is dynamically changing at run-time as gpus are allocated and deallocated.
Most static keys can be handled by host-aggregate method.
But keys with dynamic values cannot be handled by host-aggregate method.
About the scheduler filter (sorry for my late relpy), I believe I've used ComputeCapabili tiesFilter.
About the usage:
Actually we've used the flag to specify heterogeneous architecture support. In addition to x86 architecture, we wanted to support other architecture using the instance_ type_extra_ specs flag.
And we put dynamically changing values in the flag.
For example,
instance_ type_extra_ specs=cpu_ arch:x86_ 64, gpu_arch:fermi, gpus:2, hypervisor_type:LXC
shows that the nova-compute node has two GPUs of NVdia fermi and runs LXC hypervisor.
The 'gpus' key is dynamically changing at run-time as gpus are allocated and deallocated.
Most static keys can be handled by host-aggregate method.
But keys with dynamic values cannot be handled by host-aggregate method.
Even before the merge of "https:/ /github. com/openstack/ nova/commit/ 4b4f0d61836e527 340511f6198c2f2 c0bdf70888 merged in 2014-01-28", the dynamic update mechanism was broken.