default to {} in both None or nonexistent case for bandwidth
Merge pull request #230 from TMaddox/fix_null_bandwidth

default to {} in both None or nonexistent case for bandwidth
unit test for when bandwidth is None
Merge pull request #231 from TMaddox/fix_null_bandwidth

unit test for when bandwidth is None
Using new exist object in callback
Merge pull request #233 from ramielrowe/callback_fix

Using new exist object in callback
Get or create deployment in parent process

Doing this in the parent process avoids a race condition
where two consumers for a single deployment attempt to
create new deployments at the same time. Thus, creating
duplicate deployments.
Merge pull request #235 from ramielrowe/dup_dep_fix

Get or create deployment in parent process
Made Nova flavor field name configurable
Merge pull request #222 from anujm/instance_flavor_id_support

Added verification for instance_flavor_id field
Merge pull request #227 from manalilatkar/stacky_hosts

stacky/hosts modification according to service input
Added support for glance time format in str_time_to_unix()
Merge pull request #228 from anujm/glance_time_format_support

Glance time format support
Added script to populate instance_flavor_id
in InstanceUsage, InstanceExists and InstanceReconcile
using instance_type_id-to-instance_flavor_id csv mapping
Merge pull request #236 from anujm/data_migration_instance_flavor_id

Added script to populate instance_flavor_id
Remove select_related() from details/search/latest_raw calls

The join caused by select_related() can cause mysql to make poor
choices in regards to index selection. It appears that in small to
mid sized deployments, searches on RawData when joined to
Deployment will use the index on the column being searched instead
of the 'when' that ultimately orders the data. This causes mysql
to create a temp table and file sort that table, which is quite
ineffecient.

This fix simply removes the select_related() calls and populates
the deployment field on the raws by hand.
Merge pull request #238 from ramielrowe/search_detail_no_select_related

Remove select_related() from details/search/latest_raw calls
Drop delete.end notifications with blank launched_at

We can safely drop delete.end notifications without values for
launched_at because these instances never got launched. Thus,
we'd never expect any usage for them.
Merge pull request #240 from ramielrowe/drop_delete_end_no_launched_at

Drop delete.end notifications with blank launched_at
glance_usage_audit.py gives the summary of all exists within audit period along with details of failed exists. Some refactoring in nova_usage_audit is also included.