mann.com]
> Sent: Monday, March 13, 2017 11:16 AM
> To: openstack-operators
> Subject: Re: [Openstack-operators] need input on log translations
>
> Excerpts from Doug Hellmann's message of 2017-03-10 09:38:43 -0500:
> > There is a discussion on the -dev mailing list ab
#x27;ll catch you on IRC and hopefully get to a better understanding of this.
Thanks,
-amrith
--
Amrith Kumar
amrith.ku...@gmail.com
-Original Message-
From: Doug Hellmann [mailto:d...@doughellmann.com]
Sent: Monday, March 13, 2017 11:16 AM
To: openstack-operators
Subject: Re: [Opens
Excerpts from Doug Hellmann's message of 2017-03-10 09:38:43 -0500:
> There is a discussion on the -dev mailing list about the i18n team
> decision to stop translating log messages [1]. The policy change means
> that we may be able to clean up quite a lot of "clutter" throughout the
> service code,
2017-03-14 0:15 GMT+09:00 Doug Hellmann :
> Excerpts from Doug Hellmann's message of 2017-03-10 09:38:43 -0500:
>> There is a discussion on the -dev mailing list about the i18n team
>> decision to stop translating log messages [1]. The policy change means
>> that we may be able to clean up quite a
I’ve heard from several Korea operators, and I too was involved in OpenStack
operation. I cannot represent everyone here in Korea, but It is mostly clear
that log translation are not beneficial for operators, at least here in Korea.
Thanks.
Jaesuk Ahn, Ph.D.
Software Defined Infra. Laborato
Excerpts from Doug Hellmann's message of 2017-03-10 09:38:43 -0500:
> There is a discussion on the -dev mailing list about the i18n team
> decision to stop translating log messages [1]. The policy change means
> that we may be able to clean up quite a lot of "clutter" throughout the
> service code,
On Fri, Mar 10, 2017 at 6:19 PM, Amrith Kumar wrote:
> Today the workflow is to copy the message and plonk it into google and let
> search do its thing.
>
> Given this, log message translation fragments the solution space because
> nothing out there consolidates the reports of problems with error
Hello,
I'm Polish speaker and I never even though about translated logs. IMHO
english is so common language in IT that probably for most of us using
english instead of native language is perfectly fine.
--
Best regards / Pozdrawiam
Sławek Kapłoński
sla...@kaplonski.pl
On sob, 11 mar 2017, Georg
> On 11 Mar 2017, at 10:54, Saverio Proto wrote:
>
> I am Italian speaking.
> Does not make any sense to have the log messages translated. I think
> everything has already being said.
+1
I think there is not even an italian word for "log" 😉
___
OpenSt
Hello there,
I am Italian speaking.
Does not make any sense to have the log messages translated. I think
everything has already being said.
Saverio
2017-03-11 9:20 GMT+01:00 George Shuklin :
> Whole idea with log translation is half-backed anyway. About the half of
> important log messages conta
Whole idea with log translation is half-backed anyway. About the half of
important log messages contain output of things outside openstack. Libvirt,
ip, sudo, kernel, etc. In any i18n installation there going to be some
amount of untranslated messages. This kills whole idea of localization.
Modern
I think a searchable code is handy. My workflow is to try to read the log
messages and follow the flow of what I think should be happening. If I can't
resolve the issue after a significant effort, I search to see if there is a
bug or someone else hit the same error, maybe due to misconfiguratio
Doug,
I had a conversation with someone from the i18n team in Atlanta at the PTG,
and later with a couple of operators (from a non-english speaking country).
I was surprised to hear that both the operators were in favor of doing away
with log message translation. Thinking about it some more, I bel
13 matches
Mail list logo
