shutdown people01
by Seth Vidal
Hi all,
I'd like to shutdown people01, undefine it and nuke it from all of our
configs. We've been on people02 for 9 days now and I don't think we're
going to migrate back to people01 anytime soon.
Can I get 2 +1's to nuking this from orbit?
-sv
12 years, 11 months
Fwd: Changes to elections group
by Stephen John Smoogen
---------- Forwarded message ----------
From: Stephen John Smoogen <smooge(a)gmail.com>
Date: Wed, May 18, 2011 at 10:57
Subject: Changes to elections group
To: Paul Frields <pfrields(a)fedoraproject.org>, "Jared K. Smith"
<jsmith(a)fedoraproject.org>, David Nalley <david(a)gnsa.us>,
tremble(a)tremble.org.uk, Mike McGrath <mmcgrath(a)fedoraproject.org>,
Toshio Kuratomi <a.badger(a)gmail.com>
1) i added david nalley so he could do the board elections
2) I made the group invite only versus apply
3) I removed all the people since 2009 who had applied but never
accepted into the group.
--
Stephen J Smoogen.
"The core skill of innovators is error recovery, not failure avoidance."
Randy Nelson, President of Pixar University.
"Let us be kind, one to another, for most of us are fighting a hard
battle." -- Ian MacLaren
--
Stephen J Smoogen.
"The core skill of innovators is error recovery, not failure avoidance."
Randy Nelson, President of Pixar University.
"Let us be kind, one to another, for most of us are fighting a hard
battle." -- Ian MacLaren
12 years, 11 months
compress old puppet reports
by Seth Vidal
Puppet reports have grown since we switched from 0.25 to 2.6.X by
roughly 10x their original size.
so they are sucking the disk space out of puppet1 b/c we keep them
there.
When I reduced the number we keep it didn't have as nice of an impact on
our free space as I would like.
So - I wrote this to modify our reports clean up to compress all .yaml
files except for the latest 24hours worth of them.
It keeps 1month present - but much, much, smaller
and it keeps the latest 24 hours worth immediately available.
here's the patch:
diff --git a/modules/puppet/files/puppet-report-clean.sh
b/modules/puppet/files/puppet-report-clean.sh
index d274e2b..d4af330 100755
--- a/modules/puppet/files/puppet-report-clean.sh
+++ b/modules/puppet/files/puppet-report-clean.sh
@@ -2,3 +2,11 @@
# clean up all but the last 1 month of puppet reports
/usr/sbin/tmpwatch --mtime 720 /var/lib/puppet/reports/
+
+# compress all the .yaml files per host dir, except for the latest 24
hours worth.
+# since they are txt files and compress really well
+
+for host in `echo /var/lib/puppet/reports/*`
+do
+ /bin/ls -1 $host/*.yaml | head --lines=-48 | xargs --no-run-if-empty
xz -9
+done
need two +1's please
-sv
12 years, 11 months
IMPORTANT - Fedora Project Contributor Agreement Signing Window Is Open
by Tom Callaway
Please take a moment and read this brief email, as it is important.
Fedora is in the process of retiring our old "Individual Contributor
License Agreement" (also known as the ICLA or CLA) and replacing it with
the new Fedora Project Contributor Agreement (FPCA).
All Fedora contributors with accounts in the Fedora Account System
(https://admin.fedoraproject.org/accounts) who have agreed to the old
CLA *MUST* agree to the new FPCA by June 17, 2011 to continue
contributing to Fedora.
Here is how you do this:
1) Login to the Fedora Account System:
https://admin.fedoraproject.org/accounts
2) Once logged in, click on the "My Account" link in the blue box on the
left side of the window.
3) On the page that loads, you will see a section labeled "Account
Details". Look for the line that says "Contributor Agreement". On that
line, you should see a new section that says:
"New CLA Not Signed - We need contributors to sign the new Contributor
Agreement(Complete it now!)"
Click on "Complete it now!" and follow the prompts.
*****
It is important that Fedora Account holders who have signed the old
Fedora CLA sign the new FPCA. We have allotted a window of one month for
Fedora contributors to agree to the FPCA. This means that after June 17,
2011, any Fedora Contributors who have not agreed to the FPCA will have
their "cla_done" flag set to False. This also means that any groups that
they are in which are dependent upon "cla_done", such as "packager",
"ambassador", and Fedora People access will be removed.
There are a few accounts which are exempt from this, specifically,
accounts which are members of the "cla_dell", "cla_intel", and
"cla_redhat" groups. If you do not know what these groups are, you are
probably not in them. :) Accounts in these groups will not see the "New
CLA Not Signed" line on their "My Account" page, and do not need to take
any action at this time.
Please take a minute and login to FAS to agree to the terms of the FPCA,
to avoid loss of access.
More information about the FPCA, including the final FPCA text, can be
found here:
https://fedoraproject.org/wiki/Legal:Fedora_Project_Contributor_Agreement
If you have any additional questions about the FPCA or the re-signing
process, please feel free to email me directly at legal(a)fedoraproject.org.
Thanks,
Tom Callaway, Fedora Legal
==
Fedora Project
12 years, 11 months
Introduction Warren
by Warren Thomas
Hi everyone..
My name is Warren (IRC: wileywarren) and I live in the USA eastern time zone
(GMT - 4:00). Currently I'm Sr. Database Engineer in the Telecom industry. After
using Redhat/Fedora for 10+ years I think my skills are at a level that I might
be able to contribute to the project now, also this will provide an opportunity
for me to develop some newer skills.
I have a fair amount of experience with Nagios, Perl, RRD that should make me a
good fit for helping the
sysadmin-noc FIG. Ultimately, since I have some experience with databases, LDAP
and similar applications, that are my personal area of interest I'm hoping to
prove myself enough to throw my name in the hat for the sysadmin-dba FIG.
Currently I have 4-8 hours per week to contribute to the Fedora project but that
can increase from time to time depending on my project load.
12 years, 11 months
Fix people logs/awstats
by Kevin Fenzi
When we moved to people02 from people01, we didn't change where we
pulled the logs from and ran awstats on on log02.
Should be a pretty safe change:
diff --git a/manifests/nodes/log02.phx2.fedoraproject.org.pp b/manifests/nodes/log02.phx2.fedor
index 2599866..64d8b4c 100644
--- a/manifests/nodes/log02.phx2.fedoraproject.org.pp
+++ b/manifests/nodes/log02.phx2.fedoraproject.org.pp
@@ -39,7 +39,7 @@ node log02 {
log_dir => "secondary01",
}
awstats::site { "fedorapeople.org":
- log_dir => "people01",
+ log_dir => "people02",
}
iptables::firewall { 'ipv4':
#precustom => [ '-A INPUT -p udp -m udp --dport 25826 -j ACCEPT'],
diff --git a/modules/scripts/files/syncHttpLogs.sh b/modules/scripts/files/syncHttpLogs.sh
index 3e5ad55..9856d68 100644
--- a/modules/scripts/files/syncHttpLogs.sh
+++ b/modules/scripts/files/syncHttpLogs.sh
@@ -50,7 +50,7 @@ syncHttpLogs value01
syncHttpLogs value02
syncHttpLogs secondary01
syncHttpLogs hosted01 old
-syncHttpLogs people01 old
+syncHttpLogs people02
syncHttpLogs noc01
syncHttpLogs download01
syncHttpLogs download02
12 years, 11 months
Re: Cron <root@puppet01> /usr/local/bin/make_puppet_reports.py
by Seth Vidal
On Mon, 2011-05-16 at 19:35 +0000, Cron Daemon wrote:
> Traceback (most recent call last):
> File "/usr/local/bin/make_puppet_reports.py", line 98, in ?
> rep = syck.load(open(latest_report, 'r').read())
> TypeError: (1656, -1, 'syntax error')
Patch to fix the above.
need 2 +1's, please
the patch is just catching the exception and printing an error.
-sv
12 years, 11 months
Meeting Agenda Item: Introduction Jan-Frode Myklebust
by Jan-Frode Myklebust
IRC and FAS handle: janfrode
Skills: UNIX/Linux system admin for various HPC systems (Big SGI and IBM
SMPs/clusters, linux clusters), but for the last few years have been
working mostly on the linux infrastructure of an ISP running RHEL4/5/6,
RHEV, KVM, 389ds, (investigating IPA/FreeIPA), bind, apache, puppet,
openvpn, backup, netapp/iSCSI, FC-SAN, and probably much more..
I would like to join the infrastructure group to help with anything you
can use me for. I expect joining the infrastructure group will broaden
my skills by getting access to more competent sysadmins to discuss
solutions than I have in our small group at work. So a little bit
egoistic, but it will probably work both ways :-)
-jf
12 years, 11 months
change puppet report retention to 1months worth
by Seth Vidal
Right now we're keeping 2 months worth of puppet reports on our puppet
master.
thats 28GB worth of reports :(
I'd like to cut that in half.
need 2 +1's
-sv
here's the diff:
diff --git a/modules/puppet/files/puppet-report-clean.sh
b/modules/puppet/files/puppet-report-clean.sh
index 7467d60..d274e2b 100755
--- a/modules/puppet/files/puppet-report-clean.sh
+++ b/modules/puppet/files/puppet-report-clean.sh
@@ -1,4 +1,4 @@
#!/bin/bash
-# clean up all but the last 6 months of puppet reports
-/usr/sbin/tmpwatch --mtime 1440 /var/lib/puppet/reports/
+# clean up all but the last 1 month of puppet reports
+/usr/sbin/tmpwatch --mtime 720 /var/lib/puppet/reports/
ignore the 6months bit - that was apparently a typo :)
12 years, 11 months
Change request - pkgs01 items
by Kevin Fenzi
I have 2 items (feel free to vote on them separately if you prefer, as
they are independent).
1. The patched gitolite we had installed on pkgs01 in the recent outage
was incomplete. When someone tries to push changes on an old style
branch it says:
remote: refs/heads/f15/master
remote: Please see URL for more info
remote: error: hook declined to update refs/heads/f15/master
But has no actual URL in it. ;)
The updated patch says:
remote: NOTE: Branch naming scheme has changed. You attempted to push
remote: to: refs/heads/f15/master
remote: Please see https://fedoraproject.org/wiki/Dist_Git_Branch_Redux for more info.
Fixing this requires us to upgrade gitolite to the new patched version.
2. The pkgdb2branch.py script on pkgs01 still creates new packages with the old style branch names,
causing them to not work at all for maintainers. ;(
This fix to the script fixes that:
---
modules/gitolite/files/distgit/pkgdb2branch.py | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/modules/gitolite/files/distgit/pkgdb2branch.py b/modules/gitolite/files/distgit/pkgdb2branch.py
index dee7e4e..8bc0503 100755
--- a/modules/gitolite/files/distgit/pkgdb2branch.py
+++ b/modules/gitolite/files/distgit/pkgdb2branch.py
@@ -187,7 +187,8 @@ class Brancher(object):
(branch, pkgname))
# Add the master to the branch
- branch = '%s/master' % branch
+ # No longer add this after the new branching setup.
+ #branch = '%s/master' % branch
# If branchFrom is None, this is an EOL release
# If the directory already exists, no need to invoke mkbranch
if branchFrom:
--
1.7.4.1
12 years, 11 months