Skip to content
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.

vDVS 0.14 Release 2017

Pre-release
Pre-release
Compare
Choose a tag to compare
@shuklanirdesh82 shuklanirdesh82 released this 11 May 02:27
· 356 commits to master since this release
0.14
0577889

IMPORTANT

Note:

What's New

  • Cross-ESX Multi-tenancy (Experimental feature - Please drop us a note with your use cases)
  • Cleanup stale volumes upon VM, Host failure
  • Bug fixes

Contact us at

Downloads

Installation instructions

Change Log

0.14 (2017-05-10)

Full Changelog

Closed issues:

  • Attachment info upon Get/List #1199
  • [Multi-ESX] vmgroup is not removable when vms are added from both ESXs (configured as MultiNode) #1188
  • Add goreport tag to the project #1136
  • "restart" option in CI does nothing #1107
  • Extra testbed for test matrix (ESX versions, Docker versions) #161
  • VSAN volume status isn't updated to "detached" on VM poweroff event #1233
  • Wrong network type in config.json #1225
  • Use use full volume name as mountpoint in mount request and check it to avoid redundant mount. #1220
  • LogLevel is not handled if present in docker-volume-vsphere.conf #1203
  • Publish VUM compatible zip file for vmdkops #1198
  • Invalid syntax in docker-volume-vsphere.conf can cause high CPU. #1194
  • [Multi-ESX] volume metadata file got deleted while removing volume from VM(placed on Esx2) which is in use by another VM(placed on Esx1) #1191
  • Unable to unmount/detach volume after vmgroup membership change #1189
  • Admin CLI gives SyntaxWarning #1180
  • Volume stays attached after abrupt docker plugin kill and container exit #1159
  • Able to create volume from VM which belongs to newly created tenant #1145
  • [Multi-ESX] DB connection issue while invoking "vmdkops_admin volume ls" observed only on one ESX #1144
  • handling default_datastore for vmgroup #1143
  • [Multi-ESX] Confusing difference in SingleNode vs MultiNode behavior after config init #1138
  • Update user-guide - create VSAN storage policy command is incorrect #1133
  • Add VM_Name in config DB #1130
  • Update instructions to cut the release #1129
  • [Multi-ESX] VM's belonging to the same tenant are not visible across ESXs #1127
  • Able to add vm to the _DEFAULT vm-group #1125
  • [Multi-ESX] admin cli vm-group access ls command fails with default configuration #1123
  • Handle datastores with spaces or special characters #1116
  • Add a unit test case to verify that the default vm group name (_DEFAULT) can't be changed. #1109
  • Plugin panic during format-remove #1062
  • Complete the move to managed plugins - drop support for unmanaged ones #1051
  • Implement multi-node ESX support in tenancy/auth code #1032
  • Add documentation for VUM #555
  • Auto-cleanup after VM power off (detach volumes) #369

Merged pull requests:

Assets 2
Loading