- OpenStack-I18n - lists.openstack.org

What's Up, Doc? Holiday Edition!
by Lana Brindley 01 Dec '16

01 Dec '16

Hi everyone, The end of the year is nearly upon us already, and this will be my last newsletter for 2016, before I disappear for the holidays on the 16th. I've had yet another wonderful year with all you lovely OpenStack people, and I wish all of you and your families a happy and safe holiday, wherever and however you celebrate it. Here in Australia, the temperature is starting to soar, so I'm off on another cruise, followed by a few lazy days by the pool with family and friends. I'll be back in the office early in the new year, and ready to kick Ocata out of the door! As many of you already know, I'm not planning on running for Pike PTL. If you're interested in running for PTL (for Pike or any future release), and would like a crash course in PTLing, please let me know and I can share whatever meagre wisdom I've gleaned before self nominations open in mid-January. == Progress towards Ocata == 82 days to go! Closed 106 bugs so far. Release tasks are being tracked here: https://wiki.openstack.org/wiki/Documentation/OcataDeliverables == The Road to PTG in Atlanta == Event info is available here: http://www.openstack.org/ptg Purchase tickets here: https://pikeptg.eventbrite.com/ Docs is a horizontal project, so our sessions will run across the Monday and Tuesday of the event. The incoming PTL will be responsible for planning and running sessions at the Atlanta PTG. == Speciality Team Reports == * API: Anne Gentle The App Dev Support WG is working on a survey to determine which content areas to invest in for content on http://www.openstack.org/appdev (http://lists.openstack.org/pipermail/user-committee/2016-November/001469.ht…) * Configuration Reference and CLI Reference: Tomoyuki Kato We try to recreating the single page view for the "openstack" command. I'd like to generate the reference from source code automatically. However, python-openstackclient has many plug-ins. It is difficulty, but worth to tackle it. We need your help! * High Availability Guide: Andrew Beekhof No formal report, but Alex Settle has been doing a lot of work on this guide recently, cleaning up, and raising bugs for some of the TODO items. We need to consider if the HA guide is an ongoing concern. Ben Silverman is wondering if we can fold the content into the Ops/Arch Guides. This will be raised on the mailing list for more conversation. * Hypervisor Tuning Guide: Joe Topjian No report this week * Installation guides: Lana Brindley We've heard back from Foundation on design resources, I'm going to reply to that email today and hopefully start drafting the new design next week. I've also got Piet from the UX team on board to help. Anyone who wants to be involved with that, please contact me. * Networking Guide: John Davidge No update this week. * Operations and Architecture Design guides: Darren Chan For the Arch guide, patches for networking and compute content were merged, thanks to Ben and Shaun. For the Ops Guide, there is patch up to update the upgrades chapter and include links to the project upgrade notes: https://review.openstack.org/#/c/404528/ * Security Guide: Nathaniel Dillon No update this week. * Training Guides: Matjaz Pancur BCN Upstream training article in the Superuser magazine: http://superuser.openstack.org/articles/openstack-upstream-training-revamp/ - actively looking for contributors to join the Upstream training, please see http://lists.openstack.org/pipermail/openstack-docs/2016-November/009382.ht… - cleaned test entries in the Launchpad bug queue and the Sandbox repository (left from the Barcelona Upstream training) - updated Training guides README.rst * Training labs: Pranav Salunke, Roger Luethi No update this week. * User guides: Joseph Robinson The legacy command conversion continues at a good pace. I have some more updates to patch today. The only obstacle I have run into is generating new output to match the OpenStack command client. Otherwise, contributors have been adding to the table, and there's been steady patching completed. Just a reminder to update the table if making a change: https://wiki.openstack.org/wiki/Documentation/ReorganizeUserGuides == Doc team meeting == Our next meeting will be on Thursday 16 December at 2100 UTC in #openstack-meeting-alt For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting -- Keep on doc'ing! Lana https://wiki.openstack.org/wiki/Documentation/WhatsUpDoc#1_December_2016 -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

1 0

Re: [OpenStack-I18n] Adding Romanian Language Team
by Ian Y. Choi 01 Dec '16

01 Dec '16

