3

Vagrant / puppet workflow

view full story
linux-howto

http://serverfault.com – I'm new to puppet and vagrant, but I'm developing my own Puppet manifests intended to set up a vagrant box. That is, the puppet manifest is in my Vagrant directory on the host machine, and vagrant is invoking puppet -- there is no puppet server. The thing is, my workflow is: while(not working as desired) { vagrant destroy amend manifest vagrant up } ... and this means quite a lot of waiting around. What's a better way to work? (HowTos)

u85500's picture
Submitted by u85500 on 07/03/2012 – Made popular on 07/03/2012

Stories similar to Vagrant / puppet workflow

This is a follow on to my previous question Vagrant Getting Started gives getaddrinfo: Temporary failure in name resolution.

I am running a fresh install of Lint Mint Nadia (14). I am following the instructions on Vagrant: Getting Started but have gotten stuck on the Provisioning.

Cannot use puppet on mac osx 10.8, i can find it in /usr/bin/lib but display that when i launch it :

/usr/bin/puppet:3:in `require': no such file to load -- puppet/util/command_line (LoadError) from /usr/bin/puppet:3

Any idea ?

Edit : I want to use puppet in Vagrant VM to do provisioning is it the good way ?

I have set up vagrant-dns but it's a shame I can't use the names from within my Vagrant VMs. (vagrant-dns sets up a nameserver on port 5300 on the host machine)

I found the resolver cookbook and it occurred to me I could maybe use that with Vagrant's port forwarding to make the vagrant-dns nameserver accessible from with the VM.

Local Vagrant machine installed at ip address 10.0.0.23 and hostname lamp-vm. Using vagrant ssh I can connect just fine and do everything I need.

This creates an ERROR - ssh vagrant@lamp-vm -v -v and I get

debug1: connect to address 10.0.0.23 port 22: Connection timed out ssh: connect to host lamp-vm port 22: Connection timed out

My etc/hosts file contains 10.0.0.23 lamp-vm.

Routing a host to Vagrant 14 weeks 1 day ago

Vagrant

I currently have a set up on my development computer that uses apache and the hosts file to point to different folders. I's worked great but I've just discovered vagrant.

I am trying to create a simple LAMP through Vagrant that can support multiple websites stored in /var/www. That can be done with vhosts.

Each project should end in .dev

Cant stand the idea creating each build that supports one project with a database each.

I cant make head or tails with Puppet or Chef.

I am having trouble getting NFS setup on with vagrant:

On my local machine I have installed NFS:

apt-get install nfs-common nfs-kernel-server

And in my Vagrantfile set it to be used:

config.vm.share_folder("v-root", "/vagrant", ".", :nfs => true)

On vagrant up I get:

exportfs: /home/<user>/path/to/dir does not support NFS export

Mounting NFS shared folders failed.

I am installing Vagrant manually with the deb.

I did sudo dpkg -i vagrant.....deb and I found it's in /opt/. Basically it doesn't add to the bash profile like apt-get does. Is that supposed to happen with dpkg?

Thanks

I'm following a tutorial to set up vagrant (a tool to build and configure portable virtual machine images), and it seems that vagrant documentation suggests using IPv4 address 33.33.33.10 to configure a new box.

That is a publicly routed IP adress, so I'm a bit confused why using this address is suggested. Since I don't own this network, I should not use an address from the 33.33.33.10/8 range.