Introduction : Ramesh
by Ramesh Raithatha
Hi all,
My name is Ramesh and I'm from India. I am working as an intern at LinkedIn. I'm a Linux enthusiast and
love to write bash and python scripts. My skill sets covers SAN/NAS,
networking/Linux system admin and scripting. I am interested
in doing system admin stuff and automating things.
Cheers,
Ramesh
11 years, 2 months
Plan for tomorrow's Fedora Infrastructure meeting (2013-02-14)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2013-02-14 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 Private Cloud status update / discussion
#topic Upcoming Tasks/Items
#info 2013-02-12 f16 end of life
#info 2013-02-12 pkgdb update.
#info 2013-02-18 to 2013-02-19 smooge on site at phx2.
#info 2013-02-28 end of 4th quarter
#info 2013-03-01 nag fi-apprentices
#info 2013-03-07 remove inactive apprentices.
#info 2013-03-19 to 2013-03-26 - koji update
#info 2013-03-29 - spring holiday.
#info 2013-04-02 to 2013-04-16 ALPHA infrastructure freeze
#info 2013-04-16 F19 alpha release
#info 2013-05-07 to 2013-05-21 BETA infrastructure freeze
#info 2013-05-21 F19 beta release
#info 2013-05-31 end of 1st quarter
#info 2013-06-11 to 2013-06-25 FINAL infrastructure freeze.
#info 2013-06-25 F19 FINAL release
#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
11 years, 2 months
Delete Wiki Page
by Giannis Var
hello,
i have not used my fedora account for a long time and i lost my access on
it! I cant retrieve it as i dont have access to the e-mail account that i
have used to register. So, i want to delete a certain wiki page which has
my personal details from back then when i used to be active. I am looking
forward for your help and answer!
wiki page: https://fedoraproject.org/wiki/User:Gsvarsa
Thank you
11 years, 2 months
monitoring rebuild
by Kevin Fenzi
Greetings.
I'd like to look at revamping our nagios setup to be nicer.
Problems with our current setup:
- It's very easy to make syntax errors that you can only fix with
further commits. (ie, no sanity checking at all).
- nagios alerts us too much for things that don't matter or that we
cannot do anything about. (isolated network issues, servers not
responding in cases where there are no impacts, alerting then
recovering very quickly)
- our dependencies are not right, so we get 50 pages for an issue that
is a single network or gateway link being down.
- nagios monitors remote machines over vpn links, but also over non vpn
links, leading to us having confusion over what a machine is named in
nagios.
- Our current setup isn't flexable enough to allow monitoring of non
core resources, but we want to do this. (for example, qa machines
or secondary arch machines or cloud machines, where we may want
different groups to get alerted or manage those machines).
- When we add new machines or services we often forget to add
monitoring, or we don't monitor all the things we should be.
- When we do work on machines we sometimes forget to silence nagios.
Requirements:
- syntax check commits and reject them where they would break things.
- only send pages for things that impact either end users or
maintainers. Things that don't impact either of those should
mail/notify, but not page.
- correct dependencies so if one thing is down all that block on it
really does not alert.
- allow non FI groups to have machines/networks they manage.
- When adding new machine/service, monitoring should be automatically
configured if at all possible.
- Possibly have some kind of escalations setup... page, wait X min for
an ack, if not page again or page more people, etc.
- When doing work have an easy way to silence alerts for affected
machines.
Some possible parts of the solution:
- check_mk - This would allow us to just install and query it, and it
would monitor all the running process, etc. Could very much simplify
config on normal nodes.
- ansible playbooks to disable notifications or alerts in cases where
thats needed easily. We can use the web interface, but a simple
script to do this would be nice to call from other playbooks. This
needs consistent naming for hosts.
- commit hook to check syntax. This will require nagios on lockbox01
and installing to a tree or something, unless there's a way we can
pull the syntax checking out of nagios. Does python-nagios package do
it?
- Identify those items/hosts that are ones that should page, assume
rest are email/notice only. The mass reboot sop has these already in
the Class A/B hosts listed there. I can easily generate a list.
I'm sure there's more things we can do here, and several people have
looked into this problem in the past. Its not a simple one, but I think
it's a good one to work on and fix.
I'm not sure if it makes sense to make a new nagios git repo (like we
did for dns) or just move it over to ansible repo. I kind of think it
would be nicer just in ansible repo.
This is just prelim ideas on the scope and problem... I'll look at
starting on some more detailed work soon.
kevin
11 years, 2 months
New Apprentice
by John Stanton
Hi,
My name is John, I have been working with linux for the past 6 years. I am
looking forward to helping out anyway I can.
Skills/Certs I have:
- Perl
- Python(beginner)
- bash scripting
- RHCE
- Bunch of CompTia certs.
John
11 years, 2 months
Meeting Agenda Item: Introduction Kiril Nesenko
by Kiril Nesenko
Hello all,
My name is Kiril Nesenko. I work at Red Hat as Software Integration
Engineer for oVirt/RHEV product. Here are some details about me:
I have a good knowledge in Linux systems
(installing,configuring,administration). Today I
maintain continuous integration env. with 200+ servers. Working with
puppet, foreman, jenkins, gerrit.
I think it is a great opportunity for me to contribute for infra team. I
have some knowledge to share and I am sure I will learn here a lot.
I am interested to start working on koji build system servers.
I hope that team will find my skills useful.
IRC Nick: knesenko
Linkedin: http://www.linkedin.com/in/kirilnesenko
- Kiril.
11 years, 2 months
Plan for tomorrow's Fedora Infrastructure meeting (2013-02-07)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2013-02-07 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 Private Cloud status update / discussion
#topic Upcoming Tasks/Items
#info 2013-02-08 mass rebuild for f19 starts.
#info 2013-02-11 pkgdb update.
#info 2013-02-18 to 2013-02-19 smooge on site at phx2.
#info 2013-02-28 end of 4th quarter
#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
11 years, 2 months
