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,
we are now in the infrastructure freeze leading up to the Fedora 29
Final release. This is a final release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 29 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-10-23 (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.
Here is a patch (available in email attachment) to include updates-testing
as well during Atomic Host ISO creation in bodhi updates-testing run.
multiple repos to lorax should work fine on Fedora >=29 -
Can I get +1 for the patch?
I would love to be a part of the team. I have worked on C/C++, Python.
I would love to work on any C/C++ related stuff.
Please share your inputs to help me get started. This is my first time
working with such a big community, so any input will be helpfull.
Registered nick on #fedora -- _Constant
I thought I would send a short note on something I put in place before
the freeze. Basically it seems, even though we have SOPs and docs, we
spend a lot of time around release milestones changing files in ansible,
realizing we forgot something and changing another one, etc.
I'd like to minimize that.
To that end I have created some variables in ansible. You can see them
in the ansible/vars/all/ directory. Every file in this directory tree is
included via the virt_instance_create and persistent_cloud tasks (so
most of our machines, exclusing bare metal ones).
00-FedoraCycleNumber.yaml is the number only of the current stable
Fedora. So, right now it's 28, but soon when f29 is released it will
change to 29. This is used for many of the later variables so it's 00-
to be loaded first.
FedoraBranchedBodhi.yaml - indicates is we are using Bodhi in a new branch.
FedoraBranchedNumber.yaml - Number of the curret branched version.
FedoraBranched.yaml - If there is a branched or not.
FedoraPreviousCycleNumber.yaml - This is the 'older' stable release.
Right now 27.
FedoraPreviousPreviousCycleNumber.yaml - This is the 'older' 'older'
stable release. Right now we don't have one, but after f29 releases, f27
will be this until it EOLs in a month.
FedoraPreviousPrevious.yaml - If there is a 'older' 'older' release.
FedoraRawhideNumber.yaml - number of current rawhide (30)
Frozen.yaml - If infrastructure is frozen.
We can add things as we go, but some rules:
* I think for these CamelCase is easiest to read, so keep to that.
* If you can base the variable on others so you never have to edit it,
* It should be of general use.
So, given these, I updated the bodhi config to use them. So, when f29 is
* 00-FedoraCycleNumber.yaml - edit and change to 29
* FedoraPreviousPrevious.yaml - edit and change to true
* FedoraBranched.yaml - edit and set to false
* Frozen.yaml - edit and set to false a day after release.
Then we just need to run playbooks and everything adjusts. There are a
number more places we could leverage this, so I encourage people to look
for those and submit patches to enable them. In particular the
new-updates-sync script could use these so we don't have to edit it all
Hope that makes sense and feedback welcome.
You are kindly invited to the meeting:
Infra Office Hours on 2018-10-30 from 18:00:00 to 19:00:00 UTC
The meeting will be about:
Weekly hour dedicated to answer questions or help people with fixing tickets or implementing features.
Author: Mohan Boddu <mboddu(a)redhat.com>
Date: Fri Oct 26 14:31:08 2018 +0000
F29 is now GA and no need of any policy changes
This change is to just disable
Signed-off-by: Mohan Boddu <mboddu(a)redhat.com>
diff --git a/vars/all/FedoraBranchedBodhi.yaml
index 2b6c292..8a72bfa 100644
@@ -1 +1 @@
I'm not sure if it should go to test/infra or other list :)
---------- Forwarded message ---------
From: Pablo Daniel Estigarribia Davyt <pablodav(a)gmail.com>
Date: sáb., 27 oct. 2018 a las 22:38
Subject: dnf getting error to sync cache in fedora 29
To: For testing and quality assurance of Fedora releases <
I'm testing fedora 29 since it becomes beta.
Unique issue I have noticed is with dnf when trying to install/update
I get "error to sync cache" many times.
Also I got errors like:
[MIRROR] kernel-modules-4.18.16-300.fc29.x86_64.rpm: Status code: 404 for
After retrying many times (4 or 5 sometimes), it works. But it didn't
I'm testing from Uruguay.
My repos are standard ones only.
The issue I see here is with the domain I got in previous error:
Issue in Uruguay is:
our best connectivity to got out from our country is with EEUU (Miami).
To go to any other site, like: Colombia, Argentina, Brasil, etc... Traffic
first goes to Miami, then to that other country, then comes from Miami
The best mirrors for Uruguay should be the closest to Miami EEUU.