[
https://issues.apache.org/jira/browse/LIBCLOUD-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858762#comment-13858762
]
Tomaz Muraus commented on LIBCLOUD-482:
---------------------------------------
Since this is a relatively big change, it's good to start with a proposal on
the mailing list.
You can find some instructions and examples on the following links:
*
https://libcloud.readthedocs.org/en/latest/faq.html#i-want-to-add-propose-a-new-api-what-should-i-do
(this talks about adding a new api, but same things apply if you just want to
"promote" some functionality to be part of the standard API)
*
http://mail-archives.apache.org/mod_mbox/libcloud-dev/201312.mbox/%3CCAJMHEmKOsFYJZDZQLb_Z2q1Rs8Ke%2B%2BxUNnqqEbPjyTccTgPYHQ%40mail.gmail.com%3E
> Add EC2SecurityGroup and EC2SecurityGroupRule to ec2 driver
> -----------------------------------------------------------
>
> Key: LIBCLOUD-482
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-482
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Reporter: Chris DeRamus
> Priority: Minor
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Given that Amazon EC2 security groups are similar to OpenStack security
> groups, I will be adding two new classes to the ec2 driver. These classes
> will be used to store all security group properties as well as ingress/egress
> rules.
> The ex_list_security_groups method will be updated to return a list of
> EC2SecurityGroup instance objects instead of what it returns today: a simple
> list of group names.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
