[07:12] <Rohit31> HI , I wanted to create multiple dns entry for no cloud datasource using eni legacy network configuration
[07:13] <Rohit31> this is how I am passing in the yaml -       dnsservers:
[07:13] <Rohit31>         - 10.184.77.31
[07:13] <Rohit31>         - 10.184.77.32
[07:13] <Rohit31>         - 8.8.8.8
[07:14] <Rohit31> the corresponding interface file which is gnerated is showin entry like - [Network]
[07:14] <Rohit31> DHCP=no
[07:14] <Rohit31> DNS=[10.184.77.31,10.184.77.32,8.8.8.8]
[07:15] <Rohit31> but the same is not seeing applied in resolvectl command, if I pass only one that works and if I manually edit 10-cloud-init-eth0.network file like
[07:15] <Rohit31> DNS=10.184.77.31
[07:15] <Rohit31> DNS=10.184.77.32
[07:15] <Rohit31> both gets applied
[07:16] <Rohit31> can someone please help me over here how can I apply more than one dns servers for no cloud datasource using eni legacy network configuration
[07:50] <Rohit31> have anyone tried something around this?
[09:03] <minwi> hi folks, I'm wondering if anyone was able to configure cloud-init to send ipv6 duid ll client id advertisement in an ipv6 environment... I've seen https://github.com/canonical/cloud-init/search?q=DHCPV6C_OPTIONS&type=code the only DHCPV6_OPTION available is '-S' and in this case for duid ll it requires to be '-D LL'. Thanks!
=== cpaelzer_ is now known as cpaelzer
[19:19] <henk> hi, I’m running a vm with qemu and a configdrive with a user-data.yaml http://ix.io/3UDK. still ens3 is configured for dhcp. I think I’m not understanding how to do the network-config correctly. I read https://cloudinit.readthedocs.io/en/latest/topics/datasources/configdrive.html and the first two sentences already confuse me because their phrasing doesn’t make any sense to me: »By default,
[19:19] <henk> cloud-init does always consider this source to be a full-fledged datasource. Instead, the typical behavior is to assume it is really only present to provide networking information.« first sentence says "it does something" so starting the next sentence with "instead" confuses me. Is there a typo, a missing "not" maybe? any ideas about what’s wrong with my user-data.yaml? everything but the network
[19:19] <henk> config is applied …
[19:22] <minimal> henk: any reason why you're using configdrive? what's your DataSource?
[19:23] <henk> https://cloudinit.readthedocs.io/en/latest/topics/network-config-format-eni.html indicates that I am supposed to use something like "renderer: 'legacy'" somewhere but I don’t find where
[19:24] <henk> minimal: hm, well, I’m just getting started with cloud-init, so I’m not so sure. It seemed to be the best suited approach given my limited knowledge.
[19:24] <henk> minimal: I’m not aware that I have a datasource o_O let me read up on datasource, maybe I can give a better answer then.
[19:24] <minimal> are you just running qemu locally? In that scenario I use NoCloud as the datasource
[19:25] <minimal> which works in a similar way but with a couple/few YAML files on a suitably setup ISO or partition
[19:26] <henk> minimal: ah, yes, I am. and I use configdrive as my datasource. I guess …
[19:27] <henk> I have the yaml http://ix.io/3UDK and create an iso from it that I pass to qemu with »-drive file=/home/vm-redmine/cloud-config.img,index=1,if=ide,media=cdrom«
[19:28] <minimal> I tend to associate cloudconfig with OpenStack
[19:28] <minimal> https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
[19:28] <henk> cloudconfig? do you mean configdrive? sorry, I don’t follow what you mean with cloudconfig
[19:29] <henk> yeah, I’m reading about it, sounds like that might be easier (:
[19:29] <minimal> oops, yeah I meant configdrive
[19:29] <minimal> what's your distro?
[19:29] <henk> thanks, I’ll read about and try it and see where that gets me
[19:29] <henk> debian
[19:30] <minimal> ok, install the cloud-image-utils package which will give you the cloud-localds package
[19:31] <minimal> you can then use cloud-localds to take meta-data, user-data, and either v1 or v2 network-config files and create an ISO file (which then you can use instead of the cloud-config.img file you currently have)
[19:33] <henk> »cloud-localds seed.img user-data.yaml« is what I use to create the current iso
[19:34] <minimal> so its not configdrive then its nocloud you're using?
[19:35] <minimal> so then put your network stuff in a separate network-config file (as mentioned in the NoCloud link I sent you)
[19:37] <henk> hm, IIRC I was told to use "a configdrive" and read some howto that said to do that and called it a configdrive … it made sense because I was adding config using a (cdrom) drive … but now that you say that and I read the docs about nocloud and configdrive, it really does seem more like nocloud, yes. sorry for misleading you
[19:38] <henk> yes, I’ll definitely have to read more about nocloud. I was hung up on configdrive docs and didn’t even consider any other datasources … thanks for pointing me the right way (:
[19:55] <henk> hum, cloud-localds does not allow me to add anything but user-data and meta-data? so to add a network-config file I have to build the iso myself? or put the network-config in meta-data. is that all correct or am I missing something?
[20:11] <minimal> henk: I use something like this:
[20:11] <minimal> cloud-localds --verbose --network-config=network-config-v2.yaml dhcp-seed.iso user-data.yaml  meta-data.yaml
[21:04] <henk> minimal: huh, thanks, the manpage does not mention that but --help does o_O