- OpenStack-I18n - lists.openstack.org

Translation bugs on Chinese China
by Akihiro Motoki 04 Aug '17

04 Aug '17

Hi Chinese language coordinator and translators, We received several number of bug reports on Chinese China translations, but unlike other languages they have not been triaged and fixed. 9 of 13 open bugs looks related to Chinese China. Can anyone from Chinese China handle these bugs? Check bugs on https://bugs.launchpad.net/openstack-i18n Unless we have good volunteers, we cannot handle translated bugs. Thanks, amotoki

2 1

[Bug 1586041] [NEW] Incorrect PO-Revision-Date in some translation files for aodh project
by Alfredo Moralejo 03 Aug '17

03 Aug '17

Public bug reported: Following .po files have empty revision date, "PO-Revision-Date: \n": aodh/locale/it/LC_MESSAGES/aodh.po aodh/locale/pt_BR/LC_MESSAGES/aodh.po aodh/locale/zh_CN/LC_MESSAGES/aodh-log-info.po aodh/locale/zh_CN/LC_MESSAGES/aodh.po aodh/locale/zh_TW/LC_MESSAGES/aodh.po This makes compile_catalog to fail: $ python setup.py compile_catalog running compile_catalog compiling catalog aodh/locale/ja/LC_MESSAGES/aodh.po to aodh/locale/ja/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/ru/LC_MESSAGES/aodh.po to aodh/locale/ru/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/pt/LC_MESSAGES/aodh.po to aodh/locale/pt/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/en_GB/LC_MESSAGES/aodh.po to aodh/locale/en_GB/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/ko_KR/LC_MESSAGES/aodh.po to aodh/locale/ko_KR/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/de/LC_MESSAGES/aodh.po to aodh/locale/de/LC_MESSAGES/aodh.mo Traceback (most recent call last): File "setup.py", line 29, in <module> pbr=True) File "/usr/lib64/python2.7/distutils/core.py", line 151, in setup dist.run_commands() File "/usr/lib64/python2.7/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/frontend.py", line 178, in run self._run_domain(domain) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/frontend.py", line 218, in _run_domain catalog = read_po(infile, locale) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/pofile.py", line 217, in read_po _add_message() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/pofile.py", line 165, in _add_message catalog[msgid] = message File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 601, in __setitem__ self.mime_headers = _parse_header(message.string).items() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 420, in _set_mime_headers self.revision_date = _parse_datetime_header(value) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 46, in _parse_datetime_header tt = time.strptime(match.group('datetime'), '%Y-%m-%d %H:%M') File "/usr/lib64/python2.7/_strptime.py", line 467, in _strptime_time return _strptime(data_string, format)[0] File "/usr/lib64/python2.7/_strptime.py", line 325, in _strptime (data_string, format)) ValueError: time data u'' does not match format '%Y-%m-%d %H:%M' I've checked in https://translate.openstack.org that files are wrong there too, not only in github. ** 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/1586041 Title: Incorrect PO-Revision-Date in some translation files for aodh project Status in openstack i18n: New Bug description: Following .po files have empty revision date, "PO-Revision-Date: \n": aodh/locale/it/LC_MESSAGES/aodh.po aodh/locale/pt_BR/LC_MESSAGES/aodh.po aodh/locale/zh_CN/LC_MESSAGES/aodh-log-info.po aodh/locale/zh_CN/LC_MESSAGES/aodh.po aodh/locale/zh_TW/LC_MESSAGES/aodh.po This makes compile_catalog to fail: $ python setup.py compile_catalog running compile_catalog compiling catalog aodh/locale/ja/LC_MESSAGES/aodh.po to aodh/locale/ja/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/ru/LC_MESSAGES/aodh.po to aodh/locale/ru/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/pt/LC_MESSAGES/aodh.po to aodh/locale/pt/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/en_GB/LC_MESSAGES/aodh.po to aodh/locale/en_GB/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/ko_KR/LC_MESSAGES/aodh.po to aodh/locale/ko_KR/LC_MESSAGES/aodh.mo compiling catalog aodh/locale/de/LC_MESSAGES/aodh.po to aodh/locale/de/LC_MESSAGES/aodh.mo Traceback (most recent call last): File "setup.py", line 29, in <module> pbr=True) File "/usr/lib64/python2.7/distutils/core.py", line 151, in setup dist.run_commands() File "/usr/lib64/python2.7/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/frontend.py", line 178, in run self._run_domain(domain) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/frontend.py", line 218, in _run_domain catalog = read_po(infile, locale) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/pofile.py", line 217, in read_po _add_message() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/pofile.py", line 165, in _add_message catalog[msgid] = message File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 601, in __setitem__ self.mime_headers = _parse_header(message.string).items() File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 420, in _set_mime_headers self.revision_date = _parse_datetime_header(value) File "/home/amoralej/eng/babel/lib/python2.7/site-packages/babel/messages/catalog.py", line 46, in _parse_datetime_header tt = time.strptime(match.group('datetime'), '%Y-%m-%d %H:%M') File "/usr/lib64/python2.7/_strptime.py", line 467, in _strptime_time return _strptime(data_string, format)[0] File "/usr/lib64/python2.7/_strptime.py", line 325, in _strptime (data_string, format)) ValueError: time data u'' does not match format '%Y-%m-%d %H:%M' I've checked in https://translate.openstack.org that files are wrong there too, not only in github. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1586041/+subscriptions

2 1

Re: [OpenStack-I18n] IMPORTANT upcoming change to technical elections
by Jeremy Stanley 03 Aug '17

03 Aug '17

I just posted an announcement to openstack-dev which is also relevant to some subscribers of this ML who may not see it there: http://lists.openstack.org/pipermail/openstack-dev/2017-July/119786.html If possible, please follow up there with any questions. -- Jeremy Stanley

1 1

Re: [OpenStack-I18n] [openstack-dev] string freeze exception for VMAX driver
by Akihiro Motoki 03 Aug '17

03 Aug '17

I am not sure who is responsible to respond to string freeze exception, but I will comment it as my hat of the i18n team. Looking at "cinder" translation status [1], the best progress is ~73% and 718 of 2932 message are remaining. In other languages the progress is lower. Adding two new messages does not matter. Removing messages has no problem. I see no blocking issue in this request. In addition, I think the i18n team focuses on dashboard translations and server projects are less focused for translations. IIRC the I18n team discussed an idea to announce the i18n team focus on translation to let server projects be free from string freeze around the beginning of the Pike cycle but I am not sure it is announced or not. Thanks, Akihiro [1] https://translate.openstack.org/iteration/view/cinder/master/documents?docI… 2017-08-03 3:14 GMT+09:00 Walsh, Helen <Helen.Walsh(a)dell.com>: > > > > > To whom it may concern, > > > > I would like to request a string freeze exception for 2 patches that are on > the merge queue for Pike. > > > > 1. VMAX driver - align VMAX QOS settings with front end (CI Passed) > > https://review.openstack.org/#/c/484885/7/cinder/volume/drivers/dell_emc/vm… > line 800 (removal of exception message) > > > > Although it’s primary aim is to align QoS with front end setting it > indirectly fixes a lazy loading error we were seeing around QoS which > occasionally > > Broke CI on previous patches. > > > > > > 2. VMAX driver - seamless upgrade from SMI-S to REST (CI Pending) > > https://review.openstack.org/#/c/482138/19/cinder/volume/drivers/dell_emc/v… > line 1400 ,1455 (message changes) > > > > This is vital for as reuse of volumes from Ocata to Pike. In Ocata we used > SMIS to interface with the VMAX, in Pike we are using REST. A few changes > needed to be made to make this transition as seamless as possible. > > > > Thank you, > > Helen > > > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >

1 0

Re: [OpenStack-I18n] [OpenStack-docs] Summary of how I18n affects with doc-migration
by Doug Hellmann 02 Aug '17

02 Aug '17

[resending to the lists] > On Aug 1, 2017, at 10:55 AM, Doug Hellmann <doug(a)doughellmann.com> wrote: > > Excerpts from Andreas Jaeger's message of 2017-08-01 08:57:09 +0200: >> On 2017-07-31 22:46, Doug Hellmann wrote: >>> Excerpts from Ian Y. Choi's message of 2017-08-01 03:16:09 +0900: >>>> [...] >>>> 2. Draft index page for translated documents was also removed >>>> >>>> Previously, Docs team maintained draft documents for the master branch >>>> (which will be the stable branch >>>> after the official release and the document stables) on >>>> https://docs.openstack.org/draft/draft-index.html page. >>>> It also contained translated draft documents and I18n team accessed the >>>> page to see whether translated documents >>>> render well or not, and also review translated strings. >>>> >>>> I did not notice when I saw the spec [1], but recently, I noticed that >>>> the the draft-index.html page was deprecated >>>> by [next-release-name]/index.haml (e.g., >>>> https://docs.openstack.org/pike/index.html ) [4]. >>>> >>>> Since I18n team encourages translation review for the better quality of >>>> translations, it is a good idea to see >>>> draft documents before language landing pages have the link to fully >>>> translated and reviewed documents. >>> >>> Is it possible to see the draft of a translation by reviewing the >>> output of the job that proposes the patch containing the translated >>> text? >> >> Currently not, it needs publishing to docs-draft and a way to access the >> multiple documents. Note this needs handling for both openstack-manuals >> and project repos like neutron (networking-guide). > > Could we make it work that way? I understand why we need a separate > review step for the translations, but not why we need a separate > copy of the docs published outside of the context of a job in order > to perform that review. (This is probably just me not understanding > how a tool works.) > >> >>>> Motoki-san proposed an idea of translation status support using an yaml >>>> file in openstack-manuals [5], >>>> and I would like to discuss with I18n team how we deal with the change >>>> of draft index page. >>> >>> How would that flag or information be used? >>> >> >> WE could just have the link to it added - dependent on the flag - to either: >> * language index >> * draft index > > It seems like we want a list of languages for which there are > translations for a given set of docs. We could use that to populate > templates in a few different ways (link from the English version > to the other languages, link from a $language landing page to all > of the guides in that language, etc.). > > I can advise someone on how to add those features, if we have a > volunteer. > > Doug

3 4

[StringFreeze] Soft period was over - Plz contribute translation for the release!
by Ian Y. Choi 02 Aug '17

02 Aug '17

Dear language coordinators & translators! Only a few weeks left before official Pike release [1] and I would like to inform you that the last week was the Soft StringFreeze period. Language teams need to focus on Horizon and Horizon-related projects before all translated strings will be packaged for upcoming release. According to the dashboard on https://translate.openstack.org, our targeted priorities look as follows: - Dashboard - Horizon (High) - Dashboard Authorization Page (High) - Magnum UI (Medium) - Trove Dashboard (Medium) - Sahara Dashboard (Medium) - neutron-lbaas-dashboard (Medium) - Murano Dashboard (Low) - Designate Dashboard (Low) - TripleO UI (Low) All of those and more additional target projects grouped in [2] in *master* branch and current & next PTL will check feature freeze status on projects listed above. He will create a stable version: *stable-pike* in Zanata for the target projects after the project have stable/pike branch. Although the stable version has not been created yet, but it is highly encouraged to translate those projects from now, since StringFreeze periods are relatively short (about 2 weeks of RC1, then HardStringFreeze). For more details on how I18n team is doing with releases (especially Horizon & plugin projects), please see [3]. If you have questions, feel free to ask through openstack-i18n at lists.openstack.org mailing list or ask I18n members on Freenode #openstack-i18n channel. Thank you all for your contribution! [1] https://releases.openstack.org/pike/schedule.html [2] https://translate.openstack.org/version-group/view/pike-dashboard-translati… [3] https://docs.openstack.org/i18n/latest/release_management.html With many thanks, /Ian

4 3

French member with no role
by Akihiro Motoki 02 Aug '17

02 Aug '17

Hi French team coordinators, I see one member in French language team has no role. What does this mean? Is he considered as a translator? This is just a question and to clarify the situation. I see a warning every time I run a script to sync Zanata users list into the i18n repo. Thanks, Akihiro

2 3

[Elections] Candidacy for I18n PTL (Queens)
by Frank Kloeker 02 Aug '17

02 Aug '17

Good morning! Today I would like to announce my candidacy as I18n PTL in Queens cycle. I've been in the OpenStack Community since 2015, active as a translator in the German team. I participated in my first OpenStack Summit in Tokyo and met the I18n team for the first time at the Design Summit. It was an exciting moment to meet people from all over the world working on the same thing. It is not just translations, but working with different cultures, views and ... time zones. These are the magical dimensions and challenges. After Tokyo we had virtual midcycle sprint to develop the translation check site, one of the tools to help translators in their work. I met more people during Barcelona Summit and sank deeper and deeper into the work of OpenStack and I18n. In Boston we had our own session to show the work of the I18n team. We prepared a workshop also which was not so successful, but the preparation was great and we can repeat it at any time. At this point I would like to thank Ianychoi for his excellent work in the past as PTL. He is tireless, full of energy, and brought I18n far forward. He was for me in the last weeks a kind of mentor to learn all the things related to I18n and PTL. Nevertheless, I still need support from the entire team to successfully manage this task. What goals have I set for myself for Queens: 1. Completion of the translation check site. I have been involved in this project since 2015 and now it has to be finished :-) 2. Automate all the things. We have some manual work in I18n and our tools that are to automate to make the work easier. 3. Aquire more people to the team. We have great teams that do a lot. But we also get more work through translate new OpenStack projects or the User Survey. I hope I have given a good overview. Contact me directly if you have any questions or requests. On good cooperation in a new cycle of OpenStack! kind regards Frank Email: eumel(a)arcor.de IRC: eumel8 Twitter: eumel_8 OpenStack Profile: https://www.openstack.org/community/members/profile/45058/frank-kloeker

2 1

Re: [OpenStack-I18n] [OpenStack-docs] Summary of how I18n affects with doc-migration
by Andreas Jaeger 01 Aug '17

01 Aug '17

On 2017-07-31 22:46, Doug Hellmann wrote: > [...] > This is good to know. I am going to need someone who knows how the > translation jobs work to help set those up. I can assist, but I do not > know how they work so I cannot lead that effort. Doug, I'm happy to have a discussion with you - and anybody else - on these. We can do a special IRC session or some kind of videochat. Who else wants to join? Once I know participants, let's set up something... 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

Re: [OpenStack-I18n] [OpenStack-docs] Summary of how I18n affects with doc-migration
by Andreas Jaeger 01 Aug '17

01 Aug '17

On 2017-07-31 22:46, Doug Hellmann wrote: > Excerpts from Ian Y. Choi's message of 2017-08-01 03:16:09 +0900: >> [...] >> 2. Draft index page for translated documents was also removed >> >> Previously, Docs team maintained draft documents for the master branch >> (which will be the stable branch >> after the official release and the document stables) on >> https://docs.openstack.org/draft/draft-index.html page. >> It also contained translated draft documents and I18n team accessed the >> page to see whether translated documents >> render well or not, and also review translated strings. >> >> I did not notice when I saw the spec [1], but recently, I noticed that >> the the draft-index.html page was deprecated >> by [next-release-name]/index.haml (e.g., >> https://docs.openstack.org/pike/index.html ) [4]. >> >> Since I18n team encourages translation review for the better quality of >> translations, it is a good idea to see >> draft documents before language landing pages have the link to fully >> translated and reviewed documents. > > Is it possible to see the draft of a translation by reviewing the > output of the job that proposes the patch containing the translated > text? Currently not, it needs publishing to docs-draft and a way to access the multiple documents. Note this needs handling for both openstack-manuals and project repos like neutron (networking-guide). >> Motoki-san proposed an idea of translation status support using an yaml >> file in openstack-manuals [5], >> and I would like to discuss with I18n team how we deal with the change >> of draft index page. > > How would that flag or information be used? > WE could just have the link to it added - dependent on the flag - to either: * language index * draft index 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

1 0

Summary of how I18n affects with doc-migration
by Ian Y. Choi 01 Aug '17

01 Aug '17

Hello translators, The OpenStack manuals project migration [1] has been going well, and I would like to share what I have found which things influence on I18n activities from the perspective of translators, since some translators asked me about missing some openstack-manuals documents in Zanata. 1. Removal of documents in openstack-manuals project in Zanata In [2], the following documents are not currently visible : admin-guide, arch-design, networking-guide, ops-guide, user-guide . For several release cycles, there have been less amount contribution on admin-guide (migrating to each project tree) and arch-design (deprecated). For networking-guide, translating in stable-ocata will be preserved, but master version was removed and the content will be migrated into neutron repository. User-guide will be migrated and divided between the horizon repository and python-openstackclient repository. If the strings for the migrated projects (admin-guide, networking-guide, and user-guide) would be the same as the removed strings in openstack-manuals, I18n team expects that translation memory merge functionality in Zanata would be able to fill out translations for the migrated projects. Note that the translation support work of migrated documents will be started after the migration completes and I18n team need volunteers for the work. 2. Draft index page for translated documents was also removed Previously, Docs team maintained draft documents for the master branch (which will be the stable branch after the official release and the document stables) on https://docs.openstack.org/draft/draft-index.html page. It also contained translated draft documents and I18n team accessed the page to see whether translated documents render well or not, and also review translated strings. I did not notice when I saw the spec [1], but recently, I noticed that the the draft-index.html page was deprecated by [next-release-name]/index.haml (e.g., https://docs.openstack.org/pike/index.html ) [4]. Since I18n team encourages translation review for the better quality of translations, it is a good idea to see draft documents before language landing pages have the link to fully translated and reviewed documents. Motoki-san proposed an idea of translation status support using an yaml file in openstack-manuals [5], and I would like to discuss with I18n team how we deal with the change of draft index page. 3. Archiving translated documents is also needed Liberty translated documents (e.g., [6]) and translated documents which were migrated (e.g., [7], [8]) are still accessible through docs.o.o. In my opinion, those translated documents are also the target of archiving documents [9]. For translated documents, I think just publishing htmls as read-only (e.g., github pages?) would be fine, and the work needs volunteers. With many thanks, /Ian [1] http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migra… [2] https://translate.openstack.org/iteration/view/openstack-manuals/master/doc… [3] https://translate.openstack.org/iteration/view/openstack-manuals/stable-oca… [4] https://docs.openstack.org/pike/index.html [5] http://git.openstack.org/cgit/openstack/openstack-manuals/tree/www/project-… [6] https://docs.openstack.org/liberty/ko_KR/install-guide-ubuntu/ [7] https://docs.openstack.org/ja/user-guide/ [8] https://docs.openstack.org/ja/ops-guide/ [9] http://specs.openstack.org/openstack/docs-specs/specs/pike/archiving.html [10] https://etherpad.openstack.org/p/denver-doc-PTG

2 1

[I18n] Denver PTG Planning
by Ian Y. Choi 31 Jul '17

31 Jul '17

