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. >> >> Howto solve this problem. Do you need a BZ? patches welcome, BZ always helps. However I'd wait for someone more familiar with the code to answer. Thanks, michal >> >> Joop > > -- > Mit freundlichen Grüßen / Regards > > Sven Kieske > > Systemadministrator > Mittwald CM Service GmbH & Co. KG > Königsberger Straße 6 > 32339 Espelkamp > T: +49-5772-293-100 > F: +49-5772-293-333 > https://www.mittwald.de > Geschäftsführer: Robert Meyer > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen > Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen > _______________________________________________ > Users mailing list > Users@ovirt.org > http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users