Next generation translation checksite
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: https://etherpad.openstack.org/p/openstack-ansible-os_translation-checksite Pleass take a look and let me know if we should work in the next release cycle on this topic? kind regards Frank
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, Yuko On 6 October 2016 at 02:19, Frank Kloeker <eumel@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: https://etherpad.openstack.org/p/openstack-ansible-os_transl ation-checksite
Pleass take a look and let me know if we should work in the next release cycle on this topic?
kind regards
Frank
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
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,
Yuko
On 6 October 2016 at 02:19, Frank Kloeker <eumel@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/ [1] I have summarized all my thoughts on the etherpad:
https://etherpad.openstack.org/p/openstack-ansible-os_translation-checksite
[2]
Pleass take a look and let me know if we should work in the next release cycle on this topic?
kind regards
Frank
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n [3]
Links: ------ [1] https://i18n2.ref.app.telekomcloud.com/ [2] https://etherpad.openstack.org/p/openstack-ansible-os_translation-checksite [3] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hello, First of all, thank you very much for so steady and kind effort, especially Frank! As I wrote my candidacy for Ocata PTL [1], 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 [2]. 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 [3]. 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. Isn't it? One cons using DevStack is that DevStack does not support rejoin-stack.sh anymore [4], 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 sources? By the way, when I see [5] 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 branch. - 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? [1] http://lists.openstack.org/pipermail/openstack-i18n/2016-September/002406.ht... [2] http://lists.openstack.org/pipermail/openstack-i18n/2016-September/002420.ht... [3] http://docs.openstack.org/developer/i18n/check_translation.html#openstack-da... [4] https://review.openstack.org/#/c/291453/ [5] http://lists.openstack.org/pipermail/openstack-infra/2016-July/004524.html With many thanks, /Ian 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,
Yuko
On 6 October 2016 at 02:19, Frank Kloeker <eumel@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/ [1] I have summarized all my thoughts on the etherpad:
https://etherpad.openstack.org/p/openstack-ansible-os_translation-checksite
[2]
Pleass take a look and let me know if we should work in the next release cycle on this topic?
kind regards
Frank
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n [3]
Links: ------ [1] https://i18n2.ref.app.telekomcloud.com/ [2] https://etherpad.openstack.org/p/openstack-ansible-os_translation-checksite [3] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
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 experience. 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 site: (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 update). 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): [DevStack] (1) ? (Does it take too long? timeout?) (2)(3) can be covered by a custom script. [openstack-ansible] (1) nice if it works (2) it depends on how openstack-ansible catch up with the upstream repository. Can openstack-ansible deploy horizon from the latest git repository? (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. Thanks, Akihiro 2016-10-06 1:19 GMT+09:00 Frank Kloeker <eumel@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: https://etherpad.openstack.org/p/openstack-ansible-os_transl ation-checksite
Pleass take a look and let me know if we should work in the next release cycle on this topic?
kind regards
Frank
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hi Akihiro, 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 scripts everytime. 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 timeout. 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. kind regards Frank 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 experience.
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 site:
(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 update). 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): [DevStack]
(1) ? (Does it take too long? timeout?) (2)(3) can be covered by a custom script. [openstack-ansible]
(1) nice if it works (2) it depends on how openstack-ansible catch up with the upstream repository. Can openstack-ansible deploy horizon from the latest git repository? (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.
Thanks, Akihiro
2016-10-06 1:19 GMT+09:00 Frank Kloeker <eumel@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/ [1] I have summarized all my thoughts on the etherpad:
https://etherpad.openstack.org/p/openstack-ansible-os_translation-checksite
[2]
Pleass take a look and let me know if we should work in the next release cycle on this topic?
kind regards
Frank
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n [3]
Links: ------ [1] https://i18n2.ref.app.telekomcloud.com/ [2] https://etherpad.openstack.org/p/openstack-ansible-os_translation-checksite [3] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
Hello, Thank you for continuing discussion. I have talked briefly with Elizabeth (pleia2). Please see the conversation: http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra... . Let's also listen to pleia2's opinion after her looking. And good news is that I met Kevin Carter (IRC: cloudnull) during the talk who can help on the openstack-ansible front :) Frank Kloeker wrote on 10/11/2016 2:51 PM:
Hi Akihiro,
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 scripts everytime. 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 timeout. 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.
Although I recently have not tried yet, such experience is also the same previously.. As I wrote previously, we do not have to make translate checksite stable all the time. IMO we need to replace all the Horizon source (at least) and other sources during intensive horizon translation period, but just replacing *.po files after release date to check and review stable translations might be sufficient (sometimes Horizon source needs to be updated but much fewer than po file updates). I am not pretty sure currently: which type of deployments (DevStack or openstack-ansible) will be more fit between soft freeze and hard freeze period. With many thanks, /Ian
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.
kind regards
Frank
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 experience.
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 site:
(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 update). 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): [DevStack]
(1) ? (Does it take too long? timeout?) (2)(3) can be covered by a custom script. [openstack-ansible]
(1) nice if it works (2) it depends on how openstack-ansible catch up with the upstream repository. Can openstack-ansible deploy horizon from the latest git repository? (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.
Thanks, Akihiro
2016-10-06 1:19 GMT+09:00 Frank Kloeker <eumel@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/ [1] I have summarized all my thoughts on the etherpad:
https://etherpad.openstack.org/p/openstack-ansible-os_translation-checksite
[2]
Pleass take a look and let me know if we should work in the next release cycle on this topic?
kind regards
Frank
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n [3]
Links: ------ [1] https://i18n2.ref.app.telekomcloud.com/ [2] https://etherpad.openstack.org/p/openstack-ansible-os_translation-checksite [3] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
_______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n
participants (4)
-
Akihiro Motoki
-
Frank Kloeker
-
Ian Y. Choi
-
Yuko Katabami