You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by "Ivan (JIRA)" <ji...@apache.org> on 2013/11/05 11:46:18 UTC
[jira] [Updated] (LIBCLOUD-395) Unify metadata handling in AWS and
OpenStack
[ https://issues.apache.org/jira/browse/LIBCLOUD-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan updated LIBCLOUD-395:
--------------------------
Attachment: (was: 0001-Unify-argument-order-in-crate_node-AWS-OpenStack.patch)
> Unify metadata handling in AWS and OpenStack
> --------------------------------------------
>
> Key: LIBCLOUD-395
> URL: https://issues.apache.org/jira/browse/LIBCLOUD-395
> Project: Libcloud
> Issue Type: Improvement
> Components: Compute
> Reporter: Ivan
> Priority: Trivial
> Labels: patch
>
> AWS and OpenStack should handle node metadata the same way.
> Currently OS has ex_metadata argument for create_node while for AWS the user needs to call an additional function. Also there is not an unified way to get metadata.
> Proposed fixes:
> - unify argument order in docstrings for create_node in both AWS & OS
> - add ex_metadata argument to create_node for AWS (EC2)
> - add ex_get_metadata_for_node to both drivers for AWS and OS
--
This message was sent by Atlassian JIRA
(v6.1#6144)