infrastructure April 2011

infrastructure@lists.fedoraproject.org

28 participants
39 discussions

ticket#2673 - nitrate deployment
by James Laska 10 Aug '11

10 Aug '11

Greetings, I am in search of sponsorship for hosting space to deploy a test instance of nitrate [1]. Some of you may recall several years back when we deployed an instance of Testopia. That exploration was cut short when we discovered license incompatibilities between testopia and Fedora. At that time, a small group of Red Hat associates began creating a new Django-based test management system to remove the components that had conflicting licenses. That new system became nitrate [1]. The Fedora QA team would like to experiment/explore this newer Django-based test management system. At the very least, I believe we'll need a publicly accessible server where we can host the nitrate instance and a mysql database for it. I filed ticket#2673 (https://fedorahosted.org/fedora-infrastructure/ticket/2673) to track this request. Please don't hesitate with any questions/comments/concerns. Thanks, James [1] https://fedorahosted.org/nitrate/

3 7

System Naming Schema
by Adam M. Dutko 30 Apr '11

30 Apr '11

The following disscussion about how to name machines popped up in the meeting today: 15:42 < nirik> basically the issue is this... we have a db01 machine in puppet, we want to replace it with another new shiny instance. 15:42 < nirik> if we also call it db01, then there is a time where we have to cut over and the old machine gets no more updates, etc. 15:43 < nirik> and there may be puppet changes to make the new db01 happy that would have to be reverted if we went back to the old one. I am attempting to continue it on the mailing list. Instead of using functional names like db01, db02, web01 and etc. I've always used mythological names like heracles, odin, thor, and etc. It makes it a bit difficult to determine the functionality of a system but it makes it a lot easier to perform upgrades and changes like Nirik mentioned. If desired we could then use DNS in the form of CNAME records to create "functional aliases" like db01 and etc. that wouldn't affect our core utilities like puppet. Just a thought. Feedback?

7 7

Outage: FAS and dependent web apps - 2011-05-02 21:00 UTC
by Toshio Kuratomi 29 Apr '11

29 Apr '11

Outage: FAS and dependent web apps - 2011-05-02 21:00 UTC There will be an outage starting at 2011-05-02 21:00 UTC, which will last approximately 1 hour. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2011-05-02 21:00 UTC' Reason for outage: Performing an upgrade of the Fedora Account System (FAS) which will require database schema changes. This requires taking down FAS while the schema is updated. While FAS is down, the dependent web application services will be unavailable. Affected Services: Bodhi - https://admin.fedoraproject.org/updates/ Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ Additionally, the following services will be available for reading but not available for making changes: Fedora Hosted - https://fedorahosted.org/ Fedora Insight - https://insight.fedoraproject.org/ Translation Services - http://translate.fedoraproject.org/ Wiki - http://fedoraproject.org/wiki/ Unaffected Services: BFO - http://boot.fedoraproject.org/ Buildsystem - http://koji.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - http://docs.fedoraproject.org/ Email system Fedora People - http://fedorapeople.org/ Fedora Talk - http://talk.fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Smolt - http://smolts.org/ Spins - http://spins.fedoraproject.org/ Start - http://start.fedoraproject.org/ Torrent - http://torrent.fedoraproject.org/ Main Website - http://fedoraproject.org/ Ticket: https://fedorahosted.org/fedora-infrastructure/ticket/2748 Contact Information: Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above. -Toshio Kuratomi

1 0

serverbeach dns
by Seth Vidal 29 Apr '11

29 Apr '11

looks like the ips we had for the sb-provided dns servers: 66.135.45.76 66.135.45.92 are no longer working as name servers, so sb* and collab1, etc were not able to talk to puppet b/c they couldn't resolve it. I've pushed a new resolv.conf to those boxes using our nameservers instead. it appears to be working properly. just a heads up. -sv

1 0

Meeting *TODAY* 2011-04-28 at 1900 UTC in #fedora-admin
by Derek Carter 28 Apr '11

28 Apr '11

The infrastructure team will be having it's weekly meeting today at 1900 UTC in #fedora-meeting on the freenode network. Suggested topics (suggested by whom): * Upcoming Tasks(nirik) * Application logging info gathering (nirik) * Meeting tagged tickets: https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assi… * New folks introductions * Status of the sysadmin-apprentice group Submit your agenda items, as tickets in the trac instance and/or send a note replying to this thread. Thanks

