We have now 2 clusters (100 and 102) with nearly the same capabilities except a Lizardfs datastore.
We have older templates/images in a shared qcow2 datastore, usable on both clusters but I would like to restrict some of these template to the old cluster for now.
SCHED_REQUIREMENTS=CLUSTER_ID=\"100\"" to a template but this parameter completely disappear in the running VM and the scheduling is not impacted.
I made a test by uncommenting the
/etc/one/oned.conf and this time the scheduling is properly impacted and I found the attribute in
onevm show -x ID | grep SCHED_REQUIREMENTS.
Our templates are generated by a jenkins user which is not
Is there a way to fulfill the following conditions:
SCHED_REQUIREMENTScan be set by a non
SCHED_REQUIREMENTSmodify the scheduling policy
Versions of the related components and OS (frontend, hypervisors, VMs):
Steps to reproduce:
In a dual host environment, with one noted as disabled
- Define a template with
SCHED_REQUIREMENTSto select the disabled host
- Start the VM as a normal user
- The VM is scheduled on the enabled host.
- There is no
SCHED_REQUIREMENTSin the output of
- The VM should no be scheduled because the selected host is disabled
SCHED_REQUIREMENTSattribute should be in the output of