infrastructure December 2017

infrastructure@lists.fedoraproject.org

22 participants
27 discussions

About JS framework
by Pierre-Yves Chibon 14 Sep '22

14 Sep '22

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

15 19

Fedora 27 Beta Freeze now in effect
by Kevin Fenzi 04 Apr '18

04 Apr '18

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

1 2

[release] fedmsg_meta_fedora_infrastructure: 0.23.0
by Pierre-Yves Chibon 28 Jan '18

28 Jan '18

Good Morning Everyone, I just cut a new release of fedmsg-meta-fedora-infrastructure: 0.23.0. Here is its changelog: 0.23.0 ------ Pull Requests - (@ralphbean) #451 Target py3.6 https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/451 - (@pypingou) #453 Add support for the new pagure messages https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/453 - (@ralphbean) #452 WaiverDB processor. https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/452 - (@adamwill) #455 Substantial rewrite + extension of compose.* tests https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/455 - (@ralphbean) #456 An icon for waiverdb. https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/456 - (@adamwill) #457 Fix `nodoc` to exclude test class from topic list https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/457 - (@ralphbean) #450 A first pass at greenwave handling. https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/450 - (@adamwill) #459 Revise subtitles for compose.* messages https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/459 I'm working on updating the corresponding package. Thoughts on updating it in stg/prod? Thanks, Pierre

1 1

Can't save changes of settings in mailing list because of 'Maximum message size' error
by Tiansworld 02 Jan '18

02 Jan '18

Hello everyone, I am not sure this is the right list to ask about this, if you think it's out of topic, then just ignore it. Today I tried to modify the 'Message Acceptance' settings of 'trans-zh_cn.lists.fedoraproject.org' mailing list. However I couldn't save any changes due to continuous 'Maximum message size' related errors. It was left blank by default at first, but when I tried to save my changes, a line of red characters told me 'This field is required.' Then I input 100, and clicked 'Save changes' button, an error appeared on top of the page saying 'An error occured: Unknown attribute: max_message_size'. I tried to use 0 to disable the check, but still got the same error: 'An error occured: Unknown attribute: max_message_size'. The error persists no matter what number I input. Have any of you met this problem? Or is it a bug? -- Regards, Tiansworld Fedora Project Contributor

2 1

[release] - fedora-packages 4.0.0
by Clement Verna 02 Jan '18

02 Jan '18

Greetings, As an early Christmas present, a new release of fedora-packages is available. The changelog is available in here[0]. Thanks to Patrick, it is currently deployed in stg and prod. Happy Holidays. [0] - https://github.com/fedora-infra/fedora-packages/blob/develop/CHANGELOG.rst#… Clément

2 1

Fwd: Please fix your bugzilla.redhat.com account
by Stephen John Smoogen 22 Dec '17

22 Dec '17

Is the long thread of emails for people getting asked to deal with bugzilla related to any software updates that happened this week? ---------- Forwarded message ---------- From: Christian Dersch <lupinix.fedora(a)gmail.com> Date: 16 December 2017 at 14:08 Subject: Re: Please fix your bugzilla.redhat.com account To: accounts(a)fedoraproject.org Cc: kevin(a)fedoraproject.org, pingou(a)fedoraproject.org, ralph(a)fedoraproject.org, mprahl(a)fedoraproject.org Hi, what is the issue here? I use lupinix.fedora(a)gmail.com for both (changed mail ~2 months ago, but have been always in sync for FAS and bugzilla) and also receive the bugzilla mails for my packages. Greetings, Christian On 12/16/2017 08:03 PM, accounts(a)fedoraproject.org wrote: > Greetings. > > You are receiving this email because there's a problem with your > bugzilla.redhat.com account. > > If you recently changed the email address associated with your > Fedora account in the Fedora Account System, it is now out of sync > with your bugzilla.redhat.com account. This leads to problems > with Fedora packages you own or are CC'ed on bug reports for. > > Please take one of the following actions: > > a) login to your old bugzilla.redhat.com account and change the email > address to match your current email in the Fedora account system. > https://bugzilla.redhat.com login, click preferences, account > information and enter new email address. > > b) Create a new account in bugzilla.redhat.com to match your > email listed in your Fedora account system account. > https://bugzilla.redhat.com/ click 'new account' and enter email > address. > > c) Change your Fedora Account System email to match your existing > bugzilla.redhat.com account. > https://admin.fedoraproject.org/accounts login, click on 'my account', > then 'edit' and change your email address. > > If you have questions or concerns, please let us know. > > Your prompt attention in this matter is appreciated. > > The Fedora admins. -- Stephen J Smoogen.

4 5

[PATCH] - Add the final icons destination for fedora-packages
by Clement Verna 21 Dec '17

21 Dec '17

I have attached a patch that will make the icons available to fedora-packages. The current indexing is missing a parameter to specify the location of the icons. Thanks Clement

2 1

[PATCH] fedora-packages httpd configuration
by Clement Verna 21 Dec '17

21 Dec '17

I have attached a patch that remove some duplication in the httpd configuration for fedora-packages. Thanks Clement

2 1

[Release] pagure: 3.13.2
by Pierre-Yves Chibon 21 Dec '17

21 Dec '17

Good Morning Everyone, I just cut a new release of pagure: 3.13.2 Here is its changelog: * Thu Dec 21 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 3.13.2-1 - Update to 3.13.2 - Fix ordering issues by author using an alias so the User doesn't collide Since the fix was already hotfixed in prod, I push it to stg and prod ensuring we have a clean prod for the coming days. Happy hacking and packaging! Pierre

1 0

Copr storage
by Miroslav Suchý 21 Dec '17

21 Dec '17

We are running out of disk space in Copr. It will probably run out during Christmas so I am going to act before the weekend. Right now we have 4GB volume for production and 4GB for dev machine (just because we can, but we never used that). My plan is to shrink dev volume to 150 GB. And allocate 8 GB for production. I plan to do that tomorrow. Mirek

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure December 2017