> > I really don't want to SSH into the Foreman host after setting it up, and > install stuff manually. How do I set things up that a Forman system is set > up, including a Puppet configuration under version control in > /etc/puppetlabs, practically from zero? Every step I need to do manually > is somewhat wasted time, and potential to introduce errors. I want to avoid > that. > > Unless you are in a situation where you are installing new Foreman hosts > on a regular basis I think you're being a bit extreme. There is a point at > which automation no longer gives you a return on investment. >
No, I'm not extreme. I need consistency and the ability to reproduce an environment exactly and very fast (e.g. when we need to do trouble shooting or recovery). Setting up configuration management is only a side-business in our DevOps-driven business, one puzzle piece of many. We need to unleash all powers for implementing product features. The less time we spend managing our infrastructure and doing trouble shooting when things go wrong, the better. The behavior I describe should go into the installer - or more generally into the overall setup procedure -, and everyone should be encouraged to do it "the right way". No more tinkering on the Foreman host, no more uncontrolled changes when you use Foreman (and Puppet). When we think in terms of "open source" we're of course installing new Foreman hosts on a regular basis. So, we're all set. Peter -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
