On Wed, Sep 20, 2017 at 04:24:53AM +0000, Dan Callaghan wrote: > Excerpts from Jan Stancek's message of 2017-09-14 03:08 -04:00: > > Dan, > > > > I'd like to return to original question in this thread. You replied: > > > > > Yes I think this should work and would be a good workaround for the > > > short term. > > > > > > We would just need to make sure that the new fake distro tree is not > > > picked up by beaker-pxemenu to be included in the PXELINUX menu. If it > > > is included in the menu, the kernel+initrd will be cached on the LC and > > > beaker-provision will just re-use the cached images instead of > > > re-downloading them each time. > > > > How can we do that? Is this a config option or would this require > > some code changes? > > The distros to be included in the PXE menu is configurable. It's set in > the cron job which invokes the beaker-pxemenu command. In our > configuration it's here: > > https://gitlab.infra.prod.eng.rdu2.redhat.com/ansible-roles/beaker/blob/master/lab-controller/templates/etc/cron.hourly/beaker_pxemenu.j2 > > Right now, the `beaker_pxemenu_xml_filter` Ansible variable is not > defined for stage/prod, which means all distros are being included in > the menus. I think at Jeff Burke's request. :-) But we can define > a filter which matches everything *except* your new fake distro. > Essentially in inventory/group_vars/beaker we would put: > > beaker_pxemenu_xml_filter: '<not><distro_family value="SKT7"/></not>'
Hi Dan, Is that something we can quickly test/'play around with' in the beaker-in-a-box setup? I am not sure how often engops will play with that setting. And if they do I want to make sure it works correctly. :-) Cheers, Don _______________________________________________ Beaker-devel mailing list -- beaker-devel@lists.fedorahosted.org To unsubscribe send an email to beaker-devel-le...@lists.fedorahosted.org
