Quantum security group does not work with the debug port

[Jason]

The quantum security group does not work with the quantum probe port with network:probe as device owner property, the capability of creating the quantum debug probe port with other device owner property should be added.

[dan wendlandt (danwent)]

i'm assuming there's no need to target this to grizzly, is there?

[Nachi Ueno (nati-ueno)]

Hi Dan

I'm planning to add integration test for security group using this feature.
Since still need discuss with Maru, so It may be not in G.
But let me try it if you are OK.

[Akihiro Motoki (amotoki)]

Nachi,

This review seems to be related to this issue, but you have already marked it as "Do not merge". Does it mean this bug should be moved to Havana?
https://review.openstack.org/#/c/19890/

[Nachi Ueno (nati-ueno)]

yes this work is moved to H

[Akihiro Motoki (amotoki)]

Thanks. I missed it is already targeted to H-1.

[Nachi Ueno (nati-ueno)]

This one is needed for quantum-gating with security group , so I retargetd to the RC1

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/19890
Committed: http://github.com/openstack/quantum/commit/1d206cc309a3fb51c50c77ab31b886b890f0bd1f
Submitter: Jenkins
Branch: master

commit 1d206cc309a3fb51c50c77ab31b886b890f0bd1f
Author: Zhesen <email address hidden>
Date: Wed Jan 16 17:57:57 2013 -0800

    Allow probe-create to specify device_owner.

    The device owner of the probe port can be
    specified by the --device-owner option.

    There are two values for device-owner option,
    network or compute.

    The probe port will be created with the network
    as the device owner by default.

    Fixes: bug #1102726

    Change-Id: I72d62e2fe7b8f7a5eb4411bc9052efa82fb4fdf5