January 2018 - infrastructure - Fedora Mailing-Lists

by Pierre-Yves Chibon

Good Morning Everyone, After more than 2 years (!) without releases, I just cut a new release of nuancier: 0.11.0 Here is its changelog: * Wed Jan 10 2018 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.11.0-1 - Update to 0.11.0 - Change the label of the fiels from `Motif` to `Cause for rejection / Comment` - Encode the image title to UTF-8 when sending notifications - Make the CSRF token timeout configurable (Jeremy Cline) - Add a Vagrant dev environment (Jeremy Cline) - Adjust import for newer recommended flask version - Port nuancier to python3 while remaining compatible with python2 - Add an submission_date_end field to the Election It's currently happily running in stg. I would like to push it to prod but there is an election in progress and the update will likely require something like a 5 minutes outage or so. The addition of the submission_date_end field allowing some time between the end of the submissions and the start of the voting period is quite interesting as it lead to some issues during the last election. What do you think? Happy photographing! Pierre

6 years, 3 months

1
1
0 / 0

integrate dist-git and bugzilla more tightly

by Dusty Mabe

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I go to a dist-git repo and find a bug when browsing the source code. I can open a PR to fix it, but what if I don't know how to fix it? I open an issue, right? Except, there's no issue tracker for dist-git pagure repos. That's what bugzilla is for. Now I need to go to bugzilla, find the component, fill out a bug, yada yada. I understand the need for bugzilla and that it's not going away anytime soon, but could we possibly integrate dist-git pagure issue tracking and bugzilla in a way that makes the whole process more seamless for this workflow. We could even use the bugzilla API and display things differently in pagure if we wanted. These are just suggestions. I feel like this can be improved. Dusty -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlpVWZoACgkQMwLb1zlS 5nFejxAAl9SCy5mshEsPGk/qK9rDQLYMPP094r8rJt9vBYvxA+6jvR+3PcnRoe0M +CtGndYHS28RJjZTzxL9dHTDX4pzZwOZUY1IDTIyKEZHrh9NuEDgAUYVobzeGFTP 3b5kDqx/PBD8K6oGlJ6FMZ7TMqYcJsU4cHZ0Qx76R1LlFvMIU1eXX7FJysdHbVKd J/+t9OotvmZJml7RIG4cYcLyjJG7WTqSRAZNByKbK9mrXQTVAhVX5sauWsqeTotQ sbOO+vDfccrzQwPCjZR8iqSi75wHcKsI+VAByfZ4iVLOubNdou8QmhAUcHJuM0kA YdzknBXI0Yh2aoqsFFHAmwfks0fjlG7OvNnOvYcFp9XhL02s0bMr8sblTSdYBjnZ iwKbTzGjzlB0F3ZA5YiWSrUA5nigZCnycZ0ShD4FCdmsYcT9Iw3cgGBiEniYaSOk WIs8Lp0FQDvixY3D8maw/ZJ7KwZSZ+uuIpKnnHrW3GHZtrGxajNXQY7RIIw9DZt0 PXwPgfQYfINfOB8NuqMg5dZgzIeIusT/nN/xrlo8pL2QPMl79S6ZG35cFjQAmgck x6M994d1nke10c4K3oZQtsN3XgJvZ8cV9iPJZSGhekvBaD+e6ZnIksilXx52FBdN 7imp0i8UtI0+6/JRS8qx3zc1llQU4qAdgZTOIwz3C81fe2u1594= =xzlu -----END PGP SIGNATURE-----

6 years, 3 months

4
4
0 / 0

Meeting invite for later today

by Stephen John Smoogen

The infrastructure team will be having its weekly meeting tomorrow, HERE, 2018-01-11 at 18:00 UTC in #fedora-meeting on the freenode network. Our agenda is stored in the gobby-0.5 server on infinote.fedoraproject.org = 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 (2018-01-11) #meetingname infrastructure #topic aloha #chair smooge relrod nirik dgilmore threebean pingou puiterwijk pbrobinson maxamillion = Let new people say hello = #topic New folks introductions #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves = 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 = 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 Ticket cleanup #info none this week. #topic Upgrading/Migrating Jenkins #info: Working with Pagure-CI triggers #info A Pagure SCM Plugin for Jenkins #topic enabling default Pagure fedmsg hooks on Fedora DistGit - clime, pingou #link: https://pagure.io/fedora-infrastructure/issue/6612 #topic Apprentice program feedback and changes - kevin = 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 setup 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: #info none this week = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

6 years, 3 months

1
0
0 / 0

Meeting Agenda Item: Introduction Graham Williamson

by graham＠williamsonsinc.id.au

Hey everyone, Here’s my introduction, or more accurately reintroduction email to the infrastructure team. I dropped back into the feadora-admin channel after the weekly meeting last week. My IRC handle is willo and I was involved a couple of years ago as an apprentice for not quite a year. Since then I’ve moved to the beach not far from Sydney. Presently, I’m working remote for a cyber security company. Day to day, I’m cutting python some code, building things in AWS, working towards getting some CI into our pipeline and performing some integration testing. Since I was contributing last time, I've continued working with ansible, python, KVM, virtualisation, integrating HA into various services and more recently exploring containerisation with Docker. I’ve also been doing datacenter migrations, configuring more Cisco network kit that I can to remember, both in the datacenter DC and also CPE. This time around, I’d like to maybe focus a bit more on the app development side, but also would like to keep my feet wet with some sysadmin activities. Catch you all on IRC. Cheers, Willo

