cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kishan Kavala (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-3153) [UI] Network ACL : Incorrect API calls when changing the rule number
Date Tue, 23 Jul 2013 06:18:51 GMT


Kishan Kavala commented on CLOUDSTACK-3153:

Network ACL AWS docs:
They recommend the following when creating ACL items:
"We recommend that you leave gaps between the rule numbers (such as 100, 200, 300), rather
than using sequential numbers (101, 102, 103). This makes it 
easier add a new rule where it belongs without having to renumber the existing rules."

For the example you mentioned, if there is no unused number at the desired position, UI should
throw an error and fail the operation. UI should not make multiple API calls for updating
a single VAL item
> [UI] Network ACL : Incorrect API calls when changing the rule number
> --------------------------------------------------------------------
>                 Key: CLOUDSTACK-3153
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.2.0
>            Reporter: Kishan Kavala
>            Assignee: Kishan Kavala
>            Priority: Critical
>             Fix For: 4.2.0
> After creating Network ACL rules, UI for changing the number is not correct.
> UI should just update the number of rule that is moved. It should be a single updateNetworkACL
API call.
> UI currently fires 2 APIs and both of them fail. UI should not try to swap the numbers.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message