You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@libcloud.apache.org by "Tomaz Muraus (JIRA)" <ji...@apache.org> on 2013/11/02 20:56:17 UTC
[jira] [Commented] (LIBCLOUD-395) Unify metadata handling in AWS
and OpenStack
[ https://issues.apache.org/jira/browse/LIBCLOUD-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812132#comment-13812132 ]
Tomaz Muraus commented on LIBCLOUD-395:
---------------------------------------
First sorry for the delay. It looks like this patch slipped through.
I tried to apply it, but there are a bunch of conflicts (some of them are related to recent docstring format changes and other seem to be related to other changes).
Can you please re-generate the patch against the latest trunk?
Thanks!
> 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
> Attachments: 0001-Unify-argument-order-in-crate_node-AWS-OpenStack.patch, 0002-Add-ex_metadata-parameter-to-create_node.patch, 0003-Add-ex_get_metadata_for_node-to-AWS-and-OpenStack.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)