@abudef Indeed, the delay is in milliseconds.
XO Team
Developers of Xen Orchestra
-
RE: Automatic startup and shutdows VMs at the specified time
-
RE: Cannot find the link between virtual machine and virtual disk
@paul-besret It is indeed possible to do it but the VDI must be created as sharable, something which I believe is not currently possible on XO UI.
I'll investigate how the UI behave with such a VDI.
-
RE: Cannot find the link between virtual machine and virtual disk
@paul-besret What's your use case of this?
-
RE: Cannot find the link between virtual machine and virtual disk
@paul-besret A VDI cannot be attached to multiple running VMs at the same time, just like you cannot connect a physical disks to multiple computers.
-
RE: CBT: the thread to centralize your feedback
@rtjdamen We are investigating it as well
For the XO backend team, the next few months are focused on stabilization, bug fixes and maintenance
-
RE: CBT: the thread to centralize your feedback
@manilx The
incorrect backup size
warning is a known issue that we will investigate soon -
RE: Linkt to "Access XOA" - If Installed in Docker on a VM
Hi @Houbsi, good question. This is how it works:
- any XO instance that is connected to a pool will add some information about itself to the pool's metadata
- XO Lite reads that information to know the URL of XO's UI
In
xo-server
's config, you can force XO to report a custom URL instead of raw network information:[http] publicUrl = 'http://example.com'
However, at the moment, XO Lite doesn't support it, but it's coming soon: https://github.com/vatesfr/xen-orchestra/pull/7849
And @olivierlambert, yes, for now, any XO instance, whether it's an XOA or not, reports itself on the pool and we simply pick the latest one. But we can definitely implement something smarter in the future if necessary.
-
RE: netdata plugin wont install
@jshiells The netdata plugin is only supported on official XOAs because it relies on a locally configured netdata.
-
RE: Cannot find the link between virtual machine and virtual disk
So I understand that I have to get all the disks, then all the VMs and finally all the VBDs to be able to map, what disk is attached to what VM ?
Exactly.
Moreover, I can't wait to use the REST API in the future, but since it doesn't have enough functionality yet, we will stick to use only one third party system to avoid misunderstanding and technical debt.
As you wish, objects are the same in both APIs.