- OpenStack-I18n - lists.openstack.org

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 25 Feb '17

25 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