Hello, PTG (Project Team Gathering) is also important for I18n team to meet upstream project developers in person to discuss priorities for the upcoming cycle, iterate quickly on solutions for complex issues, and make fast progress on critical items with many horizontal projects, and also better internationalize to vertical projects with discussion. I have created an Etherpad for I18n team planning on next Denver PTG. Please share your idea on the Etherpad: https://etherpad.openstack.org/p/denver-i18n-PTG . I really wanted to go to Denver PTG to discuss more I18n issues with many cross project teams including Docs, Infra, Release Mgmt., and also find how more projects would be able to better internationalized with the discussion of many project team members. However, due to my busy life with my new job, I unfortunately am not able to attend to the next PTG. Hope that I18n people will go to the PTG, and meet upstream project developers with interesting topics. Note that the due of PTG travel support application is by August 6th. With many thanks, /Ian

1 0

[Bug 1659349] [NEW] [French] Delete instance translated incorrectly
by Mateusz Kowalski 30 Jul '17

30 Jul '17

Public bug reported: In French version "Delete Instance" in Horizon interface is translated as "Supprimer le l'instance" for the singular form, whereas the correct one is "Supprimer l'instance". ** 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/1659349 Title: [French] Delete instance translated incorrectly Status in openstack i18n: New Bug description: In French version "Delete Instance" in Horizon interface is translated as "Supprimer le l'instance" for the singular form, whereas the correct one is "Supprimer l'instance". To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1659349/+subscriptions

2 1

[Bug 1671367] Re: Losing a semicolon in overview page
by Akihiro Motoki 30 Jul '17

30 Jul '17

** No longer affects: horizon ** 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/1671367 Title: Losing a semicolon in overview page Status in openstack i18n: New Bug description: Losing a semicolon Behind the "This Period's RAM-Hours". Semicolons should use Chinese, but using the English a semicolon. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1671367/+subscriptions

1 0

[Bug 1661454] Re: Inadequate Japanese translation for "Browse" on App Catalog tab
by Akihiro Motoki 30 Jul '17

30 Jul '17

As the report said, this is not a bug. ** Changed in: openstack-i18n Status: New => Invalid -- 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/1661454 Title: Inadequate Japanese translation for "Browse" on App Catalog tab Status in OpenStack Dashboard (Horizon): Invalid Status in openstack i18n: Invalid Bug description: Japanese translation for "Browse" is not adequate for this context. It is currently translated into 探索, but it should be 参照 or ブラウズ, but unable to locate the string from Zanata To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1661454/+subscriptions

1 0

[Bug 1700907] [NEW] Miss translation in Get Image document
by Tomonobu Niwa 30 Jul '17

30 Jul '17

Public bug reported: In https://docs.openstack.org/ja/image-guide/obtain-images.html, the explanations for other images (CentOS, Ubuntu, etc.) are correct but that of cirros is wrong as bellow. The original version: In a CirrOS image, the login account is cirros. The Japanese version: CirrOS イメージでは、ログインアカウントは「cirros「です。 It should be CirrOS イメージでは、ログインアカウントは cirros です。 as same as other images. ** 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/1700907 Title: Miss translation in Get Image document Status in openstack i18n: New Bug description: In https://docs.openstack.org/ja/image-guide/obtain-images.html, the explanations for other images (CentOS, Ubuntu, etc.) are correct but that of cirros is wrong as bellow. The original version: In a CirrOS image, the login account is cirros. The Japanese version: CirrOS イメージでは、ログインアカウントは「cirros「です。 It should be CirrOS イメージでは、ログインアカウントは cirros です。 as same as other images. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1700907/+subscriptions

2 1

[Bug 1536226] Re: Not all .po files compiled
by Akihiro Motoki 30 Jul '17

30 Jul '17

we decided to drop translation support for log strings, so we no longer need to move this forward. As an umbrella bug in openstack-i18n, this bug should be marked as Won't Fix. ** Changed in: openstack-i18n Status: New => Won't Fix -- 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/1536226 Title: Not all .po files compiled Status in Cinder: Fix Released Status in Glance: In Progress Status in heat: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in openstack i18n: Won't Fix Bug description: python setup.py compile_catalog only compiles one <domain>.po file per language to a <domain>.mo file. By default <domain> is the project name, that is nova.po. This means all other nova-log-*.po files are never compiled. The only way to get setup.py compile the other files is calling it several times with different domains set, like for instance `python setup.py --domain nova-log-info` and so on. Since this is not usual, it can be assumed that the usual packages don't contain all the .mo files. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1536226/+subscriptions

1 0

[Bug 1675298] Re: automatic generation of LANGUAGES list in settings.py
by Akihiro Motoki 30 Jul '17

30 Jul '17

horizon patch will be released as part of Pike. This can be closed in openstack-i18n now. ** Changed in: openstack-i18n Status: New => 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/1675298 Title: automatic generation of LANGUAGES list in settings.py Status in OpenStack Dashboard (Horizon): Fix Released Status in openstack i18n: Fix Released Bug description: At now, LANGUAGES list in openstack_dashboard/settings.py is updated manually. It is better to generate the language list automatically based on the existence of PO files. In horizon, there are four types of PO files ([horizon/locale, openstack_dashboard] * [django, djangojs]). It looks better to check whether all four types of PO files exist in the repo and list such languages. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1675298/+subscriptions

1 0

[Bug 1706270] [NEW] Need redirect URL on FWaaS in Networking Guide
by Youhei Tooyama 26 Jul '17

26 Jul '17

Public bug reported: This URL are 404. http://docs.openstack.org/admin-guide-cloud/networking_introduction.html#fi… Need redirect URL. /admin-guide-cloud to New pages. http://docs.openstack.org/admin-guide-cloud/ ----------------------------------- Release: 0.9 on 2016-11-24 07:57 SHA: cc8b39934de4de69e5235ca8e5c4d4b567d0f418 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/networki… URL: https://docs.openstack.org/liberty/ja/networking-guide/adv-config-fwaas.html ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: networking-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/1706270 Title: Need redirect URL on FWaaS in Networking Guide Status in openstack i18n: New Bug description: This URL are 404. http://docs.openstack.org/admin-guide-cloud/networking_introduction.html#fi… Need redirect URL. /admin-guide-cloud to New pages. http://docs.openstack.org/admin-guide-cloud/ ----------------------------------- Release: 0.9 on 2016-11-24 07:57 SHA: cc8b39934de4de69e5235ca8e5c4d4b567d0f418 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/networki… URL: https://docs.openstack.org/liberty/ja/networking-guide/adv-config-fwaas.html To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1706270/+subscriptions

2 1

Fwd: Re: Translations-test site
by Ian Y. Choi 18 Jul '17

18 Jul '17

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_ch… [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/

3 2

Fwd: [tripleo] I18n-themed Deep Dive - July 6th
by Julie Pichon 17 Jul '17

17 Jul '17

Hi, During the IRC meeting this morning [1], Ian mentioned a talk I'm planning to do for the TripleO team about I18n in tripleo-ui, and also a bit about the processes. If you're interested in attending, you're welcome to! It's right after the IRC meeting next week. Regards, Julie [1] http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… ---------- Forwarded message ---------- From: Julie Pichon <jpichon(a)redhat.com> Date: 29 June 2017 at 16:22 Subject: [tripleo] I18n-themed Deep Dive - July 6th To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev(a)lists.openstack.org> Hi folks, As I mentioned during the weekly meeting on Tuesday, I'd like to do a short i18n-themed deep dive during next week's slot (Thu July 6th, 14:00 UTC). I'll use my BlueJeans at [1] and updated the deep dives etherpad [2] with that information. There should be two broad topics: - Life and journey of a string - From when it gets introduced in tripleo-ui, goes through infra, up to Zanata, and then back - I'd also like to share some debugging tips, and how the infra jobs work - Working with the I18n team - The role of the I18n cross-project liaison - How we interact with the team in general, how to make their work easier - Governance, release schedule & string freezes, particularly as a cycle-trailing project I mentioned this presentation at the I18n meeting this morning and several people expressed an interest in attending, it could be a nice opportunity for both devs & translators to see another side of the work. If there's something in particular you'd like me to touch on, feel free to bring it up. The talk will be recorded and I'll post a transcript as well. Regards, Julie [1] https://bluejeans.com/4050564424/ [2] https://etherpad.openstack.org/p/tripleo-deep-dive-topics

3 6

[I18n] IRC Meeting reminder: July 6th at 13:00 UTC
by Ian Y. Choi 06 Jul '17

06 Jul '17

Hello all, I18n team is having our next meeting on July 6th 2017 (Thursday) at 13:00 UTC in #openstack-meeting IRC channel. I have not updated the topics yet but previous meeting logs are available at : http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/ . With many thanks, /Ian

1 1

[Bug 1682010] [NEW] the configuration file /etc/mongodb.conf should be /etc/mongod.conf
by zenglulu 01 Jul '17

01 Jul '17

Public bug reported: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. /etc/mongod.conf If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode ----------------------------------- Release: 0.1 on 2017-03-20 12:49 SHA: abc274532d229d2083df0d95d707393521e3d162 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/environment-no… ** Affects: openstack-i18n Importance: Undecided Assignee: zenglulu (zengluul) Status: New ** Tags: install-guide ** Changed in: openstack-i18n Assignee: (unassigned) => zenglulu (zengluul) -- 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/1682010 Title: the configuration file /etc/mongodb.conf should be /etc/mongod.conf Status in openstack i18n: New Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. /etc/mongod.conf If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode ----------------------------------- Release: 0.1 on 2017-03-20 12:49 SHA: abc274532d229d2083df0d95d707393521e3d162 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/zh_CN/install-guide-ubuntu/environment-no… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1682010/+subscriptions

2 1

[I18n] IRC Meeting reminder: March 30th at 13:00 UTC
by Ian Y. Choi 29 Jun '17

29 Jun '17

Hello all, I18n team is having our next meeting on March 30th 2017 (Thursday) at 13: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 last IRC meeting minutes and full logs: Minutes: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… With many thanks, /Ian

2 10

[Bug 1700321] [NEW] 네트워킹 (neutron) 개념 in Installation Guide
by fisache 25 Jun '17

25 Jun '17

Private bug reported: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode ----------------------------------- Release: 0.1 on 2017-06-12 11:12 SHA: 1865f28305fdb1eb6b5e1a434ac7e292c3421513 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/ko_KR/install-guide-rdo/neutron-concepts.… ** Affects: openstack-i18n Importance: Undecided Status: Invalid ** 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/1700321 Title: 네트워킹 (neutron) 개념 in Installation Guide Status in openstack i18n: Invalid Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode ----------------------------------- Release: 0.1 on 2017-06-12 11:12 SHA: 1865f28305fdb1eb6b5e1a434ac7e292c3421513 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/ko_KR/install-guide-rdo/neutron-concepts.… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1700321/+subscriptions

1 1

tr_TR is broken for sahara_dashboard
by Andreas Jaeger 19 Jun '17

19 Jun '17

From http://logs.openstack.org/periodic/sahara-dashboard-propose-translation-upd… 2017-06-19 06:39:00.785324 | + trans='sahara_dashboard/locale/tr_TR/LC_MESSAGES/django.po:1375: '\''msgid'\'' and '\''msgstr'\'' entries do not both end with '\''\n'\'' 2017-06-19 06:39:00.785416 | sahara_dashboard/locale/tr_TR/LC_MESSAGES/django.po:2747: '\''msgid'\'' and '\''msgstr'\'' entries do not both end with '\''\n'\'' 2017-06-19 06:39:00.785437 | msgfmt: found 2 fatal errors 2017-06-19 06:39:00.785456 | 551 translated messages.' Could anybody fix the string, please? Thanks, 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

3 2

horizon/dashboard Translation sync broken?
by Andreas Jaeger 19 Jun '17

19 Jun '17

Looking at http://status.openstack.org/openstack-health/#/g/build_queue/periodic?group… I see lots of failures for horizon related projects. Is there anybody that can look into this, please? 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

3 4

User survey translation status with translate checksite
by Ian Y. Choi 16 Jun '17

16 Jun '17

Hello! In Zanata, not only OpenStack official projects, but also user survey [1] is available to translate for better internationalized OpenStack from around the end of April this year :) Now I have found that some countries have nice progress on user survey translation, and I have heard that Foundation recently updated translation source strings to have more source strings in Zanata. Please revisit Zanata [1], also check user survey translate checksite, and review user survey translation for better quality of translated user survey. - User survey translate checksite : The site is available through https://devbranch.openstack.org/user-survey/ page. : Login is needed: The e-mail and password should be the same as your Zanata login. If you have trouble in your login, please tell me and I would like to guide you to resolve such situation. - How to reflect translation update to the translate checksite : You can edit translations through Zanata: https://translate.openstack. org/iteration/view/openstack-user-survey/openstack-user-survey . : Foundation manually updates po files from Zanata to translation checksite repository. : You can make a pull request to gettext/Locale folder in https://github.com/openstackweb/openstack-org/ github repisitory (Note: The repository is not in git.openstack.org and it is mainly managed from GitHub.) : If you are not familiar with Github pull request, please tell me then I will make a pull request. One example of pull request is: https://github.com/OpenStackweb/openstack-org/pull/78 With many thanks, /Ian [1] https://translate.openstack.org/iteration/view/openstack-user-survey/openst…

2 1

[I18n] Canceling IRC Meeting: April 27th at 13:00 UTC
by Ian Y. Choi 14 Jun '17

14 Jun '17

Hello all, Due to my international flight schedule, I cannot stay in IRC and discuss with some topics. Since other I18n IRC meeting chairs might be unavailable as far as I know, I would like to cancel the IRC meeting on April 27th at 13:00 UTC. Please see the previous meeting minutes at : http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/ . Also, I would like to mention those two things as a reminder: : More planning for Boston Summit for I18n - are you attending? - http://lists.openstack.org/pipermail/openstack-i18n/2017-April/002895.html : Let's also consider User survey translation: now available at Zanata! - http://lists.openstack.org/pipermail/openstack-i18n/2017-April/002896.html Now I am not pretty sure whether I can organize the next IRC meeting on May 4th, but I will try to do my best. With many thanks, /Ian

1 1

[I18n] Zanata webinar with IRC meeting (qna): June 8th at 13:00 UTC
by Ian Y. Choi 07 Jun '17

07 Jun '17

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

2 1

[Turkish] Asking for glossary review
by Ian Y. Choi 31 May '17

31 May '17

Hello Turkish translators, İşbaran Akçayır asked me to upload a glossary for Turkish. I would like Turkish translators to review https://review.openstack.org/#/c/467240/ and reply with +1 if it looks good. If you are not familiar with Gerrit (review.openstack.org) please see some documents and presentations in upstream institute [1]. I think [2] and [3] might be helpful, or please share your thoughts on Turkish glossary by replying to this e-mail copying with openstack-i18n(a)lists.openstack.org . With many thanks, /Ian [1] https://docs.openstack.org/upstream-training/ [2] https://docs.openstack.org/upstream-training/accounts.html#setup-gerrit-acc… [3] https://docs.openstack.org/upstream-training/workflow-reviewing.html#1

2 1

FW: [OpenStack-docs] [openstack-doc] [dev] What's up doc? Summit recap edition
by Alexandra Settle 25 May '17

25 May '17

Docs update below ☺ From: Alexandra Settle <a.settle(a)outlook.com> Date: Friday, May 19, 2017 at 12:12 PM To: "'openstack-docs(a)lists.openstack.org'" <openstack-docs(a)lists.openstack.org> Cc: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev(a)lists.openstack.org> Subject: [OpenStack-docs] [openstack-doc] [dev] What's up doc? Summit recap edition Hi everyone, The OpenStack manuals project had a really productive week at the OpenStack summit in Boston. You can find a list of all the etherpads and attendees here: https://etherpad.openstack.org/p/docs-summit As we all know, we are rapidly losing key contributors and core reviewers. We are not alone, this is happening across the board. It is making things harder, but not impossible. Since our inception in 2010, we’ve been climbing higher and higher trying to achieve the best documentation we could, and uphold our high standards. This is something to be incredibly proud of. However, we now need to take a step back and realise that the amount of work we are attempting to maintain is now out of reach for the team size that we have. At the moment we have 13 cores, of which none are full time contributors or reviewers. This includes myself. That being said! I have spent the last week at the summit talking to some of our leaders, including Doug Hellmann (cc’d), Jonathan Bryce and Mike Perez regarding the future of the project. Between myself and other community members, we have been drafting plans and coming up with a new direction that will hopefully be sustainable in the long-term. I am interested to hear your thoughts. I want to make sure that everyone feels that we’re headed in the right direction first and foremost. All of these action items are documented in this WIP etherpad: https://etherpad.openstack.org/p/doc-planning Some further highlights from the event… * The documentation team was represented by myself, Olga, and Alex Adamov for the Project Update: Documentation on the Monday. If you’d like to catch up with what we talked about, the video is available online now: https://www.youtube.com/watch?v=jcfbKxbpRvc The translation team PTL, Ian Choi, also had a session about getting more involved with the I18N team. You can view that video here: https://www.youtube.com/watch?v=ybFI4nez_Z8 * Ian and I also hosted the joint I18N and documentation onboarding session. We were visited by some friendly faces, and some new ones. Between Ian and myself, we discussed the documentation and translation workflows, and how to get involved (the mailing list, IRC channel, etc). Which was lots of fun :) we’d love to see more people there in the future, hopefully we’ll slowly get there! * This week I was focusing heavily on making the community aware that the documentation team was struggling to maintain contributors, but continuing with the same amount of work. This was a heavy conversation to be having, but it posed some really interesting questions to key leaders, and hopefully raised appropriate concerns. Ildiko and I hosted “OpenStack documentation: The future depends on all of us”. This was a really interesting session. I was able to pose to the group of attendees that the documentation team was struggling to maintain contributions. Major Hayden was kind enough to take notes during the session, you can find those here: https://etherpad.openstack.org/p/doc-future The project teams that came and represented their groups were interested in discussing the project-specific documentation (is living in the project’s repo tree the best place?) and voiced concerns I had otherwise not heard before. I recommend reading the notes to get a better idea :) * Kendall Nelson and Ildiko also hosted a session on the OpenStack Upstream Institute highlights. I recommend watching the video which is now live and available here: https://www.openstack.org/videos/boston-2017/openstack-upstream-institute-h… * One of the key takeaways from the summit was the session that I joint moderated with Melvin Hillsman regarding the Operations and Administration Guides. You can find the etherpad with notes here: https://etherpad.openstack.org/p/admin-ops-guides The session was really helpful – we were able to discuss with the operators present the current situation of the documentation team, and how they could help us maintain the two guides, aimed at the same audience. The operator’s present at the session agreed that the Administration Guide was important, and could be maintained upstream. However, they voted and agreed that the best course of action for the Operations Guide was for it to be pulled down and put into a wiki that the operators could manage themselves. We will be looking at actioning this item as soon as possible. These action items will free up the documentation team to become gate keepers and reviewers of documentation. Our key focus as a team will be on the tooling for the docs.openstack.org site (including the API docs). I’m really interested to hear everyone’s thoughts going forward – this is not set in stone. We need to change our strategy, and now is the time. If you’d rather reach out and discuss this personally, asettle on IRC is always the best place to find me. Thanks, Alex

