hi, i newly joined fedora infrastructure group
by p sena
Hi,
I am new to the fedora infrastructure group. I am going throug few of the links in the site to get a feel of the work. I have submitted my .ssh_rsa_key.pub from the site. I think I will get some intimation on this. Please someone can let me know further proceedings from here onwards.
Cheers.
Regards & Thanks Prabir Senapati mailto: senapati2001(a)yahoo.com
13 years
[PATCH/RFC] func: Simplify minion.conf creation
by Todd Zullinger
Puppet conveniently makes most variables from Puppet.settings available
via Puppet[:variable]. Use this to generate minion.conf via a standard
ERB template.
---
This change is the sort of thing that really begs for a second set of
eyes, as it would cause too much trouble if it didn't work as
intended.
A quick way to test that the template does the right thing is to grab
http://fedorapeople.org/~tmz/tmp/func-minion-template-test.pp and run
it through puppet, e.g. sudo puppet /tmp/func-minion-template-test.pp.
I noticed this while poking the func setup to see what settings were
needed to make func use puppet's certificates with the new code from
Seth in func's git tree. (I also noticed that the overlord.conf isn't
puppet managed, and that's the one I was more curious to see, easily
found on puppet01. ;)
modules/func/files/make-minion-conf.sh | 24 ------------------------
modules/func/manifests/init.pp | 24 ++++++++++++------------
modules/func/templates/minion.conf.erb | 13 +++++++++++++
3 files changed, 25 insertions(+), 36 deletions(-)
delete mode 100755 modules/func/files/make-minion-conf.sh
create mode 100644 modules/func/templates/minion.conf.erb
diff --git a/modules/func/files/make-minion-conf.sh b/modules/func/files/make-minion-conf.sh
deleted file mode 100755
index ea50c95..0000000
--- a/modules/func/files/make-minion-conf.sh
+++ /dev/null
@@ -1,24 +0,0 @@
-#!/bin/bash
-
-
-certfile=`ruby -e "require 'puppet'; Puppet.parse_config; puts Puppet.settings['hostcert']"`
-keyfile=`ruby -e "require 'puppet'; Puppet.parse_config; puts Puppet.settings['hostprivkey']"`
-cacert=`ruby -e "require 'puppet'; Puppet.parse_config; puts Puppet.settings['localcacert']"`
-
-
-cat <<EOM>/etc/func/minion.conf
-# configuration for minions
-
-[main]
-log_level = DEBUG
-acl_dir = /etc/func/minion-acl.d
-
-listen_addr =
-listen_port = 51234
-use_certmaster = 0
-
-cert_file = $certfile
-key_file = $keyfile
-ca_file = $cacert
-
-EOM
diff --git a/modules/func/manifests/init.pp b/modules/func/manifests/init.pp
index 50d6ed8..b9d39fe 100644
--- a/modules/func/manifests/init.pp
+++ b/modules/func/manifests/init.pp
@@ -23,23 +23,23 @@ class func::funcd {
}
}
+ File {
+ require => Package['func'],
+ }
+
file { '/etc/logrotate.d/func_rotate':
source => 'puppet:///func/func_rotate',
- require => Package['func']
- }
- file { '/usr/local/bin/make-minion-conf.sh':
- source => 'puppet:///func/make-minion-conf.sh',
- require => Package['func'],
- mode => 0750,
- notify => Exec['makeminionconf']
}
- exec { 'makeminionconf':
- require => File['/usr/local/bin/make-minion-conf.sh'],
- command => '/bin/bash /usr/local/bin/make-minion-conf.sh',
- refreshonly => true,
- notify => Service['funcd']
+
+ file { '/etc/func/minion.conf':
+ content => template('func/minion.conf.erb'),
+ notify => Service['funcd'],
}
+ # This can be removed once all systems are updated
+ file { '/usr/local/bin/make-minion-conf.sh':
+ ensure => absent,
+ }
}
class func::certmaster {
diff --git a/modules/func/templates/minion.conf.erb b/modules/func/templates/minion.conf.erb
new file mode 100644
index 0000000..33395ca
--- /dev/null
+++ b/modules/func/templates/minion.conf.erb
@@ -0,0 +1,13 @@
+# configuration for minions
+
+[main]
+log_level = DEBUG
+acl_dir = /etc/func/minion-acl.d
+
+listen_addr =
+listen_port = 51234
+use_certmaster = 0
+
+cert_file = <%= Puppet[:hostcert] %>
+key_file = <%= Puppet[:hostprivkey] %>
+ca_file = <%= Puppet[:localcacert] %>
--
1.7.2.2
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
History teaches that grave threats to liberty often come in times of
urgency, when constitutional rights seem too extravagant to endure.
-- Justice Thurgood Marshall, 1989
13 years
Change with FAS sysadmin-* accounts
by Mike McGrath
FYI everyone, I've now changed all the sysadmin groups to be invite only.
Lots of users would apply and kind of just sit there for months, and
that's not good. So by invite only, one of us has to add users to the
groups and sponsor them at that time.
-Mike
13 years
Emails in FAS
by Mike McGrath
Starting from our upgrade to this afternoon emails in FAS weren't being
generated correctly. The biggest impact from this was new users, who
signed up but never got their welcome email with a password.
I've corrected the issue (configuration needed to be set to smtp) and I've
sent emails to the impacted new users (there were 39 of them total).
The bigger thing here is that we need to think about how to do email in
staging. Right now it's disabled. I'd like emails that come through
those hosts to be easily identifiable somehow.
I'm open to ideas? Is there a way to inject [staging] into their subject
with an appended --- staging body at the bottom so we can link to the wiki
explaining why they got the email and what it means.
Maybe even limit recipients. My concern here is, lets say I'm testing
packagers. If I apply for packagers in staging for testing. All the
packagers (the actual ones) are going to get emails about it. That's just
going to cause confusion. I'd prefer that doesn't happen... so we
disabled emails altogether. But clearly this fas error is a good reason
to be able to test emails in staging.
I'm open to ideas here, I'll keep chewing on it myself.
-Mike
13 years
Opening subscriptions to mirror-list{,-d} ?
by Matt Domsch
I would like to propose we remove the subscription administrative confirmation for mirror-list and mirror-list-d.
As best as I can tell, the primary users of these lists are Fedora mirrors, with a few RHEL source and beta mirrors subscribed too, though for those tracked by MirrorManager, they are all also Fedora mirrors.
We no longer are adding new mirrors to the master mirror rsync ACLs, and have not added anyone to the ACLs for at least a year. Therefore, the only "benefit" an admin gets to being on mirror-list from a Red Hat corporate perspective would be advanced notice of new bits being staged or made available, at most 1 week advance notice.
It would simplify the process for mirror admins to sign up, and remove an administrative duty that Adrian Reber and I have carried for several years.
Please advise.
Thanks,
Matt
Fedora Mirror Wrangler
--
Matt Domsch
Technology Strategist
Dell | Office of the CTO
13 years
Compressing files (gz versus bz2 versus xz)
by Stephen John Smoogen
So I was asked to look at compression on log servers and to see if
changing to xz would save us some space. My test is not comprehensive
but showed what might happen.
Basic summary. XZ may save us up to 2% over what we are currently
saving but its real advantage is in speed of uncompressing files over
bzip2. [compression may be faster for some files also.]
File | Size | Gzip | G% | Bunzip2 | B% | XZ | X%
messages.log | 644568 | 10992 | 98.3 | 4856 | 99.3 | 5940 | 99.1
mail.log | 610816 | 65060 | 89.3 | 40836 | 93.3 | 35536 | 94.5
TOTAL | 1255384 | 76052 | 93.5 | 45692 | 96.1 | 41476 | 96.5
Program | Compression Time | Uncompression Time
GZIP | 00m43.416s | 00m10.033s
BZIP | 10m42.296s | 01m02.525s
XZ | 10m15.937s | 00m12.565s
Raw data below
root@log01 smooge-b]# du -s messages.log mail.log
644568 messages.log
610816 mail.log
[root@log01 smooge-b]# time gzip -v -9 messages.log mail.log
messages.log: 98.3% -- replaced with messages.log.gz
mail.log: 89.3% -- replaced with mail.log.gz
real 0m43.416s
user 0m41.335s
sys 0m1.736s
[root@log01 smooge-b]# du -s messages.log.gz mail.log.gz
10992 messages.log.gz
65060 mail.log.gz
[root@log01 smooge-b]# time gunzip -v messages.log.gz mail.log.gz
messages.log.gz: 98.3% -- replaced with messages.log
mail.log.gz: 89.3% -- replaced with mail.log
real 0m10.033s
user 0m6.948s
sys 0m3.004s
[root@log01 smooge-b]# time bzip2 -v -9 messages.log mail.log
messages.log: 133.043:1, 0.060 bits/byte, 99.25% saved, 659381328
in, 4956148 out.
mail.log: 14.961:1, 0.535 bits/byte, 93.32% saved, 624854215
in, 41766136 out.
real 10m42.296s
user 10m36.948s
sys 0m1.608s
[root@log01 smooge-b]# du -sc messages.log.bz2 mail.log.bz2
4856 messages.log.bz2
40836 mail.log.bz2
45692 total
[root@log01 smooge-b]# time bunzip2 -v messages.log.bz2 mail.log.bz2
messages.log.bz2: done
mail.log.bz2: done
real 1m2.525s
user 0m44.779s
sys 0m4.956s
[root@log01 smooge-b]# time xz -v -9 messages.log mail.log
messages.log (1/2)
100.0 % 5,923.6 KiB / 628.8 MiB = 0.009 3.1 MiB/s 3:21
mail.log (2/2)
100.0 % 34.7 MiB / 595.9 MiB = 0.058 1.4 MiB/s 6:53
real 10m15.937s
user 10m8.550s
sys 0m3.552s
[root@log01 smooge-b]# du -s messages.log.xz mail.log.xz
5940 messages.log.xz
35536 mail.log.xz
[root@log01 smooge-b]# time unxz -v messages.log.xz mail.log.xz
messages.log.xz (1/2)
100.0 % 5,923.6 KiB / 628.8 MiB = 0.009 140 MiB/s 0:04
mail.log.xz (2/2)
100.0 % 34.7 MiB / 595.9 MiB = 0.058 74 MiB/s 0:08
real 0m12.565s
user 0m8.709s
sys 0m3.636s
--
Stephen J Smoogen.
“The core skill of innovators is error recovery, not failure avoidance.”
Randy Nelson, President of Pixar University.
"We have a strategic plan. It's called doing things.""
— Herb Kelleher, founder Southwest Airlines
13 years
FAS2 and 3
by Mike McGrath
fas2 and 3 are down at the moment, please leave them that way
-Mike
13 years
Introduction
by James Lawrie
Hi List,
I'm looking to contribute to Fedora and here's my introduction as per
the wiki.
I'm James and I'm based in the UK (UTC). I work as a Linux Engineer
(mostly technical support) for a hosting company. I'm recently Redhat
certified and I used to be a lot more heavily into scripting (mainly
Perl) than I am now.
I'm joining partly because I want to give something back, but mostly
because I want to truly understand the systems I work on daily and be
able to look back in decades to come and say I was part of it.
The amount of time I'll be able to contribute differs massively
depending on my rota. Some weeks I'll be looking to give 10-20 hours
(maybe more), other weeks I'll only be able to give maybe 4 hours.
I'm looking to help out in any way I can, mostly wherever I can help out
sysadmin wise along with any bugzapping I can do. I can't be more
specific yet but hopefully after a week or two of hanging around I'll
have a better idea.
My LinkedIn profile gives a little more information regarding my
abilities http://www.linkedin.com/in/jameslawrie and I hope my
ServerFault profile (which I've been working on for about a month) gives
a hint of my technical ability:
http://serverfault.com/users/37667/james-lawrie
--
James Lawrie
13 years, 1 month
[PATCH] This group needs to be created before the user (defined below)
by Mike McGrath
---
manifests/servergroups/koji.pp | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/manifests/servergroups/koji.pp b/manifests/servergroups/koji.pp
index 0b50705..2e130d1 100644
--- a/manifests/servergroups/koji.pp
+++ b/manifests/servergroups/koji.pp
@@ -7,6 +7,11 @@ class kojimasters {
include nfs-server
include heartbeat::heartbeat
+ group { masher:
+ gid => 751,
+ ensure => present,
+ }
+
user { masher:
uid => 751,
gid => 751,
--
1.7.2.1
13 years, 1 month