hello, ----- "Markus Roberts" <[email protected]> wrote:
> * Sites that need this functionality can set up a starting environment > for nodes that only pushes the configuration file, and the > configuration file can be a template filled in with the appropriate > external_node parameters. This will require an extra cycle for new > nodes and for existing nodes when their environment changes at such > sites, but would not require any code changes or have any impact on > sites that don't need it. I'd say this should be the last resort, I've seen several places that changes a machines environment fairly often, during maintenance periods for example. Forcing the environment change to only happen after another run would be very bad for them. > * Change puppet to request the node information from the server before > anything else (e.g. before plugins). This would have a small overhead > for all puppet runs and necessitate a moderately small code change. nice. > * Change the default environment on the client to a special "ask the > server" environment. Clients that specified an environment in their > configuration or on the command line would use that environment. > Clients that did not specify an environment would request it from the > server, imposing a small overhead only for machines that needed it. > This would require a somewhat larger code change. Even nicer. I assume we can then specify on the server the default environment that all unconfigured nodes would end up in? This would be very nice indeed. Keeping in mind that it is also very desirable to be able to set the environment via a fact. -- R.I.Pienaar --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
