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

PR: https://github.com/vatesfr/xen-orchestra/pull/8599

MathieuRA opened this pull request in vatesfr/xen-orchestra

closed fix(xo-server/xen-server): fix disabling an enabled but disconnected server #8599

Hi, I will fix it ASAP. Thanks

@hanzzz This PR adds the ability to run a schedule. So, a temporary workaround is to create a job, create a schedule for this job, then run your schedule.

If you are not using XO from source, you will have to wait for version 5.106

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

@irtaza9 you need to use the user-id, not the username

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

FYI, we have added this feature to our backlog

Hi
I created a card on our side to discuss this feature request.
I will keep you updated.

Hi @flakpyro
You can do xe help vm-migrate to see all available parameters and a small description.

BTW, in XO, if a network is specified for the migration, we call vm.migrate_send otherwise vm.pool_migrate.
vm.migrate_send also migrates VM's VIFs and VDIs.

Questions for the XCP team:

• What happens if you do a vm.migrate_send but the destination SR for the VDIs is the same?
• Is there a way to call vm.pool_migrate using a specific network?

Hi @Sugarat. thanks for the report.
Can you try this branch: fix-handle-inavlid-vm-creation?
This should fix the issue

@rs Yes, this is normal. I am still working on making the installation possible via XO.