About JS framework
by Pierre-Yves Chibon
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,
Pierre
7 months, 2 weeks
[Upgrade] pagure: 2.90.1
by Pierre-Yves Chibon
Good Morning Everyone,
Shortly after releasing 2.15 we realized the SQL-based locking mechanism we had
introduced was causing more problems than solving.
So we released 2.15.1 to try to mitigate them but that wasn't satisfactory.
Patrick has spent the majority of his time since the end of the last week (and
thus a good part of his week-end) re-architecturing how pagure writes to git
repos so that it is now handled by an async service (running under the service
pagure_worker).
The change is so large that it was deemed worthy of being called pagure 3.0.
However, we needed to stabilize the pagure instance running on pagure.io, among
other because it is being used by releng for releasing.
So, we decided to create pre-3.0 releases: 2.90.0 yesterday, then 2.90.1 today
that include the new architecture but aren't official releases (no tags, just
commits in a side-branch and their tarball uploaded).
Kevin had +1 the upgrade earlier this week on IRC. Patrick and I being both
involved in the change (Patrick to write it, me to test, merge and release)
considered we both counted as +0.5, making this the required +2.
After pushing 2.90.1 to stg and testing it there, we considered it good to go
and pushed it to prod.
So pagure should be much more stable and able to cope with the coming days, and
we'll cut the official 3.0 after freeze once all docs have been adjusted.
Thanks to Patrick for leading this change!
Happy hacking!
Pierre
5 years, 11 months
Fedora 26 Beta Freeze now in effect
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 26 Beta
release. This is a pre-release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 26 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:
git clone
https://infrastructure.fedoraproject.org/infra/ansible.git/scripts/freeze...
-i inventory
Any hosts listed as freezes is frozen until 2017-05-30 (or later if Beta
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.
Thanks,
kevin
5 years, 11 months
Combined bodhi template files
by InvalidPath
Attached is my combination of the two bodhi templates.. stg and prod.
Please take a look and gimmie some criticisms. :)
Ben
5 years, 12 months
Retroactive FBR: Fix mailman3 "template" scheme
by Patrick Uiterwijk
Hi,
While I was debugging settings not saving for Mailman, I found out
that this was caused
by the schema of the "template" table being incorrect.
It had the following gem:
password | timestamp without time zone
I've just ran the following query to make it be identical to what's in the code:
alter table template alter password type character varying;
Can I get +1s on this change?
p.s.: This is about 5 hours old, but seems I sent it to devnull.
5 years, 12 months
FMN 1.3.0
by Jeremy Cline
Hey all,
A new version of FMN, 1.3.0, has been released and will be pushed to
staging shortly so that it'll be ready when the freeze is over. The
changelog is included below.
1.3.0
=====
Refactors
---------
* Merge the fmn.sse repository into the fmn repository.
* Merge the fmn.web repository into the fmn repository.
Rule Changes
------------
* Taskotron rules: Particular tasks can now be matched using wildcards
(PR #197).
* Taskotron rules: add abicheck as a critical task (PR #198).
Performance Improvements
------------------------
* Loading rules is now cached in memory which speeds up user creation by
several orders of magnitude: creating 100 users went from 221 seconds
to 3.3 (Issue #191).
* The map of rule strings to rule Python objects is now cached which
improves preference loading time by approximately an order of
magnitude.
Bugfixes
--------
* Fix a bug where cache regions were configured to never expire cached
keys (Issue #194).
--
Jeremy Cline
XMPP: jeremy(a)jcline.org
IRC: jcline
6 years
FBR: up timeouts on kojipkgs varnish
by Kevin Fenzi
Greetings.
Due to issues with slow storage recently we have seen kojipkgs spike in
load and be slow to return packages to download. This makes varnish
return a 503 back to the build or compose and causes them to fail.
We are trying to sort out the storage issue, but in the mean time I
would like to increase the timeouts on varnish so it hopefully doesn't
hit this as much.
+1s?
diff --git a/roles/varnish/templates/kojipkgs.vcl.j2
b/roles/varnish/templates/kojipkgs.vcl.j2
index c3f7d51..66a8e9d 100644
--- a/roles/varnish/templates/kojipkgs.vcl.j2
+++ b/roles/varnish/templates/kojipkgs.vcl.j2
@@ -25,10 +25,11 @@ acl purge {
backend localapache {
.host = "127.0.0.1";
.port = "8080";
+ .first_byte_timeout = 60s;
.probe = {
.url = "/";
.interval = 5s;
- .timeout = 1s;
+ .timeout = 5s;
.window = 5;
.threshold = 3; }
}
kevin
6 years
