[ANN] Vagrant 1.2.0 Released

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[ANN] Vagrant 1.2.0 Released

Mitchell Hashimoto
Hello everyone,

Vagrant 1.2.0 has been released. You can upgrade by downloading the new package/installer for your operating system and overwriting the previous: http://downloads.vagrantup.com/tags/v1.2.0

IMPORTANT BACKWARDS COMPATIBILITY NOTES:

* VMware Fusion users MUST install the newly released plugin. Just `vagrant plugin install` the plugin again and verify you get version 0.5.0. This version is compatible with changes in 1.2.0.

* Windows users: Vagrant now uniformly uses the "USERPROFILE" directory for the ".vagrant.d" directory. This is the same behavior as before, except in Cygwin environments. In these environments, please either specify VAGRANT_HOME or move your "~/.vagrant.d" folder to "USERPROFILE/.vagrant.d"

There are a few major highlights in this release:

* Dramatically improved Windows support. Vagrant now works very well in cmd.exe, PowerShell, MingW/MSYS, Cygwin, and GOW environments. 

* cURL-based downloader. Box downloads are now done via cURL instead of Ruby's built-in HTTP libraries. This brings massive performance improvements since cURL manages download buffers much better. It also brings true SSL verification, FTP support, and more.

* Ansible and CFEngine provisioner support. 

* Parallelizable providers. `vagrant up` in multiple-machine environments will parallelize IF the provider supports it. VirtualBox does not support this at the moment. In time I think most providers will support this. This release lays the framework for that capability.

* Provider-specific configuration overrides, so you can change the "box" for example based on provider.

* Many many improvements and bug fixes.

While this email will coveThe details CHANGELOG can be found here: https://github.com/mitchellh/vagrant/blob/v1.2.0/CHANGELOG.md#120-april-16-2013

Best,
Mitchell

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Vagrant 1.2.0 Released

Andrew Ellis
Awesome! So happy to have my "vagrant reload" back :)

However, I'm noticing something fishy about Chef Solo... I have 11.4.0 installed and see the following when booting:

[2013-04-16T14:30:46-06:00] INFO: *** Chef 11.4.0 ***
[2013-04-16T14:30:47-06:00] INFO: Run List is []
[2013-04-16T14:30:47-06:00] INFO: Run List expands to []
[2013-04-16T14:30:47-06:00] INFO: Starting Chef Run for web1.ellis.dev.liquidcompass.net
[2013-04-16T14:30:47-06:00] INFO: Running start handlers
[2013-04-16T14:30:47-06:00] INFO: Start handlers complete.
[2013-04-16T14:30:47-06:00] INFO: Chef Run complete in 0.04119059 seconds
[2013-04-16T14:30:47-06:00] INFO: Running report handlers
[2013-04-16T14:30:47-06:00] INFO: Report handlers complete

Here is my Chef Solo block (which was working with 1.1.5):

# Chef Solo Provisioning
web1.vm.provision :chef_solo do |chef|
  # Configuration
  chef.cookbooks_path = "development/Chef"
  chef.json = {
    "vm_id"    => 1,
    "timezone" => timezone,
    "dns_key"  => dns_key
  }

  # Core Installation
  chef.add_recipe "system::before"
  chef.add_recipe "nginx"
  chef.add_recipe "mysql"

  # Project Recipes
  shared.each do|project|
    chef.add_recipe project[0]
  end

  # Post Install
  chef.add_recipe "system::after"
end

On Tuesday, April 16, 2013 12:16:33 PM UTC-6, Mitchell Hashimoto wrote:
Hello everyone,

Vagrant 1.2.0 has been released. You can upgrade by downloading the new package/installer for your operating system and overwriting the previous: http://downloads.vagrantup.com/tags/v1.2.0

IMPORTANT BACKWARDS COMPATIBILITY NOTES:

* VMware Fusion users MUST install the newly released plugin. Just `vagrant plugin install` the plugin again and verify you get version 0.5.0. This version is compatible with changes in 1.2.0.

* Windows users: Vagrant now uniformly uses the "USERPROFILE" directory for the ".vagrant.d" directory. This is the same behavior as before, except in Cygwin environments. In these environments, please either specify VAGRANT_HOME or move your "~/.vagrant.d" folder to "USERPROFILE/.vagrant.d"

