| aciba | meena: ntp, rsyslog and set_passwords (at least) have something to with distro.manage_service and are used in all distros | 09:12 |
|---|---|---|
| meena | aciba: re set_passwords: https://bugs.launchpad.net/cloud-init/+bug/1989743 | 11:14 |
| ubottu | Launchpad bug 1989743 in cloud-init "cc_ssh: sshd is not enabled on *BSD" [Medium, Triaged] | 11:14 |
| minimal | meena: isn't it the case that when someone is preparing a cloud-init enabled disk image they have various tasks to do (like enabling sshd) in addition to just installing the cloud-init package? | 11:17 |
| meena | minimal: i reckon so… i'm just really annoyed that the official FreeBSD vm images don't do that. | 11:18 |
| meena | minimal: they do it in the CI images | 11:18 |
| minimal | meena: official FreeBSD VM images in general or official FreeBSD cloud-init images? | 11:20 |
| meena | minimal: there's official FreeBSD cloud-init images? | 11:20 |
| minimal | meena: I don't know, you tell me :-) | 11:20 |
| meena | (i meant the former: https://www.freebsd.org/where/ ) | 11:21 |
| minimal | so then whomever creates a FreeBSD VM image with cloud-init should enable the ssh daemon as part of preparing such an image... | 11:21 |
| meena | the BASIC-CI image, which only exists for amd64, has ssh enabled, none of the others do | 11:21 |
| meena | fuckin sendmail is enabled, but not sshd | 11:22 |
| meena | (the argument goes: sendmail is only an outgoing service, sshd is an incoming service, so it's a danger… blah blah blah) | 11:22 |
| minimal | doesn't sound like a cloud-init though, sounds like a FreeBSD preparation issue | 11:24 |
| meena | minimal: yeah, I'll try to fix some of it with documentation, for people who are moving into clouds not officially supported yet, but yeah, it's just very annoying | 11:25 |
| minimal | meena: when I create cloud-init enabled images for Alpine there's a lot of stuff I need to do in OS config in addition to just installing the cloud-init package | 11:26 |
| meena | minimal: aye | 11:33 |
| ananke | Just to double check, because I haven't found any relevant documentation: there is no module that can create symlinks? other than the runcmd/etc? | 12:15 |
| meena | ananke: doesn't look like https://cloudinit.readthedocs.io/en/latest/topics/modules.html#write-files can | 12:16 |
| meena | ananke: there's also bootcmd ;) | 12:17 |
| ananke | yeah, I was first looking at write_files, hoping I was missing something | 12:17 |
| meena | i would still check the source in case there's a feature (exploit) hiding somewhere | 12:18 |
| ananke | I was just hoping to avoid having a separate write_files for what's essentially the same content (and space in user-data is limited) | 12:18 |
| === janitha5 is now known as janitha | ||
| === janitha7 is now known as janitha | ||
| === t0days_n3ws is now known as themachine | ||
| meena | hrm… | 20:52 |
| meena | it looks like the manage_service should go into distros/openbsd.py https://github.com/canonical/cloud-init/pull/1758 which then makes testing… hard… | 20:53 |
| ubottu | Pull 1758 in canonical/cloud-init "Distro manage service: Add OpenBSD support" [Open] | 20:53 |
| meena | we don't have any test_openbsd.py yet… | 20:53 |
| Minghe | Hello folks, My name is Minghe and from Microsoft. I am currently working Mariner OS (Microsoft internal Linux OS) | 22:07 |
| Minghe | I am wondering there is an instruction how to make cloud-init to support a new distro upstream? | 22:08 |
| minimal | Minghe: I don't think there's any specific docs for adding a new distro. You'd like want to add a new mariner.py file in cloudinit/distros/ for distro-specific stuff and look at which of the c-i modules in cloudinit/modules/ could be easily (i.e. no/minimal changes) supported by Mariner | 23:41 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!