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 collecting this data can be moved to smart-proxy too. OT: HA smart-proxy setups are hard b/c proxy wasn’t engineered for HA, and different HA setups require different approaches (HA dhcp is different from HA dns, etc). It very much solvable, but it’s a fair bit of work and so far I was unable to get a clear answer about how important is to have such a feature. -d On Thu, Jan 26, 2017 at 3:21 PM, Lukas Zapletal <l...@redhat.com> wrote: > On Thu, Jan 26, 2017 at 11:16 AM, Timo Goebel <m...@timogoebel.name> wrote: >> How do you want to handle the "built"-Url? I think, you still need a >> callback to Foreman when a Host has finished provisioning. That basically >> voids most of the advantages (like improving reliability - btw: a Foreman ha >> is easy vs. a smart-proxy ha setup is hard). > > Yeah, sure, I noticed this too, but this built call is special - no > output, no need of determining template API endpoint etc. It's a very > simple case. > >> I do think, it's a good idea that Foreman knows the current state of an >> installation. We could even show valueable information on the provisioning >> progress or potential errors like with [2]. That would be a huge benefit for >> users, at least from my experience. > > My proposal does not change that, I believe. Template contents audit > is something I miss from the day one when I started with foreman and > pre-rendering could basically help with that - we could put whole > template content into audit record during build, so we can be sure > clients see the exactly same. > > -- > Later, > Lukas @lzap Zapletal > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