There are a few major highlights in this release:

* Dramatically improved Windows support. Vagrant now works very well in cmd.exe, PowerShell, MingW/MSYS, Cygwin, and GOW environments. 

* cURL-based downloader. Box downloads are now done via cURL instead of Ruby's built-in HTTP libraries. This brings massive performance improvements since cURL manages download buffers much better. It also brings true SSL verification, FTP support, and more.

* Ansible and CFEngine provisioner support. 

* Parallelizable providers. `vagrant up` in multiple-machine environments will parallelize IF the provider supports it. VirtualBox does not support this at the moment. In time I think most providers will support this. This release lays the framework for that capability.

* Provider-specific configuration overrides, so you can change the "box" for example based on provider.

* Many many improvements and bug fixes.

While this email will coveThe details CHANGELOG can be found here: https://github.com/mitchellh/vagrant/blob/v1.2.0/CHANGELOG.md#120-april-16-2013

Best,
Mitchell

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Vagrant 1.2.0 Released

Mitchell Hashimoto
Andrew,

This was just fixed and will be part of a quick 1.2.1 bug fix release coming out tomorrow.

Best,
Mitchell


On Tue, Apr 16, 2013 at 1:41 PM, Andrew Ellis <[hidden email]> wrote:
Awesome! So happy to have my "vagrant reload" back :)

However, I'm noticing something fishy about Chef Solo... I have 11.4.0 installed and see the following when booting:

[2013-04-16T14:30:46-06:00] INFO: *** Chef 11.4.0 ***
[2013-04-16T14:30:47-06:00] INFO: Run List is []
[2013-04-16T14:30:47-06:00] INFO: Run List expands to []
[2013-04-16T14:30:47-06:00] INFO: Starting Chef Run for web1.ellis.dev.liquidcompass.net
[2013-04-16T14:30:47-06:00] INFO: Running start handlers
[2013-04-16T14:30:47-06:00] INFO: Start handlers complete.
[2013-04-16T14:30:47-06:00] INFO: Chef Run complete in 0.04119059 seconds
[2013-04-16T14:30:47-06:00] INFO: Running report handlers
[2013-04-16T14:30:47-06:00] INFO: Report handlers complete

Here is my Chef Solo block (which was working with 1.1.5):

# Chef Solo Provisioning
web1.vm.provision :chef_solo do |chef|
  # Configuration
  chef.cookbooks_path = "development/Chef"
  chef.json = {
    "vm_id"    => 1,
    "timezone" => timezone,
    "dns_key"  => dns_key
  }

  # Core Installation
  chef.add_recipe "system::before"
  chef.add_recipe "nginx"
  chef.add_recipe "mysql"

  # Project Recipes
  shared.each do|project|
    chef.add_recipe project[0]
  end

  # Post Install
  chef.add_recipe "system::after"
end

On Tuesday, April 16, 2013 12:16:33 PM UTC-6, Mitchell Hashimoto wrote:
Hello everyone,

Vagrant 1.2.0 has been released. You can upgrade by downloading the new package/installer for your operating system and overwriting the previous: http://downloads.vagrantup.com/tags/v1.2.0

IMPORTANT BACKWARDS COMPATIBILITY NOTES:

* VMware Fusion users MUST install the newly released plugin. Just `vagrant plugin install` the plugin again and verify you get version 0.5.0. This version is compatible with changes in 1.2.0.

* Windows users: Vagrant now uniformly uses the "USERPROFILE" directory for the ".vagrant.d" directory. This is the same behavior as before, except in Cygwin environments. In these environments, please either specify VAGRANT_HOME or move your "~/.vagrant.d" folder to "USERPROFILE/.vagrant.d"

There are a few major highlights in this release:

* Dramatically improved Windows support. Vagrant now works very well in cmd.exe, PowerShell, MingW/MSYS, Cygwin, and GOW environments. 

* cURL-based downloader. Box downloads are now done via cURL instead of Ruby's built-in HTTP libraries. This brings massive performance improvements since cURL manages download buffers much better. It also brings true SSL verification, FTP support, and more.

