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
11 months, 1 week
Fedora 26 Alpha Freeze now in effect
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 26
Alpha release. This is a pre-release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 26 Alpha 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/freezelist -i inventory
Any hosts listed as freezes is frozen until 2017-03-21 (or later if
Alpha 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
6 years, 5 months
[PATCH] add compose-utils to bodhi-backend<foo>
by dennis@ausil.us
From: Dennis Gilmore <ausil(a)fedoraproject.org>
in order to stage the release we need top have compose-utils installed
we use the compose-partial-copy script to do teh syncing.The box of
choice for staging is bodhi-backend do to the readily available sigul
setup so we can sign the CHECKSUM files.
https://pagure.io/releng/blob/master/f/scripts/stage-release.sh is the
script used to stage the release.
Signed-off-by: Dennis Gilmore <ausil(a)fedoraproject.org>
---
roles/bodhi2/backend/tasks/main.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/roles/bodhi2/backend/tasks/main.yml b/roles/bodhi2/backend/tasks/main.yml
index 4d1d93b..b09ee17 100644
--- a/roles/bodhi2/backend/tasks/main.yml
+++ b/roles/bodhi2/backend/tasks/main.yml
@@ -25,6 +25,7 @@
- python-alembic
- python-scandir
- python2-productmd
+ - compose-utils
tags:
- packages
- bodhi
--
1.8.3.1
6 years, 5 months
Freeze Break Request: add user to bugzilla fas override
by Kevin Fenzi
Greeings.
There's a use that wants to use their @fedoraproject.org alias
in bugzilla so we need to add an exception for them.
+1s?
kevin
--
diff --git a/roles/pkgdb2/files/fas2.py b/roles/pkgdb2/files/fas2.py
index 3cd2c4e..c048af8 100644
--- a/roles/pkgdb2/files/fas2.py
+++ b/roles/pkgdb2/files/fas2.py
@@ -265,6 +265,8 @@ class AccountSystem(BaseClient):
163460: 'besser82(a)fedoraproject.org',
# Amit Shah: amit(a)amitshah.net
115389: 'amitshah(a)fedoraproject.org',
+ # Mark Wielard: fedora(a)wildebeest.org
+ 102697: 'mjw(a)fedoraproject.org',
}
# A few people have an email account that is used in owners.list but
# have setup a bugzilla account for their primary account system email
6 years, 5 months
[FBR] Improve permissions for certs that enable container image sync
on compose-x86-01
by Adam Miller
Hello all,
I'd like to make the permissions for the container image sync
certs to be more restrictive.
diff --git a/roles/push-docker/tasks/main.yml b/roles/push-docker/tasks/main.yml
index 9baad7f..ed70253 100644
--- a/roles/push-docker/tasks/main.yml
+++ b/roles/push-docker/tasks/main.yml
@@ -13,11 +13,15 @@
copy:
src: "{{private}}/files/koji/{{docker_cert_name}}.cert.pem"
dest: "{{docker_cert_dir}}/client.cert"
+ owner: root
+ mode: 0600
- name: install docker client key for registry
copy:
src: "{{private}}/files/koji/{{docker_cert_name}}.key.pem"
dest: "{{docker_cert_dir}}/client.key"
+ owner: root
+ mode: 0600
- name: start and enable docker
service: name=docker state=started enabled=yes
Thank you,
-AdamM
6 years, 5 months
Plan for tomorrow's Fedora Infrastructure meeting - 2017-03-30
by Patrick Uiterwijk
The infrastructure team will be having it's weekly meeting tomorrow,
2017-03-30 at 18:00 UTC in #fedora-meeting 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.
Patrick
--
This shared document is for the next fedora infrastructure meeting.
= 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 (2017-03-30)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 lmacken dgilmore threebean
pingou puiterwijk pbrobinson
= Let new people say hello =
#topic New folks introductions
= 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 Fedora 26 Alpha freeze is on now! - everyone
#info Bodhi 2.5.0 beta deployed to staging, release notes available at
https://bodhi.stg.fedoraproject.org/docs/release_notes.html#id1 -
bowlofeggs
#info Fedora 26 alpha testing in full swing - kevin
#info kojipkgs01/02 updated and rebooted, speed seems better - kevin
#info space added to openqa/openqa.stg nfs volumes - kevin
#info
= 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
= Apprentice office hours =
#topic Apprentice Open office hours
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 gsetup 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.)
#topic Learn about:
= Meeting end stuff =
#topic Open Floor
#endmeeting
6 years, 6 months
[release] pagure: 2.14.2
by Pierre-Yves Chibon
Good Morning Everyone,
I just cut a new release of pagure: 2.14.2.
Here is the changelog
* Wed Mar 29 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.14.2-1
- Update to 2.14.2
- Fix a bug in the logic around diff branches in repos
This should fix the issue I encountered when pushing 2.14.1 to prod this morning.
What would you think about pushing 2.14.2 to prod?
Happy hacking,
Pierre
6 years, 6 months
[FBR] Update pagure.io to 2.14.1
by Pierre-Yves Chibon
Good Morning Everyone,
I would like to do two things:
- Update pagure in prod to 2.14.1
- Change the PAGURE_AUTH configuration key from 'fas' to 'openid' since legal
just cleared the requirement for the FPCA on pagure.io
https://lists.fedoraproject.org/archives/list/legal%40lists.fedoraproject...
For 2.14.1, while not released, the changelog is going to be:
- Fix typo for walking the repo when creating a diff of a PR
- Have the web-hook use the signed content and have a content-type header
- Fix running the tests on jenkins via a couple of fixes to pagure-admin and
skipping a couple of tests on jenkins due to the current pygit2/libgit2
situation in epel7
Thoughts on these?
Thanks,
Pierre
6 years, 6 months
[release] pagure: 2.14.1
by Pierre-Yves Chibon
Good Morning Everyone,
I just cut a new release of pagure: 2.14.1
Here is the corresponding changelog:
* Wed Mar 29 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.14.1-1
- Update to 2.14.1
- Fix typo for walking the repo when creating a diff of a PR
- Have the web-hook use the signed content and have a content-type header
- Fix running the tests on jenkins via a couple of fixes to pagure-admin and
skipping a couple of tests on jenkins due to the current pygit2/libgit2
situation in epel7
This is currently happily running in stg (still missing one +1 to push it to
prod).
Happy hacking!
Pierre
6 years, 6 months
Freeze break: update/reboot kojipkgs01/02
by Kevin Fenzi
Greetings.
openqa is seeing some very slow downloads from our kojipkgs01/02
machines. I cannot see anything obviously wrong with them, but as a
first step I'd like to update them (which would move them from a 4.9.x
to a 4.10.x kernel) to see if it's some odd networking stack thing thats
already been fixed.
The process would be:
* Update 01/reboot.
* Run playbook to make sure all was set right.
* Wait a few hours and make sure 01 is processing ok.
* Do the same to 02.
This shouldn't result in any downtime (the two are load balanced over
haproxy now) and if 01 doesn't process correctly after updating we can
limp along on 02 until after freeze.
+1s?
kevin
6 years, 6 months