2 1

[Bug 1691900] [NEW] Mistake in Newton Installation Guide
by Youhei Tooyama 24 May '17

24 May '17

Public bug reported: This Document are OpenStack Newton. But Document says to install Ocata. about CentOS yum install centos-release-openstack-ocata ↓ yum install centos-release-openstack-newton about RHEL yum install https://rdoproject.org/repos/rdo-release.rpm ↓ yum install https://repos.fedorapeople.org/repos/openstack/openstack-newton/rdo-release… This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. ----------------------------------- Release: 15.0.0 on 2017-05-18 19:32 SHA: 27f002a754e77d621332f30353044a91e449dd79 Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install… URL: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide ** Description changed: This Doc are OpenStack Newton. - But Document says to install ocata. + But Document says to install Ocata. about CentOS yum install centos-release-openstack-ocata ↓ yum install centos-release-openstack-newton about RHEL yum install https://rdoproject.org/repos/rdo-release.rpm ↓ yum install https://repos.fedorapeople.org/repos/openstack/openstack-newton/rdo-release… This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - - [x] I have a fix to the document that I can paste below including example: input and output. + - [x] I have a fix to the document that I can paste below including example: input and output. ----------------------------------- Release: 15.0.0 on 2017-05-18 19:32 SHA: 27f002a754e77d621332f30353044a91e449dd79 Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install… URL: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… ** Description changed: - This Doc are OpenStack Newton. + This Document are OpenStack Newton. But Document says to install Ocata. about CentOS yum install centos-release-openstack-ocata ↓ yum install centos-release-openstack-newton about RHEL yum install https://rdoproject.org/repos/rdo-release.rpm ↓ yum install https://repos.fedorapeople.org/repos/openstack/openstack-newton/rdo-release… This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. ----------------------------------- Release: 15.0.0 on 2017-05-18 19:32 SHA: 27f002a754e77d621332f30353044a91e449dd79 Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install… URL: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… -- 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/1691900 Title: Mistake in Newton Installation Guide Status in openstack i18n: New Bug description: This Document are OpenStack Newton. But Document says to install Ocata. about CentOS yum install centos-release-openstack-ocata ↓ yum install centos-release-openstack-newton about RHEL yum install https://rdoproject.org/repos/rdo-release.rpm ↓ yum install https://repos.fedorapeople.org/repos/openstack/openstack-newton/rdo-release… This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [x] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. ----------------------------------- Release: 15.0.0 on 2017-05-18 19:32 SHA: 27f002a754e77d621332f30353044a91e449dd79 Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install… URL: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1691900/+subscriptions

4 5

[Bug 1686339] [NEW] Wrong repository in Japanese install tutorials
by Tomonobu Niwa 23 May '17

23 May '17

Public bug reported: In Newton release, Japanese install manual describes to register Ocata repository when installing OpenStack packages, while that of English version explains to install Newton repository. Japanese tutorials: openSUSE: https://docs.openstack.org/newton/ja/install-guide-obs/environment-packages… CentOS: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… Ubuntu: https://docs.openstack.org/newton/ja/install-guide-ubuntu/environment-packa… ** 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/1686339 Title: Wrong repository in Japanese install tutorials Status in openstack i18n: New Bug description: In Newton release, Japanese install manual describes to register Ocata repository when installing OpenStack packages, while that of English version explains to install Newton repository. Japanese tutorials: openSUSE: https://docs.openstack.org/newton/ja/install-guide-obs/environment-packages… CentOS: https://docs.openstack.org/newton/ja/install-guide-rdo/environment-packages… Ubuntu: https://docs.openstack.org/newton/ja/install-guide-ubuntu/environment-packa… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1686339/+subscriptions

2 1

[Bug 1675298] Re: automatic generation of LANGUAGES list in settings.py
by OpenStack Infra 22 May '17

22 May '17

Reviewed: https://review.openstack.org/450126 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=a88092630014c53… Submitter: Jenkins Branch: master commit a88092630014c53c9e6fe4ee9265f8443eea96bd Author: Akihiro Motoki <amotoki(a)gmail.com> Date: Sun Mar 26 14:42:25 2017 +0000 Generate language list automatically Previously the available language list is maintained manually. This commit change horizon to check translation message catalog is available for each language and generate the language list automatically. settings.LANGUAGES is still used to determines the initial set of languages and now defaults to the list provided by django. Change-Id: I9d9c934beebd7a641e2feb0d5cdfa839e0efa3c3 Closes-Bug: #1675298 ** Changed in: horizon Status: In Progress => 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/1675298 Title: automatic generation of LANGUAGES list in settings.py Status in OpenStack Dashboard (Horizon): Fix Released Status in openstack i18n: New Bug description: At now, LANGUAGES list in openstack_dashboard/settings.py is updated manually. It is better to generate the language list automatically based on the existence of PO files. In horizon, there are four types of PO files ([horizon/locale, openstack_dashboard] * [django, djangojs]). It looks better to check whether all four types of PO files exist in the repo and list such languages. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1675298/+subscriptions

1 0

FYI: Statistics for docs.openstack.org by language & location
by Ian Y. Choi 18 May '17

18 May '17

Hello I18n team & Docs team! I would like to share Google Analytics statistics for https://docs.openstack.org . During Boston Summit, Alex showed such stats in [1] and me mentioned in [2]. I downloaded statistics data during Boston Summit for recent one year, and today I finally converted the data into text-based format to share through mailing lists. As far as I know, "Language" view in Google Analytics would be based on browser language settings, not sub-domain such as "docs.openstack.org/ja" or "docs.openstack.org/ko-kr", and "Location" might be where the web browser client actually requested. Feel free to share your thoughts: such as interpretation with such statistics, more meaningful metrics in Google Analytics to Docs & I18n team, and so on :) == Google Analytics: "Language" view for docs.openstack.org == (May 11, 2016 - May 10, 2017 / TOP 25) +----------+----------+----------------+ | Language | Sessions | % New Sessions | +----------+----------+----------------+ | en-us | 3374650 | 23.77% | +----------+----------+----------------+ | zh-cn | 1000346 | 18.03% | +----------+----------+----------------+ | en-gb | 295160 | 25.82% | +----------+----------+----------------+ | ja | 243452 | 19.06% | +----------+----------+----------------+ | fr | 159729 | 25.18% | +----------+----------+----------------+ | ko | 106003 | 17.17% | +----------+----------+----------------+ | ja-jp | 101114 | 28.62% | +----------+----------+----------------+ | zh-tw | 97826 | 19.32% | +----------+----------+----------------+ | de | 81475 | 32.40% | +----------+----------+----------------+ | ru | 68867 | 24.33% | +----------+----------+----------------+ | es | 63200 | 28.19% | +----------+----------+----------------+ | pt-br | 57748 | 30.93% | +----------+----------+----------------+ | ko-kr | 41212 | 25.11% | +----------+----------+----------------+ | pl | 33287 | 25.69% | +----------+----------+----------------+ | it | 31232 | 28.80% | +----------+----------+----------------+ | es-es | 30132 | 29.58% | +----------+----------+----------------+ | ru-ru | 26613 | 27.11% | +----------+----------+----------------+ | de-de | 22015 | 36.45% | +----------+----------+----------------+ | fr-fr | 19428 | 33.08% | +----------+----------+----------------+ | it-it | 18263 | 32.52% | +----------+----------+----------------+ | es-419 | 17672 | 28.48% | +----------+----------+----------------+ | en | 14706 | 27.52% | +----------+----------+----------------+ | nl | 13339 | 38.17% | +----------+----------+----------------+ | sv | 12805 | 23.17% | +----------+----------+----------------+ == Google Analytics: "Location" view for docs.openstack.org == (May 11, 2016 - May 10, 2017 / TOP 25) +----------------+----------+----------------+ | Country | Sessions | % New Sessions | +----------------+----------+----------------+ | United States | 1305483 | 24.73% | +----------------+----------+----------------+ | China | 906676 | 19.22% | +----------------+----------+----------------+ | India | 694034 | 23.82% | +----------------+----------+----------------+ | Japan | 428682 | 20.77% | +----------------+----------+----------------+ | France | 187056 | 25.39% | +----------------+----------+----------------+ | Germany | 180090 | 28.18% | +----------------+----------+----------------+ | South Korea | 168027 | 19.34% | +----------------+----------+----------------+ | United Kingdom | 167054 | 27.45% | +----------------+----------+----------------+ | Canada | 135999 | 24.74% | +----------------+----------+----------------+ | Russia | 125238 | 21.60% | +----------------+----------+----------------+ | Taiwan | 124119 | 18.55% | +----------------+----------+----------------+ | Brazil | 96044 | 28.07% | +----------------+----------+----------------+ | Spain | 95196 | 24.54% | +----------------+----------+----------------+ | Sweden | 73556 | 20.51% | +----------------+----------+----------------+ | Italy | 73003 | 27.99% | +----------------+----------+----------------+ | Vietnam | 66155 | 18.12% | +----------------+----------+----------------+ | Poland | 62403 | 24.73% | +----------------+----------+----------------+ | Australia | 62277 | 28.06% | +----------------+----------+----------------+ | Israel | 60821 | 19.37% | +----------------+----------+----------------+ | Hong Kong | 52224 | 22.83% | +----------------+----------+----------------+ | (not set) | 51330 | 18.09% | +----------------+----------+----------------+ | Finland | 51218 | 19.44% | +----------------+----------+----------------+ | Ukraine | 49667 | 21.54% | +----------------+----------+----------------+ | Netherlands | 49546 | 30.67% | +----------------+----------+----------------+ With many thanks, /Ian [1] https://www.openstack.org/summit/boston-2017/summit-schedule/events/18692/d… [2] https://www.openstack.org/summit/boston-2017/summit-schedule/events/18728/f…

1 0

Questions on new user registration failure in translate.openstack.org
by Ian Y. Choi 10 May '17

10 May '17

Hello Alex and Patrick, I am very thankful your your all and kind support on Zanata - translate.openstack.org :) Now I have a question on some authentication part in translate.openstack.org . As you might have already noticed, I18n team will have one important Hands-on Workshop session during Boston Summit on this Wednesday [1]. Yesterday, I met a Chinese OpenStack contributor and I asked her to also join in translate.openstack.org. However, she could not proceed to register in translate.openstack.org although she already had registered www.openstack.org account and signed ICLA. I was trying to find some log messages in Zanata but I did not know how to see some log messages. Would you investigate in this important authentication problem? It might imply that many participants on this Wednesday for Hands-on Workshop session will not able to register their accounts in Zanata, and now I am too much worried about this worst case. If we might need actual server logs in the production server, please tell me then I will ask this to infra team members. With many thanks, /Ian [1] https://www.openstack.org/summit/boston-2017/summit-schedule/events/18387/i…

3 3

[I18n] (Special) Summit hack-room & IRC meeting in this week with Skype
by Ian Y. Choi 09 May '17

09 May '17

Hello all, First of all, I really really feel that Boston Summit welcomes translators! Thanks to lots of kind support from upstream contributors, users, operators, and also Foundation staff, I think I18n team is able to have so many I18n sessions during this Summit. I have asked translators whether they would come to Boston Summit or not via i18n mailing list several times but it seems that a few active translators finally have come to Boston Summit [1]. Now, I would like to propose a hack-room for I18n team on on Thursday 9:00 AM - 10:30 AM at Hynes, MR 108 (I have signed into [2]). I think the time would be the best for I18n team since Thursday 9:00 AM - 10:00 AM is the same as I18n IRC meeting time slot [3]. So, for physical Summit attendees: - Please attend to I18n hack room on Thursday 9:00 AM - 10:30 AM at Hynes, MR 108. - If someone wants to more know I18n and translation or have questions on translation, please ping me via IRC. My IRC nickname is "ianychoi". And for I18n translators (+ Zanata development team members) who are unable to physically attend to the Summit: - Please come to IRC meeting [3]. - Also I strongly encourage to also join a voice meeting via Skype Business. I have made a link for the Meeting: https://meet.lync.com/ychoi/ianychoi/3HVZ0CY1 . Please join in the meeting if you would like to see I18n people in the Summit :) - Timezone information is also available at: [4] Also, I welcome upstream contributors, users, operators, and even Summit-101 members who would like to know how I18n team is dealing with translation. I am now proposing the following topics, but topics may be subject to change: - (Greeting) - Sharing how Summit is going with I18n - Report of recent Zanata production server error - User survey translation status - Discussion on I18n team PTG participation - Feedback from I18n contributors: PTG, Summit, Design Summit, Forum - Action items With many thanks, /Ian [1] https://etherpad.openstack.org/p/i18n-boston-summit-activities [2] https://ethercalc.openstack.org/Boston_Forum_Hacking_Rooms [3] https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting#Agenda_for_next_me… [4] https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=…

3 2

[I18n] IRC Meeting reminder today: May 4th at 07:00 UTC and next week
by Ian Y. Choi 04 May '17

04 May '17

Hello all, I18n team is having our next meeting on May 4th 2017 (Thursday) at 07:00 UTC in #openstack-meeting IRC channel. Please refer to what I am suggesting for meeting agenda at : https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting#Agenda_for_next_me… and previous meeting logs are available at : https://wiki.openstack.org/wiki/I18N/MeetingLogs . Anyone is welcome to add topics on Wiki For next week IRC meeting (May 11st 2017 13:00 UTC), It conflicts with Boston Summit schedule, however, I would like to lead the next IRC meeting if there is remote attendee. Please reply from this message if you would like to attend to the IRC meeting on May 11st. If there are no replies, then I would like to skip the IRC meeting on May 11st 2017. FYI: Please also see the timezone at : https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=… With many thanks, /Ian

2 1

Let's also consider User survey translation: now available at Zanata!
by Ian Y. Choi 25 Apr '17

25 Apr '17

Hello, OpenStack User survey translation is now available at Zanata : https://translate.openstack.org/iteration/view/openstack-user-survey/openst… Thanks a lot especially Heidi Joy, Jimmy McArthur, and Sebastian Marcet who have supported, implemented user survey translation functionality, and integrated into Zanata with pot files. QA page for qualified translation and review would be available later if translation ratio is high. Foundation asks me that it would be so nice to have translations by around the early of June. There will be OpenStack Days in Asia region on July, and the translated user survey is anticipated to distribute to local users with translated questions. Note that the followings are when each country in Asia will have OpenStack Days (OSD): - July 13-14: OSD Korea - July 18-19: OSD Taiwan - July 20-21: OSD Japan - July 22-23: OSD India - July 24-25: OSD China In my opinion, considering user survey translation with OSD would strengthen the relationship with local translators and local user group members. Please also consider and translate user survey :) With many thanks, /Ian

1 0

More planning for Boston Summit for I18n - are you attending?
by Ian Y. Choi 25 Apr '17

25 Apr '17

Hello, It is the time to more concisely plan Boston Summit with I18n :) I have create an Etherpad : https://etherpad.openstack.org/p/i18n-boston-summit-activities Please put your name if you will attend to Boston Summit with available dates. Moreover, if you are unable to attend but want to discuss via IRC, please also mention your name with available time. There are many I18n sessions during Boston Summit - once every Summit day! (although Wednesday Hands on Workshop needs to be more planned with details) For meetup, I would like decide best time slot considering number of attendees from I18n. With many thanks, /Ian

1 0

Survey for Zanata platform
by Alex Eng 24 Apr '17

24 Apr '17

Hi guys, As part of our plan to improve Zanata translation platform, it is important for us to constantly collect feedback from users to understand problems and needs. It would be appreciated if you guys can spent few minutes to complete the survey https://drive.google.com/open?id=1lcbmbJ1snljrd5t_ nRyGgDTH7SRWpp6PBKJaq7UiQkM PS. The survey will be closed on 6/MAY. <https://drive.google.com/open?id=1lcbmbJ1snljrd5t_nRyGgDTH7SRWpp6PBKJaq7UiQ…> Regards, -- ALEX ENG SENIOR SOFTWARE ENGINEER, TEam lead Red Hat Asia-Pacific Pty Ltd <https://www.redhat.com/> Level 1, 193 North Quay Brisbane 4000 aeng(a)redhat.com M: +61423353457 IM: aeng <https://red.ht/sig>

6 6

Fwd: [User-committee] Boston Forum Schedule
by Ian Y. Choi 11 Apr '17

11 Apr '17

Hello translators, I would like to happily forward one announcement: I18n feedback collection has been finally selected as one of Forum topics! More details are at http://forumtopics.openstack.org/cfp/details/116 , and the time slot is 11:15 - 11:55 AM on Tuesday (May 9th) according to Boston local time. Note that the brainstorming for I18n team Forum and Summit presentations & workshops are still on-going : https://etherpad.openstack.org/p/BOS-I18n-brainstorming . Please do not hesitate to share your idea on Etherpad, here (mailing list), IRC, or anything else. Your feedback is important and I appreciate all :) With many thanks, /Ian -------- Original Message -------- Subject: [User-committee] Boston Forum Schedule Date: Mon, 10 Apr 2017 17:35:46 +0800 From: Tom Fifield <tom(a)openstack.org> To: user-committee(a)lists.openstack.org <user-committee(a)lists.openstack.org> Hi everyone, Thank you for the many excellent topics submitted for our first Forum. We have updated the topic submission site with the status of each - please check yours. Please also find attached in PDF the proposed schedule for the Forum in Boston. Let us know if you see major issues with it. As Thierry said in design summits past; "It's difficult to make too many changes at this stage as they quickly cascade into breaking all sorts of constraints, but we may still be able to accommodate some." :) Eagle-eyed readers will see that there are a number of slots in gray (on Thursday afternoon). These are being deliberately kept aside for the usual few critical topics that come up in the next few weeks and also for the discoveries we make in the first 3 days of the summit. We'll soon publish the Forum sessions on the main schedule, using the title, abstracts and moderators you submitted, but look forward to your feedback in the mean-time! Thank you all very much for making our first Forum a success. Regards, Doug, Emilien, Melvin, Mike, Shamail & Tom Forum Scheduling Committee

2 1

[openstack-docs] [dev] What's up, doc?
by Alexandra Settle 07 Apr '17

07 Apr '17

