Talk/Pootle maintenance plan
Pootle server maintenance proposal
The pootle server is currently running version 2.1.6, in a not very well documented configuration (svn contains information about the vm, but not the pootle setup). The current version (beta until end of 2012) is version 2.5
The performance is today in a state, where it is very hard to do serious work on the server.
As a consequence it is needed to upgrade the pootle server, and get all configuration changes documented.
The upgrade will NOT have any influence on the data (po files) in the system, but will enable projects like AOO to add much needed extensions.
Furthermore there is a open issue INFRA-4964, that should be solved at the same time.
Pootle Server usage
The pootle server is not only used by AOO, but also by other projects, and in general open to all apache projects.
As a consequence upgrades and other changes must be coordinated with the projects actively using the service.
Goal
The goal is to:
- Upgrade Pootle server to version 2.5 and provide more people with knowledge to maintain the service.
- Enable/Extend the Pootle server to deal directly with SVN (avoid manual copy steps)
- Extend Pootle server to provide extra review controls, like those already present in po2oo.
- Extend Pootle server (together with the pootle project) to allow bulk download/upload (e.g. 1 zip for one language).
- Most important is to enhance the performance, during database and VM tuning.
A special project goal for the AOO project is to make the l10n process more automated and based solely on po files, other projects might benefit from the new toolset, but are not required to use it.
Plan
- 1. Research the current setup
- 2. Backup the current setup (combination of backup/svn)
- 3. Add a new DNS target: translate_test.apache.org, so it easier to test new versions
- 4. Install new version on test, while documenting all changes
- 5. Copy a partial database for test purpose
- 6. Let all projects test the new version
- 7. Vote across projects for a move to production
- 8. Move version 2.5 to production
- 9. Do database tuning on production
- 10. Enhance interface to SVN (in cooperation with pootle project) (first test, then prod)
- 11. Enhance download interface (solely test, then pootle project and wait for new release)
People
jani will do the work except 3), with gmcdonald doing review of the work. the DNS work is done through a JIRA.
After the initial installation, jani will do regular maintenance.
This plan will be sent to all the PMCs of all involved projects for comments, and the server will NOT be changed until positive feed back is received.
This page will be kept updated with the progress.
Jan I.
