[OpenStack-I18n] Next generation translation checksite
Ian Y. Choi
ianyrchoi at gmail.com
Thu Oct 6 17:03:34 UTC 2016
First of all, thank you very much for so steady and kind effort,
As I wrote my candidacy for Ocata PTL , I would like to set
translation checksite also high priority in I18n team.
We now have two horizon checksites, though those are not in openstack-infra.
One is what Frank mentioned, and the other is what Akihiro-san shared
about 3 weeks ago .
I have just checked that both work well currently.
And also, Akihiro-san happily shared how to create and just update
Horizon for translation checksite using DevStack .
Frank, what do you think about Akihiro's documentation?
I have heard from him that DevStack is more stable than previously.
Frankly speaking, I am not familiar with Ansible too much.
Fortunately, I have learned Ansible briefly as OpenStack Korea study
group activities for about last two months,
but I need to take more time to see details on Frank's implementation..
For openstack-ansible, from my current understanding, the deployment
time to create all of things
(e.g., nova, neutron, ...) to fully refresh with "up-to-date sources"
will be the same whether we will use DevStack or openstack-ansible.
One cons using DevStack is that DevStack does not support
rejoin-stack.sh anymore , as Frank wrote in Etherpad.
But I think using openstack-ansible with up-to-date sources would have
the same situation.
Does Ansible-based deployment support update mechanism with up-to-date
By the way, when I see  and related threads again, a few more things
need to be considered I think:
- Ansible looks more fancy than DevStack. But in my opinion, failure
in Ansible is also possible as DevStack fails to fully operate.
- Re-deploying DevStack once a week seems to be unnecessary.
Once we have clean DevStack instance just after soft freeze period,
then I think just updating Horizon would be fine
(assuming that we have nice agreement on string change criteria
after soft freezing).
- After new release and there will be a stable branch on
openstack-ansible and/or DevStack,
the translation checksite needs to be re-deployed with the stable
- Translation checksite will be public? What I mean is that
translation checksite should be accessible only to
translators (who have Zanata ID), or OpenStack Foundation members
(who have OpenStack Foundation ID and can openstackid auth)?
In fact, it is not easy for me to follow all of the things on
translation checksite, but I will try to follow more
and let's discuss on this.
And I am copying it with Elizabeth.
Elizabeth, how do you think about Frank's idea?
With many thanks,
Frank Kloeker wrote on 10/6/2016 5:15 PM:
> simple: admin/password
> Am 2016-10-06 00:34, schrieb Yuko Katabami:
>> Hi Frank,
>> Thank you very much for sharing this.
>> May I please ask if the prototype can be accessible by any of us? (I
>> would like to take a look inside, if possible)
>> What is the credential?
>> Kind regards,
>> On 6 October 2016 at 02:19, Frank Kloeker <eumel at arcor.de> wrote:
>>> 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
> OpenStack-I18n mailing list
> OpenStack-I18n at lists.openstack.org
More information about the OpenStack-I18n