Team, This week I have still been working on drafting a governance tag for our guides called "docs:follows-policy". I have been working with Doug Hellmann (dhellmann) in the last week to change to draft dramatically, so it would be good for doc people and doc liaisons to review. We are trying to make this a broader tag, so it can be applied for other guides too. To review: https://review.openstack.org/#/c/445536/ I am also in the process of documenting guidelines in our Contribution Guide - which would also benefit from doc reviews: https://review.openstack.org/#/c/453642/ Would like to call out and thank John Davidge for his awesome work with the Networking Guide and neutron-related patches. He's been providing valuable guidance, and reviews, and it has been greatly appreciated by myself and the team. Lana Brindley has done an awesome job for the last two weeks in keeping our bug list under control. We are down to an amazing 102 bugs in queue, and 82 bugs closed this cycle already! Next week, I will be looking after the bug triage liaison role! If you're sitting there thinking "bugs are for me, I really love triaging bugs!" well, you're in luck! We have one spot open for the rest of the cycle (14 Aug - 28 Aug): https://wiki.openstack.org/wiki/Documentation/SpecialityTeams#Bug_Triage_Te… == The Road to the Summit in Boston == Keep an eye out for the docs and I18n have a project onboarding room at the summit. Melvin Hillsman (mrhillsman) of the User Committee submitted a forum topic for the Ops Guide to get operator feedback. David Flanders from the Foundation has also proposed a forum topic for developer.openstack.org (which currently houses our API, SDK, and other dev stuff). We'll be discussing major changes to that and would like to see some feedback from people here. Any questions on that, shoot it my way. My main objective for this forum topic is to reduce our current technical debt that lives on this site. For more information on forum topics: https://wiki.openstack.org/wiki/Forum Schedule has been released: https://www.openstack.org/summit/boston-2017/summit-schedul == Specialty Team Reports == * API - Anne Gentle: API versioning in relation to release versioning is currently manually compiled for the 40-ish API services, so ideas on how to automate and surface that info welcomed. More info: http://lists.openstack.org/pipermail/openstack-dev/2017-March/114690.html * Configuration Reference and CLI Reference - Tomoyuki Kato: N/A * High Availability Guide - Ianeta Hutchinson: We are continuing to collaborate with OS DevOps team. See the tag ha-guide-draft for bugs opened to fill content for the new guide. * Hypervisor Tuning Guide - Blair Bethwaite: N/A * Installation guides - Lana Brindley: We have now branched, so please remember to backport if you have edits to the Ocata guide now. Big thanks to all the testers who have been working hard over the past month or two (that Nova cells bug was *tough*!), and to Brian and Mariia for doing the heavy lifting. Noticed a bunch links to draft versions of the guide in Newton/Ocata branches, backports for that have been merged, and the Contributor Guide updated so we don't miss it in the future (https://docs.openstack.org/contributor guide/release/taskdetail.html#update-links-in-all-books). * Networking Guide - John Davidge: More patches landed in the last couple of weeks dealing with the move to OSC, and more are still in flight. Progress also continues on RFC 5737 compliance. Thanks to all contributors for their work. * Operations and Architecture Design guides - Darren Chan: Arch Guide: edited architecture considerations content and cleaned up the index page structure which was applied across OS manuals. Some ops-related content was moved to the Ops Guide. Our current focus is improving the storage design content and networking design content. * Training Guides - Matjaz Pancur: N/A * Training labs - Roger Luethi: We released the Ocata version of training-labs this week. * User guides - Joseph Robinson: For the user guides - the spec on migrating the Admin Guide content this week moved closer to merging. I started preparing the work items for action on the User Guides tasks wiki page. * Theme and Tools - Brian Moss: Anne has a spec up for theme consolidation, please check it out: https://review.openstack.org/#/c/454346/, Brian has fixed up the sitemap tool tests, reviews welcome: https://review.openstack.org/#/c/453976/. 41 open bugs, 13 closed in Pike == Doc team meeting == Our next meeting will be on Thursday, 20 April at 2100 UTC in #openstack-meeting-alt. For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting The meeting chair will be me! Big thanks to Joseph for stepping up in the last 2 meetings and hosting in my absence! Really appreciated it :) -- Have a great weekend :) Alex IRC: asettle Twitter: dewsday

1 0

Babel 2.4 and ko_KR
by Andreas Jaeger 07 Apr '17

07 Apr '17

I see in: http://logs.openstack.org/8d/8d993d3bbd17ce22288b9ea9caa6d93618522f46/post/… "ValueError: expected only letters, got u'ko-kr'" Is there anybody that can investigate whether Babel is broken and needs blacklisting - or what else needs to change? This is using BAbel 2.4.0, Thanks for any help, 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 7

[openstack-doc] Docs team meeting
by Alexandra Settle 06 Apr '17

06 Apr '17

Hey everyone, The docs meeting will continue today in #openstack-meeting-alt as scheduled (Thursday at 21:00 UTC). For more details, and the agenda, see the meeting page: - https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_mee… The meeting with be hosted by Joseph Robinson, as I have some personal business to attend to this evening. Specialty team leads – if you are unable to attend the meeting, please send me your team reports to include in the doc newsletter. Thanks, Alex

1 0

[Bug 1536226] Re: Not all .po files compiled
by OpenStack Infra 05 Apr '17

05 Apr '17

Reviewed: https://review.openstack.org/319353 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=cf42abc85e385ea… Submitter: Jenkins Branch: master commit cf42abc85e385eac12123ccac63a7dd3eb4f83ce Author: Sven Anderson <sven(a)redhat.com> Date: Fri May 20 18:35:52 2016 +0200 Let setup.py compile_catalog process all language files Two years ago the translation files have been split into several files, separating the log messages of different log levels from each other, like X.pot, X-log-warning.pot, X-log-info.pot, and so on. However, the setup.py command `compile_catalogs`, that comes from the babel package and compiles the corresponding .po files into .mo files, only supported one file per python package. This means that during packaging `compile_catalogs` never compiled the X-log-*.po files, so the corresponding translations were always missing. Since babel 2.3 the domain can be set to a space separated list of domains. This change adds the the additional log level files to the domain list. Change-Id: I436072d03f401240df6d7b8348616bc7c4731c4a Closes-Bug: #1536226 ** Changed in: neutron Status: In Progress => 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/1536226 Title: Not all .po files compiled Status in Cinder: Fix Released Status in Glance: In Progress Status in heat: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in neutron: Fix Released Status in OpenStack Compute (nova): Fix Released Status in openstack i18n: New Bug description: python setup.py compile_catalog only compiles one <domain>.po file per language to a <domain>.mo file. By default <domain> is the project name, that is nova.po. This means all other nova-log-*.po files are never compiled. The only way to get setup.py compile the other files is calling it several times with different domains set, like for instance `python setup.py --domain nova-log-info` and so on. Since this is not usual, it can be assumed that the usual packages don't contain all the .mo files. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1536226/+subscriptions

1 0

request for help from ESL readers
by Brian Rosmaita 04 Apr '17

04 Apr '17

Hello i18n team, There's a section of Glance documentation that's written in a colloquial american english style, but some contributors have expressed concern that this attempt to make a concept clear to non-technical american english readers may actually make it more difficult for ESL readers to understand. It would be awesome if a few ESL people would take a look and let us know what you think: http://specs.openstack.org/openstack/glance-specs/specs/api/v2/sharing-imag… thanks, brian

3 3

[openstack-docs] [dev] What's up, doc?
by Alexandra Settle 27 Mar '17

27 Mar '17

Team team team team team, Well the last month has just FLOWN by since the PTG. We've got plenty going on in the doc team... This week I have been helping out the security team with the Security Guide. We've been working on some cursory edits, and removal of content. A few patches have already made it through - thanks to the OSIC security team for tackling some of the outstanding bugs. There'll be more edits coming from me in the next few weeks. To see our planning: https://etherpad.openstack.org/p/sec-guide-pike I am also in the process of drafting a governance tag for our install guides. Would be great for everyone to review and understand what the process will involve: https://review.openstack.org/#/c/445536/ Shoutout and big thanks to Brian Moss and the nova team who worked together tirelessly to document Nova v2 Cells and Placement API - which was a massive blocker for our Installation Guide. Also, thank you to our Ocata release managers, Maria Zlatkova and Brian Moss for cutting the branch! Pike is well and truly underway now. Ianeta Hutchinson has done an awesome job for the last two weeks in keeping our bug list under control. We are down to an amazing 104 bugs in queue, and 59 bugs closed this cycle already! Next week, we have Lana who will be looking after the bug triage liaison role! If you're sitting there thinking "bugs are for me, I really love triaging bugs!" well, you're in luck! We have a few spots open for the rest of the cycle: https://wiki.openstack.org/wiki/Documentation/SpecialityTeams#Bug_Triage_Te… == The Road to the Summit in Boston == * Schedule has been released: https://www.openstack.org/summit/boston-2017/summit-schedule/ * Docs and I18n have a project onboarding room at the summit, keep an eye out on the dev ML for more information. Kendall will inform us when the time comes. Anyone around to help me with that? http://lists.openstack.org/pipermail/openstack-dev/2017-March/114149.html * Docs project update will be delivered by me (asettle) on Mon 8, 3:40pm-4:20pm. https://www.openstack.org/summit/boston-2017/summit-schedule/global-search?… == Specialty Team Reports == * API - Anne Gentle: There's still a lot of discussion on https://review.openstack.org/#/c/421846/ which is about API change guidelines. Take a look and join in on the review. Also on the openstack-dev list, there's a thread about the future of the app catalog, which is relevant to the app developer audience so I include it here: http://lists.openstack.org/pipermail/openstack dev/2017-March/113362.html<http://lists.openstack.org/pipermail/openstack%20dev/2017-March/113362.html> Also related to the app dev audience is the wrapping up of the App Ecosystem working group: http://lists.openstack.org/pipermail/user-committee/2017-March/001825.html * Configuration Reference and CLI Reference - Tomoyuki Kato: N/A * High Availability Guide - Ianeta Hutchinson: At the Atlanta PTG, the documentation team outlined a new table of contents that is now upstream as a draft here: https://github.com/openstack/openstack-manuals/tree/master/doc/ha-guide-dra…. A blocker to progress in the past had been a lack of SME’s for the topic of high availability but that is no longer the case \o/. The OSIC DevOps team has an “adopt-a-guide” project in which they are collaborating with the OpenStack docs community and OSIC Docs team to apply the new ToC and validate all content for the guide. The progress of this collaboration is being tracked here https://docs.google.com/spreadsheets/d/1hw4axU2IbLlsjKpz9_EGlKQt0S6siViik7E… We are calling for more contributors both as SME's and tech writers. Ping iphutch if interested! * Hypervisor Tuning Guide - Blair Bethwaite: N/A * Installation guides - Lana Brindley: Cells bug is closer to being fixed, and we are closer to a complete test install https://wiki.openstack.org/wiki/Documentation/OcataDocTesting look at all that green!). We're planning to branch Ocata by the end of this week. * Networking Guide - John Davidge: N/A * Operations and Architecture Design guides - Darren Chan: Arch Design Guide: Minor IA and general cleanup of the storage, compute, and networking sections in the Design chapter. Currently updating gaps in storage design content. Ops Guide: Removed cloud architecture content (migrated to the Arch Design Guide). * Security Guide - Nathaniel Dillon: Edits from Alex going through, and patches from the OSIC DevOps team. See above for more info. * Training Guides - Matjaz Pancur: For Training guides, related topics: a new brand for activities around OpenStack Upstream University/Training. It is now known as OpenStack Upstream Institute (https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute) * Training labs - Roger Luethi: We are currently testing our automated version of the Ocata install-guide. We had a problem with Ubuntu's new ISO image (16.04.2 LTS) which is now resolved. * User guides - Joseph Robinson: Several other Legacy commands were converted to OS commands this week. Reviewed the Admin Guide spec. * Theme and Tools - Brian Moss: I'd like to do an openstackdocstheme release soon, as we've got some items (PDF styling, search page JS fix, image centering) that would be good to have in production. Any concerns or last minute items to merge please let me know. We've had some issues come up with the auto-generation scripts. Some have been fixed already (thanks Kato and Christian!), and we're investigating others. If you notice anything amiss or would like to help out, please let me know. 46 open bugs, 8 closed in Pike == Doc team meeting == Our next meeting will be on Thursday, 7 April at 2100 UTC in #openstack-meeting-alt. For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting -- Have a great week :) Alex IRC: asettle Twitter: dewsday

1 0

Generate horizon language list automatically
by Akihiro Motoki 27 Mar '17

27 Mar '17

Hi I18n team, I just push my patch which changes horizon to generate the language list automatically [1] and the this topic is traced by the bug [2]. I would like to share my long-standing idea with the team. Does it sound reasonable? * The basic idea is to generate the language list based on message catalogs (PO files) availability. * Horizon now has four types of message catalogs (django, djangojs) in horizon and openstack_dashboard respectively. If all message catalogs are present, such languages are listed in the language list. There are some corner case logic. * Some languages share a same locale prefix. Good example is Spanish variants: es, es-ar, es-mx and es-ve. When horizon searches message catalogs for es-ar, a locale "es_AR" is first checked and then "es" (prefix) locale is checked. In this case, if "es-ar" has no corresponding translations ("es_AR") and "es" is already registered in the language list, "es-ar" will not be added in the language list. * For the source language (i.e., English), message catalog existence check is skipped. * The current setting LANGUAGES still has effect. Operators can use e used to limit the initial set of languages to exclude languages they want to show to their users. (Note that even when a language is specified in LANGUAGES setting, if not all message catalogs for the language exist the language will be skipped.) Thanks, Akihiro [1] https://review.openstack.org/#/c/450126/ [2] https://bugs.launchpad.net/horizon/+bug/1675298

1 0

Re: [OpenStack-I18n] [OpenStack-docs] stable/ocata created, publishing frozen for now
by Ian Y. Choi 25 Mar '17

25 Mar '17

Oh, great! Congrats for stable/ocata in openstack-manuals! To work translation sync job successfully with https://review.openstack.org/#/c/449385 <https://review.openstack.org/#/c/449385> , I18n team needs to create stable-ocata version for openstack-manuals in Zanata: https://translate.openstack.org. I checked that someone (maybe Kato-san or Andreas I think) already created stable-ocata version for openstack-manuals in Zanata. Thanks a lot! I have merged from openstack-manuals translations in stable-newton version to master and stable-ocata, and updated brief documentation translation plan for Pike cycle (aims to translate stable-ocata install-guide, common, network-guide, and some master documents). For more concrete plan, I18n team will discuss Documentation translation plan & priority on later IRC meeting. With many thanks, /Ian Mariia Zlatkova wrote on 3/25/2017 2:36 AM: > The changes have been merged. Kudos to Andreas for all his reviews and > fixes! > > So core-reviewers can go ahead and merge now. > > On Fri, Mar 24, 2017 at 1:42 PM, Andreas Jaeger <aj(a)suse.com > <mailto:aj@suse.com>> wrote: > > On 2017-03-24 11:24, Mariia Zlatkova wrote: > > Hi all, > > We have the stable/ocata branch created. Brian has prepared the > > following changes to master: > > > > https://review.openstack.org/#/c/449383 > <https://review.openstack.org/#/c/449383> > > <https://review.openstack.org/#/c/449383 > <https://review.openstack.org/#/c/449383>> > > https://review.openstack.org/#/c/449385 > <https://review.openstack.org/#/c/449385> > > <https://review.openstack.org/#/c/449385 > <https://review.openstack.org/#/c/449385>> > > > > I'm going to make the required changes to stable/ocata. So > please do not > > approve any changes until those are in. > > good idea, thanks! > > Note that since we tagged again, the release scripts added comments to > lots of closed bugs - you can ignore them... > > Andreas > -- > Andreas Jaeger aj(a){suse.com <http://suse.com>,opensuse.org > <http://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 > > > > > -- > *Mariia Zlatkova* > Technical Writer | Mirantis, Kharkiv > www.mirantis.com <http://www.mirantis.com> > > > > _______________________________________________ > OpenStack-docs mailing list > OpenStack-docs(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

1 0

Pike dashboard translation plan & priority are updated in Zanata Dashboard
by Ian Y. Choi 23 Mar '17

23 Mar '17

Hello all translators and language coordinators, Pike dashboard translation plan and priority are updated in Zanata Dashboard : https://translate.openstack.org . Some notes regarding this update are: - I have merged all dashboard translations for projects from stable-ocata to master in https://translate.openstack.org/version-group/view/ocata-dashboard-translat… . - For such merge purposes, translations in master version is being overwitten by translations in stable-ocata version, since I18n team prioritized primarily on Ocata version. - Pike dashboard translations group is available at : https://translate.openstack.org/version-group/view/pike-dashboard-translati… . Tripleo-ui has been added to Pike dashboard translations group. - I have checked that Docs team will create stable/ocata branch soon. I will follow to create stable-ocata version in Zanata, do merge stuffs later, and announce through I18n mailing list. With many thanks, /Ian

1 0

[Bug 1675298] Re: automatic generation of LANGUAGES list in settings.py
by Akihiro Motoki 23 Mar '17

23 Mar '17

Added openstack-i18n to share the information ** Also 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/1675298 Title: automatic generation of LANGUAGES list in settings.py Status in OpenStack Dashboard (Horizon): New Status in openstack i18n: New Bug description: At now, LANGUAGES list in openstack_dashboard/settings.py is updated manually. It is better to generate the language list automatically based on the existence of PO files. In horizon, there are four types of PO files ([horizon/locale, openstack_dashboard] * [django, djangojs]). It looks better to check whether all four types of PO files exist in the repo and list such languages. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1675298/+subscriptions

1 0

[I18n] IRC Meeting reminder: March 23th at 07:00 UTC
by Ian Y. Choi 22 Mar '17

22 Mar '17

