Today we are releasing Chef Client 11.10.0. This release contains some bug fixes and lots of contributions from our awesome community. Check out our release notes for the highlights of this release.
This release's MVP is Nikhil Benesch with his fix for CHEF-4725 . Nikhil has resolved the issue of output buffering while running with Vagrant by diving into the internals of logging in Chef. Thanks for the awesome contribution Nikhil.
…Flapjack manifest that sets up the Vagrant box.module and
Examining the Puppet module will give you a good starting point for rolling outinto your monitoring environment.
Where to next?
We're gearing up to release Flapjack 1.0.
…built my test environment on both local https://github.com/jayjanssen/pxc_testing/tree/5_6_segments (check the run_segments.sh script as well as the and documentation for the submodule).and in using an open source Vagrant environment you can find here:
We've also released Percona Xtradb Cluster 5.6 with Galera 3.0 RC1 , the above Vagrant environment should pull the latest 5.6 build in automatically.
The post Automatic replication …
To increase the default Vagrant box memory with the VirtualBox provider there are VirtualBox specific configuration options . We are currently using the following: config.vm.provider "virtualbox" do |vb| vb.customize ["modifyvm", :id, "--memory", "1024"] end
The latest documentation also lists the following shortcut formemory configuration: config.vm.provider "virtualbox" do |v| v.memory = 1024 end
…called instances. By default your instances will be converged with Chef Solo and run in Vagrant virtual machines.
Get a listing of your instances with: $ kitchen list
Run Chef on an instance, in this case default-ubuntu-1204 , with: $ kitchen converge default-ubuntu-1204
Destroy all instances with: $ kitchen destroy
You can clone a Chef cookbook project that contains Test Kitchen support and run through all the instances in serial by running: $ kitchen test
There is help …
for Vagrant and will yield plenty of information and tutorials.
Today, we are releasing Docker-friendly Vagrant boxes based on . Docker requires at least kernel 3.8, but all the Ubuntu 12.04 Vagrant boxes that we've encountered so far come with kernel 3.2 or 3.5, so that installing Docker on them requires a reboot. This makes provisioning a to be significantly more painful than it should be.
The Vagrant boxes that we're releasing …
add warden as shared folder in Vagrant file
edit Vagrant file and add this line: config.vm.synced_folder "warden", "/warden"
then login into the vm with ssh and install all required gems: vagrant ssh cd /warden sudo gem install bundler sudo bundle
edit config/linux.yml and change the container_rootfs_path,
if you don't change it the setup will be lost after you reboot the vm because it is pointed to /tmp by default.
I've created a new dir in /tmp-warden …
An Introduction to Vagrant for Developers
On Distributing Command Line : Why I from Ruby to Go
dotRB: The Largest Ruby Conference in (October 18, Paris)
Following on from a successful ' dotJS'event comes dotRB. Announced speakers so far include , , and .
You're free to modify the Vagrant file to add or remove platforms.
Lets say you want to build a scout package for Ubuntu 10.04:
$ vagrant up ubuntu-10.04
This creates a Debian package, placing it in:
I've put this package on Dropbox, so you could install it on your Ubuntu 10 server: $ wget https://dl.dropboxusercontent.com/u/468982/scout_0.0.0%2B20130617203100-1.ubuntu.10.04_amd64.deb $ sudo dpkg -i scout_0.0.0+20130617203100-1.ubuntu.10.04_amd64.deb …
It's really simple to get Vagrant to install all of your cookbooks while it provisions the VM, you'll just need to point your provision settings within your Vagrantfile to the location of both cookbook directories. Something like the Vagrantfile below copies all of your libarian-chef managed cookbooks as well as your custom cookbooks over to the VM for provisioning. No need to install a plugin or anything additional.
Vagrant::Config.run do |config| config.vm.box = "precise64" …