NvpAdvancedPlugin should redefine create_network too

[Armando Migliaccio]

As other operations like create_lrouter etc, create_network should also go through the AdvancedPlugin

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/47489

[Salvatore Orlando (salvatore-orlando)]

is the change a draft?

[Armando Migliaccio (armando-migliaccio)]

yes it was...now it's public

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/47489
Committed: http://github.com/openstack/neutron/commit/4757ccfc8eb10bee756deb36c72d7a7ca37bdbff
Submitter: Jenkins
Branch: master

commit 4757ccfc8eb10bee756deb36c72d7a7ca37bdbff
Author: armando-migliaccio <email address hidden>
Date: Fri Sep 13 13:34:00 2013 -0700

    Redefine behavior for NvpAdvancedPlugin during network creation

    When using the NvpAdvancedPlugin, *all* logical switches should
    be created through VCNS. VCNS will then proxy the requests to
    NVP. This patch implements such a behavior. This is achieved by
    replacing the use of nvplib.create_lswitch with the one of the
    vcns driver, as the remaining logic can be left as it is.

    Fixes bug #1225011

    Change-Id: I6c276f747d02ac0d4934c38bf2858cf9b73c5e24