https://rancher.com/ logo
#vsphere
Title
# vsphere
a

adamant-kite-43734

11/24/2022, 9:04 PM
This message was deleted.
a

agreeable-oil-87482

01/10/2023, 9:45 PM
At the moment we don't parse network data, which settings are you trying to carry over? The DHCP identifier?
b

bland-painting-61617

01/10/2023, 10:17 PM
Hey @agreeable-oil-87482 Indeed, in netplan language:
Copy code
critical: true
      dhcp-identifier: mac
This is to use old fashioned mac addresses as dhcp identifiers and the critical field prevents the lease from being released upon reboot. I know this can be fed to the image using metadata or vendordata. I haven't been able to use guestinfo (I tried setting the appropriate vm configuration options) because cloud-id detects the source as nocloud instead of vmware. I'm currently thinking of baking the file into the ova. What is the
cloudinit
field for? The options passed to
cloudConfig
apply fine, but unfortunately network options get ignored by design.
It looks like the metadata can be passed via the iso file, which is what Rancher already does for userdata. Perhaps there's a way to add that extra file into the iso? https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
a

agreeable-oil-87482

01/11/2023, 12:52 PM
A couple of things I would try: 1. Configure your VM template to have this netplan config file set. Then in
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
add the line
network: {config: disabled}
so it won't alter or create a new netplan file 2. Use the user-data part of cloud-init to run a script which amends the netplan config file (or create a new one) and restart netplan.
b

bland-painting-61617

01/11/2023, 12:59 PM
Do you think I could just run a userdata script to add the
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
file and then remove the cloudinit generated netplan file, apply my own one and reboot? it would have to be early in the process to run before rke components are installed, in case the ip changes again
a

agreeable-oil-87482

01/11/2023, 1:35 PM
Could do... Better to do it in the template though
Let us know how you get on please 🙂
b

bland-painting-61617

01/11/2023, 9:13 PM
Sure, I actually had to modify the OVF anyway since it comes with VM hardware compatibility level of 10 and 13 is needed for CSI volume attachments... That part was easy since it's just an XML file; however, I did wonder if the VM version can be upgraded during clusterapi/Rancher's VM provisioning process
a

agreeable-oil-87482

01/12/2023, 7:59 AM
Currently, no. It's not something we'd want to mandate as it can have implications. You can also turn the template into a VM -> upgrade compatibility -> convert back to template
b

bland-painting-61617

01/12/2023, 10:20 AM
I was just checking, an option to optionally convert the VM version at provisioning time would be nice but it can be worked around. Considering version 10 is EOL for 2 years now, I'd actually expect the OVF to get the version bumped up sometime. Even vsphere 6.5 which is vm version 13 is EOL
99 Views