I just pushed to stg and prod a new version of pkgdb2, here is its changelog:
* Tue Jan 13 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.22.2-1
- Update to 1.22.2
- Fix the get_groups query to actually return all the groups in a timely
manner (Thanks Patrick Uiterwijk)
- Fix the CSS on the blue buttons on the update ACLs page when hovering over
- Add a title to the 'Retired' status to mention they are clickable.
I pushed to prod two releases of pkgdb2, the second fixing the first one of
Here is the changelog for both:
* Mon Jan 12 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.22.1-1
- Update to 1.22.1
- Fix the tooltips on the update ACLs pages
- Revert the changes made to generate the JSON manually and pull back to
flask.jsonify() as the JSON we were generated was invalid
* Mon Jan 12 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.22-1
- Update to 1.22
- Add the `set_monitoring_status` utility script (installed on /usr/share/pkgdb2)
- Improve documentation and default files (Thanks Michael Cronenworth)
- Make the project name configuration for example if you want to run pkgdb
for RPMFusion or another organization (Thanks Michael Cronenworth)
- Optimize the /api/vcs endpoint by generating the JSON output directly
- Optimize the /api/bugzilla endpoint by generating the JSON output directly
- Add a dedicated API endpoint to retrieve the content of the dead.package
file from cgit
- Retrieve the content of the dead.package file when clicking on 'Retired'
on the package page
1.22.1 is only in stg at the moment as Patrick is debugging something, but as
soon as we have finished to investigate I'll run the update.
Have a nice day,
Few days back I was having conversation with Pierre-Yves (Pingou)
about using jenkins-job-builder to create/configure/update jobs to
Jenkins job builder is used for openstack infra for managing a
large number of jobs on Jenkins. It uses yaml format to define a
job/job-template which can be used across project. It create a modular
structure of job definition so we can reuse a particular section
across jobs. Another great thing is we can have git repo for those
project configuration file and whenever a new project comes or need
update then Jenkins Git/Gerrit hook will trigger it (no more manual
configuration using jenkins-web).
I also create a JJB sample template  to demonstrate it's readiness
Let us know your point of view regarding this proposal.
My name is Andreas Christoforou, andreasch on irc and I am computer
scientist with experience in Linux system administration in clustered/high
availability environment. Also I am computer science enthusiast and always
look for new opportunities to learn more and meet new technologies.
Currently I am working as a System Administrator.
The infrastructure team will be having it's weekly meeting tomorrow,
2015-01-08 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 nagios/alerts recap
Here we go over the last weeks alerts and see if we can find ways to
make it so they don't happen again.
#topic Upcoming Tasks/Items
#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'm Sean Brown, Mhurron on irc, a System Admin in Raleigh-Durham and am
interested in assisting the Fedora Project as I can. I work as a Linux
administrator and know a little Python. I would be interested in helping
out with administration as well as smaller Python programming to gain
more experience with that.
Hi Infra folks,
I wanted to introduce Dmitri Pal, who manages the team at Red Hat that
works on freeIPA and SSSD among other things. Patrick of course
contributes to Ipsilon which includes fedoauth, and has been
collaborating with Simo, who's on Dmitri's team.
Dmitri asked me about Fedora identity and authentication needs and
whether any of these projects could be useful in Fedora
infrastructure. I told him I'd make an introduction so the
Infrastructure team can explain the problems we're trying to solve
with the next Fedora Account System, and how that relates to work
Dmitri's team is doing.
Dmitri, most if not all of the Fedora Engineering team are on this
list, along with many other contributors to the Fedora community.
Since some of us (Patrick, Pierre, myself) will be in Brno for the
DevConf.cz event, we may have the opportunity to meet up there to
follow up on this discussion in person, but this is a good place to
Please keep <dpal(a)redhat.com> on CC for the discussion, since he may
not follow this list daily.
* * *
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
I'm Fabio Alessandro Locati (fale on fas and IRC), an Italian freelance
sysop, dba and solution architect.
I've met GNU/Linux in 2001 and since 2002 I've completely dismissed any
I've tried every Fedora since Moonshine, but only with Constantine it
became my daily-use OS.
During my freelance job I work mainly on RedHat/CentOS 5,6, and 7 and
technologies such as Bash, Python, JBoss, Puppet, Apache, Nagios, etc.
As a DBA I manage multiple systems in medium-big companies mainly based
on MySQL/MariaDB, PostgreSQL, MongoDB, and Hadoop.
Also, I've often found myself to develop websites with Python and PHP.
I'm Packager and Ambassador in the Fedora Project since August, 2014.
I would like to join the infra team to help out and to learn more about
The part of infrastructure I'd like to focus on, at least at the
beginning is the sysop part, since I've far more experience in this
Lately I find very interesting the automation of
provisioning/DevOps/infrastructure as code topics since I think they can
really be game changer paired properly with horizontal scaling
Fabio A Locati
Fabio Alessandro Locati
PGP Fingerprint: B960 BE9D E7A8 FA12 273A 98BB 6D6A 29D6 709A 7851
You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the
Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.
At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going for
I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help us
make the apprentice program more useful.
0. Whats your fedora account system login?
1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?
2. Has it helped you decide any area you wish to focus on or contribute
3. Have you looked at or been able to work on any of the fi-apprentice
4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?
5. Is there any help or communication or ideas you have that would help
you do any of the above?
6. What do you find to be the hardest part of getting involved?
Finding things to work on? Getting attention from others to help you?
Finding tickets in your interest area?
7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting?
8. Whats your favorite work of art?
Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.
Any folks I do not hear from in the next week will be removed from the
group. (Note that it's easy to be readded when you have time or
whatever and it's nothing at all personal, we just want to keep the
group up to date with active folks).
Thanks, and looking forward to your feedback!