Creating an aggregate with an empty name should result in a 400 not a 409

[Christopher Yeoh]

This was fixed for the V2 API in commit 43f9028f84ffec9b465bec10025ba75266c1bc22 for bug 1188032. We should fix it for the V3 API too

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/41916

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/41916
Committed: http://github.com/openstack/nova/commit/a61e36e1117586bd273ed107e32b44ae771a38bb
Submitter: Jenkins
Branch: master

commit a61e36e1117586bd273ed107e32b44ae771a38bb
Author: Chris Yeoh <email address hidden>
Date: Wed Aug 14 22:31:19 2013 +0930

    Fix aggregate creation/update with null or too long name

    Fixes aggregate creation so an attempt to create an aggregate with
    a null name results in a 400 Bad Request rather than 409 Conflict.
    This was fixed for the V2 api in 43f9028f84ffec9b465bec10025ba75266c1bc22
    and is fixed in this changeset for the V3 api

    For both the V2 and V3 APIs adds a check to ensure that the aggregate
    name is not longer than 255 characters.

    Also fixes null or too long names when updating an aggregate

    Fixes bug 1212240

    Change-Id: I644a8a46f0b75e3717ecafec1889ce6316ca18c6