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
5 months, 1 week
Fedora 27 Beta Freeze now in effect
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 27 Beta
release. This is a pre-release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 27 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
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2017-09-19 (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
4 years, 11 months
Fedora 27 Final Freeze now in effect
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 27
release. This is a final release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 27 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
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2017-10-31 (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.
Thanks,
kevin
5 years, 4 months
Freeze Break Request: fix purge-ami's cron
by Kevin Fenzi
Greetings.
I happened to notice some cron output a while back and looked into it and found a slight mistake in the purge-ami's cron.
'git clone -n' was being used which tells it to not bother checking out HEAD after the clone. Just leave the checkout empty. Then it tries to run things from the checkout that just fails. :)
The solution is just to drop the -n I think, but I'd love to have sayan confirm.
kevin
--
diff --git a/roles/releng/files/purge-amis b/roles/releng/files/purge-amis
index b49942a..be677e5 100644
--- a/roles/releng/files/purge-amis
+++ b/roles/releng/files/purge-amis
@@ -1,5 +1,5 @@
# Remove launch permissions from the AMIs after every 5 days
-0 0 */5 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XXXXXX` && pushd $TMPDIR && git clone -n https://pagure.io/releng.git && cd releng/scripts && AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ ec2_image_delete_access_key }} ./clean-amis.py --change-perms && popd && rm -rf $TMPDIR
+0 0 */5 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XXXXXX` && pushd $TMPDIR && git clone https://pagure.io/releng.git && cd releng/scripts && AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ ec2_image_delete_access_key }} ./clean-amis.py --change-perms && popd && rm -rf $TMPDIR
# Delete the AMIs after every 10 days.
-0 0 */10 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XXXXXX` && pushd $TMPDIR && git clone -n https://pagure.io/releng.git && cd releng/scripts && AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ ec2_image_delete_access_key }} ./clean-amis.py --delete && popd && rm -rf $TMPDIR
+0 0 */10 * * root TMPDIR=`mktemp -d /tmp/purgeamis.XXXXXX` && pushd $TMPDIR && git clone https://pagure.io/releng.git && cd releng/scripts && AWS_ACCESS_KEY={{ ec2_image_delete_access_key_id }} AWS_SECRET_ACCESS_KEY={{ ec2_image_delete_access_key }} ./clean-amis.py --delete && popd && rm -rf $TMPDIR
5 years, 4 months
Freeze Break Request: update rpm on builders
by Kevin Fenzi
Greetings.
In order to allow the new rich deps that rust packaging requires we need
to update rpm on the builders to a version that has backported support
for 3 new rich deps. It needs these at srpm generation time to
understand the new rich deps.
ignatenkobrain has created a rpm with this backported patches and has
promised to update it as needed. When we update builders to f27 after
the release we will no longer need it, so it's only for a few weeks.
We updated staging builders and tested and all looks good there.
So, I would like to:
koji move-build f26-infra-stg f26-infra rpm-4.13.0.2-1.fc26.infrastructure
then
update rpm on all the prod builders.
In the event this causes a problem we can downgrade them back and/or get
a fixed version.
+1s?
kevin
5 years, 4 months
F26 delta RPMs
by Ron Yorston
Are delta RPMs for F26 broken again?
I've just run an update involving glibc, the kernel and libreoffice and
not one of the RPMs had a delta.
Ron
5 years, 4 months
FBR: Signing f27-u-t ostrees
by Patrick Uiterwijk
Hi,
The Atomic SIG really wants the F27 atomic tree refs to be created,
which only happens if robosignatory signs them.
Could I get +1/-1s for the underneath patch?
Patrick
commit dfbd764b0ce16b9c4df190801bdc32a9e9b9b985 (HEAD -> master)
Author: Patrick Uiterwijk <patrick(a)puiterwijk.org>
Date: Tue Oct 31 12:51:44 2017 +0100
Enable signing of f27-u-t ostrees
Signed-off-by: Patrick Uiterwijk <patrick(a)puiterwijk.org>
diff --git a/roles/robosignatory/files/robosignatory.production.py
b/roles/robosignatory/files/robosignatory.production.py
index 66a9ef674..bae63c46c 100644
--- a/roles/robosignatory/files/robosignatory.production.py
+++ b/roles/robosignatory/files/robosignatory.production.py
@@ -179,6 +179,10 @@ config = {
'directory': '/mnt/fedora_koji/koji/compose/ostree/27/',
'key': 'fedora-27'
},
+ 'fedora/27/x86_64/testing/atomic-host': {
+ 'directory': '/mnt/fedora_koji/koji/compose/updates/atomic/',
+ 'key': 'fedora-27'
+ },
'fedora/rawhide/x86_64/atomic-host': {
'directory': '/mnt/fedora_koji/koji/compose/atomic/rawhide/',
'key': 'fedora-28'
5 years, 4 months
FBR: update dist-git for namespaced lookaside
by Patrick Uiterwijk
Hi all,
So, a fedpkg update went out that enabled namespace support for
lookaside uploads.
Unfortunately, the current live version of dist-git does not support
that, so anyone that has the updated fedpkg will encounter errors.
Can I get +1s for updating dist-git to dist-git-1.4-3.el7 (which is a
very small patch to allow this and default to rpms/ for older
clients), and applying the following ansible patch?
Patrick
commit 58fcfbaca28ea1f370c53216916b2c053328bee7 (HEAD -> master)
Author: Patrick Uiterwijk <patrick(a)puiterwijk.org>
Date: Sat Oct 28 01:40:32 2017 +0200
Remove the namespace from dist-git.conf so namespaced lookaside
becomes possible
Signed-off-by: Patrick Uiterwijk <patrick(a)puiterwijk.org>
diff --git a/roles/distgit/files/dist-git.conf
b/roles/distgit/files/dist-git.conf
index d1cc8c100..8d45800b2 100644
--- a/roles/distgit/files/dist-git.conf
+++ b/roles/distgit/files/dist-git.conf
@@ -3,5 +3,5 @@ git_author_name = Fedora Release Engineering
git_author_email = rel-eng(a)lists.fedoraproject.org
cache_dir = /srv/cache
-gitroot_dir = /srv/git/repositories/rpms
+gitroot_dir = /srv/git/repositories
gitolite = True
5 years, 5 months
Need your collaboration to release fedpkg
by Chenxiong Qi
Hi all,
New release of fedpkg includes two requested changes, one is to send
namespace along with repo name to lookaside while new-sources[1] and
another one is to clone from https:// anonymous URL instead of git://
URL[2][3]. Both of these changes require update to configuration in
infra. I think we need collaborate together in order to release fedpkg
successfully.
Current status is, as we talked in fedora-admin IRC channel, clime is
working on patching dist-git, that will be reviewed, and then be
deployed and update configuration in infra ansible. Meanwhile, it is
still in Fedora 27 final freeze now (4 days remains though), therefor
it is not recommended to modify configuration to allow build from
git+https:// or https://.
According to our talk in IRC, it looks all these should be done
eventually after the final freeze. So, how about let us make a plan
for the release? My proposal is
- Revert to work with current lookaside upload.cgi script and clone
from git:// so that packagers can still build package from an
anonymous clone.
- Finish review and deploy patched dist-git
- Update necessary configuration in infra
- Enable what reverted in the first step.
As not all packagers will upgrade fedpkg at once, the configuration
should be compatible with older version of fedpkg, that is how it
works currently.
BTW, I'm not much clear about which URL prefix is allow to build
package in your plan, https:// or git+http://, or both? FYI,
git+https:// is allowed previously, e.g.
https://koji.fedoraproject.org/koji/taskinfo?taskID=19122540.
@clime, we can test patched dist-git by using fedpkg-1.30-1.
That's it. Any thought? Please correct me if anything is not correct or missing.
Relative links:
[1] https://pagure.io/fedpkg/issue/130
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1188634
[3] https://pagure.io/fedpkg/pull-request/120
[4] Support namespaced module name in lookaside upload script -
https://pagure.io/fedora-infrastructure/issue/6472
[5] Please enable allow to build from git+https:// -
https://pagure.io/fedora-infrastructure/issue/6468
Thank you all!
--
Regards,
Chenxiong Qi
5 years, 5 months
[Release] elections: 2.7
by Pierre-Yves Chibon
Good Morning Everyone,
I just cut a new release of fedora-elections: 2.7
Here is its changelog:
* Tue Oct 17 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.7-1
- Update to 2.7
- Fix spelling error (VoidWhisperer)
- Fix spelling and grammar errors (Justin W. Flory)
- Add a Vagrant-based development environment (Ryan Lerch)
- Specify rel="noopener noreferrer" to link including target='_blank'
- Port election to fedora-bootstrap (Ryan Lerch)
- Improve the README (Justin W. Flory)
- Project wide flake8 fixes
This is currently happily running in stg.
Happy voting!
Pierre
5 years, 5 months
