Exception NoMoreFixedIps doesn't show which network is out of IPs

[Drew Thorstensen]

The exception NoMoreFixedIps in nova/exception.py has a very generic error message:
"Zero fixed ips available."

When performing a deploy with multiple networks, it can become difficult to determine which network has been exhausted. Slight modification to this error message will help simplify the debug process for operators.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/120073
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=35008c0d16e41fdae6e868626477f361392aa923
Submitter: Jenkins
Branch: master

commit 35008c0d16e41fdae6e868626477f361392aa923
Author: Drew Thorstensen <email address hidden>
Date: Tue Sep 9 07:27:56 2014 -0500

    Update NoMoreFixedIps message description

    The exception NoMoreFixedIps within Nova is a generic exception.
    It is used to indicate that the subnets within the network no longer
    have any available fixed IPs for use.

    The original message was non specific. This change set provides an
    updated message that indicates which network has exhausted its fixed
    IP set.

    This is important for operators that are deploying instances with
    multiple networks.

    Change-Id: Ib8b854381b616f83e82bc573f85e109f019897dc
    Closes-Bug: #1366982