There was a discussion regarding API name alias [1]. After adding API name
alias, we still need to have different response tags for backward
compatibility.
New: ..
Old: ..
If we are to use the same API, networkId and aclId both have to be made
optional. Would it better to have new API createNe
t;Please find my response inline:
>
>> -Original Message-
>> From: Manan Shah [mailto:manan.s...@citrix.com]
>> Sent: Thursday, 21 March 2013 11:05 PM
>> To: dev@cloudstack.apache.org
>> Cc: Manan Shah
>> Subject: Re: [Discuss] ACL deny rules
>>
Please find my response inline:
> -Original Message-
> From: Manan Shah [mailto:manan.s...@citrix.com]
> Sent: Thursday, 21 March 2013 11:05 PM
> To: dev@cloudstack.apache.org
> Cc: Manan Shah
> Subject: Re: [Discuss] ACL deny rules
>
> Thanks Kishan for sharing t
Thanks Kishan for sharing the FS. Below are some of my questions.
1. What is the default for an empty container? Is it allow all or deny all?
2. Can you describe the behavior for upgrades?
3. Can you also make sure that deletion of Containers will be blocked when
containers are attached to Tiers?
I would like add support for ACL deny rules in VPC. Functional spec is
available at [1] and jira ticket is [2].
As part of this feature, NetworkACLContainer will also be introduced to manage
network ACLs.
This feature is item 2.16 in nTier Apps 2.0 requirements [3].
[1]
https://cwiki.apache.o
