Support of more than one DVS

[Andrzej Skupień]

Branch: kilo-dvs-agent

Please add support of mutliple DVSes.
Current assumptions:
1. There should be one DVS per Cluster per physnet
2. There should be one dvs-agent per Cluster
3. Dvs-agent should be deployed on same host as nova-compute-vmware-proxy is.

[Andrzej Skupień (kendriu)]

Setting to incomplete, because we don't have final architeture yet

[Andrzej Skupień (kendriu)]

Looks like dvs-agent should choose proper DVS basing on value returned by VMwareDVSMechanismDriver. get_mappings

Quoting Eugene Nikanorov:
"""
get_mappings returns correspondence between physnet's and physical bridges.
That may or may not not make sense for your particular agent.
For example, for OVS agent that is an indication that tenant networks created for certain "physnet" should "go" through certain bridge configured on controlles/computes. In other words it's a way of mapping between the network and physical bridges.
I guess that doesn't make sense for dvs driver, but I'm not sure.
Most probably you don't need mappings at all indicating that all networks are implemented in the same way via means of the backend you're creating the driver for. That would just means that you agent on compute node (or wherever it will run) will receive the network, having additional attribute "provider:network" empty.
"""