mozilla.org has need of a development and testing server for new and revised webtools, and tegu is the leading candidate. In order for it to be suited to this purpose, it needs to have mysql and python installed on it. It may also need a refresh of Perl, Apache, and the /opt/gnu tools to the current standards.
Ray, This sounds to me like a very good excersise of what mozilla.org's needs usually are and how systems are configured. --- Myk, what kind of applications you're talking about? ---
mozilla.org needs a server on which to test upgrades and enhancements to its existing webtools (bugzilla, bonsai, lxr, and tinderbox) as well as new webtools (doctree editor, test case manager, etc.) we are in the process of making available. For example, we are going to be upgrading Bugzilla in the near future, and it would be very valuable for us to be able to test it first since there are invariably bugs in Bugzilla that are not found until it gets used on an installation our size. Our webtools also utilize a number of supporting applications (CVS, MySQL, Perl and its modules, etc.) that require periodic upgrading to fix bugs and provide additional features, and we need a place to test those upgrades. For example, the new version of Bugzilla may require a newer version of the Template Toolkit Perl module (2.0.6), and we plan to look into the performance and other implications of MySQL 4.0.1 and PostgreSQL in the future as potential solutions to some Bugzilla issues. mozilla.org services are critical to the developer community they serve, so we are constantly looking for ways to improve and expand those services. We get help with this from the community itself, which is not only adamant about getting its needs met but also capable of writing the applications to meet them. We want to take advantage of these apps when they become available, for example some of the tools that Gagan Saksena has written in Python (cc:ing him on this bug), but Python and those applications should be tested before we commit to putting them on one of our production servers. I am aware that there was once a plan to move the services on gila (web and mail) onto tegu, since tegu is a much better-equipped machine. Provided Dawn agrees (since she is the mozilla.org staff member responsible for those services), I'd be happy to see that happen and for us to use gila instead of tegu for testing purposes, but then it should happen soon so we can get on with the testing. Otherwise, let's use tegu, in which case we need the latest stable version (or latest version running on mothra) of a few applications installed: Python (version 2.2), MySQL (3.23.44; mothra), Perl (5.6.1), and the Perl modules Text::Wrap (latest version) and Template Toolkit (2.06). We may also want to upgrade Apache from its current version 1.3.12 to version 1.3.19, which is running on mothra, and we may also need additional Perl modules and some Python libraries not part of the standard distribution.
*** Bug 118779 has been marked as a duplicate of this bug. ***
Sounds good to me... in fact I like the fact that you could have "preproduction" or "staging" (politically correct terms) environment separated from production environment. I think we should forgot moving web/mail away from gila. Those don't need powerful system and E450 for that would be waste IMHO. gila is fine for www and mail especially since we added bigger disk to it. If tegu becomes "development server" we need to move all production related services away from it. After that we can experiment much more with it (for example upgrade to Solaris 8, etc). I would also require that if it's used to develop applications it would never become production server. Ie. you wouldn't use it to install experimental application which one day just become production application. That production application has to be moved to production server if that's the case. This way we can give you much more freedom to play with the system since we will never get a ticket from anyone regarding a services on the system. We would restrict our support to OS, hardware, backups, network, perl, python, mysql, cvs etc core components. All services would be yours. We could of course support only OS and let you mess with everything else but it might be better that IC will do perl/python/etc tools so that we can be sure we'll have proper configurations between production/preproduction environments. Let's use this ticket to track dependencies before this system can be dedicated to be the preproduction system. Ray, what do you think would be your ETA/current workload?
Status: NEW → ASSIGNED
Summary: tegu should be outfitted with mysql & python → Make tegu a preproduction/staging system (tracking bug)
>I think we should forgot moving web/mail away from gila. Those don't need >powerful system and E450 for that would be waste IMHO. gila is fine for www and >mail especially since we added bigger disk to it. Seems reasonable to me as long as Dawn agrees. Note that solving the spam problem on gila and migrating from NES to Apache on that machine are still higher priorities than outfitting tegu as a testing server. >If tegu becomes "development server" we need to move all production related >services away from it. After that we can experiment much more with it (for >example upgrade to Solaris 8, etc). I would also require that if it's used to >develop applications it would never become production server. Ie. you wouldn't >use it to install experimental application which one day just become production >application. That production application has to be moved to production server >if that's the case. I certainly intend to do this, but I can imagine a situation in which our other servers become overloaded and we aren't able to acquire new ones. In that situation, we may have to make tegu a production server to handle the additional load. >This way we can give you much more freedom to play with the system since we >will never get a ticket from anyone regarding a services on the system. We >would restrict our support to OS, hardware, backups, network, perl, python, >mysql, cvs etc core components. All services would be yours. > >We could of course support only OS and let you mess with everything else but it >might be better that IC will do perl/python/etc tools so that we can be sure >we'll have proper configurations between production/preproduction environments. I would be happy to let your department be responsible for the hardware, OS, and supporting applications provided there are adequate resources in the department to handle our needs. >Let's use this ticket to track dependencies before this system can be >dedicated to be the preproduction system. Sounds good. Looking forward to it! -myk
Mass changing IC's ticket to reflect current situation. mozilla.org, AOL employees: If you want IC to look at issues reported in bugzilla, please open a Helpdesk ticket and ask it to be routed to AOL R1 Server Operations. We currently have no way to handle comprehensive problem resolution through bugzilla. This is not a change in the way we are supporting mozilla.org - we are still supporting you on the level as before. IC's support is based on Helpdesk ticket system - not bugzilla which only few hard-core people are looking at. Also, projects are handled elsewhere - not in bugzilla. If you have projects you need us to deliver please feel free to contact me directly. Summa summarum: tickets -> Helpdesk Project initiations -> RKotalampi@aol.com
Assignee: daruszka → nobody
Status: ASSIGNED → NEW
tegu is no longer in our possession, and we have other boxes already doing these tasks now.
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.