11:57 a.m.
This is a multi-part message in MIME format.
--------------080108070306050603070009
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Michal Skrivanek wrote:
On 11 Jun 2014, at 14:31, noc wrote:
> On 26-5-2014 16:22, Gilad Chaplik wrote:
>
>> Hi Nathanaël,
>>
>> happy to assist :) hope it will work in first run:
>>
>> 1) install the proxy and ovirtsdk.
>> 2) put attached file in the right place (according to docs:
".../plugins"), make sure to edit the file with your ovirt's ip, user@domain
and PW.
>> 3) restart proxy service.
>> 3) use config tool to configure ovirt-engine:
>> * "ExternalSchedulerServiceURL"="http://<ip>:18781/"
>> * "ExternalSchedulerEnabled"=true
>> 4) restart ovirt-engine service.
>> 5) under configure->cluster_policy see that weight function
memory_even_distribution was added (should be in manage policy units or /sth- you will see
it in the main dialog as well).
>> 6) clone/copy currernt cluster's used cluster policy (probably none - prefer
it to have no balancing modules to avoid conflicts), name it 'your_name' and
attach memory_even_distribution weight (you can leave it as the only weight module in
weight section to avoid configuring factors).
>> 7) replace cluster's cluster policy with newly created one.
>>
>> try it out and let me know how goes :-)
>>
>>
>>
> Ok, progress of some sort :-)
>
> I added the weight function to the cluster and when I replace my dns name with
localhost in ExternalSchedulerServiceURL then engine.log shows that it can contact the
scheduler. I expected a rebalance but nothing happened. Stopping and starting a VM does
provoke a reaction, an error :-(
>
> From the scheduler.log I see that engine contacts it and pushes some information, the
log also shows that some information is returned and then there is a big error message in
the log of engine.
>
xmlrpc is infamous about not being able to handle numbers like 9223372010239819775
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.
Howto solve this problem. Do you need a BZ?
Joop
--------------080108070306050603070009
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Michal Skrivanek wrote:
<blockquote cite="mid:E04C56CC-D3B2-4105-ACC8-346DEB8BFB7B@redhat.com"
type="cite">
<pre wrap="">On 11 Jun 2014, at 14:31, noc wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 26-5-2014 16:22, Gilad Chaplik wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Nathanaël,
happy to assist :) hope it will work in first run:
1) install the proxy and ovirtsdk.
2) put attached file in the right place (according to docs: ".../plugins"), make
sure to edit the file with your ovirt's ip, user@domain and PW.
3) restart proxy service.
3) use config tool to configure ovirt-engine:
* "ExternalSchedulerServiceURL"="<a
class="moz-txt-link-freetext"
href="http://">http://</a><ip>:18781/"
* "ExternalSchedulerEnabled"=true
4) restart ovirt-engine service.
5) under configure->cluster_policy see that weight function
memory_even_distribution was added (should be in manage policy units or /sth- you will see
it in the main dialog as well).
6) clone/copy currernt cluster's used cluster policy (probably none - prefer it to
have no balancing modules to avoid conflicts), name it 'your_name' and attach
memory_even_distribution weight (you can leave it as the only weight module in weight
section to avoid configuring factors).
7) replace cluster's cluster policy with newly created one.
try it out and let me know how goes :-)
</pre>
</blockquote>
<pre wrap="">Ok, progress of some sort :-)
I added the weight function to the cluster and when I replace my dns name with localhost
in ExternalSchedulerServiceURL then engine.log shows that it can contact the scheduler. I
expected a rebalance but nothing happened. Stopping and starting a VM does provoke a
reaction, an error :-(
From the scheduler.log I see that engine contacts it and pushes some
information, the log also shows that some information is returned and then there is a big
error message in the log of engine.
</pre>
</blockquote>
<pre wrap=""><!---->
xmlrpc is infamous about not being able to handle numbers like 9223372010239819775
</pre>
</blockquote>
Then oVirt shouldn't either use that kind of numbers or should not use
xmlrpc.<br>
<br>
Sorry but thats a non-answer and doesn't help anybody.<br>
<br>
Howto solve this problem. Do you need a BZ?<br>
<br>
Joop<br>
<br>
</body>
</html>
--------------080108070306050603070009--