Hello @coolsport00
I'm unable to reproduce the issue on my side.
Can you confirm that the issue persists on the latest version of XO-Lite? (v0.14.0)
Have you imported any ISOs into your SR ISO?
Hello @coolsport00
I'm unable to reproduce the issue on my side.
Can you confirm that the issue persists on the latest version of XO-Lite? (v0.14.0)
Have you imported any ISOs into your SR ISO?
Hi.
A PR is open: https://github.com/vatesfr/xen-orchestra/pull/8900
If anyone can confirm that the issue is fixed, that would be great. Thanks.
Hi @Andrew.
This PR should fix your issue https://github.com/vatesfr/xen-orchestra/pull/8854
This is normal, as the tasks
endpoints are in the old REST API (undocumented by Swagger).
We are gradually migrating to the new REST API to document all endpoints.
Hello @DevFlint.
/rest/v0/tasks/:id
exists. It's not yet documented in Swagger, but it does exist.
FYI, "actions" endpoint are specific.
They can be executed asynchronously (which is what you're currently doing). In this case, a task is returned and needs to be monitored. Use /rest/v0/tasks/:id
for this.
You can also execute your action synchronously by using sync=true
as a query parameter. In this case, the VM ID will be returned in response.
This should normally be documented in Swagger. If it's not clear in the documentation, we can improve it
Hi.
I confirm that no actions are currently available for hosts.
Hi @eeldivad
You can use the json
flag. xo-cli rest --json get vdis
Hi @irtaza9
You have a typo in your vm-templates URL.
fields
instead of field
Hi @irtaza9.
The REST API is only available for admin users.
It is planned to handle other types of users in a few months
Hi @irtaza9
FYI, for about 2 years, VMs expose a creation
field:
"creation": {
"date": string,
"template": string,
"user": string
},
With this you can filter VMs by creation.user
to list only VMs created by a user.
/rest/v0/vms?filter=creation:user:<user-id>
I will create a card for this feature request to discuss with the whole XO team. I will keep you updated here
Hi @rtjdamen
This should be doable using xo-cli
.
xo-cli backupNg.runJob id=<your-job-id> schedule=<your-schedule-id> vm=<your-vm-id>
@RS if you are using XO from source, you need to change your branch and rebuild XO
Hi @RS
Just to let you know, there is a branch available to test RPU/install patches with XenServer 8. (xs-8-install-updates
)
Feel free to test and give feedback. Thanks