Hello, ----- "Douglas Garstang" <doug.garst...@gmail.com> a écrit : | I was just doing a little research on the best way to switch over to | external nodes. It seems like you can't use a combination of the two | systems. Apparently if the external node tool can't find an external | node (because it hasn't been cut over yet), then that's a failure. | This makes moving from 'internal' nodes to external nodes BLOODY | difficult.
Yup, lookup is done only in one system : node file or external nodes. | I saw this old thread where someone else was in a similar situation: | "> 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. | " | | And a certain person, who shall remain nameless, seems somewhat | detached from reality, when his response to that issue was: | "Then add support for a default node." | | Just how is that going to help? If you define a default external | node, | the error will go away, but since your internal node is now defined | as | a default external node that does nothing, any future changes to the | internal nodes until they are cut over and going to be ignored. | Nice... nice... I leave nodes without a definition fail but you can also setup a class that reports that this node has no entry in the external node definitions with tag or an exported file. Nico. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
