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

Leverage role based access of VC to manage volume creation. #502

Closed
kerneltime opened this issue Jun 30, 2016 · 4 comments
Closed

Leverage role based access of VC to manage volume creation. #502

kerneltime opened this issue Jun 30, 2016 · 4 comments

Comments

@kerneltime
Copy link
Contributor

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.

@kerneltime kerneltime added this to the v1 GA milestone Jun 30, 2016
@andrewjstone
Copy link
Contributor

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.

@govint
Copy link
Contributor

govint commented Jul 1, 2016

+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.

@andrewjstone
Copy link
Contributor

I agree govint.

@pdhamdhere
Copy link
Contributor

Addressed with #603 and tech-preview available in Oct 2016 release.

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

No branches or pull requests

5 participants