1 1

Outage: Wiki, Insight, Smolt, Wordpress, Zarafa database outage - 2011-05-04 20:00 UTC
by Kevin Fenzi 28 Apr '11

28 Apr '11

Outage: Wiki, Insight, Smolt, Wordpress, Zarafa database outage - 2011-05-04 20:00 UTC There will be an outage starting at 2011-05-04 20:00UTC, which will last approximately 2 hours. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/Infrastructure/UTCHowto or run: date -d '2011-05-04 20:00 UTC' Reason for outage: The database backend for several services is being moved to new hardware and upgraded. This will result in an outage of services using that database server. Note that some services should move quickly and downtime on them will be small. The wiki should be up reasonably quickly, but smolt may be down for much of the window. Affected Services: Fedora Insight - https://insight.fedoraproject.org/ Smolt - http://smolts.org/ Wiki - http://fedoraproject.org/wiki/ Fedora Blogs - http://blogs.fedoraproject.org/ Zarafa - http://admin.fedoraproject.org/zarafa Unaffected Services: BFO - http://boot.fedoraproject.org/ Bodhi - https://admin.fedoraproject.org/updates/ Buildsystem - http://koji.fedoraproject.org/ GIT / Source Control DNS - ns1.fedoraproject.org, ns2.fedoraproject.org Docs - http://docs.fedoraproject.org/ Email system Fedora Account System - https://admin.fedoraproject.org/accounts/ Fedora Community - https://admin.fedoraproject.org/community/ Fedora Hosted - https://fedorahosted.org/ Fedora People - http://fedorapeople.org/ Fedora Talk - http://talk.fedoraproject.org/ Main Website - http://fedoraproject.org/ Mirror List - https://mirrors.fedoraproject.org/ Mirror Manager - https://admin.fedoraproject.org/mirrormanager/ Package Database - https://admin.fedoraproject.org/pkgdb/ Start - http://start.fedoraproject.org/ Torrent - http://torrent.fedoraproject.org/ Translation Services - http://translate.fedoraproject.org/ Ticket Link: https://fedorahosted.org/fedora-infrastructure/ticket/2745 Contact Information: Please join #fedora-admin in irc.freenode.net or add comments to the ticket for this outage above.

1 0

farewell to cvs.fedoraproject.org
by Kevin Fenzi 28 Apr '11

28 Apr '11

I have just taken cvs.fedoraproject.org down since the last 3 projects using it are moved off. ;) I'll wait a week or so before removing it entirely. If anyone finds anything that is still trying to access it or look for resources there, please let me know and we can get them moved off there. https://fedorahosted.org/fedora-infrastructure/ticket/2519 Thanks for all the good times CVS! kevin

1 0

new machines/moves over the next few weeks
by Kevin Fenzi 26 Apr '11

26 Apr '11

Greetings. I'd like to move guests that are currently on xen10 and xen12 in the next few weeks before final freeze. Both these machines are going off hardware support soon, so we should get our guests off them. They currently have: xen10.phx2.fedoraproject.org:log1:running xen10.phx2.fedoraproject.org:memcached2:running xen12.phx2.fedoraproject.org:db01:running For xen10, this week I will look at: - Nuking log01 in favor of log02 (which is already all setup). - Setup a memcached03 box (rhel6) and nuke memcached2. - Take down xen10 For xen12 things will be a bit trickier as we need to move db01: - Setup a db05 (rhel6, etc) - dump/restore data to get a idea how long it will take. Currently there's a LOT of data on db01, but much of it's stuff we no longer care about: transifex, cacti, prelude. which we can omit. - Schedule outage for around 2011-05-03 or so for insight, wiki, smolt, wordpress, zarafa. - Take down xen12. After F15 release is done, the next machine on the hit parade is xen14: xen14.phx2.fedoraproject.org:app01:running xen14.phx2.fedoraproject.org:puppet01:running We can probibly do that one without an outage needed. If anyone would like to assist with any of this, or has a better plan or ideas, let me know. ;) kevin

2 3

Introduction
by Frazer, Cody R 25 Apr '11

25 Apr '11

