- Local export function for backup: that's because how XenServer/XCP-ng work. It can't push data, it must be pulled by something (XO here). We are working on XO Proxies to avoid useless data round trip.
- If you download a VM somewhere without going with your browser, just use backup features and target a "local" remote. That's it.
- Scripting: there IS an API inside Xen Orchestra, you can also use
Posts made by olivierlambert
RE: What is miss in XO and What i like and What I like to have ;-)
RE: XOSAN - few questions :)
- This won't affect perfs a lot, the host itself doesn't use a lot of IOPS
- No, it's not really trivial with the current XOSAN technical "bricks" used
- It's not per disk but per SR (one SR used per node)
- You can grow it by adding node, not disks locally (that's a current limitation of XOSAN)
Also, now we got more knowledge on the dom0, we planned to make a new version of XOSAN in the future to remove XOSANv1 limitations, which are:
- growing only with nodes, not by disks on the local node
- limited 4k IOPS perfs
- chicken/egg problem if you boot all your infrastructure at once (XOSAN VM must be up, so it might be needed to manually plug to storage)
RE: XCP-ng Footprint Size
If you search something close to the embed world, I would suggest Xen hypervisor on a lightweight distro available (Alpine Linux?)
XCP-ng contains tools for general purpose virt platform, with XAPI, OpenvSwitch and other "large" tools useful outside embed world.