Hi Steven,
This should be working as long it is in the host information. Could you
send the onehost show -x for one of the hosts? (You can send it to me
offlist if there is any sensible information).
The Rank expression is supposed to work with any variable under the
following XPaths:
I think I see what went wrong by looking at the documentation.
The value as shown in onehost show -x
is now labeled FREE_MEM instead of FREEMEMORY.
(The current docs also correctly show the variable as FREE_MEM).
I will edit my template and see if that has an effect.
Also it looks like RANK is
On Thu, Oct 30, 2014 at 2:57 PM, Steven Timm t...@fnal.gov wrote:
I think I see what went wrong by looking at the documentation.
The value as shown in onehost show -x
is now labeled FREE_MEM instead of FREEMEMORY.
(The current docs also correctly show the variable as FREE_MEM).
I will edit
On Thu, 30 Oct 2014, Ruben S. Montero wrote:
On Thu, Oct 30, 2014 at 2:57 PM, Steven Timm t...@fnal.gov wrote:
I think I see what went wrong by looking at the documentation.
The value as shown in onehost show -x
is now labeled FREE_MEM instead of FREEMEMORY.
(The
Upgrade scripts update VM templates in the OpenNebula database but not
running VMs, maybe this is the problem.
We've missed some variables, but for these ones, take a look to the upgrade
script 4.4.1_to_4.5.80.rb. The following should be updated:
gsub(TOTALCPU,
Under OpenNebula 3 we have been using RANK=FREEMEMORY
to launch the next virtual machine on the hypervisor which
has the most memory available at the time. I am using the
same in OpenNebula 4.8 but it does not appear to be working,
even though FREEMEMORY is still a documented selection variable
