Thanks Frank for update. Some feedback on your local.conf. I wonder some of *-dashboard repositories have no devstack plugin even though your local.conf contains it. For example, designate-dashboard and senlin-dashboard. I haven't checked all though. I think such repositories are not enabled in the devstack run. In addition, in most cases we need to enable corresponding backend services as you try manila. For example, desginate itself is not enabled in your local.conf and this triggered me to find desginate-dashboard has no devstack plugin support. Akihiro 2016-03-02 6:36 GMT+09:00 Frank Kloeker <eumel@arcor.de>:
Hi Akihiro,
devstack master branch is working again after some days of broken installation,
so I was able to test some more options in local.conf. I catched the new Neutron
plugin conf and some more plugins into
https://github.com/eumel8/translation_checksite/blob/master/templates/local....
Manila plugin breaks sudoers conf and you are not able to become root after installation,
so I commented it out.
I like app-catalog-ui, which is also beta, but it’s working and maybe we can translate this also.
Sahara and Trove are already in. Feel free to review my personal conf above.
I will test again and upload the new template to Gerrit.
Kind regards
Frank
Gesendet von Mail für Windows 10
Von: Akihiro Motoki Gesendet: Sonntag, 28. Februar 2016 16:01 An: Ying Chun Guo Cc: openstack-i18n@lists.openstack.org Betreff: Re: [Openstack-i18n] translation check site local.confandconfiguraitons
I am not sure the translation check site supports trove/sahara-dashboard
for mitaka translation, so I decided not to push my current version of
local.conf
to the review of puppet-translation_checksite.
You can freely pull my local.conf to the transaltion check site configuration!
My latest version of local.conf is found at [1].
It supports trove-dashboard, sahara-dashboard and various neutron
configurations.
I also updated ansible-i18n-playbook [2] because it is referred to by
the effort of the translation check site, but this repository will be deleted
soon after the translation check site launches.
[1] and [2] is used in my current developments.
Akihiro
[1] https://github.com/amotoki/ansible-playbook/tree/master/roles/devstack/templ...
[2] https://github.com/amotoki/ansible-i18n-devstack/blob/master/roles/i18n-devs...
2016-02-24 16:55 GMT+09:00 Ying Chun Guo <guoyingc@cn.ibm.com>:
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 :-)
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
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
_______________________________________________
Openstack-i18n mailing list
Openstack-i18n@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n