[
https://issues.apache.org/jira/browse/LIBCLOUD-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858382#comment-13858382
]
Tomaz Muraus commented on LIBCLOUD-482:
---------------------------------------
Yeah, promoting security group management methods to be part of the base
compute API is definitely on top of my priority and to do list.
This is a relatively big and time consuming task (similar to the key pair
methods promotion) and I'm pretty busy atm so I don't think I will personally
have time to do it in the next month or so, but if someone else could take a
stab at, it would be great!
I would also prefer if this would be tackled before / instead of adding any
more extension methods for managing security groups.
Adding more extension methods at this point just means more technical debt and
more code to maintain and support once those methods are promoted. The problem
is that once you add something, people start rely on it and if you want to be
good to your users, you can't just remove it.
> 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)
