[00:04] <pepperoni> strange, if I don't add cloud-init setting within LXD profiles, I have no other way that I know of to create them.
[00:33] <minimal> pepperoni: network-config passed to cloud-init might be used to RENAME interfaces, but cloud-init doesn't create them, the kernel/OS does (based on the QEMU settings that LXD on the host uses)
[00:36] <minimal> isn't "lxc config device add <instance_name> <device_name> nic" uses to create network interfaces for a LXD VM?
[00:46] <minimal> I'm assuming you're creating a LXD VM rather than a container
[00:58] <holmanb> pepperoni: you can init an instance with cloud-config using `lxc init <remote:image> <name> -c cloud-init.user-data=<put it here>
[00:58] <minimal> holmanb: he's asking about creating network interfaces, cloud-init doesn't do this though
[01:00] <holmanb> minimal: sure, I guess that I interpreted the second question as separate from the first one
[01:01] <minimal> holmanb: "is there a way to create an interface in a down state in cloud-init? I have several and want one to be off." - so if he doesn't reference the interface in the provides network-config then it won't be configured
[01:06] <holmanb> Ah
[01:06] <holmanb> Okay
[01:07] <minimal> unless it ends up being the "default" (sorted by MAC address?) interface picked for DHCP fallback...
[01:08] <minimal> but there's a lack of information provided, not clear if question relates to VM or Container, etc
[01:26] <holmanb>  Yeah
[01:31] <holmanb> Cloud-init spec for public review: https://discourse.ubuntu.com/t/proposed-specification-cloud-init-service-name-changes/40125
[01:32] <minimal> holmanb: I have a briefl look at the PR for that earlier and noticed it didn't cover openrc and freebsd init.d changes, only systemd files ;-)
[01:59] <holmanb> minimal: I will include those :)
=== esv_ is now known as esv
[02:22] <holmanb> minimal: done
[20:08] <pepperon1> currently, I'm creating containers with LXD, I add cloud-init to a profile and when my instance starts, I get the new interface that normally doesn't come with a container.
[20:11] <pepperon1> When I create the instance, I then add the profile to it.
[20:12] <pepperon1> Otherwise, containers only come with preconfigured eth0, and I think possibly even an eth1, but other interfaces need to be added.
=== pepperon1 is now known as pepperoni