Hello Cristian, Sorry for my late reply. I am copying with openstack-i18n(a)lists.openstack.org to keep track of your request. (Note: I always try to read all of my e-mails but since I receive too much e-mails in my account these days, I usually check http://lists.openstack.org/pipermail/openstack-i18n/ for faster responses from openstack-i18n(a)lists.openstack.org.) Cristian Cira wrote on 11/17/2016 11:34 PM: > Hello Ian, > > Nice to meet you too! > > * I have registered to the mailing list > * It is not clear to me what is the difference between the two > encoding. I searched the net for some documentation but failed to > find one that points out the difference -maybe you could point me > to a better source. If my understanding is correct (namely that > the second one includes "somehow" a geographical component in the > characters encoding ) then I would opt for "ro" to keep it as > general as possible since there are few differences in the > Romanian dialects from various regions > Personally, I have been to Romania about 10 years ago shortly (about less than 4 weeks in Bucharest), but I do not have enough knowledge to judge between ro vs. ro-RO. Now I want to follow your decision: "ro". Thanks. > > * I will accept to be a coordinator with some hesitation. This > coordinator position must come with some extra responsibility > which is totally fine with. My concern regards the time I have to > dedicate to this activity. So, as long as I do not have to > officially commit a certain amount of hours to it, I am more then > happy to help translate. Also, I feel confident that I can find > some extra contributors, maybe even better suited for this > position then me. > That's fine. At least, I am not a full-time translator for OpenStack :) > * Also, could you please point me to a place where I can as question > related to how should I approach this task. Surely there are some > more important parts of the documentation that would need to be > tackled first. > Would you read first http://docs.openstack.org/developer/i18n/ ? Then please let me know which points you would like to know or ask. I will follow Romanian language support in Zanata after I18n IRC meeting on this Thursday 13:00 UTC ( http://eavesdrop.openstack.org/#I18N_Team_Meeting ). If you attend to this meeting, I think it will be very nice to talk each other. With many thanks, /Ian > > * > > > Thank you for your time. Have a lovely day, > ~cira > > On Thu, Nov 17, 2016 at 4:53 AM Ian Y. Choi <ianyrchoi(a)gmail.com > <mailto:ianyrchoi@gmail.com>> wrote: > > Hello Cristian, > > I am Ian. Nice to meet you! > > I think adding the support for Romanian language is possible in > Zanata :) > > Before going further, I want to ask you: > > - Please subscribe openstack-i18n(a)lists.openstack.org > <mailto:openstack-i18n@lists.openstack.org> mailing list through > : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > - For Romanian language, I want to ask you which ISO language code > is preferred > : "ro" vs. "ro-RO". > > - Are you willing to be a Romanian language coordinator in i18n team? > Since there is no Romanian translator currently, I want to > assign you as Romanian language coordinator. > As a language coordinator, it would be much better if you will > encourage more Romanian translations > to others, tell PTL (currently, me) for any updates, and share > or ask anything regarding i18n related things > through I18n IRC meeting > http://eavesdrop.openstack.org/#I18N_Team_Meeting or this mailing > list. > > > With many thanks, > > /Ian > > > Cristian Cira (KTH-PDC) wrote on 11/16/2016 4:26 AM: >> Dear all, >> >> I have recently decided to contribute to the translation of the >> OpenStack documentation to Romanian in my limited free time. >> >> I am a native Romanian currently working in Sweden at a HPC >> center. My English is proficient having studied and worked in USA >> for 5 years prior to moving here. Here is my LinkedIn >> <https://se.linkedin.com/in/cristian-cira-246b0933> account for >> some more details. >> >> My username on Zanata is *cira* >> * >> *Please let me know what are the next steps I have to take. >> >> Thank you, >> C >> >> *Cristian Cira,*PhD >> Application Expert in Code Optimization >> *PDC Center for High Performance Computing* >> KTH Royal Institute of Technology >> SE-100 44 Stockholm, Sweden >> *http://www.pdc.kth.se >> * >> Tel : +46 8 790 6309 <tel:08-790%2063%2009> >> Mob : +46 737 65 22 98 >> >> >> _______________________________________________ >> OpenStack-I18n mailing list >> OpenStack-I18n(a)lists.openstack.org >> <mailto:OpenStack-I18n@lists.openstack.org> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > > > -- > *Cristian Cira,* PhD > Application Expert in Code Optimization > *PDC Center for High Performance Computing* > KTH Royal Institute of Technology > SE-100 44 Stockholm, Sweden > *http://www.pdc.kth.se > * > Tel : +46 8 790 6309 > Mob : +46 737 65 22 98

2 2

[I18n] IRC Meeting remainder: November 3rd at 07:00 UTC
by Ian Y. Choi 30 Nov '16

30 Nov '16

Hello all, I18n team is having our next meeting on November 3rd (Thursday) at 07:00 UTC in #openstack-meeting IRC channel. You can find meeting agenda here: https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting#Agenda_for_next_me… Anyone is welcome to add topics on Wiki If you missed previous IRC meeting or want to refresh, please see i18n Barcelona contributor meetup summary on Etherpad (URL: https://etherpad.openstack.org/p/barcelona-i18n-meetup ), last IRC meeting minutes and full logs: Minutes: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2016/opensta… With many thanks, /Ian

2 4

searchlight-ui: Broken cs translation / neutron-lbaas-dashboard: broken ja translation
by Andreas Jaeger 24 Nov '16

24 Nov '16

Could somebody check and fix these, please? http://logs.openstack.org/periodic/searchlight-ui-propose-translation-updat… searchlight_ui/locale/cs/LC_MESSAGES/djangojs.po:789: number of format specifications in 'msgid_plural' and 'msgstr[2]' does not match http://logs.openstack.org/periodic/neutron-lbaas-dashboard-propose-translat… neutron_lbaas_dashboard/locale/ja/LC_MESSAGES/djangojs.po:1092: '\''msgid'\'' and '\''msgstr'\'' entries do not both end with '\''\n'\'' Andreas -- Andreas Jaeger aj(a){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

2 1

[Bug 1641785] [NEW] 环境 in Installation Guide 镜像服务写成了径向服务
by jeck 20 Nov '16

20 Nov '16

Public bug reported: 拼写错误 ----------------------------------- Release: 0.1 on 2016-11-13 23:16 SHA: 5a9c47b83b0209892f887697bb9e8bb871eee8a3 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/environment.html ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1641785 Title: 环境 in Installation Guide 镜像服务写成了径向服务 Status in openstack i18n: New Bug description: 拼写错误 ----------------------------------- Release: 0.1 on 2016-11-13 23:16 SHA: 5a9c47b83b0209892f887697bb9e8bb871eee8a3 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/environment.html To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1641785/+subscriptions

1 1

[Bug 1489311] Re: Chinese words in translations are incorrect
by Ian Y. Choi 20 Nov '16

20 Nov '16

I have found that Zanata now has a fixed string for this bug report: http://git.openstack.org/cgit/openstack/openstack- manuals/tree/doc/common/source/locale/zh_CN/LC_MESSAGES/common.po#n1145 ** Changed in: openstack-i18n Status: Confirmed => Fix Released -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1489311 Title: Chinese words in translations are incorrect Status in openstack i18n: Fix Released Bug description: I found there are mistakes of Chinese words in translations. Details: In source file: https://github.com/openstack/openstack-manuals/blob/master/doc/common/local… there are two places as follow: 1: L413 "<emphasis>用户不可以想传统的硬盘那样使用OpenStack对象存储。</emphasis>对象存" "用户不可以想传统的硬盘" should be "用户不可以像传统的硬盘". 2: L736 msgid "Access associated with a VM" L737 msgstr "访问和VM想关联" "访问和VM想关联" should be "访问和VM相关联". To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1489311/+subscriptions

1 0

[Bug 1612201] [NEW] Some strings which needn't translation appear in Zanata
by zzxwill 20 Nov '16

20 Nov '16

Public bug reported: In Zanata, document 'doc/admin-guide/source/locale/admin-guide' of openstack-manuals, some strings like 'vm2', 'doc/admin- guide/source/locale/admin-guide', 'd693db9e-a7cf-45ef-a7c9-b3ecb5f22645' are waiting for translation, while, which don't need to be translated. I think there should be a way to stop them from being shown in Zanata. Thanks. ** Affects: openstack-i18n Importance: Undecided Status: New -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1612201 Title: Some strings which needn't translation appear in Zanata Status in openstack i18n: New Bug description: In Zanata, document 'doc/admin-guide/source/locale/admin-guide' of openstack-manuals, some strings like 'vm2', 'doc/admin- guide/source/locale/admin-guide', 'd693db9e-a7cf-45ef- a7c9-b3ecb5f22645' are waiting for translation, while, which don't need to be translated. I think there should be a way to stop them from being shown in Zanata. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1612201/+subscriptions

2 1

[Bug 1612878] Re: 安装和配置 in Installation Guide
by Ian Y. Choi 20 Nov '16

20 Nov '16

"controller" vs. "10.0.0.11" is not the target of I18n team. ** Changed in: openstack-i18n Status: New => Invalid ** Tags added: simplified-chinese -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1612878 Title: 安装和配置 in Installation Guide Status in openstack i18n: Invalid Bug description: ----------------------------------- Release: 0.1 on 2016-08-12 08:52 SHA: 739d8d9e6cb81a10aca0068e5ba1b76541b0398d Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/horizon-install… 在memcached里，/etc/memcached.conf 如果-l是controller -l controller 那么在/etc/openstack-dashboard/local_settings.py这个里面也应该是controller CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': 'controller:11211', } } 否则在登录dashboard的时候，能出现登录的页面，登录不成功。如果都写IP地址，也是可以成功。在memcached里，/etc/memcached.conf 如果-l是10.0.0.11 -l 10.0.0.11 那么在/etc/openstack-dashboard/local_settings.py这个里面也应该是10.0.0.11 CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': '10.0.0.11:11211', } } 这样才能成功。 To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1612878/+subscriptions