Hello all, I18n team is having our next meeting on March 23th 2017 (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 last IRC meeting minutes and full logs: Minutes: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… With many thanks, /Ian

1 0

release notes POT file now contains branch info
by Akihiro Motoki 21 Mar '17

21 Mar '17

Hi team, Small news on release note translations. Previously POT files of release notes did not contain branch information (such as ocata, newton). I made a small change on reno (release note tool) and POT files of release notes now contains branch information (example [1]). Thanks, Akihiro [1] http://tarballs.openstack.org/translation-source/horizon/master/releasenote…

2 1

[Bug 1670640] [NEW] zanata_stat.py does not honor branch (version) and stats of the last processed branch is used
by Akihiro Motoki 19 Mar '17

19 Mar '17

Public bug reported: zanata_stat.py can process multiple versions (branches) at the same time, but the logic does not honor a version processed. As a result, user stats from the last processed version is used as user translation stats. AFAIK the tool is used to retrieve translation stats and determine ATC status. https://github.com/openstack/i18n/blob/master/tools/zanata/zanata_stats.py#… ** Affects: openstack-i18n Importance: Critical Assignee: Akihiro Motoki (amotoki) Status: New ** Changed in: openstack-i18n Assignee: (unassigned) => Akihiro Motoki (amotoki) -- 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/1670640 Title: zanata_stat.py does not honor branch (version) and stats of the last processed branch is used Status in openstack i18n: New Bug description: zanata_stat.py can process multiple versions (branches) at the same time, but the logic does not honor a version processed. As a result, user stats from the last processed version is used as user translation stats. AFAIK the tool is used to retrieve translation stats and determine ATC status. https://github.com/openstack/i18n/blob/master/tools/zanata/zanata_stats.py#… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1670640/+subscriptions

2 1

[Bug 1670725] [NEW] zanata_users.py does not work with new Zanata (3.9.6)
by Akihiro Motoki 18 Mar '17

18 Mar '17

Public bug reported: zanata_users.py does not work with Zanata 3.9.6. zanata_users.py parses the generated web pages, so there is no surprise after upgrading zanata. ubuntu@sheep6:~/tmp/i18n/tools/zanata (master)[15:23:51]$ python zanata_users.py Retreiving language list Getting member list from language el member_url=/language/view/el?dswid=-5508 Traceback (most recent call last): File "zanata_users.py", line 145, in <module> data = collect_zanata_language_and_members() File "zanata_users.py", line 120, in collect_zanata_language_and_members for role, user_id in zanata.iter_language_members(member_url): File "zanata_users.py", line 51, in iter_language_members span_txt = user.find('span', {'class': 'list__item__meta'}).text AttributeError: 'NoneType' object has no attribute 'text' ** Affects: openstack-i18n Importance: Medium 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/1670725 Title: zanata_users.py does not work with new Zanata (3.9.6) Status in openstack i18n: New Bug description: zanata_users.py does not work with Zanata 3.9.6. zanata_users.py parses the generated web pages, so there is no surprise after upgrading zanata. ubuntu@sheep6:~/tmp/i18n/tools/zanata (master)[15:23:51]$ python zanata_users.py Retreiving language list Getting member list from language el member_url=/language/view/el?dswid=-5508 Traceback (most recent call last): File "zanata_users.py", line 145, in <module> data = collect_zanata_language_and_members() File "zanata_users.py", line 120, in collect_zanata_language_and_members for role, user_id in zanata.iter_language_members(member_url): File "zanata_users.py", line 51, in iter_language_members span_txt = user.find('span', {'class': 'list__item__meta'}).text AttributeError: 'NoneType' object has no attribute 'text' To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1670725/+subscriptions

2 1

[Bug 1670638] [NEW] zanata_stat.py does not work with new Zanata (3.9.6)
by Akihiro Motoki 18 Mar '17

18 Mar '17

Public bug reported: Zanata 3.9.6 changes the format of translation stats. The new format is like: { "username": "amotoki", "contributions": [ { "locale": "ja", "translation-stats": { "translated": 7360, "needReview": 0, "approved": 152, "rejected": 0 }, "review-stats": { "approved": 220, "rejected": 0 } } ] } Previously, the format was: {"amotoki": [ {"ja": {"translated": 10, "approved": 0, "rejected": 0 } } ] } ** Affects: openstack-i18n Importance: High Assignee: Akihiro Motoki (amotoki) Status: New ** Changed in: ubuntu-translations Assignee: (unassigned) => Akihiro Motoki (amotoki) ** Project changed: ubuntu-translations => openstack-i18n ** Changed in: openstack-i18n Importance: Undecided => High -- 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/1670638 Title: zanata_stat.py does not work with new Zanata (3.9.6) Status in openstack i18n: New Bug description: Zanata 3.9.6 changes the format of translation stats. The new format is like: { "username": "amotoki", "contributions": [ { "locale": "ja", "translation-stats": { "translated": 7360, "needReview": 0, "approved": 152, "rejected": 0 }, "review-stats": { "approved": 220, "rejected": 0 } } ] } Previously, the format was: {"amotoki": [ {"ja": {"translated": 10, "approved": 0, "rejected": 0 } } ] } To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1670638/+subscriptions

3 2

Re: [OpenStack-I18n] [OpenStack-Infra] Broken zh_TW translations for monasa-ui
by Ian Y. Choi 17 Mar '17

17 Mar '17

Hello, I have temporally fixed the translated string which caused such error. Translators, please do not save the translated strings with warnings - it would imply that translation sync job does not work well. Some original strings could have unfamiliar structure. If then, please tell me to discuss with the developers who contributed and accepted the original strings. With many thanks, /Ian Andreas Jaeger wrote on 3/17/2017 5:35 AM: > See > http://logs.openstack.org/periodic/monasca-ui-propose-translation-update/14… > : > > 2017-03-16 08:07:24.539792 | ++ msgfmt --statistics -o /dev/null > monitoring/locale/zh_TW/LC_MESSAGES/django.po > 2017-03-16 08:07:24.544961 | + > trans='monitoring/locale/zh_TW/LC_MESSAGES/django.po:257: > '\''msgid'\'' and '\''msgstr'\'' entries do not both begin with > '\''\n'\'' > 2017-03-16 08:07:24.545011 | msgfmt: found 1 fatal error > 2017-03-16 08:07:24.545041 | 48 translated messages, 101 untranslated > messages.' > > Could anybody help, please? > > Andreas

1 0

Re: [OpenStack-I18n] [openstack-dev] [ptls] Project On-Boarding Rooms
by Ian Y. Choi 16 Mar '17

16 Mar '17

Hello Kendall! I18n team loves to have a project on-boarding room for new translators :) Please reserve a room for I18n if available. With many thanks, /Ian Kendall Nelson wrote on 3/16/2017 3:20 AM: > Hello All! > > As you may have seen in a previous thread [1] the Forum will offer > project on-boarding rooms! This idea is that these rooms will provide > a place for new contributors to a given project to find out more about > the project, people, and code base. The slots will be spread out > throughout the whole Summit and will be 90 min long. > > We have a very limited slots available for interested projects so it > will be a first come first served process. Let me know if you are > interested and I will reserve a slot for you if there are spots left. > > - Kendall Nelson (diablo_rojo) > > [1] > http://lists.openstack.org/pipermail/openstack-dev/2017-March/113459.html > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

2 1

FW: [openstack-dev] [ptls] Project On-Boarding Rooms
by Alexandra Settle 16 Mar '17

16 Mar '17

Hey everyone, Look out for our project onboarding room at the summit! If you are available, please come and help out Ian and I :) Thanks, Alex From: Kendall Nelson <kennelson11(a)gmail.com> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev(a)lists.openstack.org> Date: Thursday, March 16, 2017 at 3:10 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev(a)lists.openstack.org> Subject: Re: [openstack-dev] [ptls] Project On-Boarding Rooms Hello All! I am pleased to see how much interest there is in these onboarding rooms. As of right now I can accommodate all the official projects (sorry Cyborg) that have requested a room to make all the requests fit, I have combined docs and i18n and taken Thierry's suggestion to combine Infra/QA/RelMgmt/Regs/Stable. These are the projects that have requested a slot: Solum Tricircle Karbor Freezer Kuryr Mistral Dragonflow Coudkitty Designate Trove Watcher Magnum Barbican Charms Tacker Zun Swift Watcher Kolla Horizon Keystone Nova Cinder Telemetry Infra/QA/RelMgmt/Regs/Stable Docs/i18n If there are any other projects willing to share a slot together please let me know! -Kendall Nelson (diablo_rojo) On Thu, Mar 16, 2017 at 8:49 AM Jeremy Stanley <fungi(a)yuggoth.org<mailto:fungi@yuggoth.org>> wrote: On 2017-03-16 10:31:49 +0100 (+0100), Thierry Carrez wrote: [...] > I think we could share a 90-min slot between a number of the supporting > teams: > > Infrastructure, QA, Release Management, Requirements, Stable maint > > Those teams are all under-staffed and wanting to grow new members, but > 90 min is both too long and too short for them. I feel like regrouping > them in a single slot and give each of those teams ~15 min to explain > what they do, their process and tooling, and a pointer to next steps / > mentors would be immensely useful. I can see this working okay for the Infra team. Pretty sure I can't come up with anything useful (to our team) we could get through in a 90-minute slot given our new contributor learning curve, so would feel bad wasting a full session. A "this is who we are and what we do, if you're interested in these sorts of things and want to find out more on getting involved go here, thank you for your time" over 10 minutes with an additional 5 for questions could at least be minimally valuable for us, on the other hand. -- Jeremy Stanley __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

2 1

Re: [OpenStack-I18n] [openstack-dev] A Summary of Atlanta PTG Summaries (!)
by Ian Y. Choi 16 Mar '17

16 Mar '17

Hello Hugh, Just I have found that there is a typo: I18n team is "I18n", not "I8n" :) (There are total 18 characters between 'I' and 'n' in "Internationalization" - too long.) Could you fix it? With many thanks, /Ian Hugh Blemings wrote on 3/13/2017 6:30 PM: > Hi Emilien, All, > > On 8/3/17 09:26, Emilien Macchi wrote: >> On Mon, Mar 6, 2017 at 10:45 PM, Hugh Blemings <hugh(a)blemings.org> >> wrote: >>> Hiya, >>> >>> As has been done for the last few Summits/PTGs in Lwood[1] I've pulled >>> together a list of the various posts to openstack-dev that summarise >>> things >>> at the PTG - projects, videos, anecdotes etc. >>> >>> The aggregated list is in this blog post; >>> >>> http://hugh.blemings.id.au/2017/03/07/openstack-ptg-atlanta-2017-summary-of… >>> >>> >>> Which should aggregate across to planet.openstack.org as well. >>> >>> I'll update this as further summaries appear, corrections/contributions >>> welcome. >> >> Thanks Hugh, that's awesome! > > Most welcome :) > >> Can you please remove the first link: TripleO: >> http://lists.openstack.org/pipermail/openstack-dev/2017-February/112893.html >> >> and only keep this one: >> http://lists.openstack.org/pipermail/openstack-dev/2017-February/112995.html >> > > Done, apologies for the delay, got behind in my email this week! > > Cheers, > Hugh > > > __________________________________________________________________________ > > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[I18n] Canceling IRC Meeting this week & asking for opinions
by Ian Y. Choi 15 Mar '17

15 Mar '17

Hello all, Due to my personal business this week, unfortunately I need to cancel the IRC meeting in this week. Instead, I would like to ask I18n team language coordinators and translators to share your opinions for the following topics: - Finalizing Pike translation goal & priorities : Discussion on Mar 02 was 1. Dashboard - Horizon [High] 2. Dashboard Authorization Page [High] 3. Magnum UI [Medium] 4. Trove Dashboard [Medium] 5. Sahara Dashboard [Medium] 6. neutron-lbaas-dashboard [Medium] 7. Murano Dashboard [Low] 8. Designate Dashboard [Low] 9. TripleO-UI [Low] - Thoughts on ATC criteria : Please see more details on https://review.openstack.org/#/c/437188/1/doc/source/official_translator.rst - Release note translation criteria : Please see and tell your thoughts on http://lists.openstack.org/pipermail/openstack-i18n/2017-March/002822.html - Translation checksite using OpenStackAnsible : Frank proposed one infra spec - https://review.openstack.org/#/c/440825/ - Log translation discussion : It would be so important for developers to change upstream codes. Please see & share your thoughts on "[openstack-dev] [i18n] [nova] understanding log domain change" thread in http://lists.openstack.org/pipermail/openstack-dev/2017-March/thread.html - Community Goals for Pike : Following http://lists.openstack.org/pipermail/openstack-dev/2017-March/113269.html is important. : Idea - py3 support is to run pep8 job with python3 (@amotoki) : python scripts (zanata_stats.py, zanata_users.py) running with Python3 would be optional? - Review requests on openstack/i18n & openstack/i18n-specs repository Please feel free tell your opinions (just replying with +1 and/or -1 with simple reasoning would be also fine), and I hope that we will have more ideas on such topics and more topics will be well discussed on the IRC meeting next week. With many thanks, /Ian

2 1

[I18n] IRC Meeting reminder: January 12th at 07:00 UTC
by Ian Y. Choi 15 Mar '17

15 Mar '17

