Switches from tenant_id to tenant_name since latter isn't preserved between resets
Host for evacuation and reassignment removed from the configuration.

For evacuation random host is picked. Additional check for # of hosts > 1.
For reassignment tests look for the host with blocked status.
Switches to tenant picking by mask instead of hard-coded one
Updates functional tests description
Switches from '' to null for action parameter dropping via events
Adds separate handler for error events; changes files encoding to utf8
Repair block device mapping format and tests

Correct block device mapping format is {dev_name: vol_id, ...}.
Prefix name of image created from volume
Restrict in volume migration tasks

Temp image and volume for migration should be created in context of original
owner of those resources. Pass user and tenant info from server migration
function to volumes migration functions and use cloud.restrict to create
connections with user/tenant context.
Update tests for volume migration with restricted cloud
Merge remote-tracking branch 'origin/master' into cinder-resources
Attach volumes to servers in setup function

One volume per server, until either servers or volumes list in tenant is
depleted.
Workloads configuration support in setup

Configuration file allows to create test workloads in source cloud, described by
YaML formatted dictionary. Tenant workload type is supported. Tenant workload
dict might include 'volumes' section. Volumes defined there will be created by
setup function.
Volumes attachment to servers can be defined in 'workloads' config by adding
'volumes' list to 'server' definition.
Example:
workloads:
    tenants:
        name: pumphouse-test-1
        ...
        volumes:
            - &volume1
                size:           1
                display_name:   pumphouse-test-vol-1
        servers:
            -
                name:           pumphouse-test-server-1
                volumes:
                    - << *volume-1
Fix volume snapshotting task
Update volume tests
Correct handling of volumes in workload config

Volumes are configured in tenant dict, and tied to servers via server dict. When
setting up server, find its volumes by display_name parameter.
Example:
CLOUDS:
    source:
        workloads:
            tenant:
                volumes:
                    - &volume-1
                        display_name: volume-1
                        size: 1
                servers:
                    -
                        name: server-1
                        volumes:
                            - <<: *volume-1
Wait for and emit volume event in setup_volume function of management module
Add routers in neutron cleanup
Merge remote-tracking branch 'origin/master' into cinder-resources
New events in volume module