* Ansible and CFEngine provisioner support. 

* Parallelizable providers. `vagrant up` in multiple-machine environments will parallelize IF the provider supports it. VirtualBox does not support this at the moment. In time I think most providers will support this. This release lays the framework for that capability.

* Provider-specific configuration overrides, so you can change the "box" for example based on provider.

* Many many improvements and bug fixes.

While this email will coveThe details CHANGELOG can be found here: https://github.com/mitchellh/vagrant/blob/v1.2.0/CHANGELOG.md#120-april-16-2013

Best,
Mitchell

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Vagrant 1.2.0 Released

Andrew Ellis
Do you have a commit on GitHub you can link me to so I can make this change mysql temporarily?

Thanks man!

On Tuesday, April 16, 2013 2:45:19 PM UTC-6, Mitchell Hashimoto wrote:
Andrew,

This was just fixed and will be part of a quick 1.2.1 bug fix release coming out tomorrow.

Best,
Mitchell


On Tue, Apr 16, 2013 at 1:41 PM, Andrew Ellis <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="h539t5Z2q9AJ">awel...@...> wrote:
Awesome! So happy to have my "vagrant reload" back :)

However, I'm noticing something fishy about Chef Solo... I have 11.4.0 installed and see the following when booting:

[2013-04-16T14:30:46-06:00] INFO: *** Chef 11.4.0 ***
[2013-04-16T14:30:47-06:00] INFO: Run List is []
[2013-04-16T14:30:47-06:00] INFO: Run List expands to []
[2013-04-16T14:30:47-06:00] INFO: Starting Chef Run for web1.ellis.dev.liquidcompass.net
[2013-04-16T14:30:47-06:00] INFO: Running start handlers
[2013-04-16T14:30:47-06:00] INFO: Start handlers complete.
[2013-04-16T14:30:47-06:00] INFO: Chef Run complete in 0.04119059 seconds
[2013-04-16T14:30:47-06:00] INFO: Running report handlers
[2013-04-16T14:30:47-06:00] INFO: Report handlers complete

Here is my Chef Solo block (which was working with 1.1.5):

# Chef Solo Provisioning
web1.vm.provision :chef_solo do |chef|
  # Configuration
  chef.cookbooks_path = "development/Chef"
  chef.json = {
    "vm_id"    => 1,
    "timezone" => timezone,
    "dns_key"  => dns_key
  }

  # Core Installation
  chef.add_recipe "system::before"
  chef.add_recipe "nginx"
  chef.add_recipe "mysql"

  # Project Recipes
  shared.each do|project|
    chef.add_recipe project[0]
  end

  # Post Install
  chef.add_recipe "system::after"
end

On Tuesday, April 16, 2013 12:16:33 PM UTC-6, Mitchell Hashimoto wrote:
Hello everyone,

Vagrant 1.2.0 has been released. You can upgrade by downloading the new package/installer for your operating system and overwriting the previous: http://downloads.vagrantup.com/tags/v1.2.0

IMPORTANT BACKWARDS COMPATIBILITY NOTES:

* VMware Fusion users MUST install the newly released plugin. Just `vagrant plugin install` the plugin again and verify you get version 0.5.0. This version is compatible with changes in 1.2.0.

* Windows users: Vagrant now uniformly uses the "USERPROFILE" directory for the ".vagrant.d" directory. This is the same behavior as before, except in Cygwin environments. In these environments, please either specify VAGRANT_HOME or move your "~/.vagrant.d" folder to "USERPROFILE/.vagrant.d"

There are a few major highlights in this release:

* Dramatically improved Windows support. Vagrant now works very well in cmd.exe, PowerShell, MingW/MSYS, Cygwin, and GOW environments. 

* cURL-based downloader. Box downloads are now done via cURL instead of Ruby's built-in HTTP libraries. This brings massive performance improvements since cURL manages download buffers much better. It also brings true SSL verification, FTP support, and more.

* Ansible and CFEngine provisioner support. 

* Parallelizable providers. `vagrant up` in multiple-machine environments will parallelize IF the provider supports it. VirtualBox does not support this at the moment. In time I think most providers will support this. This release lays the framework for that capability.

