On Sep 27, 2008, at 3:01 PM, Eric Moore wrote: > > Luke Kanies <[EMAIL PROTECTED]> writes: > >> On Sep 26, 2008, at 4:11 PM, Eric Moore wrote: >> >>> When does the internal node definition get used, i.e. under what >>> circumstances? What do the internal nodes do in combination with >>> the >>> external tool, and under what circumstances? >> >> >> The internal and external node systems are essentially parallel ways >> of configuring nodes. If you have any nodes defined in the language, >> then Puppet will similarly fail if a given client doesn't match an >> internal node definition. >> >> And the two systems are entirely orthogonal -- they can do similar >> work, but they work with entirely separate mechanisms and they >> neither >> conflict nor work together. > > So if there's information in the external and internal systems... > Which one gets used? Or?
Both. > >> Yes, it's confusing, but the previous model -- where you couldn't use >> them together -- was apparently even more confusing. >> >> It's pretty easy, really: If you use a given node system, every >> client must have an entry in that node system. You should probably >> stick to just one of them. > > Well, we're trying to switch from one to the other, and was hoping to > not have to fully populate the external tool all at once and use it > everywhere. Then add support for a default node. -- Reality is that which, when you stop believing in it, doesn't go away. -- Philip K. Dick, "How to Build a Universe" --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
