----- Original Message -----
From: "Antoni Segura Puimedon" <asegurap(a)redhat.com>
To: devel(a)ovirt.org, "users" <users(a)ovirt.org>
Sent: Wednesday, July 30, 2014 2:15:36 PM
Subject: [ovirt-users] Testday: json rpc
[...]
**Logging**
When doing a network operation with xmlrpc we'd get the following in vdsm.log
Thread-21::DEBUG::2014-07-30
13:38:11,414::BindingXMLRPC::1127::vds::(wrapper) client
[10.34.61.242]::call setupNetworks with ({'10': {'nic':
'em2', 'vlan':
'10', 'STP': 'no', 'bridged': 'true',
'mtu': '1500'}}, {},
{'connectivityCheck': 'true', 'connectivityTimeout': 120}) {}
flowID
[686033d4]
Thread-21::DEBUG::2014-07-30
13:38:32,689::BindingXMLRPC::1134::vds::(wrapper) return setupNetworks
with {'status': {'message': 'Done', 'code': 0}}
As you can see, we get the bare minimum logging one could ask for, an entry
with the command called and the data it received and another entry with the
return result data.
Doing the same with jsonrpc (and ignoring the excessive IOProcess) if I
search
for "setupNetworks" the only thing I get is:
Thread-23057::DEBUG::2014-07-30
13:32:44,126::__init__::462::jsonrpc.JsonRpcServer::(_serveRequest)
Looking for method 'Host_setupNetworks' in bridge
And if I search for the data received, like 'STP', there is nothing
whatsoever.
As I said, unless this is fixed and we get entries with the same amount of
data
as before, it can't be used in production nor in development.
https://bugzilla.redhat.com/1124813
Can you share some VDSM logs? Attaching them to BZ would be super.
I'd like to check if that applies to virt flows as well - as I actually tend to
believe.
Bests,
--
Francesco Romani
RedHat Engineering Virtualization R & D
Phone: 8261328
IRC: fromani