Berkshelf 1.3.1 with Vagrant 1.1 support


#1

Hey Chefs,

Today we released Berkshelf 1.3.1 which includes Vagrant 1.1 support. Vagrant is no longer distributed as a Rubygem so there are some additional things to consider when upgrading.
Vagrant is no longer installed with ruby gems. Grab a copy of the latest version’s installer from their download page (http://downloads.vagrantup.com/).
Berkshelf core no longer ships with the Berkshelf plugin. There is a new gem (https://github.com/RiotGames/berkshelf-vagrant) which contains the berkshelf-vagrant plugin.
Install this plugin with the command vagrant plugin install berkshelf-vagrant once you have Vagrant installed.

You no longer require ‘berkshelf/vagrant’ at the top of your Vagrantfile to include the Berkshelf plugin; it’s just automatically loaded now.
The Vagrantfile format generated by Berkshelf 1.0-1.2 is no longer, valid. You can generate a new Vagrantfile by renaming your cookbook’s current Vagrantfile and re-running berks init. Diff the two files and make the appropriate changes; there shouldn’t be too many.

Berkshelf 1.3.1 and the Berkshelf-Vagrant plugin do not support Vagrant 1.0.x. See the CHANGELOG (https://github.com/RiotGames/berkshelf/blob/master/CHANGELOG.md) for extra details on this release.

And please, open a ticket with us if you have an issue!


Jamie Winsor
@resetexistence


#2

woot

On Wed, Mar 20, 2013 at 4:46 PM, Jamie Winsor jamie@vialstudios.com wrote:

Hey Chefs,

Today we released Berkshelf 1.3.1 which includes Vagrant 1.1 support.
Vagrant is no longer distributed as a Rubygem so there are some additional
things to consider when upgrading.

Vagrant is no longer installed with ruby gems. Grab a copy of the latest
version’s installer from their download page.
Berkshelf core no longer ships with the Berkshelf plugin. There is a new gem
which contains the berkshelf-vagrant plugin.

Install this plugin with the command vagrant plugin install berkshelf-vagrant once you have Vagrant installed.

You no longer require ‘berkshelf/vagrant’ at the top of your Vagrantfile to
include the Berkshelf plugin; it’s just automatically loaded now.
The Vagrantfile format generated by Berkshelf 1.0-1.2 is no longer, valid.
You can generate a new Vagrantfile by renaming your cookbook’s current
Vagrantfile and re-running berks init. Diff the two files and make the
appropriate changes; there shouldn’t be too many.

Berkshelf 1.3.1 and the Berkshelf-Vagrant plugin do not support Vagrant
1.0.x. See the CHANGELOG for extra details on this release.

And please, open a ticket with us if you have an issue!


Jamie Winsor
@resetexistence
https://github.com/reset


#3

Jamie,

This is awesome, thanks for all the hard work  !

-John

On Wed, Mar 20, 2013 at 4:46 PM, Jamie Winsor jamie@vialstudios.com wrote:

Hey Chefs,

Today we released Berkshelf 1.3.1 which includes Vagrant 1.1
support. Vagrant is no longer distributed as a Rubygem so there are some
additional things to consider when upgrading.

  • Vagrant is no longer installed with ruby gems. Grab a copy of the
    latest version’s installer from their download pagehttp://downloads.vagrantup.com/
    .
  • Berkshelf core no longer ships with the Berkshelf plugin. There is a new
    gem https://github.com/RiotGames/berkshelf-vagrant which contains
    the berkshelf-vagrant plugin.
    • Install this plugin with the command vagrant plugin install berkshelf-vagrant once you have Vagrant installed.
  • You no longer require ‘berkshelf/vagrant’ at the top of your
    Vagrantfile to include the Berkshelf plugin; it’s just automatically loaded
    now.
  • The Vagrantfile format generated by Berkshelf 1.0-1.2 is no longer,
    valid. You can generate a new Vagrantfile by renaming your cookbook’s
    current Vagrantfile and re-running berks init. Diff the two files and
    make the appropriate changes; there shouldn’t be too many.

Berkshelf 1.3.1 and the Berkshelf-Vagrant plugin do not support Vagrant
1.0.x. See the CHANGELOGhttps://github.com/RiotGames/berkshelf/blob/master/CHANGELOG.mdfor extra details on this release.

And please, open a ticket with us if you have an issue!


Jamie Winsor
@resetexistence
https://github.com/reset


#4

Not sure if this is the correct forum, but just updated to all this
described and am having problems with running a chef-solo provision run
with berkshelf. Berkshelf correctly downloads everything in my
Berksfile, however when I run vagrant provision, with custom cookbook
that berkshelf retrieves from my git repo, the chef-solo run in the vm
cannot find the cookbooks. On inspection, there indeed are no cookbooks
in the tmp area on the vm.

Am I missing something? Is the provision process supposed to expose a
runtime shared folder of the berks cookbook cache dir?

On 2013-03-21 10:28 AM, John Dyer wrote:

Jamie,

This is awesome, thanks for all the hard work  !

-John

On Wed, Mar 20, 2013 at 4:46 PM, Jamie Winsor <jamie@vialstudios.com
mailto:jamie@vialstudios.com> wrote:

Hey Chefs,

Today we released Berkshelf 1.3.1 which includes Vagrant 1.1
support. Vagrant is no longer distributed as a Rubygem so there
are some additional things to consider when upgrading.

  * Vagrant is no longer installed with ruby gems. Grab a copy of
    the latest version's installer from their download page
    <http://downloads.vagrantup.com/>.
  * Berkshelf core no longer ships with the Berkshelf plugin.
    There is a new gem
    <https://github.com/RiotGames/berkshelf-vagrant> which
    contains the berkshelf-vagrant plugin.
      o Install this plugin with the command `vagrant plugin
        install berkshelf-vagrant` once you have Vagrant installed.
  * You no longer require 'berkshelf/vagrant' at the top of your
    Vagrantfile to include the Berkshelf plugin; it's just
    automatically loaded now.
  * The Vagrantfile format generated by Berkshelf 1.0-1.2 is no
    longer, valid. You can generate a new Vagrantfile by renaming
    your cookbook's current Vagrantfile and re-running `berks
    init`. Diff the two files and make the appropriate changes;
    there shouldn't be too many.

Berkshelf 1.3.1 and the Berkshelf-Vagrant plugin do not support
Vagrant 1.0.x. See the CHANGELOG
<https://github.com/RiotGames/berkshelf/blob/master/CHANGELOG.md>
for extra details on this release.

And please, open a ticket with us if you have an issue!

-- 
Jamie Winsor
@resetexistence
https://github.com/reset