Release 0.5.0

Backwards-incompatible changes

• The symbol VAGRANT has been moved from libcloudvagrant.driver to libcloudvagrant.
• The Vagrant plugin vagrant-libcloud-helper is now required.
• libcloud-vagrant now checks that all components (Vagrant, VirtualBox and required plugins) are present and at the expected version numbers, throwing a RuntimeError if that's not the case.
• Driver methods ex_start_node() and ex_stop_node() have been removed.

Backwards-compatible changes

• Switch from nose to py.test for the test suite.
• The driver method create_node() now accepts an optional extension parameter ex_allocate_sata_ports, to select how many SATA ports will be allocated on the first SATA controller.

Bug fixes

• Destroying nodes with attached disks raised an error when detaching the disk (because the node destruction happened before the disk detach).
• When a node was destroyed, all volumes attached to it were not marked as detached.
• The command-line tool was not destroying volumes when requested to destroy everything.
• Destroying volumes did not remove them from the Virtualbox media registry.

Release 0.4.0

Backwards-incompatible changes

• The Vagrant plugin vagrant-libcloud-helper is now required for attaching storage volumes to nodes.
• Virtualbox shared folders are disabled, in order to make Vagrant boxes resemble more closely nodes created by other providers.

Backwards-compatible changes

• Storage volumes can be hot-plugged (if the host operating system supports it).
• Vagrant node instances have an extension attribute called ex_ssh_client, a context manager wrapping an instance of libcloud.compute.ssh.SSHClient.
• The Vagrant plugin vagrant-proxyconf, if available in the host system, is set up in order to allow node deployments behind an HTTP proxy.

Release 0.3.0

Backwards-incompatible changes

• Nodes have now an id field, matching the VirtualBox UUID.
  You must recreate all the nodes defined in your ~/.libcloud-vagrant
  catalogue.

Backwards-compatible changes

• New command-line tool libcloud-vagrant to do simple operations
  with Vagrant nodes created by Libcloud.
• Interactions with Vagrant and Virtualbox are protected by a
  filesystem-based lock.
• Unit tests use now a free 24-bit network in the 192.168/16 range,
  instead of using hard-coded ones.
• The host network interfaces of public networks are destroyed when the
  Vagrant network objects are destroyed.
• libcloud-vagrant now makes fewer calls to the Virtualbox
  VBoxManage command.

Release 0.2.0

Backwards-incompatible changes

• The non-standard parameter networks in the create_node driver
  method has been renamed to ex_networks, in order to signal that
  it's non-standard.

Backwards-compatible changes

• New driver method ex_list_networks() which returns a list of
  defined networks.

Bug fixes

• The driver method deploy_node() was badly broken:
  • It did not work if the node had not been created before.
  • It did not return the node object for the created node.

Version 0.1.0

Initial public version