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

Document update for vDVS upgrade instruction and expected behavior #1700

Closed
shuklanirdesh82 opened this issue Aug 5, 2017 · 0 comments
Closed

Comments

@shuklanirdesh82
Copy link
Contributor

One of our customer reached out through gitter channel, it seems our document should provide better detail about expected behavior of upgrade workflow with recommended steps.

for your reference some of the questions to address in our document:

1. how to make upgrade of vdvs a safe operation?
2. what actually happens to data which container tries to write to volume during plugin upgrade? If I run docker plugin rm command the /var/run/docker/plugins/*/vsphere.sock is deleted so how container accesses vmdk file in datastore?

For more information, please refer https://gitter.im/vmware/docker-volume-vsphere.

/CC @msterin @pdhamdhere

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Projects
None yet
Development

No branches or pull requests

4 participants