Michal Skrivanek wrote:
On 13 Jun 2014, at 11:04, Sven Kieske wrote:
Well, I know this is not that
helpful but afaik there is work done
to replace xml-rpc communication with json based
communication.
@Sven:
yeah, and one of the (many) reasons why we want it. But that's vdsm.
Scheduler is a different package/app.
Typical workaround is to use a string type to pass integer numbers (or use
smaller numbers:)
Am 13.06.2014 10:57, schrieb Joop:
Then oVirt shouldn't either use that kind of numbers or should not use
xmlrpc.
Sorry but thats a non-answer and doesn't help anybody.
@Joop:
what's with the attitude?
I have nothing to do with the scheduler and I have no idea what is it trying or
supposed to return…I'm just pointing out the error is due to the large whatever
number being returned; in hope of someone with knowledge of the scheduler will
take it from there.
I'd tend to agree XMLRPC is not the best thing to use; and I think it's
important to keep reminding the common pitfalls of it.
Sorry I'm only trying to help someone which got the code and it doesn't
seem to work and I just figured out what is not working and replied that
back to the list for everyone to see and comment on. With the now
supplied reason I understand why it doesn't work but don't understand
why the code is supplied in this form. Looking at the output again I
don't get why the numbers are that big. The servers only have 32G and
now way you use calc will it come close to the numbers seen :-(
Joop
_______________________________________________
Users mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/users
