similar to: Puppet is very slow when running in AWS

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

Hi, I''m using puppet on EC2 to setup my VMs with the following configuration: # puppetd --version 0.25.5 # uname -a Linux hostname.domain 2.6.16-xenU #1 SMP Mon May 28 03:41:49 SAST 2007 i686 i686 i386 GNU/Linux But I keep facing some timeout from puppetd: warning: peer certificate won''t be verified in this SSL session Exiting; failed to retrieve certificate and waitforcert

Hi, I''m building a staging environement and I would like it to be able to redeploy automatically, after each commit - or every hour, some applications. Those applications are right now deployed and set up by puppet. I wonder if I should use puppet to redeploy those applications after each commit, and if I should how trigger, on the puppet, a full redeployement of the application ? --

I''ve been going round in circles a little bit in the last few days trying to figure out how to get a 64-bit CentOS-based puppetmaster that can be managed/provisioned via puppet also - so I''d like ruby, passenger, rails etc coming from RPMs and yum. As far as I can see, the three choices are: 1) Puppetlabs prosvc repo, which specifically says it can go away at any time 2)

Hi, I''ve just finished James Turnbull book "Pulling Strings With Puppet" - which definitely an excellent introduction to Puppet, and I was wondering - as the book is a couple years old, what was the status of the all mongrel/webrick situation ? I guess it''s still recommended to use Mongrel rather than Webrick for puppetmaster, at least for 0.25.5 (which I''m

We have bunch or property files(key/value pairs) used in different modules in our java web applicaiton. our applicaiton is also distributed, part of that runs on a head office and some of the parts run at the branch. All the branches run a local server for day to day activities. We are looking to automate these files when moving to different environments like deve, test, prod. So that we can

Hi, I''ve been trying to pass the http_proxy_host option to puppet but it''s not taking. I have tried the following: sudo puppet apply --debug --verbose --http_proxy_host http://user:pass@fqdn.com.au --modulepath ''/tmp/vagrant-puppet/modules-0'' /tmp/vagrant-puppet/manifests/default.pp sudo puppet apply --debug --verbose

Hi gluster ! For those of you who need to spin up virtual gluster clusters for development and testing: Just finished creating a vagrantized, fully automated, totally rebuildable and teardownable two node fedora 19 gluster setup and shared it on the forge! It uses fedora19 but since its all vagrant powered, you dont need to grab or download a distro or iso or anything, just clone the git repo,

Trying to get SSH agent forwarding working for a popular open source configuration management system called Ansible. I?ve had some unexpected behaviour, the only cause of which I can find is how I express the command line arguments. http://stackoverflow.com/questions/20952689/vagrant-ssh-agent-forwarding-how-is-it-working?noredirect=1#comment31511341_20952689 In summarise: In the first

I'm using libvirt on Debian/stretch (testing) with vagrant and the vagrant-libvirt plugin. When I import a vagrant box (jessie64.box), the resulting file permssions let anyone in the "kvm" group read the img. But when I build upon that box, only root can read it: -rw------- 1 root root 20198785024 Sep 19 18:19 buildserver_default.img -rwxr--r-- 1 libvirt-qemu kvm

Hi, I try install python-psycopg2 with other packages, when run apt-get -y update returns the errors: err: /Stage[main]/Etc/Package[build-essential]/ensure: change from purged to present failed: Could not set ''present on ensure: Read-only file system - /tmp/puppet20120216-1063-18q7lsz-0 at /tmp/vagrant-puppet/manifests/vagrant.pp:15 err:

Hi, I launched an AWS instance `t2.medium` (use CentOS 7 image "ami-7abd0209", product code: https://aws.amazon.com/marketplace/pp/B00O7WM7QW), which is supposed to have 4GB Memory in total, but turn out it is only "3.5GB". ``` $ free -h total used free shared buff/cache available Mem: 3.5G 441M 1.4G 16M

Hi All, I am using Vagrant to provision a box (CentOS 6.x) with puppet provisioner. The box is built by using veewee, with ruby 1.8.7 and puppet 3.2 iinstalled, and the vagrant environment layout is, . ├── Gemfile ├── Gemfile.lock ├── Rakefile ├── Vagrantfile ├── definitions │ └── centos-6.3.minimal ├── hiera │ └── data ├── iso │ ├── CentOS-6.3-x86_64-minimal.iso │ └──

I have the following in vagrantfile in WIndows system. config.vm.provision :puppet do |puppet| puppet.manifests_path = "manifests" puppet.manifest_file = "base-hadoop.pp" puppet.module_path = "modules" end when i run vagrant provision, i do see manifest and module folders are mounted and ssh into vm, I can find files in the following path

I took an hour this morning to document how I use Vagrant and Puppet together to provision development VMs as well as more production-like systems. This may be entirely elementary to folks who are more fluent with Puppet, but this is an example I thought was lacking. https://github.com/blalor/vagrant-puppet-example I welcome feedback and criticism of this setup. I''m looking to

Hi, At Vagrant Cloud there are "box" images for stream8 and stream9 [1]. At least they are supposed to be there. The download links on the detail pages, for example for stream9 20230727.1 [2] are redirected to cloud.centos.org, however they give an 404 error. Possibly the centos Vagrant Cloud page is not kept up to date with the actual box images that are now present on

Good evening, all. I just tried spinning up a CentOS instance in EC2 using ami-de5bd2ee from the AWS marketplace. I put a dummy script into the user-data field when launching the instance from the EC2 console but found it didn't work, even though the SSH key for the root user did. I pinged Karanbir on ##aws and he suggested I post here to get the conversation started. I'm currently

Here''s what I''m using: exec { "cert-fix": command => "curl http://curl.haxx.se/ca/cacert.pem -o /etc/pki/tls/certs/ca-bundle.crt", onlyif => "test -e /etc/pki/tls/certs/ca-bundle.crt", } But it keeps on failing: > [default] Running Puppet with /tmp/vagrant-puppet/manifests/acid.pp... > Parameter onlyif failed: ''test -e

On 03/26/2015 10:40 PM, Bob Hepple wrote: > Boris Epstein <borepstein at ...> writes: > a set of scripts/utilities for automatically >> starting and running headless (no X11) VM's using VirtualBox omn a CentOS 6 >> server. VNC/RDP access to the VM's would be fine. > vagrant? > > _______________________________________________ > I'm unfamiliar with

I''m using puppet through Vagrant to manage my dev VM, and as part of that I have a few database grants that I run after creating users, but when I subsequently run vagrant up or provision these grants fail (because of some changes I make to the mysql config after they have been created.) I''m using database_grant to execute the grants, but there doesn''t seem to be a