Documentation - server:security_groups has no effect if neutron ports assigned

[Steve McLellan]

It makes sense now, but it's not clear from the documentation that if you assign a neutron port to a Nova::Server, security_groups assigned to the Server have no effect, although there's no notification.

Something in the Nova::Server template documentation would be helpful (or perhaps yet, reject the template). "If neutron ports are assigned, security_groups will have no effect. Assign them instead to individual ports."

[Steve Baker (steve-stevebaker)]

Better docs on the server security_groups property would help. We should also be able to validate on the server to not allow both security_groups and ports to be specified.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/69052
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=a60c684b5c8b6bc24520db3dfa95fd0b6f5409e6
Submitter: Jenkins
Branch: master

commit a60c684b5c8b6bc24520db3dfa95fd0b6f5409e6
Author: Steve McLellan <email address hidden>
Date: Fri Jan 24 15:36:30 2014 -0600

    Server secgroups and network/port together invalid

    Nova silently ignores security_groups properties for a server if the
    server has a 'networks' property that references a neutron port, the
    intent being that security groups are assigned to the port(s).

    Adds note to Server properties to this effect.
    Validation fails for a Server if 'security_groups' is defined AND
    the server has neutron Ports assigned.

    Change-Id: I883761a0bb0e73a3fcc7c362d8e6dc5a099806e0
    Closes-Bug: #1270313