6 years, 3 months

1
0
0 / 0

[Release] mdapi: 2.10.3

by Pierre-Yves Chibon

Good Morning Everyone, I just cut a new release of mdapi: 2.10.3 Here is its changelog: * Wed Jan 10 2018 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 2.10.3-1 - Update to 2.10.3 - Always initialize the output variable - Fix getting package by their source name It's currently running fine in stg and tests there are passing. If no more issues are reported with it, I will push to it prod :) Happy querying! Pierre

6 years, 3 months

1
0
0 / 0

Let's flip the switch on January 15th: gating in Fedora

by 'Dominik Perpeet'

Dear Fedora Infra, it's time to close the CI feedback loop! We have been working on adding CI to Fedora for a little while now but this has not really had avisibleeffect since there are no consequences whentests pass or fail. In order to change this, we plan to enable gating in bodhi. Originally this was meant to happen at flock already, but postponed until now due to various issues we considered blockers - those have been resolved. The change is fairly minor [3] and easy to undo if things do not work the way we expect them. Since DevConf is at the end of the month and we know people will be traveling there (and some of the infra team will travel there the week before), we propose Monday January 15th as target to enable gating in bodhi. This gives us one week before travels start to get it working or turn it back off if necessary. The tests run by the Atomic CI pipeline are controlled directly by the packager: * Files in dist-git define which tests are run What do you think? Here is a small reminder of how the systems works: * packager commit in dist-git - the Atomic CI pipeline is triggered and run tests * packager builds in koji * packager creates an update in bodhi - Taskotron is triggered and run tests on the build(s) and the update * All test results go to resultsdb * Bodhi queries greenwave * Greenwave queries resultsdb * Greenwave queries waiverdb * based on the test results found in resultsdb and the waivers in waiverdb, greenwave makes a decision about allowing the update to go through the gate or not * Based on greenwave's decision, bodhi allows (or not) the update to be included in the push to updates-testing or updates Next steps: * Packages will be tested in a non-Atomic context. * Broadening to make this available to all packagers, not just ones in Atomic. * RATS [2] will enable retriggering. * Further integration with Pagure and other Fedora services. It is up to us (the community) to define the policy in greenwave[1] which tests must pass to allow the update to go through the gate. Happy to answer any questions or concerns you may have. Dominik IRC: #fedora-ci on freenode https://pagure.io/fedora-ci/AtomicCi/ [1] https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/open... [2] https://pagure.io/rats [3] `` diff --git a/ roles/bodhi2/base/templates/production.ini.j2 b/ roles/bodhi2/base/templates/production.ini.j2 index fc304dc56..ec3b24ef7 100644 --- a/roles/bodhi2/base/templates/production.ini.j2 +++ b/roles/bodhi2/base/templates/production.ini.j2 @@ -298,7 +298,7 @@ krb_keytab = /etc/krb5.bodhi_bodhi{{ env_suffix }}.fedoraproject.org.keytab # Set this to True to enable gating based on policies enforced by Greenwave. If you set this to True, # be sure to add a cron job to run the bodhi-check-policies CLI periodically. -test_gating.required = False +test_gating.required = True # If this is set to a URL, a "More information about test gating" link will appear on update pages for users # to click and learn more. ``

6 years, 3 months

4
5
0 / 0

Meeting Agenda Item: Introduction Andres Torres

by Andres Ernesto

Hi * I´m a Linux SysAdmin, I´ve work with Fedora, CentOS, RedHat, Ubuntu also Solaris 10 and 11, have been working as a Middleware Engineer Administrator for the last 4 years, working with Oracle Middleware Suite that includes Weblogic, SOA, Service BUS, and BI. Also I have some experience coding with C, C++, Java (just a little bit), ROR, some perl, some python, bash and SQL. I have worked developing backend almost for 6 years, I know a little about frontend but not too much. Recently I have been working and learning about Docker and Ansible, nothing on production just to my own learning. I have also worked as SysAdmin over applications running on AWS and DigitalOcean. I'm interested on cloud, virtualization and DevOps. So that´s pretty much what I know and what I want to learn, I hope to be helpful to this community. IRC aetorresd *Ing. Informatico Andrés Ernesto Torres DuránCel. +506 6051-5949* *IRC aetorresd* *Skype. aetorresd* Linux user *#467559* <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_camp...> Libre de virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_camp...> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

6 years, 3 months

1
0
0 / 0

Can't save changes of settings in mailing list because of 'Maximum message size' error

by Tiansworld

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

6 years, 3 months

2
1
0 / 0

[release] - fedora-packages 4.0.0

by Clement Verna

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.rs... Clément

6 years, 3 months

2
1
0 / 0

[Fedocal] Reminder meeting : Bodhi stakeholder's meeting

by bowlofeggs＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Bodhi stakeholder's meeting on 2018-01-02 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Source: https://apps.fedoraproject.org/calendar/meeting/4671/

6 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure January 2018