14:32:33 #startmeeting Atomic CentOS SIG 14:32:33 Meeting started Tue Oct 28 14:32:33 2014 UTC. The chair is jzb. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:32:33 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:32:33 Meeting started Tue Oct 28 14:32:17 2014 UTC. The chair is jzb. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:32:34 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:33:01 here's what I know right now - Ian got pretty far along on a test build system. 14:33:13 Sent credentials/login info to me, jbrooks and walters 14:33:30 Evolution: AFAIK, we're still waiting on a CentOS system, though 14:33:45 my high level status is: hoping to figure out how to maintain srpms, watching the CBS ad-hoc upstreams discussion 14:33:46 Evolution: any idea how we can make sure that's ready to go by Monday when he returns from PTO? 14:34:07 walters: what's the missing info on maintaining SRPMs? 14:34:23 how multiple people can collaborate on them 14:34:33 a dist-git like model is one approach 14:35:07 #action jzb get info on SRPM collaboration. 14:35:28 jzb: nope. the box hasn't been reprovisioned yet, and I'm not really active on that side of the centos bits. that'd be more kb 14:35:55 Here's a Q: we now have some pkgs in the CBS that we need for our images, such as a updated docker -- what's the repo where these can live? 14:35:56 afaik ian's working on a system local to him, so he shouldn't be completely blocked. 14:36:20 Evolution: Right, we're just still way outside the CentOS build system. 14:36:22 jbrooks: there's a wider discussion going on about that on the -devel list right now. 14:36:22 So we can include them in our trees 14:36:59 Evolution, ok 14:37:00 jbrooks: currently you can use the unsigned packages via http://cbs.centos.org/repos/ but that's not really 100% proper. 14:37:20 but we're having a broader discussion about signing/distributing community packages on the list 14:38:02 Evolution, ah, got it -- this does work for now, though 14:38:19 Evolution: http://lists.centos.org/pipermail/centos-devel/2014-October/012157.html <-- that? 14:39:08 http://cbs.centos.org/repos/atomic7-testing/x86_64/os/Packages/ 14:39:09 yep. 14:39:12 for instance 14:39:47 #info discussion about signing/distributing community packages: http://lists.centos.org/pipermail/centos-devel/2014-October/012157.html 14:40:04 Evolution: so - how do things like that get decided? 14:40:22 Evolution: that is, curious how long it will take to reach a decision/consensus. 14:40:45 I think that that overarching SIG stuff would be for the board, right? 14:42:15 Another high-priority item is identifying a place for updates to live -- test updates for the test images 14:43:22 "Official" updates and images should wait for the signing to be settled, but we don't have to hold everything for that 14:44:01 what about the space where kbsingh was uploading previously? 14:44:56 http://cloud.centos.org/centos/7/devel/ 14:44:58 I believe 14:45:12 that's going to be restructured/redone. 14:45:30 Evolution: oh... what's the plan there? 14:46:16 Evolution: are you talking about just cloud.centos.org? 14:46:32 both. 14:46:55 Evolution: so, pending discussion tomorrow? 14:47:03 correct. 14:47:13 Evolution: ok, so ... how to get a permanent URL for landing Atomic images by next week? 14:47:17 and trees? 14:47:37 yeah, the trees is what we don't have at all right now 14:48:24 the trees I would assume is on imcleod 14:48:36 Evolution: providing or storage? 14:48:40 the packages from the build system are up at the url mentioned above. 14:48:56 Ian should be providing the trees once we get the first image, etc. sure. 14:49:17 ian's making the images isn't he? 14:49:20 in fact, we probably want to have a update pretty dang quickly after the first image is out so people can test that functionality. 14:49:27 Evolution: yeah. 14:49:42 Evolution, when you type rpm-ostree upgrade, or whatever, you need to reach some web server w/ the updates 14:49:53 jbrooks: ah, I see now. 14:50:17 Evolution: we'll give you the bits, we just need somewhere to stash them :-) 14:50:27 this is the largest scope item probably - for example, i think we'd want instances in AWS to hit the CentOS mirrors there 14:51:01 but we don't want to burden *all* mirrors with atomic images either. 14:51:08 I'm unsure how we would carve that out. 14:51:17 there are images and trees 14:51:23 trees are pre-composed packages 14:51:24 this is something we'd have to discuss with fabian 14:52:18 Evolution: I know MM updates are also on Ian's radar after we get images 14:52:35 so: Image -> tree -> signing -> mirrors 14:52:43 jzb: right, but we're not currently using MM, and I'm not aware of any plans to move to it. 14:52:47 generally the schedule I have mentally. 14:53:04 Evolution: O RLY? My bad. I thought CentOS did. 14:53:09 Evolution: what does CentOS use then? 14:53:46 * jzb thought Mirror Manager was one of the few universally used pieces. 14:53:53 msync I believe. this is why I mentioned needing to discuss with fabian. 14:54:19 we couldn't use mirrormanager due to missing features in it for a number of years. 14:54:26 huh. OK. 14:54:42 this is probably an action for Ian, but I'm going to put it down for myself just to make sure. 14:54:48 the patchset was finally resolved late last year I believe, but by that point.. we're already well away from it. 14:54:55 #action jzb follow up with Ian & fabian on msync/mirroring. 14:55:09 Evolution: gotcha. 14:55:56 Evolution: can I tag you with the action on finding storage for images/trees? 14:56:02 pending cloud.centos.org discussion? 14:56:18 sure. 14:56:36 Evolution, just needs to be a web server spot we can rsync to 14:56:47 #action Evolution update on storage for images/trees in the interim before Atomic is fully mirrored, etc. 14:56:49 yeah. it looks like mdomsch makde the fix to mm on 18 Dec of last year. 14:56:51 Or that someone can 14:56:56 -k 14:57:12 what else do we need to touch on this week? 14:57:26 walters: you're in limbo on the git discussion. Anything else? 14:58:02 for image generation, just keep using the internal server and migrate to cbs later? 14:58:47 Today I'm planning to push a needed syntax change to the json files in our repo on github, and push the repo files needed to build the tree there, as well 14:59:15 walters: yes 14:59:46 I'm using the upstream (fedora and centos) jsons in my updated byo atomic howto: https://github.com/jasonbrooks/byo-atomic 15:00:16 that also tells ppl how to build their own updates in a container 15:00:24 Evolution: btw - Carl asked me this morning if we had a decision on the name. 15:00:38 Evolution: AFAIK we've always planned on "CentOS Atomic Host" 15:00:52 am I misremembering/forgetting something or was there some discussion we needed to have on naming? 15:01:27 jzb, we should add that to a pre-launch-decisions checklist 15:02:05 jzb: the name is really whatever you guys decide. that's fine by me, and I like that it lines up with CAH (cards against humanity) 15:02:07 also, any mods to the pkg list? and how will we consider/choose those -- another pre-official checklist item 15:02:36 CAH is fine w/ me though 15:02:45 Evolution: oooh. Too bad producing media (CDs/DVDs) is effectively dead. I'd love to have a sleeve with the CAH design. 15:03:06 maybe we could do a t-shirt 15:03:43 jzb: artwork, or splash page design for wiki and/or cloud.centos landing page. 15:03:44 #action jzb send out pre-launch checklist, including final check on name. 15:03:46 (possibly) 15:04:26 OK, anything else this week? 15:05:40 going once, twice, thrice... 15:05:54 OK, thanks all - will send out meeting notes momentarily. 15:05:59 #endmeeting