1 0

[Bug 1637920] [NEW] 网络选项2：私有网络配置Linuxbridge代理中[linux_bridge]部分应为 physical_interface_mappings = provider:PUBLIC_INTERFACE_NAME
by gavin 20 Nov '16

20 Nov '16

Public bug reported: section of PUBLIC_INTERFACE_NAME ----------------------------------- Release: 0.1 on 2016-10-30 16:22 SHA: 0aec93ae3cabb0ba77ca4a0a2498b5dcaf454984 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/neutron-controller… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide -- You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n. https://bugs.launchpad.net/bugs/1637920 Title: 网络选项2：私有网络配置Linuxbridge代理中[linux_bridge]部分应为 physical_interface_mappings = provider:PUBLIC_INTERFACE_NAME Status in openstack i18n: New Bug description: section of PUBLIC_INTERFACE_NAME ----------------------------------- Release: 0.1 on 2016-10-30 16:22 SHA: 0aec93ae3cabb0ba77ca4a0a2498b5dcaf454984 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: http://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/neutron-controller… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1637920/+subscriptions

2 1

Re: [OpenStack-I18n] [OpenStack-docs] stable/newton created, publishing frozen for now
by Ian Y. Choi 20 Nov '16

20 Nov '16

Hello, Andreas Jaeger wrote on 11/13/2016 3:52 AM: > On 11/12/2016 07:18 PM, Andreas Jaeger wrote: >> Clark just created a stable/newton branch. >> >> I'll create the changes now for both master and stable so that >> publishing is correct. >> >> Please do not approve any changes until those are in. >> >> I'll sent in a few minutes an email with links to those changes for >> review, > > The changes that need to merge are: > > https://review.openstack.org/396874 > https://review.openstack.org/396875 > > In addition: > * stable-newton needs to be created on zanata (i18n team) Zanata now has a stable-newton version for openstack-manuals, and this version can be seen in https://translate.openstack.org/project/view/openstack-manuals and https://translate.openstack.org/iteration/view/openstack-manuals/stable-new… . i18n team will translate backported guides (common, install-guide, networking-guide) in stable-newton instead of master for translation plan and priority during Ocata cycle. Thank you all kind help and communication, especially Andreas and Olena! With many thanks, /Ian > * import of newton translations: https://review.openstack.org/396876 > * Documentation for the above: https://review.openstack.org/396877 > > Please review everything and help updating these if I missed anything, > I really like to have this properly documented so that the release > managers can do it next time, > > Andreas

1 1