| stan | what logs should I see for nova live migration failure apart from nova_compute on both hosts | 03:21 |
|---|---|---|
| *** srelf_ is now known as Continuity | 09:33 | |
| _piotrek | frickler: thanks for your reply last week - I was able to generate the PDF for openstack-ansible's deployment guide by installing all the requirements from doc/requirements.txt, copying doc/Makefile to deploy-guide/ and then running make latexpdf in deploy-guide - cheers! | 13:37 |
| jrosser_ | _piotrek: please do ask questions about openstack-ansible in the #openstack-ansible channel | 13:49 |
| jrosser_ | if there are missing docs builds then we would like to know about it | 13:50 |
| noonedeadpunk | fungi: do you know if there;s a good reason to disable pdf for deploy guides? https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/jobs.yaml#L1116 | 14:14 |
| fungi | noonedeadpunk: pdf doc generation usually has extra dependencies and takes a relatively long time to complete, but other than that i don't know | 14:15 |
| noonedeadpunk | we just do that in fact for all docs, rather then deploy-guide it seems | 14:16 |
| fungi | is it assumed to be correctly set up for all projects? | 14:16 |
| noonedeadpunk | that is a good question | 14:16 |
| noonedeadpunk | but then: https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/jobs.yaml#L777 | 14:16 |
| fungi | if memory serves, it relies on an additional tox env definition and possibly also some extra dependency management in each project | 14:16 |
| noonedeadpunk | `openstack-tox-docs` - I bet it's used for all projects, but unlikely to be configured | 14:17 |
| noonedeadpunk | *properly for all of them | 14:17 |
| noonedeadpunk | ok, I guess we can try, as we do have a child job to deploy guide... | 14:17 |
| fungi | noonedeadpunk: e.g. https://opendev.org/openstack/nova/src/branch/master/tox.ini#L230-L239 | 14:18 |
| fungi | called from https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/roles/build-pdf-docs/defaults/main.yaml#L2 | 14:19 |
| noonedeadpunk | yeah, jsut it seems that only 3 projects right now have deployment guides - osa, kolla and charms? | 14:19 |
| noonedeadpunk | https://docs.openstack.org/2023.2/deploy/ | 14:20 |
| noonedeadpunk | I will try | 14:20 |
| fungi | noonedeadpunk: also you may need to add packages to your bindep.txt tagged with the pdf-docs profile like https://opendev.org/openstack/nova/src/branch/master/bindep.txt#L48-L50 | 14:21 |
| noonedeadpunk | fungi: we do build that for regular docs, but not for deployment guide: https://opendev.org/openstack/openstack-ansible/src/branch/master/tox.ini#L52-L58 | 14:23 |
| noonedeadpunk | so I was thinking if there's smth that might block explicitly | 14:23 |
| noonedeadpunk | in openstackdocstheme or smth... | 14:24 |
| fungi | no idea. i expect it's just that nobody ever configured the deploy guides for pdf generation | 14:24 |
| fungi | but as you try turning it on you may encounter other spots where support for it hadn't been implemented yet | 14:25 |
| noonedeadpunk | fungi: do you recall from top of your head if I can override vars on the job_template, like it's done with files here: https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/project-templates.yaml#L2821-L2828 | 14:28 |
| fungi | i don't recall. there are some things that can't be overridden through a project-template since it's a pipeline addition not a job/variant definition | 14:29 |
| fungi | if you can override something in a pipeline, then i think you can do it in a project-template too | 14:29 |
| noonedeadpunk | yah | 14:29 |
| noonedeadpunk | I was surprised you can do with files actually | 14:30 |
| fungi | https://zuul-ci.org/docs/zuul/latest/config/project.html#project-template mentions not being able to set branch matchers | 14:31 |
| fungi | noonedeadpunk: https://zuul-ci.org/docs/zuul/latest/config/project.html#attr-project.%3Cpipeline%3E | 14:32 |
| noonedeadpunk | mhm, okey, thanks! | 14:33 |
| fungi | "...it is treated as a job variant local to this project and pipeline. In that case, the format of the dictionary is the same as the top level job definition. Any attributes set on the job here will override previous versions of the job." | 14:33 |
| fungi | and then the project-template section says "A Project Template defines one or more project-pipeline definitions which can be re-used by multiple projects." | 14:33 |
| fungi | so from that i infer you can | 14:33 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!