I have been a member of this list for a few years now but due to some
constraints I have not been able to actively participate. I would now
like to start be active in Fedora development. I have been using fedora
as my 1st choice OS since Fedora Core 6.
I would be very glad to have someone who can show me the ropes.
Onalenna Junior Makhura
we are now in the infrastructure freeze leading up to the Fedora 18
Alpha release. This is a pre-release freeze.
Anything in the Pre Release freeze box is frozen until 2012-08-28 (or
later if Alpha slips). This means there should be NO puppet changes to
any hosts in there (including global ones) without signoff of the
change from at least 2 folks in sysadmin-main and/or
I thought I would give a quick status update on our private cloud work
(which skvidal has been doing. Thanks skvidal! )
Our hardware in all in and working.
Our network is up and working.
We have a test instance of eucalyptus up and running with a pair of
I'd like to test out Openstack on another 3 nodes or so. It's come a
ways since we evaluated it last.
We need to test more with the admin/command line tools.
We need to figure out how we want to setup groups/users/etc.
We need to repave everything and re-install it in a controlled and
I figured we would start out with a small group of folks with access
and expand based on feedback and capacity.
has some use cases we thought of.
Questions I would love feedback on:
What expectation do we want on reboots? They can go down at any
time, or 'we will try and let you know if we want to reboot things' or
we plan on doing a maint window every X and your instances WILL be
What timeframe should we tell people they can use instances?
Do we want to kill them after some specific time?
Note that if we want to use this for dev instances, we may want to at
least snapshot before taking down.
What sort of policy do we want on "Fedora relatedness" for instances?
I don't think we want to offer general instances for people, but how to
explain the line? Do we want to specifically forbid any uses?
What ports do we want to allow folks to use? Anything? 80/443/22 only?
How about persistent data storage? We promise to keep data for X
timeframe? We make no promises? We keep as long as we have storage
I think we should have a very broad 'catch all' at the end of the
policy allowing us to refuse service to anyone for any reason, allowing
us to shutdown instances that cause problems. Or should we word that
How often do we want to update images? Say we have a Fedora 17 image
for folks, would we want to update it daily with updates? weekly? Just
when we feel like it? When security bugs affect ssh ? When security
issues affect the kernel?
Any other policy related questions folks can think of?
packages01.dev has been setup as a dev box to give people developing on the
packages app a place to work/demo/etc. Like other dev boxes, it allows
people in the commit group (gitfedoracommunity) to login there. However, it
currently doesn't allow people in the commit group to sudo.
Since we have one sudoers file shared with all of our hosts, I'd like to get
some +1's to break freeze to give the commit group the ability to sudo
there. I actually started on this last night, having forgotten that the
sudoers file would be covered by change freeze. I can revert those changes
if this seems too big a change.
The sudoers file is in the private repo so I won't post a patch but the
changes are minimal:
* Add a line defining which hosts are in the packages_dev group (just
* Add a line giving people in the gitfedoracommunity group the ability to
use sudo on boxes in the packages-dev group with nopasswd
* Add a line giving people in sysadmin-main the ability to use sudo on boxes
in the packages-dev group with nopasswd
Could I get two +1's?
#fedora-meeting: Infrastructure (2012-08-30)
Meeting started by nirik at 18:00:00 UTC. The full logs are available at
* Howdy! (nirik, 18:00:01)
* New folks introductions and Apprentice tasks (nirik, 18:03:26)
* Applications status / discussion (nirik, 18:07:40)
* Sysadmin status / discussion (nirik, 18:17:53)
* we have been seeing an odd httpd crash on app servers of late.
* ongoing problem with log02 and it's host, sometimes requiring
reboot. (nirik, 18:19:15)
* skvidal has been working on cloud stuff (nirik, 18:19:55)
* will be announcing status.fedoraproject.org... I have a draft
announcement in gobby, corrections/editing welcome (nirik,
* Private Cloud policies and status (nirik, 18:22:19)
* Upcoming items (nirik, 18:23:16)
* 2012-08-14 to 2012-09-04 F18 Alpha Freeze (nirik, 18:24:46)
* 2012-08-31 end of 2nd quarter (nirik, 18:24:46)
* 2012-09-04 F18 Alpha release. (nirik, 18:24:47)
* 2012-09-10 to 2012-09-24 Skvidal is out (nirik, 18:24:47)
* 2012-09-25 to 2012-10-09 F18 Beta Freeze (nirik, 18:24:47)
* 2012-10-09 F18 Beta release (nirik, 18:24:47)
* 2012-10-23 to 2012-11-13 F18 Final Freeze (nirik, 18:24:49)
* 2012-11-13 F18 release. (nirik, 18:24:51)
* 2012-11-26 to 2012-11-29 Security FAD (nirik, 18:24:53)
* 2012-11-30 end of 3nd quarter (nirik, 18:24:55)
* Open Floor (nirik, 18:31:13)
* LINK: https://fedorahosted.org/fedora-infrastructure/ticket/3456
Meeting ended at 18:37:03 UTC.
Action Items, by person
People Present (lines said)
* nirik (88)
* threebean (16)
* abadger1999 (13)
* smooge (10)
* lmacken (6)
* Spack (6)
* zodbot (4)
* tflink (1)
* ricky (0)
* mdomsch (0)
* skvidal (0)
* dgilmore (0)
* CodeBlock (0)
18:00:00 <nirik> #startmeeting Infrastructure (2012-08-30)
18:00:00 <zodbot> Meeting started Thu Aug 30 18:00:00 2012 UTC. The chair is nirik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:00 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:01 <nirik> #meetingname infrastructure
18:00:01 <nirik> #topic Howdy!
18:00:01 <nirik> #chair smooge skvidal CodeBlock ricky nirik abadger1999 lmacken dgilmore mdomsch threebean
18:00:01 <zodbot> The meeting name has been set to 'infrastructure'
18:00:01 <zodbot> Current chairs: CodeBlock abadger1999 dgilmore lmacken mdomsch nirik ricky skvidal smooge threebean
18:00:08 <nirik> who all is around?
18:00:11 * lmacken
18:01:17 * threebean too
18:01:32 * tflink is around
18:02:04 * Spack
18:03:16 <nirik> ok, lets go ahead and dive in then...
18:03:26 <nirik> #topic New folks introductions and Apprentice tasks
18:03:43 <nirik> Any new folks want to introduce themselves? or apprentices want to ask questions or note anything?
18:04:51 <Spack> Hello
18:04:59 * abadger1999 here too
18:05:01 <nirik> hey Spack.
18:05:14 <Spack> I'm arround since the begining of the week
18:05:16 <nirik> you interested in contributing to Infrastructure?
18:05:54 <Spack> yeah, i'm in discovering mode and i would like to help if any
18:06:24 <Spack> i leave in Belgium and i work as sysadmin
18:06:27 <nirik> excellent.
18:06:43 <nirik> I can point you to some docs after the meeting... happy to answer questions as we go along too...
18:06:46 <nirik> and welcome. ;)
18:06:54 <Spack> thanks
18:07:30 <nirik> ok, shall we move on then...
18:07:40 <nirik> #topic Applications status / discussion
18:07:49 <nirik> any applications news this week or upcoming?
18:08:18 <abadger1999> Been working on the elections rewrite this week.
18:08:19 <lmacken> nothing too exciting... making openhw2012 into a static app today
18:08:38 <abadger1999> flask is proving to be very accessible to newcomers.
18:08:39 <nirik> abadger1999: cool. any gotchas?
18:08:49 <nirik> lmacken: sounds good. let me know if I can assist any with it.
18:08:59 <abadger1999> easy to learn so it's pretty nice.
18:09:24 <lmacken> nirik: I'm not sure how to go from fedora-web git -> production
18:09:31 <abadger1999> I'm going to see if we an get this ready in time for post-F18 elections but I think we may just miss htat deadline.
18:09:49 <nirik> lmacken: it should generate on bapp02... then proxies pull/rsync the content from there.
18:09:51 <abadger1999> The todo list is pretty long and includes migrating the old data over.
18:10:01 <nirik> but it will need config changes to redirect it right I think.
18:10:16 <nirik> abadger1999: ok.
18:10:37 <lmacken> nirik: ah, yep. so it'll require a change request after all.
18:10:45 <nirik> probibly so.
18:11:10 <nirik> ok, any other app news?
18:11:12 <threebean> datanommer is on the way.. just gotta talk it over with ianweller this afternoon before we can start poking Infra.
18:11:32 <threebean> I'll need a DB for it.. and I'm not sure how to do that in our environment.
18:11:32 <nirik> cool. landing in staging then before too long?
18:11:44 <abadger1999> threebean: does that mean we can decommission the old fedoracommunity soon? Or is this just the bare bones?
18:11:57 <threebean> abadger1999: just bare bones/backend.
18:12:00 <abadger1999> k
18:12:03 * nirik would jump for joy to get rid of app07. ;(
18:12:05 <threebean> abadger1999: we'd still have to write front-end querying stuff.
18:12:51 <threebean> any leads on how to create a new db? or... after the meeting?
18:12:54 <smooge> abadger1999, anything I can help with the rewrite? testing, review? learning new pain
18:13:12 <nirik> threebean: I can assist with that.
18:13:18 <nirik> in stg it's all on db02.stg...
18:13:43 <abadger1999> smooge: If you want to -- I just forked ianweller's tree and started hacking: https://github.com/abadger/fedora-elections-flask
18:13:46 <threebean> nirik: cool, thanks. I'll need to do it again in a few weeks for tahrir/openbadges.
18:13:52 <abadger1999> smooge: There's a TODO file in there.
18:14:09 <smooge> ok thanks
18:14:43 <threebean> in other news, packages01.dev is up and running from a git repo for fchiulli. http://packages01.dev.fedoraproject.org/packages
18:15:23 <nirik> cool.
18:15:28 <abadger1999> smooge: Some self contained items would be: (code): write a conversion script for old data to the new data. (packaging): rpmify the new elections and the fas-flask package (html/designer): give the templates a fedora theme -- probably can base them off the current elections or raffle code.
18:17:19 <nirik> ok... any other apps/devel news?
18:17:22 <nirik> or shall we move on
18:17:53 <nirik> #topic Sysadmin status / discussion
18:18:04 <nirik> so, busy as always... a few things to note:
18:18:17 <nirik> #info we have been seeing an odd httpd crash on app servers of late.
18:18:31 <nirik> it would be nice to track it down, but it's sporadic and hard to pinpoint.
18:19:15 <nirik> #info ongoing problem with log02 and it's host, sometimes requiring reboot.
18:19:40 <nirik> there's a bug on this one, had a bit of activity recently.
18:19:55 <nirik> #info skvidal has been working on cloud stuff
18:20:12 <nirik> We have a test euca cloud up and running... we have been poking around with the config and kicking the tires.
18:20:42 <nirik> I've been updating https://fedoraproject.org/wiki/Infrastructure_private_cloud with use cases and some policy draft ideas.
18:21:05 <nirik> Any other sysadmin tasks or upcoming items folks would like to note?
18:21:08 <nirik> Oh, one more:
18:21:27 <nirik> #info will be announcing status.fedoraproject.org... I have a draft announcement in gobby, corrections/editing welcome
18:22:19 <nirik> #topic Private Cloud policies and status
18:22:38 <nirik> mentioned this... there is a discussion on list about policies and such... do chime in.
18:23:16 <nirik> #topic Upcoming items
18:23:27 <threebean> Hmm, a question -> I mentioned status.fp.o in a blog post.. should I have waited until after the announcement?
18:23:37 <nirik> threebean: naw, thats fine.
18:23:41 <threebean> cool
18:24:36 <nirik> upcoming I have:
18:24:46 <nirik> #info 2012-08-14 to 2012-09-04 F18 Alpha Freeze
18:24:46 <nirik> #info 2012-08-31 end of 2nd quarter
18:24:47 <nirik> #info 2012-09-04 F18 Alpha release.
18:24:47 <nirik> #info 2012-09-10 to 2012-09-24 Skvidal is out
18:24:47 <nirik> #info 2012-09-25 to 2012-10-09 F18 Beta Freeze
18:24:47 <nirik> #info 2012-10-09 F18 Beta release
18:24:49 <nirik> #info 2012-10-23 to 2012-11-13 F18 Final Freeze
18:24:51 <nirik> #info 2012-11-13 F18 release.
18:24:53 <nirik> #info 2012-11-26 to 2012-11-29 Security FAD
18:24:55 <nirik> #info 2012-11-30 end of 3nd quarter
18:25:01 <nirik> Note that we likely will slip another week, so everything moves out a week due to that.
18:25:04 <nirik> and we might slip more.
18:25:12 <nirik> so, not sure what we want to do about the Security FAD.
18:25:23 <nirik> I guess wait and see a bit if we need to reschedule.
18:25:45 <threebean> oh wow.. I haven't been following the go/no-go meetings. Is it something that more hands would help with?
18:25:48 <nirik> if we do need to change it, probibly next would be just having folks come in a few days early before fudcon
18:26:18 <nirik> well, it's mostly been installer issues. :( But things are looking better than they have been today...
18:26:41 <abadger1999> skvidal on vacation might be good to add.
18:26:41 <threebean> mm, ok.
18:26:49 <nirik> abadger1999: it's there. ;)
18:27:08 <threebean> nirik: oh, I think lmacken's out next week too.
18:27:14 <nirik> Also, I might be doing some traveling mid sept as well... but I should be working from the road mostly, so it shouldn't really affect too much
18:27:19 <abadger1999> oh I guess my brain didn't recognize him with a capital "S" :-)
18:27:30 <lmacken> threebean: indeed
18:27:31 <nirik> threebean: oh yeah.
18:27:41 <lmacken> my hotel is 10 minutes away from nirik :P
18:27:50 <nirik> yep. ;)
18:28:09 <threebean> :)
18:28:34 <nirik> so, if we slip just one more week... the fad will be the week after release and should be fine. If we slip more than 1 week, it will be release week, or pre release, which will not be
18:29:10 <nirik> so, we will see I guess.
18:29:12 <smooge> nirik, well if we slip the security fad any more we might as well do it at Fudcon
18:29:26 <nirik> smooge: yeah, that was my thought too... although before fudcon.
18:29:40 <smooge> well all funds for 4th quarter pretty much go to fudcon
18:29:40 <nirik> have everyone come in 2-3 days before.
18:30:00 <nirik> yeah.
18:30:22 <smooge> but doing it before hand at fudcon might still be possible.
18:30:36 <nirik> I think we might be able to get fad money to help for those days...
18:30:40 <nirik> but we can see.
18:31:13 <nirik> #topic Open Floor
18:31:19 <nirik> ok, anyone have items for open floor?
18:31:38 <nirik> oh, there was a request to change our wiki url scheme...
18:31:49 <threebean> -1
18:31:54 <nirik> https://fedorahosted.org/fedora-infrastructure/ticket/3456
18:32:19 <threebean> er.. just seems unnecessary and would introduce issues.
18:32:25 <nirik> yeah, if we were setting it up from scratch I wouldn't care... but it doesn't seem to have any gain for the redirect and hassle pain.
18:33:29 <nirik> anything else from anyone?
18:33:30 <smooge> actually I would say it isn't our call.
18:33:37 <nirik> smooge: oh?
18:34:09 <smooge> the webteams and websites would seem a better place to say they would like it or not.
18:34:35 <nirik> yeah, although they are kinda a subset of us...
18:34:42 <smooge> oh I thought they were different
18:34:43 <nirik> I just don't see the gain.
18:34:54 <smooge> I don't either.. it would also break probably a lot of authentication
18:35:19 <smooge> or maybe not..
18:35:40 <nirik> we would have to maintain redirects.
18:35:48 <nirik> and really, I dont want anymore of those...
18:36:43 <nirik> ok, let me light the fuse then...
18:36:52 <nirik> Thanks for coming everyone!
18:37:03 <nirik> #endmeeting
The bodhi masher that runs our periodic jobs (releng04) never got updated to
handle the f18 pre/post beta updates policy. This means that even though bodhi
is properly enforcing the mandatory 3 days in testing, it's still sending
emails after 7 days. This is a very low-risk change that will mitigate a lot of
@@ -5,19 +5,19 @@
## $Id: bodhi-prod.cfg.erb,v 1.8 2008/05/21 23:38:07 lmacken Exp $
# Release status
# pre-beta enforces the 'Pre Beta' policy defined here:
-f17.status = 'post_beta'
+f18.status = 'pre_beta'
-f17.post_beta.mandatory_days_in_testing = 7
-f17.post_beta.critpath.num_admin_approvals = 0
-f17.post_beta.critpath.min_karma = 2
+f18.post_beta.mandatory_days_in_testing = 7
+f18.post_beta.critpath.num_admin_approvals = 0
+f18.post_beta.critpath.min_karma = 2
-f17.pre_beta.mandatory_days_in_testing = 3
-f17.pre_beta.critpath.num_admin_approvals = 1
-f17.pre_beta.critpath.min_karma = 1
+f18.pre_beta.mandatory_days_in_testing = 3
+f18.pre_beta.critpath.num_admin_approvals = 1
+f18.pre_beta.critpath.min_karma = 1
The infrastructure team will be having it's weekly meeting tomorrow,
2012-08-30 at 18:00 UTC in #fedora-meeting on the freenode network.
#topic New folks introductions and Apprentice tasks.
If any new folks want to give a quick one line bio or any apprentices
would like to ask general questions, they can do so in this part of the
meeting. Don't be shy!
#topic Applications status / discussion
Check in on status of our applications: pkgdb, fas, bodhi, koji,
community, voting, tagger, packager, dpsearch, etc.
If there's new releases, bugs we need to work around or things to note.
#topic Sysadmin status / discussion
Here we talk about sysadmin related happenings from the previous week,
or things that are upcoming.
#topic F18 Alpha Release tickets/Freeze
#topic Private Cloud policies and status
#topic Upcoming Tasks/Items
#info 2012-08-14 to 2012-09-04 F18 Alpha Freeze
#info 2012-08-31 end of 2nd quarter
#info 2012-09-04 F18 Alpha release.
#info 2012-09-10 to 2012-09-24 Skvidal is out
#info 2012-09-25 to 2012-10-09 F18 Beta Freeze
#info 2012-09-26 to 2012-09-28 Puppetconf
#info 2012-10-09 F18 Beta release
#info 2012-10-23 to 2012-11-13 F18 Final Freeze
#info 2012-11-13 F18 release.
#info 2012-11-26 to 2012-11-29 Security FAD
#info 2012-11-30 end of 3nd quarter
#topic Open Floor
Submit your agenda items, as tickets in the trac instance and send a
note replying to this thread.
More info here:
I just worked with puiterwijk on IRC to fix this infra ticket:
I forgot to get +1's, and would like to make up for it by asking for
All I did was:
mv /var/cache/cgit/* /root/cgit-cache-20120829/
and checked that things still worked, then closed the ticket.
Sorry for not checking in advanced.
I've been around for a little while, but things got kinda busy with my
day-job. Kevin was kind enough to leave me in the fi-apprentice group,
and I would really like to get started making active contributions, I
really don't want to be dead weight to the team.
I look at the 'Easy Fix' tickets often, but I haven't seen anything
that looks like it would fit my areas of expertise just yet. I
attempted to hack on a FAS ticket, but quickly found I lack the skills
I would probably be more suited for sysadmin type tasks, although I
really want to learn Python scriptiong. I'm almost always available on
irc, so hit me up if I can help you with something - if I'm around,
and available, I'll respond ASAP.
Thanks again everyone,