Wonderful ! 
Team - XO Frontend
Posts
-
RE: Why are transfer sizes different between XO5 & XO6?
-
RE: 🛰️ XO 6: dedicated thread for all your feedback!
Hello everyone! We need you!
We're currently designing the XO 6 UI for non-admin users, and some choices are genuinely hard to make. If you'd like to give us your opinion, here's a 30-second survey with 2 questions we couldn't settle ourselves: https://survey.vates.tech/s/cms4nrqb4005wrw01021ru6dy
Thanks!

-
RE: Deploy VM via cloud-init config
@acebmxer Thank you for your quick feedback.
-
RE: Deploy VM via cloud-init config
Hi @acebmxer,
Can you test if the branch:
fix_cloudinit_importfix your issue?
Edit: It is available on the master branch. -
RE: Xenorchestra V6 issue
@acebmxer I can confirm that, we'll fix it, thanks

-
RE: Xenorchestra V6 issue
Hi @irtaza9, I think your question is about why the size input is disabled in your screenshot, is that right? This happens because there are two types of VDIs you can use when creating a VM:
- A brand new VDI, created from scratch. You choose its size, and it will be created empty.
- An existing VDI that is already attached to the template you're using. This VDI already has content and a fixed size, so it is simply cloned during VM creation.
Your case is the second one, which is why you can't change its size.
-
RE: ACL Permissions to CPU Topology on Self-Service Resource Set
Hi @dvdwx,
RBAC is available only at the REST API level, not through the XO6 UI. UI compatibility with RBAC is currently under development.
For the topology, this is something that has been here for a long time, so I may be wrong since I don't have the full history. However, if I look at the code, creating the topology selector requires knowing how many CPUs are available in the pool.
Since a self-service user doesn't have visibility into the pool, they can't access this kind of information. -
RE: REST API create_vm returns task URL that doesn't exist?
Hi @DevFlint,
tasks are now correctly visible in the swagger documentation -
RE: How to revert VM to snapshot
Hi @slavavrn,
FYI, its now possible to revert a snapshot via the REST API.
POST /vms/:id/actions/revert_snapshot
And the body of the endpoint:{ "snapshotId": <snapshot-id> "snapshotBefore": boolean (optional) }