XCP-NG / XO Packer Plugin
-
Apologies if this is the wrong category but I am currently using the "XenServer packer.io builder" forked by ddelnano which according to the hashicorp docs says "This is a fork of the original, and recommended by the developers of XCP-NG". Just curious if there were any plans to have the vates team contribute or maintain the plugin? I'm very grateful for the work that ddelnano has put in, it just seems like over the past couple months there hasn't been much activity on the management side of the repo and would hate to see it go down the same path of the original repo. I also saw there was some talk about creating a completely new plugin using the XO API by @olivierlambert. I would be more than happy to contribute some time to the project. I just personally don't know the status of the XO API or the future of the existing plugin and didn't want to devote time to something that is going to be forgotten about. I would love to see this maybe even be a community effort like others have talked about in the past and like how the terraform plugin was made.
Sorry for the wall of text but any advice would be greatly appreciated as I am currently migrating all of our hypervisors to xcp and would like to approach the new infrastructure from a IaC standpoint as much as possible.
-
Hi,
We have plans to get a packer plugin for XO API. It's not not yet in the active work but in the backlog
-
@olivierlambert Thanks for reaching out so quickly, is the API at a state where it would be stable enough to start to develop a plugin around it? Or is it in the backlog due to the constantly changing API
-
So if you use our "internal" API (websocket with JSON RPC), it's rather stable
The REST API isn't mature enough to be used in a complex scenario
-
@olivierlambert Just replying to keep on watching !
-
BTW, we are adding async actions in the REST API (VM actions) plugged to our new task system.
-
@olivierlambert If I'm correct, this API system is written in OCaml, right ?
-
On XCP-ng side, yes. But the goal is to rely on XO API as an entry point for everything instead of individual host API.
-
Very cool ! Will a great move relying on a single entrypoint.
