Re: [OpenStack-Infra] Translation check website
It will be great if you could help, Terri Yu. Could you find me in the IRC channel #openstack-i18n ? We could have a detail discussion there. Best regards Ying Chun Guo (Daisy) qmecha...@gmail.com wrote on 2015/12/29 12:26:58: > From: Terri Yu > To: "Elizabeth K. Joseph" > Cc: Ying Chun Guo/China/IBM@IBMCN, OpenStack Infra in...@lists.openstack.org> > Date: 2015/12/29 12:28 > Subject: Re: [OpenStack-Infra] Translation check website > Sent by: qmecha...@gmail.com > > Hi Daisy, > I'm interested in helping out with the translation check project. > Last October, I was awarded a Women of OpenStack scholarship by HPE > [1]. The scholarship includes working on an OpenStack project under > guided mentorship. My mentor is Liz Joseph (pleia2), and she > suggested that I take a look at this translation check project. I > have some previous OpenStack experience with Ceilometer and I know > Python, but I'm new to -infra and Puppet. > I have some time to get started the first two weeks of January, but > after that, my spring semester in school will begin and I will > probably only have around 10 hours a week to work on OpenStack. Liz > said she'll be available to help me. The folks at Hewlett Packard > aren't expecting me to implement any major features. They would > simply like me to get more experience working on OpenStack and have > enough accomplished for a presentation in April. > Are there any small tasks I can help you with? Let me know if you > think this project would be appropriate for me. > > Sincerely, > Terri Yu > > [1] http://community.hpe.com/t5/Grounded-in-the-Cloud/ > Congratulations-to-the-Women-of-OpenStack-Scholarship-Recipients/ba- > p/6806417#.VoIIyPkrJaQ > > On Mon, Nov 23, 2015 at 3:01 PM, Elizabeth K. Joseph > wrote: > On Thu, Nov 19, 2015 at 12:22 AM, Ying Chun Guo wrote: > > Hello, openstack-infra team > > > > I'm going to start to work of translation check website. > > The spec is > > http://git.openstack.org/cgit/openstack-infra/infra-specs/tree/ > specs/translation_check_site.rst > > > > Akihiro MOTOKI has created some scripts/configuration files to set up a > > personal check website used by Japanese team. > > I think I could refer to his work, change the scripts/config as needed, and > > set up the check website on top of Openstack infra. > > I have a few questions about how to set up these scripts/config. > > Please help to guide me to finish this work. > > > > 1. Which repo and which folder should I add those scripts/config files ? > > > > The scripts are in https://github.com/amotoki/horizon-i18n-tools. > > These scripts are used to pull translations, and change the language drop > > down list of Horizon. > > I'll bring this up at the -infra meeting on Tuesday so others can look > at this thread and chime in, but we have a couple options here. > > These scripts can either be put in your new i18n repository, > particularly if they'll be broadly useful to other people: > > http://git.openstack.org/cgit/openstack/i18n/ > > Or they can be included in the puppet-translations_checksite project > that we create (more below). > > > The config files are in https://github.com/amotoki/ansible-i18n-devstack/ > > They are Ansible jobs to pull devstack, populates local.conf, pulls > > horizon-i18n-tools and setup a cron to retrieve the latest translation. > > > > I think I need to change the codes as needed, and then upload them to > > somewhere. > > Does openstack infra use Ansible ? > > Not for service deployment, we'll need to do this in Puppet. > > You can use both Akihiro's instructions and also look at how we deploy > devstack ourselves using devstack-gate > https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/ in > order to come up with a puppet module that runs all the commands we > want. > > > Where to store them ? > > We'll want to create an infra puppet module specifically for this > project. You can look at the puppet-infra-cookiecutter module as an > example: https://git.openstack.org/cgit/openstack-infra/puppet- > infra-cookiecutter/tree/ > > > 2. When pulling the latest translations, there are two choices. > > One is to pull from Horizon repo, the other is to pull from Zanata. > > Which one do you suggest ? Lyz may help to answer this question. > > If pulling from Zanata, could I get a sample of script to install Zanata > > client ? > > In order for this check site to be as useful as possible, we'll want > to pull them from Zanata just like Akihiro used to do with Transifex > on his instance. > > Documentation for the zanata-cli can be found here: > http://docs.zanata.org/projects/zanata-client/en/latest/ > > In the puppet manifest you'll want to make sure you install the zanata > client, you can see a Puppet example of including the client on a > system here: http://git.openstack.org/cgit/openstack-infra/system- > config/tree/modules/openstack_project/manifests/proposal_slave.pp > > Some of the translations scripts we've written can be found in > pr
Re: [OpenStack-Infra] Translation check website
I will be happy since I speak italian so this could be a good option. Remo Inviato da iPhone > Il giorno 28 dic 2015, alle ore 20:26, Terri Yu ha > scritto: > > Hi Daisy, > > I'm interested in helping out with the translation check project. > > Last October, I was awarded a Women of OpenStack scholarship by HPE [1]. The > scholarship includes working on an OpenStack project under guided mentorship. > My mentor is Liz Joseph (pleia2), and she suggested that I take a look at > this translation check project. I have some previous OpenStack experience > with Ceilometer and I know Python, but I'm new to -infra and Puppet. > > I have some time to get started the first two weeks of January, but after > that, my spring semester in school will begin and I will probably only have > around 10 hours a week to work on OpenStack. Liz said she'll be available to > help me. The folks at Hewlett Packard aren't expecting me to implement any > major features. They would simply like me to get more experience working on > OpenStack and have enough accomplished for a presentation in April. > > Are there any small tasks I can help you with? Let me know if you think this > project would be appropriate for me. > > Sincerely, > > Terri Yu > > [1] > http://community.hpe.com/t5/Grounded-in-the-Cloud/Congratulations-to-the-Women-of-OpenStack-Scholarship-Recipients/ba-p/6806417#.VoIIyPkrJaQ > >> On Mon, Nov 23, 2015 at 3:01 PM, Elizabeth K. Joseph >> wrote: >> On Thu, Nov 19, 2015 at 12:22 AM, Ying Chun Guo wrote: >> > Hello, openstack-infra team >> > >> > I'm going to start to work of translation check website. >> > The spec is >> > http://git.openstack.org/cgit/openstack-infra/infra-specs/tree/specs/translation_check_site.rst >> > >> > Akihiro MOTOKI has created some scripts/configuration files to set up a >> > personal check website used by Japanese team. >> > I think I could refer to his work, change the scripts/config as needed, and >> > set up the check website on top of Openstack infra. >> > I have a few questions about how to set up these scripts/config. >> > Please help to guide me to finish this work. >> > >> > 1. Which repo and which folder should I add those scripts/config files ? >> > >> > The scripts are in https://github.com/amotoki/horizon-i18n-tools. >> > These scripts are used to pull translations, and change the language drop >> > down list of Horizon. >> >> I'll bring this up at the -infra meeting on Tuesday so others can look >> at this thread and chime in, but we have a couple options here. >> >> These scripts can either be put in your new i18n repository, >> particularly if they'll be broadly useful to other people: >> >> http://git.openstack.org/cgit/openstack/i18n/ >> >> Or they can be included in the puppet-translations_checksite project >> that we create (more below). >> >> > The config files are in https://github.com/amotoki/ansible-i18n-devstack/ >> > They are Ansible jobs to pull devstack, populates local.conf, pulls >> > horizon-i18n-tools and setup a cron to retrieve the latest translation. >> > >> > I think I need to change the codes as needed, and then upload them to >> > somewhere. >> > Does openstack infra use Ansible ? >> >> Not for service deployment, we'll need to do this in Puppet. >> >> You can use both Akihiro's instructions and also look at how we deploy >> devstack ourselves using devstack-gate >> https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/ in >> order to come up with a puppet module that runs all the commands we >> want. >> >> > Where to store them ? >> >> We'll want to create an infra puppet module specifically for this >> project. You can look at the puppet-infra-cookiecutter module as an >> example: >> https://git.openstack.org/cgit/openstack-infra/puppet-infra-cookiecutter/tree/ >> >> > 2. When pulling the latest translations, there are two choices. >> > One is to pull from Horizon repo, the other is to pull from Zanata. >> > Which one do you suggest ? Lyz may help to answer this question. >> > If pulling from Zanata, could I get a sample of script to install Zanata >> > client ? >> >> In order for this check site to be as useful as possible, we'll want >> to pull them from Zanata just like Akihiro used to do with Transifex >> on his instance. >> >> Documentation for the zanata-cli can be found here: >> http://docs.zanata.org/projects/zanata-client/en/latest/ >> >> In the puppet manifest you'll want to make sure you install the zanata >> client, you can see a Puppet example of including the client on a >> system here: >> http://git.openstack.org/cgit/openstack-infra/system-config/tree/modules/openstack_project/manifests/proposal_slave.pp >> >> Some of the translations scripts we've written can be found in >> project-config jenkins scripts (see ones that include "translation" in >> the script name): >> https://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts >> >> > 3. How to get a machin
Re: [OpenStack-Infra] Translation check website
Hi Daisy, I'm interested in helping out with the translation check project. Last October, I was awarded a Women of OpenStack scholarship by HPE [1]. The scholarship includes working on an OpenStack project under guided mentorship. My mentor is Liz Joseph (pleia2), and she suggested that I take a look at this translation check project. I have some previous OpenStack experience with Ceilometer and I know Python, but I'm new to -infra and Puppet. I have some time to get started the first two weeks of January, but after that, my spring semester in school will begin and I will probably only have around 10 hours a week to work on OpenStack. Liz said she'll be available to help me. The folks at Hewlett Packard aren't expecting me to implement any major features. They would simply like me to get more experience working on OpenStack and have enough accomplished for a presentation in April. Are there any small tasks I can help you with? Let me know if you think this project would be appropriate for me. Sincerely, Terri Yu [1] http://community.hpe.com/t5/Grounded-in-the-Cloud/Congratulations-to-the-Women-of-OpenStack-Scholarship-Recipients/ba-p/6806417#.VoIIyPkrJaQ On Mon, Nov 23, 2015 at 3:01 PM, Elizabeth K. Joseph wrote: > On Thu, Nov 19, 2015 at 12:22 AM, Ying Chun Guo > wrote: > > Hello, openstack-infra team > > > > I'm going to start to work of translation check website. > > The spec is > > > http://git.openstack.org/cgit/openstack-infra/infra-specs/tree/specs/translation_check_site.rst > > > > Akihiro MOTOKI has created some scripts/configuration files to set up a > > personal check website used by Japanese team. > > I think I could refer to his work, change the scripts/config as needed, > and > > set up the check website on top of Openstack infra. > > I have a few questions about how to set up these scripts/config. > > Please help to guide me to finish this work. > > > > 1. Which repo and which folder should I add those scripts/config files ? > > > > The scripts are in https://github.com/amotoki/horizon-i18n-tools. > > These scripts are used to pull translations, and change the language drop > > down list of Horizon. > > I'll bring this up at the -infra meeting on Tuesday so others can look > at this thread and chime in, but we have a couple options here. > > These scripts can either be put in your new i18n repository, > particularly if they'll be broadly useful to other people: > > http://git.openstack.org/cgit/openstack/i18n/ > > Or they can be included in the puppet-translations_checksite project > that we create (more below). > > > The config files are in > https://github.com/amotoki/ansible-i18n-devstack/ > > They are Ansible jobs to pull devstack, populates local.conf, pulls > > horizon-i18n-tools and setup a cron to retrieve the latest translation. > > > > I think I need to change the codes as needed, and then upload them to > > somewhere. > > Does openstack infra use Ansible ? > > Not for service deployment, we'll need to do this in Puppet. > > You can use both Akihiro's instructions and also look at how we deploy > devstack ourselves using devstack-gate > https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/ in > order to come up with a puppet module that runs all the commands we > want. > > > Where to store them ? > > We'll want to create an infra puppet module specifically for this > project. You can look at the puppet-infra-cookiecutter module as an > example: > https://git.openstack.org/cgit/openstack-infra/puppet-infra-cookiecutter/tree/ > > > 2. When pulling the latest translations, there are two choices. > > One is to pull from Horizon repo, the other is to pull from Zanata. > > Which one do you suggest ? Lyz may help to answer this question. > > If pulling from Zanata, could I get a sample of script to install Zanata > > client ? > > In order for this check site to be as useful as possible, we'll want > to pull them from Zanata just like Akihiro used to do with Transifex > on his instance. > > Documentation for the zanata-cli can be found here: > http://docs.zanata.org/projects/zanata-client/en/latest/ > > In the puppet manifest you'll want to make sure you install the zanata > client, you can see a Puppet example of including the client on a > system here: > http://git.openstack.org/cgit/openstack-infra/system-config/tree/modules/openstack_project/manifests/proposal_slave.pp > > Some of the translations scripts we've written can be found in > project-config jenkins scripts (see ones that include "translation" in > the script name): > > https://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts > > > 3. How to get a machine to set up the website ? > > Once the puppet module is complete, you'll contact one of us on the > infra team (probably me) and I'll launch the server. > > A couple notes: > > 1. We'll want to refresh this instance regularly (weekly?), so you'll > want a cron job to run unstack.sh weekly or so and then recreate the > dev
[OpenStack-Infra] [Infra] Meeting Tuesday December 29th at 19:00 UTC
Hi everyone, The OpenStack Infrastructure (Infra) team is not skipping meetings through the end of month holidays, so we are having our next weekly meeting as scheduled on Tuesday December 29th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add agenda items and everyone interested in the project infrastructure and process surrounding automated testing and deployment is encouraged to attend. In case you missed it or would like a refresher, the meeting minutes and full logs from our last meeting are available: Minutes: http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-12-22-19.03.html Minutes (text): http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-12-22-19.03.txt Log: http://eavesdrop.openstack.org/meetings/infra/2015/infra.2015-12-22-19.03.log.html -- Elizabeth Krumbach Joseph || Lyz || pleia2 ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Translation setup challenges
Reading some IRC backlog and an incoming review with a new suggestion on
how to do translations in the project, I decided to write some problems
our current scripts have, together with questions and proposals. With
the growing big tent and the automatic way to setup translations, we get
more repos requesting translations - and more support requests.
Please read the description below and tell me what's wrong,what's
missing, where you disagree - and how to move forward.
thanks,
Andreas
Setting up translations for new projects currently has the following
challenges:
a) For "python" repositories, we expect that the locale file is
located at $repo/locale/$repo.pot - without any change possible.
This leads to python-novaclient/locale/python-novaclient.pot and
oslo.log/locale/oslo.log.i18n - in both cases the python module has
a different name, novaclient and oslo_log.
Currently everybody makes it wrong and we have to help them using
the proper file names.
Proposal:
* Simplify location to use $modulename/locale/$modulename
Can we determine modulename easily from the name in setup.cfg like
in jenkins/scripts/pypi-extract-name.py?
b) For dashboard repos, there's no common entry point yet and some are
even setup like "python" repositories (designate-dashboard).
There's also no naming pattern on how to name files and everybody
does it differently.
Currently the django component is called djangjo.pot, the
javascript one djangojs.pot.
Question: Do we really need to do it this way or can we change it?
We should have a single entrypoint for projects and a standard way
to call them.
Proposal: Define standard tox environement "extractmessages", it
places translation files in (if django/djangojs are really the best
names, I prefer to change them):
* $modulename/locale/django.pot
* $modulename/locale/djangojs.pot
Can we determine modulename easily from the name in setup.cfg like
in jenkins/scripts/pypi-extract-name.py? At least
django_openstack_auth is setup differently..
c) Projects currently need to add the pot file initially, our scripts
fail if the directory does not exist.
Proposal: Make scripts robust so that they work even without
initial pot file.
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] tox change in jenkins-job-builder and lots of warnings ; (
On 12/27/2015 08:48 PM, Darragh Bailey wrote:
On 26 Dec 2015 12:55, "Jeremy Stanley" mailto:fu...@yuggoth.org>> wrote:
>
> Presumably we could rename our tox macro so that it doesn't shadow
> the recently added tox builtin, but this problem will occur any time
> support for another plugin is added which uses the same name as
> something in our existing configuration so I'm not sure if there are
> better options.
> --
> Jeremy Stanley
We could look to limit to a single warning?
That would be fine. Right now I see 782 lines of this warning ;(
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
___
OpenStack-Infra mailing list
OpenStack-Infra@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
