December 2013 - infrastructure - Fedora Mailing-Lists

Plan for tomorrow's Fedora Infrastructure meeting (2013-12-12)

by Kevin Fenzi

The infrastructure team will be having it's weekly meeting tomorrow, 2013-12-12 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 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

10 years, 4 months

1
1
0 / 0

I want to join in Fedora Sysadmin Group

by Rajasekaran Karunanithi

Respected group members, I am interested in working with Fedora servers.So I want to join in this group.Please accept my request as soon as possible. Thanking you. Yours respectively, K.Rajasekaran

10 years, 4 months

2
1
0 / 0

[freeze break request] koji03 and koji04 memory and cpu increases

by Dennis Gilmore

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, as an emergency fix I bumped the cpus on the koji boxes to 16 each from 6 and increased the memory to 16G from 10G. this was due to the systems being highly stressed after changes last week to the ssl certs used. we moved from 2048 bit certs and md5 hashing to 4096 bit certs and sha256 hashing. which resulted in an increase in cpu from about 60% to 100% so while the change has been done id like a couple of acks please. Dennis -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJSppOyAAoJEH7ltONmPFDRNAQP/RVsVLHa7NyE94zmyw2zGYiv nPq8/NNkJDLAssLUOHQeCO4fSxVxTAo0CmWUFzyDuP5kCM/lqkZ5q/yv5CKx19x5 N4Q2GBZl9RS2XYF5xjn3kTyC/CcmOEfOntB9lxnwSCkxifjFM6b73awyFhKTXjlP hksgtAktwcP4c76kZ6Hllcc3lQRA2Z4Fqnm+tglYA9xcctWNyFq+Hr6gY8FxMBdk fKt76UiF/MC1h4yJezT4bN4SYTH7iRfxxd5dL7XEtofscCyRjDV6SWHTvpNsiMwZ Gi2Tgic8c0g9HA//m0XgCmGZWChJVt/CW6GUl+F1OWctNWkTASsnKnIVOwsX6IB3 d9PQtiH01jF6GPvkx4OUX3OaO+ubYI2ptO8hdbIvB285Np/iLn+tJyUdCZ3KCwBv CToZ6867OlQzP5DHf6wHNNhyXbCxFzVg73ORHuUugTnveeevAXUo66CVdOibFfiR IsXeFgh1tUrLDmZKmY5Vzqu0tfMqtjlIFS3Y7yEd0N0tnpnAMiuwZUgxGKJO9i2S zvvOLawxQ0G884PJux6X4SkFZ5a2JpVu2f4dCXFnsmClz00C/sw4cmp+ZFJ/Xqc6 qOx6RgyVNywVfX+8fk1sKzCGAIQWeTtQT39A/4IMIao4BSRnfZRdtXb5GLT6LZzJ ctvSbFNKZ5vdLRy8A6h7 =hDdx -----END PGP SIGNATURE-----

10 years, 4 months

4
3
0 / 0

[request freeze break] Reboot proxy01

by Stephen John Smoogen

proxy01 had 1 cpu and will reboot into 4 cpus which should help its ability to handle load. Outage should be short and backout is to move number of cpus down to 1 again. -- Stephen J Smoogen.

10 years, 4 months

3
2
0 / 0

[freeze break request] reboot ibiblio03/fedorapeople

by Stephen John Smoogen

so the old mirrorlist-ibiblio is wedged on ibiblio03 and we need to reboot the box in order to get it truly dead. We need to reboot ibiblio03 which should be a 15 minute downtime at most. This will affect the following hosts: backup02.fedoraproject.org mm3test.fedoraproject.org people03.fedoraproject.org -- Stephen J Smoogen.

10 years, 4 months

3
2
0 / 0

[freeze break request] Move mirrorlist-ibiblio to different ibiblio server

by Stephen John Smoogen

We are currently seeing mirrorlist crashing on ibiblio03 every couple of hours. This seems to be due to something with the boxes network card and its virtual guests. Due to the fact we have a release coming up we would like this to be more stable when final comes. Steps to be done: 1) Edit ansible/inventory/host_vars/mirrorlist-ibiblio.fedoraproject.org 2) Nuke ibiblio03 copy of mirrorlist 3) Reboot ibiblio03 so other guests feel good about themselves again 4) Build new mirrorlist on either ibiblio02 or ibiblio01 -- Stephen J Smoogen.

