I think this is a good idea; and it can be pushed into separating
templates into a standalone service which would handle the whole
template lifecycle, not just serving of pre-rendered templates (if
eventually).
Also agreed re: “built” ping, it’s a special call, although the
responsibility for
Hi all,
So I've had a few offers of help with the booth (thanks!), but it's not
generally available info. Time to fix that.
I've added a booth-duty section to the top of the speakers pad[1] (which I
totally need to clean up once this is all over :P). I don't want to make
this majorly formal, but
Thaks for summary, just one quick comment where I think it needs clarification
On středa 25. ledna 2017 13:59:57 CET Lukas Zapletal wrote:
> Corrections.
>
> > Why you don't like explicit lock actions?
>
> I misinterpreted your statements above, looks like we both like
> explicit locking.
>
>
Hey,
our design of template proxying is not good, I constantly need to
solve problems setting it up. In order to have this working, both
Templates and TFTP features needs to be turned on. This is confusing,
then several Proxy settings need to be correctly set and since the
names are also
Hi,
> our design of template proxying is not good
I don't think, it's that bad. Your suggestion does have it's advantages,
though. From a security perspective it would be great if the smart-proxy
wouldn't need any calls to Foreman.
> The downside is that Smart Proxy would be required in
I'll comment on the rest of this when I have time to think it over, however I
do want to correct one point:
On Thursday, 26 January 2017 10:27:47 CET Lukas Zapletal wrote:
> This is only relevant to provision, iPXE and script templates, all the
> others are not affected by this. PXE templates
