cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nitin Mehta <>
Subject Re: [MERGE] CS-2163
Date Tue, 30 Apr 2013 09:25:40 GMT
Prasanna - Thanks for your question. The reasons for not using createTags
are as follows :-

- tags functionality is for grouping resources than adding meta
information and is allowed to all users. What I am proposing is for the
to have better control over the first class objects in CS. This ability
should be with admin only.
- Also list* (* == volume, vm etc.) APIs can list the tags for the enduser
and mixing tags with the meta information wouldn't go well as they
are admin only. I don't want to mix the meta information with the resource
response because they are not the attributes of the resource, we should
try to get to this model in future.
(Like we don't want to add stats to vm response )
- Lets not use something just because they seem similar, because they both
might evolve in a different way in future.

Hope you agree. Let me know your thoughts on this.


On 30/04/13 11:06 AM, "Prasanna Santhanam" <> wrote:

>On Mon, Apr 29, 2013 at 04:01:27AM +0000, Nitin Mehta wrote:
>> I would like to merge the feature which will add the ability in CS so
>>that the user can have better control over first class objects in CS
>> - The feature can be found in the branch cs-2163 and has been rebased
>>with master.
>> - Jira ticket:
>> - The FS can be found @
>> - I have added the unit tests and marvin tests as well.
>> - I ran the RAT check as well with no failures.
>Why not just use resource tags to convey this meta-information? All it
>would mean for the third-party subscriber would be to get this from
>the event bus as you mentioned.
>createTags  & resourceType = VM/Disk/Snapshot etc & key=k, value=v?
>Powered by

View raw message