On 06/05/13 5:18 PM, "Prasanna Santhanam" <t...@apache.org> wrote:
>> >> Agree. There could be use cases for both services that are cloud >>provider >> managed (admin) vs self-service that need to access/store meta-data. We >> need to keep design to be flexible. Also current proposal to add new API >> for each of the action (add/update/remove) and corresponding entity >> (AddNicDetail, UpdateVolumeDetail etc) looks too redundant. IMO, we can >> just have create/delete/List/Update meta data API's with resource type >>and >> id. We can keep API's both user and admin accessible. > >Like createTags, listTags, deleteTags? >From the design of API perspective, yes. But as I mentioned earlier, I would like think resource meta-data as separate from the 'tags'. > >-- >Prasanna., > >------------------------ >Powered by BigRock.com > >
