similar to: Vagrant Puppet Provision VM

I am trying to use the same hiera hash to create the mount point and mounts. (Would be nice if mount could create the mount points using 3.1.1) My plan was to define create_mount_points and use create_resources with the same hash, and just though away what I dont use.... maybe there is a better means? Here is the mount class: class fstab::mounts ( $config = undef ) { $defaults = {

I have download recent version puppet.3.3.0.msi from PuppetLab and trying to install it on Windows 7. The MSI package throws out the following error message, This also happen on Puppet enterprise MSI package. So I wonder if anybody encounter this problem, and what''s the solution for it? Thanks, Chengkai -- You received this message because you are subscribed to the Google

Hello All, I''m wondering what is the canonical way of associating "specific" versions of a module to a node? Is there a way of doing this in puppet? Let me explain a "Use Case" of what I''m trying to accomplish: Say we have created a puppet model called apache to manage and configure apache webserver. We have the apache module under version control and

Hello, I''m running Puppet agent stand-alone on Windows. I got data-in-modules working. However, no matter what I put into the module hiera.yaml, I can only override the defaults from common.yaml by osfamily (and not, e.g., by environment). In the setup below the following command outputs: >puppet apply --binder -e "notice lookup (''my_key'')"

Hi there, I''m running into an problem which I can resolve. It is bugging me for couple of days now. Goal: CentOS 6.4 freshly installed incl puppet 3.2.3 and I want to install puppet master, puppetdb, mod_passenger & apache with "puppet apply". So when this is complete, I should have an puppet master server running so I can create new hosts etc. So this is the command

Hi all, I''m trying to find a nice way to model different stages (like: live, test, dev) of puppet modules. Initially I thought of different branches inside one (Git) repository... - either being checked out on one puppetmaster into different directories being used as different puppet environments - or being checked out on different puppetmasters but then colleagues of mine

So something doesn''t look right for me when running puppet apply -e ''include ...'' for looking heria via facter fact. I have hiera configure as this, :backends: - yaml :hierarchy: - common - ''%{env_name}'' :yaml: :datadir: /var/lib/hiera/data and, a file envXX.yaml store in the datadir, and I can run *hiera xyz

I''m running Puppet v2.7.14. I have a puppet master server with Hiera and it works great. I also want to be able to apply my manifests locally on a node. I have installed Hiera on my node and I can verify using the Hiera command line application that values can be looked up: user@tag5-4-qa-sjc:~$ hiera corp_puppet_server region=northamerica datacenter=sjc environment=qa --debug DEBUG:

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

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, 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

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?

Hi Guys, I have a few questions about 3.6 directory environments, which we're looking to adopt. Currently the most pressing surrounds the integration of r10k and hiera… I believe I want to store hieradata inside the r10k repos, so that each r10k repo (I'm planning on using these to segregate different internal product stacks so that product owners can put sensitive data in their own

Hi all, Apologies if this has been dealt with before, but I haven''t managed to find an answer yet. I have a working "dynamic environments" setup: * A gitolite repository (on a dedicated host) with multiple branches - one for each environment. * I use r10k ro deploy the environments on the master to $confdir/environments/$::environment. This all works *really* well, but I

Hi guys: I'd like to "scriptify" my virtual machine manager deployment. In particular id like to 1) Configure a 3 node cluster from an ISO 2) Assign static IPs at the vm level, and have those cascade into /etc/hosts 3) Add storage to each machine in the cluster . 4) Set the memory/CPU# for each machine. Is there a way i can automate this task using VMM, or maybe, using VMM in

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7/x86_64 and for the first time for CentOS Linux 6/x86_64; We are providing box's for Livbirt provider and the Virtual Box provider. ref: https://atlas.hashicorp.com/centos/boxes/6 https://atlas.hashicorp.com/centos/boxes/7 Release Notes for these images are published at :

-----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 :

-----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:

Vagrant and packer look like the could be useful to developers, especially when testing, as they make it relatively painless to 'reinstall' a machine to a (mostly) known state. I find that, no matter how hard I try, there always seem to be a few keystrokes that don't make it into the changelog, and recreating from scratch is how I find them. Thanks for pointing them out. I would