sm volume driver: adding backed with specified sr_uuid fails

[Alex Meade]

when doing:

nova-manage sm backend_add fake fake2

the sr_uuid is always set to None, it should be generated.

Or when doing

nova-manage sm backend_add fake fake2 sr_uuid=53d1a9cf-fb86-45cf-ae3e-6b38cec7cdb4

it should update the backend with the specified sr_uuid or prompt to add one with that sr_uuid.

Currently, sr_uuid is basically ignored.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/5102
Committed: http://github.com/openstack/nova/commit/77495cfed17f12f225e11fbc10e0f8db516dadf2
Submitter: Jenkins
Branch: master

commit 77495cfed17f12f225e11fbc10e0f8db516dadf2
Author: Alex Meade <email address hidden>
Date: Thu Mar 8 21:56:56 2012 +0000

    Fix nova-manage backend_add with sr_uuid

    Fixes bug 950964

    Remove FIXME in db.sm_backend_conf_get_by_sr
    Add first() to sm_backend_conf_get_by_sr query
    Change db/api.py:sm_backend_conf_get_by_sr to call correct impl method
    Have nova-manage generate an actuall sr_uuid instead of always 'None'
    Actually update backend values when specifying uuid

    Change-Id: I620da4563d8c936b5a072c4683ae145280104fc2