| meena | SuperLag: can you show us the logs? | 17:51 |
|---|---|---|
| SuperLag | sorry meena, just now seeing this… | 20:29 |
| SuperLag | https://dpaste.com/AJQ4FGXD8 and https://dpaste.com/3WM76A6MG | 20:29 |
| holmanb | minimal: does `cloud-init analyze` work on alpine? | 22:45 |
| holmanb | I'm curious if the author of this page[1] meant to say: | 22:46 |
| holmanb | "The analyze subcommand only works on systemd-based distros." | 22:46 |
| holmanb | [1] https://cloudinit.readthedocs.io/en/latest/explanation/analyze.html#availability | 22:46 |
| holmanb | nevermind, I see the calls to systemctl this is very tightly coupled | 22:52 |
| holmanb | and in theory this would work on gentoo/systemd too | 22:52 |
| holmanb | ... if cloud-init had better gentoo support | 22:52 |
| minimal | holmanb: blame, show, and dump work on Alpine, it's just "boot" that doesn't due to its reliance on systemd | 22:54 |
| minimal | I briefly looked at it a month or 2 ago thinking of getting it working but didn't dig deep enough to work out what changes were needed | 22:55 |
| holmanb | minimal: gotcha, nice | 22:55 |
| holmanb | thanks for the information | 22:55 |
| minimal | it's on my long list of things to work on lol | 22:56 |
| holmanb | the neverending list :P | 22:57 |
| minimal | BTW am trying to figure out python gpep517 support | 22:57 |
| minimal | holmanb: yeah I recently added both the lxd DS and cc_lxd to that list ;-) | 22:58 |
| holmanb | ah nice | 23:02 |
| holmanb | how good is lxd support on alpine? | 23:02 |
| minimal | I'm new to lxd myself, only recently spun it up on a VM (to initially test containers) | 23:03 |
| holmanb | gotcha | 23:03 |
| holmanb | I like it | 23:03 |
| holmanb | it's nice | 23:03 |
| minimal | and from a quick look at the LXD DS it seems some Alpine-specific changes needed, e.g. the sock file is not in the usual place | 23:04 |
| holmanb | the other day I was trying to use it on an old gentoo server of mine and got stuck on subuid/subgic configuration - didn't work out of the box | 23:04 |
| holmanb | but also I didn't try debugging for very long | 23:04 |
| minimal | Alpine actually has 2 versions packaged - package lxd is 5.0.2, package lxd-feature is 5.19 | 23:05 |
| holmanb | gotcha, sock file should be easy enough to work around I assume | 23:05 |
| minimal | and they're not identically setup (2 different maintainers) | 23:05 |
| holmanb | lxd on ubuntu has been snap-only for a while - no deb is maintained | 23:05 |
| holmanb | hrm, 2 maintainers for different versions of the same package sounds problematic | 23:06 |
| minimal | it's the "usual" situation of someone supporting/maintaining a "stable" version and someone else wanting the latest/greatest | 23:06 |
| holmanb | gotcha | 23:07 |
| holmanb | if you feel like a quick docs review https://github.com/canonical/cloud-init/pull/4563/files | 23:07 |
| -ubottu:#cloud-init- Pull 4563 in canonical/cloud-init "Docs Correction" [Open] | 23:07 | |
| minimal | do you know anything about python gpep517 at all? | 23:08 |
| holmanb | uhhhh, a tiny bit | 23:08 |
| holmanb | wait is gpep a thing? | 23:08 |
| holmanb | I thought it was a typo before | 23:08 |
| minimal | its a "setup.py replacement" | 23:08 |
| holmanb | but you did it again and now I'm second guessing myself | 23:08 |
| holmanb | yeah I pushed a package to pypi a while ago that used pep517 | 23:09 |
| minimal | so using "gpep515 build-wheel --wheel-dir .dist --output-fd 3 3 3>&1 >&2" to build cloud-init | 23:10 |
| minimal | and then apparently "python3 -m installer -d "$pkgdir" .dist/*.wml" to package it up | 23:10 |
| minimal | which is how rthe numerous Alpine python packages do this, except this result in *ALL* the cloud-init stuff (including etc directory) being placed inside the site-packages directory | 23:11 |
| minimal | had a scan of the gpep517 and the python installer modules docs and am none the wiser lol | 23:12 |
| holmanb | yeah it's... confusing | 23:13 |
| holmanb | and our setup.py does some random stuff like call external scripts for templating | 23:13 |
| sam_ | gpep517 is a frontend we made to try paper over the mess | 23:14 |
| sam_ | https://github.com/projg2/gpep517 | 23:14 |
| sam_ | alpine started using it too because it's good | 23:14 |
| holmanb | howdy sam_ o/ | 23:14 |
| sam_ | hi! | 23:14 |
| minimal | I started looking at gpep517 as a side action of trying to figure out the recent "YAML parsing errors of systemd template files" that I've been seeing with c-i master (but NOT with previous releases), still haven't haven't figured that one out yet | 23:15 |
| holmanb | > It is the tool of choice for a world that does not revolve around pip and venvs. | 23:16 |
| holmanb | XD | 23:16 |
| holmanb | I like it | 23:16 |
| minimal | sam_: Hi. Looking at examples of other Alpine packages I couldn't figure out how to pass extra options to "python3 -m installer" packaging stage that I currently pass to "python3 setup.py install" (like "--init-system=sysvinit_openrc") | 23:17 |
| sam_ | https://github.com/projg2/gpep517/issues/10 | 23:19 |
| -ubottu:#cloud-init- Issue 10 in projg2/gpep517 "how to pass setup.py arguments" [Closed] | 23:19 | |
| sam_ | (https://github.com/projg2/gpep517/issues/10) | 23:19 |
| sam_ | holmanb: yeah, it's our best effort for coping with it | 23:20 |
| sam_ | the ecosystem is kind of a mess rn though | 23:20 |
| sam_ | it's a nice idea (pep517), but it's messy rn | 23:20 |
| sam_ | the defacto stuff for what gpep517 does is 'installer' and 'build' | 23:20 |
| sam_ | and they have a tonne of deps | 23:20 |
| minimal | sam_: before you joined the convo I mentioned I'm seeing the installer currently put *everything* inside site-packages, even the etc dir that should be /etc :-( | 23:23 |
| sam_ | ... that was the next bit I was going to mention | 23:23 |
| sam_ | there's no standard way for pep517 things to install outside of site-packages | 23:23 |
| sam_ | this is probably the worst part | 23:23 |
| minimal | doh! ok, so I'll forget about gpep517 for the near future then | 23:23 |
| sam_ | what we've done for portage (because it's both a python module but we also want to install files to /etc, etc) is use meson-python in two modes | 23:24 |
| sam_ | one for pure wheel | 23:24 |
| sam_ | one for system installs | 23:25 |
| holmanb | ah, interesting | 23:27 |
| minimal | ok, now I'll go back to trying to work on what the heck is going with YAML parsing of tmpl files as mentioned in #4487 | 23:29 |
| minimal | https://tpaste.us/papW | 23:29 |
| holmanb | thanks for the context sam_, appreciate it | 23:30 |
| minimal | hmm, even just running "python3 setup.py install --help" produces those YAML errors... | 23:39 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!