Plan for tomorrow's fedora infrastructure meeting (2013-04-11)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2013-04-11 at 19:00 UTC in #fedora-meeting on the freenode network.
Suggested topics:
#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 Private Cloud status update / discussion
#topic Upcoming Tasks/Items
#info 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze
#info 2013-04-15 - remove legacy-openid
#info 2013-04-15 - announce openid change on hosted.
#info 2013-04-15 - drop inactive apprentices
#info 2013-04-16 F19 alpha release
#info 2013-04-17 - switch to new sigul servers.
#info 2013-04-19 - switch hosted to openid
#info 2013-05-01 nag fi-apprentices
#info 2013-05-08 drop inactive apprentices
#info 2013-05-07 to 2013-05-21 BETA infrastructure freeze
#info 2013-05-21 F19 beta release
#info 2013-05-31 end of 1st quarter
#info 2013-06-11 to 2013-06-25 FINAL infrastructure freeze.
#info 2013-06-25 F19 FINAL release
#topic Open Floor
Submit your agenda items, as tickets in the trac instance and send a
note replying to this thread.
More info here:
https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings
Thanks
kevin
11 years
Some general Puppet questions and one Git clarify
by Frank Murphy
Not wanting to flood irc, break something,
or in case of missing meeting by accident. :(
Bastion:
~]$ puppet
Usage: puppet command <space separated arguments>
Available commands are: agent, apply, cert, describe, doc,
filebucket, inspect, kick, master, queue, resource
~]$ puppet resource User me
Could not run: Could not find a default provider for User
~]$ puppet describe
No help available unless you have RDoc::usage installed
~]$ puppet inspect
Could not prepare for execution: Inspect requires reporting to be
enabled. Set report=true in puppet.conf to enable reporting.
Hosted02:
(using some local commands to find my way.)
cat trac.ini | less
Couldn't find an entry for Freemedia in [intertrac]
How does it live?
~]$ puppet filebucket
No help available unless you have RDoc::usage installed
http://infrastructure.fedoraproject.org/infra/docs/puppet.txt
<snip/>
lockbox01:
The following commands will check out all GIT configs from a local
shell on lockbox01.phx2.fedoraproject.org:
git clone /git/puppet
Does it mean local shell on lockbox01
If logged into lockbox01 via ssh,
or local shell on myownbox
git clone lockbox01.phx2.fedoraproject.org://git/puppet
--
Regards,
Frank
http//www.frankly3d.com
11 years
[Change Request] python-fedora two timeout fixes and a flask_fas_openid fix
by Toshio Kuratomi
We put an alpha version of python-fedora onto infrastructure just before
freeze. This solved some very noisy issues for us but there are a few left.
I'd like to apply the attached hotfix which will fix three more problems:
* Increase the default timeout for http client requests from 30s to 120s.
This should fix several scripts which are making queries to bodhi and
pkgdb which take longer than 30s to complete.
* Catch timeout exceptions and reraise as ServerErrors. This has two
effects: The exception will be much more informative (the current code
raises an error at an unrelated line because a value is not initialized).
Code which already catches ServerErrors and proceeds will be able to
proceed if the Server times out as well.
* fix flask_fas_openid where a variable being referenced was misnamed.
We don't have any flask_fas_openid apps in production but this could be of
benefit for people testing new apps in stg during freeze.
Could I get two +1s ?
-Toshio
11 years
Plan for tomorrow's Fedora Infrastructure meeting (2013-04-04)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2013-04-04 at 19:00 UTC in #fedora-meeting on the freenode network.
Suggested topics:
#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 Private Cloud status update / discussion
#topic Upcoming Tasks/Items
#info 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze
#info 2013-04-15 - remove legacy-openid
#info 2013-04-15 - announce openid change on hosted.
#info 2013-04-16 F19 alpha release
#info 2013-04-17 - switch to new sigul servers.
#info 2013-04-19 - switch hosted to openid
#info 2013-05-07 to 2013-05-21 BETA infrastructure freeze
#info 2013-05-21 F19 beta release
#info 2013-05-31 end of 1st quarter
#info 2013-06-11 to 2013-06-25 FINAL infrastructure freeze.
#info 2013-06-25 F19 FINAL release
#topic Open Floor
Submit your agenda items, as tickets in the trac instance and send a
note replying to this thread.
More info here:
https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings
Thanks
kevin
11 years
Meeting Agenda Item: Introduction oddshocks
by David Gay
Hello, Fedora!
I'm a free software hacker and IT student at RIT looking to get involved
with the Fedora Infrastructure team. I will also be joining the team as
a Red Hat intern this Summer, if I am accepted. This is my
"introduction" email, as per
http://fedoraproject.org/wiki/Infrastructure/GettingStarted.
My *IRC Handle* is oddshocks. I use this username just about everywhere.
My *skills & tools* include GNU/*nix (especially Fedora), Python, Bash,
SASS/CSS, Vim, Git, Tmux, Irssi, Mako, Jinja, and SQLAlchemy. I have
full-stack experience, from back-end logic & database to front-end web
development. I am specifically interested in DevOps and Systems
Administration. From the infra team, I hope to learn more about
application and OS development and management. I am a fast learner and I
love solving problems with free software.
As far as *work*, I will perhaps explore some "easyfix" bugs to start,
and if I am accepted for the Red Hat internship, I will probably be
working in the area of fedmsg, Open Badges, datanommer, FUSS, and
similar things.
If you'd like to read more about my experience and skills, the resume I
used to apply for the Red Hat internship is at
https://github.com/oddshocks/resume/blob/master/resume.rst.
I should be in the IRC meeting today (which I believe starts in an hour
and a half), so perhaps I will see some of you there! Have a good one. :)
-- oddshocks (David Gay)
11 years
Freeze Break Request - koji fedmsg plugin
by Ralph Bean
dgilmore noted in channel that the koji fedmsg plugin is producing
tracebacks like the following:
Error running postBuildStateChange callback from _koji_plugin__fedmsg-koji-plugin: Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/koji/plugin.py", line 165, in run_callbacks
func(cbtype, *args, **kws)
File "/usr/lib/koji-hub-plugins/fedmsg-koji-plugin.py", line 94, in send_message
body = get_message_body(topic, *args, **kws)
File "/usr/lib/koji-hub-plugins/fedmsg-koji-plugin.py", line 50, in get_message_body
msg['owner'] = kojihub.get_user(info['owner_id'])['name']
KeyError: 'owner_id'
The error is not occurring for *all* postBuildStateChange calls, only for
some. We are not sure if this has been happening since the fedmsg plugin
was introduced or if it is a result of the koji upgrade that happened last
night. It is not causing koji to fail, but the subset of build state change
messages that hit this traceback are not being published. It is also adding
noise to the koji logs.
The koji fedmsg plugin is kept in puppet, so we can patch it there (it is
not in an rpm). The following patch should do the trick:
http://ralph.fedorapeople.org/0001-Silence-intermittant-koji-tracebacks.p...
For some messages, a None (null in json) will be published for the first time
in the owner field. The code that parses those messages on the consuming
side can be found here: http://bit.ly/16jqhtq It looks like it can handle
a None without causing any further issues. I can't say for certain about any
third-party code that may be listening to koji/buildsys messages and whether
or not it can handle a None/null.
I'm looking for two +1s to apply the patch above to clean up the koji logs.
-Ralph
11 years
Looking for GSoC Mentors
by Toshio Kuratomi
Greetings all,
At today's infrastructure meeting we talked briefly about what projects we
might be able to do for GSoC. Unfortunately we quickkly ran into the hard
reality of not having any core team members with the time to mentor for GSoC
at the meeting. So we're asking the list -- is there anyone here that has
the time to mentor GSoC students? Doing so is a commitment to help refine
the project initially, to review the applications to all of Fedora to select
the best ones, to answer questions that the student has, to keep track of
the student's progress (at least enough to give them a pass fail at the
midterm and final), to help the student figure out what features they can
cut if a project goes to long or let them know if they are falling behind.
We do have some interested candidates -- so please, register your interest
in mentoring and what general area of Fedora you'd be willing to mentor for.
Then students can start working with you to come up with a good project that
can help everyone.
Thanks,
-Toshio
11 years
