VM Autostart order
-
I'm just getting my head around xcpng/xo after spending a fair few years in esxi and proxmox.
I'm trying to understand how I can control the order in which VMs start and shutdown.
eg, I want XO up first, followed by any primary services followed by 'the rest'.
proxmox has the concept of both order and delay. Is there a similar mechanism or a different way of achieving this in XO?
-
Hi,
You can have a boot delay in the XO/Advanced VM tab (if I remember correctly). "Start delay (seconds)".
-
@olivierlambert Yes I was playing around with that, but I couldn't seem to get it behaving properly, so I went looking through the doco, and then came here. I must be missing something.
Are VMs started in random sequence or will everything will boot storm?
If I add delays, how can that control the order with a larger sequence? -
Depends on what you call an order. It's a simple delay after sending the boot command. If you really need order, you must use vApp, and it's possible but in CLI only.
See https://www.virtues.it/2014/12/step-by-step-guide-automatically-start-a-vapp-on-xenserver/ in the paragraph: "Configuring the vApp with the XE CLI"
-
@olivierlambert said in VM Autostart order:
Depends on what you call an order. It's a simple delay after sending the boot command. If you really need order, you must use vApp, and it's possible but in CLI only.
See https://www.virtues.it/2014/12/step-by-step-guide-automatically-start-a-vapp-on-xenserver/ in the paragraph: "Configuring the vApp with the XE CLI"
Maybe helpful at some point to expose an official vApp (or XAPI interface) to setup an AutoStart order (which Vates can provide support for officially). While also exposing configuration settings via Xen Orchestra and XO Lite.
So that people coming from Broadcom VMware can more easily setup the AutoStart for VMs and the delay. Allowing them to specify what VM in a list starts first, then which start after that and so on. As well as setting the delay between them and/or for each one.
@crembz Do you agree with my above statement about what you may be looking for?
-
We tried to implement vApps but we finally decided it was too much work for how many people were requesting it. As we grow and as it's a relatively "simple" feature (it's already in XAPI), we could probably put some resources on it in the future.
-
@olivierlambert said in VM Autostart order:
We tried to implement vApps but we finally decided it was too much work for how many people were requesting it. As we grow and as it's a relatively "simple" feature (it's already in XAPI), we could probably put some resources on it in the future.
People coming from Broadcom VMware will be looking for AutoStart order features. So they can have VMs which need a special start order to boot successfully can do so. To see what I'm referring to in reference to Broadcom VMware look at this link (https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-esxi-host-client/GUID-7D66BDEE-A02E-48B8-84C8-B989D251079F.html).
A feature for the reverse may also be helpful, as well from XAPI or vAPP (with a XOA and XO Lite) interface. So that VMs which need to be shutdown with the host in special order can be setup to be shutdown in the correct order.
-
It's not that I disagree, it's just we have a finite amount of resources and we need to prioritize.
edit: but contributions are welcome if you are in a hurry
-
@olivierlambert said in VM Autostart order:
It's not that I disagree, it's just we have a finite amount of resources and we need to prioritize.
I accept that, so if it doesn't make XCP-ng 8.3 during the standard release cycle then, it would likely be a useful addition for XCP-ng 9.0.
-
@john-c said in VM Autostart order:
@olivierlambert said in VM Autostart order:
It's not that I disagree, it's just we have a finite amount of resources and we need to prioritize.
I accept that, so if it doesn't make XCP-ng 8.3 during the standard release cycle then, it would likely be a useful addition for XCP-ng 9.0.
@AtaxyaNetwork What do you think of the above?
-
@john-c It's 100% unrelated to 8.3 or 9.0, it's an XO feature. So it's about resources in XO to get the feature;
- Designed in the UI/UX
- Implemented
- Maintained
-
@olivierlambert said in VM Autostart order:
@john-c It's 100% unrelated to 8.3 or 9.0, it's an XO feature. So it's about resources in XO to get the feature;
- Designed in the UI/UX
- Implemented
- Maintained
Actually I noted above as both - vAPP or XAPI backend (XCP-ng) then a XO Lite and XOA user interface to configure the setting.
The XCP-ng 8.3 or 9.0 was referring to the backend which XOA and XO Lite talks for when configuring.
-
There's already the vApp support in XAPI since a while, so it's really only a XO Lite/XO matter.
-
@olivierlambert said in VM Autostart order:
There's already the vApp support in XAPI since a while, so it's really only a XO Lite/XO matter.
Is the AutoStart vApp along with the script already created? If not then like I said its both.
