Ohai!
Are the bento baseboxes on S3 (as listed on
https://github.com/opscode/bento) updated regularly, e.g. when new
Chef versions come out?
Just wanted to know whether I can expect to always get the same box
from the S3 Url or whether the contents of the box might change over
time.
Cheers, Torben
Ohai!
On Oct 1, 2012, at 1:22 AM, Torben Knerr ukio@gmx.de wrote:
Are the bento baseboxes on S3 (as listed on
GitHub - chef/bento: Packer templates for building minimal Vagrant baseboxes for multiple platforms) updated regularly, e.g. when new
Chef versions come out?
Just wanted to know whether I can expect to always get the same box
from the S3 Url or whether the contents of the box might change over
time.
We didn't update to 10.14.0 because of regressions that were fixed in 10.14.2 and 10.14.4. There's currently an issue in the omnibus packaging of 10.14.4-1, so we're waiting to update the bento-built boxes until that is resolved (should be this week).
On Friday, the following boxes were updated with 10.12.0:
opscode-centos-5.8-i386.box
opscode-centos-5.8.box
opscode-centos-6.3-i386.box
opscode-centos-6.3.box
opscode-ubuntu-10.04-i386.box
opscode-ubuntu-10.04.box
opscode-ubuntu-12.04-i386.box
opscode-ubuntu-12.04.box
As soon as the omnibus packaging is fixed for 10.14.4, we'll update with that.
We'll also post more widely when these updates are done so folks are aware. As it is now, if you already have a box installed in your vagrant environment (~/.vagrant.d/boxes), it won't be updated until you specifically tell it to, usually by removing the existing box and letting Vagrant get the new one.
--
Opscode, Inc
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman
On Mon, Oct 1, 2012 at 7:42 PM, Joshua Timberman joshua@opscode.com wrote:
Ohai!
On Oct 1, 2012, at 1:22 AM, Torben Knerr ukio@gmx.de wrote:
Are the bento baseboxes on S3 (as listed on
GitHub - chef/bento: Packer templates for building minimal Vagrant baseboxes for multiple platforms) updated regularly, e.g. when new
Chef versions come out?
Just wanted to know whether I can expect to always get the same box
from the S3 Url or whether the contents of the box might change over
time.
We didn't update to 10.14.0 because of regressions that were fixed in 10.14.2 and 10.14.4. There's currently an issue in the omnibus packaging of 10.14.4-1, so we're waiting to update the bento-built boxes until that is resolved (should be this week).
On Friday, the following boxes were updated with 10.12.0:
opscode-centos-5.8-i386.box
opscode-centos-5.8.box
opscode-centos-6.3-i386.box
opscode-centos-6.3.box
opscode-ubuntu-10.04-i386.box
opscode-ubuntu-10.04.box
opscode-ubuntu-12.04-i386.box
opscode-ubuntu-12.04.box
As soon as the omnibus packaging is fixed for 10.14.4, we'll update with that.
We'll also post more widely when these updates are done so folks are aware. As it is now, if you already have a box installed in your vagrant environment (~/.vagrant.d/boxes), it won't be updated until you specifically tell it to, usually by removing the existing box and letting Vagrant get the new one.
--
Opscode, Inc
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman
Thanks Joshau for the detailed answer.
Would it make sense to encode the chef version into either the S3 URL
or the box name?
For example:
https://opscode-vm.s3.amazonaws.com/vagrant/boxes/10.12.0/opscode-ubuntu-12.04-i386.box
https://opscode-vm.s3.amazonaws.com/vagrant/boxes/10.14.4/opscode-ubuntu-12.04-i386.box
https://opscode-vm.s3.amazonaws.com/vagrant/boxes/latest/opscode-ubuntu-12.04-i386.box
Or like this:
https://opscode-vm.s3.amazonaws.com/vagrant/boxes/opscode-ubuntu-12.04-i386-chef-10.12.0.box
https://opscode-vm.s3.amazonaws.com/vagrant/boxes/opscode-ubuntu-12.04-i386-chef-10.14.4.box
https://opscode-vm.s3.amazonaws.com/vagrant/boxes/opscode-ubuntu-12.04-i386-chef-latest.box
You would get the basebox with the latest chef version using the
"latest" link, but could still access "stable" versions of the
baseboxes with the chef version encoded in the link.
If you think this makes sense I would create a ticket for it.