Hello, My name is Cody Frazer and I'm interested in helping with the Fedora Project. I'm most interested in doing system administration and the like. I live near St. Louis, Missouri (CST). I have one year of college towards a B.S. in Computational Physics and Computer Science where I worked in C++, Visual Basic, PHP, MySQL and Perl. This past year, I've worked as a full-time web developer at Concordia Publishing House, where I work mostly in Ruby on Rails. We have a small team so we have to manage our servers and do our own database, systems, and network administration. I'm an avid Vim user and I enjoy streamlining my configuration for maximum productivity. I really enjoy writing scripts in bash and ruby do normal filesystem activities (doing advanced/specific large-scale file movement/finding/changing). I also have a sort of file system OCD. I'm very particular about what gets added to my system. I love making sure that every tool and development method I use is keeping my system in pristine condition. I love making sure that changes are modular, unobtrusive, and easily controllable/removable. My favorite language for sys. admin. is ruby. I'm willing and excited to learn anything necessary. One of my favorite things is learning new things and improving my toolkit. Here's a list of skills that I possess: C: familiar/basic C++: basic Perl: basic Python: basic Lisp: basic Visual Basic: basic Ruby: intermediate Rails: intermediate Fedora: basic-intermediate Bash: intermediate Apache: basic Java: basic Linux: basic-intermediate MySQL: basic-intermediate TCL: familiar Tk: familiar-basic PHP: basic I want to join Fedora Project for a few reasons: 1) it's a large project and it seems like there's enough to do that I can do a lot of what I enjoy (sys. admin.) 2) I'm very appreciative of Fedora and Open Source software, in general. It's given me soo much, so I'd like to use my skills to give back. I couldn't imagine being a developer/scientist without Open Source and Linux. 3) Fedora was my first and remains one of my favorite Linux distributions. I use it and am invested in helping to improve/support it. I really would like to do anything involving system administration. I love scripting and automating things for developers to make development streamlined. I'm also very passionate about having the best tools available. I'm constantly critically analyzing every tool I use. I think I'd like to do this on the operating system level - make sure it's running smooth, not full of junk, and provides the best environment for development, deployment, or whatever else it is made to do. Currently, I'm working two jobs for 7 days a week and 60-70 hours. I'm pretty busy, but I've got great time management skills. I like maximizing my time so that I'm always learning or working. I can easily reserve Saturday mornings for work and probably a few hours for a couple evenings during the week. I can guarantee 4 hours on Saturday at the least. At most, I can guarantee that and 2 hours Monday - Thursday, and 4 on Friday. So 4 hrs./wk. minimum and 16 hrs./wk. maximum. I'm thinking that the average I'll be able/expecting to spend is 10 hrs./wk. Hope this wasn't too much information or useless babble! :) Thanks, Cody

4 9

Changes to PHX2 netapp ISCSI
by Stephen John Smoogen 25 Apr '11

25 Apr '11

Previously, the PHX2 facility has had one ISCSI partition that was mounted on multiple xen/kvm servers to allow for boxes to be moved from one server to another when needed. This worked for in our original PHX1 facility, but the new netapp can be configured in more ways and the storage admins have recommended we split up our storage into smaller "containers" to help deal with possible performance and continuity of service issues. Old partition: xenGuests New partitions: virtWebGuests virtBuildGuests currently on xenGuests the following partititons and guests live: compose-x86-02 xenGuests -wi-a- 300.00g cvs-storage xenGuests -wi-a- 300.00g cvs1 xenGuests -wi-a- 75.00g cvs2 xenGuests -wi-a- 15.00g koji2 xenGuests -wi-a- 10.00g nfs01 xenGuests -wi-a- 10.00g pkgs01 xenGuests owi-a- 75.00g relepel01 xenGuests -wi-a- 30.00g relepel1-old xenGuests -wi-a- 30.00g sign-bridge01 xenGuests -wi-a- 30.00g ns04 xenGuests -wi-a- 15.00g db02 xenGuests -wi-a- 75.00g we would rebuild/move ns04 and db02 over to virtWebGuests and the other boxes would be rebuilt as needed on the virtBuildGuests share. [We can also create more shares for the build network.] -- Stephen J Smoogen. "The core skill of innovators is error recovery, not failure avoidance." Randy Nelson, President of Pixar University. "Let us be kind, one to another, for most of us are fighting a hard battle." -- Ian MacLaren

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure April 2011