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

Ivan updated LIBCLOUD-395:
--------------------------

    Attachment: 0003-Add-ex_get_metadata_for_node-to-AWS-and-OpenStack.patch
                0002-Add-ex_metadata-parameter-to-create_node.patch
                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
>         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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to