libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomaz Muraus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LIBCLOUD-375) Unify ex argument for security groups of create_node for AWS and OpenStack
Date Thu, 28 Nov 2013 09:01:52 GMT

     [ https://issues.apache.org/jira/browse/LIBCLOUD-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tomaz Muraus updated LIBCLOUD-375:
----------------------------------

    Fix Version/s: 0.14.0-beta3

> Unify ex argument for security groups of create_node for AWS and OpenStack
> --------------------------------------------------------------------------
>
>                 Key: LIBCLOUD-375
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-375
>             Project: Libcloud
>          Issue Type: Improvement
>          Components: Compute
>            Reporter: Ivan
>            Priority: Trivial
>             Fix For: 0.14.0-beta3
>
>
> When creating a new node, OpenStack and AWS use different names for ex argument for security
groups although the underlying feature is the same.
> OpenStack uses 'ex_security_groups'
> AWS uses 'ex_securitygroup'
> Proposed solution: rename AWS argument to match OpenStack's. (as both support multiple
groups)
> https://github.com/ikusalic/libcloud/compare/unify-ex-security-groups
> If this is problem because it is not backwards compatible, maybe adding alias 'ex_security_groups'
to AWS makes sense.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message