[OpenStack-I18n] Next generation translation checksite
eumel at arcor.de
Tue Oct 11 05:51:06 UTC 2016
thanks for your reply. First of all: I'm not against Devstack. It's a
very useful tool to install OpenStack in a easy way. The problems
starting if you try to automate things and you trust the installation
The runtime of the puppet-module which we developed this year takes at
least one hour. If you don't have a powerful VM or a bad internet
connection it takes a bit longer. So you are save with a 7200 seconds
On the other hand: DevStack code on master branch ist not stable at all.
Beside that I wouldn't expect that but we had have a very bad phase in
spring with a lots of broken installations. At the moment I deal also
with python3 requirements on Ubuntu 14.04 installation of DevStack. It
didn't work out.
The other things are easy: Fetching the translation files from Zanata,
compile,restart apache, periodically. This things are already done.
The problems starting again if you want update DevStack or reboot the
VM. Thats why I'm thinking about container. There is also an option in
DevStack (on LXC) but I've never tried this.
Am 2016-10-10 18:19, schrieb Akihiro Motoki:
> Thanks Frank for initiating the discussion.
> I am not sure what was the real problem of DevStack-based check site.
> Is it a problem that DevStack takes much time?
> Regarding stability, DevStack itself rarely fails to run in my recent
> Anyway, I do not want to stick DevStack. The reason I used DevStack is
> just because I am
> an OpenStack developer and familiar with DevStack. That's all.
> openstack-ansible is becoming stable, so it is a good candidate.
> I see several key points for the official horizon translation check
> (1) It must be friendly with OpenStack infra scripts including puppet.
> - openstack-ansible may be a good candidate.
> - DevStack based approach takes too long time? timeout?
> (2) How fast can the check site catch up with the horizon code base?
> We would like to use the latest horizon (hopefully with daily
> It is needed to use latest translation as well.
> (3) Can we import translation from Zanata? (IMO this is optional)
> (4) ... (others?)
> My comparison (incomplete):
> (1) ? (Does it take too long? timeout?)
> (2)(3) can be covered by a custom script.
> (1) nice if it works
> (2) it depends on how openstack-ansible catch up with the upstream
> Can openstack-ansible deploy horizon from the latest git
> (3) we can prepare a playbook or a shell script.
> Note that ,as a start line, I think we can deploy the translation
> check site ONLY around the OpenStack release.
> This mean we only need to run the site for about one month. We can try
> to run it longer after that.
> 2016-10-06 1:19 GMT+09:00 Frank Kloeker <eumel at arcor.de>:
>> Dear all,
>> maybe as you know we tried this year to bring the translation
>> checksite on the stage. This wasn't sucessful because the developed
>> puppet module which called DevStack rans out of time and the
>> installation was very often broken. Not practical. Not usable.
>> I have had a deeper look in the last days and I found out
>> openstack-ansible could help us in this situation. There is also an
>> All-In-One installation of OpenStack which puts all parts like
>> Horizon separated into container. It's easy to catch the Horizon
>> container, install the Zanata stuff and fetch the translation files
>> periodically to show the changes of translation on the dashboard.
>> Prototyp is running on https://i18n2.ref.app.telekomcloud.com/ 
>> I have summarized all my thoughts on the etherpad:
>> Pleass take a look and let me know if we should work in the next
>> release cycle on this topic?
>> kind regards
>> OpenStack-I18n mailing list
>> OpenStack-I18n at lists.openstack.org
>  https://i18n2.ref.app.telekomcloud.com/
>  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
More information about the OpenStack-I18n