* Provider-specific configuration overrides, so you can change the "box" for example based on provider.

* Many many improvements and bug fixes.

While this email will coveThe details CHANGELOG can be found here: https://github.com/mitchellh/vagrant/blob/v1.2.0/CHANGELOG.md#120-april-16-2013

Best,
Mitchell

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="h539t5Z2q9AJ">vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Vagrant 1.2.0 Released

Andrew Ellis
In reply to this post by Mitchell Hashimoto
Do you have a commit on GitHub you can link me to so I can make this change my self temporarily?

Thanks man!

On Tuesday, April 16, 2013 2:45:19 PM UTC-6, Mitchell Hashimoto wrote:
Andrew,

This was just fixed and will be part of a quick 1.2.1 bug fix release coming out tomorrow.

Best,
Mitchell


On Tue, Apr 16, 2013 at 1:41 PM, Andrew Ellis <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="h539t5Z2q9AJ">awel...@...> wrote:
Awesome! So happy to have my "vagrant reload" back :)

However, I'm noticing something fishy about Chef Solo... I have 11.4.0 installed and see the following when booting:

[2013-04-16T14:30:46-06:00] INFO: *** Chef 11.4.0 ***
[2013-04-16T14:30:47-06:00] INFO: Run List is []
[2013-04-16T14:30:47-06:00] INFO: Run List expands to []
[2013-04-16T14:30:47-06:00] INFO: Starting Chef Run for web1.ellis.dev.liquidcompass.net
[2013-04-16T14:30:47-06:00] INFO: Running start handlers
[2013-04-16T14:30:47-06:00] INFO: Start handlers complete.
[2013-04-16T14:30:47-06:00] INFO: Chef Run complete in 0.04119059 seconds
[2013-04-16T14:30:47-06:00] INFO: Running report handlers
[2013-04-16T14:30:47-06:00] INFO: Report handlers complete

Here is my Chef Solo block (which was working with 1.1.5):

# Chef Solo Provisioning
web1.vm.provision :chef_solo do |chef|
  # Configuration
  chef.cookbooks_path = "development/Chef"
  chef.json = {
    "vm_id"    => 1,
    "timezone" => timezone,
    "dns_key"  => dns_key
  }

  # Core Installation
  chef.add_recipe "system::before"
  chef.add_recipe "nginx"
  chef.add_recipe "mysql"

  # Project Recipes
  shared.each do|project|
    chef.add_recipe project[0]
  end

  # Post Install
  chef.add_recipe "system::after"
end

On Tuesday, April 16, 2013 12:16:33 PM UTC-6, Mitchell Hashimoto wrote:
Hello everyone,

Vagrant 1.2.0 has been released. You can upgrade by downloading the new package/installer for your operating system and overwriting the previous: http://downloads.vagrantup.com/tags/v1.2.0

IMPORTANT BACKWARDS COMPATIBILITY NOTES:

* VMware Fusion users MUST install the newly released plugin. Just `vagrant plugin install` the plugin again and verify you get version 0.5.0. This version is compatible with changes in 1.2.0.

* Windows users: Vagrant now uniformly uses the "USERPROFILE" directory for the ".vagrant.d" directory. This is the same behavior as before, except in Cygwin environments. In these environments, please either specify VAGRANT_HOME or move your "~/.vagrant.d" folder to "USERPROFILE/.vagrant.d"

There are a few major highlights in this release:

* Dramatically improved Windows support. Vagrant now works very well in cmd.exe, PowerShell, MingW/MSYS, Cygwin, and GOW environments. 

* cURL-based downloader. Box downloads are now done via cURL instead of Ruby's built-in HTTP libraries. This brings massive performance improvements since cURL manages download buffers much better. It also brings true SSL verification, FTP support, and more.

* Ansible and CFEngine provisioner support. 

* Parallelizable providers. `vagrant up` in multiple-machine environments will parallelize IF the provider supports it. VirtualBox does not support this at the moment. In time I think most providers will support this. This release lays the framework for that capability.

* Provider-specific configuration overrides, so you can change the "box" for example based on provider.

* Many many improvements and bug fixes.

