[18:09] hi, i can't google it up, but i'm pretty sure i've seen it before, is it possible to pass url of metadata server from dhcp? afaik there was some custom option for that [18:47] ghormoon: not that I'm aware of [18:50] when would you expect that to happen exactly? normally networking is brought up temporarily in order to get to a Metadata server, so I don't see how networking (via DHCP) would be brought up not in order to contact a metadata server in order to get some DHCP option in order to figure out a metadata server to then contact [18:50] also which DataSource specifically are you referring to? [19:24] minimal: i'm using nocloud with http metadata server. i was thinking if i can somehow pass ip of the metadata server, so i don't have to put it in serial number of the vm [19:25] ghormoon: you can pass details of the metadata server, but not via DHCP [19:27] i.e. you can pass via cmdline or via DMI info (from memory) [19:28] for now, i'm using the qemu serial, is there some cleaner dmi option? [19:28] also I personally wouldn't refer to NoCloud's ability to retrieve settings from a HTTP server as "MetaData Server functionality" as it behaves slightly different from the MetaData Server functionality in other DataSources [19:30] did you check the docs for NoCloud, this is detailed there [19:33] only one i found is telling it to use some dmi variable, but still it's set in the serial, so there's nothing helping anyway [22:02] ghormoon: https://cloudinit.readthedocs.io/en/latest/reference/datasources/nocloud.html#method-1-line-configuration [22:02] "passed to an instance at boot time via *either* the kernel command line or in the serial number exposed via DMI" [22:02] note the use of the word "either" - it can be passed on the cmdline [22:56] yeah but looing from outside of qemu, it's the only practical way, if we're assuming using random cloud compatible images that user specifies ... so i'll have to stick to it