There are a bunch of places where the narrative text say things like "jenkins runs jobs". This hasn't been true for a while and it's getting less true. Left third-party and running-your-own alone because those are instructions for other people to do things - and we are not yet at the point where we are suggesting anyone do their things like we do our things. The devstack-gate document describes an old deprecated system, but the system is still in use (sadly) so it was mostly left intact. A warning was added so that people would be clear that it was deprecated. Also removed the logstash client config file. It's the only change in here that actually affects running code and became unnecessary when it was switched to geard with Ie3f814e6d3278d87f2a20a72e40b6b92217684fc Change-Id: Iaf2128c3f953976180c71cb599fcbff7bc06c28a
1.7 KiB
- title
-
Translate
Translate
As of the Liberty release, translations for various projects in OpenStack are done on the Zanata translations platform.
At a Glance
- Hosts
- Puppet
- Projects
- Bugs
Overview
The OpenStack Infrastructure runs a production instance and a development instance of Zanata running on the Wildfly JBoss Application Server. Upgrades must be tested on the development server before being applied in production.
Translators work through the Zanata web UI or with the zanata-cli
tool to do their translations. Zuul proposes updates to translations
with the upstream-translation-update
and
propose-translation-update
jobs defined in project-config
zuul jobs.
Projects are added for translations by modifying gerrit/projects.yaml
and
adding the following to the project:
options:
- translate
Projects are then registered with Zanata with the
register-zanata-projects.py from jeepyb
, this is run when gerrit/projects.yaml
changes.
Finally, the translations jobs must be added to the project in jenkins/jobs/projects.yaml
and zuul/layout.yaml
.