Created
July 23, 2013 12:13
-
-
Save akesterson/6061911 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(1:39:33 PM) unxmaal: is it better to have a very short list, basically common and nodename, and then apply classes to each node, or to have a "container" for each "node type" that'd then include the classes? | |
(1:50:39 PM) akesterson: mmm you're talking about how to specify which systems get which puppet classes? | |
(1:51:29 PM) unxmaal: yeah | |
(1:51:46 PM) unxmaal: did you use hiera yet? | |
(2:00:40 PM) unxmaal: that's the main issue now: what method do i use to tell hiera what kind of system something is? | |
(2:15:14 PM) akesterson: sorry been busy | |
(2:15:33 PM) akesterson: So the real problem you're facing here is the lack of any ENC | |
(2:16:08 PM) akesterson: and faced with the lack of ENC, you only have 2 options: | |
(2:16:08 PM) akesterson: 1- Use hiera data to determine, automagically, by either the hostname or some other tag, like you said | |
(2:16:08 PM) akesterson: 2- have the system itself tell you that through facter | |
(2:18:28 PM) akesterson: http://www.slideshare.net/PuppetLabs/roles-talk <-- this is a talk on using the 'role pattern' to classify what systems get on which nodes | |
(2:19:20 PM) akesterson: Basically, puppet node classification without relman is going to make you hate life so hard, and make you understand why I said "hiera was ALMOST relman" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment