Hi! We introduced a bug in commit 59e6868 causing "Page not found"s and fixed it in commit 6e52794.

I already opened one: https://github.com/vatesfr/xen-orchestra/issues/4882.

pdonias created this issue in vatesfr/xen-orchestra

closed [VM] Network: show IP addresses in front of their VIFs #4882

We're showing all the IP addresses reported by the VM's guest_metrics, and they're not sorted in any specific way, indeed. We could change that and show each address in front of the corresponding VIF.

I'm not seeing any. And I don't think this would be fixed by @julien-f's recent change on xo-server-xoa since it should already use the configured proxy by going through the updater.

/cc @Mohamedox

https://github.com/vatesfr/xen-orchestra/issues/4467

pdonias created this issue in vatesfr/xen-orchestra

closed Hide legacy backup menu entry #4467

@julien-f We could also completely remove the menu entry and simply keep showing the legacy backups (if there are any) in Backup NG like we already do.

@hoberion This should be fixed since XO 5.48 (xo-web 5.61.1)

@hoberion said in notifications:

@pdonias said in notifications:

Hi @hoberion, what version are you using?

xo-server 5.60.0

xo-server 5.60.0 was shipped with XO 5.47. Could you update your XOA and confirm that it fixes it? It should happen once more after the update and then it shouldn't happen any more.

Hi @hoberion, what version are you using?

Hi @BeDazzleMe,

Can someone please point me in the right direction or maybe provide an example of a working webhook to start or restart a VM ?

web hooks allow you to be notified when something happens in XO, not the other way around, at least for now. You can find an example there: https://xen-orchestra.com/docs/advanced.html#request-handling.

I already opened one: https://github.com/vatesfr/xen-orchestra/issues/4882.

pdonias created this issue in vatesfr/xen-orchestra

closed [VM] Network: show IP addresses in front of their VIFs #4882

We're showing all the IP addresses reported by the VM's guest_metrics, and they're not sorted in any specific way, indeed. We could change that and show each address in front of the corresponding VIF.

@badrAZ Do you have an idea? It sounds related to the changes for the audit.

Hi @akurzawa, this would be quite a big feature, please open an issue if you have something precise in mind (a list of possible actions, what could trigger a workflow, ideally some use cases that couldn't be done without it, etc.). Also, a lot can probably already be done with XO's Web Hooks, xo-cli and a third party workflow tool in between.

For now, all you get in the webhook request are the API call parameters and result (and a few other things). This is a generic behaviour that doesn't depend on what the call does. If you need some more specific information, your webhook handler can, for example, make a call to XO's API to fetch that information.

Could be great if wrapper could be implemented directly in XOA

Like a generic configurable wrapper in XO for any webhook target? How do you imagine it?

Hi @JCastang, what kind of data would you like to pass? Static data? Because all the dynamic data we could think of is already sent in the request body.