Multi-nic support with N1K plugin

[Abishek Subramanian]

When the cisco N1K neutron plugin is being used, an instance cannot be launched via Horizon with ability to have multiple nics.
Only the first network is used for all created nics.

This bug addressed that issue.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/65793
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=faee0c0c9284ded67a35b57fed4a68b4cfacea15
Submitter: Jenkins
Branch: master

commit faee0c0c9284ded67a35b57fed4a68b4cfacea15
Author: Abishek Subramanian <email address hidden>
Date: Wed Jan 7 14:08:23 2015 -0500

    Fix multi-nic issue with nexus plugin

    Fixes inability to assign different networks to
    multi-nics when launching a vm using the cisco n1k plugin.

    This fixes an issue wherein with the cisco n1k plugin
    launching an instance with multiple nics via horizon causes the
    same network to get assigned to all nics.

    Additionally modifying the existing test_launch_instance_post
    test to handle the situation wherein two nics are created
    with the N1K plugin using the N1K policy profile. Hence a new
    unit test reflects two ports being created. Two more unit tests
    to test port create exceptions are added to test exception
    handling as well.

    Closes bug: #1260436

    Change-Id: Ie91c94e534e1cc1dddbb6ac563b0bef102451cf1