[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205810#comment-16205810
 ] 

ASF subversion and git services commented on CLOUDSTACK-9957:
-------------------------------------------------------------

Commit a379230e8efb3014043cd4efd676178aeba00f2c in cloudstack's branch 
refs/heads/CLOUDSTACK-10012 from [~dahn]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=a379230 ]

CLOUDSTACK-9957 Annotations (#2181)

* annotations on hosts

* Adding marvin tests

* rebase error

* review comments

* context for owner

* review

* illegal entity test

* entityType check on input

* Annotation events

* rebase issues


> Annotations on entities
> -----------------------
>
>                 Key: CLOUDSTACK-9957
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9957
>             Project: CloudStack
>          Issue Type: New Feature
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Daan Hoogland
>            Assignee: Daan Hoogland
>             Fix For: 4.11.0.0
>
>
> An admin may wish to be able to add a text field for a node if it is placed 
> in Maintenance or Disabled - so that the next cloudstack admin knows as to 
> why the action has been taken. this can be implemented so it can be extended 
> to other entities like networks, pods, storages, etc, with the additional of 
> an ‘annotation’ table. This table could be accessed either by the extension 
> of individual APIs ie. listHosts, listVirtualMachines, listNetworks, 
> listSnapshots, listFirewallRules or via a new API command – listAnnotations. 
> Creating the new API command allows annotations to be created for all 
> elements without the related list APIs being updated, while it does not block 
> APIs from being updated for further convenience. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to