FBR: update prod tag name in WaiverDB
by Giulia Naponiello
Hello,
we would like to change the name of the tag in quay.io for WaiverDB. Could
you make this change?
Here's the patch:
diff --git a/roles/openshift-apps/waiverdb/templates/imagestream.yml
b/roles/openshift-apps/waiverdb/templates/imagestream.yml
index 3fe37a481..7758ea5c6 100644
--- a/roles/openshift-apps/waiverdb/templates/imagestream.yml
+++ b/roles/openshift-apps/waiverdb/templates/imagestream.yml
@@ -20,5 +20,5 @@ spec:
name: quay.io/factory2/waiverdb:latest
{% else %}
# This is 'prod' tag is maintained by hand.
- name: quay.io/factory2/waiverdb:prod
+ name: quay.io/factory2/waiverdb:prod-fedora
{% endif %}
Thank you!
Cheers
Giulia
5 years
mirrorlist server with Python3
by Adrian Reber
The latest release of MirrorManager2 is still in updates-testing. I did
not want to push this version to updates-released because this is the
first Python3 based released.
Could someone test the version from updates-testing? Update the
mirrorlist container and test it on one of the proxies?
Adrian
5 years
FBR: Adding remotepath to websocket balancers
by Tim Flink
The current template assumes that websockets are at the base of a URL
but that is not true for our buildmaster. This patch adds remotepath
to the end of the websocket url if remotepath is defined.
---
roles/httpd/reverseproxy/templates/reversepassproxy.conf | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/roles/httpd/reverseproxy/templates/reversepassproxy.conf
b/roles/httpd/reverseproxy/templates/reversepassproxy.conf index
deec40b..6131b5d 100644 ---
a/roles/httpd/reverseproxy/templates/reversepassproxy.conf +++
b/roles/httpd/reverseproxy/templates/reversepassproxy.conf @@ -29,10
+29,18 @@ SSLProxyEngine On <Proxy
"balancer://{{balancer_name}}-websocket"> {% for member in
balancer_members %} {% if
http_not_https_yes_this_is_insecure_and_i_feel_bad %}
+ {% if remotepath is defined %}
+ BalancerMember "ws://{{ member }}{{ remotepath }}
+ {% else %}
BalancerMember "ws://{{ member }}"
+ {% endif %}
+ {% else %}
+ {% if remotepath is defined %}
+ BalancerMember "ws://{{ member }}{{ remotepath }}
{% else %}
BalancerMember "wss://{{ member }}"
{% endif %}
+ {% endif %}
{% endfor %}
</Proxy>
5 years
[Fedocal] Reminder meeting : Bodhi stakeholders' meeting
by bowlofeggs@fedoraproject.org
Dear all,
You are kindly invited to the meeting:
Bodhi stakeholders' meeting on 2019-03-22 from 11:00:00 to 11:45:00 US/Eastern
At fedora-meeting-2(a)irc.freenode.net
The meeting will be about:
We will meet in #fedora-meeting-2 on Freenode to talk about what has been going on in Bodhi development and what is currently planned for the future. There will be an open floor at the end for the airing of grievances, but only after someone pins me before the Festivus tree.
The agenda will be posted in the bodhi-stakeholders document in the Infrastructure gobby repository by March 20.
Source: https://apps.fedoraproject.org/calendar/meeting/9485/
5 years
FBR for Alessandro Lorenzi for nagios certgetter change.
by Stephen John Smoogen
I have reviewed this and will sponsor it.
---------- Forwarded message ---------
From: Alessandro Lorenzi <pagure(a)pagure.io>
Date: Sat, 16 Mar 2019 at 17:24
Subject: [fedora-infrastructure] Issue #7635: Add monitoring for httpd
on certgetter
To: <smooge(a)gmail.com>
neron added a new comment to an issue you are following:
``
Hi,
first patch in fedora-infrastructure!
```
From 191cd95874e5f2f0141032cc211f2b405255df6d Mon Sep 17 00:00:00 2001
From: Alessandro Lorenzi <alorenzi(a)alorenzi.eu>
Date: Sat, 16 Mar 2019 22:10:12 +0100
Subject: [PATCH] Monitoring: add service certgetter http
Refs: #7635
---
roles/nagios_server/files/nagios/services/certgetter.cfg | 6 ++++++
1 file changed, 6 insertions(+)
create mode 100644 roles/nagios_server/files/nagios/services/certgetter.cfg
diff --git a/roles/nagios_server/files/nagios/services/certgetter.cfg
b/roles/nagios_server/files/nagios/services/certgetter.cfg
new file mode 100644
index 000000000..2b143ed23
--- /dev/null
+++ b/roles/nagios_server/files/nagios/services/certgetter.cfg
@@ -0,0 +1,6 @@
+define service {
+ host_name certgetter01.phx2.fedoraproject.org
+ service_description certgetter-http
+ check_command check_http!certgetter01.phx2.fedoraproject.org
+ use defaulttemplate
+}
--
2.17.1
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-infrastructure/issue/7635
--
Stephen J Smoogen.
5 years
RFR: Message-Tagging-Service
by Chenxiong Qi
Hi all,
This mail is for a new micro-service called Message-Tagging-Service (aka
MTS). It serves to tag module build triggered by specific MBS event.
More detailed information is provided inside RFR ticket[1].
MTS works with a series of predefined rules to see if a module build
should be tagged with one or more tags. There is requirement coming from
module maintainers to ensure a module build is tagged into correct
platforms to fulfill the dependencies of module metadata. Comment[2] has
a specific use case for that.
So far, MTS has been containerized and deployed in internal. The image
is available from quay.io[3]. We would love to run MTS in Fedora as well
in order to make it easier to manage module build tag for module
maintainers and rel-eng.
If anything is missed for this mail thread, please point out. Questions
welcome! Thanks for your time.
[1] https://pagure.io/fedora-infrastructure/issue/7563
[2] https://pagure.io/fedora-infrastructure/issue/7563#comment-553774
[3] https://quay.io/repository/factory2/message-tagging-service
--
Regards,
Chenxiong Qi
5 years
[FBR ] update-fullfiletimelist: make new-updates-sync use the fedora-secondary lock file
by kevin@scrye.com
From: Kevin Fenzi <kevin(a)scrye.com>
Currently update-fullfiletimelist is called from 4 machines:
* rawhide-composer: after rawhide compose
* branched-composer: after branched compose
* secondary01: in a cron every hour updating only /pub/alt as it can change anytime.
* bodhi-backend01: after ever updates sync that has content synced
We need bodhi-backend01 to use the same lock as rawhide/branched composers since they
update the same modules and we don't want them to step on each other.
Signed-off-by: Kevin Fenzi <kevin(a)scrye.com>
---
roles/bodhi2/backend/files/new-updates-sync | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync
index 0fa893b..7d6e456 100755
--- a/roles/bodhi2/backend/files/new-updates-sync
+++ b/roles/bodhi2/backend/files/new-updates-sync
@@ -234,7 +234,7 @@ def update_fullfilelist(modules):
logger.info('No filelists to update')
return
cmd = ['/usr/local/bin/update-fullfiletimelist', '-l',
- '/tmp/update-fullfiletimelist.lock', '-t', '/pub']
+ '/pub/fedora-secondary/update-fullfiletimelist.lock', '-t', '/pub']
cmd.extend(modules)
run_command(cmd)
--
1.8.3.1
5 years
Meeting Agenda 2019-03-21
by Stephen John Smoogen
= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2019-03-21 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document at
https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructu...
which can be edited for the agenda (see: https://fedoraproject.org/wiki/Gobby )
Please try and review and edit that document before the meeting and we
will use it to have our agenda of things to discuss. A copy as of today
is included in this email.
If you have something to discuss, add the topic to the discussion area
with your name. If you would like to teach other folks about some
application or setup in our infrastructure, please add that topic and
your name to the learn about section.
= Introduction =
We will use it over the week before the meeting to gather status and info and
discussion items and so forth, then use it in the irc meeting to transfer
information to the meetbot logs.
= Meeting start stuff =
#startmeeting Infrastructure (2019-03-21)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink threebean cverna
mizdebsk mkonecny
= Let new people say hello =
#topic New folks introductions
#info This is a place where people who are interested in Fedora
Infrastructure can introduce themselves
#info Getting Started Guide:
https://fedoraproject.org/wiki/Infrastructure/GettingStarted
= Status / Information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need
to discuss)
(Please use #info <the thing> - your name)
#topic announcements and information
#info Beta Freeze Is Currently Going On. Please get FBR for frozen systems.
= Things we should discuss =
We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus /suor decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use #topic your discussion topic - your username)
#topic Oncall
#info bowlofeggs is on call from 2019-03-14 -> 2019-03-21
#info nirik is on call from 2019-03-21 -> 2019-03-28
#info relrod is on call from 2019-03-28 -> 2019-04-04
#info smooge is on call from 2019-04-04 -> 2019-04-11
#info ????? is on call from 2019-04-11 -> 2019-04-18
#info Summary of last week: (from bowlofeggs )
#topic Monitoring discussion
#info https://nagios.fedoraproject.org/nagios
#info Go over existing out items and fix
#topic Tickets discussion
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
Go thru each ticket one by one
#topic Priorities for next week?
#info please put tickets needing to be focused on here
=====
Put all topics for discussion under here
=====
= Apprentice office hours =
#topic Apprentice Open office minutes
#info A time where apprentices may ask for help or look at problems.
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
= Learn about some application or setup in infrastructure =
(This section, each week we get 1 person to talk about an application or setup
that we have. Just going over what it is, how to contribute, ideas for
improvement,
etc. Whoever would like to do this, just add the i/nfo in this section. In the
event we don't find someone to teach about something, we skip this section
and just move on to open floor.)
#info
= Meeting end stuff =
#topic Open Floor
#endmeeting
--
Stephen J Smoogen.
5 years
Meeting Agenda Item: Introduction Alessandro Lorenzi (aka neron,
alorenzi)
by Alessandro Lorenzi
Hi guys,
I've lurked in mailing list and irc enough, It's time to introduce myself!
I'm Alessandro Lorenzi, "neron" in fas, "alorenzi" in irc, italian, and
fedora user for roughly 1/3 of my life.
I was an active Fedora Ambassador in the past. In last few years my
free software user group has been disgregated arround the Europe and now
is more difficult to organize events. Because of that, my activity in
the linux events has been decreased (shame on me).
I work as system engineer, my team mainly use puppet, and sometime ansible.
Some weeks ago, I don't remember what I was looking for, I've found the
fedora-infra-docs and it was an interesting reading, after that I've
started to study the fedora-infra git repo and here I am!
Bye!
--
Alessandro Lorenzi
5 years
FBR : Greenwave gunicorn timeout back to 30s
by Clement Verna
Hi all,
I would like to revert greenwave's gunicorn timeout to the default
30s. Changing it to 10+min was useful for our investigation but it now
slows down bodhi cron job. Also the greenwave team is working on fix
for this so long term we should not need to have a specific timeout.
I am leaving in place the longer OpenShift timeout on the route, so
that it is easier to know where the timeout comes from.
diff --git a/roles/openshift-apps/greenwave/templates/buildconfig.yml
b/roles/openshift-apps/greenwave/templates/buildconfig.yml
index d836b482d..7bb5420ba 100644
--- a/roles/openshift-apps/greenwave/templates/buildconfig.yml
+++ b/roles/openshift-apps/greenwave/templates/buildconfig.yml
@@ -30,7 +30,6 @@ spec:
# Become non-root again
USER 1001
- ENTRYPOINT docker/install-ca.sh && gunicorn-3 --workers 8
--timeout 660 --graceful-timeout 300 --bind 0.0.0.0:8080
--access-logfile=- --enable-stdio-inheritance greenwave.wsgi:app
strategy:
type: Docker
dockerStrategy:
--
2.20.1
+1s ?
5 years