@olivierlambert XO build from source listening on port 8443
The plug-in doesn't make any assumptions about the port.
Can you try with
I think @shinuza is now working on this. Don't forget to be sure you are using the latest commit.
Also, please try with XOA too in
latestchannel to compare the result.
I'm trying to find a way to schedule these long running tasks so we are not dependent on the browser staying opened and connected to XOA. Also we are looking at means to improve the export speed.
@wowi42 Hi there. It's already in the documentation:
Also, you should see an error message if it's not installed.
@tristis-oris Nope, unfortunately:
Using hostnames or ip as inventory id means there's no way to for example to: start a vm using the inventory, but you can do it using the inventory and a JSON-RPC call.
@tristis-oris Hey, so yeah. The doc was confusing, I've created a pull request to fix it.
As for your issue. It says
auto plugin: [Errno 111] Connection refused, meaning you can't connect to the API from the machine that tries to execute the inventory.
Hi there. Author of said inventory plugin.
If you ever wish to migrate you should be able to retain most of what you did on XOA side (I'm thinking tags), but you'll have something that's more standard and require less setup as long as the XOA API is accessible to the machine running the playbook.
You can keep the groups with the composable groups in your inventory plugin configuration:
simple_config_file: plugin: community.general.xen_orchestra api_host: 192.168.1.255 user: xo password: xo_pwd validate_certs: true use_ssl: true groups: kube-master: "name_label == 'kube-master'" compose: ansible_port: 2222