[one-users] Opennebula 4.6.2 debian - AUTOMATIC_REQUIREMENTS
Carlos Martín Sánchez
cmartin at opennebula.org
Mon Jul 28 03:46:02 PDT 2014
The automatic requirements attribute is added by the core because you are
using a vnet assigned to that cluster, or an image from a datastore
assigned to it .
If you want your VM to be able to run on any cluster, change the
vnet/datastore cluster to none (-1). Please note that the physical
infrastructure of all clusters must support all vnets/DS in cluster 'none'
(e.g. the DS must be mounted).
Carlos Martín, MSc
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | cmartin at opennebula.org | @OpenNebula
<http://twitter.com/opennebula> <cmartin at opennebula.org>
On Fri, Jul 25, 2014 at 12:05 PM, Robert Tanase <robert.tanase at appnor.com>
> 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 TANASE Software Developer - Appnor MSP S.A.*
> Users mailing list
> Users at lists.opennebula.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users