[patch] Add oldschool mapping for LXQt SIG badge to FAS group
by Justin W. Flory
Hi all,
Attached is a patch to the ansible repo to add a mapping for the LXQt
SIG FAS group to their badge. The purpose of doing this is that it
automatically awards the badge to all current members of the SIG when
the cronjob runs.
If someone could review this and merge it in, it would be appreciated.
:) Thanks!
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
6 years, 8 months
Metrics for Mailman & HyperKitty
by Aurelien Bompard
Hey folks!
Unless I'm mistaken, we currently don't have many useful technical metrics
about Mailman and HyperKitty. I've started writing a simple script that
would collect those and output something we can eventually graph. It
currently uses the "key: value" format that I've seen a lot of monitoring
tools use, but I can adapt that to whatever we need.
I'm currently getting the following values :
- mailinglist count in HyperKitty
- email count in HyperKitty
- email senders count in HyperKitty
- user count in HyperKitty
- async task queue size
- number of async tasks run per minute
- async tasks average exec time
- size of the archiving queues in mailman and hyperkitty (should be zero
most of the time)
- Mailman's shunt queue (for messages it failed to handle, usually encoding
problems)
Do you think there would be other values that we would need? My aim is to
detect issues with the server usage (say, a spam attack) as well as
anticipate growth. Another useful metric would be the number of emails sent
by the system, but I guess we already have a Postfix plugin somewhere, so
I'm trying to stay mailman & hyperkitty-specific here.
Currently the plugin takes between 5 and 10 seconds to collect the data. I
don't know how precise we want our metrics but a run every five minutes
seems sufficient to me. It also depends on how we can set that in collectd,
which I don't know (yet!).
Thanks!
Aurélien
6 years, 8 months
[release] pdc-updater: 0.6.0
by Ralph Bean
A new pdc-updater release!
There are a few bugfixes related to the MBS, but crucially there is a new
handler for propagating retirement: When a `dead.package` file gets committed,
the code here (on pdc-backend0*) will update the EOL of that branch in PDC,
indicating retirement.
0.6.0
-----
Pull Requests
- (@ralphbean) #57, srpm_nevra must not be set when arch is src.
https://github.com/fedora-infra/pdc-updater/pull/57
- (@ralphbean) #62, Force creation of parent with type during initialization.
https://github.com/fedora-infra/pdc-updater/pull/62
- (@ralphbean) #60, Populate the dist_git_branch value...
https://github.com/fedora-infra/pdc-updater/pull/60
- (@ralphbean) #61, Also construct container tags from stable updates tags.
https://github.com/fedora-infra/pdc-updater/pull/61
- (@mprahl) #63, Add a handler so that PDC branches are EOL'd when the branch is retired
https://github.com/fedora-infra/pdc-updater/pull/63
- (@mprahl) #64, Add some missing doc strings to RetireComponentHandler
https://github.com/fedora-infra/pdc-updater/pull/64
- (@ralphbean) #66, Some changes to the retirement handler...
https://github.com/fedora-infra/pdc-updater/pull/66
Commits
- 6118478b5 srpm_nevra must not be set when arch is src.
https://github.com/fedora-infra/pdc-updater/commit/6118478b5
- 600b6175e Populate the dist_git_branch value...
https://github.com/fedora-infra/pdc-updater/commit/600b6175e
- 17edf56ad Also construct container tags from stable updates tags.
https://github.com/fedora-infra/pdc-updater/commit/17edf56ad
- 7a022d494 Force creation of parent with type during initialization.
https://github.com/fedora-infra/pdc-updater/commit/7a022d494
- b7341977a Add a handler so that PDC branches are EOL'd when the branch is retired
https://github.com/fedora-infra/pdc-updater/commit/b7341977a
- 31f7caf33 Break retirement out into its own staticmethod.
https://github.com/fedora-infra/pdc-updater/commit/31f7caf33
- e2eeec935 Write an init method.
https://github.com/fedora-infra/pdc-updater/commit/e2eeec935
- e132ab502 Add Docstrings to RetireComponentHandler
https://github.com/fedora-infra/pdc-updater/commit/e132ab502
- e2d52896c Add the audit function to the RetireComponentHandler handler
https://github.com/fedora-infra/pdc-updater/commit/e2d52896c
- bcb112faa Add some missing doc strings to RetireComponentHandler
https://github.com/fedora-infra/pdc-updater/commit/bcb112faa
- 3a2cef32e Make these two work functions re-try-able.
https://github.com/fedora-infra/pdc-updater/commit/3a2cef32e
- fe8af401d Check pagure instead of cgit.
https://github.com/fedora-infra/pdc-updater/commit/fe8af401d
- e1b0542b4 Fix those mocks.
https://github.com/fedora-infra/pdc-updater/commit/e1b0542b4
6 years, 8 months
[release] fedmsg-0.19.1
by Jeremy Cline
Hey all,
Last night I tagged the 0.19.1 release of fedmsg to fix a few critical
issues found in 0.19.0. It's currently only built into the Fedora infra
repositories. It will be making its way out to Fedora and EPEL testing
repositories near you in the next day or two.
Change log: https://github.com/fedora-infra/fedmsg/releases/tag/0.19.1
--
Jeremy Cline
XMPP: jeremy(a)jcline.org
IRC: jcline
6 years, 8 months
Plans for Thursday 2017-08-10 Fedora Infrastructure Meeting
by Stephen John Smoogen
We will have our normal Thursday Fedora Infrastructure Meeting at 1800 UTC
on #fedora-meeting. The agenda currently looks as follows on the gobby
page. Please add or update as needed.
= Meeting start stuff =
#startmeeting Infrastructure (2017-08-10)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik abadger1999 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 PHX2 Colo Trip coming up, Dec 4th - 9th
#info FLOCK at Cape Cod Aug29->Sep01
#info Fedora F27 Rebuild (going on now)
#info Updated of all servers has been messy kevin/smooge/patrick/relrod
#info Bodhi 2.9.0 released. Deployment planned for Monday - bowlofeggs
= 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 Update cycles. Lessons learned?
#info the last couple of updates cycles have been hard
#info different reasons each time but how can we do better?
= 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: Nothing was put here this week
= Meeting end stuff =
#topic Open Floor
#endmeeting
--
Stephen J Smoogen.
6 years, 8 months
Duplicates in package owner alias cronjob?
by Ralph Bean
I'm confused about something. Can any postfix experts help debug?
On Friday I put a new package-owner-alias cronjob in place on bastion
(that Matt Prahl wrote). It generates the package owner list from
pagure over dist-git instead of generating it from pkgdb.
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=eb24...
Kevin saw that the hourly cronjob is spitting out some errors from the
postfix command.
However, when I inspect the file, I don't find any duplicates:
$ cat /etc/postfix/package-owner | awk ' { print $1 } ' | uniq -d
Anybody know what's wrong with that file/output?
-Ralph
6 years, 8 months
Aug status update for Fedora Infrastructure Apprentices
by Kevin Fenzi
You are getting this email because you are in the 'fi-apprentice' group
in the fedora account system (or are reading this on the infrastructure
list).
Feel free to reply just directly to me, or cc the infrastructure list
for everyone to see and comment on.
https://fedoraproject.org/wiki/Infrastructure_Apprentice
At the first of every month(or so), I am going to be sending out an
email like this one. I would like feedback on how things are going for
you. I'd like to ask for everyone to send me a quick reply with the
following data or anything related you can think of that might help us
make the apprentice program more useful.
0. Whats your fedora account system login?
1. Have you logged in and used your fi-apprentice membership to look at
our machines/setup in the last month? Do you plan to?
2. Has it helped you decide any area you wish to focus on or contribute
to more?
3. Have you looked at or been able to work on any of the fi-apprentice
'easyfix' tickets?
https://pagure.io/fedora-infrastructure/issues?status=Open&tags=easyfix
4. Do you still wish to be a member of the group? If not (for whatever
reason) could you provide any hints to help others down the road?
5. Is there any help or communication or ideas you have that would help
you do any of the above?
6. What do you find to be the hardest part of getting involved? Finding
things to work on? Getting attention from others to help you? Finding
tickets in your interest area?
7. Have you been able to make any weekly irc meetings? Do you find them
helpful or interesting? Do you have any suggestions for changing them?
8. Have you logged into our Gobby instance and read/seen/added to our
meeting agenda? https://fedoraproject.org/wiki/Gobby
9. What are the top 5 commands you run by number? You can get these with
something like:
history | awk '{print $2}' | sort | uniq -c | sort -nr | head -5
(or something more clever of your own devising)
Any other general feedback is also quite welcome, including improvements
to this email, the wiki page, etc. Note that we recently revamped the
getting started and other pages. Please do take a minute to re-read them
and let me know if they are more clear or need further adjustments.
Any folks I do not hear from in the next week will be removed from the
group. (Note that it's easy to be readded when you have time or whatever
and it's nothing at all personal, we just want to keep the group up
todate with active folks).
Thanks, and looking forward to your feedback!
kevin
6 years, 8 months
Meeting Agenda Item: Introduction Martin Smola
by Martin Smola
Hi all,
Let me introduce myself. My name is Martin Smola and I am coming from Czech Republic.
IRC: martincz
What skills you have to offer and which you would like to learn.
I know HTML, CSS, Bash, Linux advanced. I would like to learn more Linux to be professional, born shell and Perl, Python, OpenStack just for now but I am opened to everything what will be useful for my life.
In past I got Cisco CCNA1 and CCNA2. I made some migrations of WAR file with big MySQL database for Tomcat, which I put to my installed CentOS and deployed there. I made as well migration of Firebird database with my cleaned minimal installation of CentOS. I work with Cisco Switches L2 and L3. I installed Apache and put websites there. I can help myself or with my friend Google. I have root privileges to all our CentOS and Windows servers. I can manage group policy and AD as well. i work with Synology NAS as well.
I help end users with obviously Application problem. I learn RHCSA and I want to pass the exam soon and start learn RHCE. I hope someone of you will take me under his wings.
Regards,
Martin Smola
6 years, 8 months
[Release] pagure: 3.5
by Pierre-Yves Chibon
Good Morning Everyone,
I just cut a new pagure release: 3.5
Here is its changelog:
* Tue Aug 08 2017 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 3.5-1
- Update to 3.5
- Fix login when groups are managed outside
- Fix the ordering of the issues by priority using JS and its documentation
- Indicate the issue/PR status in the title of its link
- Correct typo in waiting page template: 'You task' -> 'Your task' (Hazel Smith)
- Fix redirect in search (Carl George)
- Fix removing users of a project
- Allow customizing the HTML title globally
- Drop the new line character and the '# end of body' message when loading the
config
- Scroll to the comment section on clicking reply. (shivani)
- only show issues on the My Issue page if the issue tracker is on for the
project (Vivek Anand)
- Update the refresh-gitolite action of pagure-admin for the new interface
(turns out this wasn't in fact merged in 3.4)
- Add a configuration key to make pagure case sensitive
- Add an USER_ACLS configuration key
- Document the different API token ACLs configuration keys
- Fix syncing groups from external account sources (Patrick Uiterwijk)
Most changes being related to dist-git, I upgrade stg.pagure.io as well as
production.
I have adjusted pkgs01.stg (which seems to be down for the moment) to benefit
from the new features so we can test them there before updating prod.
Happy hacking!
Pierre
6 years, 8 months
