Bug 1041245

Summary:	[RFE][nova]: Nova security group name/description validation in Neutron environment
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/consistency-securitygroup-api-nova-neutron
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_drafting
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:40:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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