infrastructure January 2015

infrastructure@lists.fedoraproject.org

41 participants
29 discussions

firewall rules on builders (iptables, firewalld, libvirt...)
by Matthew Miller 30 Apr '15

30 Apr '15

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 big undertaking. 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] -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

6 8

[release] pkgdb 1.23
by Pierre-Yves Chibon 17 Feb '15

17 Feb '15

Good morning everyone, I have just released and push to stg and prod a new pkgdb2 release with few changes. Here is the short changelog: * Wed Jan 21 2015 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 1.23-1 - Update to 1.23 - Increase the max width of the page - Added a public timeline to access the history of the package according to pkgdb (button in the package page) Basically the primary change is the apparition of the timeline button on the package page, for example: https://admin.fedoraproject.org/pkgdb/package/kernel/ leading to the timeline page: https://admin.fedoraproject.org/pkgdb/package/kernel/timeline#n9 I pushed this release despite the few changes because the next release will include some major changes and I wanted to be able to go back to something more stable if needed. This major change is the move of new package and new branch requests from bugzilla to pkgdb2 (cf [1, 2, 3] for more information on the topic). Have a nice day, Pierre [1] https://fedorahosted.org/rel-eng/ticket/5931#comment:12 [2] https://lists.fedoraproject.org/pipermail/rel-eng/2014-July/018167.html [3] http://blog.pingoured.fr/index.php?post/2014/07/23/New-package%2C-new-branc…

1 1

Meeting Agenda Item: Introduction Jonathan Zhang
by Jonathan Zhang 31 Jan '15

31 Jan '15

Hello, 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 - HTML5 - DNS management - Linux / *nix administration I've worked on my SKS keyserver[1] 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. Best regards, Jonathan --- [1]: https://key.bbs4.us/ (this keyserver is peering with FP's keyservers, running since April 2014)

1 0

Ansible question
by Miroslav Suchý 30 Jan '15

30 Jan '15

I have this ansible snippet: - name: Create users keystone_user: login_user="admin" login_password="{{ ADMIN_PASS }}" login_tenant_name="admin" user="{{ item.name }}" email="{{ item.email }}" tenant="{{ item.tenant }}" password="{{ item.password }}" state=present with_items: - { name: kevin, email: 'kevin(a)fedoraproject.org', tenant: infrastructure, password: "{{kevin_password}}" } - { name: laxathom, email: 'laxathom(a)fedoraproject.org', tenant: infrastructure, password: "{{laxathom_password}}" } But when I run it it produce: TASK: [Create users] ********************************************************** changed: [fed-cloud09.cloud.fedoraproject.org] => (item={'password': u'XXXX', 'name': 'kevin', 'tenant': 'infrastructure', 'email': 'kevin(a)fedoraproject.org'}) changed: [fed-cloud09.cloud.fedoraproject.org] => (item={'password': u'XXXX', 'name': 'laxathom', 'tenant': 'infrastructure', 'email': 'laxathom(a)fedoraproject.org'}) Is there way to mask the output (using -name or something) so the password is not print to console? -- Miroslav Suchy, RHCE, RHCDS Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys

5 6

Request to become apprentice
by Mikolaj Izdebski 30 Jan '15

30 Jan '15

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 [1] 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? -- Mikolaj Izdebski Software Engineer, Red Hat IRC: mizdebsk [1] https://fedoraproject.org/wiki/User:Mizdebsk

3 3

Plan for tomorrow's Fedora Infrastructure meeting (2015-01-29)
by Kevin Fenzi 29 Jan '15

29 Jan '15

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. 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 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 https://apps.fedoraproject.org/calendar/list/infrastructure/ #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

1 1

[release] anitya 0.1.16
by Pierre-Yves Chibon 29 Jan '15

29 Jan '15

Hi everyone, I just made a small (but long awaited) release of anitya. Changelog: * 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 Nice day! Pierre

1 0

Great Infrastructure projects status roundup
by Kevin Fenzi 29 Jan '15

29 Jan '15

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? :) 2. Hyperkitty. 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? 3. Mirrormanager2 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? 4. Bodhi2 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? 6. paste 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. ;) 7. ask 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. Help wanted. 8. trac 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. 9. FMN 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? kevin

8 16

Remove invalid address from kernel-team alias
by Paul W. Frields 28 Jan '15

28 Jan '15

Since davej isn't at Red Hat any longer, this patch removes his old address from the kernel-team alias.

2 2

Can not use mirrorlist with RHEL $releasever (bz#1175566)
by Ian Wienand 28 Jan '15

28 Jan '15

Hi, I'd like to try and find the/a person who could help out with [1]. EPEL version updates are a fairly constant annoyance that causes issues with CI systems in upstream openstack when the version updates. As described in the bug, I'd really like to just setup a .repo file with http://mirrors.fedoraproject.org/mirrorlist?repo=epel-$releasever&arch=$bas… to install "epel-release" and things should just work to always grab the latest release. However [6|7]Server, as given in $releasever by RHEL/Centos, don't work as a path. Any suggestions on how we can get this fixed? -i [1] https://bugzilla.redhat.com/show_bug.cgi?id=1175566

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure January 2015