Bug 1041245 - [RFE][nova]: Nova security group name/description validation in Neutron environment
Summary: [RFE][nova]: Nova security group name/description validation in Neutron envir...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 14:04 UTC by RHOS Integration
Modified: 2015-03-19 17:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:40:39 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RHOS Integration 2013-12-12 14:04:29 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/consistency-securitygroup-api-nova-neutron.

Description:

NativeNovaSecurityGroupAPI and NativeNeutronSecurityGroupAPI in Nova have different rules concerning the validation of security group names and descriptions.  Nova does not accepts empty names/descriptions and Neutron does no validation.  The aim of this blueprint is to add validation to NativeQuantumSecurityGroupAPI, thereby providing consistency between both APIs, and ensuring that Nova API will react the same regardless of backend.

Specification URL (additional information):

None
Note You need to log in before you can comment on or make changes to this bug.