Team - XO Frontend group | XCP-ng and XO forum

pdonias

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!

MathieuRA

@acebmxer Thank you for your quick feedback.

MathieuRA

Hi @acebmxer,

Can you test if the branch: fix_cloudinit_import fix your issue?
Edit: It is available on the master branch.

pdonias

@acebmxer I can confirm that, we'll fix it, thanks

pdonias

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.

MathieuRA

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.

MathieuRA

Hi @DevFlint,
tasks are now correctly visible in the swagger documentation

MathieuRA

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)
}

MathieuRA

Hi @johnnezero and thanks for the post!

Just wanted to talk about PERMISSION SYNC.

In the REST API the "permission sync" pattern is actually handled natively by the RBAC system using selectors.

For example, if you want a role that allows a user to manage VM power state only for VMs tagged dev:

Start from the built-in role template “VMs power state manager” (just to speed up role creation, but totally optional)
Create or customize a role with the required VM power privileges (read, start, stop, reboot, etc.)
Scope each privileges using a selector like:
tags:dev
Then assign the role to your user or group

Once done, the access is fully dynamic:

Any VM with the dev tag is included in the scope
Removing the tag immediately revokes access
Adding the tag grants access instantly
No need to maintain per-VM ACL entries

The key point is that RBAC evaluates privileges at request time based on selectors.
You can also base selectors on other VM properties, not only tags (for example power state, name patterns ...).

You can find the doc here
and a dedicated forum thread here

PS: For the moment the XO6 UI does not support the RBAC system, but we are working on it

MathieuRA

Hi @rzr,
When you say, "XO still showed host 2 needing patching", does that mean XO is still showing missing patches?

If so, can you run the following command: xe host-call-plugin host-uuid=<uuid-host2> plugin=updater.py fn=check_update

Team - XO Frontend

Posts

Member List