Asset name should be validated against a specific service not across services

[Sahdev Zala]

Currently, it seems like, asset name is required to be unique across the schema. However, this can be a problem for two catalog services with similar offerings, for example heat and tosca. Since both services cater to templates, it is common that both can offer a similar type of templates.

For example, Hello World template where 'Hello World' is an appropriate asset name to both services. But currently, it doesn't allow user to set the same name.

2016-03-07 19:58:09.693 | Traceback (most recent call last):
2016-03-07 19:58:09.693 | File "openstack_catalog/tests/test_openstack_catalog.py", line 61, in test_asset_schema_conformance
2016-03-07 19:58:09.693 | 'openstack_catalog/web/static/assets.schema.yaml')
2016-03-07 19:58:09.694 | File "openstack_catalog/tests/test_openstack_catalog.py", line 51, in _verify_by_schema
2016-03-07 19:58:09.694 | self.fail("Duplicate asset name: %s" % name)
2016-03-07 19:58:09.694 | File "/home/jenkins/workspace/gate-app-catalog-python27/.tox/py27/local/lib/python2.7/site-packages/unittest2/case.py", line 690, in fail
2016-03-07 19:58:09.694 | raise self.failureException(msg)
2016-03-07 19:58:09.694 | AssertionError: Duplicate asset name: Hello World
http://logs.openstack.org/32/289132/4/check/gate-app-catalog-python27/66f7ae3/console.html

The solution could to check uniqueness of name within a particular service, not across services, for a better naming and display on http://apps.openstack.org