James Turnbull <ja...@puppetlabs.com> writes:
> Kikanny wrote:
>
>> Thank you all for taking your time to explain it to me. I guess I'll give
>> it a whirl and see how it goes. Another question I have is what if the
>> person managing a web server does not have full knowledge of whatever is
>> installed in a server or there was some other configuration management in
>> place. How would I bring that under puppet's control? I'm asking this
>> because we do have servers like that. Thanks!
Write down what you need the new server to do. Then build something to do
that, using puppet, on a new system.
When that doesn't work (which, inevitably, it won't the first time) work out
what went wrong — was it your "what it does" notes, or the puppet side?
Fix that, and go back to the first step until it works. :)
> In the lack of full knowledge instance, "ralsh" is definitely your friend.
> It's a good tool to get the basics about a host.
>
> In the latter instance, I don't see that it matters if another configuration
> management system was in place - just remember to turn it off so you don't
> get conflicting management of resources!
*nod* You might be able to read the "instructions" in the other configuration
management tool, though, to head-start building the puppet side of things.
Daniel
--
✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
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.
