discussion on Fedora Council Engineering representative
by Matthew Miller
Spamming many lists to make sure this doesn't go unnoticed. (In case my
accidentally posting to both devel and devel-announce separately doesn't do
it.)
Please see the thread titled "Engineering Representiatve for the new Fedora
Council" on the devel list — this affects and should have the input of
everyone involved in the broad category of "building and shipping the
distro" efforts in Fedora. Thanks!
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
9 years, 5 months
bastion re-installs yesterday and today (2014-10-08)
by Kevin Fenzi
Greetings.
Yesterday I re-installed bastion02.fedoraproject.org.
Moving it to ansible and rhel7.
Today I would like to do bastion01. :)
I plan to start the process around 18UTC today.
* Switch openvpn to bastion02
* Shutdown postfix on bastion01
* Save postfix queue off
* Take down bastion01, saving disk
(At this point anyone ssh tunning via bastion01 will be disconnected)
* Fresh install/ansiblizing.
* Restore postfix queue
* Update sshfp and ssh_known_hosts for folks to verify against.
While I could copy the ssh host keys from the old instances, I am not
going to do that in this case. The host keys on those machines have
been copied forward through a number of re-installs and I think it's
time to have newly generated ones.
This of course means that everyone who has shell access will need to
remove the old ssh host key from their known_hosts and add and check
the new one. If you are using the: VerifyHostKeyDNS ssh option, ssh
will verify the host key against the sshfp dns record. If you aren't
you can check it against:
https://admin.fedoraproject.org/ssh_known_hosts
In the event the new bastion01 has issues, I will have the old disk and
can switch back to that instance if needed.
Thanks,
kevin
9 years, 5 months
Plan for tomorrow's Fedora Infrastructure meeting (2014-10-09)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow,
2014-10-09 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 nagios/alerts recap
Here we go over the last weeks alerts and see if we can find ways to
make it so they don't happen again.
#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
9 years, 5 months
Something is polluting lockbox01 /
by Stephen John Smoogen
So I feel bad.. I didn't see this til today and its been going on for a
while. Some script is putting a lot of file entries in / versus where-ever
it is supposed to do so. The entries will be <something>.retry
-rw-r--r--. 1 root root 36 Sep 16 04:28
fed-cloud09.cloud.fedoraproject.org.retry
-rw-r--r--. 1 root root 68 Jul 24 07:54 fedimg.retry
-rw-r--r--. 1 root root 106 Jun 17 04:29 fedoauth.retry
-rw-r--r--. 1 root root 16 Aug 19 04:09 fedocal.dev.fedoraproject.org.retry
-rw-r--r--. 1 root root 103 Jun 17 04:26 fedocal.retry
-rw-r--r--. 1 root root 37 Jul 27 05:53 gallery.retry
-rw-r--r--. 1 root root 43 Jun 17 04:11 github2fedmsg.retry
-rw-r--r--. 1 root root 28 Sep 16 04:23 hrf.cloud.fedoraproject.org.retry
-rw-r--r--. 1 root root 16 Aug 31 11:44 jenkins-cloud.retry
-rw-r--r--. 1 root root 36 Jul 2 14:05 kerneltest.retry
-rw-r--r--. 1 root root 50 Aug 16 07:14 keyserver.retry
-rw-r--r--. 1 root root 34 Jun 17 04:30 koji-hub.retry
-rw-r--r--. 1 root root 32 Aug 26 04:18
koschei.cloud.fedoraproject.org.retry
-rw-r--r--. 1 root root 34 Aug 19 04:07
lists-dev.cloud.fedoraproject.org.retry
-rw-r--r--. 1 root root 36 Sep 16 08:21 lockbox.retry
-rw-r--r--. 1 root root 29 Jul 23 04:04 logserver.retry
-rw-r--r--. 1 root root 16 Aug 19 04:08
logstash-dev.cloud.fedoraproject.org.retry
-rw-r--r--. 1 root root 66 Jul 1 04:11 mailman.retry
-rw-r--r--. 1 root root 41 Sep 3 10:39 mirrorlist.retry
-rw-r--r--. 1 root root 29 Jul 10 05:02 nagios_phx2.retry
-rw-r--r--. 1 root root 24 Sep 9 07:45 noc.retry
-rw-r--r--. 1 root root 84 Jul 18 07:02 notifs-backend.retry
-rw-r--r--. 1 root root 152 Jun 17 04:30 notifs-web.retry
-rw-r--r--. 1 root root 144 Jun 17 04:29 nuancier.retry
-rw-r--r--. 1 root root 106 Aug 2 09:57 packages.retry
-rw-r--r--. 1 root root 97 Jul 23 07:26 paste.retry
-rw-r--r--. 1 root root 97 Jun 17 04:30 pkgdb.retry
-rw-r--r--. 1 root root 68 Jun 17 04:26 postgresl-server.retry
-rw-r--r--. 1 root root 33 Aug 17 07:47 qadevel-stg.retry
-rw-r--r--. 1 root root 32 Jun 17 04:26 releng.retry
-rw-r--r--. 1 root root 37 Aug 7 11:00 resultsdb-dev.retry
-rw-r--r--. 1 root root 33 Sep 16 07:19 resultsdb-prod.retry
-rw-r--r--. 1 root root 37 Sep 4 05:01 resultsdb-stg.retry
-rw-r--r--. 1 root root 16 Aug 19 04:06
shogun-ca.cloud.fedoraproject.org.retry
-rw-r--r--. 1 root root 34 Jul 9 07:08 smtp-mm.retry
-rw-r--r--. 1 root root 76 Jul 18 06:57 summershum.retry
-rw-r--r--. 1 root root 72 Aug 7 09:48 sundries.retry
-rw-r--r--. 1 root root 100 Jun 17 04:41 tagger.retry
-rw-r--r--. 1 root root 160 Jul 23 05:30 taskotron-dev-clients.retry
-rw-r--r--. 1 root root 37 Jul 23 09:54 taskotron-dev.retry
-rw-r--r--. 1 root root 160 Jul 23 04:34 taskotron-prod-clients.retry
-rw-r--r--. 1 root root 33 Sep 16 07:27 taskotron-prod.retry
-rw-r--r--. 1 root root 40 Sep 12 05:21 taskotron-stg-clients.retry
-rw-r--r--. 1 root root 37 Jul 23 05:07 taskotron-stg.retry
-rw-r--r--. 1 root root 37 Jun 19 14:13 taskotron.retry
-rw-r--r--. 1 root root 34 Jul 1 07:20 unbound.retry
-rw-r--r--. 1 root root 66 Jun 17 04:27 value.retry
-rw-r--r--. 1 root root 37 Sep 16 13:19 virthost.retry
-rw-r--r--. 1 root root 30 Jul 24 04:40 wiki.retry
Anyone know what this is?
--
Stephen J Smoogen.
9 years, 5 months
[release] fedocal 0.11
by Pierre-Yves Chibon
Good morning everyone,
I have just released and push to staging fedocal version 0.11, here is the
changelog:
* Mon Oct 6 2014 Pierre-Yves Chibon <pingou(a)pingoured.fr> - 0.11-1
- Update to 0.11
- Fix CSS in the agenda view
- Update to jquery-ui 1.11.1
- Fix the CSS for the jquery-ui update to 1.11.1 - Thanks Johan Cwiklinski
- Drop the weekly navigation key on the list view
- Fix meeting overlap for full day meetings - Thanks Johan Cwiklinski
- Fix timespinners that the new jquery-ui seems to have broken
- Fix the home button (top right in calendar view) - Thanks Johan Cwiklinski
- Fix the message displayed in the meeting view when countdown reaches 0
- Thanks Johan Cwiklinski
- Fix deleting meetings from the list view (ticket #137)
Testing welcome as usual:
https://apps.stg.fedoraproject.org/calendar/
I hope to push this to prod tomorrow morning (which means that 0.10 will not see
prod).
Have a nice day,
Pierre
9 years, 5 months
October 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 beverage of all time? :)
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
9 years, 5 months
Meeting Agenda Item: Introduction Ahmed Thabet
by Ahmed Youssef
Hello,
My name is Ahmed, I'm from Egypt. I am an Electrical
Engineer/Programmer. I have been using fedora for many years and I'd
like to contribute back to such a wonderful project.
I've a good experience in programming with Python as main language.I'm
seeking a chance to improve my teamwork abilities and knowledge by
working in such a large project
Looking forward to work with you.
My IRC handle is xmonader
Regards,
Ahmed Thabet
9 years, 5 months