10 years, 4 months

3
3
0 / 0

fi-apprentice request or introduction

by Jaime Andrés Villegas Buriticá

Hi, I just joined the group. I a developer (Python, HTML5 & CSS) like to give a little contribution to the Fedora project. My IRC handle is "jaimico88" I'm have a little experience with development, and know some Python. I really want to learn more about python, Fedora Infrastructure and maybe something new, most of all: I want to meet developers who are best than me and learn with them. I can spend 3~6 hours weak and honestly I do not know where I can start to work. Please, if some one have a advice, please.

10 years, 4 months

2
1
0 / 0

bugzilla subcomponent questions

by Kevin Fenzi

Greetings. bugzilla.redhat.com has rolled out support for subcomponents in their latest update. See: https://www.redhat.com/archives/bugzilla-announce-list/2013-December/msg0... for more info I suspect we will have some packages that will want to take advantage of these. I know the kernel maintainers have expressed interest in it. In their case, they want to be able to put bugs (or have them just filed in) subcomponents with different owner/cc lists. So, I'd like to collect questions and gather information from maintainers on what they would use this for and get FESCo to look at the policy issues before we implement anything. Off the top of my head: Policy: - Who can use subcomponents? Any package? Packages that are acked by FESCo or some other body? - Who manages the subcomponents point of contact and cc? maintainers of the primary component, or should the subcomponents have different approveacls lists? Implementation: - pkgdb2 is close to a early release, do we want to try and add support for subcomponents before we release it? Or just push it later in a update/point release? In any case we might think about how to make implementing things easier now even if we don't implement anything now. - If we don't implement now, is there some hacky way we can still do things for a limited number of components? Like say the kernel? - We will need to modify our sync to bugzilla scripts to handle subcomponents. Not sure how much work this will be. ;( Other thoughts or ideas? kevin

10 years, 4 months

2
1
0 / 0

Ansible question

by Miroslav Suchy

Working on Copr, I want to replace/add one line in file. I spent more then hour trying various things, but I'm out of ideas. What I'm trying to do is: self.conn.module_name = "lineinfile" self.conn.module_args = "dest=/etc/mock/%s.cfg line=\"config_opts['chroot_setup_cmd'] = 'install @build %s'\" regexp=\"^.*chroot_setup_cmd.*$\"" % (self.chroot, self.buildroot_pkgs) Which in yaml language should be (with placeholders expanded): - name: putting scl-utils-build into minimal buildroot of fedora-19-i386 lineinfile: dest=/etc/mock/fedora-19-i386.cfg line="config_opts['chroot_setup_cmd'] = 'install @build scl-utils-build'" regexp="^.*chroot_setup_cmd.*$" I tried several things - among all: - change regexp - do not use regexp at all as that should put $line at the end of file, which would work as well - use command module with sed, but there is too much of escaping and it is unreadable Can somebody advise me what should be correct form to replace or add that line to mock config please? -- Miroslav Suchy, RHCE, RHCDS Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys

10 years, 4 months

3
2
0 / 0

Some questions around coprs

by Kevin Fenzi

So, at todays fesco meeting there was some discussion about coprs. http://meetbot.fedoraproject.org/meetbot/fedora-meeting/2013-12-04/fesco.... In particular some folks want to be able to ship copr repo files in the main Fedora repository. This would allow users to easily install software from there without having to discover how to enable it. However, copr packages are not signed or mirrored currently. So, this brings up thoughts around if we can somehow sign them, and how we could mirror them, or even if we want to go down this road at all. (as it seems like not a use case copr's was designed for anyhow). So: 1. Do we even want to persue this? 2. If so, do we have any ideas how signing copr packages could work? 3. Mirroring doesn't seem like it would be that hard, just rsync off the repos and push them out in our regular mirroring system. Could be a fair bit of churn tho, and there's no set schedule, so we would have to decide on frequency, etc. 4. If coprs moves to being inside koji, could we at that point have a better time with these needs? 5. Perhaps we could propose some kind if pergatory type setup between coprs (experemental, just builds, may set your house on fire, may update incompatibly every day) and fedora repository packages (with all the updates guidelines, reviews, etc). Thoughts? comments? Possibly related to this: I wonder if copr could grow a 'meta repo' that has all the repodata of all existing coprs. Then you could just enable one thing and be able to install any coprs? kevin

10 years, 4 months

6
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure December 2013