On Wed, Nov 25, 2009 at 12:21 PM, Luke Kanies <[email protected]> wrote:
> Well, the environment doesn't matter for the files, because it's > included in the URI itself. But not in localconfig.yaml right? So if you fail on your initial connection, and continue to apply a cached catalog, don't you fall back to the same problem? >>> Is this a reasonable approach? It's obviously not sufficient for >>> 0.25.2, but I think it's a better long term direction. >> >> So for me this all depends on how well it scales... happy to do tests. >> >> Is it perhaps feasible to have the server tell the client to resubmit >> the fact values to it if it doesn't have a fresh cache? I have this >> nagging feeling I already brought up this in the past and it wasn't >> feasible. > > > You have the same problem, don't you? If we push new data, it could > again end up at the wrong host. I assumed if a specific server requested the info, it would be delivered to that server. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
