staging openshift reinstall
by Kevin Fenzi
greetings everyone.
I've been playing around with openshift staging for the last few weeks
and enabling some cool features. :) However, I now seem to have gotten
it in a odd state and I think it's time to do a fresh install.
If no one objects soon, I will reinstall it this afternoon, then run all
the various app playbooks to redeploy them.
Hopefully after that we will have multitenant networking (all apps are
isolated from each other unless we want to allow them to talk),
metrics/logging/alerting (with all the cool apps:
kibana/elasticsearch/prometheus/fluentd/etc).
If all looks well with this, we can roll this out to prod after beta
(probibly by doing a reinstall there as well).
kevin
5 years, 9 months
FBR: Fix openshift websockets
by Patrick Uiterwijk
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi all,
After a bunch of debugging, I found that the problems with Openshifts websockets (used for logs and shell etc) were due to:
- - HTTP/2 (Upgrade: and Connection: headers get silently dropped for HTTP/2, websockets aren't defined yet for it...)
- - Balancer protocols
I'd like +1s to apply the underneath patch to fix this, and enable logs from the prod openshift web console.
It is working in staging.
commit 095fe0257320998e0f316787042cb4a0245ad345 (HEAD -> master)
Author: Patrick Uiterwijk <patrick(a)puiterwijk.org>
Date: Wed Sep 12 01:55:40 2018 +0200
Fix websockets for prod openshift
Signed-off-by: Patrick Uiterwijk <patrick(a)puiterwijk.org>
diff --git a/playbooks/include/proxies-websites.yml b/playbooks/include/proxies-websites.yml
index 403e1e6f1..5e9bf89ae 100644
- --- a/playbooks/include/proxies-websites.yml
+++ b/playbooks/include/proxies-websites.yml
@@ -576,6 +576,9 @@
site_name: os.fedoraproject.org
sslonly: true
cert_name: "{{wildcard_cert_name}}"
+ # The Connection and Upgrade headers don't work for h2
+ # So non-h2 is needed to fix websockets.
+ use_h2: false
tags:
- os.fedoraproject.org
@@ -585,6 +588,9 @@
sslonly: true
cert_name: "{{os_wildcard_cert_name}}"
SSLCertificateChainFile: "{{os_wildcard_int_file}}"
+ # The Connection and Upgrade headers don't work for h2
+ # So non-h2 is needed to fix websockets.
+ use_h2: false
tags:
- app.os.fedoraproject.org
diff --git a/roles/httpd/reverseproxy/templates/reversepassproxy.conf b/roles/httpd/reverseproxy/templates/reversepassproxy.conf
index 77a8dd35b..06f913720 100644
- --- a/roles/httpd/reverseproxy/templates/reversepassproxy.conf
+++ b/roles/httpd/reverseproxy/templates/reversepassproxy.conf
@@ -19,7 +19,6 @@ ProxyPreserveHost On
{% if balancer_name is defined %}
SSLProxyEngine On
- -{% if env == "staging" %}
<Proxy "balancer://{{balancer_name}}-websocket">
{% for member in balancer_members %}
@@ -32,7 +31,6 @@ RewriteCond %{HTTP:Upgrade} ^WebSocket$ [NC]
RewriteCond %{HTTP:Connection} ^Upgrade$ [NC]
RewriteRule .* "balancer://{{ balancer_name }}-websocket%{REQUEST_URI}" [P]
- -{% endif %}
<Proxy "balancer://{{balancer_name}}">
{% for member in balancer_members %}
BalancerMember "https://{{ member }}"
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJbmFaOAAoJEIZXmA2atR5QgWEP/RsP1mtvud2LOSFLcg6CLbl1
dfB4hH39rmY27/Gkr0keLxgtBczejrhJ1HQKMDZiInegESvgE7+msLN/SAHnjG8H
5KZ5SNRWfyEdlYvXxk5CMZjpOIeZMWHff2+LJvfBX2Z5GNq6OPzgtiM+7jPwjlma
NDGqgHgDRDkhQKoAy34l069GieHBF3P7W0rP8A3Jf56WdBrahCAspdhHYU79TTyg
8tM0wsFYCBFxOJfH1YfUKp6vmfs2Fi255PBALETUZe7LsLD+E5RQI5ILZwWhHUlr
JD9EpV74wk128mygwfDZCfWpnEPuHVaUWAB5yHpIuoXzHENysIZTJ0oF3JNmxh5K
F2c0tHutUD9zSigKbUKLql2ZHQCRz9iM8Hhl/EL7YqQAZosHzf68HqhTjjwazD9U
vMXBrwmIZrmjgqtqOyhWJ3SH8MuosmD9Exbx14ekaq0p8uj7g8kzug9le1oQjk3Q
4HfxVphfWHdZ2LMAn4lOboiZACqU3rkvYEk+7uwCXpRLioO0UdVTaqLoyx9Z2NeP
StHuClZZOMgFAQ38b6VsLGBOa7nUj/JzDeEVrdaIX0tzaNWGeaEVY9kpOIFDRaOg
h02O1aJJCzX+n5Xz3DtJH84GgWqL2Ir4sX8ZgIpkRJW1mpES0JXOpAbhh/I9M3zG
IfmiXpXmSa1CK0FXufNB
=9UjA
-----END PGP SIGNATURE-----
5 years, 9 months
Fedora Infrastructure 2018-09-13 meeting moved to 1500 UTC
by Stephen John Smoogen
Due to another meeting, we need to move this meeting back an hour on
Thursday to 1500 UTC. This will be a 1 time move back.
We apologize for any problems this causes people in very early time zones.
--
Stephen J Smoogen.
5 years, 9 months
FBR - Upgrade MBS
by Ralph Bean
I'd like to upgrade MBS on either Monday or Tuesday of next week to
module-build-service-2.6.0-1.el7 and libmodulemd-1.6.3-2.el7.
- https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-0a7da7520d
- https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-ee8aeba3a6
There is no database migration. It has a few bugfixes and a few new features:
- MBS can now block the building of a module stream, if its stream is
marked as EOL in PDC (requested by mboddu).
- There's also an important bugfix for sgallagh that allows building
modules that refer to refs of components not under their master
branch - this is related to the libmodulemd update.
I haven't upgraded staging yet, but would start to do so next week.
+1 to proceed? Or hold off until after freeze?
-Ralph
5 years, 9 months
Meeting Agenda Item: Introduction Christophe Dumont
by Christophe DUMONT
Hello !
IRC handle : chris787
My name is Christophe, I'm from France Grenoble. I work as a sysadmin for 3 years now and i'd like to contribute/help to the fedora project.
I have skills in sysadmin and automation (ansible), and would like to work on the infrastructure but first learn how fedora project works !
Christophe
5 years, 9 months
Copr is DOWN
by Radka Janekova
Please whoever can fix it asap, getting production downtime here.
Thanks,
Radka
------------------------------
*Radka Janeková*
.NET Engineer, Red Hat
*radka.janek(a)redhat.com <radka.janek(a)redhat.com>*
IRC: radka | Freenode: Rhea
5 years, 9 months
Fedora 29 Beta Release Readiness meeting
by Ben Cotton
Dear all,
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 29
Beta Release Readiness meeting. This meeting will be held on Thursday,
2018-09-13 at 19:00 UTC.
We will meet to make sure we are coordinated and ready for the Beta
release of Fedora 29. Please note that this meeting will be held even
if the release is delayed at the Go/No-Go meeting on the same day two
hours earlier.
You may receive this message several times in order to open this
meeting to the teams and to raise awareness, so hopefully more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
For more information, see
https://fedoraproject.org/wiki/Release_Readiness_Meetings.
I will ask for readiness from each of the teams listed below. If there
are additional teams that should be explicitly included, let me know.
All teams and contributors are welcome to provide input at the
meeting.
* Ambassadors
* Cloud WG
* Design
* Desktop
* Documentation
* Fedora Project Leader
* FESCo
* Infrastructure
* Marketing
* QA
* Release Engineering
* Server WG
* Spins
* Translations
* Websites
View the meeting on Fedocal:
https://apps.fedoraproject.org/calendar/Fedora%20release/2018/9/10/#m9337
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
5 years, 9 months
Infrastructure Meeting Agenda 2018-09-06
by Stephen John Smoogen
Here is the initial agenda. Please add items to be discussed
This shared document is for the next fedora infrastructure meeting.
= Preamble =
The infrastructure team will be having its weekly meeting tomorrow,
2018-09-06 at 14:00 UTC in #fedora-meeting-1 on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
fedora-infrastructure-meeting-next is the document.
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 (2018-09-06)
#meetingname infrastructure
#topic aloha
#chair nirik pingou puiterwijk relrod smooge tflink threebean
= 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
= 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 tflink is on extended PTO
#info Beta Freeze is in effect. All changes to frozen systems in
Infrastructure will require +1
= 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 Nirik is on call from 2018-08-30->2018-09-06
#info Relrod is on call from 2018-09-06->2018-09-13
#info ??? is on call from 2018-09-13->2018-09-20
#info Summary of last week: (from Nirik)
#topic Tickets discussion
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
Go thru each ticket one by one
= 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, 9 months