1

Utilizing an alternate CA (Like Microsoft Certificate Services) with Puppet

view story
linux-howto

http://serverfault.com – I'm investigating whether I can somehow make the puppet ecosystem utilize our existing Microsoft Enterprise CA rather than being its own CA. Since puppet touts that all of the system is "standard SSL", my guess is that it is completely possible to do this without much changing of puppet, HOWEVER it's likely a huge manual headache unless puppet is edited to make the proper calls to the enterprise CA. Has anyone tried this before? Is it a "here be dragons, turn away!" situation? (HowTos)

dayu's picture
Submitted by dayu on 11/29/2012

Stories similar to Utilizing an alternate CA (Like Microsoft Certificate Services) with Puppet

Puppet Labs, provider of open source systems management solutions, announced the release of Puppet Enterprise, the first commercially supported version of Puppet.

I am learning puppet and using this tool install puppet clients on nodes.

puppet node install --login=root --keyfile=~/.ssh/id_rsa --install-script puppet-enterprise --installer-payload ~/puppet/puppet-enterprise-2.7.0-ubuntu-12.04-amd64.tar.gz --installer-answers ~/puppet/installer.answers --puppetagent-certname puppet.node01.example.com 192.168.1.100

Everything seems to work ok.

Cannot use puppet on mac osx 10.8, i can find it in /usr/bin/lib but display that when i launch it :

/usr/bin/puppet:3:in `require': no such file to load -- puppet/util/command_line (LoadError) from /usr/bin/puppet:3

Any idea ?

Edit : I want to use puppet in Vagrant VM to do provisioning is it the good way ?

Puppet – Open source data centre automation and configuration management framework ERB – Powerful templating system for Ruby Puppet Recipes – Recipes for configuring Puppet Puppet Dashboard – Web interface and reporting tool for Puppet

I have 40 Ubuntu 12.04 servers. These servers are managed with puppet. Sometimes I have problem with puppet agent. puppet agent spawn child process (sh) and this process fails. Sh is zombie process. Puppet doesn't work, I must restart puppet agent to make it works.

I use puppet to manage files, packages and services. Problematic agent didn't make any change before fails, server is up to date.

I'm running puppet 2.7.9 on a Debian Squeeze system.

When service is described with both ensure => running and subscribed to config file changes if both conditions fulfil (i.e. it is not running and config file changed) it gets (re)started twice.

Vagrant / puppet workflow 50 weeks 18 hours ago

I'm new to puppet and vagrant, but I'm developing my own Puppet manifests intended to set up a vagrant box. That is, the puppet manifest is in my Vagrant directory on the host machine, and vagrant is invoking puppet -- there is no puppet server.

The thing is, my workflow is:

while(not working as desired) { vagrant destroy amend manifest vagrant up }

...

I'm learning my way through configuration management in general and using puppet to implement it in particular, and I'm wondering what aspects of a system, if any, should not be managed with puppet?

As an example we usually take for granted that hostnames are already set up before lending the system to puppet's management.