You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.
I think we should very strongly consider tying the plugin to vcenter, and how we do it. If we feed vcenter info that's one thing, but relying on it for centralized management state seems wrong in a container centric world. Especially with regards to photon controller use in the future.
+1 not having to rely on VC is the way forwards. But the way VSphere is made, we need a parallel implementation thats non-VC role-based access. And that should be implemented for VSphere, not for/by the plugin.
This is based on feedback received @http://cormachogan.com/2016/06/01/docker-volume-driver-vsphere/#comment-4465
This is a request to leverage role based access part of VC to control volume creation and workflow when VC is part of the environment.
The text was updated successfully, but these errors were encountered: