A Friday with Infra
by Michal Konecny
Good Morning Everyone,
As you may remember from [1] the CPE team has started categorizing its
applications into the following categories:
1. We maintain it, we run it
2. We don’t maintain it, we run it
3. We don’t maintain it, we don’t run it
4. We turn it off
In this process we picked the following four applications that we want
to move from the first category to the third:
* elections [2]
* fedocal
* nuancier
* badges
However, we do not want to throw code over the wall to anyone, so we’re
setting up something we called “A Friday with Infra”. The goal is to
help on-boarding anyone interested in picking up the maintenance of any
of these apps by taking time on Friday to work on these apps with them.
We have prepared a wiki page describing this proposal, how to get
involved in it as well as all the work we believe should be done to have
a smooth hand-over of the applications:
https://fedoraproject.org/wiki/Infrastructure_2020/Friday_with_Infra
Let us know if you have any questions or (even better) want to be
involved with any of them :)
Michal
– On behalf of the CPE team
------------------------------------------------------------------------
[1]
https://communityblog.fedoraproject.org/application-service-categories-an...
[2] elections has actually already found a new maintainer
4 years, 3 months
Congrats to our new sysadmin-mainers
by Kevin Fenzi
I'm happy to announce that We have approved several folks into the
sysadmin-main group:
mohanboddu 'Mohan Boddu'
cverna 'Clement Verna'
bowlofeggs 'Randy Barlow'
This is the core group of trusted folks that high level access to most
everything in fedora infrastructure.
All these folks have done great work over the last few years on various
big projects, proving their dedication, trustworthiness, and ability.
Congrats to them all!
Use your powers for good! :)
kevin
4 years, 4 months
Meeting Agenda Item: Introduction Adam Stackhouse
by Adam Stackhouse
Hi everyone,
I am looking to help the infrastructure team at fedora so hopefully you
will welcome me in and help me get stuck in. So I will begin with
introducing my self a bit:
Name: Adam Stackhouse
IRC Handle: adstak
I have been a Linux sys admin now for about 6 and a half years in the web
hosting industry. I currently work for Godaddy EMEA and work on roughly
2000 of their Centos servers on their UK brands. This covers everything
from mail servers to web servers and I would like to offer back some of my
skills to fedora and hopefully pick up a thing or two along the way.
I have quite allot of experience in bash, Python and Perl from everything
from sys tools to back end API's. In terms of technologies I would like to
learn etc I am pretty open and want to learn as much as I can. currently I
am working with technologies such as ansible, haproxy, buidling RPM's and
openstack but I have pretty much had to deal with many services and
technologies in Linux due to the size of the company I work and happy to
get stuck in with what ever I can :)
In terms of open source work this would be a first for me so any advice
anyone can give into how I can get involved and be of help would be great.
The only thing close to this I have done in the past is some development
for the pebble watch a feew years ago with a few people on github so bit of
a noob in the open source world so hopefully everyone here can help me out
at any point if I need it.
So I guess in terms of questions if anyone could give me some advice on
where to go next I would love to just follow that and see where this goes.
I have seen there is an apprentice group which seems like a good place to
start to get an idea of the platforms you have etc
Any help you can give would be great and I look forward to working with
everyone
4 years, 4 months
koji build archiving
by Kevin Fenzi
Koji.fedoraproject.org currently stores every rpm ever shipped to users
since the Fedora 7 days, along with a lot of information about every
build it’s ever made, even if not distributed. We have continued to grow
the storage backing koji over time, but it is close to reaching a size
we can no longer expand (75TB).
We are going to start moving builds off our main storage volume on to
slower (but still accessible) volumes in order to shrink our main volume
of active releases and make it easier to move and expand. There may be
slowdowns of builds and composes during the time we are moving builds,
but we will try and make it as transparent as possible.
All builds will continue to be available via koji.fedoraproject.org, but
you may notice a new volume name in the download path of some older
packages.
As part of initial testing of this move, we moved the *fc6* tagged
builds and this generated a number of 'buildsys.state.changed'
notifications to maintainers. We have since corrected the koji
fedora-messaging plugin to not emit these volume change events. Sorry
for the extra emails.
Please let us know if you experience excessive slowdowns or issues
related to this move.
This work is being tracked in
https://pagure.io/fedora-infrastructure/issue/8065
Thanks,
kevin
4 years, 4 months
[PATCH] Add a nagios check for each rabbitmq server
by Jeremy Cline
Commit eae92f73e95 installed the nagios scripts[0] that are packaged for
epel7-infra on the RabbitMQ hosts. This is an attempt to use them with
nagios. I don't know anything about nagios though, so I have no idea if
this is even close to right, or if it works.
[0] https://github.com/nagios-plugins-rabbitmq/nagios-plugins-rabbitmq
Signed-off-by: Jeremy Cline <jcline(a)redhat.com>
---
roles/nagios_client/tasks/main.yml | 15 +++++++++++++
.../templates/check_rabbitmq_server.cfg.j2 | 1 +
roles/nagios_server/tasks/main.yml | 22 +++++++++++++++++++
.../nrpe/check_rabbitmq_server.cfg.j2 | 1 +
4 files changed, 39 insertions(+)
create mode 100644 roles/nagios_client/templates/check_rabbitmq_server.cfg.j2
create mode 100644 roles/nagios_server/templates/nrpe/check_rabbitmq_server.cfg.j2
diff --git a/roles/nagios_client/tasks/main.yml b/roles/nagios_client/tasks/main.yml
index 0259a43ca..65a60a7c3 100644
--- a/roles/nagios_client/tasks/main.yml
+++ b/roles/nagios_client/tasks/main.yml
@@ -233,6 +233,21 @@
tags:
- nagios_client
+- name: install nrpe checks for the RabbitMQ cluster
+ template:
+ src: "{{ item }}.j2"
+ dest: "/etc/nrpe.d/{{ item }}"
+ owner: root
+ group: root
+ mode: 0600
+ with_items:
+ - check_rabbitmq_server.cfg
+ when: inventory_hostname.startswith('rabbitmq')
+ notify:
+ - restart nrpe
+ tags:
+ - nagios_client
+
- name: nrpe service start
service: name=nrpe state=started enabled=true
tags:
diff --git a/roles/nagios_client/templates/check_rabbitmq_server.cfg.j2 b/roles/nagios_client/templates/check_rabbitmq_server.cfg.j2
new file mode 100644
index 000000000..498a8757e
--- /dev/null
+++ b/roles/nagios_client/templates/check_rabbitmq_server.cfg.j2
@@ -0,0 +1 @@
+command[check_nrpe_check_rabbitmq_server]=exec /usr/lib64/nagios/plugins-rabbitmq/check_rabbitmq_server -H localhost --password "{{ (env == 'production')|ternary(rabbitmq_monitoring_password_production, rabbitmq_monitoring_password_staging) }}" --user nagios-monitoring
diff --git a/roles/nagios_server/tasks/main.yml b/roles/nagios_server/tasks/main.yml
index 2d6d50c31..f61584ed6 100644
--- a/roles/nagios_server/tasks/main.yml
+++ b/roles/nagios_server/tasks/main.yml
@@ -110,6 +110,28 @@
- config
- nagios_server
+- name: Ensure the nrpe.d directory exists for nrpe configs
+ file:
+ dest: /etc/nrpe.d
+ state: directory
+ tags:
+ - nagios_server
+
+- name: Add nrpe configurations to /etc/nrpe.d
+ template:
+ src: "/nrpe/{{ item }}.j2"
+ dest: "/etc/nrpe.d/{{ item }}"
+ owner: root
+ group: root
+ mode: 0600
+ with_items:
+ - check_rabbitmq_server.cfg
+ notify:
+ - restart nrpe
+ tags:
+ - config
+ - nagios_server
+
## Copy over the nagios configs
- name: Copy /etc/nagios/conf.d/*cfg files
copy: src=nagios/configs/{{ item }} dest=/etc/nagios/conf.d/{{ item }}
diff --git a/roles/nagios_server/templates/nrpe/check_rabbitmq_server.cfg.j2 b/roles/nagios_server/templates/nrpe/check_rabbitmq_server.cfg.j2
new file mode 100644
index 000000000..498a8757e
--- /dev/null
+++ b/roles/nagios_server/templates/nrpe/check_rabbitmq_server.cfg.j2
@@ -0,0 +1 @@
+command[check_nrpe_check_rabbitmq_server]=exec /usr/lib64/nagios/plugins-rabbitmq/check_rabbitmq_server -H localhost --password "{{ (env == 'production')|ternary(rabbitmq_monitoring_password_production, rabbitmq_monitoring_password_staging) }}" --user nagios-monitoring
--
2.21.0
4 years, 4 months