Further to this, the reason why we want '@' characters in security group names to work in general is that StarCluster (http://star.mit.edu/cluster/) wants to create secgroups with names like these when it drives OpenStack via EC2 API.
It may be possible for the StarCluster/OpenStack EC2 interop to work even if Horizon continues to be unable to create such security groups, but even then, I think Horizon should be fixed for reasons of completeness and consistency with 'nova secgroup-create'.
Further to this, the reason why we want '@' characters in security group names to work in general is that StarCluster (http:// star.mit. edu/cluster/) wants to create secgroups with names like these when it drives OpenStack via EC2 API.
It may be possible for the StarCluster/ OpenStack EC2 interop to work even if Horizon continues to be unable to create such security groups, but even then, I think Horizon should be fixed for reasons of completeness and consistency with 'nova secgroup-create'.