How tickets are resolved
by Miroslav Suchý
Hi,
I have suggestion.
Can we please put into tickets how they have been resolved?
I mean something else then "Fixed".
Something like:
Fixed - puppet.git commit abc123
or
Fixed - I run command "rm foo.bar"
This way people (and apprentice group especially) can learn how infra set up works.
And if ticket need to be reopened (or audited) later, you can easily what was really done.
I can understand exceptions in complicated tickets, but usually it is just few commits and one or few more commands.
Isn't it?
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Software Engineer, #brno, #devexp, #fedora-buildsys
10 years, 4 months
Holiday Freezing
by Kevin Fenzi
Man, it's cold in here... :)
At the meeting today we decided for over the holiday (thats starting
the late afternoon of 2013-12-20 and until 2014-01-06) we would do a
relaxed freeze. This means:
* Fixing existing things that are broken or outage is fine.
* If you are adding something new or making config changes, please send
them to the list and get at least one +1 from anyone.
* Remember that many people are away enjoying their holidays so avoid
doing things that cause alerts or outages.
* This is a great time to update docs or make plans for changes to be
done in the new year if you are inclined.
I'd like to wish everyone a happy holiday season and I hope it's
restful and enjoyable.
kevin
10 years, 4 months
Plan for tomorrow's Fedora Infrastructure meeting (2013-12-19)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2013-12-19 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
ticket #3639
by Janez Nemanič
Hi,
could somebody have a look at ticket #3639 and give me some info what is OK
and what needs to be improved,etc.
--
Janez Nemanic
Lep pozdrav
Best regards
10 years, 4 months
Fedora 20 Final Freeze now in effect
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 20
Final release. This is a final release freeze.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
git clone http://infrastructure.fedoraproject.org/infra/ansible.git
scripts/freezelist -i inventory/inventory
Anything listed as freezes is frozen until 2013-12-10 (or later if the
release slips). Frozen hosts should have no changes made to them without
a signoff on the change from at least 2 sysadmin-main or rel-eng
members.
Thanks,
kevin
10 years, 4 months
Changes for EPEL 7
by Dennis Gilmore
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi All,
Yesterday I made a bunch of changes to enable building and shipping
epel7 beta, due to time zone differences and no one being around on
sunday night in the US i made the changes to get things working but was
unable to ask for approvals.
Attached is all the patches I applied.
allong with on in the private repo adjusting sudoers to allow the beta
contents to be synced out
Dennis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJSr78gAAoJEH7ltONmPFDRHrEP/1rAeH+pnxCTPk+ffmMO8xrp
3IsEOFoscsBOageWh0gu+7cLe5eUEZ/iCBqklrW3d5A4qV7jYtDZviKNeXmJeKuT
BVsiN3gs33t6eIfLXJ+xX4eSFhRd6KcSle2jcy9TgMLyqtuqnbQEYz9XlVXw2i78
5ZPQK4X46hAQfHQJOUx3YmRAVLcdSYxIcMOT7VAdp8kU1DjcsFWOM6pMe3AKHQ+b
GOXxAgsbbAe5bP2OZRYSvTYCjohZzO49CVOl51b4ba2FcEVrI9ENkgsVgZ0zzl2z
d08KNMzF1o5ycgxuWiGgKtJqLmLvK5t1HG/9j9ngZ4vTZTmWEO59moAWVNkH04oR
KeqPlVusfEu+TsyqPekb4TTKVzEUVQDfVN15Oh/F6HS8Uv/MxBMhjSccdUvr5Qe8
10uqVfpwfxlGGbr+KhBpSJ1kppvM5bUl9sAJJ+VGgzIG89pFkEc+GCYrhPE/yqZT
ygKWQXt7K/9LAW2q1mfvkvizhZtflJzM5yc3Yu6YoJ9vbmuRpX4tJrdcZSsT7R7b
+OuoKSL9ZFg+OcP/jSJWCj59cetT+Vu/I/xJDjU4Ml4jcBgBkxNLPBJpj8wcevZS
OFW2Ff2LQqMqSQ1NgxSXmZBTBmLmXpgf8ThOks1yMK+XywtFrM1EKcjJxdJfiM/X
zbO7Hj3iJVeDdZkCM+/G
=NeFF
-----END PGP SIGNATURE-----
10 years, 4 months
[freeze break request] Switch phx2 app servers back to proxy01.
by Ricky Elrod
After talking in #fedora-noc, we would like to make phx2 app servers
talk to other app servers via proxy01, rather than (potentially) going
out to a server across the country for the benefit of load balancing.
The issue this solves is that because apps hosted on admin.fp.o talk to
each other using the same admin.fp.o roundrobin that users use, when an
application hits a random proxy and that proxy has gone down for some
reason, the application would block its thread waiting for a response.
Eventually this would happen on enough applications that we would get a
flood of alerts, and ultimately cause downtime.
By using (only) proxy01, it means re-adding a single point of failure,
but it seems likely that the case of "proxy01 is down so everything else
is down" would mean that phx2 was having a network issue anyway, meaning
we'd be in the same position (i.e., app servers unreachable). It seems
unlikely that proxy01 will just die at random, and if it does then that
is a whole new issue that we should address. So yes, the single point of
failure is bad, but it seems marginally better than what we have been
seeing lately.
I would like +1's to push this to puppet, which effectively reverts
1bac8c9a and 23ceebd5.
[codeblock@lockbox01 puppet]$ git show
commit f0445cffd64d3db980a4b689517fd4b95f6e7686
Author: Ricky Elrod <codeblock(a)lockbox01.phx2.fedoraproject.org>
Date: Fri Dec 6 17:55:38 2013 +0000
Make phx2 boxen use proxy01 for admin.fp.o again
diff --git a/manifests/services/phx.pp b/manifests/services/phx.pp
index 72c24be..317bfc2 100644
--- a/manifests/services/phx.pp
+++ b/manifests/services/phx.pp
@@ -11,11 +11,10 @@ class phx {
}
case $environment {
'production' : {
-# host { 'admin.fedoraproject.org':
- #ip => '10.5.126.52',
- #ip => '66.35.62.166',
-# ensure => absent,
-# }
+ host { 'admin.fedoraproject.org':
+ ip => '10.5.126.52',
+ ensure => present,
+ }
host { 'cvs.fedoraproject.org':
ip => '10.5.125.151',
host_aliases => ['cvs']
10 years, 4 months
Pretty slow on uploading sources?
by Christopher Meng
Hi,
It seems that it's pretty slow in uploading RPM sources in SCM from China.
Can you investigate the potential issue?
Thanks.
--
Yours sincerely,
Christopher Meng
Noob here.
http://cicku.me
10 years, 5 months
Freeze Break Request: Nightly GNOME Backups
by averi
Hi,
as we discussed earlier today in #fedora-noc, the GNOME Project is
currently not having a backup plan in place and the Fedora Infrastructure
Team (thanks Kevin and Stephen) is willing to host our backups on one of
the backups nodes. (backup03)
Given no backups are being taken since more than 10 days I'm hereby asking
to receive a freeze break to finally set up a nightly rsync run from
backup03 into each of the GNOME servers to back them up ASAP.
Ansible patch: http://averi.fedorapeople.org/freeze-break.patch
Backup script: http://averi.fedorapeople.org/backup.sh
Thanks in advance and have an awesome day!
--
Cheers,
Andrea
Debian Developer,
Fedora / EPEL packager,
GNOME Sysadmin,
GNOME Foundation Membership & Elections Committee Chairman
Homepage: http://www.gnome.org/~av
10 years, 5 months