While this email will coveThe details CHANGELOG can be found here: https://github.com/mitchellh/vagrant/blob/v1.2.0/CHANGELOG.md#120-april-16-2013

Best,
Mitchell

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="h539t5Z2q9AJ">vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Vagrant 1.2.0 Released

Mitchell Hashimoto
Andrew,


Best,
Mitchell


On Tue, Apr 16, 2013 at 1:47 PM, Andrew Ellis <[hidden email]> wrote:
Do you have a commit on GitHub you can link me to so I can make this change my self temporarily?

Thanks man!

On Tuesday, April 16, 2013 2:45:19 PM UTC-6, Mitchell Hashimoto wrote:
Andrew,

This was just fixed and will be part of a quick 1.2.1 bug fix release coming out tomorrow.

Best,
Mitchell


On Tue, Apr 16, 2013 at 1:41 PM, Andrew Ellis <[hidden email]> wrote:
Awesome! So happy to have my "vagrant reload" back :)

However, I'm noticing something fishy about Chef Solo... I have 11.4.0 installed and see the following when booting:

[2013-04-16T14:30:46-06:00] INFO: *** Chef 11.4.0 ***
[2013-04-16T14:30:47-06:00] INFO: Run List is []
[2013-04-16T14:30:47-06:00] INFO: Run List expands to []
[2013-04-16T14:30:47-06:00] INFO: Starting Chef Run for web1.ellis.dev.liquidcompass.net
[2013-04-16T14:30:47-06:00] INFO: Running start handlers
[2013-04-16T14:30:47-06:00] INFO: Start handlers complete.
[2013-04-16T14:30:47-06:00] INFO: Chef Run complete in 0.04119059 seconds
[2013-04-16T14:30:47-06:00] INFO: Running report handlers
[2013-04-16T14:30:47-06:00] INFO: Report handlers complete

Here is my Chef Solo block (which was working with 1.1.5):

# Chef Solo Provisioning
web1.vm.provision :chef_solo do |chef|
  # Configuration
  chef.cookbooks_path = "development/Chef"
  chef.json = {
    "vm_id"    => 1,
    "timezone" => timezone,
    "dns_key"  => dns_key
  }

  # Core Installation
  chef.add_recipe "system::before"
  chef.add_recipe "nginx"
  chef.add_recipe "mysql"

  # Project Recipes
  shared.each do|project|
    chef.add_recipe project[0]
  end

  # Post Install
  chef.add_recipe "system::after"
end

On Tuesday, April 16, 2013 12:16:33 PM UTC-6, Mitchell Hashimoto wrote:
Hello everyone,

Vagrant 1.2.0 has been released. You can upgrade by downloading the new package/installer for your operating system and overwriting the previous: http://downloads.vagrantup.com/tags/v1.2.0

IMPORTANT BACKWARDS COMPATIBILITY NOTES:

* VMware Fusion users MUST install the newly released plugin. Just `vagrant plugin install` the plugin again and verify you get version 0.5.0. This version is compatible with changes in 1.2.0.

* Windows users: Vagrant now uniformly uses the "USERPROFILE" directory for the ".vagrant.d" directory. This is the same behavior as before, except in Cygwin environments. In these environments, please either specify VAGRANT_HOME or move your "~/.vagrant.d" folder to "USERPROFILE/.vagrant.d"

There are a few major highlights in this release:

* Dramatically improved Windows support. Vagrant now works very well in cmd.exe, PowerShell, MingW/MSYS, Cygwin, and GOW environments. 

* cURL-based downloader. Box downloads are now done via cURL instead of Ruby's built-in HTTP libraries. This brings massive performance improvements since cURL manages download buffers much better. It also brings true SSL verification, FTP support, and more.

* Ansible and CFEngine provisioner support. 

* Parallelizable providers. `vagrant up` in multiple-machine environments will parallelize IF the provider supports it. VirtualBox does not support this at the moment. In time I think most providers will support this. This release lays the framework for that capability.

* Provider-specific configuration overrides, so you can change the "box" for example based on provider.

* Many many improvements and bug fixes.

While this email will coveThe details CHANGELOG can be found here: https://github.com/mitchellh/vagrant/blob/v1.2.0/CHANGELOG.md#120-april-16-2013

