Yeah, I seen that post, which gave me hope that my approach is possible.
So can the global iPXE template quoted in the code be managed in foreman
On Thursday, 10 August 2017 14:21:52 UTC+1, Lukas Zapletal wrote:
> Git blame shows me
I use Katello for a while and noticed that the space occupied by the
packages in /var/lib/pulp is constantly growing.The task of cleaning up
orphaned packages is performed regularly, however, no packet removal occurs.
Katello shows that the packages are not included in any repository:
Foreman 1.15.3 is now available with bug fixes for twenty nine issues.
Notably problems with permissions, CSV export and much more, check out
the release notes for the full list of changes:
Please report any bugs using our tracker (see
Git blame shows me
See the discussion, it is a very limited support basically just for
On Thu, Aug 10, 2017 at 2:06 PM, Conor Mc Garvey wrote:
> Hi Lukas,
> We have servers that we wish to provision using
We have servers that we wish to provision using UEFI and from testing we
have found that iPXE is the most stable across all cases.
I have found the following code in "foreman-proxy/modules/tftp/server.rb"
which indicates that iPXE does serve a "Global Default" through the
to be honest, I am really not sure what you are trying to do. We do
have some iPXE support in Foreman, but this is mostly limited to iPXE
template type, so you can use Foreman to generate its contents. If
your intention is to have Foreman to supply custom DHCP filename
I'm looking to use an iPXE script delivered over HTTP as my global default.
This is to make use of the "3 state boot" in pure iPXE.
- *Known to Foreman and in Build mode*
- *A MAC-specific PXE file is written (OS-specific