similar to: Reusable Puppet config for Vagrant

I've been designing the infrastructure for a new team using CentOS 6 and Puppet. I'm still learning Puppet, but thought I had things pretty well under control. After this week, I'm beginning to wonder? :-) In the last week I've had versions of three packages disappear from the yum repositories I'm using, both EPEL and the standard ones from a base CentOS 6.3 install. Since

Good Afternoon All, I''m just pondering - I think that my expectations of the forge are not 100% aligned, or I''m still rubbish with puppet! I imagine the forge to be used in the following scenario/way I''m in a situation where I need to provision package X in a particular way. I fire up my terminal: $ puppet module search packageX Searching https://forge.puppetlabs.com

I''m doing some testing with the puppetlabs/haproxy module on a vagrant box with puppet 3 set up. The module we use requires exported resources to be enabled in order to specify haproxy backends, but I don''t have it configured in puppet. I have our puppet repo checked out to the VM and am using puppet apply, pointed at the specific module path we use for development, to

I'm trying to set up cross-subnet browsing using Samba on a Linux box and a Sparc UltraEnterprise with Win95 and NT Workstation clients. I'm using the Sparc as the domain master and also as the WINS server on the 108 subnet. The Linux box is the local master on the 46 subnet. Both are running Samba 1.9.17alpha4. I can see the conversation between the two samba servers and the browse

Hello I''d love a bit of advice in terms of how I should best go about this. I am creating a bunch of vhosts, their definitions are stored in json (I''m using heira) that json file will be generated from data held on another server. I''m just using the puppetlabs apache module and create_resources to then generate all the vhosts and their directories etc. I''m

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 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 │ └──

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

Greetings, I''m trying to add ppa:nginx/stable repo for Ubuntu 12.04.1 LTS. Server: puppetmaster-common 3.0.1-1puppetlabs1 Agent: puppet 2.7.11 And when I try to apply manifest - getting: puppet agent -t info: Caching catalog for wproxy71.tpnt.net err: Failed to apply catalog: Could not find dependency File[/etc/apt/sources.list.d] for

This may be a dumb question, but here goes So I''m running on Puppet 3.1.1 on RHEL5, and i''ve been using Hiera since 2.5/2.6 ish and it''s been great!! I was reading up on Automatic Parameter Lookups and would love to use it for my modules. But I can''t seem to ever get Hiera/Puppet to load the value i''ve set in my yaml files. I feel like I must be

Hello, I would like to find a few to use files available in a module for the execution of a particular resource, without having to stage the file explicitly onto the client and possibly having to clean it up afterwards. (This could also apply to content coming from templates.) The use-cases I have in mind are: running a SQL file (to set up some content in a database), extracting an archive

puppet agent --verbose shows a verbose output of the changes done by puppet, such as: notice: /Stage[main]/Logstash::Config/Logstash::Configdir[agent]/File[/etc/logstash/agent/config]/owner: owner changed ''root'' to ''logstash'' notice: /Stage[main]/Varnish/Service[varnish]/ensure: ensure changed ''stopped'' to ''running''

Hi, I have a fresh CentOS 5.8 Vagrant VM that I''m using to emulate a customer''s server. During the first Puppet run, it takes 13 minutes and 48 seconds to sync the Puppet Labs stdlib module. On a similar Ubuntu 12.04.1 Vagrant VM, Puppet starts up, and almost instantly goes from plugin sync to facter load. Is this load time for stdlib on a RHEL variant normal?

So there''s this: http://docs.puppetlabs.com/hiera/1/custom_backends.html Is there a more thorough tutorial? That one''s a little … light. :-) -- Brian Lalor blalor@bravo5.org -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

I''ve seen mention of this error in several places, with different causes. So before I posted here, I attempted to resolve this on my own. I corrected the change from puppet:///files to puppet:/// in my manifests *.pp files. No changes were made to the auth.conf file, and I did note in the ChangeLog that: Auth.conf differentiates between names and IPs – There’s a new allow_ip

We are pleased to announce the immediate availability for CentOS Linux 7 x86_64 images for Vagrant. This image represents a minimal install set, that lines up with the user expectation for our Cloud Images, our ISO based Minimal installer and the default minimal install profile from the in-distro install options. Images are released for the VirtualBox and LibVirt providers ( more providers

I am pleased to announce the immediate availability of Vagrant 1.7.4 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install sclo-vagrant1 $ scl enable

We are in the process of evaluating our puppet related test and release process and interested in knowing what other folks are doing. We are in a position that is not ideal but is not unique from what I can tell. Our current testing process is basically the responsibility of each person making a change. Small changes are committed and pushed to dev/qa/prod in one swoop with the committer spot

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7 and CentOS Linux 6 for x86_64. These are available, as in the past, for the Libvirt and the VirtualBox providers in Vagrant. We have also enabled the vmware providers, for anyone using Vmware's products for backing Vagrant on Linux, MacOS or Windows. ref:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7 and CentOS Linux 6 for x86_64. These are available for the Libvirt and the VirtualBox providers in Vagrant. ref: https://atlas.hashicorp.com/centos/boxes/6 https://atlas.hashicorp.com/centos/boxes/7 Release Notes for these images are published at :