I support to use puppet-translation_checksite to store a newest and latest workable local.conf. For various versions of local.conf, they mostly are used as references. I think personal github is good to keep them. Thank you, Akihiro. Best regards Ying Chun Guo (Daisy) Akihiro Motoki <amotoki@gmail.com> wrote on 2016/02/24 00:32:42:

From: Akihiro Motoki <amotoki@gmail.com> To: SungJin Kang <gang.sungjin@gmail.com> Cc: "openstack-i18n@lists.openstack.org" <Openstack-i18n@lists.openstack.org> Date: 2016/02/24 00:34 Subject: Re: [Openstack-i18n] translation check site local.conf and configuraitons

I just remembered puppet-translation_checksite repo [1] is created to maintain the infra configuration for our translation check site.

BTW, it sounds good to use i18n repo to share various contents including local.conf. We have various potential configuration options, so it is nice to have docs or files in our repo :-)

[1] http://git.openstack.org/cgit/openstack-infra/puppet- translation_checksite/

2016-02-24 1:22 GMT+09:00 SungJin Kang <gang.sungjin@gmail.com>:

...

HI, Akihiro.

I things using i18n repo [1]

Make directory /config? or /devstack/version? anythings.

Thanks, Sungjin

[1]: http://git.openstack.org/cgit/openstack/i18n/

2016-02-24 0:58 GMT+09:00 Akihiro Motoki <amotoki@gmail.com>:

...

Hi,

Thanks for working on translation check site as the upstream.

Where is the configuration files maintained in OpenStack repositories? I can share my local.conf with GitHub gist or in other ways, but it is not the OpenStack way. We use gerrit to share everything. I would like to follow it.

I promised to provide devstack local.conf which enables almost all features for the check site. I now have local.conf compatible with Liberty OpenStack dashboard ('compatible' means Trove and Sahara horizon plugins are supported).

To support more horizon plugins beyond sahara/trove dashboard for translations, everyone can push a new version of local.conf once he/she finds and confirms a right configuration. There are many horizon plugins, so it is not reasonable to depend devstack configurations on a small group of peoples.

Thanks, Akihiro

_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n

_______________________________________________ Openstack-i18n mailing list Openstack-i18n@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n