similar to: Puppet & EC2: Attach an EBS volume at boot?

I''m trying to provide some "disaster-proofing" on Amazon EC2 by using a ZFS-based EBS volume for primary data storage with Amazon S3-backed snapshots. My aim is to ensure that, should the instance terminate, a new instance can spin-up, attach the EBS volume and auto-/re-configure the zpool. I''ve created an OpenSolaris 2009.06 x86_64 image with the zpool structure

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 dupes), and will all sit behind a load-balancer, so

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.mydomain.com"? If so, how/where can this be configured? -- You received

Hello Looking to build CentOS based micro EC2 instance bootable from Amazon EBS. Want that the image be minimal, so that I can add only the rpms I want. Despite looking could not find a way to import a CentOS image from scratch or an existing minimal CentOS image that is bootable from EBS. My server must must persist, as I cannot handle issues with a dynamic server, so I want to use a server

Hi, I''m using Amazon EC2 and I''m planning to use puppet to deploy automatically my instances, however, I have an issue I can''t rely think through. As most people advised, I used a DNS server (bind to be precise) so that my instances can register to it but also ask this DNS Server the IP of the puppetmaster. However, as this DNS server is also running on Amazon EC2

Hello... I wanted to be able to startup an EC2 instance with one command and have a fully functioning server without having to shell into each new instance and configure the bits to allow puppet to finish the configuration. Here are some notes I came up with for bootstrapping an ec2 instance with puppet using Ubuntu 10.04. I left out a lot of things about creating and running custom AIM

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 getting nothing, and AFAICT there aren''t any conflicting

I''ve seen a couple of examples of using puppet to control services where you can''t run a puppet agent on the resource. As far as I can tell they work by having puppet proxy through some external-service control mechanism, such as fog. The question is: where does the proxy run? I assume a puppet agent needs to run somewhere. Where do you put that agent, how do you configure it,

Hi. Have anyone ever managed several geographically distributed systems with Puppet? I have several almost exactly similar deployments (except the server IP''s), which management I''m looking to convert to Puppet. I have 2 options: * Have each deployment to host it''s own PuppetMaster for providing local configurations, then synchronize somehow the PuppetMasters (maybe

I am stuck with ubuntu 9.04 as puppet master server. But puppet version is old on ubuntu 9.04: puppetmaster,puppet 0.24.5-3 Would it be possible to upgrade it to the latest version, without upgrading the OS? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To

Any light someone can shed sure would be appreciated. I start with 1 cert -- the master''s, where I am running this: jblaine@ip-10-191-115-140:~$ sudo puppet cert list --all + "ip-10-191-115-140.ec2.internal" (74:8B:7B:EF:41:E6:F9:98:93:15:42:6A:4C:2F:28:CC) (alt names: "DNS:ip-10-191-115-140.ec2.internal", "DNS:puppet", "DNS:puppet.ec2.internal")

Hello, i''m new to puppet (and ruby). I have a problem when using a variable name containing a variable name and containing a reserved variable name : I have a class : class kernel-Linux-binary { $test = $operatingsystem ? { Fedora => "/usr/bin/test", default => undef } } and i want to call "test" and replace Linux by

Greetings! I''d appreciate hearing from anybody who''s had experience with any of this. I''ve got a Rails app that currently deployed on EC2 with MySQL and am readying to move from a dev / prototype model to a full-scale production model. Right now I''ve got a single MySQL instance. I''m getting ready to move that to a master-slave setup. I''m

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 working (http://docs.puppetlabs.com/guides/configuring.html) with a little tweak

Hi, I have created an agent node from a master node using below command. puppet node_aws create --image ami-cc5af9a5 --keyname icos-client --type ti.micro Now as i am trying to install puppet on it using below command puppet node install \ --install-script=puppet- enterprise \ --installer-payload=/usr/local/puppet/puppet-2.7.0.tar.gz \ --installer-answers=/usr/local/puppet/agent.txt \

Hi all, When i try to boot an ec2 instance using: *puppet node_aws bootstrap --server myserverOnAWS.com --image ami-61ad0108 --keyname test-malcom --login ubuntu --type m1.small --keyfile test-malcom.pem -g puppets --verbose --debug --puppetagent-certname test* I get this error: *notice: Signing certificate ...* *debug: certificate_status supports formats: b64_zlib_yaml pson raw yaml; using

Hi - I read up on this subject quite a bit, and was able to find a few posts on the mailing list, even found a wiki article. Unfortunately it doesn''t quite address what I''m looking to do. From what I understand, Puppet''s client/server authentication system - using SSL - is portable. I believe that I should be able to use the same SSL certificates and keys (and even

Hi all, just installed the puppetlabs-mysql module for puppet on my Puppet server which is an Amazon Linux (based on RedHat), but I get this error when I run puppet agent --test : *err: Could not retrieve catalog from remote server: Error 400 on SERVER: Unsupported osfamily: Linux operatingsystem: Amazon, module mysql only support osfamily RedHat and Debian at

Hi there. Can somebody help me diagnose an error? On the Puppet Master node, we''ve started the Puppet Master with: ubuntu@domU-12-31-39-09-x-x:~$ sudo puppet master Then from a node where we want to apply updates, I ran: ubuntu@ip-10-72-x-x:~$ sudo puppet agent --server domU-12-31-39-x-x- x.compute-1.internal --waitforcert 60 --test info: Creating a new SSL key for

We are happy to announce the first public release candidate of our Puppet Cloud Provisioner. This release is available for download at our Module Forge: http://forge.puppetlabs.com/puppetlabs/cloud_provisioner<http://downloads.puppetlabs.com/dashboard/> Extensive documentation can be found at: http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html Please report feedback via the