Hi, Chris
> With that change in place you can still use the 'instance-xxx-tapxxxx' ID
> in the <id> part of /v1/metric/resource/<type>/<id> URLs and in
> search queries.
But we cannot know the tap name through nova api or neutron api.
In general, there exists some conditions that we cannot know the exact
resource id in advance. And using hash of resource id also makes fuzzy search
impossible. What we know are some relationships between resources, like a vm
has several taps. The resource instance-111 and resource instance-111-tap111
has inborn connections.
So I suggest that we should add some attribute to describe such relation.
------------------
Luo Gangyi luogan...@cmss.chinamobile.com
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
