Multiple security groups with the same name are created

[kiran-vemuri]

Description:
------------
I am able to create multiple security groups with the same name and same description. This behaviour can result in confusion.

Expected Behaviour:
------------------
Enforcing uniqueness in security group names

AWS gives me an error when I try to create multiple security groups with the same name in the same vpc.

'''
An error occurred creating your security group.
The security group 'launch-wizard-3' already exists for VPC 'vpc-03cfc166'
'''

Environment:
-----------
OpenStack Mitaka on Ubuntu 14.04 server

Reproduction Steps:
-------------------

Steps from horizon:
1. Create multiple security groups with same name and same description

Steps from cli:
1. Run the command "nova secgroup-create test test" multiple times

Result:
------
nova secgroup-list
+--------------------------------------+---------+------------------------+
| Id | Name | Description |
+--------------------------------------+---------+------------------------+
| 7708f691-7107-43d3-87f4-1d3e672dbe8d | default | Default security group |
| 60d730cc-476b-4d0b-8fbe-f06f09a0b9cd | test | test |
| 63481312-0f6c-4575-af37-3941e9864cfb | test | test |
| 827a8642-6b14-47b7-970d-38b8136f62a8 | test | test |
| 827c33b5-ee4b-43eb-867d-56b3c858664c | test | test |
| 95607bc1-43a4-4105-9aad-f072ac330499 | test | test |
+--------------------------------------+---------+------------------------+

[kiran-vemuri (kiran-vemuri)]

AWS gives me an error when I try to create multiple security groups with the same name in the same vpc.

'''
An error occurred creating your security group.
The security group 'launch-wizard-3' already exists for VPC 'vpc-03cfc166'
'''

[Matt Riedemann (mriedem)]

This is how neutron works (assuming you're using neutron), security group names and descriptions are not unique. If you were using nova-network (which is now deprecated), security group names are unique per project, but nova-network != neutron and as noted nova-network is deprecated.

[Armando Migliaccio (armando-migliaccio)]

Names are generally not the unique identifiers in OpenStack. You can create multiple resources, any type, and use the same name over and over again. This is not just an issue with security groups per se.

[kiran-vemuri (kiran-vemuri)]

@Armando and @Matt I totally understand that OpenStack in general uses UUID's as the unique identifiers for various entities and allows duplication of names.

But, in a project if an admin creates multiple security groups with the same name, how will the other users be able to identify the correct security group to associate to the VM? They can't keep track of the UUID right?

To give you an analogy, if a domain name 'google.com' was pointing to yahoo and facebook IP addresses, we can't really ask the users to remember the IP addresses to uniquely identify what server they want to connect to?

I mean having same name repeated in a different project makes sense but, I'm just trying to understand how it makes sense to allow multiple entities with same name in the same project?