Remove environment name restrictions

[Ekaterina Chernova]

Previously, environment name used in heat stack name and because of that there were some restrictions on environment name.

But now, environment name is not used anywhere in engine at all. So user can can set any name to group of applications. (environment)

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Ekaterina Chernova (<email address hidden>) on branch: master
Review: https://review.openstack.org/144305

[OpenStack Infra (hudson-openstack)]

Change abandoned by Ekaterina Chernova (<email address hidden>) on branch: master
Review: https://review.openstack.org/152559

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/237458
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=ac2b523302604abca83212233d5d68ea43651877
Submitter: Jenkins
Branch: master

commit ac2b523302604abca83212233d5d68ea43651877
Author: Nikolay Starodubtsev <email address hidden>
Date: Mon Oct 19 17:20:25 2015 +0300

    Remove obsolete names checks

    Since we don't use environments and environment templates names during
    deployment process we don't need to check what is the name of the
    environment. Now we should only keep it human-readable and check that
    it exists.

    Partial-Bug: #1405788
    Change-Id: I88b447e0dbe9fde07602d4ce1e746c1ccfa62637

[Nikolay Starodubtsev (starodubcevna)]

Need to remove restriction from murano-dashboard. API side is okay now.

[OpenStack Infra (hudson-openstack)]

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

[Dmytro Dovbii (ddovbii)]

what about security groups? we use name of environment as a part of security group name:
https://github.com/openstack/murano/blob/master/meta/io.murano/Classes/system/SecurityGroupManager.yaml#L25
if we delete these restrictions, will Heat be able to create groups?

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/260972
Committed: https://git.openstack.org/cgit/openstack/murano-dashboard/commit/?id=4b7846ae4a239c19858770ef678b8e60d617310d
Submitter: Jenkins
Branch: master

commit 4b7846ae4a239c19858770ef678b8e60d617310d
Author: zhurong <email address hidden>
Date: Sat Dec 19 00:23:28 2015 +0800

    Remove environment name restrictions

    Since we don't use environments and environment templates names during
    deployment process we don't need to check what is the name of the
    environment. Now we should only keep it human-readable and check that
    it exists.

    Change-Id: I2d665b41deebf0c008d8b2b71802a1ab2c6673e8
    Closes-Bug: #1405788

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/murano-dashboard 2.0.0.0b3 development milestone.