[
https://issues.apache.org/jira/browse/LIBCLOUD-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952296#comment-14952296
]
ASF subversion and git services commented on LIBCLOUD-749:
----------------------------------------------------------
Commit 64876e9fc12d428fba99aafc4d3691db25d60598 in libcloud's branch
refs/heads/trunk from lionel
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=64876e9 ]
[LIBCLOUD-749] CloudStack: minor fixes to comply with pep8.
Closes #580
Signed-off-by: Tomaz Muraus <[email protected]>
> CloudStack: bugs in the method ex_authorize_security_group_ingress
> ------------------------------------------------------------------
>
> Key: LIBCLOUD-749
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-749
> Project: Libcloud
> Issue Type: Bug
> Components: Compute
> Environment: CloudStack compute driver
> Reporter: L. Schaub
> Labels: Bug, CloudStack, Improvement, SecurityGroups
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> The method ex_authorize_security_group_ingress contains some bugs:
> - The docstring doesn't match parameters of the method.
> - Only ICMP and TCP is allowed even if the doc of the parameter "protocol"
> mention TCP and UDP.
> - Moreover ICMP cannot be used because there is no way to specify the two
> required parameters "icmptype" and "icmpcode".
> - The parameter endport is not used if it's defined.
> - The return type is not a list but a dict.
> - The unit test doesn't use parameters in the correct order.
> So I created a patch which aims to fix these bugs and also try to do the
> following:
> - Improve the docstring to be a bit more detailed (the previous one comes
> from the official Apache CloudStack documentation).
> - Add a kwargs to allow to provide extra parameters defined in the API and in
> the docstring.
> - Improve the unit test.
> - Add support for other protocols like AH, GRE, ESP which are available on
> some Cloud like Exoscale.
> I will provide the patch as a Pull Request in GitHub.
> Regards
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)