It's my understanding (Dennis please correct if I'm wrong) that the
problem with cloud image creation was due to libvirt iptables rules
being lost when iptables was restarted. This is a fundamental known
issue (see last paragraph of <http://libvirt.org/firewall.html>), and
one of the things firewalld was meant to solve.
Dennis says that there are lot of complicated rules on the builders
making switching to firewalld difficult. One possibility might be to
move those complicated rules from the builders to a network firewall,
and keep the host rules simple and functional. But that's probably a
In the meantime, any time iptables is restarted or reloaded, libvirt
needs a SIGHUP. (I suppose this means: ansible playbooks and also added
to any manual procedures.)
[cc rel-eng, reply-to infrastructure]
Fedora Project Leader
My name is Jonathan Zhang, from Hefei, China.
I'd like to join this team to fix issues, maintain the Project's servers
and do some translation to Chinese.
I have experience working on web development projects, and I've been a
sysadmin for over 2 years.
Among my skills are:
- C++ development
- Shell script programming
- DNS management
- Linux / *nix administration
I've worked on my SKS keyserver and other projects running on my server,
been active on mailing lists such as sks-devel. I have access to my testing
machines. I also plan to join other areas of Fedora Project soon.
I'm currently learning Node.js and Python.
I'd like to learn new programming languages and new technologies on
security as well.
I can invest 2-5 hours/week in contributing to team assignments.
My Freenode IRC handle is Jonathan_Z.
: https://key.bbs4.us/ (this keyserver is peering with FP's keyservers,
running since April 2014)
I would like to become Fedora Infrastructure apprentice.
I am Mikolaj Izdebski - a Fedora developer, who primarily works in Java
SIG on maintaining different Java build systems and libraries. You can
find a bit more information about me on my user page  on the wiki.
My primary interest in infrastructure area is improving infrastructure
for Fedora developers, especially ones that work with large number of
related or similar packages. This includes topics such as build systems,
continuous integration and automated package testing.
Some of short-term things I would like to do:
* learn more about infra internals (how to use bastion to log into other
machines, how Ansible playbooks work in Fedora, how backups are done,
and much more)
* work on completing Koschei playbook (currently it sets up only basic
system, but a lot of other stuff has to be done manually)
* migrate Koschei from Fedora 20 to RHEL 7
Long term goals:
* make Koschei an official Fedora service (RFR is already filled)
What are next steps I need to follow to become apprentice?
Software Engineer, Red Hat
The infrastructure team will be having it's weekly meeting tomorrow,
2015-01-29 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 just made a small (but long awaited) release of anitya.
* Thu Jan 29 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.1.16-1
- Update to 0.1.16
- In the documentation (about page) adjust the code to store the url in a
variable making it easier for people to copy/paste the code (Elan Ruusamäe)
- Add api to query for a project by homepage. (Ralph Bean)
- Typofix in the API docs generation. (Ralph Bean)
This is already running at upstream-monitoring.org
I started to put together some emails for various people asking about
the status of various projects we have in the pipeline, but then I
realised that it might be easier to just send this query to the list
and have people answer here (default to open!)
So, if you see something below that you know the status on, please
reply to this post with that information. Also if you are blocked or
need help, please note that too and we can possibly get some more folks
involved in helping out. ;)
1. New fedora infrastructure private cloud.
msuchy was working on this.
We have 3 machines setup we were doing test installs on.
We also have a equalogics storage unit setup.
We ran into problems with the latest openstack version, so moved back
one to try and get things going.
msuchy: whats the current status? :)
abompard was working on this.
We have mailman01/02 production instances all setup in ansible.
There was a bunch of work going on to change the database backend and
ORM and such and we wanted to wait for that work to settle out.
Then we were going to start migrating lists.
abompard: whats the current status?
pingou was working on this.
We got really far at the FAD in december. Everything is pretty much
implemented I think, we just need to test a ton and roll out to
production. We have various staging instances setup already.
pingou: whats the current status?
lmacken was working on this.
I setup a bodhi02.stg on rhel7/ansible, I guess we need to finish
installing bodhi2 there and hooking it up in stg? It would really be
nice to land this asap before the f22 cycle really starts.
lmacken: whats the current status?
5. Mediawiki update
patrick was working on this.
mediawiki is moving to a new LTS release version. We were going to
migrate our setup to that and try and migrate to postgresql as well.
patrick: whats the current status?
I don't think anyone is currently working on this.
We are using an older version of sticky-notes.
We need to update to the newest version and migrate to postgresql.
The new version bundles stuff and will be a pain to package and get our
changes re-applied to.
Help wanted. ;)
Various people were working on this.
The stopforumspam plugin in stg was causing it to not load at all.
Disabling that, stg now is running the newer version at least.
We need to upgrade the prod version to that new version and see if
there's any spam handling stuff we can do that actually works.
No one is yet working on this one, but I guess I probibly will.
We need to move hosted to rhel7, but need to sort out trac for that.
Likely we need to make a parallel installable 'trac012' and all our
plugins for that version. Then when a new LTS version comes out we can
package that as trac14 or whatever and move on up.
Packaging help wanted.
ralph was working on this.
We were planning on moving everything to FMN at some point. Where are
we in that. Do we want to set a deadline?
10. Anytia / release-monitoring.org
pingou was working on this
Are we close to switching this on and announcing it? Whats left?
11. pkgs upgrade
bochecha and pingou was working on this.
pkgs01.stg still needs more testing? Whats the current status?
Still need to fix the allow admins to login?