You Got a Killer Scene There Man...

Changes in version 0.3.3 include:

Changes

• Configuration setting computer_name renamed to compute_name as this can be either a vSphere host or a Cluster name.

Fixes

• Better error management
• Fixed some commands in unwanted situations (SSH when machine suspended/off)
• Refactored code to avoid code duplication

Misfit Love

Merge branch 'release/v0.3.2'

Conflicts:
	README.md
	lib/vagrant-vcenter/version.rb

Lightning Song

• Fixed a serious regression
• Added support for Vagrant 1.6.5+

Another Love Song

Changes in version 0.3.0 include:

Fixes

• vmware_ovf support!
• You can now specify network using the public_network notation of Vagrant.
• Plugin is now operating in parallel, MOAR SPEED!
• Create the VM folder if it doesn't exist.
• Several bug fixes.

If I had a Tail

Changes in version 0.2.1 include:

Fixes

• Hostname using linux prep needs to be hostname and domain not fqdn on both.
• Checking the power state at that spot can cause ruby exceptions to be thrown.

Thanks to Karl Pietri for this PR.

First it Giveth

Changes in version 0.2.0 include:

New Features

• Add option to set the actual vm name
• Set some options in the vm via linux prep
• Static networking
• Hostname
• Add option to set vmnetwork name and backing
• Vagrant now uses builtin SyncedFolders helper to synchronize folders

Fixes

• Fix the read_ssh_info if the vm doesn't have a network yet at first try the later ssh's wont forever fail

Many thanks to Karl Pietri for submitting PR #4 with all these new features!

Songs for the Deaf

Changes in version 0.1.1 include:

• Support for vagrant share [Fixes #2]
• Support for Vagrant Cloud boxes [Fixes #1]

Smooth Sailing

Right now the provider supports the following features:

• Cluster or single host deployments
• Linked clones
• Templates upload

What is still missing:

• TEST SUITES! (working on that).
• Speed, the code is definitely not optimized.
• Thorough testing.
• Error checking is absymal.
• Some spaghetti code here and there.
• Bugs, bugs and BUGS!.

If you're a developer and want to lend us a hand, head over to our develop branch and send us PRs!