Hello all, I18n team is having our next meeting on January 12th 2017 (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 last IRC meeting minutes and full logs: Minutes: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… Log: http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/opensta… With many thanks, /Ian

3 9

Two I18n presentations on Boston Summit & preparation for Forum is needed: Let's brainstorming!
by Ian Y. Choi 13 Mar '17

13 Mar '17

Hello translators, I have three so delightful news to share with all translators regarding Boston Summit & Forum. First, I would like to happily announce that there will be two presentations with I18n & translation during Boston Summit! [Title: I18n-101: Introduction to translation and contributing qualified translation with useful tips] - Presenters: Zheng Xi Zhou (@zzxwill), Alex Eng (@aeng), Ian Y. Choi (@ianychoi) - Date & Time: Wednesday, May 10, 1:50pm-3:20pm - Track: Hands-on Workshops - More details: [1] [Title: Participating in translation makes you an internationalized OpenStacker & developer] - Presenters: Zheng Xi Zhou (@zzxwill), Jean-François Taltavull (@jftalta), Frank Kloeker (@eumel8) - Date & Time: Thursday, May 11, 1:30pm-2:10pm - Track: How to Contribute - More details: [2] @zzxwill (Chinese language team coordinator) suggested & actively submitted those two presentations and they have been finally accepted as two main presentations. Thanks a lot! Note that I have been notified that [3] was not accepted but approved as an Alternate Session for potential inclusion. If I receive a positive news on [3], then I will take appropriate actions to make the possible panel discussion successfully land on Boston Summit (e.g., more discussion with speakers, well-preparing panel questions, ...). Second, That's not all why it would be so nice and attractive for translators to come to Boston Summit. Forum is also important for I18n! There will be more Forum discussion(s) with I18n people - but not limited to I18n: Zanata dev. team, Infra people, developers and operators. I have created an Etherpad [4] to discuss ideas for nice topics during Boston Forum and included the Etherpad on [5]. We have sufficient time to well organize, prepare, and make successful Forum discussion(s) [6]. Please feel free to share your idea on [4] for fruitful discussions with I18n & translation. Third, recently, I have also heard that all ATCs received 300$ discount codes a few days ago. If you have translated >= 300 words from August 2016 to January 2017 but have not received such discount codes, please check your e-mail inbox with spam folder and if there is no such e-mail for discount codes, then please tell me. For such cases, I will take care of it by checking the exact statistics [7, 8] and asking to Foundation if needed. I hope that many translators will come to Boston, see the presentation sessions, and also discuss I18n & translation feedback + issues for Forum. Let's do brainstorming for Boston Summit & Forum for better I18n & translation world in OpenStack! With many thanks, /Ian [1] https://www.openstack.org/summit/boston-2017/summit-schedule/events/18387/i… [2] https://www.openstack.org/summit/boston-2017/summit-schedule/events/18315/p… [3] https://www.openstack.org/summit/boston-2017/vote-for-speakers#/17919 [4] https://etherpad.openstack.org/p/BOS-I18n-brainstorming [5] https://wiki.openstack.org/wiki/Forum/Boston2017 [6] http://lists.openstack.org/pipermail/openstack-dev/2017-March/113115.html [7] https://review.openstack.org/#/c/417569/ [8] http://git.openstack.org/cgit/openstack/i18n/tree/tools/zanata/zanata_stats…

3 4

[Bug 1671248] Re: liberty install guide is not available in english
by Andreas Jaeger 13 Mar '17

13 Mar '17

Liberty is not supported anymore by OpenStack, please install using a newer version. ** Changed in: openstack-i18n Status: New => Invalid ** Changed in: openstack-manuals Status: New => Invalid -- 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/1671248 Title: liberty install guide is not available in english Status in openstack i18n: Invalid Status in openstack-manuals: Invalid Bug description: I was trying to get to the liberty install guide in english but i was not able to access it. Mitaka and Newton are available To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1671248/+subscriptions

1 0

[Bug 1671248] Re: liberty install guide is not available in english
by Alexandra Settle 13 Mar '17

13 Mar '17

** Also 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/1671248 Title: liberty install guide is not available in english Status in openstack i18n: New Status in openstack-manuals: New Bug description: I was trying to get to the liberty install guide in english but i was not able to access it. Mitaka and Newton are available To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1671248/+subscriptions

1 0

translated release note: import criteria and publishing
by Akihiro Motoki 11 Mar '17

11 Mar '17

Hi i18n team, CC: Doug from the release team. We are now preparing translated version of release notes. I would like to discuss the import criteria of release notes translation. If there is a better way, it would be great. == Problem == Release notes translation is imported when 75% of a PO file is translated. 75% is calculated as a whole. If a language team wants to translate release notes of a specific release, the team needs to translate release notes of other releases. This comes from the fact that the translation percentage is calculated as a whole. The development teams started to use reno for translation at the beginning of Mitaka cycle and Liberty release notes are converted into reno-based release notes. This mean if we want to publish Newton release notes translation, we need to translate release notes for Liberty and Mitaka at the same time. == Proposal == I hope we can publish translated release notes per release. If Newton release notes translation completes, I want to publish Newton release notes. My proposal is to change the import criteria for release notes translation to 75% at least for a specific release. If translation progress of release notes are less than 40% for all releases, a corresponding PO file will be removed from the repo. I proposed an infra scirpt change to implement the above. https://review.openstack.org/#/c/383622/ Proposed threshold 75% and 40% might need to be revisited. == Open question == Do we publish translated release notes for a release with <75% progress? This is about publishing rendered release notes. For example, assume my lang team have translated release notes 90% for Newton, 10% for Mitaka and Liberty. In this case, which is better not to publish Mitaka and Liberty release notes translation or to publish all? My vote is not to publish less-translated version of release notes. == Note == Question from Ian on the gerrit review. By the way, is it possible to see only Newton release note strings in Zanata? Answer: The current Zanata version we use does not support filtering by an original filename. You need to check English release notes like [1] or [2] and search strings on Zanata. [1] https://releases.openstack.org/newton/index.html [2] http://docs.openstack.org/releasenotes/horizon/ Akihiro

6 18

[openstack-docs] [dev] What's up, doc?
by Alexandra Settle 10 Mar '17

10 Mar '17

Team team team team team, It's been a crazy few weeks since the PTG ramping up our goals for Pike! Big thanks to everyone who has really hit the ground running with our new set of objectives. This week I have been helping out Ianeta with the High Availability Guide ToC plan, (which you can review here: https://review.openstack.org/#/c/440890/ ) and Rob Clark with the Security Guide plan (https://etherpad.openstack.org/p/sec-guide-pike ). I have also been working alongside Brian and the nova team to unblock ourselves from a particularly nasty, critical, bug affecting the Install Guide. For more information: https://bugs.launchpad.net/openstack-manuals/+bug/1663485 Big thanks to Darren Chan who has been doing an awesome job for the last two weeks in keeping our bug list under control. We are down to an amazing 108 bugs in queue. Next week, we have Ianeta who will be looking after the bug triage liaison role! If you're sitting there thinking "bugs are for me, I really love triaging bugs!" well, you're in luck! We have a few spots open for the rest of the cycle: https://wiki.openstack.org/wiki/Documentation/SpecialityTeams#Bug_Triage_Te… == Progress towards Pike == https://www.timeanddate.com/countdown/newyear?p0=24&msg=Pike+release&ud=1&f… Bugs closed in Pike: 32! You guys rock :) == The Road to the Summit in Boston == The summit schedule has been announced: https://www.openstack.org/summit/boston-2017/summit-schedule/#day=2017-05-08 I will be representing the docs team at the summit for the new 'Project Update' session. For more information: https://www.openstack.org/summit/boston-2017/summit-schedule/global-search?… Let me know if you had any doc talks accepted! == Speciality Team Reports == API - Anne Gentle: One prominent change is that the Block Storage API v2 is now exactly replicated with v3 and so is now marked Deprecated. The list of all OpenStack APIs is now also here: https://developer.openstack.org/#api and you can see them based on support level here: https://developer.openstack.org/api-guide/quick-start/ Configuration Reference and CLI Reference - Tomoyuki Kato: N/A High Availability Guide - Ianeta Hutchinson: So, we have this patch https://review.openstack.org/#/c/440890/13 to establish the new ToC for HA Guide. We are trying to move all content that is relevant in the current guide over to the new ToC. From there, we will be filing bugs to start collaboration with the OSIC DevOps team who have signed up to adopt-a-guide and will be helping to provide content as SME's. Hypervisor Tuning Guide - Blair Bethwaite: The Scientific-WG is considering proposing a hypervisor tuning + guide session for the Boston Forum though, so hopefully if that goes ahead it will create some renewed interest. Installation guides - Lana Brindley: Waiting to sort out the last couple of bugs before we branch, hopefully next week. Networking Guide - John Davidge: Huge number of patches this week on the RFC 5737 fix[1] - thanks to caoyuan! Continued progress on replacing neutronclient commands with OSC versions. Thank you to all contributors. A patch[2] changing a documented use of ’tenant’ to ‘project’ sparked a discussion in the neutron team about the mixture of terminology in neutron, with the conclusion that all remaining references to ’tenant’ in our config files and elsewhere are to be replaced with ‘project’ as soon as possible. Some of these will require deprecation cycles. Impact on the networking guide should be minimal. [1] https://launchpad.net/bugs/1656378 [2] https://review.openstack.org/#/c/43816 Operations and Architecture Design guides - Darren Chan: A patch to move the draft Arch Guide to docs.o.o has merged. The previous guide has been moved to a "to archive" directory until the archiving process is ready. The Arch Guide working group met this week to rearchitect and scope the design content. We're currently focussed on the storage content. Security Guide - Nathaniel Dillon: Rob Clark (PTL) and Alex are in the process of planning the ins and out of the overhaul of the guide. We're talking about dramatically reducing the scope, and introducing new, maintainable, content. Rob (hyakuhei) is also looking at getting a sprint in Austin at some point to get the security team all together and pump out some content. We also have the OSIC Security team pumping out some of the main, non-wishlist, bugs at preset. Training Guides - Matjaz Pancur: N/A Training labs - Pranav Salunke, Roger Luethi: We have pushed the current state of the Ocata training-labs changeset in case others find it useful. The scripts follow the install-guide and https://review.openstack.org/#/c/438328/ . The resulting cluster cannot launch instances because it fails to find a host (just like others following the install-guide have reported). Admin and User guides - Joseph Robinson: For the User and Admin Guides, I've been looping through the bug list - there are SDK bugs and the issue of moving the python SDK examples, which was discussed back in Newton. There are also two telemetry bugs, which I need to contact the liaisons for. The only other point, is reviewing the Admin Guide migration spec: https://review.openstack.org/#/c/439122/ == Doc team meeting == Our next meeting will be on Thursday, 23 March at 2100 UTC in #openstack-meeting-alt. For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting I am unavailable to be the meeting chair this week :( is someone able to host? Ping or email if you are able to help out! -- Have a great weekend! Alex Fastest typer in the universe (2014) and expert cactus photographer IRC: asettle Twitter: dewsday

1 0

[Bug 1671367] Re: Losing a semicolon in overview page
by Rob Cresswell 10 Mar '17

10 Mar '17

** Also affects: openstack-i18n Importance: Undecided Status: New ** Changed in: horizon Status: In Progress => Invalid -- 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/1671367 Title: Losing a semicolon in overview page Status in OpenStack Dashboard (Horizon): Invalid Status in openstack i18n: New Bug description: Losing a semicolon Behind the "This Period's RAM-Hours". Semicolons should use Chinese, but using the English a semicolon. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1671367/+subscriptions

1 0

[Bug 1671690] [NEW] Use incorrect semicolon
by ZouHuiying 10 Mar '17

10 Mar '17

Public bug reported: Losing a semicolon Behind the "This Period's RAM-Hours". Semicolons should use Chinese, but using the English a semicolon. ** Affects: openstack-i18n Importance: Undecided Assignee: ZouHuiying (zhouhy) Status: New ** Changed in: openstack-i18n Assignee: (unassigned) => ZouHuiying (zhouhy) -- 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/1671690 Title: Use incorrect semicolon Status in openstack i18n: New Bug description: Losing a semicolon Behind the "This Period's RAM-Hours". Semicolons should use Chinese, but using the English a semicolon. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1671690/+subscriptions

1 0

Re: [OpenStack-I18n] [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500
by Ian Y. Choi 09 Mar '17

09 Mar '17

Doug Hellmann wrote on 3/9/2017 9:24 PM: > Excerpts from Sean McGinnis's message of 2017-03-07 07:17:09 -0600: >> On Mon, Mar 06, 2017 at 09:06:18AM -0500, Sean Dague wrote: >>> On 03/06/2017 08:43 AM, Andreas Jaeger wrote: >>>> On 2017-03-06 14:03, Sean Dague wrote: >>>>> I'm trying to understand the implications of >>>>> https://review.openstack.org/#/c/439500. And the comment in the linked >>>>> email: >>>>> >>>>> ">> Yes, we decided some time ago to not translate the log files anymore and >>>>>>> thus our tools do not handle them anymore - and in general, we remove >>>>>>> these kind of files." >>>>> Does that mean that all the _LE, _LI, _LW stuff in projects should be >>>>> fully removed? Nova currently enforces those things are there - >>>>> https://github.com/openstack/nova/blob/e88dd0034b1b135d680dae3494597e295add… >>>>> and want to make sure our tools aren't making us do work that the i18n >>>>> team is ignoring and throwing away. >> So... just looking for a definitive statement on this since there has >> been some back and forth discussion. >> >> Is it correct to say - all projects may (should?) now remove all bits in >> place for using and enforcing the _Lx() translation markers. Only _() >> should be used for user visible error messages. >> >> Sean (smcginnis) >> > The situation is still not quite clear to me, and it would be > unfortunate to undo too much of the translation support work because > it will be hard to redo it. > > Is there documentation somewhere describing what the i18n team has > committed to trying to translate? I18n team describes translation plan and priority in Zanata - translation platform : https://translate.openstack.org/ . > I think I heard that there was a > shift in emphasis to "user interfaces", but I'm not sure if that > includes error messages in services. Should we remove all use of > oslo.i18n from services? Or only when dealing with logs? When I18n team decided to removal of log translations in Barcelona last October, there had been no discussion on the removal of oslo.i18n translation support for log messages. (I have kept track of what I18n team discussed during Barcelona I18n meetup on Etherpad - [1]) Now I think that the final decision of oslo.i18n log translation support needs more involvement with translators considering oslo.i18n translation support, and also more people on community wide including project working groups, user committee, and operators as Matt suggested. If translating log messages is meaningful to some community members and some translators show interests on translating log messages, then I18n team can revert the policy with rolling back of translations. Translated strings are still alive in not only previous stable branches, but also in translation memory in Zanata - translation platform. I would like to find some ways to discuss this topic with more community wide. With many thanks, /Ian [1] https://etherpad.openstack.org/p/barcelona-i18n-meetup > > Doug > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[Bug 1671138] [NEW] network related command returning SSL Error
by Arnaud 09 Mar '17

09 Mar '17

Public bug reported: I'm currently installing openstack following the tutorial for ocata on ubuntu-server. After installing and configuring neutron on the controller and the first compute-node, any command related to the network that I tried failed and returned an SSL Error. openstack extension list --network, openstack network list and openstack network agent list all return : 'unicode' object has no attribute 'get' openstack extension list works fine, same for openstack user/service/project list This is the tail of /var/log/neutron/neutron-server.log 2017-03-08 15:59:40.863 3366 INFO neutron.wsgi [-] 10.0.4.10 - - [08/Mar/2017 15:59:40] "GET / HTTP/1.1" 200 272 0.000515 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors [-] An error occurred during processing the request: GET /v2.0/agents HTTP/1.0 Accept: application/json Accept-Encoding: gzip, deflate Connection: keep-alive Content-Type: text/plain Host: cloudcontroller:9696 User-Agent: openstacksdk/0.9.13 keystoneauth1/2.18.0 python-requests/2.12.4 CPython/2.7.12 X-Auth-Token: ***** 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors Traceback (most recent call last): 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/oslo_middleware/catch_errors.py", line 41, in __call__ 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors response = req.get_response(self.application) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1299, in send 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors application, catch_exc_info=False) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1263, in call_application 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors app_iter = application(self.environ, start_response) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__ 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors resp = self.call_func(req, *args, **self.kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return self.func(req, *args, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 332, in __call__ 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors response = self.process_request(req) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 623, in process_request 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors resp = super(AuthProtocol, self).process_request(request) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 405, in process_request 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors allow_expired=allow_expired) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 435, in _do_fetch_token 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors data = self.fetch_token(token, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 762, in fetch_token 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors allow_expired=allow_expired) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 217, in verify_token 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors auth_ref = self._request_strategy.verify_token( 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 168, in _request_strategy 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors strategy_class = self._get_strategy_class() 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 190, in _get_strategy_class 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors if self._adapter.get_endpoint(version=klass.AUTH_VERSION): 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/adapter.py", line 176, in get_endpoint 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return self.session.get_endpoint(auth or self.auth, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 856, in get_endpoint 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return auth.get_endpoint(self, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_auth.py", line 118, in get_endpoint 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors authenticated=False) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/positional/__init__.py", line 101, in inner 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return wrapped(*args, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/discover.py", line 140, in __init__ 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors authenticated=authenticated) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/positional/__init__.py", line 101, in inner 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return wrapped(*args, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/discover.py", line 40, in get_version_data 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors resp = session.get(url, headers=headers, authenticated=authenticated) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 758, in get 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return self.request(url, 'GET', **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/positional/__init__.py", line 101, in inner 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return wrapped(*args, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 616, in request 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors resp = send(**kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 678, in _send_request 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors raise exceptions.SSLError(msg) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors SSLError: SSL exception connecting to https://127.0.0.1:35357: ("bad handshake: Error([('SSL routines', 'SSL23_GET_SERVER_HELLO', 'unknown protocol')],)",) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors 2017-03-08 15:59:40.876 3366 INFO neutron.wsgi [-] 10.0.4.10 - - [08/Mar/2017 15:59:40] "GET /v2.0/agents HTTP/1.1" 500 419 0.010823 ** 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/1671138 Title: network related command returning SSL Error Status in openstack i18n: New Bug description: I'm currently installing openstack following the tutorial for ocata on ubuntu-server. After installing and configuring neutron on the controller and the first compute-node, any command related to the network that I tried failed and returned an SSL Error. openstack extension list --network, openstack network list and openstack network agent list all return : 'unicode' object has no attribute 'get' openstack extension list works fine, same for openstack user/service/project list This is the tail of /var/log/neutron/neutron-server.log 2017-03-08 15:59:40.863 3366 INFO neutron.wsgi [-] 10.0.4.10 - - [08/Mar/2017 15:59:40] "GET / HTTP/1.1" 200 272 0.000515 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors [-] An error occurred during processing the request: GET /v2.0/agents HTTP/1.0 Accept: application/json Accept-Encoding: gzip, deflate Connection: keep-alive Content-Type: text/plain Host: cloudcontroller:9696 User-Agent: openstacksdk/0.9.13 keystoneauth1/2.18.0 python-requests/2.12.4 CPython/2.7.12 X-Auth-Token: ***** 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors Traceback (most recent call last): 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/oslo_middleware/catch_errors.py", line 41, in __call__ 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors response = req.get_response(self.application) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1299, in send 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors application, catch_exc_info=False) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/request.py", line 1263, in call_application 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors app_iter = application(self.environ, start_response) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__ 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors resp = self.call_func(req, *args, **self.kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return self.func(req, *args, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 332, in __call__ 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors response = self.process_request(req) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 623, in process_request 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors resp = super(AuthProtocol, self).process_request(request) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 405, in process_request 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors allow_expired=allow_expired) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 435, in _do_fetch_token 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors data = self.fetch_token(token, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py", line 762, in fetch_token 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors allow_expired=allow_expired) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 217, in verify_token 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors auth_ref = self._request_strategy.verify_token( 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 168, in _request_strategy 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors strategy_class = self._get_strategy_class() 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_identity.py", line 190, in _get_strategy_class 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors if self._adapter.get_endpoint(version=klass.AUTH_VERSION): 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/adapter.py", line 176, in get_endpoint 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return self.session.get_endpoint(auth or self.auth, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 856, in get_endpoint 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return auth.get_endpoint(self, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystonemiddleware/auth_token/_auth.py", line 118, in get_endpoint 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors authenticated=False) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/positional/__init__.py", line 101, in inner 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return wrapped(*args, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/discover.py", line 140, in __init__ 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors authenticated=authenticated) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/positional/__init__.py", line 101, in inner 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return wrapped(*args, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/discover.py", line 40, in get_version_data 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors resp = session.get(url, headers=headers, authenticated=authenticated) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 758, in get 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return self.request(url, 'GET', **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/positional/__init__.py", line 101, in inner 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors return wrapped(*args, **kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 616, in request 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors resp = send(**kwargs) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors File "/usr/lib/python2.7/dist-packages/keystoneauth1/session.py", line 678, in _send_request 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors raise exceptions.SSLError(msg) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors SSLError: SSL exception connecting to https://127.0.0.1:35357: ("bad handshake: Error([('SSL routines', 'SSL23_GET_SERVER_HELLO', 'unknown protocol')],)",) 2017-03-08 15:59:40.875 3366 ERROR oslo_middleware.catch_errors 2017-03-08 15:59:40.876 3366 INFO neutron.wsgi [-] 10.0.4.10 - - [08/Mar/2017 15:59:40] "GET /v2.0/agents HTTP/1.1" 500 419 0.010823 To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1671138/+subscriptions

2 1

Re: [OpenStack-I18n] [openstack-dev] [i18n] [nova] understanding log domain change - https://review.openstack.org/#/c/439500
by Ian Y. Choi 06 Mar '17

06 Mar '17

Doug Hellmann wrote on 3/7/2017 12:53 AM: > Excerpts from Sean Dague's message of 2017-03-06 09:06:18 -0500: >> On 03/06/2017 08:43 AM, Andreas Jaeger wrote: >>> On 2017-03-06 14:03, Sean Dague wrote: >>>> I'm trying to understand the implications of >>>> https://review.openstack.org/#/c/439500. And the comment in the linked >>>> email: >>>> >>>> ">> Yes, we decided some time ago to not translate the log files anymore and >>>>>> thus our tools do not handle them anymore - and in general, we remove >>>>>> these kind of files." >>>> Does that mean that all the _LE, _LI, _LW stuff in projects should be >>>> fully removed? Nova currently enforces those things are there - >>>> https://github.com/openstack/nova/blob/e88dd0034b1b135d680dae3494597e295add… >>>> and want to make sure our tools aren't making us do work that the i18n >>>> team is ignoring and throwing away. >>> Sean, this was removed as followup to: >>> >>> http://lists.openstack.org/pipermail/openstack-i18n/2016-November/002574.ht… >>> >>> Let me copy Ian as i18n PTL, >>> >>> Andreas >> That all seems reasonable, and I'm happy to follow the i18n team's lead >> here. It is however a significant reversal of policy, and there is >> substantial code infrastructure in projects (like Nova) to support the >> old policy. >> >> So if this is new policy, a much wider dissemination of it would be >> welcomed, as it means we can purge this infrastructure from projects >> like Nova. >> >> -Sean >> > Yes, we went to a great deal of trouble to enable log translations, > so I'm surprised to see it being dropped to quickly. I don't > necessarily disagree with the decision, because I know translator > time is limited. But it would be nice to have the discussion here, +1 and for such discussions including openstack-i18n(a)lists.openstack.org mailing list would be also nice :) On Barcelona Design Summit, there were I18n contributor meetup and I18n team members discussed a lot. One of things was not to translate log-level strings for server projects. Note that such decision was made not because translator time is limited. Log messages are important to better identify which errors are being posed and most operators (+ developers) diagnose and start to solve error situations from the log messages. I18n team previously translated log messages a lot especially thanks to translation contribution from IBM. (AFAIK) However, after then, there have been some voices - why I18n team translated log messages? After listening to the voices in details, I18n team identified that the background of such voices was related with searching log messages on Internet. Searching English log messages on the Internet will retrieve more number of results than searching translated log messages on the Internet. Translating log messages now has two different point of views: - Will be useful for OpenStack users to better understand log messages in details with translated log messages? - Or will not be useful for OpenStack users because the original log messages will have better chance to find solutions who occurred the similar cases on the Internet? I18n team discussed with such point of views and on Barcelona Summit the latter point would be more important than the former point. Also, it would be just a point of view from PTL, but it is difficult for me to encourage to contribution translations which have such kind of controversy. Now I would like to listen again to not only developers, but also operators and translators - for log string translation. If someone thinks that the former point would be more important than the latter point, please share through this mailing list to reconsider the current decision. With many thanks, /Ian > instead of on a list most of the community isn't subscribed to, so > everyone involved can understand the reason for the change and so > the folks who asked for it originally can be included in the > conversation. As Sean points out, the policy change has a lot of > other implications about how logging is handled throughout the > applications. > > Doug > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

2 1

Pike goals
by Kato, Tomoyuki 06 Mar '17

06 Mar '17

Hi Ian, As you may or may not know, it is time to set Pike goals. https://governance.openstack.org/tc/goals/pike/index.html Regards, KATO Tomoyuki

1 0

New ESL chapter in Contributor Guide
by Lana Brindley 06 Mar '17

06 Mar '17

Hi everyone! I just wanted to let you know that docs merged a new chapter into the Contributor Guide over the weekend: https://docs.openstack.org/contributor-guide/non-native-english-speakers.ht… As so many of you represent non-English speaking cultures, I would love to ask you to update this chapter over time, especially if you have things to share from your own culture, or tips or tricks that have helped you out. I hope that this becomes a valuable resource for us all, as we strive to make OpenStack more diverse and inclusive. Thanks! Lana -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

2 1

Fwd: [ptl][release] Pike release management communications
by Ian Y. Choi 04 Mar '17

04 Mar '17

Hello, I am looking for the volunteer for I18n Release Management cross-project liaison. Could someone help this role? The more details on I18n team activities with release are currently written in: https://docs.openstack.org/developer/i18n/release_management.html and I am finding colleague(s) who will co-work with Release Management team and me (current I18n PTL) to more precisely define team activities with release, do with fun, and make me not to forget release activities :) Please reply to me by the end of next week (March 10) if anyone is interested in. @ttx: I am copying this as ack :) With many thanks, /Ian -------- Original Message -------- Subject: [ptl][release] Pike release management communications Date: Fri, 3 Mar 2017 16:56:30 +0100 From: Thierry Carrez <thierry(a)openstack.org> Organization: OpenStack To: OpenStack Development Mailing List <openstack-dev(a)lists.openstack.org> CC: a.chadin(a)servionica.ru, adrian.otto(a)rackspace.com, alexandrelevine(a)gmail.com, amrith(a)amrith.org, andrea.frittoli(a)gmail.com, andr.kurilin(a)gmail.com, andy.mccrae(a)gmail.com, antonisp(a)celebdor.com, aschultz(a)redhat.com, a.settle(a)outlook.com, ben(a)swartzlander.org, brian.rosmaita(a)rackspace.com, cbelu(a)cloudbasesolutions.com, cdiep(a)us.ibm.com, christophe.sauthier(a)objectif-libre.com, dmccowan(a)cisco.com, dtantsur(a)redhat.com, dtroyer(a)gmail.com, ekcs.openstack(a)gmail.com, emilien(a)redhat.com, eng.szaher(a)gmail.com, eran(a)itsonlyme.name, eric.guo(a)easystack.cn, felipe.monteiro(a)att.com, flwang(a)catalyst.net.nz, fungi(a)yuggoth.org, gong.yongsheng(a)99cloud.net, hongbin.lu(a)huawei.com, hyakuhei(a)gmail.com, ianyrchoi(a)gmail.com, ifat.afek(a)nokia.com, inc007(a)gmail.com, iyozhikov(a)mirantis.com, james.page(a)ubuntu.com, j.klare(a)cloudbau.de, joehuang(a)huawei.com, johnsomor(a)gmail.com, julien(a)danjou.info, kevin(a)benton.pub, kulkarni.devdatta(a)gmail.com, lbragstad(a)gmail.com, me(a)not.mn, mriedem(a)us.ibm.com, omer.anson(a)toganetworks.com, renat.akhmerov(a)gmail.com, rico.lin.guanyu(a)gmail.com, robert.cresswell(a)outlook.com, roland.hochmuth(a)hpe.com, sean_mcginnis(a)dell.com, steven.j.mclellan(a)gmail.com, tengqim(a)cn.ibm.com, tenobreg(a)redhat.com, thierry(a)openstack.org, tim.simmons(a)rackspace.com, tony(a)bakeyournoodle.com, vkuklin(a)mirantis.com, yuval(a)brik.org.il, zigo(a)debian.org, zxkuqyb(a)gmail.com Hello, fellow PTLs, As Doug did for the past few cycles, I want to start the Pike cycle by making sure the expectations for communications with the release team are clear to everyone so there is no confusion or miscommunication about any of the process or deadlines. This email is being sent to the openstack-dev mailing list as well as the PTLs of all official OpenStack projects individually, to improve the odds that all of the PTLs see it. Note that future release-related emails will *not* be CCed to all individual PTLs. (If you were a PTL/release liaison last cycle, feel free to skip ahead to the "things for you to do right now" section at the end.) The release liaison for your project is responsible for coordinating with the release management team, validating your team release requests, and ensuring that the release cycle deadlines are met. If you don't nominate a release liaison for your project (something I encourage you to do), this task falls back to the PTL. Note that release liaisons do not have to be core reviewers. Please ensure that your liaison has the time and ability to handle the communication necessary to manage your release: the release team is here to facilitate, but finishing the release work is ultimately the responsibility of the project team. Failing to follow through on a needed process step may block you from successfully meeting deadlines or releasing. In particular, our release milestones and deadlines are date-based, not feature-based. When the date passes, so does the milestone. If you miss it, you miss it. A few of you ran into problems in past cycles because of missed communications. My goal is to have all teams meet all deadlines during Pike. We came very very close for Ocata; please help by keeping up to date on deadlines. To ensure smooth coordination, we rely on three primary communication tools: 1. Email, for announcements and asynchronous communication. The release management team will be using the "[release]" topic tag on the openstack-dev mailing list for important messages. This includes weekly countdown emails with details on focus, tasks, and upcoming dates. As PTL or release liaison, you should ensure that you see and read those messages (by configuring your mailing list subscription and email client as needed) so that you are aware of all deadlines, process changes, etc. 2. IRC, for time-sensitive interactions. With more than 50 teams involved, the three members of the release team can't track you each of you down when there is a deadline. We rely on your daily presence in the #openstack-release IRC channel during deadline weeks. You are, of course, welcome to stay in channel all the time, but we need you to be there at least during deadline weeks. 3. Written documentation, for relatively stable information. The release team has published the schedule for the Pike cycle to http://releases.openstack.org/pike/schedule.html. Although I will highlight dates in the countdown emails, you may want to add important dates from the schedule to your calendar. One way to do that is to subscribe to the ICS feed for community-wide deadlines: https://releases.openstack.org/schedule.ics Note that the Pike cycle overlaps with summer holidays in the northern hemisphere. If you are planning time off, please make sure your duties are being covered by someone else on the team. Its best to let the release team know in advance so we don't delay approval for release requests from someone we dont recognize, waiting for your +1. Things for you to do right now: 1. Update your release liaison on https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management 2. Make sure your IRC nickname and email address listed in http://git.openstack.org/cgit/openstack/governance/tree/reference/projects.… are correct. The release team, foundation staff, and TC all use those contact details to try to reach you at important points during the cycle. Please make sure they are correct, and that the email address delivers messages to a mailbox you check regularly. 3. Update your mail filters to ensure you see messages sent to the openstack-dev list with [release] in the subject line. 4. Reply to this message, off-list, to me so I know that you have received it. A simple “ack” is enough :) -- Thierry Carrez (ttx) Release Management PTL

1 0

[Bug 1669029] [NEW] Überprüfung der Funktion in Installation Guide
by Günther Stattenberger 03 Mar '17

03 Mar '17

Public bug reported: Hi, - [x] This doc is inaccurate in this way: the first step of verification fails: root@openstack_ocata_control:~# openstack compute service list Unable to establish connection to http://openstack_ocata_control:8774/v2.1/d978aa0e55e141508b4c8e1113bdafa8/o… Can anybody help? I followed the steps for installing ocata on debian up to this point with one small modification: on the controller node, in /etc/nova/nova.conf there is no section [api], so the auth_strategy = keystone goes to section [DEFAULT] netstat shows: root@openstack_ocata_control:~# netstat -l |grep 8774 tcp 0 0 *:8774 *:* LISTEN Thanks! ----------------------------------- Release: 0.1 on 2017-03-01 12:21 SHA: d7845ae2ddb3f222b496b40416cfb7ba1a38eac5 Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install… URL: https://docs.openstack.org/draft/de/install-guide-debian/nova-verify.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/1669029 Title: Überprüfung der Funktion in Installation Guide Status in openstack i18n: New Bug description: Hi, - [x] This doc is inaccurate in this way: the first step of verification fails: root@openstack_ocata_control:~# openstack compute service list Unable to establish connection to http://openstack_ocata_control:8774/v2.1/d978aa0e55e141508b4c8e1113bdafa8/o… Can anybody help? I followed the steps for installing ocata on debian up to this point with one small modification: on the controller node, in /etc/nova/nova.conf there is no section [api], so the auth_strategy = keystone goes to section [DEFAULT] netstat shows: root@openstack_ocata_control:~# netstat -l |grep 8774 tcp 0 0 *:8774 *:* LISTEN Thanks! ----------------------------------- Release: 0.1 on 2017-03-01 12:21 SHA: d7845ae2ddb3f222b496b40416cfb7ba1a38eac5 Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install… URL: https://docs.openstack.org/draft/de/install-guide-debian/nova-verify.html To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1669029/+subscriptions

2 1

[Bug 1669037] Re: [I18N]localized Chinese po file of api-quick-start is broken
by Ian Y. Choi 03 Mar '17

03 Mar '17

@junhuihe, thanks a lot for such following. I want you to change it since I think you and jian.song have the credit for such change suggestion, but it you think submitting into Zanata by you would take time and if you are fine for others to change translations in Zanata, then I think @zzxwill will kindly help it. ** Project changed: openstack-api-site => openstack-i18n ** 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/1669037 Title: [I18N]localized Chinese po file of api-quick-start is broken Status in openstack i18n: New Bug description: Locale:Chinese(zh_CN) Steps to reproduce: 1.add language setting in api-site\api-quick-start\source\conf.py language = 'zh_CN' 2.add extra packages to enable zh_CN in sphinx. git clone https://github.com/bosbyj/sphinx.search.zh_CN 3.run building html with command tox -e api-quick-start 4.error occurred and the build Error Message: Inline interpreted text or hprase reference start-string without end-string. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1669037/+subscriptions

1 0

[Bug 1669037] [NEW] [I18N]localized Chinese po file of api-quick-start is broken
by Launchpad Bug Tracker 03 Mar '17

03 Mar '17

You have been subscribed to a public bug: Locale:Chinese(zh_CN) Steps to reproduce: 1.add language setting in api-site\api-quick-start\source\conf.py language = 'zh_CN' 2.add extra packages to enable zh_CN in sphinx. git clone https://github.com/bosbyj/sphinx.search.zh_CN 3.run building html with command tox -e api-quick-start 4.error occurred and the build Error Message: Inline interpreted text or hprase reference start-string without end-string. ** Affects: openstack-i18n Importance: Undecided Assignee: JunhuiHe (junhuihe) Status: New -- [I18N]localized Chinese po file of api-quick-start is broken https://bugs.launchpad.net/bugs/1669037 You received this bug notification because you are a member of OpenStack I18n Core Team, which is subscribed to openstack i18n.

1 0

[I18n] Translation platform may be unstable or down during 2/27 - 3/3 due to upgrade
by Ian Y. Choi 02 Mar '17

02 Mar '17

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+%22Impo… [3] http://status.openstack.org/openstack-health/#/g/build_queue/post?groupKey=… [4] http://status.openstack.org/openstack-health/#/g/build_queue/periodic?group… [5] http://zanata.org

4 5

[i18n] Translation for logs in keystone removed
by Alfredo Moralejo Alonso 01 Mar '17

01 Mar '17

Hi openstack-i18n, I've observed that all *-log-*.po files have been removed from keystone project in https://review.openstack.org/#/c/437811/ . This is making compile_catalog command to fail as it expects those files to exist in [1]. Is this expected?, will translation for all log files be removed from projects?, if so changes in setup.cfg should be coordinated when needed. Best regards, Alfredo [1] https://github.com/openstack/keystone/blob/master/setup.cfg#L54

3 4

Temporary glossary deletion
by Kato, Tomoyuki 26 Feb '17

26 Feb '17

Hi I18n team, As preparation for Zanata upgrade, I will remove the glossaries temporarily. The new Zanata has the feature, language specific glossary, but it cannot migrate the current glossary into the new one. However, I will upload the glossaries again just after upgrade. Sorry for your inconvenience. KATO Tomoyuki

3 2

Re: [OpenStack-I18n] [OpenStack-docs] FW: Team photo reminder :)
by Edgar Magana 25 Feb '17

25 Feb '17

A good looking team! I hate that I missed the PTG! Edgar From: Alexandra Settle <a.settle(a)outlook.com> Date: Wednesday, February 22, 2017 at 11:30 AM To: "openstack-docs(a)lists.openstack.org" <openstack-docs(a)lists.openstack.org>, "openstack-i18n(a)lists.openstack.org" <openstack-i18n(a)lists.openstack.org> Subject: [OpenStack-docs] FW: Team photo reminder :) Hi everyone! Attached are our team’s (docs and i18n) photos from the PTG :) Thanks, Alex From: Kendall Nelson <kennelson11(a)gmail.com> Date: Tuesday, February 21, 2017 at 4:07 PM To: "a.settle(a)outlook.com" <a.settle(a)outlook.com> Subject: Re: Team photo reminder :) Here are the photos! On Tue, Feb 21, 2017 at 9:24 AM Kendall Nelson <kennelson11(a)gmail.com<mailto:kennelson11@gmail.com>> wrote: 10:30 outside Grand ballroom A 3rd floor! -Kendall Nelson

