<html><body>
<p><font size="2" face="sans-serif">Hi, Tom and Anne</font><br>
<br>
<font size="2" face="sans-serif">These scripts are similar with what nova or horizon use to generate their pot files, </font><br>
<font size="2" face="sans-serif">like "setup.py" in nova or "./run_tests.sh" in horizon.</font><br>
<br>
<font size="2" face="sans-serif">So I think there should be a "tools" folder under each documentation repository.</font><br>
<font size="2" face="sans-serif">The question is how can we maintain a single version but use them in several different repositories.</font><br>
<br>
<font size="2" face="sans-serif">Do you know how openstack maintain the common folder (Oslo project)?</font><br>
<font size="2" face="sans-serif">I think each openstack project copies it when checking out?</font><br>
<font size="2" face="sans-serif">Or has a script to check out to a specific folder?</font><br>
<br>
<font size="2" face="sans-serif">Daisy</font><br>
<br>
<tt><font size="2">Tom Fifield <tom@openstack.org> wrote on 2013/08/28 06:22:02:<br>
<br>
> Tom Fifield <tom@openstack.org> </font></tt><br>
<tt><font size="2">> 2013/08/28 06:22</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>
> 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 openstack-infra/config<br>
> > too, but discarded it. Essentially, I think we can do this without<br>
> > putting additional review load on openstack-infra. Having a<br>
> > bare-bones configuration in openstack-infra/config that points to<br>
> > scripts in docs-controlled repositories would enable us to be much<br>
> > more responsive to updates, and means we don't need to bother infra :)<br>
> > <br>
> > The last few patches I put through to config are took 1-3 weeks to<br>
> > get through. Importantly, this is completely fine - our patches are<br>
> > definitely low priority compared to others, and being typically less<br>
> > skilled at the ways of jenkins-job-builder we do want the time 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. They<br>
> > also have a separate Jenkins job review team so for these types of 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 a<br>
> > fix. Basically the zuul layout file is running in openstack-manuals and<br>
> > should run for operations-guide. What I'm unsure of, though, is whether<br>
> > the same pom.xml is used for non-english output. David or Daisy can 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 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 in<br>
> operations-manual, bolstering the claim somewhat :)<br>
> <br>
> I also still feel that moving tools into openstack-infra/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 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 tools,<br>
> > given the amount of churn we're going through right now (consider 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 openstack-infra/config and<br>
> > point it at different repos? They're already running scripts 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>
> openstack___project/files/jenkins_job___builder/config/translation-__jobs.yaml<br>
> > <<a href="https://review.openstack.org/#/c/32824/3/modules/">https://review.openstack.org/#/c/32824/3/modules/</a><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 start<br>
> > translations. Clark or Jeremy, do you know if a change in the config<br>
> > project would do what's needed -- slice docs from any repo?<br>
> > <br>
> > It's important to figure out because the next priority to me<br>
> > would be<br>
> > the API quick start in the openstack/api-site repo, then the install<br>
> > guides, so we have at least 3 repos with docs to translate. We could<br>
> > put all the high-priority-to-translate docs in one repo but 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 select<br>
> > a way forward:<br>
> > <br>
> > <a href="https://bugs.launchpad.net/__openstack-manuals/+bug/1216153">https://bugs.launchpad.net/__openstack-manuals/+bug/1216153</a><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 the Operations<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 repositories.<br>
> > <br>
> > 2013-08-23 23:42:49.457 | cp: cannot stat<br>
> > `./doc/src/docbkx/openstack-__ops': No such file or directory<br>
> > <br>
> > To fix this, we either need to:<br>
> > <br>
> > 1) Check out the openstack-ops repo into manuals for build time<br>
> > <br>
> > 2) Copy the tools into the openstack-ops repo and perform<br>
> > the painful<br>
> > ongoing task of keep them synchronised<br>
> > <br>
> > 3) move openstack-ops back into the openstack-manuals 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>
> 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>