20:04:18 #startmeeting 20:04:18 Meeting started Tue Sep 9 20:04:18 2014 UTC. The chair is jzb. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:04:18 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:04:49 #chair stickster walters dustymabe number80 oddshocks dgilmore nirik 20:04:49 Current chairs: dgilmore dustymabe jzb nirik number80 oddshocks stickster walters 20:04:52 miss anybody? 20:05:08 * nirik is lurking around 20:05:32 .hellomynameis pfrields 20:05:33 stickster: pfrields 'Paul W. Frields' 20:05:39 .hellomynameis dustymabe 20:05:40 dustymabe: dustymabe 'Dusty Mabe' 20:05:45 .hellomynameis jzb 20:05:46 jzb: jzb 'Joe Brockmeier' 20:06:05 so, it may have been a few weeks since we had have an actual meeting. 20:06:30 Yeah, congrats to walters is implicated in that ;-) 20:06:39 heh, indeed. 20:06:43 thanks =) 20:06:43 walters: glad to have you back 20:07:09 walters: the important question - are you catching up on your sleep in the office? :-) 20:07:42 heh 20:07:52 ok, nirik - last week, dgilmore pointed me at a TC6 (I think it was) compose for Atomic 20:08:06 nirik: so are we now producing Atomic images regularly? 20:08:21 with the test composes, yeah. But not nightly yet. 20:08:33 nirik: any sticking points or blockers left there? 20:08:41 .hellomynameis hguemar 20:08:42 number80: hguemar 'Haïkel Guémar' 20:08:57 not sure. I think we just need to get it added to the compose scripts. 20:09:50 If oddshocks is around... maybe he'd be inclined to help with some of the rel-eng bits too. There's a lot going on in rel-eng due to multi-product Fedora, and this is one component. 20:09:56 that's this script right? https://git.fedorahosted.org/cgit/releng/tree/scripts/run-pungi 20:10:17 or is that only for the manually-initiated composes, and something else is nightly? 20:11:12 https://git.fedorahosted.org/cgit/releng/tree/scripts/buildbranched and https://git.fedorahosted.org/cgit/releng/tree/scripts/buildrawhide 20:11:22 which call run-pungi for the pungi part. 20:11:59 * stickster amazed but not surprised by the fact that nirik seems to know everything 20:12:08 about *everything* 20:12:14 heh. I'm old. ;) 20:13:06 #info note, we are producing Atomic images regularly in test composes, not yet in nightlies 20:14:10 nirik: so - adding to the script, is this a lot of work, a formality, or...? 20:14:28 a bit of work.... 20:14:34 but nothing too vast. ;) 20:15:24 nirik: so - is that something you or dgilmore will handle, or do you need assistance? 20:15:36 assistance would be great. Patches to the releng list. 20:16:16 #info Help is needed patching the compose scripts! 20:16:24 #url https://git.fedorahosted.org/cgit/releng/tree/scripts/run-pungi 20:16:29 #url https://git.fedorahosted.org/cgit/releng/tree/scripts/buildbranched 20:16:37 any volunteers? 20:16:38 argh, wrong command. 20:16:44 #link https://git.fedorahosted.org/cgit/releng/tree/scripts/run-pungi 20:16:49 #link https://git.fedorahosted.org/cgit/releng/tree/scripts/buildbranched 20:16:55 #link https://git.fedorahosted.org/cgit/releng/tree/scripts/buildrawhide 20:17:06 jzb: I'm nominating oddshocks :-) 20:17:19 is oddshocks around? 20:17:43 He doesn't appear to be here right now -- might be lunchtime his TZ -- but I'm dropping him an email to request his help 20:17:47 OK 20:18:16 anything else on the composes? 20:18:21 I think that's pretty much it. 20:18:31 is the current compose mirrored? 20:18:39 ah, good question 20:19:01 walters: I don't think the last one was - it's just in Koji. 20:19:09 the repo is mirrored here? http://dl.fedoraproject.org/pub/alt/stage/atomic/ 20:19:34 that area is mirrored... but not by the full pile of mirrors, only some few that want to 20:20:10 #topic metalink XML, mirroring 20:20:16 (is that right?) 20:20:37 to recap from before the meeting, http://koji.fedoraproject.org/koji/buildinfo?buildID=576104 should support metalinks and has a new "summary" file 20:20:40 walters: yeah, I don't think the meetbot has perms to change the channel topic though. 20:21:02 to make this work we'd need to have the updated ostree on the compose server (should just happen via mock next run I assume) 20:21:07 #info http://koji.fedoraproject.org/koji/buildinfo?buildID=576104 should support metalinks and has a new "summary" file 20:21:11 then we need to patch the scripts to run ostree summary -u 20:21:21 both are easy 20:21:34 what's unclear to me is the next step to hook in with mirrormanager 20:21:34 cool. 20:21:48 and have it generate the XML 20:22:07 mirrormanager has a cron called 'update master directory list' where it crawls the filesystem looking for new repos/things or updated repos/things. 20:22:26 I think we need to teach that to identify ostree dirs/trees. 20:22:33 if we can iterate on this soon that'd be good, because while I *think* the metalink code will work, it'd be nice to test it in something resembling reality soon 20:22:39 ah 20:23:18 I'm not sure where it is in code, but can look/ask around. 20:23:26 a suitable pattern would probably be "repo/summary" (if there can be conditionals, if repo/objects exists too) 20:24:32 alright 20:25:15 nirik: Might be this? https://git.fedorahosted.org/cgit/mirrormanager/tree/server/update-master-directory-list 20:26:36 sounds right.. 20:29:20 * oddshocks looks around 20:29:21 once the file mapping is updated, this process would automatically handle filtering the generated XML for which mirrors carry the atomic repo? 20:29:48 sorry for being late. alarm might have been messed up by me listening to music on the phone. 20:29:50 walters: not 100% sure, but I think so. it should save it in the db and then check sites against it. 20:31:15 * stickster wonders if people are looking at code now and not really IRC :-) Sorry for derailing, if so. 20:31:18 oddshocks: you might want to scroll up 20:31:48 * oddshocks is now caught up 20:31:53 jzb, you said there had been a compose? 20:31:57 do you have a link? 20:32:03 walters: yeah, somewhere, hang on... 20:32:57 I'm glad I didn't completely miss this because I was hoping to get an update -- now that I'm done moving -- on what still needs to be done with MM, or if there is something else I could do that is higher priority. are these aforementioned scripts something I should take a look at? 20:33:45 walters: http://koji.fedoraproject.org/koji/taskinfo?taskID=7531374 20:34:06 oddshocks, we'll need to run ostree summary -u on the compose server, then MM will need to generate a metalink to the repo/summary file resulting from that 20:34:16 (in the future, there will be a GPG signing step in there too) 20:34:29 walters: I think oddshocks is asking about prior scripts as well for nightly generation 20:34:44 ah right 20:34:49 oddshocks: In which case -- yes, some help would be appreciated there too 20:35:29 oddshocks: I'm pretty sure that dgilmore has a lot going on w/ multiple Fedora products and so any script fixing you can assist with would be a good idea (and hopefully welcome!) 20:36:46 got it. are any of these completed or changed?: http://ur1.ca/i5qk7 http://ur1.ca/i5qkg 20:37:55 yep, the ostree metalink part is done 20:38:00 walters: cool 20:38:14 are all of these scripts in the releng scripts repo or..? 20:39:05 i think so 20:39:20 20:16 < stickster> #link https://git.fedorahosted.org/cgit/releng/tree/scripts/buildbranched 20:39:23 20:16 < stickster> #link https://git.fedorahosted.org/cgit/releng/tree/scripts/buildrawhide 20:39:43 oddshocks: ^^ I think those are what we're talking about? 20:40:10 yep. those two for nightly composes 20:40:41 oddshocks: so we can put you down for tackling adding Atomic? 20:41:02 sure, I'll go at it 20:41:49 #action oddshocks work on adding Atomic to releng scripts 20:42:10 walters: any other blockers or issues right now you're aware of? 20:43:05 how we pre-configure the generated images to point to the mirrors is as yet somewhat fuzzy to me 20:43:21 i had been waiting to tackle this until we had content mirrored and metalink XML generated 20:43:38 walters: for updates, you mean? 20:43:40 basically in mainline, we ship a fedora-release package which contains yum repositories which link to metalinks 20:43:41 yes 20:44:29 walters: on a scale of 1-10, how bad is it if they have to adjust after the alpha to get updates? 20:44:36 3? 20:45:04 anyways not a blocker to my knowledge 20:45:04 walters: with 1 being "no worries" and 10 being "you're being eaten by a shark"? 20:45:12 heh 20:45:25 OK 20:45:36 Is this something we might be able to sort out before the beta? 20:45:43 hopefully yes 20:45:46 ok 20:45:48 so will the alpha image contain a location where we can get updates (during the alpha)? 20:46:14 I would "vote" to have a non-mirrored location for the alpha if we can. 20:46:14 I know that might sound funny but it would be nice to have an 'update' to perform for testing purposes 20:46:29 dustymabe: right. That is sort of core functionality. 20:46:31 jzb, yeah, it's pretty easy to provide that 20:46:47 i'm a bit more concerned about the default experience/layout 20:48:39 for the alpha, I think if Docker + Cockpit are working, that's a good start. 20:48:47 but I agree. 20:49:41 so - let's try to answer for next week how we get to pointing to mirrors? 20:49:51 yep 20:50:31 any other topics this week? 20:50:35 #topic open floor 20:51:13 dustymabe: anything on your end? 20:51:17 stickster: ^^? 20:51:22 yeah actually 20:51:33 missed the meeting didn't I? 20:51:37 a few questions 20:51:54 so in the test images from koji I notice we are using an LV structure 20:52:15 jzb: The only thing I wanted to mention is that we are still looking slippy/not-good for Alpha. So if there's anything not working yet for Atomic wrt. Alpha release that *is* releease-blocking and not communicated elsewhere, don't wait to talk about it 20:52:21 so we have sda1 and sda2 with sda2 chunked up into LVs 20:53:04 roshi: little bit 20:53:25 I notice centos7 at least at the moment was using sda1 sda2 sda3 and no LVM structure.. should we get together with them and have something consistent? 20:53:32 sorry, had an unavoidable appt that ran long :( 20:53:55 I don't theres is finalized either.. just wondering if we should collaborate 20:53:58 dustymabe: I can certainly see the value in being consistent. 20:54:03 dustymabe: so +1 yes. 20:54:30 jzb: thanks 20:54:38 walters: sorry, to clarify on the things that are done, is the repomd.xml parsing done, as well? 20:54:41 dustymabe, this is a really important topic but i see it as a bit outside of the atomic/fedora-infra meeting scope, though this meeting is sometimes pure atomic specific 20:55:12 walters.. should we discuss after the meeting? 20:55:31 oddshocks, i'm not sure what that referred to exactly; ostree doesn't use repomd.xml. Perhaps that task was about teaching MM to look for repo/summary (ostree repo style) instead of yum/repomd.xml ? 20:55:56 walters: yeah I believe it was a mirrormanager task 20:56:00 * stickster is sorry he has to duck out for another appt. 20:56:17 stickster: thanks for helping 20:56:24 what little I did, np 20:56:25 dustymabe, i know i owe you a followup on that but can i get back to you by tomorrow? 20:57:05 walters: sure. The messages on the list don't necessarily address collaboration with centos. I was thinking about sending a new email about that 20:57:23 that is.. after we talked and perhaps came up with what we thought was the ideal layout 20:59:42 ok, i can do a chat after this 20:59:58 walters: thanks. 21:00:06 anything else on the fedora-infra/atomic discussion? 21:01:39 thanks all! 21:01:41 #endmeeting