looks like it's been taken care of automatically! i'll give it a shot today-tomorrow and confirm

@dan89 this is complete and available in v0.29.0 of the provider.

@TITUS-MAXIMUS what kind of logs would you like to see, there are none, since in sourcecode is only username and password option https://github.com/ansible-collections/community.general/blob/102a0857db23905cdfa2e2fdae531eb5d2043b9a/plugins/inventory/xen_orchestra.py#L169 and it is also required to be filled in My question is, if there is a way to login with oidc just like in this plugin [image: 1708781551664-87f8c519-f4de-4677-9590-9dba4c22a0d3-obrazek.png] https://docs.ansible.com/ansible/latest/collections/netbox/netbox/nb_inventory_inventory.html

@brodiecyber no worries and I hope you are doing better and staying healthy! Just wanted to give you an update that the terraform provider is currently testing against multiple versions of terraform (v0.14.11 and v1.6.5). The build matrix will be easy to extend to support OpenTofu testing, so we should be able to integrate that testing soon.

@twaapo @ddelnano Hi ! I think the problem is here: installation:map[method:network repository:] You need to have some value for the var "repository" After some digging in internet, XAPI code (because why not), I found the solution in an old commit in the XO repo: https://github.com/vatesfr/xen-orchestra/commit/07bf93e022a0026cacf28bf8797646361f7ea4a6 I think the var need to be set to "pxe" (i'm doing some more digging) 0 julien-f committed to vatesfr/xen-orchestra Add PXE installation method for HVM templates. (fix #436)

@AtaxyaNetwork https://pastebin.com/raw/q6qMn73M and file cloud_config.tftpl file used by the cloudinit templating. #cloud-config hostname: ${hostname} fqdn: ${hostname}.${domain} package_upgrade: true

@ddelnano My goal is to have one DHCP (on my LAN) network and 0 or 1 private networks per VM. The way I have my module setup currently I will just have one network created via Terraform. The main part I'm having trouble with is the second network being conditionally created with or without a MAC assigned. If I use a dynamic block, all the network options will be configured for each network. There's really only two situations I want the module to work for. a single network that has a MAC assigned one network with a MAC assigned and another network without a MAC assigned and on a different pool network. Until I can figure out whether it's possible I just created a second module that uses two networks. One idea I had was to use a a complex list(object) variable where each item in the list has a network name and a boolean that determines whether or not to assign a MAC from the pre-populated list but I could not get things going the right direction using the same variable for a terraform data object (used to get the ID associated with the named network) then also for the dynamic network block, having each network only assign a MAC conditionally. If that was possible it would allow much more freedom to create whatever combination of network connections I wanted. If possible it would check for a specific network name that would always get a MAC assigned and another that never gets a MAC. I am currently using the network name, from a list variable, to create a data object that provides the network ID for use in the xenorchestra_vm network block. I had trouble figuring out how to do that for two networks and be able to access the ID for each and get the MAC boolean conditionally applied to the network data object or objects.

@rochemike I had the same issue as you did. To get around this error. "│ Error: jsonrpc2: code 10 message: invalid parameters: {"errors":[{"instancePath":"/VIFs/0/mac","schemaPath":"#/properties/VIFs/items/properties/mac/minLength","keyword":"minLength","params":{"limit":1},"message":"must NOT have fewer than 1 characters"}]} │ │ with xenorchestra_vm.rbbmspcs2, │ on vm-windows.tf line 19, in resource "xenorchestra_vm""rbbmspcs2": │ 19: resource "xenorchestra_vm""rbbmspcs2" {" I modified the tf file to pass a mac_address network { network_id = data.xenorchestra_network.cladevops01net1.id mac_address = be:d0:74:96:5a:66 } It would then go and create the VM but once created. I'd log into XO, delete the VIF and readd it to get the randomized MAC address. Please note that I also tried mac_address = null and mac_address = random which also failed. Hope it helps.

@mlustosa apologies for the slow response on that issue. I'm hoping to around to addressing that within the next week or so and thanks for posting the workaround on the related issue.

Hi @slynch, I unfortunately don't have any experience with Talos Linux. It seems like a very promising project. Creating packer images with the xenserver packer plugin is OS dependent. The Ubuntu and CentOS examples provided in the repo use autoinstallation and kickstart respectively. Is Talos Linux based on an existing distro that has an existing unattended / automatic install solution? I think the key to accomplishing this is using an off the shelf auto install tool or finding something that will work for Talos. Talos's nocloud data source will likely be part of this solution, however, for the existing examples it's just a means for configuring the auto install tool for the target distro. There are two platforms they support that they document using Packer - Hetzner and Upcloud - but I can't figure out how to use that knowledge to get this to work with packer-plugin-xenserver. While I'm not familiar with the the Hetzner and Upcloud packer plugins, it seems there "examples" are essentially booting a VM and then dd'ing the raw.xz file over top of a disk device. So unfortunately I don't think those examples will be useful for implementing this with the xenserver packer plugin. [image: 1680243202599-screenshot_20230330_231257.png]