Hi Pablo, I have done a number of on-site consultations and implemented Hiera with very positive results. To answer a couple of your questions:
1. You don't NEED to have a YAML file for every node in your infrastructure, but if you need to overwrite values that are set at lower levels of the hierarchy then you CAN create one and set parameter values that are node-specific (if that makes sense). 2. You can alter your hierarchy 'on-the-fly', but need to consider how that will impact your current environment. Levels can be added, but they must be based on fact values - so you do need to create a 'role' fact or 'environment' fact to correspond with adding 'role' or 'environment' in your hierarchy. Feel free to ask any more questions that you may have. On Thu, Mar 15, 2012 at 3:02 AM, Pablo Fernandez <[email protected]>wrote: > Hi, > > After some time playing with Puppet, I came to realize simple node > inheritance > with includes is not enough, and you may experience unwanted results. Then > I > started playing with the External Node Classifier that Puppet Dashboard > brings > in, and even though they implement node groups the way one would expect > (much > better than native inheritance), I see various problems with it: > - You introduce an external service, that if it breaks, may lead to > disaster. > I want to keep things simple. > - If you want to do staging (production, development...) it forces you to > do > it its way, and I found no reasonable way to merge the stages the way I > like. > - It does not have version control. > - Additionally, it does not support arrays or hashes as of today. > > I have found an alternative, that is using Hiera as a node classifier. It > will > allow me to have everything inside the same tree (that I can do version > control with) I even found you can pass class parameters (within this very > same list: http://www.mail-archive.com/puppet- > [email protected]/msg28134.html ). > > But before diving into that see, I want to ask you: have any of you done > this? > What is your level of satisfaction? Is there anything you miss? > > I also found quite anoying having to have at least one .yaml file per node, > specially when you have hundreds of nodes. Also, you must know all the > facts > before starting with the hierarchy, you can't modify/include .yaml files > on the > fly (if you want to have machine groups, you need to have them as facts, > essentially forcing you to do two runs every time you change a group). How > do > you overcome this limitation? > > Thanks a lot, > Pablo > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" 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-users?hl=en. > > -- Gary Larizza Professional Services Engineer Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
