07:01:42 <eumel8> #startmeeting OpenStack I18n Meeting
07:01:43 <openstack> Meeting started Thu Feb 22 07:01:42 2018 UTC and is due to finish in 60 minutes.  The chair is eumel8. Information about MeetBot at http://wiki.debian.org/MeetBot.
07:01:44 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
07:01:46 <openstack> The meeting name has been set to 'openstack_i18n_meeting'
07:03:00 <ianychoi> eumel8, hi I am doing another thing so might have slower response now
07:03:14 <eumel8> hi ianychoi
07:03:29 <eumel8> okay, better then nothing ;)
07:03:31 <ianychoi> eumel8, hi :)
07:04:07 <eumel8> hi amotoki
07:04:11 <eumel8> #topic PTG topics
07:04:26 <eumel8> #link https://etherpad.openstack.org/p/dublin-i18n-PTG
07:04:55 <eumel8> there is no much changes in the ptg agenda as last week
07:05:33 <ianychoi> #link https://review.openstack.org/#/c/545377/
07:05:42 <ianychoi> This is the initial version of project doc translation support
07:05:43 <eumel8> ptg schedule and plan are out #link http://lists.openstack.org/pipermail/openstack-dev/2018-February/127611.html
07:05:52 <ianychoi> but still lots of more work would be needed I think
07:06:37 <eumel8> timetable for our team days have the same status like last week. Will talk with pkovar  to fill out the slots
07:07:18 <amotoki> I will be at Dublin, but as of now I cannot attend docs/i18n sessions this time.
07:07:19 <ianychoi> I see
07:07:26 <ianychoi> eumel8, enjoy PTG! Also amotoki :)
07:08:03 <eumel8> fixed dates are contributor guide project incl. translation on Tuesday and User Survey translation on Wednesday
07:09:16 <eumel8> ianychoi: thanks for the proposal. I put in on the etherpad.
07:09:38 <ianychoi> Thanks :)
07:11:14 <ianychoi> As mentioned in the link, Andreas suggested to limit the coverage of project docs
07:11:31 <eumel8> during ptg we could make the zanata live upgrade but I do not screw up hope too high.
07:12:03 <ianychoi> In my opinion, documents in current translation targets in project-config would be nice, but I don't know now how to filter them so need to learn more on project-config repo.
07:13:07 <ianychoi> eumel8, live upgrade in dev first and then production would be good, but I updated Etherpad for Zanata upgrade test last week. I failed to use REST APIs using Zanata CLI on Zanata 4.3 and it might be a big problem in production
07:13:39 <ianychoi> #link https://etherpad.openstack.org/p/i18n-zanata-test-for-translate-dev
07:13:46 <amotoki> kind of gerrit/projects.yaml options ? http://git.openstack.org/cgit/openstack-infra/project-config/tree/gerrit/projects.yaml#n2761
07:13:47 <ianychoi> #link https://zanata.atlassian.net/browse/ZNTA-1757
07:14:18 <amotoki> mine is about "limit the coverage of project docs".
07:14:23 <ianychoi> amotoki, yep I want to learn how to find and use those options in shell scripts
07:14:40 <amotoki> or python scripts :)
07:14:52 <ianychoi> right :)
07:17:30 <eumel8> ianychoi: we will use the same version in zanata live as in dev. The certificate issue happens only on the dev server.
07:17:44 <eumel8> I think it's self-signed there
07:17:53 <ianychoi> eumel8, no - that's because translate-dev.o.o actual server is translate-dev01.o.o
07:18:07 <ianychoi> eumel8, in production, translate.o.o 's actual server is translate-01.o.o
07:19:06 <ianychoi> That's related with "strict hostname checking", not development purpose of translate-dev certificate
07:23:37 <amotoki> hmmm... I cannot understand. certificate hostname should match a hostname served. it is not related to actual hostname.
07:24:06 <amotoki> translate.o.o certificate returns translate.o.o, so translate-01.o.o is not related I think.
07:24:27 <ianychoi> #link http://git.openstack.org/cgit/openstack-infra/system-config/tree/manifests/site.pp#n1595
07:24:45 <ianychoi> Infra team uses translate.openstack.org as alias to translate01.openstack.org
07:25:18 <ianychoi> #link http://paste.openstack.org/show/681324/
07:26:31 <ianychoi> Before Zanata-cli <4.0.0, certificate of translate.o.o and server host translate.o.o and actual host translate01.o.o worked fine with configuring translate.o.o in zanata.xml and config.ini
07:26:39 <eumel8> so we have to change the DNS record from CNAME to A? Or change fqdn in zanata.ini https://github.com/openstack-infra/project-config/blob/master/zuul.d/secrets.yaml#L509 ?
07:27:43 <ianychoi> More tests might be needed but not sure right now this is why I am sharing now .. unfortunately hmm
07:29:11 <eumel8> so we are still far away from zanata upgrade in live
07:30:46 <ianychoi> Hmm, let's figure out how to solve this in this case....
07:34:00 <eumel8> but translate-dev has this self-signed certificate (regarding my browser), so it's not really testable with live
07:36:47 <ianychoi> eumel8, testable with options :)
07:37:17 <ianychoi> Last week, I uploaded some resources to translate-dev using zanata-cli
07:37:58 <eumel8> test means I'm doing the same like in prod - without options ;)
07:38:43 <ianychoi> eumel8, aha right
07:39:30 <eumel8> Qualys said: #link https://www.ssllabs.com/ssltest/analyze.html?d=translate-dev.openstack.org #link https://www.ssllabs.com/ssltest/analyze.html?d=translate.openstack.org
07:39:34 <ianychoi> eumel8, by the way, how do you test zanata-cli on translate-dev? Using scripts in openstack-infra or something other ways?
07:40:03 <eumel8> so in translate-dev are definitly ssl issues
07:41:46 <eumel8> for me it's not a blocker for an upgrade now. If the strict host feature will not work on live, we could change the DNS to A record. Because we have only translate91 and no more other hosts.
07:42:27 <eumel8> ianychoi: using zanata-cli standalone and then push/pull content
07:43:13 <ianychoi> Hmm, okay then eumel8 would u ask this to infra team during PTG? I don't know how .openstack.org dns names are managed.
07:43:29 <ianychoi> If infra team can manage this, then it would not be a main blocker I think.
07:45:15 <eumel8> if zanata upgrade goes through most of the experts will be on-site ;)
07:46:02 <eumel8> but maybe zanata team has an answer in https://zanata.atlassian.net/browse/ZNTA-1757
07:47:42 <eumel8> so, a little bit offtopic. I would initiate the live upgrade next week but not focus during PTG. This comes from my experience with translation check site last PTG
07:48:04 <eumel8> better focus on topics which are makeable
07:48:14 <eumel8> next topic? 12 min left
07:48:49 <ianychoi> Nope
07:49:30 <amotoki> horizon RC2 was released yesterday
07:49:35 <eumel8> #topic Queens release
07:49:43 <amotoki> neutron-fwaas/vpnaas-dashboard will be released today or tomorrow.
07:50:06 <eumel8> #link https://review.openstack.org/#/q/topic:translation-jobs-queens+(status:open+OR+status:merged)
07:50:07 <amotoki> I don't know other horizon plugins plan another release or not.
07:50:18 <jftalta> hi!
07:50:28 <eumel8> hi jftalta
07:50:34 <ianychoi> hi jftalta !
07:51:49 <eumel8> amotoki: that's still the question. I investigated dev mailing list + repos for new branches in different repos but it's time intensive to find out what will happen.
07:51:51 <jftalta> eumel8 : thanks for the check site, it's very helpful :-)
07:52:35 <eumel8> jftalta: great! customer feedback :)
07:52:59 <amotoki> eumel8: I coordinated horizon plugin releases in the past but I am no longer doing it. it's time consuming.
07:53:57 <amotoki> some projects do not extract all strings properly due to misconfiguration of babel-django.cfg like https://review.openstack.org/#/c/540908/
07:54:30 <amotoki> unfortunately manila-ui failed to land in time, so we cannot translate some?many? strings.
07:56:59 <eumel8> amotoki: I would try to automate such things with branching in Zanata. Maybe a nightly job that checks source repos for new branches, configure this in Zanata and send proposal to gerrit
07:57:53 <amotoki> eumel8: that should work
07:58:03 <eumel8> alright, 2 min left for discussion
07:58:04 <eumel8> #topic Open Discussion
07:58:06 <amotoki> eumel8: my comment is about tracking horizon plugin releases.
07:58:49 <amotoki> ideally it is better to encourage their maintainers to release it for translations
07:59:08 <amotoki> but unfortunately not all maintainers does not understand this.
07:59:38 <eumel8> amotoki: sure, but that doesn't worked in the last weeks. Maybe also a topic for PTG
07:59:40 <amotoki> it is a communication problem, but as of now I do not have a good idea to address this easily
08:00:11 <eumel8> so, time is over. thanks for participating. Not sure, if we make a meeting next week or better the week after
08:00:23 <eumel8> #endmeeting