libcloud-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Morris (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LIBCLOUD-930) EC2 create_node should supply tag data to RunInstances rather than tagging separately
Date Wed, 12 Sep 2018 19:08:00 GMT

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

Tom Morris resolved LIBCLOUD-930.
---------------------------------
    Resolution: Fixed

This was fixed by this ldpenti PR [https://github.com/apache/libcloud/pull/1100]

 

I think the fix versions are 2.2.1 and 2.3, but the selector doesn't allow those.

> EC2 create_node should supply tag data to RunInstances rather than tagging separately
> -------------------------------------------------------------------------------------
>
>                 Key: LIBCLOUD-930
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-930
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>            Reporter: Tom Morris
>            Priority: Major
>
> While LIBCLOUD-690 is a real bug, it'd be moot if things were done correctly with the
tagging metadata being provided to the AWS RunInstances call where it could be applied atomically
with the creation of the node. The current style of doing it in two separate calls allows
for a window where nodes can get created without their associated tags, making accounting
for them much more difficult.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message