This is a multi-part message in MIME format. --------------090806070109050204010202 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit 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 --------------090806070109050204010202 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Michal Skrivanek wrote: <blockquote cite="mid:5310D03D-51D4-4FB2-BDE3-69CB1B77BC17@redhat.com" type="cite"> <pre wrap="">On 13 Jun 2014, at 11:04, Sven Kieske wrote: </pre> <blockquote type="cite"> <pre wrap="">Well, I know this is not that helpful but afaik there is work done to replace xml-rpc communication with json based communication. </pre> </blockquote> <pre wrap=""><!----> @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:) </pre> <blockquote type="cite"> <pre wrap=""> Am 13.06.2014 10:57, schrieb Joop: </pre> <blockquote type="cite"> <pre wrap="">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. </pre> </blockquote> </blockquote> <pre wrap=""><!----> @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. </pre> </blockquote> 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 :-(<br> <br> Joop<br> <br> <br> </body> </html> --------------090806070109050204010202--