Hi,
As far as I understand the nova-network module treats the errors. Please
look at the trace - this is when deploying a new instance (via devstack)
and the quantum server is not available:
2012-06-05 07:42:09 DEBUG nova.network.quantum.quantum_connection
[req-f3a300fa-2fae-4438-9bc3-b6b78c53fc8d
762c85b0eae0430a89b9f1a2f3099dfa b3147572ff324a0fb6168c61a31d405a]
Connecting interface 4765b48e-624e-4fcc-93a6-669fbc731ec9 to net
77ea4e74-ea38-4834-ba16-20d2a9d6865d for default from (pid=4579)
create_and_attach_port
/opt/stack/nova/nova/network/quantum/quantum_connection.py:104
2012-06-05 07:42:09 DEBUG nova.network.quantum.quantum_connection
[req-f3a300fa-2fae-4438-9bc3-b6b78c53fc8d
762c85b0eae0430a89b9f1a2f3099dfa b3147572ff324a0fb6168c61a31d405a]
Quantum Client Request: POST
/v1.1/tenants/default/networks/77ea4e74-ea38-4834-ba16-20d2a9d6865d/ports.json
from (pid=4579) do_request
/opt/stack/nova/nova/network/quantum/client.py:183
2012-06-05 07:42:09 DEBUG nova.network.quantum.quantum_connection
[req-f3a300fa-2fae-4438-9bc3-b6b78c53fc8d
762c85b0eae0430a89b9f1a2f3099dfa b3147572ff324a0fb6168c61a31d405a]
{"port": {"state": "ACTIVE", "vm_id":
"4cfb94fc-e2cf-43f7-9b87-6ed1b3dbd01b", "nova_id": "nova",
"allowed_address_pairs": [], "rxtx_factor": 1.0}} from (pid=4579)
do_request /opt/stack/nova/nova/network/quantum/client.py:185
2012-06-05 07:42:09 ERROR nova.rpc.amqp [-] Exception during message
handling
2012-06-05 07:42:09 TRACE nova.rpc.amqp Traceback (most recent call last):
2012-06-05 07:42:09 TRACE nova.rpc.amqp File
"/opt/stack/nova/nova/rpc/amqp.py", line 267, in _process_data
2012-06-05 07:42:09 TRACE nova.rpc.amqp rval =
self.proxy.dispatch(ctxt, version, method, **args)
2012-06-05 07:42:09 TRACE nova.rpc.amqp File
"/opt/stack/nova/nova/rpc/dispatcher.py", line 103, in dispatch
2012-06-05 07:42:09 TRACE nova.rpc.amqp return getattr(proxyobj,
method)(ctxt, **kwargs)
2012-06-05 07:42:09 TRACE nova.rpc.amqp File
"/opt/stack/nova/nova/network/quantum/manager.py", line 385, in
allocate_for_instance
2012-06-05 07:42:09 TRACE nova.rpc.amqp allowed_address_pairs=pairs)
2012-06-05 07:42:09 TRACE nova.rpc.amqp File
"/opt/stack/nova/nova/network/quantum/quantum_connection.py", line 108,
in create_and_attach_port
2012-06-05 07:42:09 TRACE nova.rpc.amqp resdict =
self.client.create_port(net_id, port_data, tenant=tenant_id)
2012-06-05 07:42:09 TRACE nova.rpc.amqp File
"/opt/stack/nova/nova/network/quantum/client.py", line 82, in with_params
2012-06-05 07:42:09 TRACE nova.rpc.amqp ret = self.func(instance,
*args, **kwargs)
2012-06-05 07:42:09 TRACE nova.rpc.amqp File
"/opt/stack/nova/nova/network/quantum/client.py", line 283, in create_port
2012-06-05 07:42:09 TRACE nova.rpc.amqp return
self.do_request("POST", self.ports_path % (network), body=body)
2012-06-05 07:42:09 TRACE nova.rpc.amqp File
"/opt/stack/nova/nova/network/quantum/client.py", line 213, in do_request
2012-06-05 07:42:09 TRACE nova.rpc.amqp "server. Got error: %s") % e)
2012-06-05 07:42:09 TRACE nova.rpc.amqp QuantumIOException: Unable to
connect to server. Got error: [Errno 111] ECONNREFUSED
2012-06-05 07:42:09 TRACE nova.rpc.amqp
2012-06-05 07:42:09 ERROR nova.rpc.common [-] Returning exception Unable
to connect to server. Got error: [Errno 111] ECONNREFUSED to caller
I assume that the nova-network will treat the REST error codes accordingly.
Thanks
Gary
On 06/05/2012 02:35 PM, Irena Berezovsky wrote:
>
> Rami,
>
> Following the recent discussions on the mailing list regarding the
> responsibility of the VIF driver, seems that it should be very thin
> and network provisioning should be handled by Quantum Plugin Agent as
> in OpenvSwitch and LinuxBridge plugins.
>
> I have similar need to get attributes for the attached network/ port
> and seems that the way to do it is via API extension.
>
> You can see the details in the following mailing thread:
>
> https://lists.launchpad.net/openstack/msg12716.html
>
> Hope this helps,
>
> Irena
>
> *From:*netstack-bounces+irenab=mellanox.com@lists.launchpad.net
> [mailto:netstack-bounces+irenab=mellanox.com@lists.launchpad.net] *On
> Behalf Of *Rami Cohen
> *Sent:* Tuesday, June 05, 2012 1:14 PM
> *To:* netstack@lists.launchpad.net
> *Subject:* [Netstack] Nova & Quantum integration
>
> Hi,
> Is there any mechanism to pass some parameters from Quantum Manager to
> the Quantum VIF driver (that is part of the Nova compute)?
> In particular, I saw that when Nova network calls Quantum API (create
> and attach ports) it ignores the return values sent from the quantum
> manager, so there is no formal way to reflect them back to the Nova
> compute.
>
> Thanks,
> RamiC
>