/srv/irclogs.ubuntu.com/2016/12/05/#cloud-init.txt

=== mgagne is now known as Guest51737
another_larskssmoser, I'm curious how soon you think 0.7.9 might drop...I see that there are a ton of changes to the systemd units since 0.7.8, and thinking about carrying patches vs. just waiting a bit.15:24
=== another_larsks is now known as larsks
=== Guest51737 is now known as mgagne
larsksharlowja, systemd dependencies question:  if cloud-init-local.service is Before=NetworkManager, shouldn't it also be Before=networking.service?18:42
larsksAnd similarly, if cloud-init.service is After=networking.service, shouldn't it also be After=NetworkManager.service?18:43
larsksThis may just be me being unfamiliar with the naming of ubuntu/debian systemd units...18:43
harlowjanrezinorn ^18:54
harlowjalarsks there was dragons there that nrezinorn hopefully remembers18:55
larsksharlowja, because I need to set deps correctly on the redhat legacy "network.service" as well as NetworkManager, and want to be consistent...18:56
harlowjadraggggggons18:56
harlowjalol18:56
* harlowja poked nrezinorn internally, he should be able to answer19:00
nrezinornall i remember is that on the newer cloud-init the systemd files were wrong for RHEL 719:01
mdorman_doyou have the link to the bug or patch?  This was a while ago, i’ll have tp page this stuff back into my brain19:02
nrezinornbecause its called network.service (rhel) vs networking.service (ubuntu)19:02
nrezinornthats all i remember, and i think i just made a specific file for rhel builds, but i dont think any of that is merged back upstream yet19:03
mdorman_i think taht was the only difference, too19:03
nrezinornonce i fixed the rpm build for network.service things just worked - for my super limited testing that i did lol - other things have taken my time away19:04
harlowjalarsks u trying to fix it for good i hope :-P19:05
harlowjanever again!19:05
harlowjalol19:05
larsksnrezinorn, where are your fixes?19:09
larsksharlowja, I don't know.  Because rhel and ubuntu have different service names, we can't really have a single unit file.19:10
larsksI think unit files should be part of the packages, not part of the upstream code, but smoser and I disagree on that point.19:10
harlowjalarsks right, we may need 219:10
harlowjalarsks prob disagree with me also :)19:10
harlowjai like it when code-bases can build themselves into packages19:11
harlowjaif we have 2 unit files, doesn't seem to bad19:11
larsksharlowja, I think it's a terrible idea because it requires the upstream code maintainers to also be expert package maintainers for multiple distributions.19:11
larsksOr they end up being experts in one distribution, and everyone else has to carry a list of patches a mile long.19:11
harlowjasounds like package creation is to much a PITA then19:11
harlowjaand if it requires a expert then its not done right :-P19:11
harlowjapackaging software shouldn't require experts imho ;)19:12
larsksWhich is why it should just be left to the package maintainers.19:12
harlowja(not in the 21st century)19:12
larsksWhy make upstream developers worry about those things?19:12
larsksLet the upstream concentrate on quality code, rather than making sure they have the names of depdendencies correct.19:12
harlowjai get that POV19:12
harlowjait still feels like a messed up situation19:13
larsksI dunno.  I mean, ubuntu/debian/redhat/suse/fedora/alpine/etc...everyone has there own packaging system.  I'm not sure it's possible to get everyone to settle on a single set of package metadata.19:14
larsks...until systemd introduces a packaging format, I guess.19:14
harlowjasounds like we need a package trump for president19:14
harlowjalol19:14
nrezinornmake packages great again!19:15
larsksSo here's another idea...we remove *all* distribution specific dependencies out of the unit files, and those go into separate systemd drop-in files.  This lets the distro-specific stuff be managed without needing to duplicate the entire unit file(s).19:15
harlowjak19:16
larsksnrezinorn, you mentioned that you were working on the rpm packages...what did you end up with for service dependencies?  Are those rpms somewhere I can grab them and look?19:17
nrezinornlarsks: i last poked things 2 months ago- and i dont have anything to share .  let me see if i can drop a file somewhere you can grab...you can poke it yourself (if i remember where i did all this stuff)19:29
=== mpontillo_ is now known as mpontillo
nrezinorni cant find where i put the stuff i was doing lol, it may have been on a server that got wiped...so thats fun19:35
larsksnrezinorn, thanks for looking!19:40
nrezinorni really only added the rhel files for systemd and editing some other thing, prob the makefile macros to feed in the rhel systemd files19:41
nrezinornthere was also other things not working right lol19:41
nrezinorni looked under a few rocks, sorry i couldnt find it.19:46
larsksharlowja, debian packaging question: what part of the packages/debian/* files causes the systemd unit files from the systemd/ directory to get copied into the right place?19:56
harlowjaeck, ask smoser not me :-P19:56
larsksDarn.  smoser seems to be afk today.  Or at least af irc.19:57
nrezinornill find it for you19:57
harlowjai don't do that debian stuff, ha19:58
nrezinornhttps://git.launchpad.net/cloud-init/tree/packages/bddeb?id=166df605dc9864eb163007300db7a611feb309d6  something in that lol19:59
nrezinornjsut trace it all the way down to where its copying the systemd/ folder i guess :)19:59
nrezinornah i see20:00
nrezinornso the debian packager just takes ther tarball of the source20:00
nrezinornso "it's just there"20:00
larsksnrezinorn, ugh, right, we've abused setup.py as a general installation tool.  Thanks.  I keep forgetting that.20:04
nrezinornyeah im not a fan of that stuff lol20:05
suro@harlowja: around?20:06
larsksUgh, so why does the spec file copy things in manually?  HEAD ASPLODE.20:08
nrezinornrpm spec?20:48
nrezinornit copies things becuase it has to be copied into the RPM BUILDROOT, thats how rpms work20:48

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!