Re: networkACLList

2013-06-06 Thread Prasanna Santhanam
: Thursday, 6 June 2013 8:03 AM > > To: dev@cloudstack.apache.org > > Subject: Re: networkACLList > > > > On Wed, Jun 05, 2013 at 05:43:31PM +, Kishan Kavala wrote: > > > Agree that it is redundant. They should be create/list/delete > > > NetworkACL.

RE: networkACLList

2013-06-06 Thread Kishan Kavala
ilto:t...@apache.org] > Sent: Thursday, 6 June 2013 8:03 AM > To: dev@cloudstack.apache.org > Subject: Re: networkACLList > > On Wed, Jun 05, 2013 at 05:43:31PM +, Kishan Kavala wrote: > > Agree that it is redundant. They should be create/list/delete > > NetworkACL. But the

Re: networkACLList

2013-06-05 Thread Prasanna Santhanam
On Wed, Jun 05, 2013 at 05:43:31PM +, Kishan Kavala wrote: > Agree that it is redundant. They should be create/list/delete > NetworkACL. But these API names are already used for rules (ACL > items) within the ACL List. > This cannot be fixed without breaking backward compatibility. I was talk

RE: networkACLList

2013-06-05 Thread Kishan Kavala
...@citrix.com] Sent: Wednesday, June 05, 2013 7:40 PM To: dev@cloudstack.apache.org Subject: RE: networkACLList +1 to this . Sounds more logical and easy to differentiate from an end user perspective as we are actually creating a container/group of acl rules there. -Original Message- From

RE: networkACLList

2013-06-05 Thread Pranav Saxena
+1 to this . Sounds more logical and easy to differentiate from an end user perspective as we are actually creating a container/group of acl rules there. -Original Message- From: Prasanna Santhanam [mailto:t...@apache.org] Sent: Wednesday, June 05, 2013 7:14 PM To: CloudStack Dev Su