Basically #2 makes sense to me.
> 2) Enrich/enhance the NeutronServer exceptions with a type and detail
properties.
> This way, when a NeutronServer exception is serialized and sent to
python-neutronclient,
> the specific NeutronClient exception can be raised (and then sent to
nova-api).
What gra
I think approach #2 makes sense. I can take a stab at it, but I am not
guaranteeing any delivery dates.
Do you have a specific api/exception that you would like to test to see if
the concept works for nova-api? The one bug you mention singles out
associating a floating IP to a port. That might be
Hi,
Any ideas on this one ? Maybe I should forward this email to a more
specific ML ?
On Thu, Jul 4, 2013 at 6:24 PM, Jordan Pittier wrote:
> Hi guys,
>
> Nova-api makes extensive use of python-neutronclient. But the only
> exception from neutronclient that nova-api catches is the
> generic Qua
Hi guys,
Nova-api makes extensive use of python-neutronclient. But the only
exception from neutronclient that nova-api catches is the
generic QuantumClientException (defined in
quantumclient/common/exceptions.py).
neutronclient has some more specific exceptions
like PortInUseClient, NetworkNotFou
