cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9957) Annotations on entities
Date Thu, 19 Oct 2017 06:58:00 GMT


ASF subversion and git services commented on CLOUDSTACK-9957:

Commit 285fd77674c20c2546b157ad0662f3fc4b640633 in cloudstack's branch refs/heads/master from
[;h=285fd77 ]

CLOUDSTACK-9957 test fix (#2297)

* tyopos in test
* unittest to prove interface
* test logic flaw fixed

> Annotations on entities
> -----------------------
>                 Key: CLOUDSTACK-9957
>                 URL:
>             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:
> 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

View raw message