Plan for tomorrow's Fedora Infrastructure meeting (2014-03-20)
by Ralph Bean
The infrastructure team will be having it's weekly meeting tomorrow,
2014-03-13 at 18:00 UTC in #fedora-meeting on the freenode network.
Suggested topics:
#topic New folks introductions and Apprentice tasks.
If any new folks want to give a quick one line bio or any apprentices
would like to ask general questions, they can do so in this part of the
meeting. Don't be shy!
#topic Applications status / discussion
Check in on status of our applications: pkgdb, fas, bodhi, koji,
community, voting, tagger, packager, dpsearch, etc.
If there's new releases, bugs we need to work around or things to note.
#topic Sysadmin status / discussion
Here we talk about sysadmin related happenings from the previous week,
or things that are upcoming.
#topic Upcoming Tasks/Items
https://apps.fedoraproject.org/calendar/list/infrastructure/
#topic Open Floor
Submit your agenda items, as tickets in the trac instance and send a
note replying to this thread.
More info here:
https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings
Thanks
ralph
10 years, 1 month
Re: [ansible] Try out this conditional restart stuff.
by Miroslav Suchý
On 03/14/2014 04:30 PM, Ralph Bean wrote:
> +- name: restart fedmsg-gateway
> + command: /usr/local/bin/conditional-restart.sh fedmsg-gateway fedmsg-gateway
Ralph,
I tried to run copr-backend playbook and this notified and therefore executed, but failed, because
NOTIFIED: [restart fedmsg-gateway] ********************************************
failed: [209.132.184.142] => {"cmd": ["/usr/local/bin/conditional-restart.sh", "fedmsg-gateway", "fedmsg-gateway"],
"failed": true, "item": "", "rc": 2}
msg: [Errno 2] No such file or directory
and:
yum whatprovides /usr/local/bin/conditional-restart.sh
No matches found
So where I can get that file please?
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
10 years, 1 month
Lookaside: Move away from md5
by Mathieu Bridon
We should move to something more secure than md5 for the uploaded sources.
This patch series implements the server-side part of this change, adding
support for sha512, but keeping support for md5 as a fallback for now.
We might want to drop the md5 fallback once we have migrated completely, that
is when fedpkg has been updated too.
The last patch is unrelated, but it's a fix for a problem I found while
testing this change.
https://fedorahosted.org/rel-eng/ticket/5846
10 years, 1 month
bug in fedora badges?
by Mohan Prakash
I use my fedora fas login for fedora-badges.
My irc-nickname is not the same as my fas name.
When I attended an IRC meeting, Fedora-badges awarded two badges for a
user with my IRC nickname which perhaps should be added to my account.
I checked the fedora user accounts and there is no user with the name
'mpduty' which is my IRC nickname.
Is this a bug?
regards
Mohan Prakash (mpduty)
10 years, 1 month
Re: bug in fedora badges?
by Mohan Prakash
Hi,
I wanted to have the same fas name, IRC nickname and mail ID.
So I had created another account mpduty, however that needed a
separate mail ID to be registered. So I later marked that inactive
(since it can't be deleted).
However the point is that I created the user 'mpduty' after 'mpduty'
got those two badges.
So its not that fedora badges application was picking up mpduty
because of two accounts.
There was actually no user called 'mpduty' when it assigned two badges
to 'mpduty'.
I think it picked up the nickname 'mpduty' from the logs or minutes
without the fas name. Perhaps it would be better for the badges
application if the minutes or logs used fas names along with the IRC
nick names for attendees.
regards
Mohan Prakash (mpduty)
10 years, 1 month
Plan for tomorrow's Fedora Infrastructure meeting (2014-03-13)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2014-03-13 at 18:00 UTC in #fedora-meeting on the freenode network.
(We are moving back one hour due to the daylight saving time changes.
Hope that works for everyone).
Suggested topics:
#topic New folks introductions and Apprentice tasks.
If any new folks want to give a quick one line bio or any apprentices
would like to ask general questions, they can do so in this part of the
meeting. Don't be shy!
#topic Applications status / discussion
Check in on status of our applications: pkgdb, fas, bodhi, koji,
community, voting, tagger, packager, dpsearch, etc.
If there's new releases, bugs we need to work around or things to note.
#topic Sysadmin status / discussion
Here we talk about sysadmin related happenings from the previous week,
or things that are upcoming.
#topic Upcoming Tasks/Items
https://apps.fedoraproject.org/calendar/list/infrastructure/
#topic Open Floor
Submit your agenda items, as tickets in the trac instance and send a
note replying to this thread.
More info here:
https://fedoraproject.org/wiki/Infrastructure/Meetings#Meetings
Thanks
kevin
10 years, 1 month
Fedora Cloud cleanup
by Miroslav Suchý
According to my searches this images are not used (I searched both ansible.git and puppet.git).
not used at all:
f17_qcow_id: ami-00000001
f16-64: ami-00000002
Can I remove it? Unless you stop me, I will remove it after one week.
used by inventory/host_vars/209.132.184.166 (jenkins-f18) and playbooks/fedora_temp_instance.yml
vars/global.yml:f18_qcow_id: ami-00000016
Can it be removed? Or migrated to more recent Fedora?
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
10 years, 1 month
mirror rsync idea
by Kevin Fenzi
Greetings.
With our recent woes about rsync hitting our storage kind of hard, I
had an idea of how we could make things better for at least our tier1
mirrors and anyone who is actually paying attention.
The only time our master mirrors change is when we push updates (once a
day) or when epel7beta/rawhide finish. When we have branched that adds
another set.
Right now, mirrors (or any people who are rsyncing content) just hits
the master mirrors N times a day and pulls any changes. Or if they are
very smart (like a few folks on the mirrors list), they grab the
fullfilelist and only sync if it's changed. Which still hits the full
tree when they do.
I think there's something we can do that might improve things:
rsync has a ability to make "BATCH MODE" updates. (see 'man rsync' and
the BATCH MODE section).
- enhance the cron job that syncs updates to generate a batch on each
push and place it on master mirrors.
- enhance the rawhide/epel7beta/branched crons to generate a batch file
for rawhide/epel7beta/branched.
- Mirrors that are otherwise caught up, can just use the batch file for
that day. If they are more than a day out of sync it won't help them,
but if they are in sync it will really help them a lot. They can
ignore all the metadata fetching and files that haven't changed and
just get the actual things that have.
- Interested parties can just run their sync to pull the days batch
file(s). If they don't exist, then no sync has happened yet and they
can do nothing. If they do, they can download the batch and run it.
Caveats:
- This won't help mirrors that do subsets of things unless they tweak
the batch files (ie, if they exclude debuginfo or something)
- This won't help anyone who doesn't opt in to using it.
- This won't help anyone who is more than a day out of date, they will
need to sync up normally first.
- This may result in a "thundering herd" of syncs after the batch files
appear. I suspect however it still may be a lot less load than people
doing full useless syncs.
Thoughts?
kevin
10 years, 1 month
March status update for Fedora Infrastructure Apprentices
by Kevin Fenzi
Greetings.
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://fedorahosted.org/fedora-infrastructure/report/14
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?
8. What is your favorite programming or scripting language? :)
Any other general feedback is also quite welcome, including
improvements to this email, the wiki page, etc.
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 to date with active folks).
Thanks, and looking forward to your feedback!
kevin
10 years, 1 month
