<html><body>
<p><font size="2" face="sans-serif">Thank you, Anne and KATO.</font><br>
<br>
<font size="2" face="sans-serif">The "po file not found" problem is caused by the downloading script broken because the repository moved another place.</font><br>
<br>
<font size="2" face="sans-serif">I think we can fix this issue and then the downloading script can download the po file.</font><br>
<br>
<font size="2" face="sans-serif">KATO, I think I agree with you. The publish process need to be refined and come up with details.</font><br>
<br>
<font size="2" face="sans-serif">Regards<br>
Ying Chun Guo (Daisy)<br>
</font><br>
<tt><font size="2">KATO Tomoyuki <tomo@dream.daynight.jp> wrote on 2013/08/31 21:03:24:<br>
<br>
> KATO Tomoyuki <tomo@dream.daynight.jp> </font></tt><br>
<tt><font size="2">> 2013/08/31 21:03</font></tt><br>
<tt><font size="2">> <br>
> To</font></tt><br>
<tt><font size="2">> <br>
> Anne Gentle <annegentle@justwriteclick.com>, </font></tt><br>
<tt><font size="2">> <br>
> cc</font></tt><br>
<tt><font size="2">> <br>
> "openstack-docs@lists.openstack.org" <openstack-docs@lists.openstack.org></font></tt><br>
<tt><font size="2">> <br>
> Subject</font></tt><br>
<tt><font size="2">> <br>
> Re: [Openstack-docs] ops guide japanese build fails due to split repositories</font></tt><br>
<tt><font size="2">> <br>
> Hi all,<br>
> <br>
> > "error while opening "./doc/src/docbkx/openstack-ops/locale/ja.po" for<br>
> > reading: No such file or directory"<br>
> <br>
> I requested to merge Japanese translation file "ja.po".<br>
> This file is the newest translation file from Transifex.<br>
> Please check it.<br>
> <br>
> <a href="https://review.openstack.org/44591">https://review.openstack.org/44591</a><br>
> <br>
> Thanks,<br>
> KATO Tomoyuki<br>
> <br>
> > Hi again all,<br>
> > <br>
> > The Japanese HTML/PDF builds will continue to fail until the slicing script<br>
> > can be run on any repo.<br>
> > <br>
> > Daisy, right now the Japanese ops-guide job fails due to trying to get the<br>
> > po file from a directory relative to the openstack-manuals repo.<br>
> > <a href="https://jenkins01.openstack.org/view/Openstack-manuals/job/">https://jenkins01.openstack.org/view/Openstack-manuals/job/</a><br>
> openstack-operations-guide/<br>
> > reports:<br>
> > <br>
> > "error while opening "./doc/src/docbkx/openstack-ops/locale/ja.po" for<br>
> > reading: No such file or directory"<br>
> > <br>
> > Can you continue to work on a way forward as described by Clark? Let us<br>
> > know any concerns you have and we'll work on mitigating them.<br>
> > <br>
> > Thanks,<br>
> > <br>
> > Anne<br>
> > <br>
> > <br>
> > On Thu, Aug 29, 2013 at 12:26 PM, Clark Boylan <br>
> <clark.boylan@gmail.com>wrote:<br>
> > <br>
> > > I think there are two reasonable solutions to this problem and they<br>
> > > may end up being temporarily complementary.<br>
> > > 1. Put the tools/scripts in<br>
> > > openstack-infra/config/modules/jenkins/files/slave_scripts so that the<br>
> > > scripts are installed on all of the Jenkins slaves and can be used by<br>
> > > the Jenkins jobs.<br>
> > > 2. Break the tools out into a distinct project that can be pip installed.<br>
> > ><br>
> > > Option 1 has one major flaw in that it makes it a little hard to find<br>
> > > and install the scripts for people not running our puppet. Not<br>
> > > impossible but definitely difficult. Option 1 is a quick fix, I think<br>
> > > we can start with option 1 to keep the ball rolling and start working<br>
> > > on option 2 at the same time then we can transition to option 2 when<br>
> > > it is ready.<br>
> > ><br>
> > > Clark<br>
> > ><br>
> > > On Thu, Aug 29, 2013 at 10:18 AM, Anne Gentle<br>
> > > <annegentle@justwriteclick.com> wrote:<br>
> > > > Looping in Clark Boylan from the Infrastructure team.<br>
> > > ><br>
> > > > Anne<br>
> > > ><br>
> > > ><br>
> > > > On Wed, Aug 28, 2013 at 2:03 AM, Ying Chun Guo <guoyingc@cn.ibm.com><br>
> > > wrote:<br>
> > > >><br>
> > > >> Hi, Tom and Anne<br>
> > > >><br>
> > > >> These scripts are similar with what nova or horizon use to generate<br>
> > > their<br>
> > > >> pot files,<br>
> > > >> like "setup.py" in nova or "./run_tests.sh" in horizon.<br>
> > > >><br>
> > > >> So I think there should be a "tools" folder under each documentation<br>
> > > >> repository.<br>
> > > >> The question is how can we maintain a single version but use them in<br>
> > > >> several different repositories.<br>
> > > >><br>
> > > >> Do you know how openstack maintain the common folder (Oslo project)?<br>
> > > >> I think each openstack project copies it when checking out?<br>
> > > >> Or has a script to check out to a specific folder?<br>
> > > >><br>
> > > >> Daisy<br>
> > > >><br>
> > > >> Tom Fifield <tom@openstack.org> wrote on 2013/08/28 06:22:02:<br>
> > > >><br>
> > > >> > Tom Fifield <tom@openstack.org><br>
> > > >> > 2013/08/28 06:22<br>
> > > >> ><br>
> > > >> > To<br>
> > > >> ><br>
> > > >> > Anne Gentle <annegentle@justwriteclick.com>,<br>
> > > >> ><br>
> > > >> > cc<br>
> > > >> ><br>
> > > >> > "openstack-docs@lists.openstack.org"<br>
> > > >> > <openstack-docs@lists.openstack.org><br>
> > > >> ><br>
> > > >> > Subject<br>
> > > >> ><br>
> > > >> > Re: [Openstack-docs] ops guide japanese build fails due to split<br>
> > > >> > repositories<br>
> > > >><br>
> > > >> ><br>
> > > >> > On 28/08/13 00:35, Anne Gentle wrote:<br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > > On Sat, Aug 24, 2013 at 7:59 PM, Tom Fifield <tom@openstack.org<br>
> > > >> > > <<a href="mailto:tom@openstack.org">mailto:tom@openstack.org</a>>> wrote:<br>
> > > >> > ><br>
> > > >> > > Cheers for the look-in :) I agree we should be looking at the<br>
> > > >> > > general case ... sorry for the short-sighted bug report!<br>
> > > >> > ><br>
> > > >> > > Thought about the idea of putting things in<br>
> > > openstack-infra/config<br>
> > > >> > > too, but discarded it. Essentially, I think we can do this<br>
> > > without<br>
> > > >> > > putting additional review load on openstack-infra. Having a<br>
> > > >> > > bare-bones configuration in openstack-infra/config that points<br>
> > > to<br>
> > > >> > > scripts in docs-controlled repositories would enable us to be<br>
> > > much<br>
> > > >> > > more responsive to updates, and means we don't need to bother<br>
> > > >> > > infra :)<br>
> > > >> > ><br>
> > > >> > > The last few patches I put through to config are took1-3 weeks<br>
> > > to<br>
> > > >> > > get through. Importantly, this is completely fine - our patches<br>
> > > >> > > are<br>
> > > >> > > definitely low priority compared to others, and beingtypically<br>
> > > >> > > less<br>
> > > >> > > skilled at the ways of jenkins-job-builder we do want the time<br>
> > > >> > > spent<br>
> > > >> > > on thorough review from the overworked infracores.<br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > > I ask for eyeballs in #openstack-infra if I have a review delay.<br>
> > > They<br>
> > > >> > > also have a separate Jenkins job review team so for these types of<br>
> > > job<br>
> > > >> > > additions I think your experience is atypical.<br>
> > > >> > ><br>
> > > >> > > I've put this patch in: <a href="https://review.openstack.org/#/c/43734/">https://review.openstack.org/#/c/43734/</a> as<br>
> > > a<br>
> > > >> > > fix. Basically the zuul layout file is running in openstack-manuals<br>
> > > >> > > and<br>
> > > >> > > should run for operations-guide. What I'm unsure of, though, is<br>
> > > >> > > whether<br>
> > > >> > > the same pom.xml is used for non-english output. David orDaisy can<br>
> > > >> > > you<br>
> > > >> > > review?<br>
> > > >> ><br>
> > > >> > mm. I hadn't realised we're already in this state:<br>
> > > >> ><br>
> > > >> > > 2) Copy the tools into the openstack-ops repo and<br>
> > > perform<br>
> > > >> > > the painful<br>
> > > >> > > ongoing task of keep them synchronised<br>
> > > >> ><br>
> > > >> > If that's the decision, then it's an easy-to-fix patch in config.<br>
> > > >> > However, I think this state is sub-optimal. I note that the tools<br>
> > > >> > directory in operations-guide is already way out of sync with the one<br>
> > > in<br>
> > > >> > operations-manual, bolstering the claim somewhat :)<br>
> > > >> ><br>
> > > >> > I also still feel that moving tools into openstack-infra/<br>
> config is not<br>
> > > >> > the solution - and it appears my point above has been missed ... it's<br>
> > > >> > not entirely about the timing! It's also about adding to the workload<br>
> > > of<br>
> > > >> > a busy team, and whose 'job' it is to review what.<br>
> > > >> ><br>
> > > >> > My advice would be to take a look at what nova, neutron et al do with<br>
> > > >> > their 'tools' directories.<br>
> > > >> ><br>
> > > >> > Regards,<br>
> > > >> ><br>
> > > >> > Tom<br>
> > > >> ><br>
> > > >> ><br>
> > > >> ><br>
> > > >> > > Thanks,<br>
> > > >> > > Anne<br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > > However, this doesn't seem like a tenable situation for the<br>
> > > tools,<br>
> > > >> > > given the amount of churn we're going through right now<br>
> > > (consider<br>
> > > >> > > eg<br>
> > > >> > > validate.py!). I think it would seriously slow things down for<br>
> > > >> > > something that could potentially be done another way.<br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > > Regards,<br>
> > > >> > ><br>
> > > >> > > Tom<br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > > On 25/08/13 01:17, Anne Gentle wrote:<br>
> > > >> > ><br>
> > > >> > > Is there an option to store the tool in<br>
> > > openstack-infra/config<br>
> > > >> > > and<br>
> > > >> > > point it at different repos? They're already <br>
> running scripts<br>
> > > >> > > to send<br>
> > > >> > > Horizon strings to transifex. This makes me think so:<br>
> > > >> > > <a href="https://review.openstack.org/#__/c/32824/3/modules/">https://review.openstack.org/#__/c/32824/3/modules/</a><br>
> > > >> ><br>
> > > >> ><br>
> > > openstack___project/files/jenkins_job___builder/config/<br>
> translation-__jobs.yaml<br>
> > > >> > > <<a href="https://review.openstack.org/#/c/32824/3/modules/">https://review.openstack.org/#/c/32824/3/modules/</a><br>
> > > >> ><br>
> > > >> ><br>
> > > openstack_project/files/jenkins_job_builder/config/translation-jobs.yaml><br>
> > > >> > ><br>
> > > >> > > Plus<br>
> > > >> > > <a href="https://review.openstack.org/#__/c/34700/3/modules/">https://review.openstack.org/#__/c/34700/3/modules/</a><br>
> > > >> > jenkins/__files/slave_scripts/propose___translation_update_manuals.sh<br>
> > > >> > > <<a href="https://review.openstack.org/#/c/34700/3/modules/jenkins/">https://review.openstack.org/#/c/34700/3/modules/jenkins/</a><br>
> > > >> > files/slave_scripts/propose_translation_update_manuals.sh><br>
> > > >> > > points to a repo and a folder.<br>
> > > >> > ><br>
> > > >> > > It's from one the original patches Daisy sent through to<br>
> > > start<br>
> > > >> > > translations. Clark or Jeremy, do you know if a change in<br>
> > > the<br>
> > > >> > > config<br>
> > > >> > > project would do what's needed -- slice docs fromany repo?<br>
> > > >> > ><br>
> > > >> > > It's important to figure out because the next <br>
> priority to me<br>
> > > >> > > would be<br>
> > > >> > > the API quick start in the openstack/api-site <br>
> repo, then the<br>
> > > >> > > install<br>
> > > >> > > guides, so we have at least 3 repos with docs to translate.<br>
> > > We<br>
> > > >> > > could<br>
> > > >> > > put all the high-priority-to-translate docs in one repo but<br>
> > > >> > > that<br>
> > > >> > > seems<br>
> > > >> > > too rigid. Let's find a way.<br>
> > > >> > ><br>
> > > >> > > Thanks,<br>
> > > >> > > Anne<br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > > On Aug 23, 2013, at 7:23 PM, Tom Fifield <tom@openstack.org<br>
> > > >> > > <<a href="mailto:tom@openstack.org">mailto:tom@openstack.org</a>>> wrote:<br>
> > > >> > ><br>
> > > >> > > Hi all,<br>
> > > >> > ><br>
> > > >> > > Just throwing this bug out there for your comment to<br>
> > > >> > > select<br>
> > > >> > > a way forward:<br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > > <a href="https://bugs.launchpad.net/__openstack-manuals/+bug/1216153">https://bugs.launchpad.net/__openstack-manuals/+bug/1216153</a><br>
> > > >> > ><br>
> > > >> > > <<a href="https://bugs.launchpad.net/openstack-manuals/+bug/1216153">https://bugs.launchpad.net/openstack-manuals/+bug/1216153</a>><br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > > The build job for the Japanese version of theOperations<br>
> > > >> > > Guide was<br>
> > > >> > > merged at: <a href="https://review.openstack.org/#__/c/39846/">https://review.openstack.org/#__/c/39846/</a><br>
> > > >> > > <<a href="https://review.openstack.org/#/c/39846/">https://review.openstack.org/#/c/39846/</a>><br>
> > > >> > ><br>
> > > >> > > However, from the first run of the job (logs:<br>
> > > >> > > <a href="https://jenkins01.openstack.__org/job/openstack-">https://jenkins01.openstack.__org/job/openstack-</a><br>
> > > >> > operations-__guide-ja/1/console<br>
> > > >> > > <<a href="https://jenkins01.openstack.org/job/openstack-">https://jenkins01.openstack.org/job/openstack-</a><br>
> > > >> > operations-guide-ja/1/console>)<br>
> > > >> > > it becomes clear that it fails due to the split<br>
> > > >> > > repositories.<br>
> > > >> > ><br>
> > > >> > > 2013-08-23 23:42:49.457 | cp: cannot stat<br>
> > > >> > > `./doc/src/docbkx/openstack-__ops': No such file or<br>
> > > >> > > directory<br>
> > > >> > ><br>
> > > >> > > To fix this, we either need to:<br>
> > > >> > ><br>
> > > >> > > 1) Check out the openstack-ops repo into manuals for<br>
> > > build<br>
> > > >> > > time<br>
> > > >> > ><br>
> > > >> > > 2) Copy the tools into the openstack-ops repo and<br>
> > > perform<br>
> > > >> > > the painful<br>
> > > >> > > ongoing task of keep them synchronised<br>
> > > >> > ><br>
> > > >> > > 3) move openstack-ops back into the openstack-manuals<br>
> > > repo<br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > > Regards,<br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > > Tom<br>
> > > >> > ><br>
> > > >> > > _________________________________________________<br>
> > > >> > > Openstack-docs mailing list<br>
> > > >> > > Openstack-docs@lists.__openstack.org<br>
> > > >> > > <<a href="mailto:Openstack-docs@lists.openstack.org">mailto:Openstack-docs@lists.openstack.org</a>><br>
> > > >> > > <a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/">http://lists.openstack.org/__cgi-bin/mailman/listinfo/</a><br>
> > > >> > __openstack-docs<br>
> > > >> > > <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/">http://lists.openstack.org/cgi-bin/mailman/listinfo/</a><br>
> > > >> > openstack-docs><br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > ><br>
> > > >> > > --<br>
> > > >> > > Anne Gentle<br>
> > > >> > > annegentle@justwriteclick.com <<a href="mailto:annegentle@justwriteclick.com">mailto:annegentle@justwriteclick.com</a><br>
> > > ><br>
> > > >> ><br>
> > > >> ><br>
> > > >> > _______________________________________________<br>
> > > >> > Openstack-docs mailing list<br>
> > > >> > Openstack-docs@lists.openstack.org<br>
> > > >> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
> > > >> ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > --<br>
> > > > Anne Gentle<br>
> > > > annegentle@justwriteclick.com<br>
> > ><br>
> > > _______________________________________________<br>
> > > Openstack-docs mailing list<br>
> > > Openstack-docs@lists.openstack.org<br>
> > > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
> > ><br>
> > <br>
> > <br>
> > <br>
> > -- <br>
> > Anne Gentle<br>
> > annegentle@justwriteclick.com<br>
> > <br>
> > <br>
> <br>
> _______________________________________________<br>
> Openstack-docs mailing list<br>
> Openstack-docs@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
> <br>
</font></tt></body></html>