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)"
}
@olivierlambert It's a limitation of CRON patterns, to support this we need to implement it separately and design a dedicated UI.
@olivierlambert No, CRON patterns does not support this kind of scheduling.
@olivierlambert It's a limitation of CRON patterns, to support this we need to implement it separately and design a dedicated UI.
@Rhodderz I'm not able to reproduce the issue on my side.
I successfully filtered VMs by a /foo
tag and was able to filter for it (tags:/^\/foo$/
) in the REST API, either by using filter=tags%3A%2F%5E%5C%2Ffoo%24%2F
(encoded with encodeURIComponent()
) or by using filter=tags:/%5E%5C/foo$/
(encoded using encodeURI()
which does not encode /
or :
).
Thanks for the report, it should be fixed, let us know if that's not the case
https://github.com/vatesfr/xen-orchestra/commit/aa6b23c06cf2056600cdabaaa1705ab1067ed2a9
Ghost XO user authentication task has nothing to do with backup restore, it is a known bug that will likely be fixed in the next release.
@aqua-calc Not right now, this would not be a trivial change and we have other priorities at the moment
@olivierlambert Any opinions on this?
@Rhodderz First of all, this filter
param is using the same syntax as xo-web and there is documentation on it: https://xen-orchestra.com/docs/manage_infrastructure.html#live-filter-search
Can you show me an example of your filter that is not properly working and I'll try it directly in xo-web?
@aqua-calc No, XO currently only supports basic CRON patterns.
@infodavid It's an opaque identifier, it just have to match between schedules
and settings
.
@infodavid No, the debug mode will show calls to the JSON-RPC API which is the original XO API used internally, xo-cli
uses the same API by default, unless using the xo-cli rest
command.
The JSON-RPC API and the REST API are completely different, the first one is the oldest and most complete one but was not intended for external use.