| === esv_ is now known as esv | ||
| phunyguy | Hey all, I have a couple questions for the group. I'm new to cloud-init and have begun making my own images with diskimage-builder, for gentoo. I was poking around at the github for this project, and I don't there is much currently in the way of network config support for gentoo, via both systemd and openrc. There is a .network file that gets created, but the services systemd-{network,resolve}d | 18:09 |
|---|---|---|
| phunyguy | are never enabled. Are there any plans in the works to get this implemented? Am I missing something important where this already is, and I'm just doing something wrong? Thanks. | 18:09 |
| phunyguy | I can help develop if needed, however I am no good in Python, bash only. | 18:11 |
| blackboxsw | phunyguy: I think we can help you with functional review from a python standpoint for gentoo specific netwokring fixes, most of the networking content I'm aware of for gentoo comes from distro-specific overrides at https://github.com/canonical/cloud-init/blob/main/cloudinit/distros/gentoo.py#L63-L131. | 21:27 |
| blackboxsw | phunyguy: while cloud-init upstream team committers and generally more versed in Ubuntu/Debian/RHEL, there are a couple of active gentoo maintainers that could validate and vet some of content changes for functionality if you were to provide suggested fixes in a Draft PR | 21:28 |
| blackboxsw | phunyguy: from my perspective, cloud-init has proper network renderers definitions over in https://github.com/canonical/cloud-init/tree/main/cloudinit/net. If there are significant changesets and extensions to the way gentoo is writing out network over in distro/gentoo.py it may make sense to have an official cloudinit.net.openrc or something | 21:31 |
| phunyguy | blackboxsw: first of all, thank you so much for the detailed response. Yeah, that's where my head was going. With gentoo+systemd however, it works for the most part, just have to enable the systemd-{network,resolve}d services. | 22:01 |
| phunyguy | It's really openrc that is just not there at all from a network standpoint. | 22:02 |
| phunyguy | what would need to happen there, is on boot, something would have to scan for the interface name, then populate /etc/conf.d/net with the proper settings, and then /etc/init.d/net.lo symlinked to /etc/init.d/net.${interface_name}. I don't think it's anything more complex than that. A cherry on top would be both systemd and openrc starting the network services. | 22:03 |
| phunyguy | although that last bit isn't strictly required thanks to the changes I helped bring to diskimage-builder, which can enable services during the image build. | 22:04 |
| phunyguy | But if other distros get network enabled on boot, then I think it's fair to have ci do it for openrc too. | 22:08 |
| phunyguy | Interesting.... https://github.com/canonical/cloud-init/blob/main/cloudinit/distros/gentoo.py | 22:10 |
| phunyguy | there is a lot of openrc stuff in there, but I am not a python whiz, but my guess is something DOES exist, and my implementation just sucks, | 22:10 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!