[one-users] Opennebula 4.6.2 debian - AUTOMATIC_REQUIREMENTS
Robert Tanase
robert.tanase at appnor.com
Fri Jul 25 03:05:04 PDT 2014
Hi,
I am trying to deploy VM's in a specific CLUSTER and I am facing a strange
behavior regarding AUTOMATIC_REQUIREMENTS.
By default one assigns the value CLUSTER_ID = 101 and PUBLIC_CLOUD.
I am passing in template SCHED_REQUIREMENTS = "CLUSTER_ID = 102" and
SCHED_DS_REQUIREMENTS = "CLUSTER_ID =102 ".
The scheduler - on deploy step is using "and" between automatic and user
defined conditions.
The result of this action is - VM always in PENDING state and a warning
message that the scheduler condition:
CLUSTER_ID = 101 && PUBLIC_CLOUD & CLUSTER_ID = 102
is not satisfied.
First I was using the default 1 value in sched.conf and than tried value 3
for both "policy" in DEFAULT_SCHED and DEFAULT_DS_SCHED with same result.
DEFAULT_SCHED = [
policy = 3
]
DEFAULT_DS_SCHED = [
policy = 3
]
Any ideea please? Is there any issue in my conf files?
Thank you,
*Robert TANASESoftware Developer - Appnor MSP S.A.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20140725/6003fe2c/attachment.htm>
More information about the Users
mailing list