Comment 16 for bug 1187244

Reviewed: https://review.openstack.org/98488
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=322cc9336fe6f6fe9b3f0da33c6b26a3e5ea9b0c
Submitter: Jenkins
Branch: master

commit 322cc9336fe6f6fe9b3f0da33c6b26a3e5ea9b0c
Author: Racha Ben Ali <email address hidden>
Date: Wed Jan 15 00:42:31 2014 -0800

    Boot an instance with multiple vnics on same network

    If the same L2 network is requested multiple times for the same
    instance then creating ports on same network and attaching them
    to the same instance raises a DuplicateNetworks exception.
    Similarly, attaching multiple existent ports on same L2 network
    to the same instance raises a DuplicateNetworks exception. This
    is the default behavior that is defaulted by a newly introduced
    nova flag "allow_duplicate_networks" which is set to
    False by default.

    Not raising a DuplicateNetwork exception and allowing an instance
    to have multiple vnics on same network is useful for NfV service
    instances and in that case this newly introduced nova flag should
    be set to True.

    DocImpact: New neutron.allow_duplicate_networks configuration option
    Implements blueprint multiple-if-1-net
    Change-Id: Id4d633162c785c9b56b9c8426c0445770bc1352e
    Closes-Bug: #1187244