5 4

[I18n] Pike PTG Summary
by Ian Y. Choi 24 Feb '17

24 Feb '17

Hello all, I18n team participated in PTG for horizontal discussions with the tight collaboration of Documentation team on Monday and Tuesday. Also, there were a few collaboration sessions with Infrastructure, Horizon, Release Management, and OpenStackAnsible team on Wednesday & Thursday in a reservable room. The following is the summary of what I18n team discussed with other project teams. More details for I18n issues are available at: https://etherpad.openstack.org/p/i18n-ptg-pike-topics 1. Documentation / I18n (Monday & Tuesday) The details of all discussions with Docs & I18n teams are written in: https://etherpad.openstack.org/p/docs-i18n-ptg-pike , and I would like to summarize mainly I18n issues (For Documentation topic summary, please see [1]). - For Horizon strings, Documentation team & I18n team identified : Documentation team wants to implement automated screenshot functionality for user-guide. Then, stable DevStack instance would be fine with adding the functionality. : On the other hand, I18n team wants to implement translation checksite which requires re-import of translated strings to review translated strings after around Soft & Hard StringFreezes. - Agreed that archiving & versioning [2] translated documents are also the target with consideration. - Defined url policy for translated project specific install guides : https://docs.openstack.org/<deliverable>/<projectname>/<lang>/ (e.g., https://docs.openstack.org/project-install-guide/baremetal/ja/newton/ ) - I18n team will implement to generate translated PDF documents after pdf implementation spec [3] is successfully landed. - I18n team discussed the approach for implementing translation checksite, I18n contributor guide translation, considering different release models, and solving Stackalytics integration issues. 2. Infrastructure + I18n (Wednesday) + OpenStackAnsible + Horizon (Thursday) - Translation platform ( https://translate.openstack.org ) is now ready for upgrade. - There will be upgrade during 2/27 - 3/3. Translation platform might not work due to upgrade progress. - openstackid-dev developer will test authentication with Zanata using https://translate-dev.o.o from next week - I18n team will automate to propose ATC status rather than current manual proposal work as extra-ATCs using upgraded translation platform. - Implementing translation checksite with OpenStackAnsible will be a feasible solution in OpenStack Infrastructure. I18n team will start to implement translation checksite using OpenStackAnsible from Pike cycle (spec [4] needs to be changed). - Discussed how to Improve algorithms to match Zanata ID with Launchpad & Gerrit ID in Stackalytics 3. Horizon I18n collaboration session w/ Release Management team - Shared current status of I18n team’s translation priority : I18n team sets the highest priority during Soft & Hard StringFreezes to include more qualified translated strings as much as possible for Horizon & Horizon plugin projects. - I18n team shared Ocata cycle experience: cycle-with-milestone, cycle-with-intermediary, and cycle-trailing release models for Horizon plugin projects are not matched with Soft & Hard StringFreeze periods. - Discussed & drawn a new proposal to consider translations for Horizon plugin projects : I18n team will consider Soft & Hard StringFreeze for the projects which follow cycle-with-milestone release model. : I18n team will also consider translation with releases for the projects which follow cycle-with-intermediary release model if they are fine following deadlines. : I18n team will propose a specification to tag (e.g., with “translate”) for projects which are the target of translations with managing stable branches in translation platform. : For cycle-trailing release models, I18n will consider translations with managing stable versions in translation platform if there is I18n cross-project liaison [5] for the project. : I18n team will higher priority for projects which have I18n cross-project liaison. - I18n team will ask to Zanata development team to automate to create new stable versions in Zanata, copying master translations over. I great appreciate all the help and support from especially Alex - Pike Docs PTL to help successfully land collaboration room with I18n team, and also many project team contributors to participate in the discussion and draw nice, and cool approach for better internationalization. With many thanks, /Ian [1] http://lists.openstack.org/pipermail/openstack-dev/2017-February/112885.html [2] http://specs.openstack.org/openstack/docs-specs/specs/pike/archiving.html [3] http://specs.openstack.org/openstack/docs-specs/specs/ocata/build-pdf-from-… [4] http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_ch… [5] https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n

1 0

[openstack-docs] [dev] What's up, Doc?
by Alexandra Settle 24 Feb '17

24 Feb '17

Team team team team team, Welcome to my second edition of What's up, Doc! We have had an extremely busy week in Atlanta for the PTG. We had a really enthusiastic attendance and I am truly impressed by how much we have managed to get done. This newsletter will be a short one and focus on a small PTG update! Our bug triager for the first 2 weeks of Pike is Darren Chan. Looking for more people to sign up and help out: https://wiki.openstack.org/wiki/Documentation/SpecialityTeams#Bug_Triage_Te… == Progress towards Pike == Thanks to our amazing release managers, Maria, Brian and Lana for all their amazing hard work on the Ocata release. Big thanks to Anne for stepping in at the last minute! * 44 days to go! https://www.timeanddate.com/countdown/newyear?p0=24&msg=Pike+release&ud=1&f… == The Road to the Summit in Boston == Voting is now open for topics. You can find the list of topics here: https://www.openstack.org/summit/boston-2017/vote-for-speakers#/ I was able to find some documentation related topics. If anyone has any more topics I am unaware of, please reply to this email thread and share your talks! Please vote for your fellow documenter below: 1. https://www.openstack.org/summit/boston-2017/vote-for-speakers#/17888 2. https://www.openstack.org/summit/boston-2017/vote-for-speakers#/18078 3. https://www.openstack.org/summit/boston-2017/vote-for-speakers#/17711 Event info is available here: http://www.openstack.org/ptg Purchase tickets here: https://pikeptg.eventbrite.com/ Tickets for the Boston summit: https://www.openstack.org/summit/boston-2017/ == PTG Update == We had a very successful PTG! Thanks to all those that were able to attend. Thanks to Ian Choi and the I18n team for being wonderful collaborators. We were able to get a lot done in our horizontal sessions. For anyone that is interested, here's our etherpad with all the notes from the sessions: https://etherpad.openstack.org/p/docs-i18n-ptg-pike Here are a few of the exciting things to look out for in Pike: 1. High Availability Guide improvements a. Adam Spiers and Ianeta Hutchinson will be leading the charge on the HA guide with a massive restructure and up-to-date new content. 2. Reno release notes for OpenStack manuals a. Adam Spiers has been working alongside John Davidge and the Infra team to work on implementing the reno release notes process for documentation. Including looking at implementing new reno templates to work specifically for documentation! 3. Networking Guide improvements and more collaboration with the neutron team. a. John Davidge has been working with the neutron team to develop the best way to ensure information flows into the guide. Discussions around the use of the DocImpact tag were successful. 4. Administrator Guide changes! Keep your eye out for exciting developments. a. Ildiko Vancsa and Joseph Robinson will be working together to come up with a new specification to implement in Queens for our Administration Guide. Development teams have been enthusiastic about implementing the project-install-guide and are looking for similar structures with the Admin Guide. Stay tuned for more news here! I had the opportunity to report back to meeting attendees yesterday afternoon, if anyone would like to know more, here are the meeting minutes: http://eavesdrop.openstack.org/meetings/docteam/2017/docteam.2017-02-23-20.… == Doc team meeting == Our next meeting will be on Thursday 9 March at 2100 UTC in #openstack-meeting-alt. Meeting chair will be me (Alexandra Settle - asettle)! \o/ For more meeting details, including minutes and the agenda: https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting -- Have a great weekend! Alex Lamp enthusiast and award winning marathon sleeper IRC: asettle Twitter: dewsday

