Thank you for this constructive argument
Have a nice day.
Thank you for this constructive argument
Have a nice day.
This should work:
xe vm-param-set uuid="$uuid" \
xenstore-data:vm-data/ip="$ip" \
xenstore-data:vm-data/netmask="$netmask" \
xenstore-data:vm-data/gateway="$gateway"
Optionally the default DNS server can be replaced as well:
xe vm-param-set uuid="$uuid" xenstore-data:vm-data/dns="$dns"
Don't forget to restart the XOA afterward!
@markhewitt1978 Hi, thank you for your feedbacks!
We are aware that this limitation bothers a lot of users and we have plan to address that in the next major version of XO.
XO 5 was already a major improvement over its predecessor because it allows viewing and handling a much bigger infra.
XO 6 will go further in this direction by introducing a tree view and the possibility to edit and handle many objects at the same time.
@Danp That may not be directly to script but to the external environment: SMB works much better if cifs-utils
is installed on the system, something that is present on our doc but might be missing in some install scripts.
We have no animosity whatsoever regarding these scripts but we prefer our appliances (or even manual installs from our documentation) because we understand much better what's going on and it's easier to replicate and fix the issues
Regarding your idea of including the commit identifier for the source version, that's not a bad idea, a (as simple as possible) implementation in a PR would be welcome
@M92 There is now a /groups
collection which lists all the groups and two new collections, /groups/:id/users
and /users/:id/groups
which list respectively all users in a group and all groups a user belongs to.
These new collections have the same behaviours than the others, which means they accept the fields
, filter
and limit
parameters.
And yes the limit
parameter should work correctly, let me know if you have any issue.
@M92 Hello, no, groups are not exposed at this time, will do it ASAP.
@olivierlambert Done: https://github.com/vatesfr/xen-orchestra/commit/33b45d2eda2ce6d8071541da246bdcfd06b133b8
It's not perfect but that should help
Example:
vm.start
{
"id": "123e4f2b-498e-d0af-15ae-f835a1e9f59f",
"bypassMacAddressesCheck": false,
"force": false
}
{
"errors": [
"R620-L3: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)",
"R620-L1: HOST_NOT_ENOUGH_FREE_MEMORY(216430280704, 18778341376)",
"R620-L2: VM_REQUIRES_SR(OpaqueRef:21fa00fc-62ce-4694-8b49-fcecd600a89e, OpaqueRef:4dd615a7-9a8c-4698-aceb-c10f782321c8)"
],
"message": "",
"name": "Error",
"stack": "Error:
at Xapi._startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1358:15)
at Xapi.startVm (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xapi/index.mjs:1393:7)
at Api.callApiMethod (file:///home/julien/dev/vatesfr/xen-orchestra/packages/xo-server/src/xo-mixins/api.mjs:307:20)"
}
@fataugie Should be fixed, let me know if there are any issues left!
https://github.com/vatesfr/xen-orchestra/commit/194db8d0dd28ccfd058c97e8c16b32d853b26cf8
Yes, this is likely related to the undici
changes even though I don't know yet how, I will investigate today.
@Gheppy bfb8d3b has introduced a number of issues, but 6c16055 should have fixed most of them, please test and let me know.
@jr-m4 You're saying that git
no longer updates the repo`?
What's the git pull --ff-only
error message?
@Mathieu Interrupted means that XO was stopped (abruptly) during the backup run, it has no information why just that the backup run could not finish.
As @Danp said, in this case you need to check out the pool's and host's logs to figure out why it crashed.
@JamfoFL I have absolutely no idea how this error could be related to the version of Node, it really looks like an old version of xo-server which did not support the creation
param.
If you cannot reproduce, let's close this for now.
@magentinos All collections are listed when you get /rest/v0
, amongst them there is the vm-templates
collection.
It has likely nothing to do with Node's version.
@JamfoFL Make sure your xo-server is up-to-date on master, both rebuilt and restarted.
Yes, that was merged 4 days ago: https://github.com/vatesfr/xen-orchestra/pull/7388