<html><body><p>Hi, infra team<br><br>The puppet module is proposed to <a href="http://git.openstack.org/cgit/openstack-infra/puppet-translation_checksite/">http://git.openstack.org/cgit/openstack-infra/puppet-translation_checksite/</a>.<br>Please help to review.<br><br>Below are some follow up questions. <br>Hope to get inputs from infra experts.<br><br>1. How to handle user accounts for openstack instance ?<br>The puppet module has set up an admin account with a configurable password.<br>Do we need to protect the admin password ?<br>I hope to have some tester accounts only for testing.<br>The tester accounts may be shared within I18n team.<br><br>2. What's the hardware config of the translation_checksite server ?<br>After testing, we recommend a 8GB memory to support the set up of openstack.<br><br>3. Do we need to deal with the health check or monitoring of openstack instance ?<br><br>4. The puppet module has two cron jobs and a list of parameters.<br>I don't know how to configure the parameters.<br>Are there a web UI to configure ?<br><br>Thank you.<br>Best regards<br>Ying Chun Guo (Daisy)<br><br><br><tt>Andreas Jaeger <aj@suse.com> wrote on 2016/02/01 22:36:23:<br><br>> From: Andreas Jaeger <aj@suse.com></tt><br><tt>> To: Ying Chun Guo/China/IBM@IBMCN</tt><br><tt>> Cc: <openstack-infra@lists.openstack.org></tt><br><tt>> Date: 2016/02/01 22:38</tt><br><tt>> Subject: Re: [OpenStack-Infra] Translation check website</tt><br><tt>> <br>> On 2016-02-01 15:15, Ying Chun Guo wrote:<br>> > <br>> > Thank you for the detail guidance, Elizabeth.<br>> > We have had the first version of puppet module in github[1].<br>> > We hope to move it to openstack infra.<br>> <br>> Daisy, the infra repo has been created yesterday, now you can send<br>> changes for it,<br>> <br>> Andreas<br>> <br>> > @Emilien, can I get your support<br>> > to <a href="https://review.openstack.org/#/c/274090/">https://review.openstack.org/#/c/274090/</a> ?<br>> > The patch is to create the puppet module repository under openstack-infra.<br>> > Thank you.<br>> > <br>> > Best regards<br>> > Ying Chun Guo (Daisy)<br>> > <br>> > [1] <a href="https://github.com/eumel8/translation_checksite">https://github.com/eumel8/translation_checksite</a><br>> > <br>> > <br>> > <br>> > ----- Original message -----<br>> > From: "Elizabeth K. Joseph" <lyz@princessleia.com><br>> > To: Ying Chun Guo/China/IBM@IBMCN<br>> > Cc: OpenStack Infra <openstack-infra@lists.openstack.org><br>> > Subject: Re: [OpenStack-Infra] Translation check website<br>> > Date: Tue, Nov 24, 2015 4:02 AM<br>> > <br>> > On Thu, Nov 19, 2015 at 12:22 AM, Ying Chun Guo<br>> > <guoyingc@cn.ibm.com> wrote:<br>> > > Hello, openstack-infra team<br>> > ><br>> > > I'm going to start to work of translation check website.<br>> > > The spec is<br>> > ><br>> > <a href="http://git.openstack.org/cgit/openstack-infra/infra-specs/">http://git.openstack.org/cgit/openstack-infra/infra-specs/</a><br>> tree/specs/translation_check_site.rst<br>> > ><br>> > > Akihiro MOTOKI has created some scripts/configuration files to set<br>> > up a<br>> > > personal check website used by Japanese team.<br>> > > I think I could refer to his work, change the scripts/config as<br>> > needed, and<br>> > > set up the check website on top of Openstack infra.<br>> > > I have a few questions about how to set up these scripts/config.<br>> > > Please help to guide me to finish this work.<br>> > ><br>> > > 1. Which repo and which folder should I add those scripts/config<br>> > files ?<br>> > ><br>> > > The scripts are in <a href="https://github.com/amotoki/horizon-i18n-tools">https://github.com/amotoki/horizon-i18n-tools</a>.<br>> > > These scripts are used to pull translations, and change the<br>> > language drop<br>> > > down list of Horizon.<br>> > <br>> > I'll bring this up at the -infra meeting on Tuesday so others can look<br>> > at this thread and chime in, but we have a couple options here.<br>> > <br>> > These scripts can either be put in your new i18n repository,<br>> > particularly if they'll be broadly useful to other people:<br>> > <br>> > <a href="http://git.openstack.org/cgit/openstack/i18n/">http://git.openstack.org/cgit/openstack/i18n/</a><br>> > <br>> > Or they can be included in the puppet-translations_checksite project<br>> > that we create (more below).<br>> > <br>> > > The config files are in<br>> > <a href="https://github.com/amotoki/ansible-i18n-devstack/">https://github.com/amotoki/ansible-i18n-devstack/</a><br>> > > They are Ansible jobs to pull devstack, populates local.conf, pulls<br>> > > horizon-i18n-tools and setup a cron to retrieve the latest<br>> > translation.<br>> > ><br>> > > I think I need to change the codes as needed, and then upload them to<br>> > > somewhere.<br>> > > Does openstack infra use Ansible ?<br>> > <br>> > Not for service deployment, we'll need to do this in Puppet.<br>> > <br>> > You can use both Akihiro's instructions and also look at how we deploy<br>> > devstack ourselves using devstack-gate<br>> > <a href="https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/">https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/</a> in<br>> > order to come up with a puppet module that runs all the commands we<br>> > want.<br>> > <br>> > > Where to store them ?<br>> > <br>> > We'll want to create an infra puppet module specifically for this<br>> > project. You can look at the puppet-infra-cookiecutter module as an<br>> > example:<br>> > <a href="https://git.openstack.org/cgit/openstack-infra/puppet-infra-">https://git.openstack.org/cgit/openstack-infra/puppet-infra-</a><br>> cookiecutter/tree/<br>> > <br>> > > 2. When pulling the latest translations, there are two choices.<br>> > > One is to pull from Horizon repo, the other is to pull from Zanata.<br>> > > Which one do you suggest ? Lyz may help to answer this question.<br>> > > If pulling from Zanata, could I get a sample of script to install<br>> > Zanata<br>> > > client ?<br>> > <br>> > In order for this check site to be as useful as possible, we'll want<br>> > to pull them from Zanata just like Akihiro used to do with Transifex<br>> > on his instance.<br>> > <br>> > Documentation for the zanata-cli can be found here:<br>> > <a href="http://docs.zanata.org/projects/zanata-client/en/latest/">http://docs.zanata.org/projects/zanata-client/en/latest/</a><br>> > <br>> > In the puppet manifest you'll want to make sure you install the zanata<br>> > client, you can see a Puppet example of including the client on a<br>> > system here:<br>> > <a href="http://git.openstack.org/cgit/openstack-infra/system-config/">http://git.openstack.org/cgit/openstack-infra/system-config/</a><br>> tree/modules/openstack_project/manifests/proposal_slave.pp<br>> > <br>> > Some of the translations scripts we've written can be found in<br>> > project-config jenkins scripts (see ones that include "translation" in<br>> > the script name):<br>> > <a href="https://git.openstack.org/cgit/openstack-infra/project-config/">https://git.openstack.org/cgit/openstack-infra/project-config/</a><br>> tree/jenkins/scripts<br>> > <br>> > > 3. How to get a machine to set up the website ?<br>> > <br>> > Once the puppet module is complete, you'll contact one of us on the<br>> > infra team (probably me) and I'll launch the server.<br>> > <br>> > A couple notes:<br>> > <br>> > 1. We'll want to refresh this instance regularly (weekly?), so you'll<br>> > want a cron job to run unstack.sh weekly or so and then recreate the<br>> > devstack instance. We'll also want to keep an eye on how this goes,<br>> > since unstack.sh is not a perfect script and we may need to recreate<br>> > the instance from scratch now and then.<br>> > <br>> > 2. We also want to pull the translations regularly (daily?), so you'll<br>> > want a cron job to run the zanata-cli script for the translations in<br>> > Horizon<br>> > <br>> > > 4. How to get a domain name ? for example:<br>> > translation-test.openstack.org ?<br>> > <br>> > This will be created when I bring up the server in step 3. We don't<br>> > have a name for it yet, but should probably update the spec when we<br>> > decide upon one.<br>> > <br>> > --<br>> > Elizabeth Krumbach Joseph || Lyz || pleia2<br>> > <br>> > <br>> > <br>> > <br>> > <br>> > _______________________________________________<br>> > OpenStack-Infra mailing list<br>> > OpenStack-Infra@lists.openstack.org<br>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><br>> > <br>> <br>> <br>> -- <br>> Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi<br>> SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany<br>> GF: Felix Imendörffer, Jane Smithard, Graham Norton,<br>> HRB 21284 (AG Nürnberg)<br>> GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126<br>> <br></tt><BR>
</body></html>