Start order, delay, timeout relationship limited to single node

[boo]

I have four nodes in a cluster. Of primary concern in the startup relationship between the Windows DCs and the file server (which preferably starts after the DCs).

Node 1 = Windows DC1 KVM
Node 2 = Windows DC2 KVM
Node 3 = Windows file server KVM
Node 4 = other stuff.

If the VMs are on the same node, then the "Start/Shutdown order" behaves as expected and delays work.

However, playing around with the "Start/Shutdown order" across nodes doesn't have any affect. I have concluded I cannot make Node 3 (Windows file server) KVM delay-start based on Node 1 (Windows DC1).

Is my conclusion valid or did I miss something basic?



---- Version information ----
pve-manager: 2.2-32 (pve-manager/2.2/3089a616)
running kernel: 2.6.32-16-pve
proxmox-ve-2.6.32: 2.2-82
pve-kernel-2.6.32-16-pve: 2.6.32-82
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-34
qemu-server: 2.0-71
pve-firmware: 1.0-21
libpve-common-perl: 1.0-41
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.3-10
ksm-control-daemon: 1.1-1

 

[dietmar]

There is no ordering between different nodes.