I have a question that I thought was very simple but I probably am missing something.
I would like to create some kind of self-service test environment in my VCenter. Of course, I would like to isolate this environment from the rest of my network. The simplest and safest way would be to dedicate a host for that and physically limit its access to the network via firewall, however this is not possible in my case.
This means that I will have to allow people to fully control the VM creation/modification in a resource pool, including adding/removing/editing network cards. However I want to restrict them to some specific network cards (which are attributed to specific VSwitches).
For example, let's say I have sveral network configurations for : LAN, INTERNET, DMZ, HOST-ONLY.
How can I give full access rights on a resource pool without allowing access to LAN and DMZ when editing VM settings ?
It's probably very simple but I cannot figure it out by myself.
very similar question here after 4 years, just on start of my vCenter journey (some 2 months now), preparing lab deployment for the team and looking for restricting access to some network resources.
Have you found a way to solve your issue, what was it?
Thanks if you come by and quickly (hope so) react.
What are you trying to achieve exactly?
What devices/systems should and should not be able to communicate with one another?
Where are these devices/systems relative to your underlying network?
easy thing. We are bunch of networkers virtualizing all we can in our lab to match real customer deployments and trends, so while migrating to vCenter and being only conf tool for them, we need to keep their comfort of being able to create vSwitches, portgroups.. etc like there are used to from single-host access.
For that, folks of "VM Power User" role need to have Hosts.Configuration.NetworkConfiguration role. In turn, they get by default a right to do so on all hosts in vCenter domain (datacenter), and in vCenter's GUI there is no option to specifically limit their config access to some core vSwitches we determine.
How can I achieve that?