Chris Behrens
3f42e11ca0
Filters are supposed to be pluggable, but they are not, since you have to modify __init__.py. This adds a --scheduler_availabile_filters setting which replaces the hardcoding in __init__.py. This setting is a MultiStr (a list, which you can specify more than once) containing the full paths to filter classes to make available to the scheduler. Using a value of 'nova.scheduler.filters.standard_filters' maps to all standard filters included in nova under nova.scheduler.filters. This is the default setting and matches what was in __init__.py before. Also renamed --default_host_filters to --scheduler_default_filters to make the flag a bit more clear. Change-Id: I10eb54e9982b6d42316adfb2cc2600b44a9c3bdf
The Choose Your Own Adventure README for Nova ============================================= You have come across a cloud computing fabric controller. It has identified itself as "Nova." It is apparent that it maintains compatibility with the popular Amazon EC2 and S3 APIs. To monitor it from a distance: follow `@openstack <http://twitter.com/openstack>`_ on twitter. To tame it for use in your own cloud: read http://docs.openstack.org To study its anatomy: read http://nova.openstack.org To dissect it in detail: visit http://github.com/openstack/nova To taunt it with its weaknesses: use http://bugs.launchpad.net/nova To watch it: http://jenkins.openstack.org To hack at it: read HACKING To cry over its pylint problems: http://jenkins.openstack.org/job/nova-pylint/violations