Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Michael K
@Yserz
ohai, I observed that vagrant-cachier is not caching chef files...do i have to set up special commands to activate the chef-caching?
something like config.omnibus.cache_packages = true in Vagrantfile or cache_type 'BasicFile' in knife.rb?
Michael K
@Yserz
one example of a package which is not cached is the chef-server from the chef-server cookbook on centos 6.6. Surprisingly the packge is present in the cache of the host machine (.vagrant.d) but is never taken in the vm :/
Michael K
@Yserz
Vagrant 1.7.1, vagrant-cachier (1.1.0), vagrant-omnibus (1.4.1) (installing chef 12.0.0)
Fabio Rehm
@fgrehm
Sorry, I haven't used omnibus in a looong time =/
Michael K
@Yserz
rly? no more chef or what's ur workflow?
Fabio Rehm
@fgrehm
started using ansible not long ago, but I havent been messing up with servers for a while now so I dont need for a proper provisioning tool these days. http://fgrehm.viewdocs.io/devstep is what I've been using on my daily work (which borrows lots of ideas from vagrant-cachier's caching approach)
Michael K
@Yserz
just started reading...but looks like docker is behind that, right? :)
confirmed ;D
Fabio Rehm
@fgrehm
Right now: yes. For the future: its just a set of heroku buildpacks, so in theory it could be easily applied to some vagrant provisioner plugin
https://gitter.im/fgrehm/devstep if someone is interested on discussing that :)
Michael K
@Yserz
Alright, currently that's not my goal I want to reach but if I need something like this I'll remember :)
Also I took a deeper look to Ansible (I heard of it before). It looks easier but I'm not sure if this is the case with really complex "Roles" especially for roles for multiple os
the agentless-thing is really neat ;)
Michael K
@Yserz
okay...I found out that /var/chef/cache is simply not linked with the cachier-cache
Michael K
@Yserz
==> vm-chef-server: Chef 12.0.0 Omnibus package is already installed.
==> vm-chef-server: Configuring cache buckets...
==> vm-chef-server: Running provisioner: chef_solo...
==> vm-chef-server: Detected Chef (latest) is already installed
^C==> vm-chef-server: Waiting for cleanup before exiting...
Vagrant exited after cleanup due to external interrupt.
$ vagrant ssh
Last login: Thu Dec 11 02:22:17 2014 from 10.0.2.2
[vagrant@vm-chef-server ~]$ cd /var
[vagrant@vm-chef-server var]$ ls
cache crash db empty games lib local lock log mail nis opt preserve run spool tmp yp
the folder isnt present before the chef run
I guess i nailed it :D
Michael K
@Yserz
okay...got it
@fgrehm cassianoleal/vagrant-butcher@81cc73c
vagrant changed from the attribute name to type
thus the chef cache path is never found correctly because no chef-provisioner is found
time for a open issue :)
Michael K
@Yserz
fgrehm/vagrant-cachier#133
David Boucha
@UtahDave
I'm getting an nfs locking error when using vagrant-cachier with lxc containers. seems to be working fine with virtualbox vms. Is anyone else running into this?
Darragh Bailey
@electrofelix
Wondering if there is a reason that cachier runs InstallBuckets after every provisioner? At first glance it seems inefficient and I was thinking of submitting a change to reduce it to only running the first time, but is it enabling some behaviour I'm not considering?