Ceilometer i18n support isn't complete, messages should be wrapped by "_" function

[David Jia]

Ceilometer has enabled i18n support, but there are a lot of messages in source code aren't wrapped by "_" function, for example:

https://github.com/openstack/ceilometer/blob/master/ceilometer/api/app.py#L112

LOG.info('Starting server in PID %s' % os.getpid()) should be replace by LOG.info(_('Starting server in PID %s') % os.getpid())

those messages can't be captured into po file and translated.

we should keep consistency with Oslo codes, such as:

https://github.com/openstack/ceilometer/blob/master/ceilometer/openstack/common/service.py#L113

[xingzhou (xingzhou)]

There is still an indeterminacy for OpenStack i18n team on whether to support LOG level translation or not, because if we translate the LOGs, it might not be easy to search and locate errors,

[David Jia (jiataotj)]

Xing,

    Is there any i18n team work progress information on wiki page or public accessing place? I'd like to know the newest plan for LOGs tranlstaion.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/36774

[David Jia (jiataotj)]

@Doug Hellmann

Hi Doug,

    According to your comments for Review:https://review.openstack.org/36774, is there any blueprints or bug in Olso for log translation discussion? If yes, could you share the link? I'm curious about the discussion result. Thanks you!

[Justin Shepherd (jshepher)]

Un-assigning based on Doug's comments in https://review.openstack.org/36774

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/54683
Committed: http://github.com/openstack/ceilometer/commit/7f542e3ac8c822bc0e5f1d5e7f9de3b7338a717d
Submitter: Jenkins
Branch: master

commit 7f542e3ac8c822bc0e5f1d5e7f9de3b7338a717d
Author: ChenZheng <email address hidden>
Date: Thu Oct 31 15:46:30 2013 +0800

    Add i18n warpping for all LOG messages

    Add i18n wrapping for all LOG messages

    Change-Id: I7f9c71a3aa76364b291f7e21a1737b927cbdc300
    Fixes: bug #1199678