Comment 2 for bug 1516994

It looks like that, if we want delegate ports/networks management to agent, we would have to implement everything by hand.
This isn't something that ovs mech driver does either.

Furthermore decision to move this functionality to agent should depend on vSphere API. if it can deal with concurrent requests
then we may leave management in the plugin, if it should be serialized - then we need to put it into the agent.

In our case, port and networks management works fine as it is now implemented, so without other argument it should stay in driver.