Security groups need to be created in non-ASCII characters

[Matt Borland]

There are many localizations that do not use standard ASCII, and the code currently restricts individuals from creating Security Groups with names containing non-ASCII characters.

You can see in https://review.openstack.org/#/c/54007/ and the associated launchpad tickets that the current validation was only loosening overly-restrictive validation; I believe we need to restrict them even less.

Unless there are specific reasons that the names need to be ASCII, we should loosen this restriction.

[Matt Borland (palecrow)]

It should be noted that users have been able to create security groups from the command line including such non-ASCII characters.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/324079
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=db23d096b2a0a4d4164cdcb19909bc4d5a92f90c
Submitter: Jenkins
Branch: master

commit db23d096b2a0a4d4164cdcb19909bc4d5a92f90c
Author: Matt Borland <email address hidden>
Date: Wed Jun 1 13:52:28 2016 -0600

    Allowing non-ASCII characters for Security Group names

    See bug report for details; this removes the ASCII-only restriction for
    the Security Group name. You can also test that the command-line allows
    for non-ASCII characters, so we should do the same.

    Change-Id: I5dc4ca35985b134ac806a1c7d50e045c3f462137
    Closes-Bug: 1588039

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/horizon 10.0.0.0b2 development milestone.