I have since found out that actually using puppet standalone and node classifier is possible. In our tests, we added the classifier to the wrong part of the config file which is probably why we didn't get very far. Good news is this makes everything simpler. Still very happy to hear your thoughts and hear any recommendations.
Thanks On Jul 4, 10:17 am, Tass Skoudros <[email protected]> wrote: > A little history, I work with a small startup and we are looking at > rolling out a automated cloud based provisioning platform. We have a > dilemma and i wanted to ask your communities thoughts. > > As far as I am aware there are 3 ways to run puppet, standalone with > puppet, Client/Server and a hybrid of client/server and rsync. The > last of these wouldn't work very well in our case so I am not looking > at it as a potential solution. > > We have tried the standalone, its slick. To me the standalone method > is intended to address a need thats something entirely different to > what we require. I moved on. > > I then went on to the client/server method. Essentially there are 2 > ways this can work, the first is we(startup) control the master and > deploy clients. The second is we deploy master+client on every server, > the configuration would point to our external node web service. > > Each has its own advantage and we will be using external nodes to load > the configurations in both cases. The differences are that the first > would quickly become an issue when the version of the puppet client > changes. So we have been exploring the second of these and still have > other encounters that break with our goal of full automation. > > So my question, is there a better way? Am I missing something. -- 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.