Best,
Mitchell

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
 
 
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Vagrant 1.2.0 Released

Andrew Ellis
In reply to this post by Andrew Ellis
Never mind, found it!

On Tuesday, April 16, 2013 2:47:33 PM UTC-6, Andrew Ellis wrote:
Do you have a commit on GitHub you can link me to so I can make this change my self temporarily?

Thanks man!

On Tuesday, April 16, 2013 2:45:19 PM UTC-6, Mitchell Hashimoto wrote:
Andrew,

This was just fixed and will be part of a quick 1.2.1 bug fix release coming out tomorrow.

Best,
Mitchell


On Tue, Apr 16, 2013 at 1:41 PM, Andrew Ellis <[hidden email]> wrote:
Awesome! So happy to have my "vagrant reload" back :)

However, I'm noticing something fishy about Chef Solo... I have 11.4.0 installed and see the following when booting:

[2013-04-16T14:30:46-06:00] INFO: *** Chef 11.4.0 ***
[2013-04-16T14:30:47-06:00] INFO: Run List is []
[2013-04-16T14:30:47-06:00] INFO: Run List expands to []
[2013-04-16T14:30:47-06:00] INFO: Starting Chef Run for web1.ellis.dev.liquidcompass.net
[2013-04-16T14:30:47-06:00] INFO: Running start handlers
[2013-04-16T14:30:47-06:00] INFO: Start handlers complete.
[2013-04-16T14:30:47-06:00] INFO: Chef Run complete in 0.04119059 seconds
[2013-04-16T14:30:47-06:00] INFO: Running report handlers
[2013-04-16T14:30:47-06:00] INFO: Report handlers complete

Here is my Chef Solo block (which was working with 1.1.5):

# Chef Solo Provisioning
web1.vm.provision :chef_solo do |chef|
  # Configuration
  chef.cookbooks_path = "development/Chef"
  chef.json = {
    "vm_id"    => 1,
    "timezone" => timezone,
    "dns_key"  => dns_key
  }

  # Core Installation
  chef.add_recipe "system::before"
  chef.add_recipe "nginx"
  chef.add_recipe "mysql"

  # Project Recipes
  shared.each do|project|
    chef.add_recipe project[0]
  end

  # Post Install
  chef.add_recipe "system::after"
end

On Tuesday, April 16, 2013 12:16:33 PM UTC-6, Mitchell Hashimoto wrote:
Hello everyone,

Vagrant 1.2.0 has been released. You can upgrade by downloading the new package/installer for your operating system and overwriting the previous: http://downloads.vagrantup.com/tags/v1.2.0

IMPORTANT BACKWARDS COMPATIBILITY NOTES:

* VMware Fusion users MUST install the newly released plugin. Just `vagrant plugin install` the plugin again and verify you get version 0.5.0. This version is compatible with changes in 1.2.0.

* Windows users: Vagrant now uniformly uses the "USERPROFILE" directory for the ".vagrant.d" directory. This is the same behavior as before, except in Cygwin environments. In these environments, please either specify VAGRANT_HOME or move your "~/.vagrant.d" folder to "USERPROFILE/.vagrant.d"

There are a few major highlights in this release:

* Dramatically improved Windows support. Vagrant now works very well in cmd.exe, PowerShell, MingW/MSYS, Cygwin, and GOW environments. 

* cURL-based downloader. Box downloads are now done via cURL instead of Ruby's built-in HTTP libraries. This brings massive performance improvements since cURL manages download buffers much better. It also brings true SSL verification, FTP support, and more.

* Ansible and CFEngine provisioner support. 

* Parallelizable providers. `vagrant up` in multiple-machine environments will parallelize IF the provider supports it. VirtualBox does not support this at the moment. In time I think most providers will support this. This release lays the framework for that capability.

* Provider-specific configuration overrides, so you can change the "box" for example based on provider.

* Many many improvements and bug fixes.

While this email will coveThe details CHANGELOG can be found here: https://github.com/mitchellh/vagrant/blob/v1.2.0/CHANGELOG.md#120-april-16-2013

Best,
Mitchell

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.