test_port_security_macspoofing_port should not use dhcp port

[YAMAMOTO Takashi]

dhcp port is an implementation detail of the reference implementation.
it's better for port-sec test independent from it.

[OpenStack Infra (hudson-openstack)]

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

[Yair Fried (yfried)]

Do you have an example where the secondary network ("new_net") wouldn't have a dhcp port?

[YAMAMOTO Takashi (yamamoto)]

Yair,

for example, midonet has an alternative dhcp and metadata proxy implementation [1]
which doesn't use neutron dhcp agent. (note that dhcp port is created by neutron dhcp agent.)

[1] https://github.com/midonet/midonet/blob/master/docs/openstack-metadata-usage.md

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/251423
Committed: https://git.openstack.org/cgit/openstack/tempest/commit/?id=c3978419bf1e368afd00fb06bf27afd0d6ecc3a6
Submitter: Jenkins
Branch: master

commit c3978419bf1e368afd00fb06bf27afd0d6ecc3a6
Author: YAMAMOTO Takashi <email address hidden>
Date: Mon Nov 30 23:55:56 2015 +0900

    test_port_security_macspoofing_port: Don't assume DHCP port

    DHCP port is a detail of the reference implementation.
    Non agent based implementations might not provide it.
    Anyway, as the purpose of this test case is to test
    port-security, not DHCP, it's better to avoid assuming
    the existance of DHCP port. Use an ordinary VM instead.

    Closes-Bug: #1521224
    Change-Id: I84a69c6b3d81218ba7811332d936cb891bdff353