Ignore everything I wrote -- my configuration file which started up
the puppet master sets the --certname, however it was corrupt after a
config tweak. Fixing that fixed the communication.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post
A quick overview of our setup:
We have an EBS-backed puppet master instance with an Elastic IP, and a
number of puppet agent AMI images in various regions. When these AMIs
were created, they were authenticated with the puppet master using the
following command:
# puppet agent --certname=$(cat /et
Hi all
I'm trying to set up a separate puppet master and client on EC2. I've
used two instances of CentOS5.4 with nothing other than the base
install and have installed puppet via the ruby gems. Puppet is at
2.6.4 on both machines.
I've been following the guide to get a basic configuration workin
On Feb 16, 2:40 pm, Nigel Kersten wrote:
> Where does it say this Phillip? We must have some unclear documentation.
http://docs.puppetlabs.com/guides/configuring.html#configure-dns-optional
It is quite confusing... I struggled for a moment getting a puppet-
master daemon running, too - the confi
In the docs it says one must add a line to the /etc/hosts file with
the name "puppet" and the IP of the puppet master. This isn't a
possibility for us as the IP is subject to change. Is it possible to
configure the puppet clients to look for a specific domain to find the
master? eg. "puppetmaster.m
Is it possible for puppet to configure a set of MySQL masters and
manage circular replication, so that if additional master nodes are
required (or need to be stopped & moved) puppet can add them to the
set and bring them "up to date"? How would it cope with unresponsive
nodes; could puppet reconfig
Should probably mention:
Master is a CentOS 5.2 box running puppet 0.25.4, not running inside
EC2.
Client is a CentOS 5.4 box also running puppet 0.25.4, EC2 instance.
Puppet has been installed from yum on both machines, and both are
"clean".
--
You received this message because you are subscri
How can I pre-sign a server which doesn't yet have a domain pointing
to it?
I'm trying to get an EC2 "base image" together which is pre-signed
with our master, so I can spin-up as many instances as required. These
instances which will all share the same characteristics and files
(they're basically
I'm unable to get a response from the puppetmaster I'm testing with.
`netstat -apn` shows puppetmaster/ruby listening on port 8140, but
telnet connections are refused both from a different location and from
the commandline on the master server.
I've restarted a number of times but I'm still getti
So, am I correct in thinking then that the following workflow *can't*
be done with puppet?
1) The EC2 instance starts up, and the puppet client on the instance
connects to the puppet master.
2) The puppet client receives the EC2 authentication credentials (env
vars, certs, etc) from the master.
3)
On Apr 22, 12:04 pm, Ken wrote:
> > I personally prefer to set-up the instances externally with some other tool,
> > saves having AWS credentials on the EC2 instance.
>
> I agree. Its a concern that each box will have so much control over
> not only themselves but other instances that the key has
On Apr 22, 9:26 am, Matt wrote:
> I personally prefer to set-up the instances externally with some other tool,
> saves having AWS credentials on the EC2 instance.
So there's no way for the puppet config on the master to have the AWS
credentials and pass them down to the instance/client?
--
You
On Apr 21, 6:06 pm, Ken wrote:
> > My main problem is defining in puppet the name of the EBS volume to
> > attach, and having the puppet client on the EC2 instance actually
> > *attach* the volume after it has "spun-up".
>
> Is this because you want to be able to convert the EBS id to a /dev/
> sd
Thanks for the reply. I think the mounting part should be straight
forward.
My main problem is defining in puppet the name of the EBS volume to
attach, and having the puppet client on the EC2 instance actually
*attach* the volume after it has "spun-up".
On Apr 21, 1:07 pm, Ken wrote:
> > Is it p
Is it possible, using puppet, to configure an EC2 instance so that
when it boots it attaches & mounts an EBS volume? If so, what steps
would one take to achieve this?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send em
We use Nginx rather than apache due to a number of useful modules,
however these modules need to be compiled in and therefore we're
unable to use a package manager for installation.
Would it be possible with puppet to grab specific versions of the
various source files, compile them, and then confi
16 matches
Mail list logo