2 2

Fwd: Greek language team.
by Ian Y. Choi 22 Feb '17

22 Feb '17

Oops.. I have forgot including with our important mailing list as a recipient. FYI With many thanks, /Ian ---------- Forwarded message ---------- From: Ian Y. Choi <ianyrchoi(a)gmail.com> Date: Wed, Feb 22, 2017 at 2:50 PM Subject: Re: [OpenStack-I18n] Greek language team. To: Dimosthenis Trichakis <dtrich0(a)gmail.com> Hello, I am attending now PTG and my response would be slow. But, I have just found that Greek team is already in Zanata and I have added your Zanata into Greek Language team. Currently, Efstathios Iosifidis is Greek language coordinator but unfortunately I have not discussed with the guy at least for one year. It would be great if you also discuss Greek translation with Efstathios and I welcome you to come to I18n IRC meeting to discuss more translation-side things if you would like to ask or discuss : https://wiki.openstack.org/wiki/Meetings/I18nTeamMeeting By the way, which projects are you interested in translations? (e.g., Horizon, Install-guide, and so on) With many thanks, /Ian On Wed, Feb 22, 2017 at 6:21 AM, Dimosthenis Trichakis <dtrich0(a)gmail.com> wrote: > Hi there, > > I'm a telecom engineer and I would like to learn about cloud technologies. > I'm a linux user for more than a decade and I like to contribute as much as > I can. From my point of view a good way to contribute and at the same time > to learn is translating projects. > I would like to request the creation of Greek Language team. > My user name in Zanata platform is dtrich0 and my Openstack member ID is > 83507. > > Regards, > > Dimosthenis Trichakis > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n > >

1 0

glossary, translation changes order
by Robert Simai 22 Feb '17

22 Feb '17

Hi, while working in the "openstack-manuals master Documents (de) doc/common/source/locale/common" tree in Zanata I noticed, by translating the technical terms we're apparently changing the order. As an example, the term "Image" in German becomes "Abbild" and while it originally was under "I", now it should be under "A". But as far as I understand it won't since the order is given in the file "doc/common/ glossary.rst" which is the source of these strings. Am I right, and is this what happens? Or is there some "intelligence" that assembles the final documentation in the correct (alphabetical) order? -- Thanks, Robert

2 1

FW: Team photo reminder :)
by Alexandra Settle 22 Feb '17

22 Feb '17

Hi everyone! Attached are our team’s (docs and i18n) photos from the PTG :) Thanks, Alex From: Kendall Nelson <kennelson11(a)gmail.com> Date: Tuesday, February 21, 2017 at 4:07 PM To: "a.settle(a)outlook.com" <a.settle(a)outlook.com> Subject: Re: Team photo reminder :) Here are the photos! On Tue, Feb 21, 2017 at 9:24 AM Kendall Nelson <kennelson11(a)gmail.com<mailto:kennelson11@gmail.com>> wrote: 10:30 outside Grand ballroom A 3rd floor! -Kendall Nelson

1 0

Greek language team.
by Dimosthenis Trichakis 22 Feb '17

22 Feb '17

Hi there, I'm a telecom engineer and I would like to learn about cloud technologies. I'm a linux user for more than a decade and I like to contribute as much as I can. From my point of view a good way to contribute and at the same time to learn is translating projects. I would like to request the creation of Greek Language team. My user name in Zanata platform is dtrich0 and my Openstack member ID is 83507. Regards, Dimosthenis Trichakis

1 0

[Bug 1666020] [NEW] Typo in Install Guide keystone-verify (japanese)
by suguru sugiyama 21 Feb '17

21 Feb '17

Public bug reported: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. input セキュリティーのため、一時認証トークンメカニズムを無効化します。 /etc/keystone/keystone-paste.ini ファイルを編集して、admin_token_auth、[pipeline:public_api]、[pipeline:admin_api] セクションから admin_token_auth を削除します。 output セキュリティーのため、一時認証トークンメカニズムを無効化します。 /etc/keystone/keystone-paste.ini ファイルを編集して、admin_token_auth、[pipeline:public_api]、[pipeline:admin_api] セクションから admin_token_auth を削除します。 ----------------------------------- Release: 0.1 on 2017-02-18 10:08 SHA: e9d309bbe9bdb9b83a023d4487a51f392adddce0 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/newton/ja/install-guide-rdo/keystone-verify.html ** Affects: openstack-i18n Importance: Undecided Status: New ** Tags: install-guide ** Description changed: - This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - - [x] I have a fix to the document that I can paste below including example: input and output. + - [x] I have a fix to the document that I can paste below including example: input and output. + input セキュリティーのため、一時認証トークンメカニズムを無効化します。 /etc/keystone/keystone-paste.ini ファイルを編集して、admin_token_auth、[pipeline:public_api]、[pipeline:admin_api] セクションから admin_token_auth を削除します。 - output セキュリティーのため、一時認証トークンメカニズムを無効化します。 /etc/keystone/keystone-paste.ini ファイルを編集して、admin_token_auth、[pipeline:public_api]、[pipeline:admin_api] セクションから admin_token_auth を削除します。 - - - - If you have a troubleshooting or support issue, use the following resources: - - - Ask OpenStack: http://ask.openstack.org - - The mailing list: http://lists.openstack.org - - IRC: 'openstack' channel on Freenode - ----------------------------------- Release: 0.1 on 2017-02-18 10:08 SHA: e9d309bbe9bdb9b83a023d4487a51f392adddce0 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/newton/ja/install-guide-rdo/keystone-verify.html -- 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/1666020 Title: Typo in Install Guide keystone-verify (japanese) Status in openstack i18n: New Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: ______ - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. input セキュリティーのため、一時認証トークンメカニズムを無効化します。 /etc/keystone/keystone-paste.ini ファイルを編集して、admin_token_auth、[pipeline:public_api]、[pipeline:admin_api] セクションから admin_token_auth を削除します。 output セキュリティーのため、一時認証トークンメカニズムを無効化します。 /etc/keystone/keystone-paste.ini ファイルを編集して、admin_token_auth、[pipeline:public_api]、[pipeline:admin_api] セクションから admin_token_auth を削除します。 ----------------------------------- Release: 0.1 on 2017-02-18 10:08 SHA: e9d309bbe9bdb9b83a023d4487a51f392adddce0 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/newton/ja/install-guide-rdo/keystone-verify.html To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1666020/+subscriptions

2 1

[PTG] Remote session for I18n from 19:40 to 20:10 UTC today
by Ian Y. Choi 21 Feb '17

21 Feb '17

Hello, I am a little bit sorry to write this thing so late. But there will be a remote session on from 19:40 to 20:10 UTC today. Please refer to timezone information : https://www.timeanddate.com/worldclock/meetingtime.html?iso=20170221&p1=25&… The topics are now available (and will be changed dynamically) through : https://etherpad.openstack.org/p/docs-i18n-ptg-pike With many thanks, /Ian

1 0

[Bug 1666429] [NEW] 安装和配置 in Installation Guide
by lenmo 21 Feb '17

21 Feb '17

Public bug reported: https://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/glance- install.html when edit the config /etc/glance/glance-api.conf [keystone_authtoken] ... auth_uri = http://controller:5000 auth_url = http://controller:35357 it should be configed like this [keystone_authtoken] ... auth_uri = http://controller:5000 identity_uri = http://controller:35357 ----------------------------------- Release: 0.1 on 2017-02-15 15:23 SHA: 19650f4248540f2c7b27951252a288b2c3d06569 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/glance-install.ht… ** 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/1666429 Title: 安装和配置 in Installation Guide Status in openstack i18n: New Bug description: https://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/glance- install.html when edit the config /etc/glance/glance-api.conf [keystone_authtoken] ... auth_uri = http://controller:5000 auth_url = http://controller:35357 it should be configed like this [keystone_authtoken] ... auth_uri = http://controller:5000 identity_uri = http://controller:35357 ----------------------------------- Release: 0.1 on 2017-02-15 15:23 SHA: 19650f4248540f2c7b27951252a288b2c3d06569 Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-… URL: https://docs.openstack.org/mitaka/zh_CN/install-guide-rdo/glance-install.ht… To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1666429/+subscriptions

1 1

Re: [OpenStack-I18n] [OpenStack-docs] [openstack-docs][i18n] PTG team photos
by Alexandra Settle 21 Feb '17

21 Feb '17

Just by the 10 minutes or so that it will take us to take the photos :) We will endeavor to do both. Does this work? From: "Silverman, Ben" <Ben.Silverman(a)onx.com> Date: Monday, February 20, 2017 at 1:59 PM To: Alexandra Settle <a.settle(a)outlook.com>, "openstack-docs(a)lists.openstack.org" <openstack-docs(a)lists.openstack.org>, "openstack-i18n(a)lists.openstack.org" <openstack-i18n(a)lists.openstack.org> Subject: Re: [OpenStack-docs] [openstack-docs][i18n] PTG team photos Are we then going to push the schedule back since the Arch blueprints section is at the same time. -B -- Ben Silverman | Principal Cloud Architect OnX Enterprise Solutions 20830 N. Tatum Blvd Suite 210 Phoenix, AZ 85050 Mobile 623-252-4506 ben.silverman(a)onx.com<mailto:ben.silverman@onx.com> [cid:image001.png@01D28BCB.E660EF20]<https://www.linkedin.com/in/benjsilverman> From: Alexandra Settle <a.settle(a)outlook.com> Date: Monday, February 20, 2017 at 1:07 PM To: "openstack-docs(a)lists.openstack.org" <openstack-docs(a)lists.openstack.org>, "openstack-i18n(a)lists.openstack.org" <openstack-i18n(a)lists.openstack.org> Subject: [OpenStack-docs] [openstack-docs][i18n] PTG team photos Hi team, For all those at the PTG (docs and I18n) – we have a joint team photo session booked for 10.30am, Tuesday morning. The location we are taking the photos on the 3rd floor in the prefunction space in front of the Grand Ballroom (across the hall from Fandangles). Thanks, Alex _______________________________________________ OpenStack-docs mailing list OpenStack-docs(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

1 0

Re: [OpenStack-I18n] [OpenStack-docs] [openstack-docs][i18n] PTG team photos
by Ben Silverman 20 Feb '17

20 Feb '17

Alex, Are we then going to push the schedule back since the Arch blueprints section is at the same time. -B From: Alexandra Settle <a.settle(a)outlook.com> Date: Monday, February 20, 2017 at 1:07 PM To: "openstack-docs(a)lists.openstack.org" <openstack-docs(a)lists.openstack.org>, "openstack-i18n(a)lists.openstack.org" <openstack-i18n(a)lists.openstack.org> Subject: [OpenStack-docs] [openstack-docs][i18n] PTG team photos Hi team, For all those at the PTG (docs and I18n) – we have a joint team photo session booked for 10.30am, Tuesday morning. The location we are taking the photos on the 3rd floor in the prefunction space in front of the Grand Ballroom (across the hall from Fandangles). Thanks, Alex _______________________________________________ OpenStack-docs mailing list OpenStack-docs(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs

1 0

[openstack-docs][i18n] PTG team photos
by Alexandra Settle 20 Feb '17

20 Feb '17

Hi team, For all those at the PTG (docs and I18n) – we have a joint team photo session booked for 10.30am, Tuesday morning. The location we are taking the photos on the 3rd floor in the prefunction space in front of the Grand Ballroom (across the hall from Fandangles). Thanks, Alex

1 0

Fwd: I18n project mascot
by Ian Y. Choi 20 Feb '17

20 Feb '17

Hello! Please see the final project mascot logo files for I18n team! With many thanks, /Ian -------- Original Message -------- Subject: I18n project mascot Date: Mon, 13 Feb 2017 13:49:49 -0800 From: Heidi Joy Tretheway <heidijoy(a)openstack.org> To: Ian Y. Choi <ianyrchoi(a)gmail.com> Hi Ian, I’m excited to finally be able to share final project logo files with you. Inside this folder, you’ll find full-color and one-color versions of the logo, plus a mascot-only version, in EPS, JPG and PNG formats. You can use them on presentations and wherever else you’d like to add some team flair. https://www.dropbox.com/sh/h1viph4bhbc06lw/AABxQGzAHhN3nAmk_1jy8OA2a?dl=0 At the PWG, we’ll have stickers for your team of the mascot, plus signage on your room. I’m especially excited for the project teams to see all of the logos together as one group, because they work beautifully together stylistically while making each project’s mark distinctive. Feel free to share this with your team, and thanks to you and to them for the hard work they put into reaching an agreement on the mascot. Also feel free to direct any questions my way! photo *Heidi Joy Tretheway* Senior Marketing Manager, OpenStack Foundation 503 816 9769 <tel:503%20816%209769> | Skype: heidi.tretheway <https://webapp.wisestamp.com/sig_iframe?origin=mac-mail&signature_id=549976…> <http://linkedin.com/in/heiditretheway> <http://twitter.com/heiditretheway> <http://www.openstack.org/>

5 6

[Bug 1665255] [NEW] request to OpenStack service with header "Accept-Language: zh-TW", but the response language is not
by WangBinbin 17 Feb '17

17 Feb '17

Public bug reported: In my OpenStack Mitaka cluster, I want to make the service response with zh-TW language, according to the steps below. (take the glance service as example) 1 stop glance-api service with "systemctl stop glance-api" 2 export the env with "export GLANCE_LOCALEDIR=/usr/lib/python2.7/site-packages/glance/locale/ " 3 start glance-api service with "systemctl start glance-api" 4 show image detail with wrong uuid; curl -g -i -X GET http://192.168.51.253:9292/v2/images/8b0e2af4-178e-48bdbad30fe6e99d1ca2 H "User-Agent: python-glanceclient" -H "Content-Type: application/octet-stream" -H "X-Auth-Token: $token" -H "Accept-Language: zh-TW" expect i18n translate the exception to zh-TW, but the response is zh-CN https://github.com/openstack/oslo.i18n/blob/master/oslo_i18n/_gettextutils.… language_list.extend(alias for locale, alias in aliases.items() if (locale in language_list and alias not in language_list)) the zh_Hant is not in the language_list, so the zh_TW will not append to the language_list ** Affects: openstack-i18n Importance: Undecided Assignee: WangBinbin (bbwang5827) Status: New ** Changed in: openstack-i18n Assignee: (unassigned) => WangBinbin (bbwang5827) -- 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/1665255 Title: request to OpenStack service with header "Accept-Language: zh-TW", but the response language is not Status in openstack i18n: New Bug description: In my OpenStack Mitaka cluster, I want to make the service response with zh-TW language, according to the steps below. (take the glance service as example) 1 stop glance-api service with "systemctl stop glance-api" 2 export the env with "export GLANCE_LOCALEDIR=/usr/lib/python2.7/site-packages/glance/locale/ " 3 start glance-api service with "systemctl start glance-api" 4 show image detail with wrong uuid; curl -g -i -X GET http://192.168.51.253:9292/v2/images/8b0e2af4-178e-48bdbad30fe6e99d1ca2 H "User-Agent: python-glanceclient" -H "Content-Type: application/octet-stream" -H "X-Auth-Token: $token" -H "Accept-Language: zh-TW" expect i18n translate the exception to zh-TW, but the response is zh-CN https://github.com/openstack/oslo.i18n/blob/master/oslo_i18n/_gettextutils.… language_list.extend(alias for locale, alias in aliases.items() if (locale in language_list and alias not in language_list)) the zh_Hant is not in the language_list, so the zh_TW will not append to the language_list To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-i18n/+bug/1665255/+subscriptions

2 1

[openstack-docs] [i18n] PTG schedule
by Alexandra Settle 15 Feb '17

15 Feb '17

Hey everyone, Ian and I have written up combined docs and I18n schedule for the PTG: https://etherpad.openstack.org/p/docs-i18n-ptg-pike I have packed in everything on a pretty tight schedule with time allocations simply because we have a lot of *big* topics to talk about between the two projects and I want to make sure we cover the smaller stuff too, but this is only a recommended set of guidelines. We have the full 2 days no matter what – things can be changed. Please reach out if the time does not work for you. I have included everyone’s names next to the sessions they have proposed. There is one session that is nameless – Upgrade Guide – please let me know if this is you (Darren Chan, maybe?) Some of the time slots are purposefully done to accommodate for remote attendees – keep this in mind as well. I have included a new section underneath the schedule for working sessions. I know a few docs people will be around on the Wed – Fri. If anyone is interested in getting together after the 2 days to smash some bugs, or implement a new plan, put your name down and I will organize a room for us. This will be an informal session. Any questions, or if I have missed something, please reach out to me :) Alex

1 0

Fwd: [OpenStack-docs] OpenStack Individual Board Member nomination
by Ian Y. Choi 14 Feb '17

14 Feb '17

Hello translators, I am forwarding one e-mail to share that 1) OpenStack Individual Board Member election will be held in Jan 9-13 2017 for 2017 Board Election. 2) Kato-san is seeking nominations :) Note that I am now on the candidate list because I wanted to check who nominated me, but I will not go for 2017 Board Election. I am now busy but so happy on serving I18n Ocata PTL :) With many thanks, /Ian -------- Original Message -------- Subject: [OpenStack-docs] OpenStack Individual Board Member nomination Date: Tue, 6 Dec 2016 15:41:59 +1000 From: Lana Brindley <openstack(a)lanabrindley.com> To: OpenStack Manuals <openstack-docs(a)lists.openstack.org> Hi everyone, One of our core team members, Tomoyuki KATO, is seeking election for the OpenStack board. In order to stand for candidacy, though, he needs 10 nominations. If you think Tomoyuki-san would be a good addition to the Board, then you can nominate him by going to http://www.openstack.org/community/members/ and searching for "Tomoyuki KATO". No supporting documentation required, just a click if you think he'd be a good candidate :) Voting for the accepted candidates happens in January. Lana -- Lana Brindley Technical Writer Rackspace Cloud Builders Australia http://lanabrindley.com

2 3