Re: [vagrant-up] [ANN] vagrant-vmware-fusion/workstation 4.0.17

[Torben Knerr]

Hi Chris, 

just wondering: wasn't linked clones already supported for VMware Workstation already ever since Vagrant 1.8 came out? 

Or is there anything new to this? 

Cheers, 

Torben 

Am 28.02.2017 6:25 nachm. schrieb "Chris Roberts" <crob...@hashicorp.com>:

Hi everyone,

I'm pleased to announce the release of vagrant-vmware-fusion and vagrant-vmware-workstation 4.0.17. This release adds support for linked clones to VMware Workstation. It also includes bug fixes for invalid guest IP addresses returned from vmware and NAT configuration file repair support to prevent invalid port collisions. The full list of updates can be found in the CHANGELOG:

https://github.com/hashicorp/vagrant-plugin-changelog/blob/master/vagrant-vmware-changelog.md#4017-february-28-2017

Cheers!

- Chris Roberts

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/7cf4c8c7-b2d6-4392-87e0-9c4a3c25eb3f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chris Roberts]

Hi Torben,

Linked clones were supported in Fusion, but were not enabled in Workstation. This update enables them in Workstation as well. It also adds the `linked_clone` option seen in the VirtualBox provider configuration to enable/disable linked clones.

- Chris

[Torben Knerr]

Hi Chris,

thanks, and sorry for the late reply. I just double-checked and noticed we were actually using the `linked_clone` option for the vmware_workstation provider already, but looks like it was a no-op for vmware workstation until this release of the plugin. Cool stuff!

Another question: was it by intent that the 4.0.14 version is not available anymore on https://gems.hashicorp.com? We are currently experiencing some build failures because some of our systems are currently pinning to the 4.0.14 version explicitly.

Is there some kind of retirement policy for the vagrant-vmware-* plugins I'm not aware of?

Cheers,

Torben

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/746a4aa1-554f-41e3-8906-0d7c1fdc5fd3%40googlegroups.com.