IRC log for #gooseproject on 20130527

00:27.36shalkieherlo ping
00:30.57shalkiehotsdpot to study python and/or openshift. SMS if interested.
00:31.30shalkieargh. going to public hotspot.
00:31.53shalkieputs the phone done and walks away...
00:57.11herloshalkie: too tired
00:58.09shalkieno worries. i will just enjoy the caffiene by my self. :-p
00:59.20herloshalkie: caffeine is good all by itself :)
01:00.02herloshalkie: just spent a day (Saturday) boating with my brother at Yuba and another day (today) at Heber Valley RR with Thomas the tanke engine for AJ
01:00.30herlogot back about 3pm, still have to mow the lawn and a bunch of other yard work, too...
01:42.31shalkieYeah, you have had a busy busy weekend already. :-)
02:27.36herloshalkie: indeed. I'm going to be testing goosepkg a bit more tomorrow. Then I'll probably email an announcement about it tomorrow afternoon.
02:37.59*** join/#gooseproject bochecha_ (~bochecha@175.45.17.220)
02:38.00*** join/#gooseproject bochecha_ (~bochecha@fedora/bochecha)
15:23.19herloGoOSe morning
16:02.47herlogoozbach: ping
17:37.36goozbachpong. i am just finishing lunch will be online in a bit
18:38.51goozbachherlo: ping
19:44.37herlogoozbach: pong, I thought you said 12pm EDT
19:46.05goozbachI did, apparetnly my wife had scheduled me to grill at noon
19:46.07goozbach:/
19:46.10goozbachI'm working now
19:46.19goozbachbut I can't seem to gain root access on pilgrim
19:46.27goozbachwhich is where I should be doing the mash, correct?
19:47.00goozbachif you can't help now I understand. I'm trying to get as much done as I can
19:48.13herlono worries
19:48.20herloI'll be there in a bit, potty training
19:52.53goozbachk, when you get back try and put my ssh key from roman into root for pilgram and roman
19:55.35herloyou don't need root for those
19:55.56herloyou ssh as yourself...
19:55.59herlogoozbach: ^^
19:56.15goozbachI'd like to install make on pilgrim
19:56.19herlosudo
19:56.40herloyou should have rights... what are you using make for, just out of curiosity...
19:57.23goozbachmy dotfiles :)
19:57.44herloahh, okay. You aren't in wheel, I'll put you in there.
19:57.55goozbachI don't have a pw and I can't sudo
19:57.59goozbachthat's the issue!
19:58.04herlotry again
19:58.07herlolog out and back in
19:58.31herlowants to get freeipa in place for us. Would be so much easier.
19:59.18goozbachI'm in!
19:59.23goozbach+1 to freeipa
19:59.29goozbachwe have a server to put it on?
19:59.34goozbachI've been wanting to play with that
20:02.45herlono
20:02.57herlobut I can get us one at prgmr, probably. Right nb? :)
20:03.41herlogoozbach: if you don't have rights on a certain box, let me know.
20:04.38goozbachwill do, we keeping user accounts in our salt?
20:04.48goozbachmight make things more consistent?
20:06.19herlonot yet, but ipa will take care of that
20:06.24herlonb: ping!
20:07.37herlogoozbach: the trick is handling dns in one place. Since we're doing most everything server related with gooselinux.org that won't be too hard. I'm only debating the security of the proces...
20:07.56goozbachfreeipa should be able to do splitdns no?
20:08.22goozbachif not, just use iPA for internal dns and keep maintaining external dns on admin.
20:11.32herlogoozbach: I'm not debating that actually. We don't have to have gooseproject.org on there and it does support zone transfers to a standard dns (aka bind) server.
20:11.54herlobut that's not really a concernt since gooselinux.org is where everything would reside for our infrastructure.
20:12.07goozbachtrue
20:12.16goozbachthen what's the concern?
20:12.18herloI just need to move it from tosdomains.net to freeipa. I'm more concerned about the security of freeipa access and krb
20:12.34herloI need to better understand it if we just do that sort of stuff in the open...
20:12.50goozbachahh
20:22.23herloI might want to limit where we do that. Machines will auth themselves, users, sudo, etc via krb
20:28.43herlogoozbach: how can I help you now?
20:28.57goozbachgot the first mash running in a tempdir
20:29.14herlogoozbach: there's a script for mashing already
20:29.21herloand we need to sign them first
20:29.27goozbachahh
20:29.34herlogoozbach: the order is posted here
20:29.35herlohttps://github.com/gooseproject/main/wiki/How-to-Cook-A-GoOSe
20:29.36goozbachI'm out of order
20:29.44herloyep, it won't hurt anything
20:29.49herlojust won't have signed packages yet
20:30.36herlobesides. http://koji.gooselinux.org/pub/updates/6.0/
20:31.02herlogoozbach: those are already mashed, we did this last week. Thus my desire to start making things show up via email or something. :)
20:31.32herlois starting to think of something like a task chart for each release would be good with statuses of each.
20:32.52herloemail at the end of a mash run, email at the end of a signing run, email at the end of a build, etc. Email when we finish a compose, etc.
20:33.03herloprobably be good to store this in a db of some sort too
20:33.10herlogoozbach: want help signing?
20:34.32goozbachlet's use something like trello.com
20:34.39herloI considered that
20:34.43goozbachyeah, can you point me in the right direction
20:34.48herlobut I want the status to be automatic when something finishes
20:35.07goozbachhttps://github.com/gooseproject/main/wiki/Sigul tells me what to run
20:35.15goozbachwhere do I run it though?
20:35.34herloyeah, we need to update that on the wiki
20:35.41herloyou run it as kojiadmin user on roman
20:37.09goozbachand I should be signing 6.1? or 6.0-updates?
20:37.17herlo6.0-updates
20:37.23herlobut it just uses the 6.0-gold key
20:37.39herlogoozbach: we also need a place to store our passphrases securely
20:37.46herlolastpass could work, I suppose.
20:38.45herlogoozbach: you want to open a screen session as root on roman?
20:39.56goozbachdone
20:43.47herlo<PROTECTED>
20:44.49herlogoozbach: check you prm
20:44.51herloer pm
20:50.51herlogoozbach: anything I can help with?
20:52.57goozbachsigning now I suppose
20:53.12goozbachINFO: Calling koji to write 0 rpms
20:53.21goozbachthat mean it succeeded?
20:54.11herloI saw the same thing. We can check by visiting the repo
20:54.55herlogoozbach: look here: http://kojiweb.gooselinux.org/mnt/koji/
20:55.18herloyou can go to one of the packages that was built as 6.0-updates tag and see if it has a signed file
20:55.51herlooh, goozbach I tihnk I know why
20:56.13herlothe target is gl6.0-updates, but the tag the target points to is gl6.0-updates-candidate
20:56.30herlowhich makes sense why the darn thing was so huge
20:58.02goozbachso I should change to gl6.0-updates-candidate
20:58.12goozbach?
20:58.13herloyep, that should do it.
20:58.14goozbachor re-tag
20:58.28herlono, check the gl6.0-updates-candidate tag on koji.gooselinux.org
20:59.54herlogoozbach: you can check any package to see if it has the gl6.0-updates-candidate tag. like nss:  http://kojiweb.gooselinux.org/koji/buildinfo?buildID=2695
21:02.30goozbachthat looks better
21:02.39herloyeah, it sure does
21:04.27goozbachkk, I'll let that run, and then mash it
21:04.31goozbachthanks for the help
21:04.44herloyeah, no problem. Can you document this process on the sigul page?
21:04.58goozbachyup
21:05.07herlothanks!
21:07.06herlogoozbach: with gl6.0-updates-candidate, we don't want to mash in the parent packages from gl6.0. So the /etc/mash/updates.mash file indicates inherit = False, where /etc/updates/gold.mash indicates inherit = True
21:07.14herlothis is when the signing is done.
21:07.54goozbachhttps://github.com/gooseproject/main/wiki/Sigul
21:08.45goozbachalrighty got something runnint now
21:08.50goozbachgonna go hang with the family
21:08.55goozbachI'll email the list when it's done
21:09.04herlogoozbach: hmm, could we ad something there?
21:09.06goozbachmaybe even write up a script which will email the last
21:09.11herloadd
21:09.18herlogoozbach: well, we could add it to the python script
21:10.07herlobut for the docs, could you instead indicate the tag is specific
21:10.25herlosomething like, if we're doing version 6.1, the tag might be gl6.1
21:10.41herlowe'll also need to explain how sigul is set up at some point.
21:14.32goozbachyeah
21:14.38goozbachmodified slightly with those updates
21:17.49goozbachINFO: Signing batch 172/1292 with 1 rpms
21:26.02herlothanks
22:30.53nbherlo, you have a server for goose at prgmr
22:52.06herlonb: true, I was thinking that was for building. I was hoping to transfer more stuff there.
22:52.18nbherlo, hey, come in #prgmrclubhouse
22:52.27nbherlo, and talk to prgmrcom real quick
22:52.31nbif he says ok, i can set up another one
22:52.42herlowe can put them up as a sponsor
22:53.52nbBTW, that's a basically prgmr-staff-only channel
22:53.57nbso no one else go there please
22:54.02herlolol
22:54.12herlospams invites to all his friends...
22:54.43nbwe need to register it so we can set up acls and stuff
22:54.58herloyeah, you totally should.
23:40.16nbherlo, so how many, and what kind of specs vps's woudl you want
23:53.13goozbachsigning complete
23:53.17goozbachnow to mash!
23:53.34goozbachFWIU it should be updates

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