Re: [OpenStack-Infra] Zanata broken on Bionic
Hello Carlos,
I am not sure which team you are working currently, but heard that you are
working in a tooling team a few months ago - would u help to resolve this?
I can’t forget your name - we met on Tokyo Summit in 2015, and many
OpenStack team members appreciate your lots of effort on Zanata + OpenStack.
Andreas, is it the same person as who I ask to? :) Hopefully it isn’t wrong.
With many thanks,
/Ian
On Friday, March 15, 2019, Andreas Jaeger wrote:
> All translation jobs are failing since zanata-cli fails, looking at the
> error it looks like Java11 is too new for zanata-cli.
>
> I tested the most recent zanata-cli package 4.6.2 (from last year), and
> it failed as well.
>
> Logs:
> http://logs.openstack.org/periodic/git.openstack.org/openstack/python-
> keystoneclient/master/propose-translation-update/8c7d3e8/
> job-output.txt.gz#_2019-03-15_07_56_38_362424
>
> I see two options:
> 1) Downgrading java to openjdk8 in the used bionic image
> 2) Going back to Xenial for the job
>
> Alex Eng is not working on Zanata anymore and was our contact in the
> past - I remember another person involved but forgot his name ;( Anybody
> remembers or can reach out to Zanata folks for help on fixing this for
> good, please?
>
> I've pushed https://review.openstack.org/643539 for going back to
> Xenial as temporary workaround. But we should figure out the real fix,
>
> Andreas
> --
> Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>GF: Felix Imendörffer, Jane Smithard, Graham Norton,
>HRB 21284 (AG Nürnberg)
> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
>
>
> ___
> OpenStack-Infra mailing list
> OpenStack-Infra@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [storyboard] [I18n] Can Storyboard web pages be translatable to multiple languages?
Hello, I wanna ask whether https://storyboard.openstack.org/ web pages can be translatable to multiple languages (e.g., Chinese, Japanese, Korean, German, French, Spanish, ...) or not. I have thought such idea on my mind from some time period ago, and I think now would be a good timing for raising this question since it seems that more project repositories are migrating to Storyboard, and internationalization of Storyboard is one of criteria for I18n team to decide to migrate to Storyboard (FYI: discussion on I18n team - [1]). From my very brief investigation, it seems that adding I18n support on html pages like [2], extracting translation source strings to pot files, syncing with Zanata [3] with powerful infra support [4] would make Storyboard translatable with translating to multiple languages by I18n team. Am I understanding correctly and can I18n team get help on such effort? With many thanks, /Ian [1] http://lists.openstack.org/pipermail/openstack-i18n/2018-September/003307.html [2] http://git.openstack.org/cgit/openstack-infra/storyboard-webclient/tree/src/app/stories/template/list.html#n26 [3] http://translate.openstack.org/ [4] https://docs.openstack.org/i18n/latest/infra.html ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Asking for comments on translate-dev.o.o auth table mismatch
Hello, I would like to update this (sorry for my late sharing on this mailing list and infra team): - Jimmy commented on the Etherpad on Dec 13. According to his comment, it would be nice if Zanata manages openid full url by separating into domain part (e.g., "openstackid.org") and rest part (e.g., "/..."). @Patrick, would it be possible to support in Zanata as a new feature? By the way, I18n team decided to have another approach: freshing database used in translate-dev.openstack.org, which would address current openstackid issues and I18n PTL proposed https://review.openstack.org/#/c/531736/ . It would be so nice if the patch gets more attention from system-config cores. With many thanks, /Ian Patrick Huang wrote on 12/6/2017 11:03 AM: I've put my comments in the etherpad. On Wed, Dec 6, 2017 at 11:19 AM, Ian Y. Choi <ianyrc...@gmail.com <mailto:ianyrc...@gmail.com>> wrote: Hello, Since Zanata upgrade to 4.3.1 on translate-dev.openstack.org <http://translate-dev.openstack.org> is going well [1], I think it is a good time to discuss translate-dev.o.o authentication problems. I wrote a brief current problem on authentication issues in translate-dev.o.o and my suggestion on proposed solution : https://etherpad.openstack.org/p/translate-dev-openstackid-issues <https://etherpad.openstack.org/p/translate-dev-openstackid-issues> . Clark looked at this proposal and said that it looked good previously. It would be so nice if infra team, openstackid developers, I18n PTL, and Zanata development team would be in same pages. In my opinion we can discuss more on for example: - openstackid developers: How the sync between openstackid-dev and openstackid databases is accomplished (regarding password mismatch) - Sharing Zanata auth table structure from Zanata development team would be nice. With many thanks, /Ian [1] https://storyboard.openstack.org/#!/story/2001362 <https://storyboard.openstack.org/#%21/story/2001362> -- Patrick Huang Senior Software Engineer Engineering - Internationalisation Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8278 Fax: +61 7 3514 8199 IRC: pahuang github: github.com/huangp <http://github.com/huangp> Website: www.redhat.com <http://www.redhat.com> ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Asking for comments on translate-dev.o.o auth table mismatch
Hello, Since Zanata upgrade to 4.3.1 on translate-dev.openstack.org is going well [1], I think it is a good time to discuss translate-dev.o.o authentication problems. I wrote a brief current problem on authentication issues in translate-dev.o.o and my suggestion on proposed solution : https://etherpad.openstack.org/p/translate-dev-openstackid-issues . Clark looked at this proposal and said that it looked good previously. It would be so nice if infra team, openstackid developers, I18n PTL, and Zanata development team would be in same pages. In my opinion we can discuss more on for example: - openstackid developers: How the sync between openstackid-dev and openstackid databases is accomplished (regarding password mismatch) - Sharing Zanata auth table structure from Zanata development team would be nice. With many thanks, /Ian [1] https://storyboard.openstack.org/#!/story/2001362 ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Add member to upstream-institute-virtual-environment-core group
Hello Infra team, Could you please add "Mark Korondi" in upstream-institute-virtual-environment-core group? He is the bootstrapper of the project: https://review.openstack.org/#/c/490202/ , and also managing the repository is important for preparing Upstream Institute in Sydney Summit. @ildikov & @diablo_rojo: I am not pretty sure but if adding openstack-training-guides-core into this upstream-institute-virtual-environment-core group would be nice, please add your thoughts :) With many thanks, /Ian ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Fwd: Re: Translations-test site
Hello infra team (copying: openstack-i18n mailing list), I18n team initially proposed a spec for translation checksite about two years ago [1], and the specification was revised [2] by making use of OpenStackAnsible with the help of Horizon team [3]. Three teams have been communicating a lot and now we think that it is time to deploy translate checksite using OpenStackAnsible into openstack-infra side. Would you help us to successfully deploy translate checksite into openstack-infra? It would be much nice if such deployment is accomplished by around R-5 [4], since Soft and Hard StringFreezes are important for translators, but it we do not have enough time to prepare by then, it would be also nice to prepare translate checksite for the next cycle. I am copying & pasting a recent message from Frank to share up-to-date status on translate checksite implementation status. === We are nearly done with the developement of translation check site. At the moment I'm doing some test with the work from Andy but basicly it's realized as described in [5] Now it's time to think about the installation on openstack-infra site. I think we need a new server with Ubuntu Xenial, clone the git repo [6] and run the script on [7]. Finaly with need a cron job to sync the translation files periodically. The question is what you need for the installation. Is it a puppet manifest like [8] or you prefer a new format? The installation of the site takes up to 50-60 min. This was a problem in the past for running puppet. But we need the time only for a fresh installation. Later we can refresh code with git pull as ansible task or manually. kind regards Frank === With many thanks, /Ian [1] https://review.openstack.org/#/c/184559/ [2] https://review.openstack.org/#/c/440825/ [3] http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_check_site.html [4] https://releases.openstack.org/pike/schedule.html [5] http://git.openstack.org/cgit/openstack-infra/infra-specs/tr ee/specs/translation_check_site.rst [6] http://git.openstack.org/cgit/openstack/openstack-ansible/tree/ [7] http://git.openstack.org/cgit/openstack/openstack-ansible/tr ee/scripts/gate-check-commit.sh [8] https://review.openstack.org/#/c/276466/ ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [I18n] Inviting to Zanata (translation platform) webinar: June 8th at 13:00 UTC
Hello, I am organizing a webinar by inviting Zanata (OpenStack translation platform) development team as an invited speaker and seeing #openstack-meeting IRC channel for questions and answers on tomorrow (June 8th) 13:00 UTC. I would like to invite to all who are interested in OpenStack translation platform and which new features I18n team is expecting with a newer version of Zanata. With many thanks, /Ian ( http://lists.openstack.org/pipermail/openstack-i18n/2017-June/002933.html ) Original Message Subject: [I18n] Zanata webinar with IRC meeting (qna): June 8th at 13:00 UTC Date: Wed, 7 Jun 2017 14:21:19 +0900 From: Ian Y. Choi <ianyrc...@gmail.com> To: Openstack-i18n <openstack-i...@lists.openstack.org> Hello, I am glad to announce that there will be a webinar from Zanata development team. - Title: The features since 3.9 in Zanata - Date & Time: June 8th at 13:00 UTC (presentation will be for 30-40 minutes) - Invited speaker: Patrick Huang (Senior Software Engineer in Red Hat) - Presentation description: Zanata [1] is an open source translation platform and OpenStack I18n team [2] uses it as a translation platform [3] running upon openstack-infra [4]. At the moment translate.openstack.org is running Zanata version 3.9.6. Here we will have a preview of the new features developed by Zanata team since 3.9.x. This will help us to decide when to upgrade to newer version as well as better utilize the tool once it's upgraded. - YouTube Live URL: https://www.youtube.com/watch?v=mVCSAfk4t54 During this webinar, I18n IRC meeting (#openstack-meeting freenode IRC channel) will be used for questions and answers on the webinar. Also, I have heard that YouTube Live access might be limited to some countries. For that, please tell me for me to prepare a channel with Skype for Business URL. Note that the attendees using Skype for Business might be muted. With many thanks, /Ian [1] http://zanata.org/ [2] https://wiki.openstack.org/wiki/I18nTeam [3] https://translate.openstack.org [4] http://git.openstack.org/cgit/openstack-infra/puppet-zanata ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-I18n] [I18n] Translation platform may be unstable or down during 2/27 - 3/3 due to upgrade
Kato, Tomoyuki wrote on 3/2/2017 11:41 AM: Hello, I would like now to say that Zanata - translation platform has upgrade to 3.9.6 and it looks the working is pretty fine! Thanks for your leadership, Ian. I have continued from the effort from previous PTL - Kato-san :) From my remembrance, one Gerrit review from Frank: https://review.openstack.org/#/c/384239/ opened a good direction to support newer version of Zanata with Java 8. After then, lots of things have been discovered & done for successful Zanata upgrade such as running a Xenial instance, additional Wildfly 10 support, hacking puppet, new Zanata configuration, and testings. Those things have been done with all participation - Infrastructure team, Zanata development team, and I18n team :) Please check, experience, and test the new Zanata - https://translate.openstack.org and if there has some issues, please do not hesitate to ping me or infra team. Note that the previous instance (Zanata 3.7.3 with Trusty & Java 7) is being kept now to revert if there will be a significant issues. If there will be no issues on the next couple of days, Infra team will delete the old Zanata server instance. I really appreciate all the help and support for more than one year for such upgrade : Infra team - clarkb, fungi, ianw, pabelanger, and jhesketh , and also Zanata development team members - aeng and pahuang have actively helped for lots of issues. Also, you might forget early days support: pleia2 and stevek Oh I never forget them - I still remember my first time when I went to Tokyo and I met them, Zanata development team and all I18n members for the 1st time :) But.. I admit that I forgot mentioning them for great support & transition. - Without pleia2's help on Barcelona Design Summit to meet with Clark & I18n team, the current upgrade result would be impossible. - StevenK keeps staying and has helped kindly when asking more details on Zanata side in #openstack-infra channel as a Zanata infra-side pioneer :) With many thanks, /Ian ( And I have marked it in one of successes - https://wiki.openstack.org/wiki/Successes ) With many thanks, /Ian Thanks, KATO Tomoyuki ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-I18n] [I18n] Translation platform may be unstable or down during 2/27 - 3/3 due to upgrade
Hello, I would like now to say that Zanata - translation platform has upgrade to 3.9.6 and it looks the working is pretty fine! Please check, experience, and test the new Zanata - https://translate.openstack.org and if there has some issues, please do not hesitate to ping me or infra team. Note that the previous instance (Zanata 3.7.3 with Trusty & Java 7) is being kept now to revert if there will be a significant issues. If there will be no issues on the next couple of days, Infra team will delete the old Zanata server instance. I really appreciate all the help and support for more than one year for such upgrade : Infra team - clarkb, fungi, ianw, pabelanger, and jhesketh , and also Zanata development team members - aeng and pahuang have actively helped for lots of issues. ( And I have marked it in one of successes - https://wiki.openstack.org/wiki/Successes ) With many thanks, /Ian Clark Boylan wrote on 3/1/2017 3:46 AM: On Fri, Feb 24, 2017, at 12:57 PM, Ian Y. Choi wrote: Hello all, As I shared I18n summary in my previous e-mail [1], there will be a major OpenStack translation platform upgrade during Feb 27 to Mar 3. It implies that: - Translation platform (https://translate.openstack.org) might be unstable or might not work for some time slots during the upgrade period. - “Imported Translation from Zanata” patch proposals [2] might not work. - Translation sync jobs [3, 4] may fail during some period. Infrastructure team kindly agreed to help a lot for the translation platform upgrade (I truly appreciate it!), and I18n team & Zanata [5] development team will have high attention on upgrade and changes. Note that the current Zanata version is 3.7.3, and the target upgrade version is 3.9.6. With many thanks, /Ian [1] http://lists.openstack.org/pipermail/openstack-dev/2017-February/112889.html [2] https://review.openstack.org/#/q/owner:%22OpenStack+Proposal+Bot%22+%22Imported+Translations+from+Zanata%22 [3] http://status.openstack.org/openstack-health/#/g/build_queue/post?groupKey=build_queue=translation [4] http://status.openstack.org/openstack-health/#/g/build_queue/periodic?groupKey=build_queue=translation [5] http://zanata.org I've trimmed the lists a bit here (don't think -dev is as interested). Just want to give a heads up that March 1 at 2300UTC is looking like the time that we will perform the actual cut over of services to the new server. Expect about an hour long outage. I will respond to this thread notifying people of when the work is complete so that we can get more eyeballs on the system to make sure we didn't miss anything. If interested in following along this etherpad is tracking the upgrade steps: https://etherpad.openstack.org/p/translate.o.o-upgrade Thank you, Clark ___ OpenStack-I18n mailing list openstack-i...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [I18n] Translation platform may be unstable or down during 2/27 - 3/3 due to upgrade
Hello all, As I shared I18n summary in my previous e-mail [1], there will be a major OpenStack translation platform upgrade during Feb 27 to Mar 3. It implies that: - Translation platform (https://translate.openstack.org) might be unstable or might not work for some time slots during the upgrade period. - “Imported Translation from Zanata” patch proposals [2] might not work. - Translation sync jobs [3, 4] may fail during some period. Infrastructure team kindly agreed to help a lot for the translation platform upgrade (I truly appreciate it!), and I18n team & Zanata [5] development team will have high attention on upgrade and changes. Note that the current Zanata version is 3.7.3, and the target upgrade version is 3.9.6. With many thanks, /Ian [1] http://lists.openstack.org/pipermail/openstack-dev/2017-February/112889.html [2] https://review.openstack.org/#/q/owner:%22OpenStack+Proposal+Bot%22+%22Imported+Translations+from+Zanata%22 [3] http://status.openstack.org/openstack-health/#/g/build_queue/post?groupKey=build_queue=translation [4] http://status.openstack.org/openstack-health/#/g/build_queue/periodic?groupKey=build_queue=translation [5] http://zanata.org ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [I18n] Regarding Zanata upgrade plan to 3.9.6 with Xenial: Help is needed
Hello, Thanks a lot for so wonderful clarification with detail explanation! I agree that it is time to upgrade Zanata to a newer version with Xenial on translate-dev server. Just two things I would like to say now a little bit more are: - I am not too much familiar with database backups for mysql on Trove, but [1] is related with database backup? Also, I was informed that Reik, Frank's colleague, proposed a patch [2] for translate (production) server backup. It would be much better if it is also considered during the overall upgrade procedure not to lose database data on production. - When I have just added some sentences on [3], I have found that Zanata 4.0 is now released and also it has more enhancements: personally, shortcut key for review approval & reject is so cool...! Then in my opinion, upgrading to Zanata 4.0 not 3.9.6 would be fine. (Doesn't it, Alex?) [1] http://docs.openstack.org/infra/system-config/sysadmin.html#backups [2] https://review.openstack.org/#/c/420735/ [3] https://etherpad.openstack.org/p/I18n-Zanata-enhancement With many thanks, /Ian Clark Boylan wrote on 1/17/2017 4:34 AM: On Mon, Jan 16, 2017, at 09:37 AM, Ian Y. Choi wrote: Hello, I already talked with Alex through IRC: Testing copy version with a smaller scale project was completely fine. As ianw shared: http://lists.openstack.org/pipermail/openstack-infra/2017-January/005058.html and http://lists.openstack.org/pipermail/openstack-i18n/2017-January/002670.html , gc and database status might be suspected which contribute to too slow Zanata. Some additional thoughts from me are: - Different mysql driver from Trusty: https://review.openstack.org/#/c/406398/1/manifests/init.pp might contribute, after seeing Alex's comment on "mysql driver". - Current master version of openstack-manuals in translate.o.o (not translate-dev.o.o) has 17,423,952 words, which is larger than the number of words for versions: test-version-creation2, test-version-creation, and stable-newton. If it is really the bug from Zanata, then future execution of creating a new version: "stable-ocata" after Ocata documentation release will contribute to production server downtime. @clarkb, then might it be better to also test with larger memory size? Or testing openstackid-dev for a while would be a good idea now? One correction: I thought http://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/site.pp#n1392 enumerates the root admins in translate.openstack.org and also translate-dev.openstack.org, but it was my complete misinterpretation on the file. After deeper investigation, I have found that the list is for Zanata instance admins : https://review.openstack.org/#/c/172528/ . I'd like to make sure we get back on the same page with everything going on as I feel like we have all gone in about 5 different directions the last couple days. Clarifications: We have not upgraded to 3.9.6 yet. We are merely running the same version of Zanata as in production (3.7.3) on top of Xenial and Java 8 instead of Trusty and Java 7. This is because it is easier to separate the OS upgrade from the application upgrade and will allow us to upgrade the OS for translate.openstack.org first, then upgrade Zanata. The MySQL instance is running in a Trove instance and is not collocated with Zanata on the same instance. The Zanata wildfly instance can use 4096 Megabytes of memory (according to the Xmx value) on an 8GB memory VM. TODO: There have been a list of things that have been suggested that we try and I would like use to decide whcih are most important and start there. Increase memory on translate-dev.openstack.org host. I think the next biggest VM size is 16GB of ram. That doubles system memory and we can double Xmx to 8192MB as well. Increase size of Trove database instance. It is currently 2GB RAM instance, we can double that to 4GB. Upgrade Zanata to 3.9.6 on translate-dev.openstack.org if you are happy with calling this issue and Zanata bug and go from there. Then once at least some of this is done and we are happy with it we can upgrade the production instance. What are the things that people feel are important here? Personally I think that if we only have performance issues when hitting what is probably a Zanata bug then I wouldn't bother increasing the resources available to the dev instance and instead continue focusing on testing of the upgrade. My suggestion would be to upgrade to 3.9.6 and if it looks good do the production instance as well. But feedback is much appreciated as I know that others have been putting a bit of effort into this and may have better ideas than me :) Clark ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [I18n] Regarding Zanata upgrade plan to 3.9.6 with Xenial: Help is needed
Clark Boylan wrote on 1/14/2017 6:31 AM: On Thu, Jan 12, 2017, at 02:36 PM, Ian Y. Choi wrote: - I18n team completed tests with current Zanata (3.7.3) with Xenial [1], but found one error mentioned in [2]. It seems that more memory size allocation for Zanata with Java 8 is needed. Could you upgrade the memory size for translate-dev server first to test again? How much memory do we think will be necessary? The current instance is an 8GB RAM instance. As long as we have quota for it, there should not be a problem redeploying on a bigger instance. Regarding this, I have recently seen another Zanata server: https://translate.zanata.org/ already uses Zanata 3.9.6. Alex, could you share how much memory is being used for this server? (server memory size, jvm heap size, and so on). I think the server will use Java 8 (OS will be Fedora, right?). It might provide good estimation of how much memory is needed for translate-dev and also translate (in future) with us I think. - I remember that newer version of openstackid needs to be tested with translate-dev. So I have just uploaded this patch: https://review.openstack.org/#/c/419667/ . I18n team needs more tests, but I think it is a good time to change to openstackid-dev for such testing. Please ping me after openstackid-dev test with translate-dev is completed with no error :) - On last I18n team meeting, I18n team recognized that the backup would be so important. Is there more disks for such backup on translate-dev and translate.o.o server? And the approach implementing like [3] looks quite a good idea I think. Thanks, Frank! I have commented on this change. I would prefer we not backup the dev server and only backup the production server. We don't treat our dev servers as permanent or reliable installs as they may need to be reloaded for various reasons to aid development and testing. Also we should set up backups similar to how we do the other services (I left a comment on this change with a link to an example). Thanks for kind comments, Clark! I have just read and I agree with your comment. - Can I have root access to translate-dev and translate server? This is something that can be discussed with the infra team, typically we would give access to someone assisting with implementation to the -dev server while keeping the production server as infra-root only. I will make sure fungi sees this. I agree with your thoughts and also fungi's comments mentioned in another thread :) One additional thought I just want add for the consideration of this is that at least it would be much better if at least one active I18n team member who assists the implementation, on-going upgrade and operational issues (e.g., Zanata login is not working) has the access to dev and production servers with providing good insights on Zanata infra side with I18n team members. Also, I expect more aligned communication between I18n team and Infra team. To accomplish this, I would at least one I18n team member will have good insight on such as understanding how Zanata deployment has implemented previously and seeing & analyzing server logs. This one I18n member to tho such role should not be me, but unfortunately, it is difficult for me to find another relevant I18n team member now. Now I would like to think more on it and also discuss with I18n team members, and then ask again if my thoughts will come up (Or I may need more discussion with infra team members during PTG). With many thanks, /Ian Hope this helps, Clark ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [I18n] Regarding Zanata upgrade plan to 3.9.6 with Xenial: Help is needed
Hello, I would like to summarize the status for Zanata (translation platform) upgrade here from various but a little bit scattered results, and also ask some questions to infra team. - I18n team completed tests with current Zanata (3.7.3) with Xenial [1], but found one error mentioned in [2]. It seems that more memory size allocation for Zanata with Java 8 is needed. Could you upgrade the memory size for translate-dev server first to test again? - I remember that newer version of openstackid needs to be tested with translate-dev. So I have just uploaded this patch: https://review.openstack.org/#/c/419667/ . I18n team needs more tests, but I think it is a good time to change to openstackid-dev for such testing. Please ping me after openstackid-dev test with translate-dev is completed with no error :) - On last I18n team meeting, I18n team recognized that the backup would be so important. Is there more disks for such backup on translate-dev and translate.o.o server? And the approach implementing like [3] looks quite a good idea I think. Thanks, Frank! - Can I have root access to translate-dev and translate server? I really appreciate kind and continuous help for such Zanata upgrade, but sometimes I feel that considering priority like in [5] would be also a good idea. (Or somewhere on i18n-specs, which is not yet revised with items [6]). Since O cycle is rather short and also StringFreeze period is important for I18n team with translations, it seems that applying new Zanata version into production (I mean, translate.openstack.org) would be difficult. But, I really want to upgrade Zanata 3.9.6 with Xenial in translate-dev.openstack.org during O cycle and hope that all tests will be fine. Then I would like to have some discussions during PTG event including this topic :) [1] https://etherpad.openstack.org/p/i18n-zanata-test-for-translate-dev [2] http://lists.openstack.org/pipermail/openstack-i18n/2017-January/002643.html [3] https://review.openstack.org/#/c/419389/ [4] http://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/site.pp#n1416 [5] http://specs.openstack.org/openstack-infra/infra-specs/#priority-efforts [6] http://specs.openstack.org/openstack/i18n-specs/ With many thanks, /Ian Clark Boylan wrote on 12/8/2016 7:56 AM: On Wed, Dec 7, 2016, at 01:08 AM, Frank Kloeker wrote: - Original Nachricht Von: Clark Boylan <cboy...@sapwetik.org> An: "Ian Y. Choi" <ianyrc...@gmail.com>, OpenStack Infra <openstack-infra@lists.openstack.org> Datum: 03.12.2016 00:37 Betreff: Re: [OpenStack-Infra] [I18n] Regarding Zanata upgrade plan to 3.9.6 with Xenial: Help is needed On Tue, Nov 22, 2016, at 03:56 PM, Clark Boylan wrote: On Wed, Nov 9, 2016, at 09:49 AM, Ian Y. Choi wrote: Hello, I18n team currently uses Zanata in translate.openstack.org so frequently as an OpenStack translation platform. I really appreciate great help from all contributors, especially infra team members and Zanata development team : http://specs.openstack.org/openstack-infra/infra-specs/specs/migrate_to_zana ta.html . Thanks to [1], the current deployed Zanata version is 3.7.3. During about one year, there were some discussions for Zanata enhancements in many i18n IRC meetings, and especially Austin & Barcelona summits [2]. Zanata development team members kindly listen to such enhancements, and they are actively upgrading Zanata with fixing bugs and incorporating cool features, which are very helpful for translators. One main obstacle for upgrading Zanata (as far as I know) was that newer versions of Zanata requires Java 8, but it is not default on Trusty. To upgrade Zanata, upgrading from Trusty to Xenial for translate.openstack.org is needed since default-jre-headless on Trusty is Java 7 and Xenial is Java 8. Recently [3] has been merged, so I really hope that i18n team will see newer version of Zanata soon :) I18n team discussed Zanata upgrade with pleia2 and clarkb during i18n Barcelona meetup (See number 4 in [4]), and the following is my thoughts on appropriate procedures to support Zanata latest version (Currently 3.9.6 - [5]): 1. Xenial OS test for translate-dev.openstack.org : IMO after tests from infra team, [6] will be changed from "# Node-OS: trusty" to "# Node-OS: xenial" 2. Using openstackid instead of openstackid-dev for translators to test translate-dev.o.o : I uploaded a patch [7]. 3. Uploading a patch on openstack-infra/puppet-zanata for Zanata 3.9.6 : [8] is a reference for previous upgrade from Zanata 3.7.2 to 3.7.3 4. translate-dev.o.o with Zanata 3.9.6 will be ready => I18n translators will test it :) 5. If there will be no error for Zanata 3.9,6, then node upgrade from Trusty to Xenial and Zanata upgrade to 3.9.6 is needed for translate.openstack.org : changing [9] line and also proposing a patch similar to [10] will be needed later. Since newer ve
Re: [OpenStack-Infra] [I18n] Regarding Zanata upgrade plan to 3.9.6 with Xenial: Help is needed
Hello Clark, Thanks a lot for helping Xenial upgrade. https://review.openstack.org/#/c/393405/ needs to be merged for me and other translators to test translate-dev.o.o with current Zanata 3.7.3. With many thanks, /Ian Clark Boylan wrote on 12/6/2016 9:04 AM: This change has merged and the service seems up again. Sorry for not checking that before weekending. Clark On Mon, Dec 5, 2016, at 02:17 PM, Clark Boylan wrote: I think puppet undid my fixes because https://review.openstack.org/#/c/406398/ hasn't merged yet. Once that merges we should be good (I will work on getting that in today). Clark On Mon, Dec 5, 2016, at 01:42 PM, Alex Eng wrote: Hi, For both URL, I can see wildfly 9, but nothing else. What are we testing here again? - Alex Eng Senior Software Engineer Globalisation Tools Engineering DID: +61 3514 8262 <callto:+61+3514+8262> Mobile: +614 2335 3457 <callto:+614+2335+3457> Red Hat, Asia-Pacific Pty Ltd Level 1, 193 North Quay Brisbane 4000 Office: +61 7 3514 8100 <callto:+61+7+3514+8100> Fax: +61 7 3514 8199 <callto:+61+7+3514+8199> Website: www.redhat.com On Sat, Dec 3, 2016 at 9:37 AM, Clark Boylan <cboy...@sapwetik.org> wrote: On Tue, Nov 22, 2016, at 03:56 PM, Clark Boylan wrote: On Wed, Nov 9, 2016, at 09:49 AM, Ian Y. Choi wrote: Hello, I18n team currently uses Zanata in translate.openstack.org so frequently as an OpenStack translation platform. I really appreciate great help from all contributors, especially infra team members and Zanata development team : http://specs.openstack.org/openstack-infra/infra-specs/ specs/migrate_to_zanata.html . Thanks to [1], the current deployed Zanata version is 3.7.3. During about one year, there were some discussions for Zanata enhancements in many i18n IRC meetings, and especially Austin & Barcelona summits [2]. Zanata development team members kindly listen to such enhancements, and they are actively upgrading Zanata with fixing bugs and incorporating cool features, which are very helpful for translators. One main obstacle for upgrading Zanata (as far as I know) was that newer versions of Zanata requires Java 8, but it is not default on Trusty. To upgrade Zanata, upgrading from Trusty to Xenial for translate.openstack.org is needed since default-jre-headless on Trusty is Java 7 and Xenial is Java 8. Recently [3] has been merged, so I really hope that i18n team will see newer version of Zanata soon :) I18n team discussed Zanata upgrade with pleia2 and clarkb during i18n Barcelona meetup (See number 4 in [4]), and the following is my thoughts on appropriate procedures to support Zanata latest version (Currently 3.9.6 - [5]): 1. Xenial OS test for translate-dev.openstack.org : IMO after tests from infra team, [6] will be changed from "# Node-OS: trusty" to "# Node-OS: xenial" 2. Using openstackid instead of openstackid-dev for translators to test translate-dev.o.o : I uploaded a patch [7]. 3. Uploading a patch on openstack-infra/puppet-zanata for Zanata 3.9.6 : [8] is a reference for previous upgrade from Zanata 3.7.2 to 3.7.3 4. translate-dev.o.o with Zanata 3.9.6 will be ready => I18n translators will test it :) 5. If there will be no error for Zanata 3.9,6, then node upgrade from Trusty to Xenial and Zanata upgrade to 3.9.6 is needed for translate.openstack.org : changing [9] line and also proposing a patch similar to [10] will be needed later. Since newer version of Zanata is what translators are expecting a lot :) , I would like to kindly ask infra team members for the help of reviewing and accomplishing such steps with higher priority. @clarkb, would the proposed procedures cover all the things regarding Zanata upgrade? If yes, would you share a sort of scheduled plans? IMO Zanata development team will kindly help following schedules if there will be some issues which are dependent to Zanata itself. [1] https://review.openstack.org/#/c/240383/ [2] https://etherpad.openstack.org/p/I18n-Zanata-enhancement [3] https://review.openstack.org/#/c/384239/ [4] https://etherpad.openstack.org/p/barcelona-i18n-meetup [5] https://github.com/zanata/zanata-platform/releases [6] http://git.openstack.org/cgit/openstack-infra/system-config/ tree/manifests/site.pp#n1282 [7] https://review.openstack.org/#/c/393405/ [8] https://review.openstack.org/#/c/239617/1/manifests/init.pp [9] http://git.openstack.org/cgit/openstack-infra/system-config/ tree/manifests/site.pp#n1257 [10] https://review.openstack.org/#/c/232313/ Just a quick status update on this. I have updated puppet things so that we can deploy translate-dev01.openstack.org on Xenial then CNAME translate-dev.openstack.org to it. (This is part of how we are trying to deploy services in the future to avoid being tied to a single instance in our puppetry). This includes running the noop puppet apply test against Xenial for these nodes on puppet changes as wel
Re: [OpenStack-Infra] Tri-Weekly IRC meetings?
Thierry Carrez wrote on 11/10/2016 6:52 PM: Tony Breeds wrote: On Wed, Nov 09, 2016 at 10:56:38AM +0100, Thierry Carrez wrote: Our scheduling system currently only supports biweekly or weekly meetings. We don't currently support monthly or triweekly meetings (mostly to avoid having to detect complex conflicts with biweekly meetings). I guess we could evolve openstack-infra/yaml2ical to detect more complex conflicts. We'd gain in scheduling flexibility, but lose in our ability to pack the schedule tightly and make it pretty difficult to find empty slots manually. Yeah I think we should add monthly (which would more-or-less cover triweekly) In that you could have a monthly-1st, monthly-3rd and monthly-4th events. --- - time: '1400' day:Monday irc:openstack-meeting frequency: monthly-1st # 1400 on the 1st Monday of the month - time: '2100' day:Thursday irc:openstack-meeting-alt frequency: monthly-3rd # 2100 on the 3rd Thursday of the month - time: '0930' day:Thursday irc:openstack-meeting-alt frequency: monthly-4th # 0930 on the 4th Thursday of the month --- It isn't quite a tri-weekly rotation but may be close enough. The issue with this solution is that any "monthly" slot ends up being exactly the same as a "weekly" slot: you can't schedule any weekly/biweekly meetings at the same time and location. Monthly meetings are therefore paradoxically more wasteful than biweekly meetings, and there is therefore little point in adding them to the software since you can emulate them with "weekly" bookings and just skip most meetings. Instead of monthly-1st/2nd/3rd/4th we could have monthly-1st-odd/1st-even/2nd-odd/2nd-even. That would make them slightly less wasteful (monthly-*-odd things do not conflict with biweekly-even things). But they would be pretty complex to interpret and then why not just use biweekly-* things and skip one every two meetings ? Of course adding this would mean adding tools to grok the data ad see if a meeting slot is open search-open --day Monday --time 1000 --freq weekly ? Which could list the available irc channels or nothing. Later it could be extended to list "nearby options" We'll probably have to add a meeting channel as well, since that will create wasted slots (places where you can't put a weekly or biweekly meeting). +1 for adding a meeting channel :) At first, I had similar idea with Tony: supporting monthly-1st/2nd/3rd/4th would be needed in openstack-infra/yaml2cal, and I started to work for the support like https://review.openstack.org/#/c/395762/ . But after reading ttx's comments, now I am more inclined to substitute with weekly or bi-weekly instead. One of my small concern is that ICS file will also occupy all meeting time every week or bi-week. To solve this concern and also to provide exact information, IMO documenting into description for skipping meetings in some weeks might be needed like https://review.openstack.org/#/c/394719/ . With many thanks, /Ian ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-docs] Training guides meeting @Barcelona Summit
Ildiko Vancsa wrote on 11/10/2016 4:57 AM: Hi, I like the ISO week numbers better. I think it’s more consistent, gives a regular cadence and does not cause confusions with having a meeting on the 5th week or not for instance. My 2 cents. Make sense. Then IMO changing [1] with biweekly-odd or documenting this as description would be good. For monthly meeting occurrence idea, I would like to follow another mail thread [2]. Although the next week is even according to ISO week numbers, let's have training-guides meeting on next Tuesday 13:00 UTC and make accordance for that, since there were no training-guides team meeting for latest 3 weeks. Is this okay for all training-guides meeting attendees? [1] http://git.openstack.org/cgit/openstack-infra/irc-meetings/tree/meetings/training-guides-team-meeting.yaml [2] http://lists.openstack.org/pipermail/openstack-infra/2016-November/004835.html With many thanks, /Ian Thanks and Best Regards, Ildikó On 2016. Nov 9., at 20:21, Ian Y. Choi <ianyrc...@gmail.com <mailto:ianyrc...@gmail.com>> wrote: Hello, IMO if there is an IRC meeting on every week with alternating times for odd and even weeks, having two bi-weekly schedules with alternating times would be self-explanatory. However, if the meeting frequency would be just one or two in a month, then referring such as n-th week in every month would be more intuitive I think. Unfortunately current yaml2ical does not support such logistics, but my WIP patch (https://review.openstack.org/#/c/395762/) will make a clue to support such logistics in the near future I think :) Note that I suggest not to consider 5th weeks because some months do not have 5th weeks. With many thanks, /Ian Jeremy Stanley wrote on 11/9/2016 10:45 PM: On 2016-11-09 13:34:34 +0900 (+0900), Ian Y. Choi wrote: My understanding of *odd* weeks is the 1st and 3rd weeks in every month, since we actually had training-guides meetings with such logistics a few months ago. [...] So you skip 5th weeks when those happen? Or you have back-to-back meeting weeks in those cases? The way alternating weeks are usually interpreted (and handled in the IRC meeting scheduling automation we have) is based on even or odd ISO week numbers: http://git.openstack.org/cgit/openstack-infra/yaml2ical/tree/README.rst?id=c29e042#n163 https://en.wikipedia.org/wiki/ISO_week_date ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org <mailto:OpenStack-Infra@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-docs] Training guides meeting @Barcelona Summit
Hello, IMO if there is an IRC meeting on every week with alternating times for odd and even weeks, having two bi-weekly schedules with alternating times would be self-explanatory. However, if the meeting frequency would be just one or two in a month, then referring such as n-th week in every month would be more intuitive I think. Unfortunately current yaml2ical does not support such logistics, but my WIP patch ( https://review.openstack.org/#/c/395762/ ) will make a clue to support such logistics in the near future I think :) Note that I suggest not to consider 5th weeks because some months do not have 5th weeks. With many thanks, /Ian Jeremy Stanley wrote on 11/9/2016 10:45 PM: On 2016-11-09 13:34:34 +0900 (+0900), Ian Y. Choi wrote: My understanding of *odd* weeks is the 1st and 3rd weeks in every month, since we actually had training-guides meetings with such logistics a few months ago. [...] So you skip 5th weeks when those happen? Or you have back-to-back meeting weeks in those cases? The way alternating weeks are usually interpreted (and handled in the IRC meeting scheduling automation we have) is based on even or odd ISO week numbers: http://git.openstack.org/cgit/openstack-infra/yaml2ical/tree/README.rst?id=c29e042#n163 https://en.wikipedia.org/wiki/ISO_week_date ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] [I18n] Regarding Zanata upgrade plan to 3.9.6 with Xenial: Help is needed
Hello, I18n team currently uses Zanata in translate.openstack.org so frequently as an OpenStack translation platform. I really appreciate great help from all contributors, especially infra team members and Zanata development team : http://specs.openstack.org/openstack-infra/infra-specs/specs/migrate_to_zanata.html . Thanks to [1], the current deployed Zanata version is 3.7.3. During about one year, there were some discussions for Zanata enhancements in many i18n IRC meetings, and especially Austin & Barcelona summits [2]. Zanata development team members kindly listen to such enhancements, and they are actively upgrading Zanata with fixing bugs and incorporating cool features, which are very helpful for translators. One main obstacle for upgrading Zanata (as far as I know) was that newer versions of Zanata requires Java 8, but it is not default on Trusty. To upgrade Zanata, upgrading from Trusty to Xenial for translate.openstack.org is needed since default-jre-headless on Trusty is Java 7 and Xenial is Java 8. Recently [3] has been merged, so I really hope that i18n team will see newer version of Zanata soon :) I18n team discussed Zanata upgrade with pleia2 and clarkb during i18n Barcelona meetup (See number 4 in [4]), and the following is my thoughts on appropriate procedures to support Zanata latest version (Currently 3.9.6 - [5]): 1. Xenial OS test for translate-dev.openstack.org : IMO after tests from infra team, [6] will be changed from "# Node-OS: trusty" to "# Node-OS: xenial" 2. Using openstackid instead of openstackid-dev for translators to test translate-dev.o.o : I uploaded a patch [7]. 3. Uploading a patch on openstack-infra/puppet-zanata for Zanata 3.9.6 : [8] is a reference for previous upgrade from Zanata 3.7.2 to 3.7.3 4. translate-dev.o.o with Zanata 3.9.6 will be ready => I18n translators will test it :) 5. If there will be no error for Zanata 3.9,6, then node upgrade from Trusty to Xenial and Zanata upgrade to 3.9.6 is needed for translate.openstack.org : changing [9] line and also proposing a patch similar to [10] will be needed later. Since newer version of Zanata is what translators are expecting a lot :) , I would like to kindly ask infra team members for the help of reviewing and accomplishing such steps with higher priority. @clarkb, would the proposed procedures cover all the things regarding Zanata upgrade? If yes, would you share a sort of scheduled plans? IMO Zanata development team will kindly help following schedules if there will be some issues which are dependent to Zanata itself. [1] https://review.openstack.org/#/c/240383/ [2] https://etherpad.openstack.org/p/I18n-Zanata-enhancement [3] https://review.openstack.org/#/c/384239/ [4] https://etherpad.openstack.org/p/barcelona-i18n-meetup [5] https://github.com/zanata/zanata-platform/releases [6] http://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/site.pp#n1282 [7] https://review.openstack.org/#/c/393405/ [8] https://review.openstack.org/#/c/239617/1/manifests/init.pp [9] http://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/site.pp#n1257 [10] https://review.openstack.org/#/c/232313/ With many thanks, /Ian ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] I18n in BCN: I18n contributor meetup wrap up
Hello! There were around total 20 participants for last I18n contributor meetup @Barcelona, including Daisy, Zanata team, Infrastructure team, Docs team, and Stackalytics team members! Thank you very much for such all kind and so active participation! Although there have been sort of time conflicts for some active translators and main contributors on other projects but who are helping i18n team a lot, we have met each other and discussed for better i18n. I think i18n team members have dealt various topics with so long time. If there was no time limit: 6pm, i18n members might have discussed much longer :) I am now transferring to go home and my final flight has been delayed about 3 hours, but thanks to such delay, I have briefly summarized now what have been discussed and what are results from I18n contributor meetup. Please see Etherpad: https://etherpad.openstack.org/p/barcelona-i18n-meetup , and "Discussed Topics and Results" (2nd) section. - Andreas Jaeger shortly visited due to his return flight and we agreed with translation job import and export criteria. I have briefly summarized in number *(1)*. - Ilya Shakhat, who is a Stackalytics core developer and maintainer, kindly participated in the meetup. If anyone is interested in Stackalytics with i18n statistics, please refer to number *(3)* for the details. - Although there is another infrastructure team meeting on the same time, Elizabeth K. Joseph and Clark Boylan came to I18n contributor meetup (thank you so much again!). Zanata upgrade *(4)* is what i18n team is really waiting for. Alex Eng and Patrick Huang from Zanata team gave some beneficial feedback (e.g., current Zanata version number and new version release plan) through IRC in real time. Moreover, I hope that some discussion of translation checksite *(5)* will yield more positive progress, although it seems that more discussion is needed. - Also, Lana from Docs team PTL visited to i18n contributor meetup, although she was leading Docs contributor meetup on the same time. Lana and me both agreed that more communication between two teams will make nice fruit *(6)*. - For i18n activities, we have differentiated and clarified the usage of web pages : Zanata dashboard, Wiki, i18n contributor guide, and so on *(2)*, and also finalizing Ocata translation plans is very important during Ocata Design Summit *(7)*! I will update Zanata dashboard according to the finalization. Because of some time restriction, some topics has not been discussed yet or just briefly mentioned. Let's also consider those topics gradually such as on the next IRC meeting. Some meetup participants took photos. Frank shared photos to Etherpad! I hope that other participants will share photos soon. Hope all to have a return flight safely. Again, thank you very much all! With many thanks, /Ian ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] [OpenStack-I18n] What happens in openstack-manual on Zanata?
It seems that it came from one Andreas's patch : http://git.openstack.org/cgit/openstack-infra/project-config/commit/jenkins/scripts?id=1c5f830a40acdd7f9ff666f0154daedcb9f3bdeb Please see https://review.openstack.org/#/c/216988/1/jenkins/scripts/common_translation_update.sh So IMO the previous line #170-175 should be reverted. Since I am now focusing another thing, it would be much better if someone fixes :) Or I will able to manage it after about 7-8 hours later. With many thanks, /Ian Akihiro Motoki wrote on 9/20/2016 3:48 PM: Hi, I see many many 'common' in openstack-manual project on Zanata? https://translate.openstack.org/iteration/view/openstack-manuals/master/documents 'common' in openstack-manuals are linked into individual guides and they are uploaded by accident. Is there any change around upstream_translation_update.sh ? Akihiro ___ OpenStack-I18n mailing list openstack-i...@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Log in problem in translation website
Hello Jimmy, Neither do I currently. The translation web site URL is : https://translate.openstack.org/ . When I do login with OpenStack ID, the url is redirected to https://translate.openstack.org/?cid=[cid_value} but the login is not accomplished in translate.openstack.org . I have seen on IRC that smarcet was working on it. Hope that it will be resolved soon. With many thanks, /Ian Jimmy Mcarthur wrote on 3/17/2016 11:35 AM: Hi - Could you paste the URL of the site you're trying to log into? Thanks, Jimmy Ying Chun Guo wrote: Hello, I meet problem to log in to translation website with Openstack ID. When I click log in button, the page refreshed and nothing happened. The login button is still there. Refstack website cannot login with Openstack ID neither. So I think it's a problem of Openstack ID. Who can help to resolve the problem? Best regards Ying Chun Guo (Daisy) ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
