Orchestration Resource Types names restriction is incorrect

[Tatiana Ovchinnikova]

The additional columns "Implementation", "Component" and "Resource" are representative for a limited resource type group only. Resource type name can have less or more than three words and Heat even allows to specify a URL as a resource type. Horizon should not use these columns at all: "Type" column and filter will do just the same trick.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit a86c7d9be7b7399b117b1289d6548f50b657efe6
Author: Tatiana Ovchinnikova <email address hidden>
Date: Wed Aug 17 20:21:19 2016 +0300

    Remove Orchestration Resource Types names restriction

    The additional columns "Implementation", "Component" and "Resource"
    are representative for a limited resource type group only. Resource
    type name can have less or more than three words and Heat even allows
    to specify a URL as a resource type. Horizon should not use these
    columns at all: "Type" column and filter will do just the same trick.

    Change-Id: I38a671490b90122e2d75e6aa11d3de0fa12817c9
    Closes-Bug: #1614000

[Doug Hellmann (doug-hellmann)]

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