bastion03 outage/issue tonight
by Kevin Fenzi
At around 05:20 UTC there were vpn issues. bastion03 (the current vpn
hub) was only sporadically reachable. It wasn't clear if this was a
network issue, or something with the instance. I was able to login, but
then it would just not respond for minutes at a time, then recover.
I got in and upped it's cpus (it had only 1, I changed to 4) and
rebooted it and everything came back up and was working again at around
5:40 UTC.
I couldn't find much in the logs, but more eyes on it welcome.
Hopefully it was just a network issue (although I could get to
bastion02 fine), or a lack of cpu power.
kevin
12 years, 7 months
Plan for tomorrow's Fedora Infrastructure meeting (2011-09-08)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow
2011-09-08 at 1900 UTC in #fedora-meeting on the freenode network.
Suggested topics (suggested by whom):
* New folks introductions and Apprentice tasks.
* Upcoming new machine plans.
* Upcoming Tasks/Items (nirik)
2011-09-13 - 27: Beta change freeze
2011-09-09 Remove inactive fi-apprentice people.
2011-09-27: Fedora 16 Beta
2011-10-01 mail fi-apprentice folks.
2011-10-09 Remove inactive fi-apprentice people.
2011-10-18 - 2011-11-01: Final change freeze
2011-11-01: Fedora 16 release.
* Meeting tagged tickets:
https://fedorahosted.org/fedora-infrastructure/report/10
NOTE: I have cleaned out the ones that have been sitting around with
this tag. Anytime anyone would like to discuss a ticket, just add the
meeting keyword and we will get to it in this section.
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
12 years, 7 months
bastion changes
by Kevin Fenzi
Just a heads up about bastion changes with today's outage:
bastion03 is currently the primary vpn hub as well as the default when
you go to 'bastion.fedoraproject.org'. This used to be bastion02 before
today, so you will note that ssh host key fingerprints have changed
since this cutover.
bastion01 has been retired.
bastion02 will be retired in favor of bastion04 sometime in the next
few days.
kevin
12 years, 7 months
AUTO: Shannon Mcleod is out of the office (returning 09/08/2011)
by Shannon Mcleod
I am out of the office until 09/08/2011.
I am attending to personal business today and will be back in the office on
Thursday. Tim Blow is my backup.
Thanks,
Shannon McLeod
Unix System Administrator
Dubuque GDF
Note: This is an automated response to your message "infrastructure
Digest, Vol 64, Issue 5" sent on 9/7/11 6:00:23.
This is the only notification you will receive while this person is away.
12 years, 7 months
New python-fedora and you
by Toshio Kuratomi
I've just updated python-fedora on the app servers to 0.3.25. This update
has quite a few changes to the server helpers. For people watching for end
user issues, if someone reports problems with logging in and out of the
turbogears web apps on admin.fedoraproject.org or having their csrf token
cause problems it is possible that the python-fedora update is to blame.
Please let me know if you spot something like that and I'll try to
troubleshoot. (abadger1999 on irc).
For web application developers there have been a few deprecations and
additions.
* The fedora.tg.tg1utils and fedora.tg.tg2utils modules have been
deprecated. tg1 and tg2 have their own hierarchy now: fedora.tg.utils
(for TG1) and fedora.tg2.utils (for tg2).
* The TG2 auth middleware has been reworked a bit. It should no longer log
you out if you don't have a CSRF token. You should be able to regain your
logged in status simply by clicking on a link. Links should have the CSRF
token embedded in them in these instances.
* Additionally, the TG2 fas auth middleware has had its metadata updated so
that it is compatible with the default TG2 auth provider. This should
make it possible to write code that is compatible with both out-of-the-box
TG2 auth and the faswho auth middleware.
* Provisions for testing web applications with the faswho auth provider have
been made and documented. You should now be able to set faswho to use tes
fas servers for authentication. Details of setting this up are in the
updated documentation.
https://fedorahosted.org/releases/p/y/python-fedora/doc/faswho.html#authe...
* One last, untested feature is that the CSRF middleware that faswho uses to
protect against CSRF attacks has been made independent of faswho. You
should be able to combine it with other repoze.who auth providers (like
the TG2 default auth provider) to have CSRF protection in your
application. If you are working on an app that should be able to auth
against both fas and some other repoze.who auth source, please feel free
to test this and report any bugs to me. This is a desirable feature and
I want to make it work.
https://fedorahosted.org/releases/p/y/python-fedora/doc/faswho.html#using...
* Last but not least, just as we have genshi templates for TG1 for CSRF
enabled login forms and buttons we now have mako templates for TG2 that do
the same. With all the other changes in this release, it shouldn't be
hard to make a TG2 version of the genshi templates if those are needed.
https://fedorahosted.org/releases/p/y/python-fedora/doc/faswho.html#templ...
-Toshio
12 years, 7 months
Meeting Agenda Item: Introduction batnomuun
by Nomuun.B
Hi all,
My IRC handle: batnomuun
I new user fedora. I study IT university in Mongolia. I know python, sql
little lol. Hopeful, I will learn lot of things this project. It's very
important to my future job career.
12 years, 7 months
Ask Fedora SOP complete
by Rahul Sundaram
Hi
All settings, customizations are now fully documented at
https://fedoraproject.org/wiki/Ask_Fedora_SOP
Next step would be to use Puppet to automate all of this and we are good
to go although I am going to continue to update to the latest versions
from upstream for a while since I have a bunch of feature requests that
upstream has committed to implementing or already been implemented in
the git head. I haven't yet tested with memcached but I expect the
production launch would need this. When I did test it earlier, it
seemed buggy although it might have been just my misconfiguration. I
will test again soon. I hope to do the initial production launch before
Fedora 16 release.
http://fedoraproject.org/wiki/Releases/16/Schedule
Rahul
12 years, 7 months
serverbeach maint window: 2011-09-12/13
by Kevin Fenzi
From an email from serverbeach:
> 70103::serverbeach4, 70104::serverbeach5
>
> Please be advised that on September 12th starting at 22:00CT
> and ending on September 13 at 05:00CT, we will be continuing our
> planned ServerBeach Network Upgrades in the SAT Data Center that will
> provide you with a more robust and scalable network and enable us to
> better server your needs using our new Juniper Routing equipment.
>
> This maintenance will last approximately 7 hours, during
> which your server will experience up to 5 minutes of network downtime
> as your gateway is moved to the new Juniper routing equipment. Once
> this is done, we will be configuring the newer routers and you will
> see 6 brief periods of latency/packet loss as we redirect traffic to
> the newer systems. This maintenance will ensure that the networking
> systems are standardized and will allow us to use more supported
> commands for configuring and investigating issues at the networking
> level.
Serverbeach04 and 05 are hosted01 and 02.
So, just a head up that we may see some short network outages in that
window.
kevin
12 years, 7 months
Plan for tomorrow's Fedora Infrastructure meeting (2011-09-01)
by Kevin Fenzi
The infrastructure team will be having it's weekly meeting tomorrow
2011-09-01 at 1900 UTC in #fedora-meeting on the freenode network.
Suggested topics (suggested by whom):
* New folks introductions and Apprentice tasks.
* Upcoming new machine plans.
* Upcoming Tasks/Items (nirik)
2011-08-31: send out outage announcement for next week
2011-09-01 infra meeting
2011-09-01 mail fi-apprentice folks.
2011-09-06: Outage to migrate from db02 to db01 and bastion02 ->
bastion03 2011-08-31 send infra meeting agenda
2011-09-13 - 27: Beta change freeze
2011-09-09 Remove inactive fi-apprentice people.
2011-09-27: Fedora 16 Beta
2011-10-01 mail fi-apprentice folks.
2011-10-09 Remove inactive fi-apprentice people.
2011-10-18 - 2011-11-01: Final change freeze
2011-11-01: Fedora 16 release.
* Meeting tagged tickets:
https://fedorahosted.org/fedora-infrastructure/report/10
NOTE: I have cleaned out the ones that have been sitting around with
this tag. Anytime anyone would like to discuss a ticket, just add the
meeting keyword and we will get to it in this section.
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
12 years, 7 months
