Good Morning Everyone,
Our infrastructure is mostly a python store, meaning almost all our apps are
written in python and most using wsgi.
However in python we are using a number of framework:
* flask for most
* pyramid for some of the biggest (bodhi, FAS3)
* Django (askbot, Hyperkitty)
* TurboGears2 (fedora-packages)
* aiohttp (python3, async app: mdapi)
While this makes sometime things difficult, these are fairly standard framework
and most of our developers are able to help on all.
However, as I see us starting to look at JS for some of our apps (fedora-hubs,
wartaa...), I wonder if we could start the discussion early about the different
framework and eventually see if we can unify around one.
This would also allow those of us not familiar with any JS framework to look at
the recommended one instead of picking one up semi-randomly.
So has anyone experience with one or more JS framework? Do you have one that
would you recommend? Why?
Thanks for your inputs,
(sorry this email was delayed, it didn't seem to send yesterday when I
thought I sent it).
we are now in the infrastructure freeze leading up to the Fedora 29
Beta release. This is a pre release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 29 Beta when it's available.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2018-09-18 (or later if
release slips). Frozen hosts should have no changes made to them without
a sign-off on the change from at least 2 sysadmin-main or rel-eng
members, along with (in most cases) a patch of the exact change to be
made to this list.
-----BEGIN PGP SIGNED MESSAGE-----
Can I get +1s for the underneath patch to fix mediawiki not calling their own API correctly?
This breaks creating new pages on the wiki (and I should've fixed it way earlier, but forgot).
- From caa8183ffa572ee6ded823e3d1e895d1dcc6a466 Mon Sep 17 00:00:00 2001
From: Patrick Uiterwijk <patrick(a)puiterwijk.org>
Date: Fri, 31 Aug 2018 19:31:58 +0200
Subject: [PATCH] Fix creating of new wiki pages
This breaks because mediawiki doesn't follow their own documented API and doesn't pass
a base revision ID when creating new pages.
Signed-off-by: Patrick Uiterwijk <patrick(a)puiterwijk.org>
roles/mediawiki/files/fedmsg-emit.php | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/roles/mediawiki/files/fedmsg-emit.php b/roles/mediawiki/files/fedmsg-emit.php
index c62bd3ee7..846d28e8a 100644
- --- a/roles/mediawiki/files/fedmsg-emit.php
@@ -205,7 +205,7 @@ function article_save(
- - $baseRevId,
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
We are trying to install a aarch64 osbs node for staging so we can get
multi-arch containers building, but for some reason the install is not
completing correctly. It seems to hang at:
[ OK ] Started Service enabling compressing RAM with zRam.
I'd like to:
* disable buildvm-arvm7-23/24 in koji
* update / reboot aarch64-c23n1/c24n1
* re-enable the armv7 builders.
Hopefully this will allow us to get a working install for osbs aarch64
So as discussed on https://pagure.io/fedora-infrastructure/issue/7120 , here
is the 2nd part for the website. That's cut/paste/sed of the 2 others (silverblue,
and coreos). It shouldn't impact negatively anything on openshift, but
the master in prod are frozen, hence the FBR.
Proxies, etc, are already done.
This needs review by both infrastructure and people who are familiar
with osbs. I am mostly copya pasta editing here so it may or may not
work. It is also not clear if we need both a master and a node or just
Stephen J Smoogen.
Right before freeze we got a security qemu update (which was auto
applied) on buildvm-ppc64le-01/02. Unfortunately this broke creating
images and since those two are our ppc64le image builder machines it's
not been fun.
I'd like to update them with qemu-2.11.2-3.fc28 which fixes the problem
commit (hopefully). If it doesn't it cannot make it worse, as they
always fail image building now anyhow.
Bug https://bugzilla.redhat.com/show_bug.cgi?id=1614948 has details and
https://pagure.io/releng/issue/7703 has information on all the images
that haven't been building.