IRC log for #gooseproject on 20110604

00:09.30herlogoozbach: okay, I have build from SCM working!
00:09.58herlonow what we need to do is build out everything from scratch. That's 91+ RPMS, with deps.
00:10.04herlothen we'll have a decent buildroot
00:10.27herloI am still targeting July1 as our launch date. I think we can make it now...
00:29.49shalkieherlo: This weekend I will be setting up that system for use. Did you have any luck with a colo?
00:50.20herloshalkie: nope, struggled to get koji working first
00:52.51herloshalkie: I think I'll send out emails this weekend though
01:01.02herloFirst though, I need to get the wording straight.
01:05.23shalkieYes. Free space please would work much better then "space please free".
01:05.27shalkie:-)
01:07.58herlolol
01:08.04herlonot quite that
01:08.25herloI was thinking more about the ethos and how we represent ourselves. Why we want to exist and the purpose for the colocation.
01:08.38herlobut I suppose grammatical correctness would be appropriate as well.
01:08.58herloshalkie: probably tomorrow I'll be writing up the 'koji howto' for goose
01:09.06shalkieAin't nuttin but aires de fancy...
01:09.11herlobbl
01:09.19shalkieYeah I am out for the ride home too.
13:10.41*** join/#gooseproject makfinsky (~imak@c-76-104-102-89.hsd1.va.comcast.net)
13:44.57herlogoozbach: ping
14:44.35*** join/#gooseproject makfinsky (~imak@c-76-104-102-89.hsd1.va.comcast.net)
15:12.13herlowell, documentation repo now exists. Time to document :)
16:02.11herlogoozbach: would a goal of releasing GoOSe 60 days after RHEL release be too ambitious?
16:02.27herloI'm talking minor releases here
16:02.42herloI think the .0 release might be more flexible
17:27.35*** join/#gooseproject makfinsky (~imak@c-76-104-102-89.hsd1.va.comcast.net)
18:05.28*** join/#gooseproject josephnexus (~josephnex@67-42-163-130.bois.qwest.net)
18:05.42josephnexuswas summoned here by the mighty powers of herlo.
18:05.51herlolol
18:06.02herloI don't know how mighty my powers really are
18:06.13herloI think that depends on how long you stay and how much you help :)
18:09.42josephnexusda da da!!!!
18:09.45josephnexus:-P
21:10.01herloshalkie: ping
21:19.36shalkieshalkie: pong
21:23.02herlolol
21:23.09herlomissed it for that reason
21:23.19shalkied'oh.
21:23.27shalkiejust realized as well.
21:23.41herlono wories
21:23.47herlowitn only one 'r'
21:24.51shalkieherlo: Eh wats up doc?
21:25.27herloshalkie: so I fingered out a good purpose for your machine if you can get it online with a public IP
21:25.28shalkiechews on a carrot like a certain wascly wabbit
21:25.43shalkieYeah? What would that purpose be?
21:25.49herlolookaside cache
21:26.17herloI need to shower a child, but if you'll be around in 20-30 minutes?
21:26.58shalkieI could be.
21:27.05herlowell, be
21:27.26shalkiehey, do you have a copy of RHEL6 on disc?
21:27.34shalkiedoesn't have a copy on hand.
21:27.36herloI have a copy, not on disk
21:27.50herlowe could burn one, though or make a usb installer
21:28.02shalkieI could use just an ISO image.
21:28.10herloyeah, I have one of those
21:28.17shalkiek
21:28.43herlopingyalater
21:28.55shalkieYes sir. ttyl
21:33.47*** part/#gooseproject josephnexus (~josephnex@67-42-163-130.bois.qwest.net)
21:48.40herloshalkie: ping
21:55.05shalkieherlo: pong
21:55.14herloshalkie: okay, so you ready to hear what I need?
21:55.21shalkieYes sir
21:55.26herlok, here it is
21:55.54herlowhen building an rpm from source control, there needs to be more than just the spec and patch files
21:56.28herlobut in source control, we don't want to upload the archives that are used to build the rpm
21:56.44herloso we need a place to store the archives...
21:57.22herloessentially, a makefile will do an scp to your server and put the file in some directory we specify and then make it available via ftp/http
21:58.18herloshalkie: so what I need from you is approximately 250GB of space to do such a thing. It doesn't actually matter what the underlying OS is as long as it has ssh and either ftp/http support for downloading the files.
21:58.43shalkieOkay. I think I have a perfect little system for that.
21:58.53herlok, here's the other sticking point
21:59.44herlowe need to make it in such a way that when another contributor wants to do the same thing, they can put their ssh pub key somewhere. We can take that key then and put it in the authorized keys for probably a single user...
21:59.49herlono passwords
22:00.27herloshalkie: make sense?
22:01.22herlofor example, the make file might do something like this
22:01.24herlomake upload
22:01.30shalkieIt does make sense. However let me ask this question: Have we gotten to the point of actually setting up Kerberos?
22:02.14herlowe have had kerberos setup, but I had to remove it as it conflicted with koji
22:03.13shalkiedo you mean it conflicted with the setup of koji on the same sytem or in some other way?
22:03.34herloshalkie: either way. kerberos, while nice is going to need some way to get reimplemented
22:03.52herloshalkie: yeah, it caused pain with apache for koji and freeipa to be on the same box
22:04.15herlobut let me say this. I don't plan to use kerberos for koji, for a couple reasons.
22:05.05herloKoji certificates are much easier to deal with and setup. Plus we can expire them on a yearly basis
22:05.17shalkieThe system that I was thinking about using is, unfortunately a bit on the old side. I could setup kerb. easily enough on it with ldap, but I don't know if I trust it being exposed.
22:05.27shalkiekk
22:05.54herlofor this, if you had F14 or F15 on it (or RHEL5/6) it would be fine
22:06.11herlojust needs ssh and either ftp/http server to allow koji to grab the archived files
22:06.14shalkieI was thinking about using the old Cobalt Qube3.
22:06.34herloand btw, I don't actually care if people can download the source, that's kind of the point
22:07.06herlobut we don't want people just willy nilly *uploading* archives. It has to be individuals who have their keys on the server.
22:07.18herloso probably something like this
22:07.29herlowe have an 'admins' group (probably wheel)
22:07.36herloyou, me, goozbach in there
22:08.05herlothen we have a 'archive' user (any name you like, maybe bitch)
22:08.31herlofor each authorized user we add their key to the 'bitch'
22:09.47herlothen, the make upload command will upload the archive to  bitch@some.adress
22:11.09shalkieOkay, Well I am down to the last few digits on my netbook battery.
22:11.16herloscp /path/to/archive.tar.gz bitch@some.address:/path/to/package-name/archive.tar.gz
22:11.21herloshalkie: where are you?
22:11.41shalkiethat makes sense. At home. I just need to plug in here in a moment and I need a break.
22:11.59herlohehe, that's fine. I have to go cook fish and chips
22:12.05herloshalkie: if you are hungry, you could come over
22:12.53shalkieOh no thanks. I just ate about an hour or so ago at the new couscouse mediteranian gourmet grill and am very full. :-)
22:13.03herlowhere's that?
22:14.52shalkieTook over the Bajio Grill by my house: http://www.yelp.com/biz/couscous-mediterranean-gourmet-grill-murray
22:15.26herlocool, thanks
22:15.32herlogoes to cook fish now...
22:15.36shalkieyeah. Free Wifi!
22:15.43herlo:)
22:16.28shalkiek, I am wandering for a few. I think I will try F15 on that system and see how well that works.
22:16.32shalkiettyl

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.